When a client will not pay, first rule out a process problem, then send short written reminders on a fixed schedule, stop any new work, and send a final notice with a specific date and what happens next. If that fails, decide whether the amount is worth a formal claim or a collection agency, or whether to write it off. Most late invoices get paid at the reminder stage, as long as the reminders actually go out.
The emotional part is harder than the procedural part. Chasing money feels awkward, so people wait, and waiting is the one thing that reliably makes it worse. An invoice that is a week late is an admin problem. One that is three months late is a negotiation.
First, check it is not a process problem
A surprising share of unpaid invoices are not refusals. They are stuck. Before you assume the worst, check:
- Did the invoice reach the person who pays? Your contact may not be the person who approves payments. Ask who handles invoices and send it to them directly.
- Does it have everything their accounts team needs? Legal company names, an invoice number, a purchase order number if they use one, and your payment details in full.
- Was it in the right currency and to the right entity? An invoice to the wrong legal company can sit in a queue forever.
- Are they waiting on something from you? Some clients only release payment once a deliverable is formally accepted.
A friendly "just checking this reached the right person" fixes a lot of late payments with no awkwardness at all.
A reminder schedule that does not depend on your mood
Decide the schedule once, so you are not deciding each time whether it feels too pushy.
| When | What you send | Tone |
|---|---|---|
| Day after it is due | Short reminder with the invoice attached | Friendly, assumes it was missed |
| 7 days late | Second reminder, asks for a payment date | Polite, direct |
| 14 days late | Notice that work is paused until it is paid | Firm, factual |
| 30 days late | Final notice with a deadline and the next step | Formal, no emotion |
Every message in writing, by email, even if you also mention it on a call. If this ever goes further, the written trail is what matters.
Stop new work, but do not sabotage old work
Once an invoice is properly late, pause any further work for that client until it is paid. Say so plainly: "I am pausing work on phase two until invoice 2026-014 is settled. Happy to pick it up straight away once it is." That is a normal business response and most clients understand it.
What you should not do is break, delete or take down anything you have already delivered. Taking a live site offline or revoking access to code the client has already received can turn a debt they owe you into a claim against you, and it destroys any chance of a quiet resolution. Your contract decides what you are allowed to withhold, and that is one more reason to have one.
The final notice
Short, factual, and with a date:
Invoice 2026-014 for $2,400 was due on 3 October and is now 30 days overdue. I have sent reminders on 4, 10 and 17 October. Please pay the full amount by 14 November. If I have not received payment or heard from you about a payment date by then, I will pass this to a collection agency [or: start a claim]. I would much rather resolve it directly.
Only name a next step you are actually prepared to take. An empty threat teaches the client that your deadlines are negotiable.
The formal options
If the final notice does not work, there are a few routes. Which ones exist and how they work depends on where you and the client are.
- A small claims process. Many countries have a simplified court process for smaller debts that does not need a lawyer. It works best when you and the client are in the same country.
- A collection agency. They chase on your behalf and usually take a percentage of what they recover. Often more effective than another email from you, because the tone changes.
- A lawyer's letter. A formal demand from a lawyer is relatively cheap and often enough on its own.
- The platform's dispute process. If the work went through a marketplace, use their process first. It is usually the fastest route, and it is one argument for keeping work with new clients on a platform at the start.
Across borders, formal routes get expensive quickly. For a client in another country, the realistic choice is often between a collection agency and writing it off.
Decide whether it is worth it
Put a number on your time. If chasing a $300 invoice through a formal process takes twenty hours, you have paid to collect it. Sometimes writing it off, saying so clearly, and moving on is the correct business decision, and it frees up the attention you need for clients who do pay.
That is not the same as letting it go quietly. Send a last message saying the invoice remains unpaid and that you will not be working together again. Then stop.
Set up the next project so this cannot happen twice
Non-payment is much easier to prevent than to fix:
- Take a deposit. Something up front before work starts. A client who will not pay a deposit is telling you something.
- Bill in milestones. Never let the unpaid amount grow larger than you can afford to lose. How to structure milestone payments covers how to split a project.
- Transfer ownership on final payment. Have the contract say the code and rights pass to the client when they have paid in full. What to put in a contract with a freelance developer covers that clause from the client's side.
- Invoice on the day. Late invoices get paid late. What to put on a freelance invoice has the checklist.
- Use short payment terms. 7 or 14 days is reasonable for freelance work.
None of this is about distrust. It is about structuring the work so that one bad client costs you a fortnight rather than a quarter.