Payment reminder templates
Invoice follow-up email templates: five messages for the full receivable arc
Updated 28 April 2026 · 16 min read
Five copy-ready invoice follow-up email templates with placeholders: pre-due, due day, +7, +14, and 30+ days overdue, plus tone notes for repeat late payers. Pairs with our payment reminder deep-dive article for timing and mistakes to avoid.
These invoice follow-up email templates sit on one page so you can paste them into a wiki, a shared doc, or an automation tool. Placeholders use double braces: {{INV}}, {{AMOUNT}}, {{DUE}}, {{PAY_ROUTE}}, {{NAME}}. Replace with your house style. The sequence is designed for typical B2B service work; consumer, legal, or regulated environments may need a review for compliance. The tone principle: each message should add a fact the previous one did not—balance age, pay date offered, or next policy step—not a louder adjective.
Template 1 — Pre-due (3–5 business days before {{DUE}})
Subject: Upcoming payment — invoice {{INV}} (due {{DUE}})
Hi {{NAME}},
Quick note that invoice {{INV}} for {{AMOUNT}} is due on {{DUE}}. Payment route: {{PAY_ROUTE}}.
If anything blocks entry in your AP system (PO line, tax ID, portal setup), reply with the exact item and we will fix it before the due date.
Thanks,
[Company]Template 2 — Due day (quiet check-in)
Subject: Due today — invoice {{INV}} for {{AMOUNT}}
Hi {{NAME}},
Invoice {{INV}} for {{AMOUNT}} is due today per our terms. Payment: {{PAY_ROUTE}}.
If payment is already queued, a one-line remittance note helps us match it. If something is wrong on the invoice, tell us now and we will correct and re-issue the same day where possible.
Thanks,
[Company]Template 3 — Seven days after due (status, not shame)
Subject: Status on {{INV}} — now 7 days past {{DUE}}
Hi {{NAME}},
We do not yet show payment for invoice {{INV}} ({{AMOUNT}}), now 7 days past the {{DUE}} due date. {{PAY_ROUTE}}
Please reply with one of: pay date scheduled, remittance on file, or a specific billing fix you need from us.
Thanks,
[Company]Template 4 — Fourteen days after due (next internal step in policy)
Subject: Overdue — invoice {{INV}} ({{AMOUNT}}) — [action by {{ESCALATE_DATE}}]
Hi {{NAME}},
Invoice {{INV}} for {{AMOUNT}} remains open, now 14 days past due (original due date {{DUE}}). {{PAY_ROUTE}}
Per our [contract / policy], if we do not have payment or a written pay date by {{ESCALATE_DATE}}, we will [pause new work / route to [owner] / other written step].
If cash timing is the issue, propose a pay date in writing; we will log it. If a line item is disputed, name it so we can address it directly.
[Company]Template 5 — Thirty or more days after due (for chronic delay; match your risk tolerance)
Subject: Final written step — open balance {{INV}} ({{AMOUNT}})
Hi {{NAME}},
Invoice {{INV}} for {{AMOUNT}} is more than 30 days past the {{DUE}} due date. We need a path to resolution this week: payment, a firm pay date on letterhead, or a named AP contact to speak with. {{PAY_ROUTE}}
[Optional: next step in your real policy, such as a call time window or a smaller settlement path if you use one. Not legal advice.]
[Company]Tone note for a repeat late payer (same person, not a new company)
Use shorter sentences, reference that you have been here before, and name the last pay date that was broken if you are keeping a log. The goal is not humiliation. It is to make clear that a pattern is visible and you will not pretend it is a one-off. If a friendly relationship is worth preserving, a phone call after template 3 is often the right next step, not a fifth identical email. For step-by-step timing theory, use the invoice payment reminder email resource. For get-paid behavior, use how to get clients to pay on time and invoice payment tips.
Frequently asked questions
How is this different from the payment reminder email article?
That article is a deep guide on timing, tone, and mistakes, with multiple template blocks. This page is a single scroll of five arc templates (pre-due through very late) using a consistent placeholder style, for teams that want to lift copy into their playbooks quickly. Use both together: principles there, quick copy here.
Back to all resources or the Arkvela home page.