AI Agents for Collections
and Dunning
Working the ageing report from the oldest item down is the obvious sequence and close to the worst one.
- Age is weakly related to whether a chase will collect, so working the ageing report oldest first is close to the worst available sequence.
- Disputed, undelivered, awaiting credit and already scheduled items all age identically and none of them responds to a chase.
- A meaningful share of overdue invoices were never received, and a chase on those can only ever end in a request to resend.
- Supplier portals reject invoices silently on format and purchase order mismatches, which produces an ageing row and no notification.
- A statement is more useful as a reconciliation than as a reminder, because the differences it surfaces are why the invoices are unpaid.
AI agents for collections split the ageing report by why each item is unpaid, verify that the invoice was actually delivered, and reconcile the customer statement before anything is escalated. ChatFin sequences chase work by what will collect rather than by how old the invoice is.
Most items on an ageing report do not respond to being chased. They are in dispute, they were never delivered, they are waiting on a credit that finance owes the customer, or they are simply scheduled in the customer's next payment run. ChatFin identifies all of those before a collector spends a day on them and damages a relationship for nothing.
Chasing by age is chasing in the wrong order
Almost every collections process works the ageing report from the oldest item down. It is the obvious sequence and it is close to the worst one, because age is weakly related to whether a chase will collect anything.
| Item at ninety days | Why it is unpaid | Will chasing collect |
|---|---|---|
| Invoice in dispute | A deduction was raised | No, resolve the dispute |
| Invoice never delivered | Sent to a closed mailbox | No, resend it |
| Customer in difficulty | They cannot pay | Not by chasing harder |
| Simply overlooked | No process on their side | Yes, immediately |
| Awaiting a credit | Finance owes them first | No, issue the credit |
| Payment run is monthly | Their cycle, not yours | No, it is already scheduled |
One row out of six responds to a chase. The other five consume the collector's day and damage the relationship, and all of them are identifiable before anyone picks up a phone. ChatFin sequences the ageing by what will actually collect rather than by how old the invoice is.
ChatFin separates the ageing into disputed, undelivered, awaiting credit, scheduled and genuinely overlooked, so a collector works the list that responds.
A surprising share of overdue invoices were never received
The failure mode nobody measures is delivery. An invoice that never reached the customer ages exactly like one that did, and produces an identical row in the ageing report.
ChatFin checks delivery and acknowledgement before anything is escalated, because a chase on an invoice the customer never received produces a request to resend and nothing else.
ChatFin verifies that the invoice was delivered and acknowledged before escalating, which removes the chases that can only ever end in a resend.
Statements are a reconciliation, not a reminder
A customer statement is usually treated as a dunning tool. It is more useful as a reconciliation, because the disagreements it surfaces are the reason the invoices are unpaid in the first place.
| Difference on the statement | What it usually means | Action |
|---|---|---|
| Invoice they do not have | Delivery failure | Resend, do not chase |
| Credit you do not have | They raised a deduction | Investigate the claim |
| Payment you have not applied | Unapplied cash your side | Apply it, do not chase |
| Different amount | A pricing or tax dispute | Resolve before dunning |
| Agrees exactly | A genuine overdue balance | Chase this one |
Only the last row deserves a dunning letter. ChatFin reconciles the statement against the customer's own record where they publish one, and reports the differences by type, so dunning goes only to the balances both sides agree on.
ChatFin reconciles statements before dunning, so escalation goes only to balances the customer already agrees they owe.
Where this underperforms
Three.
Deeper in collections
The use cases this hub covers.
Worked on this page
Collections support · Customer statement preparation · Dunning
Covered as sections here
Ageing segmentation · Delivery verification · Statement reconciliation · Dispute separation
Questions AR managers ask first
What is wrong with working the ageing report oldest first?
It sorts by a field that does not predict collection. An invoice at ninety days may be in dispute, may never have been delivered, may be waiting on a credit note you owe, or may just be scheduled in a monthly payment run. None of those responds to a chase, and all of them are identifiable in advance. ChatFin splits the ageing before the calls start.
How common are invoices that were never received?
Common enough to matter and almost never measured, because an undelivered invoice produces exactly the same ageing row as a delivered one. Mailboxes change after a restructure, recipients leave, and supplier portals reject silently on format or purchase order mismatches. ChatFin checks delivery and acknowledgement before escalating.
Should statements be sent as reminders?
They are worth more as a reconciliation. The useful output is the list of differences: invoices the customer does not have, credits you do not have, payments you have not applied. Each one is a different action, and only a balance both sides agree on deserves a dunning letter. ChatFin reports the differences by type.
Chase the list that responds.
ChatFin splits the ageing into disputed, undelivered, awaiting credit, scheduled and genuinely overlooked, and sequences the work accordingly.
It verifies delivery before escalation and reconciles statements so dunning goes only to balances the customer already agrees they owe.
Bring your current ageing report. The split 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 current ageing report.
We will split it through ChatFin by why each item is unpaid and show you how much of your chase list was never going to respond.