Payment Reminder Email Templates for Every Stage of the Chase

You have written this email a dozen times and it never gets easier. An invoice is overdue, you open a blank message, and you sit there rewriting the same sentence because every version sounds either too soft to work or too sharp to send to someone you actually like doing business with.

The wording is not really the problem. A good payment reminder email is short and plain, and most people can write one just fine. What decides whether you get paid is whether that email goes out on a schedule, in a tone that fits how late the invoice is, and whether it is the only reminder that customer needed.

This is a sequence, not a single message. Five templates below, one for each stage from a friendly heads-up before the due date to a firm final notice, plus the reasoning for why the tone changes at each step. Copy them, fill in your own specifics, and use them in order.

Why the wording matters less than the sequence

Most people treat a late invoice as a writing problem. They search for the perfect phrase that gets a customer to pay without sounding pushy, as if the right sentence exists and they just haven't found it yet. It doesn't. Customers who intend to pay respond to a clear ask, and customers who don't intend to pay respond to none of the wording either way.

What actually moves the needle is consistency: the reminder goes out the day it's due, not whenever someone remembers to check the aging report. A single well-written email sent three weeks late does less than a plain one sent on time. The schedule is doing the work the wording gets credit for.

That's also why one invoice reminder template for every stage falls flat. The email that should feel like a courtesy on day one reads as a shrug by day 30, and the one firm enough for day 30 feels aggressive sent to someone whose invoice is two days old. The fix is a short sequence, not a better sentence.

The five-stage payment reminder email sequence

Five stages cover almost every business, from a two-person shop to a mid-market AR team. Each one has a job: catch oversight early, assume good faith once, then get progressively more direct about what happens next. Here is the shape, before the actual templates.

Five is not an arbitrary number. Fewer stages and you skip straight from friendly to firm, which reads as an overreaction the first time you send it. More stages and the later ones stop meaning anything, because a customer who ignored four reminders isn't moved by a fifth that sounds the same.

Templates you can copy, stage by stage

Each template below is deliberately short. Fill in the brackets, adjust the specifics to your own business, and send as-is. The lead-in above each one explains what changed from the last stage and why, so you can keep adjusting the tone correctly as you write your own versions.

Pre-due nudge, sent 2-3 days before the due date

This one isn't a chase at all, it's a heads-up. No urgency, no ask beyond confirming the invoice is on someone's radar. Its whole job is catching the invoices that would otherwise go overdue purely because nobody flagged them, which is more common than most owners assume.

Subject: Invoice #[number], due [date]. Hi [name], just a heads-up that invoice #[number] for $[amount] is due on [date]. No action needed if it's already scheduled to pay. Let me know if you need anything from us to process it. Thanks, [your name]

Day 1, the friendly assumption

The invoice is now overdue, but the email still assumes it slipped through rather than being ignored. Naming a specific reason it might have been missed, and giving the customer an easy out, gets a faster response than anything that opens by pointing out they're late.

Subject: Invoice #[number] is now overdue. Hi [name], I think invoice #[number] for $[amount], due [date], might have slipped past. If it's already paid, thank you, please ignore this. If not, here's the link to pay: [link]. Happy to help with anything on our end. [your name]

Day 14, ask for a date

Two weeks is long enough that oversight stops being the likely explanation. The email shifts from assuming good faith to asking directly for a commitment. It also opens the door for the customer to flag a real problem with the invoice, which is worth surfacing now rather than at day 30.

Subject: Following up, invoice #[number], 14 days overdue. Hi [name], checking in on invoice #[number] for $[amount], now two weeks past its due date of [date]. Could you let me know when we can expect payment? If there's an issue with the invoice itself, tell me and I'll get it sorted. [your name]

Day 30, firm and specific

A month overdue earns a firmer message, but firm isn't the same as hostile. State the consequence once, plainly, only if it's actually in your terms. A late fee you never mentioned before or don't actually charge reads as an empty threat, and empty threats cost you credibility on the next invoice.

Subject: Invoice #[number], 30 days overdue, action needed. Hi [name], invoice #[number] for $[amount] is now a month past due. Per our terms, a late fee applies from [date], and we'll need to pause further work until this is settled. Please confirm a payment date by [date], or call me at [phone]. [your name]

Final notice, the last step before escalation

This is the last email you send before handing the invoice to whatever process comes next, a collections agency, legal counsel, or simply no further credit. Say plainly what happens and by when, so the deadline is real. Vague final notices get read as one more reminder, not a last one.

Subject: Final notice, invoice #[number]. Hi [name], this is our final reminder before invoice #[number] for $[amount], now [X] days overdue, moves to our collections process. We would rather resolve this directly. Please contact me by [date] to arrange payment or a payment plan. [your name]

What closing the gap is worth in cash

The sequence isn't just neater, it's worth a real number. Take a business invoicing $60,000 a month on 30-day terms, currently averaging 54 days to get paid. That's a 24-day gap between when the terms say money should land and when it actually does.

Fourteen days closed on this book is $28,000 landing in the account roughly two weeks sooner, every month, with no extra selling involved. The 54 and 40-day figures are illustrations of a typical improvement, not a promised outcome. Run the same math with your own monthly sales and current DSO.

Why one template for everyone makes chasing feel rude

The complaint you hear most about automated reminders isn't that they exist, it's that they're tone-deaf. The same email lands in a best customer's inbox and a serial late payer's inbox on the same fixed schedule, sometimes after the invoice is already paid. That's what earns automation a bad name, not the automating itself.

A reliable account and a repeat late payer shouldn't get the same starting point. The first deserves the full sequence, starting at the gentle pre-due nudge, because their history has earned that benefit of the doubt. The second can reasonably start at day 14, and a large key account may be worth a phone call before any email at all. Blasting the same template to everyone treats a relationship like a form letter: it saves the sender a minute and costs the reader's patience. Deciding who starts where is most of what automating accounts receivable actually involves.

How to build a payment reminder sequence, step by step

You don't need software to start. A shared folder of five templates and a habit of checking the aging report on the same day each week covers a small business. Here's the sequence to actually build it, in order.

1. Map the five stages to your own terms. If you invoice on 14-day terms, don't wait until calendar day 30 to sound firm, scale the stages to a multiple of your own payment window instead of copying someone else's.
2. Write one template per stage, not one for everything. Five short drafts, saved somewhere your whole team can find and use, each pitched at a different level of urgency.
3. Decide who starts where. A reliable customer gets the full sequence from the pre-due nudge. A customer with a pattern of late payment can reasonably start at day 14 or day 30.
4. Set sends by each invoice's due date, not the calendar. A reminder scheduled for the last day of the month catches some invoices right on time and others three weeks late.
5. Check for payment before every send. A firm reminder demanding money for an invoice that was paid yesterday undoes exactly the trust the sequence is supposed to build.
6. Decide the real escalation step in advance. Know what actually happens after the final notice, a collections process, a credit hold, or something else, and only promise it if you'll follow through.

Every one of those steps is simple by itself and hard to sustain by hand once you're past a handful of invoices a week, because it has to happen on the right day, for every invoice, without slipping when someone's out sick. That's exactly the shape of work the agents we build take on. We built one for a building-materials distributor whose AR team was chasing overdue invoices by hand, see the invoice chase case study: it knows who owes what today, follows up in the company's tone on a sensible schedule, and stops the moment an invoice is paid.

Frequently asked questions

The bottom line

A payment reminder email is not hard to write. Five short, honest templates and a schedule you actually stick to will out-collect a beautifully worded single message every time. The tone should shift as the invoice ages, and the sequence should know who it's talking to.

If your team is already sending something like this by hand, the templates above will make it sharper. If nobody has time to send it consistently, that's a scheduling problem, not a writing one, and it's the exact problem worth automating first.