How to Follow Up on an Unpaid Invoice: 3 Emails and a Schedule for Freelancers
An unpaid invoice is uncomfortable, but following up on it is a normal part of running a freelance business. The goal isn't to sound tough or apologetic. It's to make paying you the easiest next step for the client, and to leave a clear, polite paper trail if it takes more than one message.
This guide gives you a schedule you decide before anything is late, the details every reminder needs, and three copy-paste emails (Friendly, Firm and Final) adapted from the invoice chase templates in our Client Ops Starter Kit.
The short version
- Decide your follow-up schedule before you send the invoice, so you're following a plan, not reacting to a feeling.
- Put the same four facts in every reminder: invoice number, amount, original due date and a pay link.
- Escalate one tone at a time: Friendly, then Firm, then Final.
- Ask for one clear thing: payment, or a confirmed payment date.
- Only mention next steps you will actually take, and only ones your agreement supports.
- Keep a short log of what you sent and when.
Before anything is late: set it up in writing
Most payment follow-ups get easier when the rules were written down at the start. Your scope of work or agreement should state:
- The payment terms (for example, net-15 from the invoice date) and the payment schedule (deposit, milestones, final).
- How you invoice and where the pay link comes from.
- What happens if an invoice runs late. For example: "Work may pause if any invoice is more than 10 business days past due." Use whatever policy you actually intend to follow.
Then send each invoice on the day it's due under your schedule. A reminder is much easier to write when the invoice itself was clear and on time.
If you're setting this up for a new client, our client onboarding checklist covers where payment terms and a single decision-maker fit into your kickoff, and our guide to freelance payment terms and late fee clauses has wording to adapt.
Decide the follow-up schedule up front
A simple default you can adjust to your own terms:
| Step | When to send | Tone |
|---|---|---|
| Friendly | Due date + 2 business days | Assume it slipped through the cracks |
| Firm | About 5 business days after the Friendly email | Name the days overdue and set a reply-by date |
| Final | About 5 business days after the Firm email | Facts, a final date and the next step you'll take |
Adjust the gaps to your payment terms and your client. The point is that the schedule is decided in advance, so each email is a step in a plan rather than a new decision every time.
What every follow-up should include
Each reminder should stand on its own, so the person who processes payments can act on it without digging through old threads:
- Invoice number
- Amount due
- Original due date (and, from the Firm email onward, how many days past due)
- Pay link (or clear payment instructions)
- One clear ask: pay here, or reply with a confirmed payment date
Keep it short. A long, apologetic email makes the request harder to find.
Email 1: Friendly (due date + 2 business days)
Assume good intent. Invoices get buried, approvals stall and payment runs happen on fixed days.
Subject: Quick nudge: invoice #[number] for [Project Name]
Hi [Name],
Quick nudge on invoice #[number] for $[amount], due [due date].
Pay here: [pay link]
If it's already in progress, just reply with the expected payment date and I'll note it.
Thanks,
[Your name]
Email 2: Firm (about 5 business days later)
Still polite, but specific: how late it is, and a date by which you need either payment or a confirmed payment date.
Subject: Invoice #[number] is [N] days past due: need a payment date
Hi [Name],
Invoice #[number] ($[amount]) for [Project Name] is now [N] days past due (original due date [due date]).
Please either:
1. Pay here: [pay link], or
2. Reply by [firm deadline date] with a confirmed payment date
I want to keep delivery and support on track, and a clear date helps me plan.
Thanks,
[Your name]
Email 3: Final (about 5 business days after that)
State the facts, give a final date, and name the next step you will actually take under your agreement, such as pausing remaining work or holding final files. Leave room for a written payment plan if something is genuinely blocking them.
Subject: Final notice: invoice #[number] ($[amount]) before [next step]
Hi [Name],
This is a final notice about invoice #[number] for $[amount], originally due [due date], now [N] days past due.
Pay link: [pay link]
Per our agreement, if payment isn't received (or a written payment plan confirmed) by [final deadline date], I will [next step you will actually take, e.g. pause remaining work / hold final files / close the engagement per our agreement].
If there's a blocker on your side, reply before that date and we can agree a short payment plan in writing.
[Your name]
Subject lines that say what the email is
| Step | Pattern |
|---|---|
| Friendly | Quick nudge: invoice #[number] for [Project Name] |
| Firm | Invoice #[number] is [N] days past due: need a payment date |
| Final | Final notice: invoice #[number] ($[amount]) before [next step] |
A specific subject line helps the email get routed to whoever handles payments, and it makes the thread easy to find later.
What to avoid
- Invented threats. Don't mention lawyers, collections or fees you have no intention of pursuing, or that your agreement doesn't cover. Empty threats undermine the next message.
- Late fees that aren't in your agreement. If you want late fees, put them in your terms before the work starts, and check what applies where you and your client are.
- Burying the ask. "Hope all is well, no rush, just wondering if maybe…" makes the request easy to skip.
- Changing the facts. Keep the invoice number, amount and due date identical across every email.
- Skipping steps. Jumping straight to a Final notice on day three can damage a relationship that a Friendly email would have fixed.
If they reply with a problem
A reply, even a slow one, is progress. Common situations:
- "We never got it" or "It went to the wrong person." Resend the invoice and ask who processes payments, so future invoices go straight to them.
- "We need a PO number" or "It's in the approval queue." Ask what's missing and when the next payment run is, then note the date.
- "We can't pay it all right now." Offer a short payment plan and confirm it in writing: amounts, dates and what happens to remaining work in the meantime.
Keep a simple log
A small table (in the same doc as your templates, or in your project notes) keeps you consistent and gives you a clear record:
| Date | Tone sent | Reply / outcome | Next action |
|---|---|---|---|
| Friendly | |||
| Firm | |||
| Final |
Add two more lines: whether work is paused (and from what date) and any payment plan you agreed.
FAQ
How long should I wait before following up on an unpaid invoice? A common approach is a short grace window of one to three business days after the due date, then a friendly reminder. What matters most is that you pick a window and use it every time.
Should I follow up by email or another channel? Start with email, because it creates a written record. If emails go unanswered, it's reasonable to try the channel the client normally uses with you, such as a call or a project chat, and then confirm what was agreed by email.
When can I stop work? Only when your agreement allows it, and ideally after you've said so in writing (that's what the Final email is for). If you're unsure what your agreement or local rules allow, ask a qualified professional.
Is this legal advice? No. These are business email drafts to adapt and review. Laws and payment rules vary by location. Have a qualified professional review anything you intend to rely on as binding.
Get the full sequence as a free sample
Our free sample includes the full invoice chase sequence (Friendly, Firm and Final, with the internal log) plus a proposal AI prompt, as a direct download (read it in your browser or save it as plain text) with no sign-up and no email needed.
For the rest of the client workflow, the paid kit adds a proposal template, a Scope & Extra-Work Agreement (including an extra-work approval step for scope creep), a kickoff pack, weekly updates, AI prompts and five worked examples that follow one fictional project.