# The Invoice Follow-Up Sequence: What to Send on Day 0, 7, 14, and 30

A complete follow-up schedule for unpaid invoices: what to send at each stage, why the cadence matters more than the wording, and how to run it without thinking.

Category: templates  
Last updated: 2026-07-07  
Source: https://getdunpilot.com/templates/invoice-follow-up-sequence

---

**The short version:** the sequence beats the sentence. Any reasonable wording works if it arrives on a fixed schedule that never skips a step, because what clients actually learn is whether your invoices can age quietly. Here's the full ladder; each stage links to a copy-paste template.

## The ladder at a glance

| Day | Message | Tone | Goal |
|-----|---------|------|------|
| 0 (due date) | Friendly nudge | Warm | Solve forgetfulness |
| +7 | Firm follow-up | Direct | Get a payment *date* |
| +14/21 | Formal notice | Businesslike | Invoke terms & late fees |
| +30 | Final notice | Consequential | Deadline + consequence |

Full email text for every stage: [payment reminder templates](/templates/payment-reminder-emails) · final stage variants: [final notice templates](/templates/final-notice-email).

## Day 0: the nudge most freelancers skip

Sending a reminder *on the due date* feels premature to most freelancers, which is exactly why it works: it establishes that your invoices are tracked. Most late payments are [forgetfulness, not refusal](/blog/why-freelancers-get-paid-late), and this single email prevents the majority of them.

## Day 7: ask for a date, not for money

The firm follow-up has one job: convert silence into a commitment. "When will payment go out?" forces a reply like "Friday", and a dated promise changes everything downstream. If Friday passes unpaid, your next message isn't a nag, it's an accountability note: *"You mentioned Friday. It hasn't arrived."* Track every promise; broken ones are your strongest polite leverage.

## Day 14-21: structure does the escalating

Same facts, formal packaging: notice format, invoice terms cited, late fees mentioned **only if they're in your agreed terms** (wording help: your contract's late-fee clause, at 1-1.5%/month, is standard practice). The tone shift comes from the format; you never have to sound angry.

## Day 30: final notice, then follow through

Hard date, concrete consequence (work stoppage, collections), one last payment link. The cardinal rule: **never send a "final" notice twice.** Details and both variants, including the "my accountant handles this now" version that freelancers swear by, are in the [final notice templates](/templates/final-notice-email).

## Why sequences fail in real life

Nobody forgets to send day-0. They forget day-7, because they're mid-project, because checking who-owes-what means opening a spreadsheet, because the awkwardness compounds. The sequence's power is consistency, and consistency is precisely what humans are bad at while juggling client work.

That's the entire reason [DunPilot](/) exists: it watches every unpaid invoice, drafts each stage in the right tone for that specific client's payment history, pauses when a client promises a date, and resumes the moment the promise breaks. You approve each email; the ladder never skips a rung.


## Frequently asked questions

### How often should I follow up on an unpaid invoice?

On a fixed ladder: a friendly reminder at the due date, a firm follow-up at +7 days, a formal notice at +14 to +21, and a final notice at +30. Consistency matters more than exact intervals.

### How many payment reminders should I send before escalating?

Two reminders (due date and +7) before shifting to formal notices. More than that teaches clients that your reminders are background noise.


Written by DunPilot. DunPilot chases your overdue invoices and measures which reminder brought the money in. Paste rows, upload a CSV or an invoice PDF, or sync Stripe on Pro.