Dynamics 365 collections and disputed invoices
Dynamics 365 Finance skips invoices marked Disputed in collections automation and lists them on their own tab. Resolving the dispute stays your process.
Use the module for what its documentation shows. When an invoice’s collections status is Disputed, collections process automation skips it, and the Collections coordinator workspace lists it on a Disputed invoices tab. Do not expect the module to resolve the dispute. Research, proof, credit decisions and the move back to Resolved need a separate process with one owner. This rests on Microsoft’s Dynamics 365 Finance pages on collections process automation, its FAQ, the Collections coordinator workspace and Review collections information.
What happens to an invoice the customer disputes?
A customer reports a pricing error or a missing delivery and holds payment on one invoice. Your collectors need two things. Dunning stops for that invoice, and the dispute stays visible until someone closes it. Review collections information defines Disputed as “The customer has notified you that there is a problem with the transaction.” Resolved means all problems with the transaction have been solved and no additional collections action is necessary. Not disputed means no collections action has occurred for the transaction. The same document describes changing the collections status for selected transactions. In practice the status is a flag that a collector sets after a call or an email. What matters is what the flag does to automation and to the collector’s view.
How the Disputed status interacts with dunning
The Collections process automation FAQ is direct. If the collections status of the invoice has changed to Disputed or Promised to pay, collections process automation skips that invoice during processing. If the status has changed to Resolved or Promise to pay broken, and the invoice is overdue, automation picks the invoice up again.
Where it re-enters matters. The FAQ example uses an invoice due January 15. If the status is updated on January 24, nine days past due, automation runs the step closest to that date, the Second notice step. If the status is updated on February 2, 17 days past due, only an activity is created. The collection letters are skipped. The FAQ says a new parameter was added in version 10.0.39 to address this. The Collections process automation article says that with Use track step set to Yes, an invoice whose status went from Disputed to Resolved starts at the first step on the Process details tab. That checkbox is available when the track step enhancement feature is enabled in release 10.0.43 and later, and the article says it can’t be disabled.
What collectors see, and what still needs a decision
The Collections coordinator workspace has a Disputed invoices tab that shows any open transactions where the collections status has been updated to Disputed. The Open transactions tab offers Change status, Write-off, Settle and other options. Two mechanics deserve a test in your setup. The Collections process automation article says process steps are based on the leading or oldest open invoice. The FAQ says collection letters are created per customer, not per transaction. We would run Process simulation for a customer with one disputed invoice and one overdue invoice before trusting the letters. We would also decide who approves a write-off on a disputed invoice before collectors use the button. Review collections information shows write-offs using a default journal name and reason code, which is a setting, not a policy.
Can the module carry disputes, or do you need a separate process?
The choice is how much of the dispute lives in the status flag and how much in a resolution flow across customer-to-cash.
| Option | We would choose it when | What we would check first |
|---|---|---|
| Disputed status only | Disputes are rare and settled in one call | Who sets and clears the status |
| Status plus Use track step | Resolved invoices must restart dunning from the first step | Release 10.0.43 or later, feature enabled |
| Status plus collections cases | Several invoices and activities belong to one problem | Whether collectors filter by case |
| Status plus a separate resolution process | Disputes need proof, sales input or credits | One owner and one record per dispute |
What to do this quarter
- Pull every open invoice with collections status Disputed and sort it by days in that status.
- Name one owner who moves a status to Resolved, and list the evidence that person needs.
- Run Process simulation for a customer with a disputed invoice and an overdue invoice, especially in hypercare after an ERP go-live.
- Decide on Use track step at hierarchy level. The FAQ says enabling it later means redoing the process hierarchy.
- Measure how many invoices move from Disputed to Resolved each month and which step they re-enter.
What this means for a bottleneck worth $1M or more
When disputed invoices stack up between collectors, sales and credit, the flag is not the bottleneck. The resolution flow is, and it is worth redesigning as one domain. Rules handle the predictable: status gates, track step, the letter sequence. AI reads the messy part: customer emails, remittances, proof of delivery. People approve credits, write-offs and the move to Resolved. AI never decides alone. Weigh deduction software against process redesign before you buy another tool.
Limits of this evidence
These are Microsoft documentation pages. They describe setup and behavior, not results. They do not show how often invoices are disputed, how long disputes stay open, or what collection outcomes follow. They do not describe how a dispute is researched or resolved, or what a per-customer letter shows when the oldest invoice is disputed. They cover Dynamics 365 Finance only, with no other products, add-ons or benchmarks.
Questions buyers ask
Does a disputed invoice still trigger collection letters?
The Collections process automation FAQ says automation skips an invoice whose collections status has changed to Disputed or Promised to pay. Because letters are created per customer, test in Process simulation what a customer with other overdue invoices receives.
What happens when the dispute is marked Resolved?
If the invoice is overdue, automation picks it up and runs the step closest to that date. With Use track step set to Yes, it starts at the first step on the Process details tab instead.
Can collectors see all disputed invoices in one place?
The Collections coordinator workspace has a Disputed invoices tab that shows open transactions whose collections status has been updated to Disputed. The workspace is enabled in the Feature management workspace.
Sources
Sources give context. Dates show when each was last checked.