A distributor wants collection priority for customers with overdue invoices. Those invoices already live in Dynamics 365 Finance. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
The overdue list on the desk is the one that still matches the ledger. You take collection priority from the finance copilot's view of the live overdue invoices, not from a CSV copied out of Finance. A nightly file is already wrong as soon as someone pays.
Full Explanation
Dynamics 365 Finance already calculates overdue amounts, and the finance copilot in the collections workspace summarizes that live view, including overdue invoices and payment history. Collection priority should come from that view so the collector sees the current invoices, not from a CSV copied out of Finance. A nightly CSV leaves the copilot unused and goes stale when a payment posts after the file is written. A model trained on last quarter's export ignores every invoice posted since the copy and cannot see a payment made this morning. A detached spreadsheet that is refreshed only when someone remembers to export it has the same defect, with a person as the scheduler. Exam caveat: the copilot summarizes Finance's figures. It does not invent the balance. Priority still rests on the live overdue amounts Finance calculated, which is why the copy is the wrong source. Operational check: post a test payment against an overdue invoice, refresh the finance copilot's customer view, and confirm the priority follows the new balance rather than the previous CSV.