Past Due Email Templates: The 4-Notice Ladder

These past due email templates are for the invoice that is already overdue — the human-sent ladder you run when a balance sits unpaid, especially on B2B accounts where an accounts payable contact, not an automated checkout, controls the payment. That makes this page different from our automated dunning email templates: those fire automatically inside a subscription billing sequence the moment a card fails. The four notices below are deliberate, escalating, and sent by a person who can answer a reply. Copy them as written, fill the bracketed fields, and keep the timing discipline: each notice earns the next one's firmer tone.

The ladder at a glance

Notice	When to send	Tone	Sent by
1. Friendly reminder	1–3 days past due	Assume an oversight	Automation or owner of the account
2. Second notice	7–10 days past due	Clear, specific, still warm	Account owner
3. Firm notice	14–21 days past due	Firm: name the consequence	Account owner or finance
4. Final demand	28–30 days past due	Formal, short, dated	Finance — a human, always

Do not compress this ladder into a week. Most past-due balances at the first notice are process failures on the customer's side — a card on file with the wrong person, an invoice sitting in the wrong inbox. Escalating faster than the ladder reads as aggression and buys nothing. For the wider B2B context behind these notices, see our guide to B2B subscription payment recovery.

Template 1 — Friendly reminder (1–3 days past due)

Subject: Quick note on invoice [number] — payment now due

Hi [First name],

A quick note that invoice [number] for [amount], due on [due date], is now showing as past due on our side. This is often just an expired card or an invoice that landed in the wrong inbox, so we wanted to flag it early while it is easy to fix.

You can update your payment details here: [payment update link]. If you have already paid, or if this invoice should go to someone else on your team, just reply to this email and we will sort it out.

Thanks,
[Your name], [Business name]

Why it works: it offers two innocent explanations before it asks for anything, and it gives the recipient an exit — "send me to the right person" — that frequently is the whole problem on B2B accounts.

Template 2 — Second notice (7–10 days past due)

Subject: Invoice [number] for [amount] is 7 days past due

Hi [First name],

Following up on invoice [number] for [amount], originally due [due date]. We have not received payment yet, and we want to make sure your account stays in good standing and your service continues without interruption.

To resolve this today, update your payment method here: [payment update link]. If there is a problem with the invoice itself — a wrong amount, a missing purchase order number, anything — reply and tell us; we would rather fix it than keep reminding you.

If payment is already on its way, thank you, and please disregard this note.

[Your name], [Business name]

Why it works: it names the amount and the age of the debt in the subject line, where an AP inbox triages it, and it explicitly invites a dispute. A disputed invoice handled at day 7 costs a reply; handled at day 30 it costs the relationship.

Template 3 — Firm notice (14–21 days past due)

Subject: Action needed: invoice [number] is [14/21] days past due

Hi [First name],

Invoice [number] for [amount] is now [number] days past due. Despite our previous notes, we have not received payment or heard from you about an issue with the invoice.

Please arrange payment by [specific date, 5–7 days out] using this link: [payment link]. If we have not received payment or a reply by that date, we will need to pause your account on [specific date], which will interrupt [the service / deliveries / access] for your team.

If something is blocking payment, reply to this email today and we will work through it with you. Silence is the one option that guarantees the pause happens.

[Your name], Finance, [Business name]

Why it works: firm means specific, not loud. A concrete date, a concrete consequence, and a stated preference for a reply. Never threaten a consequence you will not carry out — one empty threat trains the customer to ignore every later notice.

Template 4 — Final demand (28–30 days past due)

Subject: Final notice: invoice [number] for [amount]

Dear [Name / Accounts Payable team],

This is a final notice regarding invoice [number] for [amount], due [due date] and now [number] days past due. Previous reminders were sent on [date] and [date].

Unless payment is received by [specific date], your account will be [paused / closed] on that date and the balance may be passed for further collection activity in line with our terms.

To pay now: [payment link]. To discuss the balance, reply to this email or contact [finance email / phone]. If you believe this invoice was issued in error, reply with the detail and we will review it the same day.

[Full name], Finance, [Business name]

Why it works: it is short, dated, and documentary. By this point the email is a record as much as a request — it lists what was sent and when, names exactly what happens next, and still leaves a genuine dispute path open. Send this one from a named human in finance, never from an automated sequence.

Tone rules: the line between firm and hostile

• Firm is about facts: amount, dates, deadlines, consequences. Hostile is about character: never imply dishonesty, incompetence, or bad faith.
• One ask per email. Pay, reply, or redirect you to the right person. Notices that ask for three things get none of them.
• Never shame and never copy the world. Do not cc colleagues, managers, or group inboxes to apply pressure unless the account's own terms and your existing relationship make escalation to a named finance contact appropriate — and in B2B, escalating to the AP contact is normal; escalating to embarrass is not.
• Shorten as you escalate. Each notice should be shorter than the last. Length reads as negotiability.
• Keep every promise in the copy. If the email says the account pauses on a date, pause it on that date — or send a human explanation before it.

B2B accounts payable etiquette

On B2B accounts, assume you are dealing with a process, not a person dodging you. Ask who owns vendor payments and get that name for the next notice. Include the purchase order number, invoice number, and amount in every send — AP teams pay from those fields, not from your prose. Accept that many companies pay on fixed weekly or monthly runs: a reply saying "you are in Friday's run" is a resolution, and the correct response is to note the date and stop the ladder until it passes. If the same account lands on the ladder repeatedly, the fix is structural — a card on file, a different billing date, or a direct AP contact — not a sterner template.

Where automation takes over

This ladder is for invoiced and high-touch accounts. For self-serve subscriptions failing at the card level, a human ladder cannot keep up — model the volume with the recovery calculator and compare your failure pattern with the failed payment recovery benchmarks. One relevant pattern: each additional dunning email touch adds roughly 1–2 points of recovery (Churnkey analysis of Stripe data), which is why the automated sequence and this human ladder both use several touches — spaced, escalating, and always with a working payment link.

The bottom line

Past due recovery is a tone discipline executed on a schedule: assume an oversight first, get specific second, name a real consequence third, and put a dated final notice in writing fourth. Every template above works only if the dates are real and the consequences happen. Run the ladder by hand for invoiced accounts, and automate the card-failure side rather than copying these notices into a sequence they were not built for. If the automated side is the gap, Swipe Again handles retries, branded dunning emails, SMS, and card-update pages for a flat $179/mo — check pricing to see whether it fits your volume.

Frequently asked questions

How many past due emails should I send before pausing an account?

Four notices over about thirty days is a workable default: a friendly reminder, a second notice, a firm notice naming the pause date, and a final demand. The exact count matters less than real spacing and consequences that actually happen on the dates stated.

What is the difference between a past due email and a dunning email?

A dunning email is automated and fires inside a billing system when a payment fails. A past due email is a deliberate, usually human-sent notice about an invoice that is already overdue. The ladder on this page is the human version, built mainly for invoiced and B2B accounts.

Should the final demand come from finance or the account owner?

Finance. A change of sender signals a change of seriousness, and the final notice functions as a record of what was requested and when. The account owner should stay the friendly route back in if the customer replies.

Can I add late fees in a past due notice?

Only if your contract or terms already provide for them, and only stated exactly as those terms state them. Never introduce a fee for the first time inside a collection email, and check your terms before referencing one at all.

What if the customer replies that the invoice is wrong?

Stop the ladder immediately, resolve the dispute, and restart only if a corrected balance remains unpaid. Continuing to escalate over a genuinely disputed invoice damages the relationship far more than the invoice is worth.

The cheaper save happens earlier: the pre-dunning email templates warn subscribers before a known card expiry turns into a failure at all.