AI Agents in Accounts Receivable: Where It Breaks
Collections happen when someone remembers, which means late.
The loop, as it actually runs
- Invoice issued
- payment terms tracked
- reminder sequence runs
- payment received
- applied to invoice
- exceptions escalated
Where it breaks
Not in the steps. In the joins between them:
- Dunning depends on a person remembering
- Payments get applied to the wrong invoice
- Disputes sit unowned
- Nobody sees ageing until month end
What that actually costs
Days sales outstanding is the number this function is judged on, and most of what inflates it is not customers refusing to pay. It is the reminder that went out on day forty instead of day thirty-one because nobody had time, the dispute that sat unowned for three weeks because it arrived as a reply to an invoice email, and the payment applied to the wrong invoice so the account still shows a balance. Every one of those is a timing failure rather than a credit failure, and timing failures are what software is actually good at fixing.
What we would build first
The reminder sequence goes first, because it is the single change that moves DSO and it requires no judgement at all. A schedule that runs whether or not anyone remembers — a note before the due date, one on it, then escalating — is more effective than the sporadic version not because the messages are better but because they are certain. Build it before payment application, before dispute routing, before anything clever. Consistency is the entire mechanism.
It runs inside Stripe, QuickBooks Online, Bill.com, Gmail, Slack — the tools already in use.
How this one goes wrong
The failure that costs you a customer is dunning aimed at someone who has already paid. It happens when payment application lags the reminder schedule: the money arrived, nobody matched it, and the timer fired anyway. The guard is an interlock rather than a tuning exercise — any unapplied payment or open dispute on the account pauses the sequence immediately, and it resumes only when a person clears the flag, never on a timer. Automated persistence is an asset right up until it is pointed at the wrong person, at which point it is worse than doing nothing.
The individual jobs inside this loop — what starts each one and where it has to hand back to a person — are covered under finance & bookkeeping.
Where it lands hardest: accounting & CPA firms, medical & dental practices, property management, insurance brokerages and managed service providers. Each of those pages carries the sector’s own economics — the three roles that absorb the work, and the season that decides when a build can start.
In most companies this work sits with bookkeepers, billing clerks, medical office administrators and claims processors. Each of those pages carries the wage arithmetic for that role, and says plainly where the numbers do not justify the spend.