Direct answer

A client is disputing your invoice. Handle it with the record, not the argument.

A disputed invoice feels personal and reads emotional, but underneath it is a sorting problem. The client is making one of five claims, possibly two, and each claim has exactly one record that settles it. Find the claim first. Answer it with the record, once, line by line. Most disputes end inside that single exchange, because there is nothing left to perform.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 17, 2026. The delivery records quoted below are real and public, with their states read back from the live service on publication day. This page is general information, not legal advice.

The five claims, and the record that answers each

The amount is wrong. Settled by arithmetic against the agreement: the rate, the quantity, the approved changes. If the invoice and the agreement disagree, the agreement wins and you correct the invoice. If they agree, show the two side by side and the claim is finished.

The work was outside the scope. Settled by the change approvals. Work the client asked for in writing is inside the job. Work nobody approved is a real argument, and it is the reason changes get approved in writing on the next job, every time, even when the price effect is zero.

The work was never delivered. Settled by the delivery record: the steps, saved with their times, at one link the client can open. This is the claim that evaporates fastest against a real record and lingers longest against email attachments and recollection.

The quality is not what was agreed. Settled partly by the agreement's standard and partly by the acceptance state, and not settled by delivery proof at all. Handled honestly, this is the claim where you offer a specific fix on a specific step rather than defending the whole job.

The work was never accepted. Settled by the acceptance state. If the client accepted on the record, the state says so, with the time. If the state is still pending, that fact cuts both ways and you should say so: the decision is open, and the dispute is partly about closing it.

The reply: one message, built like the record

Answer once, in one message, in the order of the invoice lines. For each line: the claim as you understand it, the record that answers it, and what you propose. Concede the line that is genuinely wrong, visibly and without being asked twice; one honest concession makes the other lines very hard to perform against. Close by splitting the invoice into the disputed lines and the rest, and ask for the undisputed part on the original terms. Then stop writing. Disputes grow in the space between messages, and every extra message you send is new material. The record has said everything.

Why accepted work is barely disputable

Accepted first, invoiced second

Scope: Retrieval, extraction, verification, and reporting pipeline producing an AI-adoption research packet for a law firm.

Status: accepted by the client on 2026-10-16, decision ok_to_release, all 4 steps checked.
An invoice against this record disputes nothing about delivery, scope of the record, or acceptance; all three were settled by the client's own recorded decision before the invoice existed.
Open the handover or read its acceptance.json.

Still pending: where disputes are born

Scope: AI visibility audit of zambo.dev: homepage copy inventory, on-page citation audit, and evidence-based recommendations.

Status: still pending, decision hold, 5 of 5 steps saved on 2026-10-16.
Work delivered and visible, acceptance never recorded: exactly the gap a dispute grows in. The fix is not a better invoice. It is closing the acceptance before the invoice goes out.
Open the handover or read its acceptance.json.

What the record does not settle

A delivery record proves the saved result was not changed since it was saved, and it shows the acceptance state. It does not prove the price was fair, the work was good, or who produced it. A dispute about value is a negotiation, and a dispute about a client who cannot pay is a credit problem. This page is general information, not legal advice; formal routes and their limits vary by place and agreement. What the record does is shrink the dispute to the lines that are genuinely arguable, and most invoices only ever had one.

Frequently asked questions

How do I handle a client disputing my invoice?

Slow the conversation down and find the actual claim before answering any of it. A dispute is one of five arguments: the amount is wrong, the work was outside the agreed scope, the work was not delivered, the quality is not what was agreed, or the work was never accepted. Each one is settled by a different record: the invoice against the agreement, the change approvals, the delivery record with its times, the agreement plus the acceptance state. Reply once, line by line, attaching the record that answers each disputed line, concede any error that is genuinely yours in the same message, and ask for the undisputed part to be paid on the original terms. Most disputes shrink to one line within one exchange when the record does the talking.

Should I keep working while an invoice is disputed?

Separate the disputed job from everything else. Pause new work that depends on the disputed agreement if the dispute is about scope or acceptance, because continuing builds a bigger argument on the same unclear ground. Keep communicating, keep delivering anything already accepted and undisputed, and do not hold unrelated finished work hostage unless your agreement says you can: it converts a one-invoice argument into a relationship-ending one and rarely speeds the payment. The clean move is narrow: this invoice, this record, this decision, while the rest of the relationship stays visibly professional.

What if the dispute is about quality, not delivery?

Then the record alone does not settle it, and pretending otherwise weakens your position on the parts it does settle. Quality is judged against the agreement: the scope, the examples or standards it referenced, and the acceptance state. A client who accepted the work step by step has a smaller quality dispute than one who saw it for the first time at the invoice, which is why acceptance during the job matters. Answer the delivery and scope lines with the record, answer the quality line against the agreed standard, and if a specific step genuinely misses, offer the fix for that step, priced or free, as its own line. Precision is what makes the rest of the invoice boring to argue with.

When does a dispute become a refusal to pay?

When the client stops naming lines and starts refusing the whole invoice, or stops answering altogether. At that point the dispute tools are done and the payment sequence begins: the formal demand with a date, then the platform dispute, mediation, small claims, or collections routes that fit the amount and the agreement. Everything you sent during the dispute becomes the file for that sequence, which is why the dispute replies should be factual, single, and record-carrying from the first one. The sister page on a client who will not pay carries the full sequence in order.

How do I make the next invoice boring to dispute?

Invoice against a record the client has already seen and accepted. When the work runs through Zambo, the delivery is a handover the client checks and accepts or flags step by step, so by invoice time the scope, the delivery, and the acceptance are one record the client has already acted on, and the invoice is just the price of a settled thing. For $0.99, answer your next invoice dispute with the record instead of the argument: get the Day Pass. A Day Pass covers 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.