How to build a payment reminder email sequence that collects on autopilot

A payment reminder email sequence is a scheduled series of emails tied to each invoice's due date that nudges the customer before, on, and after the due date until the invoice is paid. Built well, it collects most invoices on the first one or two touches without anyone chasing by hand, and it escalates tone only for the few that go quiet. This guide gives you the cadence, the templates for each stage, and the metrics to prove it works.

The reason a sequence beats one-off reminders is consistency. A person forgets to follow up, gets busy, or skips the awkward second email. A sequence sends the right message at the right age every time, which is what gets the bulk of your ledger paid before it ages.

What a reminder sequence should accomplish

A good sequence does three jobs at once. First, it prevents late payments by reminding customers before the due date, since most missed invoices are oversights, not refusals. Second, it recovers overdue balances by escalating tone in a controlled way as the invoice ages. Third, it protects the relationship by staying polite early and only getting firm when the customer has gone silent.

What it should not do is spam. Sending the same flat "payment is due" email five times trains customers to ignore you. Each touch needs a clear reason to exist: a different tone, a sharper consequence, or a new option like a payment plan. The aim is to collect with the fewest, best-timed messages, not the most.

The ideal reminder cadence and timing

For standard net-30 terms, this cadence balances persistence against relationship. It front-loads gentle reminders, then escalates as the balance ages.

Shorten the spacing for shorter terms and stretch it for longer ones. Tighten it for habitual late payers and loosen it for reliable customers. The structure stays the same: start before the due date, and let tone climb with the age of the invoice rather than jumping straight to stern.

Pre-due, due-date, and overdue templates

Below are the three templates that anchor the sequence. Keep every email short, name the exact invoice and amount, and put a payment link in front of the customer every time. Fill the [Placeholders] before sending.

Pre-due reminder

Subject: Invoice [Invoice number] is due [Due date]

Hi [Customer name],

A quick heads-up that invoice [Invoice number] for [Amount] is due on
[Due date].

You can pay it here: [Payment link]

If you have already scheduled payment, thank you. If anything on the invoice
needs a second look, just reply and we'll sort it out.

Thanks,
[Your name]
[Company name]

When to send: 3 to 5 days before the due date, as a courtesy nudge.

Due-date reminder

Subject: Invoice [Invoice number] is due today

Hi [Customer name],

Just a reminder that invoice [Invoice number] for [Amount] is due today.

Here's the payment link to make it easy: [Payment link]

If payment is already on its way, please ignore this. Otherwise, reply if there's
anything we can help with.

Thanks,
[Your name]
[Company name]

When to send: on the due date itself.

Overdue escalation

Subject: Action needed: invoice [Invoice number] is [Days overdue] days overdue

Hi [Customer name],

Invoice [Invoice number] for [Amount] was due on [Due date] and is now
[Days overdue] days overdue. We haven't received payment or heard back.

Please settle the balance here: [Payment link]

If you can't pay in full right now, reply and let us know. We'd rather agree on a
payment date with you than let this keep aging.

Regards,
[Your name]
[Company name]

When to send: at 15 days past due, then escalate tone further at 30 and 45 days. For a deeper set of stage-by-stage messages you can drop into each step, see these collection email templates.

When to switch channels and escalate

Email carries the routine load, but some invoices need a different channel. Switch when a balance is large, when two or more reminders have gone unanswered, or when you need a real-time decision. A phone call gets you a commitment that email can't, and a written letter adds weight late in the cycle.

Two events should pull an invoice out of the automated sequence entirely: a dispute and a promise to pay. The moment a customer questions the charge, stop reminding and resolve the dispute, because another nudge only annoys them. The moment they commit to a date, pause the cadence and follow up on that specific promise instead. Knowing when a friendly reminder should give way to a final notice keeps your escalation proportional to the situation.

Measuring sequence performance

Track the sequence so you can tune it rather than guess. Watch these:

• Paid-by-step rate. What share of invoices clear at each touch. If most land on steps 1 and 2, your front-loading is working.
• Average days to pay. The gap between invoice date and payment. A falling number means the cadence is pulling cash in earlier.
• Reply and click rates per email. Low engagement on a given step tells you the subject line or tone needs work.
• DSO trend. The headline measure. A reminder sequence that works shows up as a steady drop in days sales outstanding over a few months.

Review these monthly. If one step underperforms, change one variable at a time, the timing or the copy, and watch the paid-by-step rate move.

How Rex runs the sequence automatically

A reminder sequence only collects on autopilot if something actually runs it on every invoice, every day, without forgetting. That is the work Rex does. Rex watches each open invoice, sends the right message at the right age across the whole cadence, and stops the instant cash lands, so customers never get a reminder for an invoice they already paid.

Rex also handles the exceptions that break a do-it-yourself sequence. It pauses automatically when a customer raises a dispute or promises a date, follows up on that exact commitment, switches to a firmer tone as the balance ages, and escalates only the cases that genuinely need a person. The team stops chasing the calendar and sees just the decisions that matter. See how Rex runs collections end to end.