First-pass invoicing as a trust test

First-pass invoicing is a test of the whole business, not a measure of how good your finance team is.

The metric is simple enough to state. What proportion of invoices go out as first drafted, without being rebuilt, queried internally, or held while somebody works out what actually happened. In most professional services firms nobody tracks it, because the rework has been absorbed into the definition of month end.

The mistaken diagnosis

When invoices go out late, the reading is almost always that finance is slow. So the response is a finance response: start the invoice run earlier, add a reminder cycle, put a second person on the drafting, escalate the chasing of timesheets.

Late invoices are rarely a finance problem. They are the visible end of an upstream control problem — scope that drifted without a reset, approvals that were never captured, time entered a fortnight after the work, and no single record of what is billable under which terms.

Finance is not slow. Finance is reconstructing. Those are different failures and they have different fixes, and the reason the distinction matters commercially is that only one of them can be fixed by working harder in the last week of the month.

What a first-pass invoice actually proves

If an invoice can be generated without anyone rebuilding the story behind it, a series of things must already be true.

The engagement was set up with its commercial terms attached. The billing rules were unambiguous before the work started, not inferred afterwards. Time and costs were captured against the right record and approved. Work-in-progress was linked to the work it represents. And exceptions — the held line, the disputed hour, the change nobody priced — surfaced while they were still administrative rather than becoming an argument.

That is why first-pass rate is worth watching. It is not really an efficiency measure. It is a reading of whether sales, delivery and finance are operating from the same governed record, taken at the one point in the month where a disagreement between them cannot be deferred.

Where the rework comes from

The causes are consistent and individually small.

A rate agreed on a call and written down nowhere. A discount conceded in the sale that never reached the billing rules. A change delivered on goodwill, described in a meeting note, and never converted into a priced variation. Time booked to the wrong engagement and corrected informally. A milestone marked complete before the acceptance criteria were met.

None of those looks like a billing failure at the moment it happens. Each one severs the link between a line on an invoice and the evidence that justifies it, and the cost of that severance is only paid weeks later, by somebody with less context than the person who created it.

This is also why the same firms see disputes and credit notes cluster. A client does not usually argue with an invoice because they object to paying. They argue because the invoice cannot explain itself, and an unexplained invoice invites a negotiation the firm did not intend to have.

The mechanism

Making invoices first-pass is structural work done upstream, not tighter drafting done downstream.

In practice it means the engagement carries its commercial rules from the point it is quoted, so time entered against it inherits those rules rather than being classified later. Approval becomes a state on the record instead of an email thread. Change orders attach to the engagement they change, priced against the contract terms, before the work is delivered. Readiness gates hold an invoice that is not yet defensible, and hold it for a stated reason recorded against the item rather than in somebody’s head.

Then each invoice line links back to the time, cost, approval and contract clause that produced it. The part of DAY ONE that does this is the invoicing engine, where traceability runs to an individual timesheet record. There is more detail on our invoicing and WIP governance page, and the same discipline is what separates a WIP register from a WIP argument.

On Salesforce; works with your Salesforce org, or available as a bundled edition if you don’t use Salesforce.

What this costs, and where it does not apply

Getting to a high first-pass rate means agreeing billing rules, approval gates and change control before delivery starts, rather than settling them when the invoice is drafted. That is real work, done up front, by senior people who are already busy — and some firms will conclude they would rather keep the flexibility and absorb the rework each month. That is a legitimate trade, provided it is made deliberately rather than by default.

It also constrains behaviour that currently reads as good service. If unapproved scope cannot be billed until a variation exists, someone has to raise the variation before doing the work. In a culture that says yes first and reconciles afterwards, that will feel like friction, because it is.

And there is a floor below which the discipline is not worth its cost. A firm running a handful of simple engagements on one billing model, where invoicing takes an afternoon and nobody argues with the result, is better served leaving it alone. This matters when several projects, several billing models and several approvers already collide in the same cycle.

One more limit worth naming plainly: no amount of downstream governance invents a record of work that was never entered. Better capture reduces exceptions; it does not manufacture evidence.

What to measure first

Before changing anything, count. Take last month’s invoice run and mark each invoice as issued-as-drafted or reworked, and for the reworked ones write down the reason in a few words. The pattern usually resolves within twenty invoices, and it almost never points at finance.

Faster invoicing improves cash flow, which is the reason it gets funded. The more valuable outcome is the one that is harder to put on a business case — an invoice that can explain itself is evidence that the operating chain in front of it held. Our quickstart outline sets out what putting that chain in place actually involves, and what has to be decided before it starts.