Send a dated written notice first, then escalate to a payment-processor dispute, platform arbitration or small claims depending on where your client is registered. Every route is slow because each needs a third party to act. The durable fix is delivering code that will not run until the invoice clears.
You sent the fourth follow-up yesterday. It was read. Nothing came back.
The site you built is live. It is taking their orders right now, on their domain, earning them money. And the invoice attached to it has been sitting unpaid for six weeks.
A client not paying after delivery is the most common way freelance work goes wrong, and it rarely looks dramatic from the outside. This page covers what you can still do about that invoice, honestly, including the cases where the honest answer is that you will not get the money. Then it covers the thing nobody tells you about why it got this hard.
What to do first about a client not paying
Start with the unglamorous steps. They resolve more invoices than the dramatic ones, and they cost you nothing but an hour.
Send a final written notice with a deadline. Not another chase — a notice. State the amount owed, the work delivered, the agreed terms, and a specific date. Keep the tone flat and unemotional. A meaningful share of non-payers settle at exactly this point, because the change in register tells them the informal phase has ended and you are keeping records.
Put it in writing even if every previous conversation happened on a call or in chat. If this ever reaches a formal process, the written trail is the thing that carries weight, and reconstructing it later is painful.
If the notice goes unanswered, your options narrow. They also change depending on where your client is registered, which matters more than where you are.
The recovery routes that actually exist
| Route | Best when | Realistic cost |
|---|---|---|
| Payment processor dispute | They paid a deposit by card | Free, but time-limited |
| Platform arbitration | Work came through a marketplace | Free, platform takes a view |
| Small claims | Domestic client, modest sum | Filing fee plus weeks of waiting |
| Formal legal notice | Larger invoice, local client | A few hundred, often less than the debt |
A payment processor dispute is worth checking first if any money changed hands by card. Processors hold leverage over merchants that you simply do not have, and the process costs you nothing. The catch is the window: most schemes expire a few months after the transaction, so this route closes quietly while you are still sending polite reminders.
Platform arbitration is the fastest option when the work came through a marketplace, because the platform can freeze funds and has its own reasons to resolve disputes.
Small claims is genuinely accessible in many places and designed for people without lawyers. It is also slow, and it assumes your client is somewhere you can practically reach.
The signs that show up before the silence
Most non-payment is visible days before it happens, if you know what you are looking at. Reading the pattern will not save the current invoice, but it will change how you handle the next contract.
- Scope grows while payment terms stay vague. New requests keep arriving, but questions about the invoice get shorter answers.
- The decision-maker stops appearing. You start dealing only with someone who cannot authorise a payment.
- They ask for the deliverable before the milestone closes. Often framed as urgency, a deadline, or a demo for somebody senior.
- Praise replaces process. Warm feedback, no purchase order, no date.
None of these prove bad intent. Plenty of clients do all four and pay on time. They are useful because they tell you when to tighten delivery terms rather than when to panic.
What if they pay part of it?
Partial payment is the hardest case, because it feels like progress while quietly weakening your position. Accepting a payment marked as settlement in full can close the debt, even when the number is lower than you agreed.
If you accept partial payment, say in writing that you are applying it against the outstanding balance and that the remainder is still due. One sentence is enough, and it keeps the debt alive.
Why chasing so rarely works
Look at that table again and you will notice what every row shares.
Each one requires somebody else to decide to act. A processor, a platform, a court, or the client. You are asking a third party to compel a person who has already chosen not to pay you, and that is a slow and uncertain position to argue from. Your client understands this better than you do. It is the reason the replies got shorter and then stopped.
There is also arithmetic that nobody enjoys. For a smaller invoice, the filing fees, the paperwork and the weeks of waiting can cost more than the amount you are chasing. That is the real reason so much freelance work gets written off rather than pursued. Not laziness, and not a lack of nerve. It is a rational response to a bad position.
But there is one option that is not on that table at all, and it is not a recovery route.
The same six weeks, two versions
The moment your leverage disappeared
Go back to the day you delivered.
You handed over working code. Not a demo, not a staging link behind a password — the real thing, deployed and running on infrastructure they control. At that exact moment the transaction completed for them and stayed open for you.
Everything after that follows from it. The ignored emails, the deadline that slipped, the apologetic excuses that stopped arriving. None of that is really a character problem with your client, however much it feels like one. It is structural. You gave away the only thing you had that they wanted, before the money arrived, and no email you write afterwards can put it back.
This is the part most advice skips. It tells you to write firmer emails and use better contracts, which treats the symptom. The real reason you have no leverage is that leverage was handed over on delivery day, and it was handed over by the delivery model rather than by you.
What the same six weeks look like the other way
Change exactly one thing about that day. Not the client. Not the contract, not your follow-up technique, not your rates. Only whether the code you delivered runs unconditionally.
Everything else in the story stays the same, including the client going quiet.
How do you stop this happening with the next client?
You cannot fix the invoice that is already outstanding by changing how you deliver. That money is subject to the routes above, and you should work them.
What you can change is the position you are in next time. Payment-gated delivery means the client receives everything — every file, every folder, the complete project — but the code only runs while you authorise it. An unpaid invoice shows a payment screen on their site instead of the homepage. Nothing is broken into and nothing is taken back, because unconditional access was never granted in the first place.
That distinction matters legally as well as practically. Interfering with a system you no longer control is a different act from never handing over unconditional access. DevAegis does the second one, configured before you deliver.
If you want the mechanics, the user guide walks through it, and the pricing page is short.
Frequently asked questions
The questions below come up most often. They are answered in full underneath.
Key takeaways
- A dated written notice settles more unpaid invoices than another follow-up email does.
- Card disputes expire within months, so that route closes while you are still chasing politely.
- Every recovery route depends on a third party choosing to act on your behalf.
- For smaller invoices, formal recovery often costs more than the invoice is worth.
- Leverage is lost the moment working code runs unconditionally on the client's own servers.
Frequently asked questions
Straight answers to what people ask about client not paying.
You probably cannot fix this one. You can make sure it is the last.
The reason this invoice is hard to recover is that the code was working on their server before the money arrived. DevAegis moves payment in front of that moment, so the next client never gets the same position.
Protect your next delivery
