A payment reminder email gets paid faster when it carries the invoice reference, amount, due date, payment route and a real dispute route in one short message — and when it is sent on a schedule rather than when somebody remembers. Below are six stage-specific examples, from a pre-due heads-up to a firm final internal reminder, plus a builder that produces the finished email as Word or PDF.
Create a polite reminder without generated fees, threats, legal deadlines, or jurisdictional claims. The final copy keeps the invoice reference, amount, due date, stage, payment route, contact, and dispute path together.
Guided draft builder
* marks fields required for final exports. Blank fields remain visible as placeholders in draft preview.
Enter the verified invoice amount only.
Same values in every output
Draft — review required
Subject: [Reminder stage] — invoice [Invoice reference]
Hello,
Please review the invoice details below.
| Invoice | Amount | Due date |
|---|---|---|
| [Invoice reference] | [Currency] [Amount] | [Due date] |
Payment route: [Payment instructions or link]
[Question or dispute route]
Thank you, [Accounts contact] [Sender organization]
Copy is an honest paste workflow. Downloads are real files built after server-side validation.
Before final export
Editorial examples
One example per stage of a normal reminder sequence. All references and amounts are invented. These are operational wordings reviewed for neutrality; they are not debt-recovery, legal or tax advice.
Use when: A courtesy heads-up that also confirms the invoice arrived and reached the right person.
Subject: Invoice INV-1042 due 14 August — £1,250.00
Hello Jordan,
A quick note that invoice INV-1042 for £1,250.00 is due on 14 August. The invoice is attached again for convenience.
Payment route: the bank details shown on INV-1042, quoting INV-1042 as the reference.
If it has already been scheduled, please ignore this. If anything on the invoice needs changing before it can be paid — a PO number, an entity name, a cost code — reply and I will reissue it today.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: Keep this one genuinely short. Its job is to catch a missing PO number while there is still time to fix it.
Use when: The due date has arrived and no payment or remittance advice has been received.
Subject: Invoice INV-1042 is due today — £1,250.00
Hello Jordan,
Invoice INV-1042 for £1,250.00 is due today, 14 August. We have not received a payment or remittance advice yet.
Payment route: the bank details on INV-1042, reference INV-1042.
If it is already in your payment run, could you confirm the run date so I can close it on our side? If it is held for any reason, tell me what is needed and I will sort it today.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: Asking for the payment-run date is the most useful question here — it usually replaces three follow-ups.
Use when: First reminder after the due date, still assuming an administrative hold rather than a refusal.
Subject: Invoice INV-1042 — 7 days past due (£1,250.00)
Hello Jordan,
Invoice INV-1042 for £1,250.00 was due on 14 August and is now seven days past due. I have not had a payment or a reply, so I would like to check whether it is stuck rather than assume it was declined.
Invoice INV-1042 · £1,250.00 · due 14 August · payment route: bank details on the invoice, reference INV-1042.
Common holds at this stage are a missing PO number, an approver on leave, or the invoice sitting in a queue we cannot see. If any of those apply, tell me which and I will work with whoever needs it.
If it is already paid, please send the remittance and I will reconcile it and stop the reminders.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: Naming the three usual holds makes replying easy. Do not add a consequence at this stage — there is nothing to escalate to yet.
Use when: Earlier reminders went unanswered. Firm, factual, still neutral, and copied to a finance owner.
Subject: Overdue invoice INV-1042 — £1,250.00, 30 days past due
Hello Jordan, and copying Rae Whitcombe in finance,
Invoice INV-1042 for £1,250.00 was due on 14 August and is now thirty days past due. I sent reminders on 11, 14 and 21 August and have not had a reply to any of them.
Invoice INV-1042 · £1,250.00 · issued 31 July · due 14 August · payment route: bank details on the invoice, reference INV-1042.
Payment timing follows the terms already agreed for this invoice. I am not adding any charge to it.
Please either confirm the payment date, or tell me what is preventing payment so it can be resolved. If there is a dispute about the work or the amount, say so directly and I will put it in front of the right person here this week.
If I have not heard from you by 20 September, I will refer this internally to our finance lead to decide next steps.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: The final line says only that the matter moves internally — a fact you control. Do not name legal action, collection agencies, interest or fees in a templated email.
Use when: Some money arrived, or the customer has asked to pay in instalments.
Subject: INV-1042 — £500.00 received, £750.00 outstanding
Hello Jordan,
Thank you — £500.00 reached us on 22 August against invoice INV-1042. That leaves £750.00 outstanding on an invoice due 14 August.
You mentioned splitting the balance. Two payments of £375.00 on 5 and 19 September would work for us if that suits you. Confirm in a reply and I will note the dates against the invoice so no further reminders go out in the meantime.
Payment route stays the same: bank details on INV-1042, reference INV-1042.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: Put the arrangement in writing with amounts and dates, and record it against the invoice so your own reminder schedule does not undercut it. Any change to agreed terms should follow your organisation’s approval process.
Use when: The customer has told you something is wrong, or their accounts payable process has rejected the invoice.
Subject: INV-1042 — resolving the query so it can be paid
Hello Jordan,
Thanks for telling me INV-1042 is on hold. As I understand it, the query is that the purchase order number is missing and your system will not accept the invoice without it.
Here is what I can do: send me the PO number and I will reissue INV-1042 with it today, keeping the amount at £1,250.00 and the original due date of 14 August unchanged.
If the query is about the amount or the work rather than the paperwork, tell me which lines are in question and I will get them reviewed here and come back to you with either a correction or an explanation by 28 August.
I have paused the reminder schedule on this invoice until 28 August so we are not talking past each other.
Thank you,
Morgan Ellis — Accounts, Northstar Studio
What to change: Restate the dispute in your own words so any misunderstanding surfaces immediately, and pause the reminders you said you would pause.
These examples are written illustrations, not records of real customers, invoices or clients. To produce a version with your own verified details — and a real Word or PDF file rather than a copied block of text — use the builder above.
Field coverage
The builder above requires the items marked with an asterisk before it will produce a final file. This list is the reasoning behind that field model.
Method
Three to five working days before the due date, as a courtesy with the invoice attached. It costs nothing and removes “we never received it” from the conversation.
Due date, then roughly 7, 14 and 30 days after. A predictable rhythm reads as process; sporadic chasing reads as personal and invites negotiation.
Move from the day-to-day contact to accounts payable to their finance lead. Changing who receives the email works better than making the language sharper.
Most late invoices are stuck, not refused — a missing PO number, a wrong entity, a rejected format, an approver on leave. One question surfaces that in a single reply.
Repeat the payment route in every email. Never make the recipient open a previous thread or an attachment to find where the money goes.
When internal reminders are exhausted, escalate through your organisation’s approved route and take qualified advice. Do not let an email template be the thing that asserts a legal position.
Questions
Answers from the same editorial review that owns the builder. Where a question touches legal, tax or regulatory ground, the answer says so rather than guessing.
Report a correctionSend a short factual email with the invoice reference, amount, due date and payment route, and add one line inviting them to tell you if something is blocking it. Politeness comes from assuming the invoice is stuck rather than refused; firmness comes from sending the reminder on schedule rather than from stronger language.
A common sequence is four: a courtesy note before the due date, one on the due date, one around seven days overdue, and one around thirty days overdue sent to an escalated recipient. Beyond that, more emails to the same person rarely help — escalate through your own approved internal route instead.
Change the recipient before you change the tone: day-to-day contact, then accounts payable, then their finance lead. Keep a dated record of every reminder sent. When your internal sequence is exhausted, refer the matter through your organisation’s approved escalation process and take qualified advice — an email template is the wrong place to assert a legal position.
Only where that was already agreed for the invoice, and entitlement depends on your contract and jurisdiction. This builder never adds a fee, interest figure, statutory claim or legal deadline for you. If you intend to charge something, confirm the entitlement through qualified advice and state the agreed term rather than letting a template imply one.
Yes for the pre-due and due-date reminders, and restate the payment route as text in the email body as well. Many accounts-payable systems strip or quarantine attachments, so the reference, amount and payment route should be readable without opening anything.
Email is faster, timestamped and easier to forward to an approver, which is why it works for the routine sequence. A letter matters mainly when your own process or contract requires written notice at a particular stage — check that requirement rather than assuming it. The builder exports the same reminder as a .docx or .pdf when you need a formal copy on file.
Editorial and review record
Added six stage-specific reminder examples (pre-due, due today, seven days, thirty days escalated, partial payment, disputed invoice), sequence guidance, prohibited wording, and six reviewed answers. Field model and export behaviour are unchanged.
Verify the invoice and agreed terms before sending. The builder never adds fees, threats, statutory interest, legal deadlines, or jurisdiction-specific claims.
Sources inform field coverage and conservative boundaries. They do not certify the generated document or endorse TemplateNook.
Polite reminder, agreed terms, amount, due date, payment route, and escalation boundaries.
Stage-specific tone, invoice details, payment route, and dispute/blocker check.
Adjacent jobs
Customer recovery
Reviewedv1.1.0 · reviewed 2026-07-25
Draft a specific, accountable apology with the impact, action taken, next step, and escalation route kept visible.
Controlled operations
Reviewedv1.1.0 · reviewed 2026-07-25
Create an organization-scoped SOP covering revisions, ownership, approval, controlled copies, review, archive, and exceptions.