AI Agents for Dynamics
AX Receivables
Years of unsettled receipts means the payment behaviour history that would be most valuable cannot be built at all.
- Long running AX installations accumulate a settlement backlog nobody has cleared. Cash was posted, the balance is right, and which invoice was paid was left for later, for years.
- The backlog breaks the ageing, credit exposure, collections and dimension analysis, and it makes payment behaviour history impossible to compute.
- In a worked backlog, 129 receipts worth 698,000 were settleable from evidence and the oldest 201 were a write off decision rather than a matching problem.
- Separate what is resolvable from what is a policy decision. Leaving both in one backlog is why neither gets done.
- On an old installation the behaviour history is the most valuable asset in the receivables data, and it is unreadable until settlement is done.
AI agents for Dynamics AX accounts receivable work the settlement backlog that long running installations accumulate, separate what can be settled from evidence from what is a write off decision, and build payment behaviour history once settlement is representative. ChatFin proposes settlements and settles nothing itself.
The problem compounds in a way that is specific to old systems. Cash gets posted and settlement is left for later, which is quick and leaves the customer balance correct. Do that for several years and the ageing, the credit position, the collections list and the dimension analysis are all built on cash that was never matched to an invoice.
Settlement, and years of it left undone
AX settles receipts against specific invoices, and ChatFin finds long running installations accumulate a settlement backlog that nobody has ever cleared. Cash was posted, the customer balance is right, and which invoice was paid was left for later, repeatedly, for years.
| What the backlog breaks | Consequence |
|---|---|
| The ageing | Old invoices show unpaid while cash sits unsettled |
| Credit exposure | Customers appear at their limit when they are not |
| Collections | People are chased for balances already covered |
| Dimension analysis | Which invoice cleared drives which dimension cleared |
| Any historic analysis | Payment behaviour cannot be computed from unsettled cash |
The last row matters more than it looks on an old installation. Years of unsettled receipts means the payment behaviour history that would be most valuable cannot be built at all.
ChatFin proposes settlements across the backlog rather than only for new receipts, and ChatFin settles nothing itself because settlement changes customer standing.
A worked settlement backlog
An AX installation with several years of history. Unsettled cash on account, by age.
| Age | Receipts | Value | Realistically resolvable |
|---|---|---|---|
| Current period | 41 | 286,000 | Yes, from the remittance |
| 1 to 6 months | 88 | 412,000 | Mostly, from references and amounts |
| 6 to 24 months | 134 | 318,000 | Partly. Combination matching against open items |
| Over 24 months | 201 | 194,000 | Rarely. Likely a write off decision |
The first two rows are 129 receipts and 698,000 that can be settled from evidence. The last row is a policy decision somebody has to make rather than a matching problem, and naming it as such is more useful than leaving it in the queue.
ChatFin separates what is resolvable from what is a write off decision, because leaving both in one backlog is why neither gets done.
Payment behaviour, once settlement exists
Settled history is what makes behaviour analysis possible, and an old AX database holds more of it than most systems.
Compute days to pay per customer per invoice
From settled receipts, across the full history. ChatFin does this once the backlog is cleared enough to be representative.
Report the distribution, not the average
A customer paying at 30 or at 90 with nothing in between needs both outcomes represented.
Detect shifts over quarters
A customer slowing steadily is the earliest credit signal available.
Price the cash forecast on behaviour
Rather than on stated terms, which are wrong in the same direction every time.
Where this underperforms
Three.
ChatFin reports what share of the backlog it can evidence before proposing anything, because a settlement proposal with no evidence behind it is worse than leaving the receipt unapplied.
Deeper in Dynamics AX 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 backlog · Cash application · Payment behaviour · Collections · Credit exposure
Questions Dynamics AX teams ask first
What does an unsettled backlog actually break?
The ageing shows old invoices unpaid while cash sits on account, credit exposure shows customers at their limit when they are not, collections chase balances already covered, and dimension analysis is wrong because which invoice cleared drives which dimension cleared. On an old installation it also makes payment behaviour history impossible to compute, which is the most valuable thing in the data.
Can a years old backlog be cleared?
Partly, and being honest about which part matters. In a worked backlog, the current period and the first six months were settleable from remittances, references and amounts, totalling 129 receipts and 698,000. Beyond twenty four months it is a write off decision rather than a matching exercise. ChatFin separates the two rather than leaving both in one queue.
Why does settlement matter for forecasting?
Because payment behaviour can only be computed from settled receipts. Days to pay per customer per invoice needs to know which invoice a receipt cleared. On an AX installation holding years of history that behaviour data would be the best input a cash forecast could have, and it is unreadable while the settlement backlog exists.
Clear the backlog, then the history becomes readable.
ChatFin proposes settlements across the whole backlog rather than only new receipts, and separates what is evidenced from what is a write off decision.
Once settlement is representative it builds payment behaviour per customer from years of history, and it settles nothing itself.
Bring your unsettled cash 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 your unsettled cash on account.
We will show you through ChatFin how much of the backlog is settleable from evidence and how much is a write off decision.