The most effective payment reminder email is rarely the sternest one. It is the one that arrives on schedule, names the invoice precisely, and puts a payment link one click away. In B2B, where most late payments are invoices that got buried in an AP queue rather than deliberate non-payment, consistency beats intensity: buyers pay the suppliers who reliably ask. Below are seven copy-paste templates mapped to the cadence that works (pre-due, due date, +7, +14, +30, a payment-plan offer, and a final demand), plus the rules that make any reminder land.
The five rules of a reminder that gets paid
Before the templates, the mechanics. Every effective B2B payment reminder does five things:
- Names the invoice in the subject line: invoice number, and once overdue, how overdue. AP inboxes triage by subject.
- States number, amount, and due date in the first two sentences. The reader should never have to open an attachment to know what you're asking for.
- Includes a one-click payment link: card and ACH on a hosted page, through your existing payment provider. Every step between "reminder read" and "payment made" costs days.
- References the PO number where the buyer requires one. An unmatched invoice can't be approved, no matter how polite the email.
- Invites a reply. A silent stall becomes a conversation, and a dispute you can resolve is worth more than a reminder you can resend.
One more rule about the sender: reminders should come from your domain, in your brand's voice. Buyers deprioritise third-party dunning notices.
The cadence, then the templates
The schedule matters more than the wording: a nudge 3 days before due, a prompt on the due date, follow-ups at +7 and +14, and a formal escalation at +30, applied to every invoice, not just the big ones. This cadence is the single largest DSO lever available to a finance team. Fill in the brackets and send.
Template 1: Pre-due nudge (day −3)
Subject: Invoice [#1234] from [Your Company] - due [date]
Hi [Name],
A quick heads-up that invoice [#1234] for [$amount] (PO [number]) is due on [date].
You can pay by card or bank transfer in one click here: [payment link]
If anything on the invoice needs correcting before then, just reply and we'll sort it out.
Thanks, [Name], [Your Company]
Why it works: catches "we never received it" cases while there's still time, and surfaces disputes before the invoice is late.
Template 2: Due-date prompt (day 0)
Subject: Invoice [#1234] is due today
Hi [Name],
Invoice [#1234] for [$amount] falls due today. If it's already in your payment run, thank you. Please disregard this note.
If not, you can settle it in under a minute here: [payment link]
Any questions, just reply.
Best, [Name]
Template 3: First follow-up (day +7)
Subject: Overdue: invoice [#1234] - 7 days past due
Hi [Name],
Our records show invoice [#1234] for [$amount], due [date], is now 7 days past due. A copy is attached in case the original didn't reach you.
Pay by card or ACH here: [payment link]
If the invoice is queued for approval or there's an issue holding it up, let me know and I'll help move it along.
Thanks, [Name]
Template 4: Second follow-up (day +14)
Subject: Invoice [#1234] - 14 days past due, action needed
Hi [Name],
Following up on invoice [#1234] for [$amount], now 14 days past due despite earlier reminders.
Please arrange payment here: [payment link], or reply with a payment date we can plan around.
If there's a query or dispute on this invoice, tell me now so we can resolve it rather than let the balance age.
Regards, [Name]
Why it works: asks for a promise-to-pay, which converts silence into a commitment you can track.
Template 5: Formal escalation (day +30)
Subject: Formal notice: invoice [#1234] - 30 days past due
Dear [Name],
Despite previous reminders, invoice [#1234] for [$amount], due [date], remains unpaid 30 days past its due date.
We ask that the full amount be settled within 7 days: [payment link]
Under our agreed terms, continued non-payment may result in late-payment interest and a hold on the account. If circumstances are making payment difficult, contact me directly. We'd rather agree a plan than escalate.
Sincerely, [Name], [Title]
At this stage, also move the conversation up a level on the buyer's side: AP manager or controller, not the clerk.
Template 6: Payment-plan offer (day +45, for willing-but-constrained buyers)
Subject: Invoice [#1234] - proposal to resolve
Hi [Name],
Invoice [#1234] for [$amount] remains outstanding. If cash flow is the constraint, we can split the balance into [2/3] instalments of [$amount] on [dates], payable here: [payment link].
Reply to confirm and I'll set the schedule up today. A plan that pays beats a demand that doesn't, but we do need one of the two.
Best, [Name]
Template 7: Final demand (day +60/+90)
Subject: Final demand: invoice [#1234]
Dear [Name],
This is a final demand for payment of invoice [#1234], [$amount], due [date], now [X] days overdue. Previous reminders on [dates] have gone unanswered.
Payment in full is required by [firm date, 7-14 days out]: [payment link]
If payment is not received by that date, we will [apply late-payment interest per our terms / place the account on hold / refer the balance to a collection agency], which we would prefer to avoid.
If you dispute this invoice or need to discuss it, contact me before [date].
Sincerely, [Name], [Title]
The honest problem with templates
Templates fix the wording. They don't fix the operational problem: applying this cadence to every invoice, every week, across hundreds of accounts. Adjusting tone per relationship, logging every reply, chasing every promise-to-pay, and stopping instantly when payment lands (nothing burns goodwill like dunning a buyer who already paid, which is a cash application problem, not a wording problem).
Manual teams run this cadence on their top 50 accounts and let the long tail age. That's the gap autonomous AR closes: an agent that sends the right message at the right stage to every account (across email, SMS, and chat) escalates on schedule, reads the replies, and reconciles payments back to the ERP so no one gets chased after paying. The templates above are, in effect, its default policy.
FAQ
When should I send the first payment reminder?
Before the due date - 3 to 5 days out. A pre-due nudge catches lost invoices and open disputes while the invoice can still be paid on time.
How many reminders should I send before escalating?
Typically four (pre-due, due date, +7, +14) before a formal escalation at +30. Escalate in predictable steps; surprises damage relationships more than firmness does.
Should payment reminders include late fees?
Reference late-payment interest only from the formal escalation onward, and only if your contract or governing law (e.g., statutory interest in the UK/EU) supports it. Mentioning penalties in a first reminder sours relationships unnecessarily.
How do I automate payment reminder emails?
AR software ranges from dunning tools that fire scheduled emails to autonomous platforms that run the entire cadence, take payment, and reconcile cash to your ERP. The right level depends on whether you want help sending reminders or want the collecting done for you.
Fin sends every reminder in this guide, so your team doesn't.
Finero's AI agent runs the full chase cadence across email, SMS and chat, with hosted card and ACH payment on every message, and reconciles cash back to your ERP automatically.