How to automate invoice chasing without annoying your customers

Most unpaid invoices in a small business are not disputed and not refused. They are simply sitting in somebody's approvals pile at the other end, and nobody at your end has had a spare hour to ask about them.

That is why automating this works so well. You are not building a debt collection operation. You are making sure the polite reminder actually goes out on the day it should.

The sequence that works

Before it is due. A short note a few days ahead, confirming the invoice arrived and the amount is as expected. This is the single highest-value message in the sequence and almost nobody sends it. It catches the invoice that went to the wrong address, the purchase order that was never raised, and the amount somebody was going to query at the last minute.

The day after it is due. Short, friendly, factual. Invoice number, amount, date, a copy attached. No tone at all. Most payments land here.

A week later. Same again, slightly firmer, and this time ask a question rather than making a statement: is there anything holding this up. A question gets a reply; a statement gets ignored.

Three weeks. A person picks up the phone. This is where automation should stop.

What to automate and what not to

Automate the watching, the timing, the drafting and the record. Those are the parts that fail because they are boring.

Keep in a person's hands: anything after the third reminder, anything where the customer has replied with a problem, and anything involving a customer you know is struggling. An agent that keeps sending cheerful reminders to somebody who has just told you they are in trouble does real damage, and it is exactly the failure that makes people distrust the whole idea.

The rule we use: the moment a human replies, the sequence stops and a person takes over. That single rule prevents most of the harm.

The mistakes that cost you relationships

Chasing something already paid. This is the one that genuinely angers people, and it is almost always a data problem rather than a chasing problem — the payment arrived but had not been matched when the reminder went out. Any agent doing this work must check the payment status at the moment of sending, not when the sequence was scheduled.

Chasing the wrong person. Accounts payable is rarely the person who bought from you. Sending increasingly firm notes to your day-to-day contact about something they cannot control is a good way to lose them.

Sending at the wrong time. Friday afternoon and the week between Christmas and New Year are wasted sends. So is anything before nine in the morning, which reads as automated even when it is not.

Getting the amount wrong. Credit notes, part payments and agreed discounts all need to be reflected. Chasing the full amount when half was paid last week undoes any goodwill the first three reminders built.

What this actually looks like running

An agent connected to your accounting system — Xero, QuickBooks, Sage and the rest are all standard connections — watches what is outstanding, works out what stage each invoice is at, drafts the right message for each one, and either sends it or puts it in front of you to approve.

The version most people start with has the agent drafting and a person pressing send. After a month of the drafts being right, most people let it send the first two stages itself and keep the third.

Is it worth it

Work out how many invoices you have outstanding beyond terms right now, and what your average is worth. Then be honest about how many reminders actually went out last month.

For most businesses the gap between the terms you set and the day you actually get paid is not a policy problem. It is the reminders that never went. Tell us what your ledger looks like and we will tell you whether this is your bottleneck or whether something else is.