What to do when a client questions your invoice

It usually arrives politely. “Quick question about the invoice, could you break down the six hours on the 14th?”

Nothing in that sentence is hostile. But the next ten minutes decide whether you are having an administrative exchange or a negotiation, and which one it becomes depends almost entirely on something that happened three weeks earlier.

The two versions of this conversation

Version one. You open your records and reply within the hour: two hours forty in the design file, an hour ten on the revised copy, fifty minutes on the call, and the rest across three smaller pieces on the same brief. Here is the breakdown.

The client says thanks. That is the end of it. They were not accusing you of anything, they were reconciling a number against a budget, and you gave them what they needed to close the line.

Version two. You do not have it broken down, because the six hours were entered as six hours. You reconstruct from memory and calendar, and what comes back is “I think that was mostly the design work and some revisions”. It is probably accurate. It does not sound accurate.

Now the client has a decision to make that they did not have a moment ago, and some proportion of the time they will ask for the line to come down. Not because they think you are dishonest, but because a soft number is easier to negotiate than a hard one, and their job includes negotiating.

The discount, if it happens, is not the real cost. The real cost is that they now check the next one.

What makes an answer land

Three things, and only the third is about the numbers.

Speed. Answering within a couple of hours signals that the information already existed. Answering in three days signals that you went and made it, whether or not you did.

Specificity. “About two and a half hours on the design” is a worse answer than “two hours forty in the design file”. The second one is not more impressive, it is more obviously a record.

Volunteering the awkward part. If forty of those minutes were you rereading a brief because you had misunderstood the first time, say so and take it off. One line removed voluntarily does more for the credibility of the rest of the invoice than any amount of explanation, and it costs less than the discount you would otherwise be arguing about.

The record has to be made at the time

This is the whole thing, and it is not really about invoicing.

A reconstruction has a direction. When you sit down on a Friday to work out where Tuesday went, you are not neutral: you know what the number ought to be roughly, you know what you were working on, and you fill the gaps in a way that is consistent with the story you already have. That is not dishonesty, it is how memory works.

A record made at the time has no story. It says the design file was focused for two hours and forty minutes across four stretches, that there was input activity throughout, and that there was a nineteen minute gap in the middle. Some of that record will be unflattering. That is precisely what makes the rest of it worth something.

If you want the mechanics of what such a record contains, how automatic time tracking works sets out the five things that get captured and what each is for.

Idle time is the awkward one, and showing it helps

The specific case that comes up most: a document was open for two hours and you worked in it for eighty minutes.

The tempting move is to bill two hours, because the document was open and you were “on it”. The defensible move is to bill the eighty minutes and say so.

Counterintuitively, the second one strengthens the invoice. An invoice that distinguishes active work from open windows is telling the client something they did not have to ask for, and it makes every other line on the document more believable. Clients notice this, and it is one of the few things that reliably converts a project client into a retainer client.

A tracker that separates idle from active gives you this for free. One that folds them together takes the choice away and bills the higher number on your behalf, which is a bad trade even when the higher number is defensible.

Getting the question asked less often

The best version of this is that the question stops arriving.

Invoice with lines, not a total. A single line that says “Development, 34 hours” invites the question. Six lines naming what was done mostly answer it in advance.

Invoice more often. A fortnightly invoice covers work the client still remembers asking for. A quarterly one covers work they have forgotten the context of, which is when the reconciling starts.

Say what the rounding rule is, in the contract. Most disputes that look like arguments about hours are actually arguments about an unstated rounding convention. Rounding is a pricing decision, and an unannounced one is the kind clients push back on.

Send the breakdown before they ask. If your tracker produces one, attach it. Almost nobody reads it. That is fine, because the point is that it exists and they know it exists.

If the client is actually disputing, not asking

Occasionally it is not a reconciliation. Occasionally the position is that the work should not have taken that long.

That is a different conversation and a record does not settle it, because you are no longer arguing about what happened. You are arguing about what was reasonable.

What the record does is keep you out of the worse version of that argument, where you are simultaneously defending the hours and the judgment. Establish the facts quickly and without heat, then have the actual disagreement about scope and estimation, which is a conversation two professionals can have.

The one thing not to do is discount immediately to make it go away. It ends this conversation and prices the next one.