Weekly DSS call

## Summary ### The Core Problem: Unknown Vendor Customers The central issue discussed was the occurrence of "unknown" vendor customers in the system. This problem arises when DSS fails to process a bill for any reason, preventing the system from correctly identifying and setting the vendor customer associated with that bill. A significant concern is that these "unknowns" do not trigger any alerts or appear in standard operator workflows, making them difficult to detect without manual intervention. ### Root Cause Analysis The primary source of these unknown records was traced back to the process of uploading bills through the FDG Connect platform, specifically when using the download helper feature. It was noted that during this upload method, information was not being retained properly before being sent to DSS, leading to the identification failures. While a recent fix was deployed to address duplicate bill issues, the fundamental challenge of identifying the vendor customer before DSS fully processes the bill remains a systemic design consideration. ### A Short-Term Monitoring Solution To address the immediate need for visibility, a new monitoring tool was introduced. This is a modified version of the system status report within Power BI, which now includes a dedicated view for tracking unknown vendor customers. This new report provides a queue-based overview, showing approximately 2,100 records currently stuck in the "account setup" phase, with smaller numbers in other queues like DSS IPS. The report allows team members to look up problematic batches using the provided document batch IDs, enabling manual investigation and resolution. ### Investigation and Cleanup Strategy Initial analysis of the unknown records suggests that a large portion are likely duplicates, many dating back to July and September, which have probably been repulled and reprocessed successfully since. The strategy for handling these involves a manual review process, with an expectation that most will be deleted from the system. The team plans to incorporate a daily check of the new report into their routine to proactively manage this issue moving forward. ### Long-Term Considerations and Next Steps The discussion concluded with an acknowledgment that while the new report provides a crucial short-term solution for monitoring, a more robust, long-term fix is needed to "stop the leakage" and prevent unknown unknowns from entering the system in the first place. The underlying design decision regarding how and when vendor customer information is populated from DSS was flagged as an area requiring further discussion and potential redesign.