How to automate AR collections
Collections that depend on someone remembering to follow up will always be inconsistent. A bucket-based dunning cadence never forgets.
Why manual collections fail
Manual collections depend on a person checking an aging report, remembering who is overdue, and deciding what to say - every week, for every customer. It works for a handful of accounts and breaks down as volume grows, because the effort scales with headcount, not with a process.
Where teams get it wrong
- Sending the same reminder tone to a 5-day-late invoice and a 90-day-late invoice.
- Chasing invoices reactively when cash is tight instead of on a fixed schedule.
- No clear escalation path from automated reminder to a phone call to a collections hold.
- Losing track of which invoices are in dispute versus simply unpaid.
- Not closing the loop with an easy way for the customer to pay right from the reminder.
The Collections Automation Framework
- 1Segment open invoices into overdue buckets - current, 1-30, 31-60, 60+ days.
- 2Define a message and channel for each bucket, escalating tone as invoices age.
- 3Schedule automated dunning runs on a fixed cadence per bucket.
- 4Include a direct online payment link in every reminder.
- 5Flag disputed invoices out of the automated queue and into a named owner.
- 6Escalate invoices that clear a final threshold to a human collections call.
How Fintra automates collections
| Step | What Fintra does |
|---|---|
| Segment buckets | AR aging automatically groups every open invoice by days overdue. |
| Define escalation | Dunning/collections runs apply an escalating message by overdue bucket. |
| Schedule runs | Reminder runs execute automatically on a fixed cadence, no manual trigger needed. |
| Enable payment | Online payments let a customer settle directly from the reminder. |
| Handle disputes | Disputed invoices route to a named owner instead of continuing through automated dunning. |
| Escalate | Aging past a final threshold flags the account for a human follow-up call. |
The pattern holds here too: automation runs the routine, repetitive cadence, and a human handles the judgment calls - disputes, hardship, escalation - that a template message cannot.
Your collections automation checklist
Set these up before your next collections cycle
- Segment open invoices into at least four overdue buckets.
- Write a distinct message for each bucket, escalating in tone and urgency.
- Schedule reminder runs on a fixed cadence, not ad hoc.
- Add a direct payment link to every automated reminder.
- Define the threshold at which an invoice escalates to a human call.
- Route disputed invoices out of automated dunning immediately.
- Review collections effectiveness monthly against your DSO target.
Frequently asked questions
What is a dunning process?
Dunning is the structured process of reminding customers about overdue invoices, typically with escalating urgency as an invoice ages further past due. An effective dunning process segments invoices by how overdue they are and sends a different message and channel to each segment, rather than a single generic reminder to everyone.
Can collections be fully automated?
The routine reminder cadence - messages by overdue bucket, sent on schedule, with a payment link - can run automatically. What should stay human is judgment: disputes, hardship cases, and any account that crosses a final threshold where a phone call is more effective than another email. Automation handles the volume; people handle the exceptions.
How many overdue buckets should a dunning process use?
Four is a common, workable starting point: current, 1-30 days, 31-60 days, and 60-plus days overdue. Fewer buckets can lump very different situations together; many more adds complexity without much added precision for most small and mid-sized businesses.
What should happen to a disputed invoice in an automated system?
It should be pulled out of the automated dunning queue immediately and routed to a named owner, since continuing to send escalating payment reminders on a legitimately disputed invoice damages the customer relationship and does not resolve the actual issue. The dispute needs a conversation, not another automated message.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Let dunning run itself, by bucket
Fintra automates reminder runs by overdue bucket and hands you only the exceptions. Free to start, no card required.
Talk to us