Freelance guide
How to Follow Up on an Unpaid Invoice — Email Templates and Escalation Steps
A client who hasn’t paid isn’t always a client who won’t pay. Most late invoices are resolved by a professional, structured follow-up before any formal action is needed. This guide gives you three ready-to-send email templates, a clear escalation path when they don’t work, and the documentation habits that protect you if the matter goes further.
- Why invoices go unpaid
- Stage 1: Friendly reminder
- Stage 2: Firm follow-up
- Stage 3: Final notice
- Escalation options
- Building your paper trail
- How to prevent late payment
- FAQ
Why invoices go unpaid — and what it tells you
Before you send a follow-up, it is worth distinguishing the likely cause. The response you get to your first email tells you which situation you are in, and the approach differs for each.
| Likely cause | Signal | Approach |
|---|---|---|
| Invoice went to spam or was missed | Client responds apologetically and pays quickly | Friendly reminder resolves it |
| Waiting for internal approval | Client acknowledges but cites an internal process | Firm follow-up with a specific date; offer to re-address the invoice if needed |
| Cash flow problem | Client acknowledges but asks for time | Negotiate a payment plan in writing; get part-payment now |
| Disputed work quality | Client raises issues they have not mentioned before | Address the dispute in writing; reference the acceptance criteria in your contract or SOW |
| Deliberate non-payment | No response or repeated empty promises; escalation follows | Three-stage sequence then formal escalation |
The three-stage sequence below assumes the client has not responded substantively. If they respond and raise a dispute, address it in writing before resuming the payment chase — a disputed invoice is a different problem from a late one.
Stage 1: Friendly reminder (1–3 days after due date)
Send this the day after the due date, or within 2–3 days. The tone is professional and assumes an oversight on either side — not a deliberate non-payment. Most late invoices are resolved here.
Friendly reminder
Subject: Invoice [#001] — payment reminder
Hi [Name],
Just a quick note to flag that invoice [#001] for [amount],
covering [project name / deliverable], was due on [date].
If this has already been sent, please ignore — bank transfers
can take a few days to show. If not, I’ve attached the invoice
again for convenience.
Please let me know if you have any questions.
[Your name]
Attach the original invoice PDF. Do not add a late fee at this stage unless your contract specifies an immediate penalty — doing so before the client has had a chance to respond creates unnecessary friction.
Stage 2: Firm follow-up (7–10 days after due date)
If Stage 1 produced no payment and no substantive response after a week, send a firmer follow-up. The tone remains professional but makes the situation clear: the invoice is overdue, you need a confirmed payment date, and you are noting the late payment.
Firm follow-up
Subject: Invoice [#001] — now [X] days overdue
Hi [Name],
Invoice [#001] for [amount] was due on [date] and remains
unpaid. I sent a reminder on [date of Stage 1 email].
Could you confirm when payment will be processed? If there is a
problem with the invoice or an internal approval step I can help
with, please let me know.
[If your contract includes a late fee clause:]
As noted in our agreement, a late payment charge of 1.5% per month
applies to balances unpaid after the due date. I have not applied
this yet and am happy to waive it if payment is received by
[date 7 days from now].
I have attached the invoice again for reference.
[Your name]
If the client responds with a specific payment date, get it in writing and hold them to it. If they ask for a payment plan, agree to it in a brief email and ask for part-payment now to confirm good faith. Do not agree verbally only — the written record matters.
Stage 3: Final notice (14–21 days after due date)
Stage 3 is a formal notice before you pursue legal or collections remedies. The tone is direct and states consequences. Send it to the client’s main contact and, if you have it, to their accounts payable or finance team directly.
Final notice before escalation
Subject: FINAL NOTICE — Invoice [#001] — payment required
by [date 7 days from now]
Hi [Name],
This is a formal notice that invoice [#001] for [amount],
originally due [date], remains unpaid despite reminders
sent on [Stage 1 date] and [Stage 2 date].
The total now owed, including the late payment charge per our
agreement, is [updated amount].
If payment in full is not received by [date 7 days from now],
I will have no option but to pursue recovery through
[small claims court / a solicitor’s letter / a debt collection
referral] without further notice.
Please confirm receipt of this notice.
[Your name]
Send this by email and, for higher-value invoices, also by recorded post to the client’s registered address. The combination creates an unambiguous record of delivery that courts and collections agencies recognise.
Escalation options
If Stage 3 produces no payment, you have four main options. The right one depends on the amount, the jurisdiction, and whether you want to preserve any chance of a future working relationship.
| Option | Best for | Typical cost | Time |
|---|---|---|---|
| Small claims court | Amounts under the local limit (£10K UK, $5K–$25K US by state, €5K–€20K EU); undisputed work | Filing fee: £35–£455 UK / $30–$400 US depending on amount; no lawyer needed | Hearing typically within 4–12 weeks |
| Solicitor’s letter / lawyer’s letter | Higher amounts; clients who have been unresponsive but are solvent | £150–£400 / $200–$500 for a standard letter before action | 1–2 weeks to receive; often prompts payment immediately |
| Collections agency | Debts 60+ days old; no ongoing relationship at stake | 15–35% of recovered amount; no upfront fee for most agencies | Variable; typically 30–90 days for B2B debt |
| Mediation | Disputed invoices where you want to preserve a long-term relationship | £200–£600 / $300–$800 for a half-day session | 2–6 weeks to arrange |
For most freelance invoices under £5,000 / $5,000, small claims court is the most cost-effective first escalation step. Filing fee is low, no lawyer is needed for straightforward payment disputes, and the process is designed for individuals. Bring your invoice, the signed contract or SOW, and printed copies of all follow-up emails.
Building your paper trail as you go
Courts, collections agencies, and solicitors all want the same thing: a chronological record showing that the work was agreed to, delivered, and invoiced, and that you made repeated reasonable attempts to collect. Build this automatically by following a few habits on every project.
- Always send invoices by email, not just as a file share link. An email to the client with the invoice PDF attached creates a timestamped record of delivery. A link in a project management tool does not create the same kind of record outside the platform.
- Reference the contract or SOW on every invoice. A line in the Notes field (“Per Statement of Work dated [date]”) ties the invoice to the agreed deliverables. This closes off “I never agreed to this amount” as a defence.
- Keep every follow-up in a single email thread. Replies in the same thread create a chronological record showing the invoice date, each follow-up, and any response. Avoid switching to phone calls or project tools for the payment conversation — or, if you do, follow up the call with a brief written summary of what was discussed.
- Export your invoice PDF at the time you send it. Do not regenerate it later with different figures. The invoice PDF you send should match exactly what you’ll show a court. InvoiceQuick lets you download a clean, consistent PDF at the point of sending — save a copy as soon as you generate it.
- Record any payment commitment in writing. If a client says on a call that they will pay by a specific date, send a brief email: “Thanks for confirming — I’ll expect payment by [date].” Their failure to correct it is effectively written confirmation of the commitment.
Create my invoice with InvoiceQuick →
Generate a clean, professional invoice PDF you can attach to any of the templates above — no signup, works in your browser.
How to prevent late payment on future projects
The most reliable protection against late payment is not in the follow-up — it is in the contract and the invoicing structure you set up before work begins.
- Require a deposit. A client who has paid 25–50% upfront is a client who is financially committed to the project. The deposit is also your signal to start — without it, you have not confirmed the client has budget. See the statement of work guide for a deposit invoice structure tied to project milestones.
- Write a late payment clause into your contract. State the rate (1.5%/month is standard) and the trigger (the original due date). A visible late payment clause in the freelance contract changes client behaviour more than any follow-up email will.
- Use specific due dates, not “NET 30.” An invoice that says “Due: 5 October 2026” is more likely to be paid on time than one that says “NET 30.” Accounts payable teams schedule specific dates; “NET 30” introduces ambiguity about when the clock started.
- Invoice promptly at each milestone. Waiting a week after delivering work to send the invoice signals that the payment is not urgent. Send the invoice the same day you deliver the milestone or obtain acceptance.
- Consider shorter payment terms for new clients. “NET 14” on first projects and “NET 30” for established clients is a reasonable graduated approach. New clients have not yet demonstrated payment reliability; a shorter window is a reasonable ask before extending longer terms.
Also read:
- How to write a freelance contract — late payment clauses, kill fees, and IP-on-payment language →
- Statement of work template — milestone payment schedule and acceptance criteria →
- How to send an invoice by email — subject lines, follow-up cadence, and vendor portals →
Frequently asked questions
What should I do if the client ignores all three follow-up emails?
After three unanswered emails, move to a phone call or video call. A direct conversation sometimes uncovers a genuine problem — invoice lost in spam, internal approval hold, cash-flow issue — that email alone would not reveal. After the call, follow up in writing with a summary of any commitment made. If that also produces no result, send a final letter of demand stating a 7-day payment deadline before you pursue formal remedies (small claims, solicitor’s letter, or collections).
Can I charge late payment interest on an overdue invoice?
Only if your original invoice or contract specifies a late payment rate. Without such a clause, adding interest unilaterally is unlikely to be enforceable. For future projects, add a late payment clause to your freelance contract or SOW before work starts and reference it on every invoice. Most clients pay on time simply because the clause is visible — it is more prevention than enforcement.
Can I withhold deliverables or suspend work until the client pays?
Only if your contract gives you that right. A clause stating that IP ownership transfers upon payment in full, and that you may suspend services for unpaid invoices, is standard in freelance contracts and gives you a practical mechanism. Without it, withholding deliverables may itself breach the agreement. Include IP-on-payment and suspension-for-non-payment clauses in every new client contract before starting work.
Should I call the client instead of emailing?
Email creates a paper trail; phone calls do not. For the first two stages, email is preferable: it documents the date of each follow-up, the amount, and any response. After two or three unanswered emails, a call is worth making — it is harder to ignore. After any call, send a brief written summary: “Following our call today, you confirmed payment will be processed by [date].” This converts the verbal commitment to a written record.
When should I consider small claims court?
Small claims court is practical for undisputed work at amounts under roughly £10,000 (England and Wales), $5,000–$25,000 (US, varies by state), or €5,000–€20,000 (EU, varies by country). The process is designed for individuals without legal representation: you submit a claim form, pay a modest filing fee, and attend a hearing. Bring your invoice, signed contract or SOW, and copies of all follow-up emails. For undisputed payment cases, success rates for claimants are high.
When should I use a debt collection agency?
Collections agencies are most useful for debts 60 or more days overdue where direct follow-up has produced no response. They take a percentage of the recovered amount (typically 15–35%), so they are less attractive for small invoices. The main trade-off: a collections referral typically ends the working relationship. For amounts under £5,000 or $5,000 where you have not yet tried small claims court, filing a claim yourself is usually faster and cheaper than a collections referral.
How do I prevent late payment on future projects?
The most effective steps: require a deposit before starting; include a late payment clause in your contract or SOW; use specific due dates (not “NET 30”); invoice at each milestone the same day you deliver, not days later; and keep payment terms short for new clients (NET 14) until you have established their payment reliability. A deposit invoice is the single most effective prevention tool — it confirms the client has budget before you allocate time to the project.
More free tools for freelancers
If you are chasing a late invoice, you are already in the follow-up phase. These tools help earlier in the workflow — before the first invoice goes out.
Generate a GDPR & CCPA-aware privacy policy, terms of service, and cookie-consent notice for your freelance business website — free, in your browser.
ADA & privacy risk ShipSafeScan a URL for the accessibility and privacy gaps that get sites sued — useful before handing over a web project to a client.
Security headers HardenCheckCheck a live site’s HTTP security headers before client handover — enterprise buyers routinely run this scan before accepting delivery.
Secret scanning LeakCheckPaste code or a config file and see exposed API keys flagged before they reach your repo or client’s codebase.