An overdue invoice email needs the amount, the invoice number, and how many days past due it is stated in the first two sentences, every time, regardless of how many notices you've already sent. What should change across a collections sequence is the tone and the stated consequence, not how specific you are about the numbers.
What an Overdue Invoice Email Needs at Every Stage
Exact figures, always. "Your invoice is overdue" makes the recipient go look something up. "Invoice #1042 for $4,200 is 12 days past due" gives them everything they need to act immediately.
No hedging language past the first notice. "Just wanted to check in" or "no rush, but" undercuts a message that's supposed to be about a real, overdue obligation. Save the softer language for the first notice only, if at all.
A specific next step, not just a status update. Every notice should tell the recipient what happens next: what you need from them, and by when, not just restate that money is owed.
A stated consequence in the final notice, and only in the final notice. Threatening collections or late fees in the first notice reads as disproportionate. Reserve it for the point in the sequence where it's actually the next real step.
Overdue Invoice Email Sequence
First notice, a few days to a week past due
Assume oversight, not bad faith. Still specific about the numbers.
Subject: Invoice #[number], now past due
Hi [Name],
Invoice #[number] for $[amount], due [original due date], hasn't come through yet. This is often just a scheduling gap on the payment side, wanted to flag it in case it slipped through.
Could you confirm the status, or let me know if there's a question about the invoice?
[Your name]
Second notice, two to three weeks past due
Firmer. No hedging. Still professional.
Subject: Invoice #[number], now [X] days past due
Hi [Name],
Invoice #[number] for $[amount] is now [X] days past due. Original due date was [date].
If there's a hold on your end or a question about the invoice, let me know and I can help resolve it. If payment is already in process, a confirmation of the date would be helpful.
Please reply to confirm status by [specific date].
[Your name]
Final notice before escalation
States the specific consequence and date clearly, once.
Subject: Final notice: Invoice #[number], [X] days past due
Hi [Name],
Invoice #[number] for $[amount] remains unpaid, now [X] days past due after two previous notices.
If we don't receive payment or hear from you by [specific date], we will need to [specific consequence, e.g., "refer this to formal collections" or "pause work on active projects until the account is current"].
I'd rather resolve this directly. Please reply or call [phone number] this week.
[Your name]
Responding to a disputed invoice
Pause the escalation and address the specific issue raised.
Subject: Re: Invoice #[number]
Hi [Name],
Thanks for flagging the concern about [specific line item or issue]. [Direct response to the specific dispute: correction, explanation, or a request for more detail.]
Once this is resolved, I'll follow up on the remaining balance of $[amount]. Let me know if you need anything else from me in the meantime.
[Your name]
Common Mistakes
Using "just a friendly reminder" past the first notice. It reads as either out of touch with how overdue the invoice actually is, or as passive-aggressive once the recipient knows it's the third email.
Vague amounts or dates. Any overdue invoice email that doesn't restate the exact figure and due date makes the recipient do work you could have done for them in one line.
Threatening consequences too early. Mentioning collections or late fees in the first notice, before there's any indication of bad faith, escalates a situation that might just be an oversight.
No clear next step. "Please pay this invoice" without a specific date or action leaves the recipient to decide when it actually needs to happen, which is usually later than you'd like.
Related Reading
For softer, non-collections reminder situations, see friendly reminder emails and how to write a reminder email. For the broader finance and AR communication workload, see how ForthWrite works for finance and accounting professionals.
Build a voice profile so collections emails stay firm without sounding cold →