AI Agents for Dynamics
365 Receivables
Posting cash without settling it is fast, and it moves the work to whoever runs the ageing review under more time pressure.
- Cash posted on account without settlement leaves the customer balance right and everything built on which invoice was paid wrong.
- Match in order: the customer's own reference, then the normalised invoice number, then a combination against the total, and amount last. Amount first settles the wrong invoice.
- In a worked population of 96 unsettled receipts, 18 a month came from one configuration gap where the customer reference never reached the invoice.
- Credit limits test against a balance inflated by unsettled cash and disputes, and excluding open orders. Both distortions push the wrong way.
- Report credit holds caused by something already resolved. It takes one query and it is revenue sitting still for no reason.
AI agents for Dynamics 365 Finance accounts receivable propose the settlement rather than just the receipt, match on the references customers actually use, and report the credit holds caused by something already resolved. ChatFin traces every settlement line to a specific invoice and settles nothing itself.
The pattern worth naming is cash posted on account and settled later. It is quick, the customer balance is correct, and everything downstream that depends on which invoice was paid is not: the ageing, credit exposure, collections lists, dimension analysis and settlement discount windows. The work moves to whoever runs the ageing review, under more time pressure than the person who posted the receipt.
Settlement is where a Dynamics receivable is really decided
ChatFin sees the same pattern on most Dynamics 365 implementations. Cash arrives, gets posted, and settlement against specific invoices is left for later. The customer balance is right. Everything built on which invoice was paid is not.
| What a payment on account breaks | Why it matters |
|---|---|
| The ageing | Old invoices look unpaid while cash sits unsettled |
| Credit exposure | The customer appears at their limit when they are not |
| Collections lists | People get chased for balances already covered |
| Revenue and dimension analysis | Which invoice was paid drives which dimension cleared |
| Settlement discounts | The window passes while the receipt sits on account |
Posting cash without settling is fast and it moves the work to whoever runs the ageing review, usually under more time pressure than the person who posted it.
ChatFin proposes the settlement, not just the receipt, with every line traced to a specific invoice. It settles nothing itself.
What to match on, in order
Order matters. Amount first is how a receipt settles the wrong invoice.
The customer's own reference
Their purchase order or document number, present on the invoice only if billing captured it. This is your match rate ceiling
The invoice number, normalised
Strip punctuation and leading zeros before comparing
A combination constrained by the receipt total
One receipt settling forty invoices is routine, blind subset testing is not
Amount against a single open invoice, last
Unambiguous only when one invoice matches, and dangerous when several do
A worked unsettled population, 96 receipts
96 receipts posted on account, 1.4 million, at month end.
| Cause | Receipts | Value | Where it belongs |
|---|---|---|---|
| Remittance arrived separately, never matched up | 28 | 486,000 | Settle from the remittance |
| Payer name differs from the customer | 21 | 310,000 | Resolvable, then a master data fix |
| Customer reference not on the invoice | 18 | 204,000 | Billing configuration. Recurs monthly |
| Short by a settlement discount | 17 | 112,000 | Allowable, settle on the rule |
| Genuine deduction | 12 | 288,000 | Commercial, not receivables |
The third row is 18 receipts every month caused by one configuration gap. The other four are work. That one is a fix.
Credit management that reflects reality
Dynamics credit limits test against a balance that includes unsettled cash and excludes unbilled orders. Both distortions push in the wrong direction.
ChatFin reports customers whose credit hold is caused by something already resolved, which is revenue sitting still for no reason and takes one query.
Where this underperforms
Three.
Deeper in Dynamics 365 receivables
Three use cases sit under this hub, in build and shown rather than linked.
Worked on this page
AR inbox automation · Open AR analysis · Bank payment to open invoice matching
Covered as sections here
Settlement · Cash application · Credit management · Collections · Deductions
Questions Dynamics 365 receivables teams ask first
Why does posting cash on account cause problems later?
Because the customer balance is right and nothing else is. Old invoices look unpaid, the customer appears at their credit limit, collections chase balances already covered, settlement discount windows pass, and dimension analysis is wrong because which invoice cleared drives which dimension cleared. ChatFin proposes the settlement with every line traced to a specific invoice rather than leaving it for the ageing review.
What order should cash be matched in?
The customer's own reference first, then the invoice number with punctuation and leading zeros stripped, then a combination constrained by the receipt total, and amount against a single open invoice last. Amount first is how a receipt settles the wrong invoice of the same value, which clears the queue and misstates the analysis.
Why are credit holds often wrong in Dynamics?
Because the balance they test against includes unsettled cash and disputed invoices while excluding open sales orders. A customer who has paid can appear at their limit, and a customer with large committed orders can appear well within it. Holds also rarely get reviewed once the cause clears. ChatFin reports the ones caused by something already resolved, which is a single query.
Settle the receipt, not just post it.
ChatFin proposes settlement with every line traced to a specific invoice, matching on the references customers actually used rather than on amount.
It reports credit holds whose cause has already cleared, and settles and contacts nobody.
Bring one month of receipts posted on account. The comparison takes an hour.
Book a demoAll images are served from the Pexels content network. No third party product screenshots, vendor logos or licensed media are used on this page.
Bring one month of unsettled receipts.
We will group them by cause through ChatFin, propose the settlements, and show you which configuration gap is producing them every month.