Skip to content
Ninety days, eight deliverablesSee how
Nightshift

Measurement

Revenue computed at the wrong grain

Calculate revenue from invoice headers instead of the underlying postings and you fold in things that are not revenue, then find a third of it will not attribute to anything.

August 5, 20266 min read

The shortcut

Invoice headers are convenient. They are one row per document, they carry a total, and they are usually the easiest thing to extract. Building revenue from them is the default first move.

It also pulls in items that are not revenue, and it throws away the dimension you most want to slice by, because the attribution lives on the lines and not the header.

What it costs you

On one estate this left a material share of revenue that could not be assigned to any division at all. The temptation is to distribute that share proportionally so the chart looks complete.

The honest move is to show it. A number that admits its own gap is more useful than one that hides it, and the gap itself is usually the argument for extending the extract.

The fix pays for several problems at once

Bringing line-level postings into the extract resolved the attribution gap, the tax-basis inconsistency between two marts, and a days-to-pay measure that had been unavailable. One extraction change closed four findings.

It is worth looking for that shape of fix before working through defects one at a time.

Want this against your own numbers?

A scoping call works out which measures are worth baselining and whether your systems can actually be read.

Let’s chat

More field notes

MeasurementAugust 8, 2026· 4 min read

Count from the catalog, not from the page

A screen reported seven products selling below cost. The catalog held twenty-six. The bug was not in the calculation, it was in what the count was computed over.

Read more

Start with the numbers you cannot see today

Half an hour works out which measures are worth baselining and whether your systems can be read.