Invoice Follow-Up Email Templates, From Polite to Firm

July 2026 · 5 min read

Good follow-up emails share three traits: they're short, they're specific (invoice number, amount, date — every time), and each one is slightly harder to ignore than the last. The escalation should live in the structure — tighter deadlines, more explicit consequences — not in the tone, which stays professional all the way down. Here's a ladder you can copy, and when to send each rung.

1. The nudge — a few days before the due date

Optional, but it measurably reduces late payments, and it's the friendliest email in the sequence because nothing is wrong yet:

Subject: Invoice #1042 due Friday

Hi Karen — quick reminder that invoice #1042 for $2,140 is due this Friday, June 12. If it's already in process, ignore this. If anything's needed on our side to get it through — a PO number, a W-9 — just let me know.

2. First follow-up — 3–5 days past due

Assume good faith: most first-lateness is an invoice that fell through a crack, not a decision.

Subject: Following up: invoice #1042 ($2,140, due June 12)

Hi Karen — following up on invoice #1042 for $2,140, which came due on June 12. Could you let me know when payment is scheduled? Happy to resend the invoice or answer any questions. Thanks!

The key ask is a date. "We'll get to it" is not a useful reply; "scheduled for the 24th" is a commitment you can track — and hold them to.

3. Second follow-up — about two weeks past due

Same courtesy, more structure. Name the history, ask for a specific commitment, and set your own next checkpoint:

Subject: Invoice #1042 — now 2 weeks past due

Hi Karen — invoice #1042 for $2,140 is now two weeks past its June 12 due date, and I haven't been able to get a payment date from you yet. Could you confirm by Thursday when this will be paid? If there's an issue with the invoice itself, tell me now and we'll resolve it — otherwise I'll follow up again Friday.

4. After a broken promise to pay

This one is its own category, because the context changed: they gave you a date and missed it. Reference the promise directly — it does the escalating for you:

Subject: Invoice #1039 — payment promised for May 16

Hi Bryan — on May 2 you mentioned invoice #1039 ($6,720) would be paid by May 16. That date has passed and the payment hasn't arrived. Can you tell me what happened and give me a firm new date? Given the earlier commitment, I do need something concrete this time — a scheduled payment confirmation or a check number once it's sent.

Broken promises are also where you should quietly tighten terms going forward — deposits, shorter nets, or pause-work clauses for repeat offenders. Which requires actually tracking promises and their dates; more on that in our guide to tracking invoice replies.

5. Final notice — 45–60 days past due

State facts, state consequences, stay flat. No anger — anger reads as bluffing:

Subject: Final notice — invoice #1039, 60 days past due

Bryan — invoice #1039 for $6,720 is now 60 days past due. We've followed up on June 1, June 15, and June 29, including a payment commitment for May 16 that wasn't met. If payment isn't received by July 15, we'll have to [pause current work / apply the late fee per our terms / refer this to collections]. I'd much rather resolve it directly — call me today or tomorrow and we'll work out a plan.

Only name consequences you'll actually enforce. An empty threat teaches the customer that your final notices are just louder reminders.

The system behind the templates

Templates are the easy half. The hard half is knowing which invoice needs which email today — who's at day 5 vs. day 45, whose promise lapsed yesterday, who replied with a dispute that pauses the ladder entirely. That's a tracking problem, and past a few dozen invoices a month it's the part that actually breaks. If replies were logged with their meaning and dates, the right next email would be obvious every morning.