Most D365 credit and collections setups are more capable than the team running them realizes. Not because the features are hidden exactly, but because a workspace got configured once, a report location changed in a later release, and nobody went back to check what moved.
This is a list of seven specific things about D365 credit and collections that finance and collections management teams routinely miss, not because the platform lacks them, but because they sit one screen, one setting, or one release note away from where most people are looking. This guide will explore each one and where analytics closes the gap once you know it is there.
1. DSO moved. Most dashboards did not follow it.
Days sales outstanding (DSO) used to live on the Collections overview report inside the Customer credit and collections workspace. As of Dynamics 365 Finance version 10.0.38, Microsoft removed the DSO calculation from that report to fix a performance issue, and moved it to the Credit statistics factbox instead.
Anyone who built a saved view, a screenshot-based report, or a training deck around the old report location is now missing a number that did not actually disappear; it just changed address. Confirming where DSO currently lives, and rebuilding whatever depended on the old location, is a five-minute check that a surprising number of D365 credit and collections teams have not done.
The underlying reason is worth knowing too. The DSO calculation was pulled out of the report specifically because it was slow enough to time out the rest of the Power BI content around it, not because Microsoft decided the metric mattered less. Anyone troubleshooting a slow-loading collections report from an older release should check whether this is the exact issue already fixed by moving on to the current version.
2. There are two collections workspaces, and most teams only use one.
The classic Customer credit and collections workspace is where most organizations start. The Collections coordinator workspace is newer, has to be turned on separately in Feature management, and is built specifically around a collections agent’s day: a Highest balances grid showing credit limit and risk score, an Aged balances grid, and a details page that includes a Copilot-generated summary of a customer’s balance and payment history.
Teams that never enabled it are not missing a minor cosmetic option. They are missing an AI-generated head start on exactly the judgment call, is this customer actually a collections risk, that collections agents spend the most time making manually. Most D365 credit and collections deployments were configured before this workspace existed, which is the whole reason it tends to go unnoticed rather than declined.
Two native workspaces, one Power BI report, and a factbox is already a lot of places to look for one customer’s status. The Metrixs analytics suite puts all of it in one place.
3. An aging snapshot is a snapshot, not a live number.
Nothing shows up on the Aged balances list page or the Collections page until an aging snapshot has actually been generated. The snapshot calculates aged balances for a point in time, and it has to be rerun, manually or on a batch schedule, for that view to reflect anything more recent than the last successful run.
A failed or skipped batch job does not throw an obvious error on the screen collectors are looking at. It just means everyone is working from balances that are quietly a day, a week, or longer out of date, with no visual cue that anything is stale.
Confirming when a D365 credit and collections snapshot last ran successfully takes one extra click most collectors never make, checking the batch job history rather than trusting that the page in front of them refreshed itself. It did not. It is showing exactly what the last completed snapshot calculated, however old that turns out to be.
4. Three different date types can age the same invoice three different ways.
An aging period definition can age transactions by transaction date, due date, or document date. Two companies, or two customer pools inside the same company, set up with different date bases will report different DSO and different aging buckets for what is functionally the same set of invoices.
- Transaction date ages from when the sale was recorded, regardless of payment terms.
- Due date ages from when payment was actually owed, the basis most collections teams assume by default.
- Document date ages from the invoice document itself, which can differ from both of the above depending on posting timing.
Comparing DSO or aging across entities without first confirming they use the same date basis is comparing two different measurements and calling them the same number.
A DSO gap between entities is either a real risk difference or a setup difference, and guessing which is expensive. The Metrixs consulting team can tell you which one you are looking at before you act on it.
5. A credit hold rarely explains itself.
Credit limits, credit available, and risk score all sit on the collections workspace grids as numbers, but the reason a specific order is actually on hold, which rule tripped, which threshold was crossed, is configured back on the customer’s credit and collections setup, not surfaced next to the hold itself.
A collections agent or a sales rep looking at a blocked order sees that it is blocked. Working out why, without a separate trip to configuration, is where a genuinely avoidable back-and-forth eats up time that should have gone toward actually resolving the account.
This gets more expensive at scale. A single credit hold is a two-minute lookup. A D365 credit and collections setup with dozens of credit rules across several customer groups, each rep independently re-discovering which rule applies to which hold, adds up to a lot of repeated investigation for information the system already has, just not displayed where the hold shows up.
6. A broken collection letter sequence fails silently.
The dunning process in D365 F&O runs through collection letter sequences and collections process automation, identifying which invoices need an email reminder, a phone call activity, or a formal collection letter, and applying that consistently instead of leaving it to an analyst’s memory.
That consistency depends entirely on the schedule actually running and the customer pool assignments actually being current. A sequence with a stale customer pool, or a recurrence job that quietly stopped firing, does not alert anyone that dunning has effectively paused. Customers keep aging. Nobody gets a letter. The first sign is usually a customer calling to ask why nobody followed up, which is precisely backward.
Validating a collection letter sequence is not a one-time setup task. Customer pools change as accounts open and close, and a sequence built around last year’s customer list quietly drifts out of sync with this year’s, which is exactly the kind of gap D365 credit and collections will not surface on its own until a customer notices first.
7. None of this rolls up across entities or years on its own.
Individually, every insight above is a native D365 F&O capability, not a missing feature. Collectively, they live across two workspaces, a factbox, a snapshot process, and an automation schedule, each scoped to its own company and its own point in time. Comparing DSO trend over the last eight quarters, or credit risk across five legal entities side by side, means exporting from several of these places and reconciling the date basis, the workspace version, and the snapshot timing by hand.
That reconciliation work is exactly where a dedicated analytics layer stops being optional.
| What you need | Native D365 F&O tools | A dedicated layer such as Metrixs |
|---|---|---|
| DSO trend over several quarters | One point-in-time figure, factbox or report | Configurable history in one saved view |
| Cross-entity credit risk comparison | Exported and reconciled by hand | Consolidated across entities automatically |
| One consistent aging date basis | Set per aging period definition, easy to drift | Standardized and visible across every entity |
| Refresh | As current as the last aging snapshot run | 15 to 30 minutes via Synapse Link |
How Metrixs turns these seven blind spots into one view
Metrixs reads customer aging, credit data, and collections activity through Azure Synapse Link into the same dedicated Azure Data Lake used for the rest of D365 F&O, built across more than 6,000 backend tables.
- DSO, aging, and credit risk held as configurable history, so a quarter-over-quarter trend is a saved report, not a rebuilt export.
- Collections management data consolidated across entities, even across a multi-ERP environment, with one consistent aging basis instead of several silently different ones.
- Refresh every 15 to 30 minutes, inside the same 12-module, 100+ report, 1,000+ metric suite, most deployments live in under 6 weeks, client ROI 290% to 450%.
None of this replaces D365 credit and collections. It reads the same aging snapshots, the same collection letter activity, and the same credit data, and puts all seven of the blind spots above in a single place a collections manager can actually see without knowing which workspace, which factbox, or which release note to check first.
The seven insights above are not really seven separate problems. They are one problem, visibility scattered across releases, workspaces, and companies, showing up in seven different places. Fixing that once, at the reporting layer, is usually less work than fixing each of the seven individually.
Curious what customer aging and credit risk look like consolidated across every entity you run? See the D365 F&O finance and accounting analytics use case.
Frequently asked questions
Where is DSO located in D365 credit and collections?
DSO now appears on the Credit statistics factbox rather than the Collections overview report, following a performance change introduced in Dynamics 365 Finance version 10.0.38. Teams relying on saved views or training material built before that change are often looking in the wrong place without realizing the figure moved rather than disappeared.
What is the difference between the two D365 collections workspaces?
D365 credit and collections actually offers two workspaces, not one. The Customer credit and collections workspace is the original, broader view with Power BI content, while the Collections coordinator workspace is newer, must be enabled in Feature management, and is built around a collections agent’s daily worklist, including a Copilot-generated summary of each customer’s balance and payment history.
How often does customer aging update in D365 F&O?
In D365 credit and collections, customer aging only updates when an aging snapshot is generated, manually or on a batch schedule, not continuously. If a scheduled snapshot job fails or is delayed, the Aged balances and Collections pages continue showing the last successful snapshot with no visible warning that the data is out of date.
Why might DSO differ between two legal entities in D365 F&O?
DSO and aging depend on which date an aging period definition uses, transaction date, due date, or document date. Two entities using different date bases will calculate DSO differently even against comparable invoice data, so a DSO gap between entities can reflect a setup difference rather than an actual difference in D365 credit and collections performance.
How do credit limits affect order processing in D365 F&O?
Credit limits are core to D365 credit and collections: when a customer’s outstanding balance and open orders approach or exceed their credit limit, the system can place new orders on hold based on configured credit rules. The hold itself is visible on the order, but the specific rule or threshold that triggered it is configured separately, so diagnosing why an order is blocked often takes a second lookup.
What is the dunning process in D365 F&O called natively?
Inside D365 credit and collections, the dunning process runs through collection letter sequences and collections process automation, which identify overdue invoices and generate an email reminder, a collection activity, or a formal collection letter based on configured rules. The process depends on customer pool assignments and schedules staying current to keep working.
Can D365 F&O consolidate collections management across multiple entities?
Not as a single automatic view. Aging snapshots, credit statistics, and collections activity are scoped per company, so comparing collections management performance, DSO, or credit risk across legal entities usually means exporting from each entity and reconciling the results, including confirming they share the same aging date basis.
The verdict
None of these seven points is a gap in D365 credit and collections itself. DSO is calculated, aging is tracked, credit limits are enforced, and the dunning process runs on a schedule. The gap is visibility: knowing where each of these lives today, trusting that the data is current, and seeing all of it consolidated across entities and time without a manual reconciliation exercise.
Metrixs closes that gap: reading the same aging, credit, and collections data, refreshing every 15 to 30 minutes, and shipping it as part of the same suite that already covers general ledger, budgeting, fixed assets, and cash flow.
Ready to see your customer aging and credit risk as one connected view? Book a Metrixs reporting assessment, and we will map your collections management setup against what the reporting layer already covers.
