Video hosted on LinkedIn. Open the original video if the player is unavailable.
An overdue balance is a starting point. The collections team still needs to decide which customers to focus on, understand the outstanding transactions and prepare the next communication.
In my July 2026 demonstration, I explored how Copilot Cowork could support that journey using D365 Finance and Operations data, an interactive dashboard and printable collection letters.
The business request
The demonstration starts with a practical instruction: build an interactive dashboard of customer balances more than 60 days past due, with multilingual, printable collection letters.
This brings two activities into the same experience: understanding overdue exposure and preparing a customer communication.
From financial data to a working view
In the video, Cowork uses the D365 plugin to work with customer and transaction data. The resulting dashboard presents outstanding balances with filters for country, currency and ageing bucket.
For a collections user, those filters help organise the work. A country view supports a regional discussion. A currency view helps separate balances that should not be read as one undifferentiated total. An ageing view makes the oldest outstanding items easier to identify.
The demonstration focuses on making the information easier to explore and use. It does not provide a measured comparison of processing time or a production reconciliation assessment.
Preparing the collection letter
The next step is a multilingual, printable collection letter. The video shows a notice for a customer in China and describes support for further languages, including Thai, Arabic and German.
The important shift is the connection between the balance being reviewed and the communication being prepared. The user can move from identifying an overdue customer to a document they can review.
The demonstrated output is a printable letter. This article does not imply that a letter was automatically sent to the customer.
Why this matters for Credit and Collections
My original post described a move from insight to action. This example makes that idea tangible: a finance user asks for a business outcome and receives a working view of the balances together with a proposed next step.
The potential value is less effort moving between data extraction, analysis and document preparation. Whether that improves collections performance depends on the quality of the financial data, the usefulness of the output and how the team incorporates it into its daily work.
What I would validate before using it operationally
The following are implementation recommendations, rather than results established by the video:
- Reconcile the dashboard to the agreed D365 source, using a defined cut-off date and legal entity scope.
- Confirm how the selection handles ageing, settlements and balances in different currencies.
- Review the letter against the customer account, transaction details and intended language.
- Define who can prepare, approve and send customer communications.
- Confirm the specific plugin, permissions and environment setup before treating the demonstration as a repeatable production process.
Watch the original demonstration
The embedded 1 minute 50 second video shows the dashboard and collection-letter experience described here. You can also open the original LinkedIn post using the link below.
The question for an implementation team is practical: where should the experience help a collections specialist prepare the work, and where should the specialist review and authorise the next action?
Standard ageing reference
For the D365 baseline, Microsoft explains how customer ageing snapshots calculate aged balances at a point in time, using a selected date criterion and company scope. See Customer aging snapshots on Microsoft Learn.
This reference supports the ageing concepts to validate. It does not establish that the dashboard in the video uses the standard ageing snapshot implementation.
Continue the discussion