How to chase unpaid invoices without hiring a credit controller

Every growing trade business has a version of the same scene: it's Friday afternoon, someone in the office has a list of overdue accounts, and they're working through it by phone and email. Except — the phone keeps ringing with orders, a delivery query interrupts, and by 4pm the list is half done. The half that didn't get chased pays late again next month.

Nobody chases because chasing is nobody's whole job, it's awkward, and it's endlessly interruptible. And so the most valuable admin task in the business — collecting money you've already earned — is the one that most reliably slips.

What late payment actually costs you

Not just the cash-flow squeeze, though that's real enough — money sitting in your customers' accounts is money you're effectively lending them, interest-free, while paying your own suppliers on time.

The quieter costs:

• The compounding effect of inconsistency. Customers learn, fast, who chases and who doesn't. If your invoices can be paid late without consequence, they will be — not out of malice, but because their office also has a list, and the squeaky suppliers get paid first.
• The awkwardness tax. When chasing is sporadic, every chase feels like a confrontation, because it's been 45 days and now the amount is big and the conversation is tense. Regular, early, polite chasing is less awkward, not more.
• The write-offs you never call write-offs. The £400 invoice from eight months ago that everyone's quietly given up on. A few of those a year is a holiday. Several a month is a salary.

The anatomy of chasing that works

Whether a person or a system does it, effective credit control is the same recipe. It is boring, and that is the point — it works because it never has a bad week.

1. Before due date, not after. A friendly note a few days before payment is due ("just flagging this is due Friday — any issues, let me know") isn't chasing at all. It's the single highest-value message in the sequence, because it surfaces disputes and "we never got the invoice" problems while there's still time.
2. Day one, not day fifteen. The first overdue reminder goes the day after the due date. Polite, short, assumes good faith. The gap between "due" and "first chase" is the strongest signal you send about whether your terms mean anything.
3. A ladder, written down. Day 1 polite · day 7 firmer with a copy of the invoice · day 14 phone call · day 21 statement of account and a named person · day 30 stop supply / escalate. Your ladder can differ — the power is that it's written down and always happens.
4. Different rules for different customers. Your five biggest accounts probably deserve a relationship call, not an email sequence. The long tail of smaller accounts is where systematic chasing earns its keep.
5. Stop the machine the moment a human replies. Nothing destroys trust like a "FINAL REMINDER" landing after the customer already emailed about a dispute. Any decent process — human or automated — halts the sequence on a reply and routes it to a person.

"But my accounting software already does reminders"

It does — Xero, Sage and QuickBooks all have invoice reminder features, and if you've never turned them on, do that this week. It's free and better than nothing.

Here's why they usually underperform: they send the same template to everyone, on the same schedule, regardless of the customer's history or size. They don't know that this account always pays on the statement, that one disputes everything, and that one is your biggest customer and needs handling gently. So the emails smell automated — and automated-smelling emails are exactly as easy to ignore as no email at all. After a few months someone turns them off because "they annoy customers," and the office goes back to the Friday list.

The difference between a reminder feature and a credit-control system is judgment: knowing who to chase, how firmly, in what voice, and when to hand it to a human.

What good automation looks like now

Modern AI systems close most of that judgment gap. A well-built one:

• drafts each chase in your voice, referencing the actual invoices and history, so it reads like your office wrote it — because the awkward truth is that customers pay people, not systems;
• follows your ladder and your per-customer rules — gentle with the big accounts, persistent with the tail;
• tells the difference between "forgot" and "dispute," and escalates disputes to a person immediately instead of sending reminder #3;
• gives you a Monday-morning list of the accounts that genuinely need a human phone call — so the human hour goes where the machine can't.

The person doesn't vanish; the person gets promoted from doing the chasing to deciding the exceptions. One hour a week of decisions instead of every Friday afternoon of awkward calls.

When you shouldn't automate this

If you have a dozen customers and they're all sizeable, the answer isn't a system — it's the owner making a dozen relationship calls a month. Automation earns its keep when the number of accounts is the problem: fifty, a hundred, three hundred accounts on credit terms, where consistent chasing is physically impossible for a busy office.

And if your invoices are frequently wrong — pricing errors, missing PODs — fix that first. Chasing a disputed invoice faster just makes the dispute arrive faster.

Start here, this month

Write your ladder down — the five steps, the days, who takes over when. That single page is worth more than any software, because now "chasing" is a defined process instead of a dreaded task. Turn on your accounting package's reminders as a stopgap.

Then look at the arithmetic: your average overdue book, the hours spent on the Friday list, and the accounts that never get chased at all. If those numbers are big enough to annoy you, that's the point where a purpose-built system pays for itself — and it's exactly the kind of thing we look for on a walk-through.