What to Do When a Client Disputes an Invoice on a Claude Code Build (Settle It Without Losing the Client)
- A disputed invoice is rarely a client trying to skip the whole bill. It is usually one line they did not expect: extra hours, an API cost, a change they thought was included, or a milestone they do not think is finished. Treat it as a question about that line, not an attack on your work.
- Use the Profit Room's Line-Item Split: ask which specific lines they disagree with, and ask them to pay everything else now. That gets most of your money in, shrinks the argument to its real size, and keeps the project moving while you sort out the rest.
- Resolve the disputed line with the paper trail - the agreement, the change orders, the sign-off - not with feelings. Decide in advance where you will give a little, put the outcome in writing, and fix the gap in your process that let the surprise happen.
The Short Answer
When a client disputes an invoice, do not defend the whole bill and do not cave on it. Reply calmly within a day, thank them for raising it, and ask one question: which lines, specifically, do they disagree with? Then ask them to pay the rest now while you look into those lines together. Most disputes shrink fast once they are pinned to a specific item, and getting the undisputed amount paid takes most of the pressure off both of you.
That is the Line-Item Split. It works because it separates the part you both agree on from the part you do not. Without it, a disagreement over one line holds up the whole payment, and every day it sits unpaid makes the conversation tenser. With it, you are no longer arguing about whether you get paid, only about one line.
Why Clients Dispute Invoices on AI Builds
Before you reply, figure out which kind of dispute you have. On a Claude Code build, it is almost always one of these, and each one points to its own fix.
- Surprise extra work. The client asked for small changes along the way and did not realize each one added to the bill. This is the most common cause, and the fix is a [change order](/blog/change-order-template-for-a-claude-code-project) for every addition, signed before you start it.
- Surprise usage costs. The invoice includes model or API costs the client did not expect, or expected to be folded into your fee. [Billing clients for AI API costs](/blog/bill-clients-for-ai-api-costs) covers how to set that up so it never surprises anyone.
- They do not think it is finished. You billed a milestone, and the client thinks something in it still does not work. This is a sign-off problem more than a billing problem.
- They expected a different price. The scope or the price was never written down clearly, so the client is remembering a different number than you are.
- Cash flow. Sometimes the dispute is really a client who cannot pay right now and is looking for a reason. Treat that as a [late payment](/blog/how-to-handle-a-client-who-pays-late) conversation, not a dispute.
Run the Line-Item Split
Your first reply sets the tone for everything after it. Keep it short, calm, and focused on getting to specifics.
Try: 'Thanks for flagging this - I want to make sure the invoice is right. Can you tell me which lines you disagree with? In the meantime, could you go ahead and pay the rest of the invoice, and we will sort out those lines together this week? I can send a revised invoice for the undisputed amount today if that is easier.'
Then do exactly that. Send a revised invoice for the agreed amount, and a separate note listing the disputed lines with the evidence for each one. Do not add anything else to the message, such as a lecture about the project, a list of past favors, or how hard you worked. Every extra sentence gives the client something new to argue about.
| Disputed line | What to check | Fair outcome |
|---|---|---|
| Extra work | Was there a signed change order or a written yes? | If yes, it stands. If it was only a chat, consider meeting halfway this once. |
| API or usage costs | Did the agreement say how usage is billed? | If yes, show the usage record. If not, split it and fix the agreement. |
| Unfinished milestone | Does the build meet the acceptance criteria you agreed on? | If something is missing, fix it fast, then rebill. If it meets the criteria, walk them through it. |
| Price they remember differently | What does the written scope or proposal say? | The written number wins. If nothing was written, settle and write it down next time. |
How to handle each kind of disputed line
Resolve the Disputed Part
Put the evidence in front of both of you: the agreement, any change orders, the client's written approvals, and the milestone sign-off if you have one. [Getting a client to sign off on a build](/blog/get-a-client-to-sign-off-on-a-build) is what makes this step quick. Claude Code can help you assemble it: point it at your project notes, commit history, and message exports and ask it to list every change made after the original scope, with the date each one was requested. Check the list yourself before you share it.
Have the conversation on a short call if the client is open to it, then confirm the outcome in writing the same day: what was agreed, the final amount, and the date it will be paid. If you agree to a reduction, call it a one-time adjustment and say why, so it does not become the new price for the next invoice.
If the dispute is really about quality - the client is unhappy with the build itself - handle that first and the money second. [When a client asks for a refund](/blog/when-a-client-asks-for-a-refund) covers how to respond when the complaint is about the work, not the bill.
If They Will Not Pay at All
Most disputes end with a payment. A few do not. If the client refuses to pay anything, including the undisputed part, stop new work on the project until the account is settled, and say so politely in writing. Do not hand over source code, credentials, or deliverables you have not been paid for if your agreement ties handover to payment. [Who owns the code you build for a client](/blog/who-owns-the-code-you-build-for-a-client) covers how to set that up.
Then decide what the remaining amount is worth to you. For a small amount, it is often better to settle, write it off, and end the relationship well, following [how to fire a client without burning the relationship](/blog/how-to-fire-a-client-without-burning-the-relationship). For a larger amount, a formal demand letter or small claims court may be worth it. Rules and limits vary by location, so check what applies where you and the client are based, and talk to a lawyer before you take a large dispute that far. This is not legal advice.
Stop the Next Dispute Before It Starts
- Write the price and scope down before you build, even for small jobs. A [one-page agreement](/blog/one-page-agreement-before-you-build) is enough.
- Bill in milestones, not one big invoice at the end. [Structuring client payments in milestones](/blog/structure-client-payments-milestones) keeps each invoice small and each disagreement small.
- Take a deposit. [The deposit conversation](/blog/the-deposit-conversation-get-paid-upfront) means you are never fully exposed.
- Put every addition in a change order with a price, signed before you start it.
- Show the running total in your [weekly client update](/blog/weekly-client-update-prevents-fires), so the final invoice is never the first time the client sees the number.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What should I do when a client disputes an invoice?
Reply calmly within a day, ask which specific lines they disagree with, and ask them to pay the rest now while you sort out those lines together. Send a revised invoice for the undisputed amount, then resolve the disputed lines using the written agreement, change orders, and sign-offs.
Should I ask the client to pay the undisputed part of the invoice?
Yes. A disagreement about one line should not hold up the whole payment. Asking for the undisputed amount now gets most of your money in, keeps the project moving, and shrinks the conversation to the part you actually disagree on.
Should I give a discount to settle an invoice dispute?
Sometimes. If a line was genuinely unclear, such as extra work agreed only in a chat, meeting halfway once can be worth it to keep a good client. If the client signed off on the work or the cost in writing, hold the line. Either way, put the outcome in writing and call any reduction a one-time adjustment.
Can I stop working if a client will not pay a disputed invoice?
If the client refuses to pay anything, including the undisputed part, pausing new work until the account is settled is reasonable, and you should say so politely in writing. Check your agreement first, and if a large amount is at stake, talk to a lawyer about your options where you are based.
How do I prevent invoice disputes on future projects?
Write the price and scope down before you build, bill in milestones, take a deposit, put every addition in a signed change order, and show the running total in your weekly update. When the client has already seen every number before the invoice arrives, there is little left to dispute.
Last reviewed October 10, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →