Late Payment Recovery Kit
Ready-to-send scripts for Late Payment Recovery - copy, adjust the details, send.
Sending the invoice was never the hard part. The silence afterwards is.
A week passes. Then two. You do not want to seem desperate, or damage a relationship you depend on, so you say nothing - and the longer you say nothing, the harder the first message becomes to write. Meanwhile the money is yours, the work is done, and you are the one feeling awkward about it.
This kit is the escalation ladder, written out: eight messages that take you from a friendly nudge to a formal final notice, each one calibrated so you never skip a rung or overreact. Plus a tracker so you always know which invoice is at which stage.
How the two parts work together
- The scripts (this document) - the exact wording for each stage, from the day after the due date through to the last message before formal action.
- The Payment Tracker (companion CSV) - one row per invoice: client, amount, due date, which stage you are at, and when you last chased. When a date passes, the tracker tells you which script is next.
Used together: no invoice quietly ages past the point of recovery, and no awkward silence because you could not decide what to write.
Why this exists
Almost every freelancer escalates too slowly and then too suddenly. Weeks of silence, then a message with an implied threat in it, which damages the relationship far more than steady, unremarkable follow-up would have.
The fix is not being tougher. It is having each rung of the ladder written in advance, so following up feels like process rather than confrontation - to you and to them.
Why not just ask an AI to write this?
You could, and the wording would be fine. What you are paying for is not having to decide which stage you are at while irritated and slightly anxious about the money - and having the tone already calibrated so message three is firmer than message two without being a threat. That judgement is what is packaged here, plus the tracker so the ladder is actually followed.
Who this isn't for
- You work through an agency or platform that handles collections.
- Your invoices are large enough that a debt-recovery firm or solicitor is the right first call - these scripts are for the ordinary case where the money is recoverable and the relationship is worth keeping.
1. The day after the due date
Send this without hesitation. Sending it immediately is what makes every later message easier - it establishes that you notice, quietly.
Hi [name] - just a quick check that invoice [number] for [amount] reached you okay. It was due yesterday. Let me know if you need anything from my side to get it processed.
2. One week overdue
Still friendly, but now with the date named explicitly.
Hi [name] - following up on invoice [number] for [amount], now a week past its due date of [date]. Could you let me know when I can expect it? Happy to resend the invoice if it's easier.
3. Two weeks overdue - ask for a date, not a status
The shift here matters: stop asking whether it will be paid and start asking when. A question with a date in it is much harder to leave unanswered.
Hi [name] - invoice [number] for [amount] is now two weeks overdue. I'd rather not keep chasing, so could you give me a specific date it will be paid? If there's a hold-up on your side, tell me what it is and we'll sort it out.
4. When they go completely silent
Two ignored messages is a pattern. Name it plainly, without accusation.
Hi [name] - I've not heard back on invoice [number] for [amount], now [X] weeks overdue. I want to assume this is an oversight rather than anything else, so I'm flagging it clearly: the work was delivered on [date] and payment is outstanding. Can you confirm receipt of this message and give me a payment date?
5. Pausing further work
Use this when there is ongoing work. Say it as a consequence, not a punishment.
Hi [name] - since invoice [number] is still outstanding at [X] weeks, I'm going to pause work on [current project] until it's settled. Not a decision I enjoy, but I can't carry unpaid work forward. Everything is ready to pick up again the moment payment clears.
6. When the client says cash flow is tight
Believe them, and get a structure anyway. Vague sympathy leaves you in the same place next month.
Thanks for being straight with me - I'd rather know. Let's put something in writing so we both know where we stand: could you pay [amount] by [date] and the balance by [date]? If those dates don't work, propose ones that do and I'll work with them.
7. The final notice before formal action
Formal, unemotional, specific. No threats, just the next step stated as fact.
Hi [name] - invoice [number] for [amount] is now [X] days overdue, despite several reminders on [dates]. If payment or a firm payment date isn't received by [date, at least 7 days out], I'll begin formal recovery. I'd much rather resolve this directly - the account can be settled at any point before then.
8. After it is paid, if the relationship continues
Do not skip this one. Reset the terms while goodwill is fresh.
Thanks [name], received - appreciated. So we avoid this next time, I'm moving to [50% upfront / payment on delivery / 14-day terms] on future work. Nothing personal in it; it's how I keep things predictable on my side.
A short checklist for using these
- Send message 1 the day after the due date, every time, without deciding whether to. Deciding is what causes the delay.
- Never send two rungs in the same week - the escalation only works if the gaps are visible.
- Put every promised date in writing, including ones given on a call.
- Keep the tone identical throughout. Firmness comes from the content and the timeline, never from the adjectives.
Where to go deeper
- Check whether your jurisdiction gives you a statutory right to interest and recovery costs on late commercial payment - many do, and simply mentioning it factually in message 7 changes the response rate.
- If late payment is routine rather than occasional, the problem is usually the terms rather than the chasing: deposits, milestone billing, or shorter payment windows fix upstream what these scripts fix downstream.