Most freelancers write a single payment reminder email and re-use it forever — which is why those reminders work for the easy cases and fail for everything else. A reminder that is too soft at Day 30 sounds careless; a reminder that is too firm at Day 1 sounds aggressive. The fix is having seven templates, sequenced from pre-due through final notice, and sending the right one on the right day. Copy them below.
The structure below maps to how clients actually behave. Most invoices are paid by the second reminder. The small portion that aren't usually share one of three patterns: an approval stuck behind a vacation, an AP batch cadence mismatch, or a genuine dispute. The templates handle all three. For the deeper strategy on why people pay late and how to follow up without burning the relationship, read the full guide.
The seven-stage system at a glance
- Day -3 (pre-due nudge): Friendly heads-up before payment is due. Sets expectation, prevents most lateness.
- Day +1 (gentle reminder): Polite assumption that they meant to pay and forgot. Most invoices get paid here.
- Day +7 (firm but professional): Direct ask, restate due date, attach invoice again.
- Day +14 (escalation flag): Mention timeline expectations, late fee policy if any, request explicit response.
- Day +30 (formal notice): Tone shifts from request to notification. Names consequences.
- Day +45 (final notice): Last email before phone/escalation. Restated terms, clear deadline.
- Day +60 (phone-first follow-up): Email becomes secondary to direct call or stakeholder escalation.
Template 1 — Day -3: The pre-due nudge
Send three business days before the invoice is due. Most freelancers skip this email entirely, which is a mistake — pre-due reminders prevent about 40% of would-be late payments by surfacing the invoice before it's buried in the inbox.
Subject: Invoice #[INV-NUMBER] — due [DUE DATE], no action needed yet Hi [CLIENT NAME], Quick heads-up: invoice #[INV-NUMBER] for [WORK DESCRIPTION] is due [DUE DATE] — that's three business days from now. No action needed if it's already in your AP queue. If you don't see it, I've attached a copy here for convenience. Let me know if there's anything that needs clarification before then. Thanks, [YOUR NAME]
Template 2 — Day +1: The gentle reminder
Send the day after the invoice was due. The tone is "I'm sure this is just a delay" because most of the time it actually is. Approval got stuck, AP runs Thursdays, the invoice landed in spam. The job here is to surface the invoice without sounding like you're accusing anyone of anything.
Subject: Invoice #[INV-NUMBER] — friendly reminder ([X] day past due) Hi [CLIENT NAME], Just a quick note that invoice #[INV-NUMBER] for [WORK DESCRIPTION], dated [INVOICE DATE], was due [DUE DATE] — yesterday. No worries if it's already in flight; this is just a quick nudge in case it slipped through. I've attached the invoice again here. Let me know if you need anything else from me to process it. Thanks, [YOUR NAME]
Template 3 — Day +7: Firm but professional
By Day 7, the easy explanations have run out. The Day 7 email keeps the polite frame but shifts to direct: restate the amount, restate the due date, ask explicitly for a status update. This is the version most freelancers should be sending — many default to repeating the Day 1 tone, which signals lower urgency than is warranted.
Subject: Invoice #[INV-NUMBER] — past due, please advise on timing Hi [CLIENT NAME], I'm following up on invoice #[INV-NUMBER] for [AMOUNT], originally due [DUE DATE]. It's now seven days past due and I wanted to check in directly. Could you let me know either (1) the date payment is scheduled, or (2) if there's anything blocking processing on your end? I've attached the invoice again here in case it would help. Thanks for the quick update, [YOUR NAME]
Template 4 — Day +14: Escalation flag
Two weeks past due is the inflection point. By this stage you need either a payment commitment with a date or a clear answer about what's blocking the invoice. The Day 14 email names the timeline explicitly and (if your contract includes it) references the late fee policy without applying it yet.
Subject: Invoice #[INV-NUMBER] — 14 days past due, requesting update Hi [CLIENT NAME], Invoice #[INV-NUMBER] for [AMOUNT] is now 14 days past due. My previous reminders may have been missed, so I want to make sure this is visible. Per our agreement, invoices unpaid past 30 days are subject to a [X%] monthly late fee. I'd like to avoid applying that and assume there's a simple processing reason for the delay. Could you confirm by [SPECIFIC DATE, 3-5 BUSINESS DAYS OUT] either (1) the payment date, or (2) the specific blocker if there is one? Thanks for getting back to me, [YOUR NAME]
Template 5 — Day +30: Formal notice
At 30 days past due, the email shifts from request to notification. The tone is still professional, but the structure changes: state the facts, name the consequences, give a final timeline. Late fees can now be applied (if your contract supports it). Most clients who haven't responded by now will respond at this stage because the consequence becomes concrete.
Subject: NOTICE — Invoice #[INV-NUMBER] past due 30 days, late fee applied Hi [CLIENT NAME], This is a formal notice regarding invoice #[INV-NUMBER] for [ORIGINAL AMOUNT], originally due [DUE DATE]. The invoice is now 30 days past due. Per our signed agreement (Section [X], or attached), a [X%] monthly late fee now applies. The updated total is [ORIGINAL AMOUNT + LATE FEE], reflected on the attached revised invoice. I need either payment in full, or a payment plan with specific dates, by [SPECIFIC DATE, 5-7 BUSINESS DAYS OUT]. If there's a dispute I'm not aware of, I'd like to discuss it directly — please reply with a time for a call this week. Thanks, [YOUR NAME]
Template 6 — Day +45: Final notice
The final-notice email serves two purposes: one more chance for the client to resolve before things get expensive, and documentation if the matter escalates to collections or small claims. Keep it short, factual, and dated.
Subject: FINAL NOTICE — Invoice #[INV-NUMBER] (45 days overdue) Hi [CLIENT NAME], This is final notice regarding invoice #[INV-NUMBER], now 45 days past due. Current outstanding balance: [AMOUNT WITH LATE FEES]. I've sent reminders on [LIST DATES OF PREVIOUS REMINDERS]. I haven't received a response or a payment commitment. If I do not receive payment in full or a documented payment plan by [SPECIFIC DATE, 7-10 BUSINESS DAYS OUT], I will pursue the matter through [collections / small claims court / legal counsel, as appropriate]. This is the last contact before that escalation. I'd much rather resolve this directly. Please reply today if you're willing to do so. [YOUR NAME]
Template 7 — Day +60: Phone-first, email as backup
By 60 days, email is the wrong primary channel. Phone the client directly first (or, if you can't reach them, escalate to a different contact at the company — typically finance, AP, or the primary contact's manager). Use the email below as a documentation backup after the call, or as the trigger for the call.
Subject: Calling tomorrow re: invoice #[INV-NUMBER] — 60 days overdue Hi [CLIENT NAME], I'm calling you tomorrow at [SPECIFIC TIME, BUSINESS HOURS] to discuss invoice #[INV-NUMBER], currently 60 days past due. If that time doesn't work, please reply with one that does today. If I can't reach you tomorrow, I'll be contacting [SECONDARY CONTACT NAME if known, or "your accounts payable team / finance department"] directly to find a path forward. [YOUR NAME]
Three tone rules every template follows
- Restate the invoice details every time. Invoice number, amount, original due date, days overdue. Never assume the recipient has the context — they receive hundreds of emails per week.
- Attach the invoice on every reminder. Even if you sent the original. Most late payments trace to a misplaced original invoice; the friction of finding it is enough to delay payment.
- Always include a specific deadline. "Please advise" is weak; "Please confirm by Friday May 30" is strong. Specific dates force specific responses.
What to do after sending each reminder
Track which reminder you sent and when, on the invoice itself. The most common cause of awkward follow-ups is sending the wrong-stage reminder because you forgot which one went last — sending a Day 1 template at Day 30 (sounds careless) or a Day 30 template at Day 1 (sounds aggressive). Most invoicing systems can log this automatically; if yours can't, a simple note on the invoice works. Clockout flags the reminder cadence on each invoice so you never send the wrong stage. For the full guide on how to follow up on unpaid invoices end-to-end, read the strategy piece.
Common mistakes to avoid
- Apologizing for sending the reminder. "Sorry to bother you about this" undermines the message. The work was done; the payment is owed; you have nothing to apologize for.
- Stacking multiple invoices in one email. Separate emails for separate invoices. Multi-invoice reminders are easier to ignore and harder for AP to process.
- Using passive voice ("the invoice has not been paid"). Direct voice works better: "I have not received payment for invoice #X." Passive voice reads as evasive in this context.
- Skipping the late fee on Day 30 if your contract specifies one. If the contract says you charge late fees and you don't, you signal that contract terms are optional. That weakens every future negotiation.