Where do your billing rules live?

Your billing rules live in one of two places: in the system, or in people’s heads. Most firms have not chosen which, and have therefore chosen the second.

The test is quick. Ask two experienced people, separately, whether a particular category of time is billable on a particular engagement. If the answers differ, or if either answer begins with an explanation of the history, the rule is not in the system.

The mistaken diagnosis

The questions that come out of this are treated as finance questions, because finance is where they surface. Who approved this rate. Is this time billable. Why does WIP not match delivery. Can we send the invoice yet.

None of those are finance questions. Each one is a signal that the system is not carrying contract rules through the job, and that judgement is therefore being applied at the most expensive point in the value chain — the invoice, at the end of the month, by people who were not present when the commitment was made.

Judgement is not the problem. Judgement applied late, repeatedly, by whoever happens to be available, is.

The heroics that hide it

Firms in this position rarely feel broken, because a small number of highly capable people are absorbing the difference.

They remember what was promised. They decode the WIP. They rescue the invoice. They explain the spreadsheet, and they quietly reconcile the gap between what sales sold, what delivery did, and what finance can defensibly bill. From the outside it reads as capability, and it genuinely is — these are usually the best people in the firm.

It stops reading as capability at scale. When the heroics become the operating model, the cost shows up as slower billing, margin leakage, administrative drag, tired senior people, and project financials that leaders do not fully trust. It also becomes a concentration risk: the operating knowledge is held by individuals who can resign, go on leave, or simply be busy in the week the invoices are due.

The tell is not the number of hours those people spend. It is that nobody else can do what they do, and nobody has written down why.

What putting the rules in the system means

Not a policy document. A rule the system applies the same way every time, attached to the engagement it governs.

Contract terms, rate cards, approval thresholds and the conditions under which work becomes billable sit on the same governed job record as the work, from the point the engagement is quoted. Time and cost entries inherit those rules rather than being classified afterwards. Approval is a state on the record, not an email. Control gates hold an invoice that is not yet ready, with the reason held against the item rather than in someone’s memory. Each invoice line links back to its source records and the contract term that permits it, so a billing question is answered by looking rather than by convening.

The part of DAY ONE that does this is the invoicing engine, where traceability runs back to an individual timesheet record — described further on our invoicing and WIP governance page. 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

The cost is not the configuration. It is the decisions the configuration forces.

Writing billing rules down means resolving the ambiguous cases in advance — the travel time, the rework caused by the client, the junior hour billed at a senior rate because that is what was quoted, the goodwill discount that has been applied for so long it is now expected. Those conversations are uncomfortable, they involve people who disagree, and they happen before any benefit is visible. Some firms will decide the flexibility of deciding case by case is worth more than the consistency, and for a firm with a handful of long-standing clients and one experienced biller, they may be right.

There is a second cost that is easy to miss. Making the rules explicit removes discretion from experienced people who have been exercising it well. Some of them will experience that as being trusted less, and the honest answer is that it is not about trust — it is about the firm being able to operate when they are not there. That still needs saying out loud rather than being left to be inferred.

And a limit: encoding rules does not fix rules that are wrong. A firm that has been systematically under-pricing will find the system applies the under-pricing consistently. Consistency exposes the pricing question; it does not answer it.

Where the rules are set, and where they are tested

Rules enter the chain at the quote and are tested at the invoice, which is why the two ends have to be the same record rather than two systems reconciled by a person. Where they are set is covered on our scoping and quoting page. Whether they held is legible in the WIP position, which is the difference between a register and an argument.

A short exercise

Write down the ten billing questions your finance team asked delivery last month. For each, note whether the answer existed anywhere other than in a person’s recollection.

The proportion that did not is the size of the problem, and it is also the list of rules worth encoding first. Fixing this is not a matter of asking capable people to work harder or to document more thoroughly in their own time. It is a matter of moving the judgement to the point where it is cheap — the beginning — and letting the system carry it forward, so commercial truth stops depending on memory, spreadsheets and the availability of the person who remembers. Our quickstart outline sets out what that involves and what has to be decided before it starts.