How to handle a client who disputes your invoice

The message arrives on a Tuesday. “I’ve had a look at the invoice and I’m not sure the hours are right. Can we discuss?”

The instinct: apologise, review immediately, offer a discount to move on. It’s the path of least resistance, and it’s usually wrong.

Ask what’s actually being disputed

Before you do anything else: “Can you tell me which line items specifically you’re questioning?”

Vague objections (“this seems high”) require a different response than specific ones (“you billed 6 hours for the kick-off but it only ran 2”). Until you know which you’re dealing with, any response is a guess.

Don’t launch into a defence. Don’t offer to “take a look at the numbers.” Ask the specific question and wait.

The three types of disputes

Hours they didn’t expect. The client had a number in their head. You had a different number. Almost always a communication failure from before the project started — not a billing error on your part.

Work they can’t account for. “I don’t remember a call on the 12th.” This is where your documentation either ends the conversation in two minutes or drags it out for a week.

A fee they didn’t see coming. Additional revisions, admin time, expenses not discussed upfront. If it wasn’t clear in advance, the invoice is a surprise — and clients who are surprised dispute.

Why documentation is your strongest response

A disputed hour is a matter of opinion without a record. With a record, it’s a fact.

If you track work in your calendar, every session has a timestamp: client name, task description, start time, end time. When a client says a meeting was two hours and you billed three, you forward the calendar event. The conversation ends.

Timescanner generates a billing report directly from your calendar events — hours by client, by period, by date. If a client questions the February invoice, you export the breakdown. Instead of “I’m pretty sure we worked that many hours,” you send a report showing every session logged under their name, with dates and durations. That’s not aggressive — it’s just the record.

Works with any iCal calendar: Google Calendar, Outlook, iCloud, Proton Calendar, and others.

Scenario one: you made an error

Acknowledge it, correct it, resend. One sentence: “You’re right — I miscounted the hours on that review call. Updated invoice attached.” No extended apology, no explanation of how it happened. Correct and move on.

If it happens more than once, you have a process problem. The fix is better documentation during the project, not after the invoice is sent.

Scenario two: the client is misremembering

Share the record — not as a confrontation, as information. “Here’s the calendar breakdown for that week. The strategy call on the 12th ran from 10:00 to 13:20, including the 30-minute debrief.”

If that’s new information to them, most clients adjust their position without drama. Don’t send it with language like “as you can see.” Send it as a neutral document.

Scenario three: mismatched expectations

The client thought revisions were included in the fixed price. You billed for them as extras. The invoice isn’t technically wrong — the scope agreement was incomplete.

There’s no clean answer here. You can negotiate to preserve the relationship, or hold the invoice and accept some friction. What you shouldn’t do is absorb it silently. Absorbing it means it will happen on the next project too.

The fix is upstream: clear invoice line items that reference the original scope, plus a short note mid-project any time scope changes. “Just to confirm — the additional revision round will be billed at my standard rate, included in the final invoice.” One sentence. Client confirms. No surprise at the end.

If the dispute turns into non-payment

A dispute in good faith is a question. After a few weeks of back-and-forth without resolution, you can usually tell if it’s turned into something else.

If the client stops responding after you’ve shared the documentation, the escalation sequence for overdue invoices applies — including the formal notice that puts the non-payment on record.

A genuine billing dispute is not a reason to pause payment entirely. The client can pay the undisputed portion while the rest gets sorted. If they refuse that, it’s not a billing dispute anymore.

One situation that looks similar but works differently: a client who disputes the charge at the card processor level rather than with you directly. That’s a chargeback — a different mechanism, a shorter window, and a third party making the decision. Same documentation helps, but the process is not the same.