Short answer
Automate invoicing and reminders in this order: make the invoice correct and easy to pay, send a short pre-due confirmation, then a small number of specific, human-sounding reminders after the due date. Wire the stop conditions first — payment received, invoice disputed, client replied — because a reminder that fires after payment or during a dispute costs more than the late payment did. Escalation past the second reminder should be a person's decision, not a scheduled email.
Why invoices are actually paid late
Before automating anything, it is worth being honest about the causes, because they are not what the collections language implies. In small and mid-sized companies, late payment usually comes down to four things.
- The invoice reached the wrong person. It went to the contact you deal with, who does not approve payments, and it is sitting in their inbox.
- Something on it is wrong. A missing purchase order number, the wrong entity, a line the client does not recognize. It gets parked rather than queried.
- It arrived outside their payment run. Many companies pay in batches. Missing the cutoff by a day costs you a full cycle.
- Nobody followed up. The invoice was correct, went to the right person, and was simply forgotten by both sides.
Only the last of these is solved by reminders. The first three are solved upstream, and automating reminders without fixing them means politely chasing a problem you created.
Fix the invoice before you automate the chase
The highest-return work here happens before the invoice is sent, and it is unglamorous.
Ask each client, once, who should receive invoices and what reference they need on them. Store it against the client record rather than in someone's memory. Send the invoice to that person, with that reference, in the format they asked for. Make paying it a single click rather than a bank transfer assembled by hand.
A well-addressed, correct, easy-to-pay invoice removes most of the need for the sequence you are about to build. Automating reminders on top of a broken invoicing process makes the problem more frequent and more annoying, not smaller.
A reminder sequence that does not burn goodwill
Four touches is usually enough, and the tone matters more than the timing.
- A few days before the due date — a short confirmation: the amount, the date, the reference, and an offer to resend if anything is missing. This one catches the wrong-recipient and wrong-details cases while they are still cheap.
- The day after the due date — brief, factual, and written as though it were an oversight, because it usually is. Attach the invoice again rather than referring to it.
- Around a week later — same tone, plus a direct question: is there anything blocking this on your side? That question converts a silent non-payment into a conversation, which is the actual goal.
- Around two to three weeks — this one is not automated. It is a person picking up the phone.
Every message should name the specific invoice and amount, come from a real person's address, and be short enough to read on a phone. The generic templates that ship with accounting software fail all three tests, which is why so many people conclude that reminders do not work.
The stop conditions, which matter more than the sends
This is the part that separates a system that helps from one that costs you a client. Before writing a single reminder, decide what stops the sequence.
- Payment received. Obvious, and still the most common failure — usually because the check runs against data that is a day stale. Verify against the live payment status, not a nightly export.
- Invoice disputed or queried. If the client has raised anything, the sequence must halt immediately. Chasing a disputed invoice is the single fastest way to turn an administrative issue into a relationship one.
- Any human reply. Once a person has written back, a person should read it before anything further is sent.
- Credit note or partial payment. Partial payments break naive logic badly: the invoice is not settled, so the sequence continues, and the client who just paid most of it receives a chasing email.
Write these down as rules before you build anything. They are the requirements; the emails are the easy part.
What to build, in what order
A sequence that avoids the usual rework.
- Turn on whatever your accounting package already does, and rewrite its default text in your own voice. For many companies this alone recovers most of the benefit within a week.
- Add the pre-due confirmation. It is the highest-value message and the one almost nobody sends.
- Only then reach for a workflow tool, and only for the logic accounting cannot express — checking a project system for disputes, alerting the account manager, or applying different sequences by client tier.
- Add an alert when the automation itself fails. A reminder system that silently stopped three weeks ago is worse than none, because everyone assumes it is running.
The general principles here — start narrow, wire the failure path before going live, keep a human at the ends — apply to every process of this shape, and are covered in automation without developers.
The leverage you have depends on where you are
One thing worth knowing before you write the third reminder: your legal position differs sharply between the United Kingdom and the United States, and it changes what you can credibly say.
In the UK, businesses have a statutory right to charge interest on late commercial payments. The government's guidance sets the rate for business-to-business transactions at 8 percent plus the Bank of England base rate, alongside a fixed sum for recovery costs — and it applies whether or not your contract mentions it, unless the contract sets a different rate. Most companies never invoke it. Its value is not the money; it is that a late payment has a defined consequence you can reference calmly and factually.
In the United States there is no federal equivalent for ordinary commercial invoices. Interest on late payment is a matter of what your contract says, plus state law that varies. The practical implication is that your leverage is contractual rather than statutory, and it has to be established when the engagement is signed rather than when the invoice ages.
If you sell into both markets, this belongs in your terms rather than in your reminder templates. An automated message that threatens a statutory remedy that does not exist in the client's jurisdiction is worse than saying nothing.
Measuring whether the whole thing worked — days sales outstanding before and after, not messages sent — follows the same discipline as any other automation, covered in measuring automation ROI honestly.
Where a human has to take over
Past the second reminder, automation stops helping. A client who has ignored two specific, polite messages either has a problem with the invoice, a problem with your work, or a problem with their own cash position. All three need a conversation, and none of them improves with a third email.
The useful thing automation can do at that point is prepare the conversation: put the invoice, its age, the full message history and the account manager's name in front of the person who will make the call. That is a genuinely good use of a workflow, and it is a different job from sending another reminder.
A practical rule: automate everything up to the point where judgment is required, then hand over with full context. The handover is the feature, not the failure.
Frequently asked questions
Will automated reminders damage client relationships?
Badly written ones will, and so will the alternative. The reminders that cause friction are the ones that sound like a collections agency wrote them, arrive without checking whether the invoice was disputed, or keep firing after the client has already paid. Reminders that reference the specific invoice, come from a named person, and stop the moment payment lands read as administration rather than pressure. Most clients who pay late are disorganized, not unwilling — and a clear, early, polite reminder helps them.
When should the first reminder go out?
Before the due date, not after. A short note a few days ahead — confirming the amount, the due date and that everything is in order — catches the two most common causes of late payment: the invoice never reached the person who approves it, and something on it was wrong. Both are cheap to fix at that point and expensive to discover three weeks later.
What should stop the sequence?
Payment, a dispute, and any human reply. The first is obvious and still gets missed when the payment check runs on a stale copy of the data. The second is essential: chasing an invoice the client has already queried destroys trust faster than the late payment costs you. The third is a judgment call worth making — once a person has replied, a human should read it before anything else goes out automatically.
Can we charge interest on a late invoice?
It depends entirely on where your client is. In the United Kingdom there is a statutory right to interest on late commercial payments — the government sets it at 8 percent plus the Bank of England base rate for business-to-business transactions, plus a fixed recovery sum, and it applies unless your contract specifies a different rate. In the United States there is no federal equivalent for ordinary commercial invoices: interest depends on what your contract says and on state law. If you sell into both, put the term in the contract rather than relying on statute, and never let an automated reminder threaten a remedy that does not exist in the client's jurisdiction.
Do we need dedicated software for this?
Usually not at first. Most accounting packages already send scheduled reminders, and the fastest improvement for many companies is switching that feature on and rewriting the default text, which tends to be cold. A workflow tool becomes worthwhile when the logic has to reach outside accounting — checking a project system for a dispute, alerting an account manager before escalation, or applying different sequences to different client tiers.
If your reminder process currently lives in someone's calendar and their memory, we build the version that does not. Book a call and we will map it with you.
