The short answer
Connect your accounting software to a workflow tool that checks for overdue invoices every day. It sends a polite reminder on a fixed schedule and stops the moment an invoice is marked paid. Anything awkward goes to you personally, so the routine work runs on its own and the conversations that need judgement stay with a person.
This guide covers the schedule that works for most small firms, what the automation has to do, the rules that stop it annoying good customers, the UK rules worth knowing and when it makes sense to get help building it.
Why chasing slips in the first place
Most owners do not forget that an invoice is overdue. They put the reminder off because it feels like an accusation or because a busy week gets in the way. Sometimes the customer is a friendly regular and the message feels awkward. A few days of delay turns into a few weeks, and the longer the gap the harder the message is to write.
There is also a practical problem. Chasing needs somebody to open the accounts, filter the overdue list, find the right contact, write something suitable and remember to follow up. That is a small task, but it repeats every week and it depends on one person having time. A scheduled workflow removes the dependence on memory and mood and makes every customer get the same treatment.
A reminder schedule that works
The exact days depend on your payment terms, so treat this as a starting point. The idea is to begin gently, add firmness slowly and bring a person in before the relationship is damaged.
| When | What goes out | Who sends it |
|---|---|---|
| 3 days before the due date | A short heads-up with the invoice attached | Automation |
| 1 day after the due date | A friendly note asking if anything is blocking payment | Automation |
| 7 days after | A clear reminder with the amount, the invoice number and a payment link | Automation |
| 14 days after | A firmer message that mentions your terms and any late payment charges | Automation, copied to you |
| 21 days after | A task for you to phone or write personally | You |
What the automation needs to do
A useful chasing workflow is more than a timer that sends emails. These are the parts that make the difference between helpful and irritating.
- Read live invoice data. It should pull open invoices from your accounting package every day, because most packages offer a way for other tools to connect.
- Check the status before every message. If the invoice was paid this morning, nothing should go out. This one check prevents most embarrassing reminders.
- Use the right contact. The reminder should go to the person who pays invoices, which is often different from the person you deal with day to day.
- Fill in the details. Amount, invoice number, due date, a copy of the invoice and a payment link should all appear in the message.
- Keep a record. Every reminder should be logged against the invoice so you can see what was sent and when.
- Pause on request. A customer who says they will pay on Friday should be able to be put on hold with one click, not chased again on Wednesday.
Rules that keep it polite
Automation makes it easy to send too much, so decide the limits first. Send from a real address that a person reads, so replies do not vanish. Write in your normal voice and keep each message short. Avoid threatening wording in anything that goes out without a human reading it.
Exclude the customers who need a personal touch. A disputed invoice or a customer going through a bad month should sit on a hold list that the workflow respects. It is also sensible to cap the number of reminders per invoice, so that nothing can loop indefinitely if a status is wrong.
Where an AI model is involved, use it for drafting or for reading replies, such as spotting that a customer has written to say the invoice is disputed. Let a person approve anything that goes beyond the standard wording. A plain template is usually safer than a freely generated message for a money conversation.
UK points worth knowing
In the UK, the Late Payment of Commercial Debts (Interest) Act 1998 can let a business charge statutory interest on overdue invoices from another business, plus a fixed sum that depends on the size of the debt. The details and the current rates are on gov.uk, and your contract terms matter too. This is general information and not legal advice, so check your own position before you rely on it.
Reminders to a business contact are usually treated as ordinary account management, but they still involve personal data such as names and email addresses. Keep the data you hold to what you need, store it with a provider that gives you a data processing agreement, and mention reminders in your privacy notice. Reminders to sole traders and individuals deserve extra care with tone and records. If a dispute or a serious debt is involved, a solicitor or a credit control specialist is the right next step, not a longer email sequence.
Build it yourself or get help
Many accounting packages have a built-in reminder feature, and it is worth trying first. If it covers your needs, stop there. Built-in reminders tend to fall short when you want different schedules for different customers, a hold list, a task for you at day 21, a message in your own wording or a link to your CRM and calendar. That is the point where a workflow tool earns its place.
RAWR Productions builds this kind of workflow on n8n, which we run on our own server in the EU, and adds an AI step only where a message needs judgement. A first workflow is typically live within one to two weeks. We quote a fixed price in writing after a free 20-minute intro call, and we run our own studio on the same stack.
Questions
Is it rude to send automated payment reminders?
Not if they are short, accurate and sent from a real address. Most customers see a reminder as a normal part of doing business. What causes offence is a reminder for an invoice already paid or a harsh tone, which is why the paid check and a friendly first message matter so much.
Can I use my accounting software's reminders instead?
Yes, and it is often the right first step. Built-in reminders usually apply one schedule to everyone. A separate workflow helps when you need different rules per customer, a hold list, escalation to a phone call or a link to your other tools. Start simple and only add more when you hit those limits.
Where should the automation stop and a person take over?
Hand over when a customer replies with a dispute, when an invoice reaches about three weeks overdue, or when the amount is large enough to matter. The workflow should create a clear task for you, with the history attached, so you can phone or write personally rather than send another standard email.
Do I need customer consent to send payment reminders?
Reminders about an existing invoice are generally treated as account administration rather than marketing, so they are handled differently from promotional emails. You still need to handle personal data properly and say so in your privacy notice. This is general information and not legal advice, so check with your adviser if you are unsure.
How long does it take to set up invoice chasing?
A simple version connected to an accounting package can usually be built in one to two weeks, including testing on real invoices before anything goes to customers. More complex setups with several schedules, a hold list and a CRM link take longer. The first week is mostly agreeing the rules and wording.