Direct answer
One disputed line does not freeze the whole invoice.
The invoice lands, and back comes a message: one item is wrong, a stage they question, an amount they do not recognise, and until that is sorted, nothing gets paid. Read it carefully and two separate things have been fused into one block. The disputed part, which may be a genuine error, a misunderstanding, or a real disagreement, deserves a real answer. The undisputed rest, work delivered, accepted, and not questioned by anyone, is simply being held hostage to the first conversation. The fix is not to argue louder about the disputed item. The fix is to split the invoice in writing the same day: the disputed lines isolated with their own amount and their own settlement path, and the balance reissued as due now, on its own date. Once the parts are separate, the dispute gets smaller and the money gets moving. Here is how.
Updated November 3, 2026. First published November 3, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on November 3, 2026.
Step 1. Split the invoice in writing the same day the dispute arrives
Reply while the message is fresh, in numbers, not in feelings. Restate the invoice as two piles. Pile one, the disputed part: the exact lines questioned, quoted word for word, with their total stated alone. Pile two, the undisputed balance: every other line, with its total stated alone, and a sentence naming the obvious: no part of this balance has been questioned. Then attach the ask the whole page turns on: the balance is due on the original terms, please confirm the date it will be paid, and the disputed part will be settled on the path in step 3, separately. This single move changes the geometry of the argument. Before the split, paying anything felt to the client like conceding everything. After the split, refusing the balance requires them to defend holding money they agree is owed, which is a much harder sentence to write, and most clients do not write it. They pay the balance and argue the small pile, which is exactly where you want the argument.
Step 2. Check the disputed part against its own record before defending it
Before you answer the substance, audit your own position in private. Pull the disputed lines apart one by one and set each against its evidence: what was agreed for that item, in the quote, proposal, or change message. What was delivered for it, and when. Whether it was checked and accepted, or is still awaiting a decision. Whether your invoice line matches the agreed figure exactly, because the most common honest outcome of this audit is finding one line that is genuinely yours to fix: a figure carried over wrong, a stage billed twice, a change priced but never confirmed in writing. Fix any such line immediately and visibly, restate the disputed pile at its corrected size, and let the correction stand as proof of good faith. A supplier who finds and fixes their own error in the first reply earns the right to be believed on the lines that survive the audit, and the dispute usually shrinks to the one or two lines that are a real disagreement rather than a pile nobody had actually read.
Step 3. Settle the disputed pile on its own dated path
The disputed lines need a settlement path with dates, or the small pile will be used to delay the large one forever. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the states a delivery can carry:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
An accepted record, 4 of 4 steps checked, decided_by client, release_hint ok_to_release, decided 2026-10-16T14:31:51.146Z in that example, answers a disputed line about delivered work with a fact: this stage was delivered, checked, and accepted on that date, so the argument about it is about price or memory, not about whether the work exists. Attach the relevant record link to the disputed line it covers and let it do that work. A pending record, 5 of 5 steps checked and release_hint hold, marks the genuinely open shape: checked work with no decision yet, where a price argument and a missing acceptance have fused together. There, propose the sequence in writing: the decision recorded first, then the line settled on the agreed figure, each by a named date. Either way the disputed pile now has a finish line, and a pile with a finish line cannot hold the balance hostage past it.
Step 4. Hold the line kindly: no new work rides on a frozen balance
While the balance is unpaid past its terms, pause new work, and say so in the same even tone as the split: happy to continue the moment the undisputed balance lands, and the disputed part can be argued for as long as it honestly takes. The pause is what keeps the split real. Without it, the client's cheapest strategy is to keep the dispute permanently warm and keep receiving work, and every week of delivered work enlarges the sum the warm dispute is sitting on. With it, the incentives point the right way for both sides: the balance is the fastest thing to pay, the disputed pile is small enough to settle in one meeting, and the project both sides actually want resumes. Keep the pause scoped and reversible in writing: it covers new starts, not the settlement work itself, and it lifts automatically on receipt of the balance, no second negotiation required. Clients who were using the dispute as a cash flow device will pay within days. Clients with a genuine grievance will settle the small pile, because you have made settling it cheap.
Step 5. If they still refuse the balance, escalate the undisputed sum alone
Escalation works best when it inherits the split. A reminder, a formal notice, or any later step that demands the whole original invoice, disputed lines included, hands the client their defence back: part of this is genuinely contested. The same step taken for the undisputed balance alone, a sum they have never questioned, with the delivery and acceptance record attached and the disputed pile expressly set aside as under separate discussion, leaves almost nothing to argue with. State, in each escalation message, that the disputed part remains open for settlement and is not being demanded in this step; the scrupulousness is not weakness, it is what makes the demand for the balance unanswerable. Keep every message dated and in writing, keep the amounts identical across every retelling, and let the record show a supplier who separated the arguable from the unarguable and only ever chased the second. That record, if the argument ever reaches a third reader, is the strongest exhibit you own.
Step 6. Invoice the next job so a part can never freeze the whole again
Three habits, set at invoice time, prevent this shape entirely. Bill in stages, each stage invoiced on its own acceptance, so any dispute is born small and attached to one stage rather than spread across a whole project sum. Write each invoice line so it names the deliverable and its agreed figure source, the quote line or the confirmed change, making your step 2 audit a five minute read instead of an excavation. And carry one sentence in your terms from the start: where part of an invoice is disputed in writing, the undisputed balance remains due on its normal terms. Clients sign that sentence without blinking at the start of a friendly job, and it converts a future argument about fairness into a simple reading of what was agreed. Disputes will still happen; honest people misread lines. With stage billing and that sentence, a dispute becomes what it should have been all along: a small, dated conversation about one item, conducted while the rest of the money moves.
What a record does not settle
A verifiable receipt proves the saved result was not changed since it was saved; it does not price a stage, decide whether a disputed line was agreed, or compel any payment. The agreement, the delivery record, the acceptance, and your written split of the invoice are what the conversation stands on. This page is general information, not legal advice.
Frequently asked questions
My client is disputing part of my invoice and will not pay any of it until that part is settled. What do I do?
Split the invoice in writing the same day. Restate it as two piles with separate totals: the disputed lines, quoted exactly, and the undisputed balance, which nobody has questioned. Confirm the balance is due on the original terms and ask for its payment date, and give the disputed part its own settlement path: audit each disputed line against what was agreed, what was delivered, and whether it was accepted, fix any line that is genuinely your error immediately, and settle the rest against the delivery record by a named date. Pause new work until the balance lands, lifting automatically when it does. If escalation is needed, escalate the undisputed balance alone, with the disputed part expressly set aside. The whole method rests on one fair fact: a question about one item is not a reason to hold money that is agreed on every side to be owed.
Is it normal for a client to hold the whole invoice over one disputed item?
It is common, which is not the same as reasonable, and the two causes need different handling. The innocent cause is accounting habit: many payment systems process an invoice as one payment, and a query flags the whole document rather than a line. That cause dissolves the moment you reissue the undisputed balance as its own clean invoice with its own reference, because the system can pay it without anyone overriding the flag. The deliberate cause is leverage: the disputed item is being used to delay the whole sum or to soften you up for a discount on the rest. That cause dissolves when the split is in writing and new work is paused, because the delay stops buying anything. Either way your first move is identical, which is why the split comes first and the diagnosis of motive can wait until you see which client you have.
What if the disputed part is most of the invoice?
Then split honestly at whatever size the piles really are, and let the small undisputed balance be paid first anyway. A modest first payment still proves the split works, starts the settlement clock, and separates any good faith on the client's side from a pure freeze. For the large disputed pile, tighten the process: each line answered in writing against the agreement and the delivery record, one meeting with a stated agenda of the surviving disagreements, and a settlement date both sides name. Resist the temptation to discount the whole pile to end the discomfort; if a discount is traded at all, trade it line by line for something real, immediate payment of the settled figure, written acceptance of the stage, never as a percentage shaved off an unexamined total. A big dispute settled line by line usually ends smaller than it started, because most piles contain lines nobody still disputes once they are read separately.
Should I offer a discount on the disputed part to get the rest paid?
Do not fuse the two piles by trading one against the other. A discount offered on the disputed lines in exchange for releasing the balance teaches the client that disputing any item earns a percentage off it plus delay on everything else, and the lesson will be applied to every future invoice. If, after the audit, a genuine concession is warranted on a disputed line, make it on that line, for a stated reason tied to that line, in exchange for settlement of that line by a stated date. The balance, meanwhile, was never part of the negotiation: it is owed in full on its terms, and keeping it out of the trading is what preserves the meaning of undisputed. Suppliers who protect that word find clients use disputes more carefully. Suppliers who trade against it find disputes arriving on schedule, at invoice size.
How do I invoice so an undisputed balance always moves on its own?
Bill by stage against a checkable record. When the work runs through Zambo, every step carries a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and each stage can be accepted on its handover before its invoice is issued, so a later dispute starts attached to one stage and one record instead of spreading across the project. New users get 20 calls and 1 wrap-up free every day, and picking up work in another AI is always free. For $0.99, run the next staged job that way and let each stage carry its own proof into its own invoice: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.
Related
- My client wants me to give up the right to show the work in my portfolio. Should I agree?
- My client wants me to redo the work because they gave me the wrong information at the start. Who should pay?
- My client is disputing my invoice. What should I send them?
- My client wants a payment plan for an invoice they cannot pay all at once. Should I agree?
- Start with your problem: every problem in this directory, routed to its page