Client Will Not Pay the Final Invoice for Their Website: What to Do, in Order, Without Hostage Tactics

The site is built. The client approved it, maybe it is even live, and the final invoice is now two, four or eight weeks overdue. Your emails get no reply, or a vague “we will sort it next week” that never happens. You are tempted to change a password, take the site down or hang on to the domain until they pay.

Do not do that. It feels like leverage, but it usually turns a debt you are owed into a dispute you can lose, and in many places it can expose you to legal claims of your own. This guide walks through what experienced freelancers and small agencies do instead, in order: check your own paperwork, chase politely, find out what is really going on, offer a way to pay, pause new work, send a formal final notice, and then use small claims, mediation or a collections service if you have to.

This is practical guidance, not legal advice. Contract, debt collection and computer misuse laws differ by country, state and province. For a large amount, or if the client threatens you, talk to a lawyer licensed where you work.

What is usually going on

Most unpaid invoices are not fraud. The usual causes are:

• Admin failure. The invoice went to someone who left, landed in spam, needs a purchase order number, or is waiting in an accounts payable queue.
• Cash flow. The client wants to pay but cannot right now and is embarrassed to say so.
• Quiet dissatisfaction. Something about the project bothers them (a missed feature, a bug, a delay) and not paying is how they are expressing it.
• A genuine scope dispute. They believe the price included something you believe was extra.
• Bad faith. Rare, but it happens.

Each needs a different response, so your first job is to find out which one you are dealing with. Assume the kindest explanation until the client proves otherwise. It keeps the tone right and it keeps your written record clean.

Step 1: Check your own paperwork first

Before you chase, read what you actually agreed. Find the proposal, the contract or terms, any change requests, and the invoice itself, and answer these questions:

• What are the payment terms? Due on receipt, 14 days, 30 days? Is the date on the invoice correct?
• Does the contract say when ownership of the site, design and code passes to the client (for example, on payment in full)?
• Did you agree late fees or interest? Only charge what the contract or local law allows.
• Was the final payment tied to a milestone (launch, sign-off) that has actually happened?
• Is the invoice addressed to the right legal entity and person, with any reference number they asked for?
• Did every extra item go through a written change request, or did some get agreed in passing?

If you find a weakness (no written contract, extras agreed by phone), that does not mean you cannot collect. It means you should be extra polite and specific, and fix the process for next time.

Some places give freelancers specific protections. For example, New York State and New York City have “Freelance Isn’t Free” laws that require a written contract for many freelance engagements above a set value and set a default payment deadline when the contract does not name one. The UK and EU have statutory late payment interest schemes for business to business debts. Rules and amounts change, so look up what applies where you and your client are based.

Step 2: Chase politely, on a schedule

A friendly, predictable sequence collects most overdue invoices. Put it in your calendar so you do not depend on remembering or on your mood.

When	What to send	Tone
A few days before the due date	A short reminder with the invoice attached and a payment link	Helpful, routine
The day after it is due	“Just checking this reached the right person”	Friendly, assumes an admin slip
About 7 days overdue	Reminder plus a direct question: is anything holding this up?	Warm, direct
About 14 days overdue	Ask for a call, or a payment date, and mention any agreed late fee	Polite, firmer
About 30 days overdue	Pause new work (Step 5) and set a date for a final notice	Calm, businesslike

A reminder you can adapt: “Hi [name], a quick note that invoice [number] for [amount], for the [project] website, was due on [date]. I have attached it again in case it went astray, and you can pay at [link]. If anything is holding it up, a question about the work or an accounts process I need to follow, just let me know and I will sort it out.”

Track each overdue invoice with a status and the date it last moved (sent, reminded, promised, part paid). If nothing has changed for a week, that is your cue for the next step, not a reason to wait and hope. The same habit works earlier in the project: content or approvals stuck “waiting on client” for more than a week deserve a polite nudge, because a project that drags is a project whose final invoice gets disputed.

Keep every message in writing, even if you also talk. After any call, send a two line email confirming what was agreed. Try a different channel and a different person if one goes silent: the business owner, an office manager, or the accounts email on their own website.

Step 3: Find out the real reason, and fix what is genuinely yours

Once you get a reply, listen for which of the causes above you are dealing with.

• If something is genuinely unfinished or broken, fix it fast and ask for written sign-off. Do not argue the point while a real bug sits on the site.
• If they dispute part of the invoice, separate the disputed amount from the undisputed amount. Ask them to pay the undisputed part now while you discuss the rest. This is reasonable and often unblocks things.
• If it is a scope disagreement, go back to the proposal and any change requests. Be willing to compromise on a small item to get the bulk paid; a partial discount costs less than months of chasing.
• If they say they are unhappy but cannot say why, ask for a short call with a specific question: “What would need to be true for you to feel the project is complete?” Write down the answer and agree it in an email.

Step 4: Offer a payment plan

If the problem is cash flow, a plan gets you paid. Put it in writing with:

• The total owed, the number of payments, the amount and the date of each.
• How they pay (a payment link or automatic card payments reduce missed payments).
• What happens if a payment is missed: the full balance becomes due, and any late fee in your contract applies.
• That handover of anything still pending (Step 5) happens on the final payment.

Ask for a first payment straight away. It shows good faith and gets money moving.

Step 5: What you may and may not withhold

This is the part that gets designers into trouble. The rule of thumb: you can stop giving more, but you must not take back or disable what the client already has, and you must never touch accounts that belong to the client.

Usually reasonable, if your contract supports it	Do not do this
Pause new work, change requests and support until the account is current	Take down, suspend or deface a live site to force payment
Hold off launching a site that still lives only on your own staging server or account	Change passwords on, or remove the client from, their hosting, registrar, email, analytics or WordPress
Hold back unpaid deliverables not yet handed over, such as source design files, if the contract says ownership passes on payment	Refuse to release, transfer or renew a domain registered in the client’s name, or let it lapse on purpose
Withhold a license key you bought and pay for yourself, for future updates, if the contract says licenses are provided on payment	Insert a kill switch, time bomb, back door or code that disables the site later
Charge late fees or interest that the contract or local law allows	Publish the client’s name, post about them on social media, or contact their customers
Decline future projects with this client	Delete their content or backups

Why the right hand column is off limits:

• Legal exposure. Accessing or changing a computer system without authorization is a crime in many jurisdictions (for example under computer misuse or computer fraud laws), and a hidden kill switch or a password change on an account you were trusted with can fit that description even if you built the site. Damaging the client’s business can also give them a claim against you that is larger than your invoice.
• It makes you the wrongdoer. A judge, mediator or registrar who sees that you took a site offline will be far less sympathetic to your unpaid invoice.
• It hurts people who owe you nothing: the client’s customers and staff.
• Reputation. Clients talk, and the story will be “the designer held our site hostage”, not “we did not pay”.

Two situations need care:

• You host the site on your own account. Treat the project invoice and the hosting service as separate agreements. Do not use hosting to force payment of a project invoice. If the hosting fees themselves go unpaid, follow the notice and termination terms of your hosting agreement in writing, give the client time and a full export of their site and data, and never delete anything. Get advice before you suspend a business’s live site for any reason.
• The domain is registered in your name. That is a problem to fix, not leverage. If the client paid for the domain or it carries their business name, transfer it to them. Registrars and dispute processes generally side with the business the domain represents, and holding it is the fastest way to turn a debt into a complaint against you. The other side of this story is in our guide for clients, former web designer has my domain or logins.

A pause notice you can adapt: “Hi [name], invoice [number] for [amount] is now [X] days overdue. Until the account is up to date, I am pausing new work and change requests on [project]. Your live website is not affected and nothing about it will change. As soon as payment arrives, or we agree a payment plan, I will pick up where we left off.”

Step 6: Send a formal final notice

If the gentle route has failed, send one clear, formal letter or email. In some countries, a written demand that gives the debtor a fair chance to pay is expected, or even required, before you go to court, so check the local rules. Include:

• Who you are and who the client is (legal names).
• What was agreed, with dates: the proposal, the contract, any change requests and sign-off.
• The invoices, amounts, due dates and payments received.
• Any late fee or interest you are entitled to, and how it is calculated.
• A final deadline (14 days is a common, reasonable period).
• What you will do if it is not paid: file a small claim, refer it to a collections service or seek advice.
• An offer to talk or agree a payment plan.

Keep it factual and unemotional. Imagine a judge reading it.

Step 7: Small claims, mediation and collections

If the deadline passes, you have several routes. None is quick, so weigh the amount against your time.

• Small claims court. Most countries and US states have a simplified court for smaller debts, designed for people without lawyers. Limits, fees and procedures vary a lot by place, and suing a client in another country or state is harder. Look up the official court or government website for where the client is based. Often the claim being filed is enough to prompt payment.
• Mediation. A neutral mediator helps you agree a settlement. Some small claims courts offer free or low cost mediation.
• A lawyer’s letter. A short demand letter from a lawyer often resolves things at modest cost, especially with a business client.
• A collections agency. Agencies usually take a share of what they recover, and how they may operate is regulated. Choose a reputable, licensed one and understand the fee before you sign.
• Payment platform disputes. If the client paid part of the invoice and then charged it back, respond through the payment processor’s dispute process with your contract, sign-off and delivery evidence.

Whatever route you choose, you will need an evidence pack: the proposal, contract or accepted terms, change requests, emails showing approval and sign-off, proof of delivery (staging links, launch confirmation, screenshots with dates), invoices, reminders and the final notice.

Step 8: Know when to write it off

Sometimes the cost of chasing (your time, fees, stress) is more than the debt. Set a limit in advance. If you write off a debt, ask your accountant whether it can be treated as a bad debt for tax purposes where you are. Close the relationship cleanly, hand over what was paid for, and move on. Your energy is better spent on clients who pay.

Prevent it next time

Almost every hostage story starts with a project set up so that the designer had all the risk until the very end. Change the structure instead:

• Take a deposit before you start. A meaningful deposit filters out clients who were never going to pay.
• Bill by milestone. For example: deposit, design approval, build complete on staging, launch. The final payment is then a small share, not most of the project.
• Launch after the final payment. Build on your own staging and make “final payment before launch” a standard term. This is the clean, legitimate version of leverage: you have not handed it over yet.
• Put ownership and licenses in the contract. State that ownership of the design and code passes on payment in full, and who holds each license.
• Set the client up as the owner of their own accounts from day one. Registrar, hosting, analytics and Search Console in their name, with you added as a user. It sounds like it gives away leverage, but it removes the temptation and the dispute, and clients trust you more for it.
• Agree late fees in writing, within what local law allows, and payment terms that suit you.
• Use change requests for every extra, so the final invoice holds no surprises. The scope creep script and change request makes this easy.
• Invoice promptly and make paying easy, with a payment link on every invoice and reminder.

The proposal and scope of work outline and the website project contract outline in the Client Survival Kit list the payment, milestone and ownership terms to discuss with your lawyer. For ongoing work, the maintenance agreement outline covers billing, late fees and termination.

If none of that worked

If the client has gone silent, the business has closed, or the amount is too small to pursue, close the file deliberately. Send a final, polite email saying the matter is closed or referred, hand over anything that was paid for, and remove your own access from any accounts that belong to the client so nobody can later say you kept it. Use the client offboarding template to make sure the exit is clean.

If the client threatens you, accuses you of something you did not do, or the amount is large, stop corresponding and get legal advice. And if you are taking on a site from another designer in the middle of a payment dispute, stay out of the dispute and work only through accounts the client owns, as described in the inherited site takeover playbook.

Related reading: how to price website care plans and managing many client sites safely.