Client billing · 7 min read

Disputed and short-paid invoices: how to resolve billing disagreements

A disputed invoice is a different problem from an unpaid one. The client is not avoiding you — they disagree about what is owed. Handling that distinction well protects both the money and the relationship.

An invoice split into an agreed balance and a single disputed line item

Chasing tactics that work on a late payer actively damage a dispute. Sending escalating reminders to someone who genuinely believes they were overcharged reads as refusing to listen, and it usually makes the amount harder to collect rather than easier.

Worked example

A studio invoices 5,000 for a website project. The client pays 4,200 with no explanation.

Point 1: The 800 shortfall matches a line for "additional page templates — 4 at 200." The studio checks its records and finds the extra templates were requested by email, but never confirmed as a scope change with a price.
Point 2: The response: acknowledge the same day, confirm that 4,200 has been received and thank them, quote the email requesting the extra pages, and acknowledge honestly that the price was not confirmed in writing beforehand. Offer to settle at 400 as a shared outcome, with a note that future scope changes will be confirmed with a price before work starts.
Point 3: The client accepts. The studio issues a credit note for 400 against the original invoice, and the remaining 400 is paid within a week. More usefully, the quote template now includes a scope-change clause, and that particular dispute never recurs.

Original diagram

Disputed and short-paid invoices: how to resolve billing disagreements decision flow

1First, work out which problem you have
2Short payments: read the number
3A structured response
4Preventing the next one

First, work out which problem you have

Three situations look similar in your accounts and need entirely different responses.

The quickest way to tell them apart is specificity. A process block produces a specific, answerable reason. A genuine dispute produces a specific objection to a specific line. A stall produces vague dissatisfaction that shifts when you address it.

A process block. Nobody disagrees with anything. The invoice is stuck because a field did not match or a receipt was never confirmed. This is administrative.
A genuine dispute. The client believes the amount, the scope, or the quality is not what was agreed.
A stall. The client has a cash problem and is raising a query to buy time.

Short payments: read the number

When a client pays less than invoiced, the shortfall itself usually tells you what happened. Before contacting anyone, check whether the difference corresponds to:

Several of these are not disputes at all. Arriving at the conversation already knowing which line is affected changes the tone entirely, and often resolves it in one message.

A specific line item the client did not accept
A tax amount, suggesting a disagreement about tax treatment or a withholding deduction
An early payment discount taken, correctly or otherwise
A previous credit note the client has applied without telling you
A bank or intermediary charge deducted in transit on an international transfer
A currency conversion difference on an invoice billed in another currency
A rounding or data-entry error, particularly if the shortfall is small and odd

A structured response

1. Acknowledge quickly:

Respond within a day, even if only to say you are looking into it. Silence after a client raises a concern is read as defensiveness and hardens their position.

2. Ask for the objection in writing, specifically:

"Which line are you querying, and what did you expect it to be?" A verbal complaint about "the invoice being higher than expected" cannot be resolved; a written objection to a named line can.

3. Separate agreed from disputed:

This is the most important step. If 4,500 of a 5,000 invoice is uncontested, that 4,500 should not be sitting unpaid while you debate the rest. Ask for the undisputed portion on the original timeline.

Practically, many AP systems cannot part-pay. The workaround is to credit the original invoice and issue two new ones: one for the agreed amount, payable now, and one for the contested amount, held pending resolution.

4. Check your own evidence before arguing:

Pull the quote, the approval, any scope change confirmations, and the delivery record. Do this before responding on the substance. Suppliers who defend a line and then discover they were wrong lose far more credibility than suppliers who concede early.

5. Respond on the facts, in one message:

Quote the agreement, attach the approval, and state your position plainly. Avoid restating the whole history — it reads as building a case rather than solving a problem.

6. Set a resolution date:

"Can we settle this by Friday 26th?" A dispute without a deadline drifts, and drifting favours whoever is holding the money.

7. Close it in writing:

Whatever the outcome, confirm it: what was agreed, what will be credited or paid, and by when. Then issue the paperwork immediately, because a resolved dispute with no credit note is a dispute that will resurface at year end.

Preventing the next one

When a dispute cannot be resolved and the amount is significant, formal options exist — mediation, small claims processes, debt recovery — but they vary by jurisdiction and are worth taking specific advice on. For most disagreements, a specific question, a fast acknowledgement and a willingness to split agreed from contested resolves things well before that point.

Price scope changes before doing them, in writing, even informally.
Itemise enough to be checkable. A single line reading "Consultancy — 8,400" invites scrutiny that an itemised breakdown does not.
Send a draft of large invoices for confirmation before issuing.
Name the approver on the invoice where work was authorised verbally.
Log every dispute with its cause. Patterns show up quickly, and they are almost always fixable upstream.

Common questions

Helpful clarifications

A client paid less than the invoice. What should I do first?

Work out the exact shortfall and check whether it matches a specific line item, a tax figure, a currency conversion, or a bank charge deducted in transit. The amount usually identifies the cause. Then ask the client one direct question about that specific figure rather than sending a general reminder, because a general reminder invites a general non-answer.

Should I stop work when an invoice is disputed?

Not automatically. Stopping work escalates a disagreement about one line item into a disagreement about the whole relationship. It is more effective to keep the dispute contained, ask for the undisputed portion to be paid on time, and set a short deadline for resolving the rest. If the dispute is unresolved and the balance is significant, then pausing new work is a reasonable next step, ideally stated in advance and in writing.

Can I ask a client to pay the part of the invoice they agree with?

Yes, and you should. Splitting the invoice into an agreed portion and a disputed portion stops the whole amount being held hostage by a small disagreement. Many accounts payable systems can only process an invoice in full, so the cleanest approach is often to credit the original invoice and issue two: one for the agreed amount, one for the contested amount.

What if the client raises a dispute only after the due date?

Treat it as genuine but note the timing in writing. Late-surfacing disputes are sometimes real and sometimes a way to reset the payment clock. Respond substantively to the point raised, and at the same time confirm the original due date and that the undisputed balance remains payable. Keeping both threads in one message avoids the appearance of accepting a new deadline.

How do I stop the same dispute happening again?

Look at where the expectation gap opened. Most repeat disputes trace back to scope wording that was clear to you and ambiguous to the client, or to work approved verbally and never confirmed in writing. Fixing the quote template or adding a short written confirmation step usually eliminates a whole category of disagreement.