Checking every invoice is not diligence

If three people review every invoice draft before it goes out, that is not diligence. It is the cost of a commercial record that cannot prove itself.

The ritual is familiar. Finance drafts. Delivery explains what actually happened. Someone checks the spreadsheet against the timesheets. A partner reads the total and quietly decides what the client will tolerate. Then the invoice goes out, several days later than intended, having been rebuilt rather than issued.

The mistaken diagnosis

Firms read this as care. Our margins are thin, our clients are demanding, so we check everything. The review is described as a control.

It is not a control. A control tests a specific condition and fails a specific item. Routine full review tests nothing in particular — it re-derives the whole invoice, every cycle, because nobody can tell in advance which lines are safe.

That is a diagnostic finding, not a moral failing. If the record could prove itself, you would review exceptions. The fact that you review everything is evidence that you cannot tell the exceptions apart from the rest.

What the review is actually reconstructing

Each pass through the draft is answering questions that should already have answers attached to the record.

Was this rate the agreed rate, or the one someone conceded on a call. Was this time approved, and by whom. Does the contract permit billing this line, and under which clause. Was this change priced, or delivered on goodwill and described in a meeting note. Is this milestone genuinely accepted, or marked complete because the delivery date passed.

Those are not billing questions. They are commercial questions, and every one of them was answerable at the moment it arose, by the person who was there. The review is doing that work weeks later, with less context, under time pressure, on behalf of somebody who has moved on to the next engagement.

What the client sees

The internal cost is slow cash and a finance team doing archaeology. The external cost is the dispute, and it is the more expensive of the two.

An invoice is the moment a client audits the commercial story. What was agreed, what changed, what was approved, why this line is billable. Clients rarely dispute an invoice because they object to paying. They dispute it because the invoice cannot explain itself, and an unexplained invoice invites a negotiation the firm never intended to have.

Once that negotiation opens, the concession is usually made on the spot to protect the relationship. A softened line item. A goodwill credit. A write-off that never gets attributed to the upstream decision that caused it. The dispute is a rules failure surfacing at the least favourable moment, in front of the client, with the firm holding the weaker hand.

The mechanism that removes the rebuild

Making invoices defensible is upstream structural work, not tighter drafting downstream.

In practice it means the engagement carries its billing rules from the point it is quoted, so time entered against it inherits those rules rather than being classified afterwards. Approval is a state on the record, not an email. Change orders attach to the engagement they change and are priced against the contract terms before delivery. Each invoice line links back to the time, cost, approval and clause that produced it.

Then readiness gates do the work the review was doing — but selectively. An item that cannot yet prove itself is held, with the reason recorded against the item rather than in someone’s head, and the rest proceeds. The part of DAY ONE that governs this is described on our invoicing and WIP page, and what it looks like in a consulting business specifically is on the IT services and consulting page.

What this costs, and where review still belongs

Two things have to be said plainly.

Some review is non-negotiable and always will be. A first invoice on a new client, a milestone with a contested variation, an engagement where the commercial relationship is delicate — those should be read by a human regardless of how good the chain is. The argument here is against routine rebuild, not against judgement at the exception. A firm that automates away its judgement has removed the wrong thing.

And gating readiness makes invoicing slower before it makes it faster. In the first cycle or two, work that used to be quietly absorbed at the end of the month surfaces in week two as a blocked invoice with a named reason. That feels like a regression. It is the same amount of work, moved to where it can still be fixed cheaply — but firms that cannot hold that line through two cycles will not get the benefit and should not start.

The position, restated: routine full review is not diligence, it is the price of an unprovable record, and the fix is upstream. If you want a single number to watch while you find out whether that is true in your firm, watch what proportion of invoices go out as first drafted — the argument for that metric is in first-pass invoicing as a trust test.