HEINOUX Journal Portfolio

Journal

Counting what we actually use

A balance dropped and my morning report could not say why. Reading every line, not the two totals, explained it exactly.

By · · 3 min read

Counting what we actually use

On Tuesday my morning report flagged a gap it could not explain. A prepaid balance on one of the media tools I use had dropped by far more than the daily marketing run had spent. The report said so plainly and left it open. This morning I counted.

What the report saw

Every morning the run reads the balance before it spends anything, and it writes down what it spent afterwards. Sunday's report closed on one number. Tuesday's started on a much lower one. In between, Monday's run had stalled before making anything, so the drop had no owner. The report logged it as unexplained and said the likely cause was a separate piece of work, but it could not prove that.

An unexplained drop is the worst kind of number. It is not big enough to panic about and not small enough to ignore, so it tends to sit there.

How I counted it

The tool keeps a line for every job: when it ran, what kind of job it was, and what it cost. I read every line between the two reports, one at a time, instead of comparing the two totals.

The lines fell into two clusters, both on Sunday. One was late morning, one was late evening. Neither matched the daily run's shape or its schedule. They belonged to a separate piece of creative work I had going that day, outside the daily run. When I added up every line in those two clusters, plus one small job that runs on its own each morning, the total matched the gap exactly. Not roughly. Exactly.

What changed

Nothing was wrong, and nothing was lost. But for two days the business was carrying a number nobody could explain, because the spending lived in one place and the record of what it was for lived in another.

So the morning run now reads the job lines, not just the balance. Anything that does not belong to the run gets named in the report on the day, with its time and its type, instead of being parked as "unattributed".

Why this is the point of one source of truth

Every business has this in some shape. A card statement shows a charge and nobody remembers the purchase. Stock goes down and no sale explains it. The money and the reason sit in different systems, so the question gets asked at month end, when the trail is cold.

A Business Operating System ties each movement to the job that caused it, on the same record. The win is not a prettier report. It is that "where did that go?" gets answered the same day, by reading, not by guessing.

Frequently Asked Questions

What was the unexplained drop?

A prepaid balance on a media tool fell by more than the daily marketing run had spent between two morning reports. Monday's run had stalled, so the report could not say who spent the difference.

How was it explained?

By reading every job line the tool keeps, one at a time, rather than comparing two totals. Two clusters on Sunday belonged to separate creative work, and together with one small daily job they matched the gap exactly.

What changed afterwards?

The morning run now reads the individual job lines as well as the balance, and names anything outside the run on the same day, with its time and type, instead of leaving it unexplained.

Want this kind of build for your business?

I build AI systems, custom company dashboards and automation for growing businesses.

Get your autopsy Email me