How to automate chasing overdue invoices without annoying clients

August 3, 20267 min read

Chasing money you are owed is the task business owners put off longest, and the delay is expensive in a way that compounds: the later a chase goes out, the less likely it is to work.

Most of the chase is mechanical and can be handed over entirely. The part that has to stay human is smaller than it looks, and knowing where the line sits is what separates a system that gets you paid from one that costs you a client.

How bad is the late payment problem?

Worse this year than last, and the data is unusually good because two accounting platforms publish it from their own transaction records rather than from surveys of opinion.

Xero's US Small Business Insights puts the average wait for a small-business invoice at 28.8 days, with invoices paid 9.0 days late on average - up from 8.4 days. QuickBooks' 2026 late payments report finds that 59% of businesses have at least some invoices overdue by 30 days or more, against 47% a year earlier, and that those waiting are owed $17,700 on average.

Two things follow. The first is that being owed money for a month is now the normal condition of a small business rather than a sign that something went wrong. The second is that a month of silence is the default outcome if nobody does anything, which is exactly the situation automation is good at.

What part of chasing can actually be automated?

Most of it. The chase breaks into six jobs, and five of them are mechanical:

Noticing that an invoice is late. Pure bookkeeping, no judgement.
Deciding which reminder is due. A schedule, not a decision.
Writing the reminder. Templated, with the amounts and dates filled in.
Sending it at a sensible hour. Better than you at this, since it does not forget on busy days.
Stopping the moment payment lands or the client replies. The step that matters most, covered below.
Deciding what happens when polite reminders stop working. Yours. Always.

Everything except the last is a candidate. That is the honest scope: automation handles the routine chase and hands you the cases that have stopped being routine.

What does the reminder schedule look like?

A workable default, adjusted to your terms:

When	Tone	What it says
3 days before due	neutral, informational	invoice is coming due, here are the payment details
Day after due	assume an oversight	invoice is now due, link to pay
Day 7 overdue	direct, still friendly	payment outstanding, ask if there is a problem
Day 14 overdue	firm	reference the terms, state the next step
Day 30 overdue	stop the sequence	hand to you, with the history attached

The pre-due reminder is the one people skip and the one that does most of the work. A large share of late payments are not disputes or cash-flow problems - the invoice was simply missed. Arriving before the due date costs nothing in goodwill and removes that whole category.

The day-30 handover matters just as much. An automation that keeps sending polite notes forever teaches the client that nothing happens when they ignore you, which is the opposite of the intended lesson.

What breaks the relationship?

Four failure modes, all of them avoidable, all of them common enough to be worth naming.

Chasing money that has already arrived. The single most damaging failure. It tells the client you are not paying attention to your own books, and it makes every future reminder from you less credible. This is why step five in the list above matters: the automation must read payment status before it sends, and it must stop on receipt rather than on a schedule.

Chasing after the client has replied. Somebody writes "our finance team runs payments on the 15th" and then gets three more reminders. Any inbound message from the client has to pause the sequence and put a human in the loop.

Escalating tone on a good client. A client eight days late for the first time in four years should not receive the same message as one who is late every quarter. Payment history is available to the system, and using it costs nothing.

Sending as if it were personal when it is not. Reminders written in the voice of a real person work well - until the client replies with a question and gets silence. If it sends from your address, somebody must be watching that address.

Which invoices should be left out of the sequence?

Some cases should never enter automatic chasing at all:

Anything in dispute. The client has raised a problem with the work. Reminders make it worse.
Clients on an agreed payment plan. They are following the plan you agreed. Chasing them punishes cooperation.
Your two or three largest accounts. Not because they are exempt from paying, but because the cost of an awkward automated message is higher than the time you save. Chase these yourself.
Anyone you know to be in trouble. A business struggling to pay needs a conversation, not a sequence.

Exclusion lists are cheap to build and are usually the difference between a system you trust and one you switch off after a bad week. If you are unsure whether a process has too many exceptions to be worth automating, that is one of the tests in when not to automate a process.

What does this cost to run?

The chase itself is a small automation: it watches invoice status, sends templated messages on a schedule, and stops on payment or reply. On the platforms covered in what automation costs a small business, running costs land in the tens of dollars a month rather than the hundreds, because the volume is low - a handful of events per invoice, not thousands.

The build cost depends on your accounting tool. Most have a proper API, in which case this is straightforward work. If your invoicing lives in a spreadsheet, the automation is not the first problem to solve.

Worth checking before commissioning anything: your accounting software may already do a basic version. Xero, QuickBooks and FreeAgent all ship some form of automatic reminder. If simple scheduled reminders are all you need, use theirs and spend the money elsewhere. Custom work earns its keep when you need the exclusion rules, the payment-history awareness and the reply detection described above.

The arithmetic

Count the hours. If chasing invoices takes forty-five minutes on a working day, that is roughly fifteen hours a month.

Then count the second effect, which is usually larger: reminders that go out on time rather than when you remember shorten the wait. On an average outstanding balance near $17,700, moving payment forward by a week is a meaningful improvement in working capital, and it repeats every month.

Both numbers are yours to fill in rather than ours to promise. What we can say is that this particular process is unusually well suited to automation: high frequency, clear rules, low judgement, and a well-defined point at which it should stop and call you.

If you want that arithmetic done against your actual invoice history rather than an example, that is what the process audit produces - a written map, $299, three business days, credited towards the project.