The short version
- Credit control is the best first job to automate in most finance teams: repetitive, disliked, and measurable in cash rather than in vague hours.
- The agent watches the ledger, chases on a schedule in your own wording, escalates what stays unpaid and logs every reply against the account.
- It must never decide who gets legal action, who gets a payment plan, or which relationships are worth protecting.
- The test is not “hours saved”. It is whether debtor days move and whether the awkward conversations happen earlier.
Why this job and not a more interesting one
Four things make a task suitable for an agent, and chasing invoices has all four.
- It has a right answer. An invoice is either overdue or it is not, and two sensible people would take the same action.
- It repeats every week, forever, which is where the compounding is.
- It is disliked, and disliked jobs slip. The slipping is what costs the money.
- The outcome is cash, so you do not have to argue about whether it worked.
Contrast that with advisory work, where the answer depends on judgement and the judgement is the value. That is the wrong job to hand over, and handing it over is how firms end up disappointed with AI.
What the agent actually does
It watches the ledger rather than waiting to be asked, which is the whole difference between an agent and a chatbot.
- Day one after the due date. A short, polite reminder in your firm’s wording, not a template that reads like a debt collector.
- Day seven. A follow-up that acknowledges the first one and takes account of anything the client said in between.
- Still unpaid. Escalation on your rules, with the case prepared for a person rather than dumped on them cold.
- Throughout. Every reply logged against the account, so the history is in one place instead of in somebody’s inbox.
What arrives on Monday morning is not a full inbox. It is a short list of the accounts that genuinely need a phone call, with the context already attached.
What stays with a person
Three decisions should never sit with the agent, and we would decline to build it that way:
- Who gets legal action. That is a commercial and relationship decision.
- Who gets a payment plan, and on what terms.
- Which relationships are worth protecting even when the invoice is late.
The agent’s job is to make sure those decisions get made early, with the facts assembled, instead of three months late because nobody had time to chase.
Isn’t this just the reminders my software already sends?
A fair objection, and built-in reminders do solve part of it. Where they fall down is memory and tone. A fixed template on a fixed timer does not know the client replied last week promising payment on the 20th, and it does not escalate. It sends the same message again, which is worse than nothing because clients learn to ignore it.
The difference worth paying for
An agent reads the replies, adjusts what it says, escalates properly, and tells a human exactly when to step in.
How to know if it is worth it
Two numbers you already have. What are your debtor days now, and how many hours a month does somebody spend chasing? If the honest answer to the second is “not enough, we know we are behind”, that is the finding, and it is the argument for doing something, not against it.
Start there, measure for a quarter, and expand only if the numbers move. We would rather build one thing that demonstrably works than a platform that impresses in a demo.
