An AI Agent That Chases Late Invoices
Chasing money is the job nobody in a small business wants and everybody keeps putting off. An AI agent will do it every single day, in your words, and stop the moment you tell it to.

The most expensive job you keep forgetting
If you run a business with five to fifteen people, late invoice follow-up is almost certainly costing you more than any other unglamorous task on your list. Not because chasing is hard, but because it is awkward, it is nobody's actual job, and it always loses to whatever is on fire that day.
The pattern is familiar. An invoice goes out. Nobody looks at it again until the bank balance gets tight. By then the invoice is forty days old, the person who approved the work has moved on, and you are sending an email that starts with "sorry to chase" — which is a sentence you should never have to write about money you have already earned.
An AI agent that chases late invoices fixes this by being boring and relentless. It checks every day. It knows how many days late each invoice is. It writes the nudge in your voice, at the right level of firmness for that stage, and it waits for your yes before anything leaves your outbox.
What the agent actually does, step by step
Here is the shape of an accounts receivable follow-up agent, described the way you would describe it to a new bookkeeper.
1. It reads your unpaid invoices. Every morning it pulls the list of open invoices from your accounting system or the spreadsheet you actually use, with the amount, the issue date, the due date and the contact.
2. It works out who needs chasing today. Not everyone at once. It sorts by how far past due each invoice is, and it applies your ladder: a gentle reminder at three days, a clearer one at ten, a firm one with the payment terms restated at twenty-one, and a flag to you personally at thirty.
3. It drafts each message individually. Same person, same job, same tone every time — but the specifics are real: the invoice number, the amount, the work it covered, the date it was due, and the payment link. Nothing generic, nothing that reads like a debt collector's template.
4. It shows you the drafts before sending. One list, each with an approve or edit button. Ten invoices takes about ninety seconds to clear.
5. It logs what it did. Every reminder sent, when, and what happened next, so you can see at a glance which clients are habitually slow and which ones just needed a nudge.
6. It notices when someone pays. The follow-up stops. That sounds obvious, and it is exactly the thing that goes wrong when a person is doing this manually across two systems.
The escalation ladder that keeps clients
The reason most small businesses do not automate payment reminders is a real fear: that a blunt automated email will damage a relationship worth far more than the invoice.
That fear is legitimate, and it is a briefing problem, not a technology problem. Write the ladder down and the agent will hold the line better than a stressed human on a Friday afternoon.
A ladder that works for professional services:
- Day 3 past due — assume an oversight. Short, friendly, no mention of terms. "Just flagging invoice 1043 for the March retainer went past its due date on Tuesday — payment link below if it slipped through."
- Day 10 — assume a process problem. Ask who handles payables and offer to resend. This is the message that actually unblocks most invoices, because the problem is usually that it never reached the right inbox.
- Day 21 — restate the terms. Reference the agreed payment window, the amount outstanding, and any late fee that exists in your contract. Still polite, no threats.
- Day 30 — stop and hand it to you. The agent should not decide when to escalate to a phone call, pause work, or involve a third party. That is your call, on relationship information the agent does not have.
Add your exceptions explicitly. Most owners have three or four: the big client who always pays on day 45 and that is fine, the one whose finance team needs a purchase order number on every email, and the one you are mid-negotiation with who should be left entirely alone. Name them, and the agent will respect them permanently.
What it saves, in numbers you can check
Do not take an estimate from a vendor. Do this arithmetic with your own figures.
Count your open invoices in a normal month. For each one that goes past due, the manual version costs roughly five to eight minutes: opening the accounting system, checking whether payment landed, finding the last email in the thread, writing something that does not sound annoyed, sending it, noting that you sent it.
Twenty late invoices a month at six minutes is two hours. That is the small number. The big number is the cash timing: most late invoices are late because nobody asked. Businesses that follow up consistently on day three instead of day thirty do not just save admin time, they get paid weeks earlier — which is the difference between comfortable and calling the bank.
The third number is the one owners mention most often once it is running: they stop carrying it around. Knowing that every unpaid invoice is being chased by something that does not forget is worth something that does not appear on a timesheet.
Where it connects
An invoice-chasing agent needs three things: the invoice data, a way to send email as you, and somewhere to report.
In practice that means your accounting or invoicing system as the source of truth, Gmail or Outlook to send from your real address so replies land in your normal thread, and Slack or email for the daily summary. If your CRM holds the client contact rather than your accounting tool, the agent reads both and matches them.
If your invoices live in a spreadsheet, that works too. Plenty of ten-person businesses run receivables from one sheet, and an agent can read a sheet perfectly well.
Before you turn it on
Get the data clean enough. The agent will be as accurate as your invoice records. If three invoices are marked unpaid but were settled by bank transfer last month, fix those first — one wrong chase costs you more trust than ten right ones earn.
Turn approvals on. Every outgoing email waits for your sign-off for the first fortnight. Read every draft. You will find two or three tone adjustments in the first week and almost none after that.
Test on real invoices. Take the ten oldest unpaid ones, including the awkward ones — the disputed job, the client you are quietly worried about, the one where you owe them a credit. Check that the agent's draft is one you would actually send.
Decide what it must never do. Never contact a client marked in dispute. Never mention a late fee that is not in the contract. Never send anything to more than one contact at that company without asking. Write those as hard rules, not preferences.
Release approvals slowly. After two weeks of watching, let the day-3 gentle reminders send themselves and keep approvals on everything firmer. Many owners never release the day-21 messages, and that is a sensible permanent setting, not an unfinished setup.
What an agent will not fix
It will not make a client who cannot pay, pay. If someone is in genuine trouble, the answer is a conversation, and an agent that keeps nudging makes it worse — which is exactly why the ladder stops at day 30 and hands the file to you.
It will not fix invoices that were wrong, vague, or sent to the wrong person. If a chunk of your late payments trace back to unclear scope or missing purchase order numbers, automate the reminder by all means, but fix the invoice template too.
And it will not replace the judgement about which relationships you are willing to press. That stays with you, permanently, by design.
Build it this afternoon
Describe the job in a sentence: chase the invoices more than three days past due, write each nudge in my voice with the invoice details, escalate on my ladder, stop at thirty days and tell me, and never touch anything in dispute. That is the whole brief.
Describe your invoice-chasing agent free — or try it in the preview on the home page first, with no signup and nothing saved.
Describe your first agent today
Free to start. No credit card, no setup calls, no engineering ticket.