The 3-Email Sequence for Overdue Invoices (Polite, Then Firm)

The invoice was due ten days ago. You've opened the compose window four times, written "Hi, just checking in on—", and closed it again. Too soft and you'll be chasing this for another month. Too hard and you might torch a relationship worth ten more invoices.

Here's what most freelancers get wrong about payment chasing: they treat it as one awkward email, when it's actually a sequence — and the sequence works precisely because it starts early and calm, not late and angry.

Why sequences beat single emails

A single reminder carries all your frustration in one message, usually sent after you've stewed for three weeks. A sequence distributes the pressure: the first touch assumes innocence (and is usually right — most late payments are oversights, lost approvals, or a PO stuck in someone's inbox). The second touch is direct. The third is formal. Each message escalates the register while staying professional, and because you wrote all three on day one — before you were annoyed — none of them sound bitter.

The other advantage: a sequence removes the decision fatigue. You're not deciding each week whether today's the day to be firm. The calendar decides.

The three emails

Email 1 — the day it goes overdue. One sentence, friendly, assumes oversight. "Hi Dana — flagging that invoice #214 came due yesterday; here's the link in case it slipped through." That's it. Sent on day one, this email does more work than any strongly-worded letter sent on day thirty, because it signals — gently — that you notice, and that you track.

Email 2 — five business days later. Direct but warm. Reference the contract terms. Ask if something is stuck on their end — approvals, PO numbers, a finance process — and offer to help unstick it. This reframing matters: you're not accusing, you're troubleshooting a shared problem. Most stuck payments come loose right here.

Email 3 — ten business days after that. Formal. State the late fee taking effect (if your contract has one) and the date you'll pause active work per your agreement. No threats, no apology for asking. You should sound like someone who expects to be paid — because you are.

The prompt that writes all three

Write a 3-email follow-up sequence for an overdue invoice.

Context: Invoice #[X] for [amount], due [date], now [N] days overdue.
Client relationship: [good / neutral / strained].
Payment terms in contract: [e.g., net 15, 2% monthly late fee].

Email 1 (send now): friendly assumption of oversight. One sentence.
Include invoice link.
Email 2 (send +5 business days): direct but warm. Reference the contract
terms. Ask if there's an issue on their end.
Email 3 (send +10 business days): firm and formal. State the late fee
taking effect and the date I will pause active work per our agreement.
Still professional — no threats, no apology for asking.

Keep each email under 90 words. I should sound like someone who expects
to be paid, not someone asking a favor.

Paste it into ChatGPT, Claude, or Gemini. Adjust the relationship variable honestly — the tone calibration between "good" and "strained" is real, and it's the thing the AI does better than an irritated human at 11pm.

Two rules that keep the sequence safe

Never claim contract terms you don't have. Before email 3 goes anywhere, open your actual contract and confirm it says what you're about to say it says. If there's no late-fee clause, email 3 leans on pausing work instead — and your next contract gets a late-fee clause. The sequence is only as strong as the paper behind it.

Write for the forward. Assume every email might be forwarded to their finance team, their boss, or — in the worst case — read aloud in a small-claims hearing. The test for every line: could this be forwarded without embarrassing anyone, including you? Firm passes that test. Sarcastic doesn't.

What if the sequence runs out?

If all three emails produce silence, you've left reminder territory and entered escalation territory — a formal demand letter addressed to accounts payable, with the full paper trail attached, and a stated next step you're actually prepared to take. That's a different document with different rules (chief among them: never threaten an action you won't follow through on). But here's the encouraging statistic from my own tracking: sequences that start on day one almost never get there. It's the chases that start on day twenty-five that end in demand letters.

Start early. Stay calm. Let the calendar do the escalating.

This is workflow #21 of 30 in The Freelancer's AI Operations Kit — the free sample includes it, along with the weekly status update and proposal workflows. Download the free sample