How accounting firms can automate overdue invoice reminders
By the PauSolutions teamPublished 9 min read
The short answer
Overdue invoices get followed up when one invoice list decides who is reminded, and a small automation sends three polite emails from your own mailbox — a friendly one at 3 days overdue, a firmer one at 10 and a final one at 20 — then stops the moment the invoice is marked paid.
- Keep one list: invoice number, client, email, amount, due date, whether it is paid, and which reminder was last sent.
- Send each stage once: friendly at 3 days overdue, firmer at 10, final at 20. Skip anything paid or not yet due.
- A payment stops the sequence on the next run. After the final email, stop writing and flag the invoice for a phone call.
- The office gets a short overview of what is paid, not yet due and overdue, instead of rebuilding the unpaid list from memory.
- The same routine fits other small service offices. You can build it with n8n, Make or Zapier on a spreadsheet or an export from the software you already use.
Why overdue invoices wait longer than they should
Chasing a fee is awkward, so it slips. Someone means to "check the unpaid list on Friday", then a deadline lands and the list waits another week. Clients who would have paid after a polite nudge stay open. The ones who need a conversation never get the call, because nobody is sure who was already emailed.
The other cost is uneven treatment. One client gets a gentle note because they know a partner; another gets nothing, or three emails in a single week. A fixed rhythm is easier to explain and harder to forget.
What an automated payment reminder actually does
It is not a collections process and it does not need AI. It is a short set of rules that runs every working morning:
- Reads your invoice list — a Google Sheet, an Excel file, or an export from the invoicing or practice software you already use. Each row has the invoice number, client, email, amount, due date, whether it is paid, and which reminder stage was already sent.
- Skips paid invoices and invoices that are not yet due.
- Sends the next stage only if it has not gone out yet: a friendly reminder at 3 days overdue, a firmer one at 10, a final one at 20.
- Sends that email from your own mailbox (Google Workspace or Microsoft 365), naming the invoice, the amount and the original due date, and inviting a reply if something is wrong.
- Records the stage it sent. On the final stage it flags the invoice for someone in the office to call, and the office gets a short overview of what is paid, not yet due and overdue.
You can move the dates forward and mark fictional invoices as paid in our interactive payment reminder demo — nothing is sent, and no sign-up is needed. Chasing clients for missing paperwork is a different job: that setup is in the guide on document requests.
How to set it up, step by step
1. Decide which invoices belong on the list
Start with the fees your own office has already issued — one row per open invoice. Leave client bookkeeping documents off this list. If a client still owes you a bank statement, that belongs in the document chase, not in a payment reminder.
2. Keep one list, with a paid column someone actually uses
Columns that are enough: client, email, invoice number, amount, due date, paid, reminder stage sent (0, 1, 2 or 3) and date of the last reminder. Whoever records a payment marks the row paid the same day. That tick is what stops the next email. If your software can export unpaid invoices, refresh the list from that export instead of retyping it.
3. Write three short templates, with a tone that steps up
- Friendly (3 days overdue) — assumes it slipped. Names the invoice, the amount and the due date. Says that if they have already paid, they can ignore the note. Offers to resend the invoice.
- Firmer (10 days) — still unpaid. Asks for a date you can expect payment, and invites a reply if the amount or the invoice is wrong.
- Final (20 days) — says this is the last email, asks them to arrange payment by a clear date, and says someone from the office will call if there is no reply.
4. Fix the rhythm and the stop rules
| When | What happens | Stops if |
|---|---|---|
| 3 days overdue | Friendly reminder naming the invoice, amount and due date | Marked paid |
| 10 days overdue | Firmer reminder asking for a payment date | Marked paid |
| 20 days overdue | Final reminder, and the invoice is flagged for a phone call | Marked paid |
| After the final email | No further automatic emails | — |
Send on working mornings only, and send each stage once. The gaps above are a solid default — the same one in the demo — and you can widen or tighten them when you set the workflow up. If a client replies with a payment date or says the invoice is wrong, take that row off the automatic list and handle it by hand. Another automated email on top of a conversation makes the office look as if it is not listening.
5. Test on a few invoices, then go live
Run it first to internal addresses, with fictional invoices. Check that a paid row sends nothing, that an invoice 3 days overdue gets only the friendly note, and that the final stage shows up on the call list. Then turn it on for real invoices and read the overview, instead of rebuilding the unpaid list from the inbox.
Common mistakes to avoid
- Reminding someone who has already paid. If "paid" is updated late, the automation emails the wrong clients. Mark payments the day you see them, or refresh from an export.
- Sending from a no-reply address. Clients answer with receipts and questions. Use the mailbox they already know, so the reply lands in the office.
- Emailing past the third note. After the final reminder, more email rarely helps. A short call does. The last stage should flag a person, not schedule a fourth template.
- A vague message. "Your account is overdue" is easy to ignore. Invoice number, amount and due date get a reply.
- Putting formal wording in the automatic emails. Keep the three notes polite and specific. A formal letter, if the firm later decides one is needed, is written by a person. This guide does not cover interest, formal notices or legal deadlines.
- Chasing on several channels the same day. An email plus a text plus a chat message feels like pressure. Use email for the automatic sequence; a person calls when the invoice is flagged.
Which tools to use
You have two broad options. Invoicing or practice software that already sends reminders can do the job if you are happy with its wording, its timing and the address it sends from. An automation on your own tools — n8n, Make or Zapier, connected to a spreadsheet or an export and to Gmail or Outlook — keeps the emails in the mailbox clients already reply to, with the rhythm you choose. The second option is what we build, as a one-off setup in your own accounts.
The same routine fits other small service offices — consultants, agencies, studios — wherever overdue invoices are still chased by hand. It needs a list you can maintain or export. It is a poor fit if unpaid invoices live only in someone's head.
Check the data basics either way: the emails leave from your account, the list holds only what the reminder needs, and anyone who builds or maintains the automation for you should sign a data processing agreement (art. 28 GDPR). For an accounting firm, the invoice list stays in your accounts. Our data & privacy page explains how we handle this.
Is it worth automating?
As a rule of thumb, if the office sends more than about 20 payment reminders a month, an automation usually pays for itself within a few months — mostly because the awkward ones stop being postponed. Below that, a shared unpaid list and a weekly calendar reminder may be enough. Put your own figures into the Chasing Cost Check before you decide. Prices for the setup are on the Document & Payment Chaser page: Payment Chaser €290, Document Chaser €290 (introductory price; regular price €390), both together €590.
Frequently asked questions
Will clients know the reminders are automated?
They come from your own mailbox, with your firm's wording, and they name that client's invoice, amount and due date, so they read like a normal email from the office. Replies arrive in your inbox as usual.
What if the client pays after the first reminder?
Once the invoice is marked paid — by hand, or because the list was refreshed from your invoicing export — the next run sends nothing further for that invoice.
How does the automation know an invoice has been paid?
Someone in the office marks it paid on the list, or the list is replaced by a fresh export of unpaid invoices. The automation does not guess from a bank feed unless you have connected one.
How many reminders should we send?
Three, each once: a friendly reminder at 3 days overdue, a firmer one at 10 and a final one at 20. After that the invoice is flagged for a phone call. You can change the gaps, but more than three automatic emails rarely helps.
Is this a formal demand for payment?
No. The three emails are polite operational reminders. Whether to send a formal notice later, and what it should say, is a separate decision for the firm. This guide does not give legal advice on wording, interest or deadlines.
Is it GDPR-compliant?
It can be, and it should be designed that way: emails are sent from your own account, the list holds only the data the reminder needs, and the provider who builds it signs a data processing agreement and works with least-privilege access.
