Chasing overdue invoices without chasing customers away
Late follow-up is what damages the relationship, not early follow-up. What good chasing looks like at each stage, which parts are safe to automate, and the exact point where a system has to stop and a person take over.
Chasing money is the job every small business is worst at, and it is not because people are disorganised. It is because it is socially uncomfortable. You know the customer. You will see them again. The invoice is only two weeks over and bringing it up feels like an accusation, so it waits, and then it is six weeks over and the conversation is harder than it would have been.
The irony is that late follow-up is what damages the relationship. A polite note at seven days is administrative. The same note at ninety days is a confrontation, because by then real money is involved and somebody has to explain themselves.
Why this is the wrong job for a person
Not because people do it badly. Because the parts that matter are the parts people are worst at: doing it on time, every time, in the same tone, without letting how they feel about the customer change the schedule.
Consistency is the whole thing. A business that follows up every account at seven days is a business with a policy. A business that follows up the customers it feels comfortable chasing has a bias, and the customers who get chased least are usually the ones who owe most, because they are the ones the relationship feels most valuable with.
The accounts that go unchased longest are rarely the smallest. They are the ones somebody did not want to ring.
What good follow-up actually looks like
It changes as the account ages, and the change is mostly in tone rather than content. Early on, assume it was missed, because usually it was: the invoice went to the wrong address, or the person who approves it was away. Later, be direct about what happens next. Throughout, make paying easy, which means the invoice attached, the reference included and the amount stated, not a link back to a portal nobody can log into.
| Stage | What it should say | What it should never do |
|---|---|---|
| Just overdue | Assume it was missed, attach the invoice, make paying easy | Imply bad faith over an administrative slip |
| A few weeks | Be specific about the amount and how long, ask whether something is holding it up | Send the identical message again, which signals nobody is reading |
| Over a month | State plainly what happens next and when | Threaten something you have not decided to actually do |
| Beyond that | Nothing automatic. A person picks this up | Let a system send anything near a legal position |
Where automation fits, and where it has to stop
The schedule, the tone for each stage, the attachment and the reference are all known in advance, which makes the early stages a good fit for an agent or even a plain automation. The system can read the accounting data, work out which accounts are at which stage, and send the right message with the right document.
What it must not do is make a judgement about a customer. An account approaching a stop-credit, a payment plan, a dispute about the work, or anything that could become a legal position goes to a person before a word is sent. That is not caution for its own sake: an automated message at the wrong moment can turn a slow payer into a dispute, and the cost of that is far higher than the admin it saved.
The same applies to the customer who replies. The moment somebody writes back explaining why they have not paid, the automation is finished and a person picks it up. A system that keeps sending scheduled reminders to a customer who has already responded is the single fastest way to make this worse.
What changes when it is consistent
We will not put a number on what this recovers, because it depends entirely on your customers and your terms. What we can say plainly is what changes in the business: the follow-up happens whether or not anyone had a good week, it happens early enough to be administrative rather than confrontational, and the awkward conversations that remain are the ones that genuinely need a human, which is a much shorter list than the one most owners are carrying.
You also find out something uncomfortable and useful: which customers only ever pay when chased. That is a commercial decision rather than an admin one, and it is very hard to see when the chasing is inconsistent.
Before you automate any of it
Check the obvious first. A surprising amount of late payment is caused by invoices going to a person who left, terms nobody agreed to in writing, or an invoice that does not carry the purchase order number the customer's system requires. None of that is fixed by chasing harder, and all of it is cheaper to fix than to chase.
The short version
Follow up early, consistently, in a tone that changes as the account ages, and make paying easy. Automate the part that is a schedule. Stop automatically the moment judgement is needed or the customer replies. And fix the invoices that were never going to be paid on time before blaming the customers.
Chasing it by hand at the moment?
Tell us how your invoicing and follow-up works today and we will tell you which parts are worth automating, which are not, and what it would take.
The quote that lives in one person's head
One person can price a job by looking at it. That works until they are on leave, or somebody else has a go and the number is twenty per cent different. Why writing the rules down is worth more than the automation, and exactly what stays with the estimator.
Innovation and resisting change
Every business has someone pushing to modernise and someone saying they tried that once. Both are usually partly right. Why resisting change is information rather than obstruction, why changing for its own sake costs just as much, and the one question that settles most of the argument.