The goal of a reminder is payment, not apology. Most overdue emails fail in one of two directions: so vague that the reader cannot tell what to do, or so apologetic that the deadline stops feeling real. A useful reminder states the invoice, the amount, the date it was due, and the single action needed — then stops.
A cadence matters more than any individual email. Seven touches, spaced over roughly forty-five days, moving from courtesy to consequence. Most invoices clear at stage two or three; the later stages exist so that the rare difficult case has a documented trail.
The cadence at a glance
| Stage | Send | Tone | Purpose |
|---|---|---|---|
| 1 · Pre-due | 3 days before | Courtesy | Catch problems before they become overdue |
| 2 · Due today | On due date | Neutral | Confirm it is in the payment run |
| 3 · Overdue | +3 days | Neutral | Re-attach the invoice, ask for a date |
| 4 · Firm | +10 days | Direct | Request a specific payment date |
| 5 · Escalation | +20 days | Formal | Note the consequence and the deadline |
| 6 · Final notice | +30 days | Formal | State what happens next, with a date |
| 7 · Handover | +45 days | Factual | Record the trail before external recovery |
Stage 1: pre-due courtesy
Use when: three days remain and there is no sign of a problem.
Subject: Invoice [number] due [date]
Hi [Name],
A quick note that invoice [number] for [amount] falls due on [date]. It is attached again for convenience.
If anything on it needs changing — a PO number, a different billing contact — tell me now and I will reissue it before the date.
[Your name]
Stage 2: due today
Use when: the due date has arrived.
Subject: Invoice [number] due today
Hi [Name],
Invoice [number] for [amount] is due today. Could you confirm it is in this week's payment run, or let me know if it is held up on your side?
Invoice attached.
[Your name]
Stage 3: overdue, first notice
Use when: three days have passed with no reply.
Subject: Invoice [number] · [amount] overdue
Hi [Name],
Invoice [number] for [amount] was due on [date] and we have not seen payment. Invoice attached.
If it is already processed, ignore this. If not, could you confirm the date it will be paid?
[Your name]
Stage 4: firm request
Use when: ten days overdue, and the first notice got no reply.
Subject: Payment date needed · Invoice [number]
Hi [Name],
Invoice [number] for [amount] is now [N] days overdue. I would rather resolve this directly than through a formal process.
Please confirm by [date] the date payment will be made. If there is a dispute about part of the invoice, tell me which part and we will separate it from the rest.
[Your name]
Stage 5: escalation notice
Use when: twenty days overdue.
Subject: Overdue account · Invoice [number] · [amount]
Hi [Name],
Invoice [number] remains unpaid [N] days after the due date of [date].
Unless payment is received by [date], [consequence — work paused, account referred, late fees applied per agreement]. Existing commitments remain unaffected until that date.
[Your name]
Stage 6: final notice before handover
Use when: thirty days overdue and you intend to escalate.
Subject: Final notice · Invoice [number]
Hi [Name],
This is the final notice for invoice [number] ([amount]), originally due [date].
If payment is not received by [date], the account will be [handed to our recovery agent / referred to small claims], and [any further consequence]. A copy of the correspondence to date is attached.
If there is a reason I have not heard about, I would still like to resolve it. [Phone number].
[Your name]
Stage 7: internal handover record
Use when: preparing the file for external recovery — this one is internal, not sent to the client.
Invoice [number] · [amount] · issued [date] · due [date]
Contact: [name, role, email, phone]
Reminders sent: [dates] · Replies received: [dates and substance]
Disputes raised: [yes/no, detail] · Payments received: [amounts and dates]
Contract reference: [agreement, payment terms, late fee clause]
Phrasing that changes the outcome
Small wording choices carry most of the weight. Ask for a date, not for payment — "when will this be paid" is easier to answer than "please pay this", and a committed date is enforceable in a way a request is not. Re-attach the invoice every time, because the most common cause of non-payment is that the document is nowhere to be found. Name the specific consequence rather than implying one; vague threats get ignored.
Separate disputes from the rest. If the client challenges one line item, agree the undisputed amount and a date, and handle the contested part separately. Bundling them is how recoverable money becomes unrecoverable.
Keep every email short enough to read on a phone. If yours needs scrolling, it will be deferred, and deferred means forgotten.
Turn the cadence into drafts
Set the seven stages once, then let a tool produce each message with the invoice details filled in. You still check the numbers.
Try Rytr →Frequently Asked Questions
How soon should I send the first reminder?
Three days before the due date, as a courtesy. It catches missing PO numbers and wrong billing contacts while there is still time to fix them.
Should I call as well as email?
From stage four, yes. A phone call resolves what email cannot, and it confirms the reminder reached a person.
Can I charge late fees?
Only if your contract or invoice terms allow it and you stated it before the work began. Applied retroactively, it is rarely enforceable.
What if the client disputes part of the invoice?
Split it. Agree the undisputed amount and a payment date, then resolve the contested line separately.
How long before I escalate?
Roughly forty-five days from the due date, provided you have a documented trail of reminders and any replies.
Is it too aggressive to set a deadline?
No, provided it is specific and you honour it. Deadlines that pass without consequence are worse than none.