Reporting and finance

Why month-end reports break

8 min read

The five most common causes of reports that disagree with each other, and how to design them out.

The problem

It is the third business day. Finance sends a revenue number. Operations sends a different one, for the same month, off the same business. Now two capable people spend an afternoon working out which one is right, and the answer is usually that neither is wrong.

Reports that disagree are rarely an arithmetic mistake. They are a design problem. Each report quietly made its own choices about what to count, when to pull it, where to get it and what to adjust. Those choices were never written down, so nobody sees them until the numbers collide.

The fix is not more checking after the fact. It is making those choices once, in one place, so the reports cannot drift apart.

The five causes

Each cause answers a different question about a number. That is why they are easy to tell apart, and why one report can fail on several at once.

DefinitionsWhat is counted
TimingWhen it was pulled
SourceWhere it came from
Copy-pasteHow it travelled
OverridesWhat was changed on top

This is why a $36,700 gap is almost never one mistake. It is usually a handful of small, reasonable choices that added up.

Try it

Here are two reports for the same month. The finance deck shows $1,284,000 of revenue and the operations dashboard shows $1,247,300. Each cause below explains part of the gap. Tick a fix to design that cause out and watch the dashboard close in on the deck.

Close the gap

Tick the fixes you have made.

Green on the dashboard bar is gap you have designed out. Amber dashed is gap that remains.

No single fix gets you there. The biggest one, definitions, only explains about a third of the gap. That is the point: you need all five, and you need them in one place.

How each one shows up

Use this table to recognise the cause and decide where the fix belongs.

CauseHow it shows upDesign it out
DefinitionsSame label, different rules. One report nets out returns and the other does not. Headcount with and without contractors.Write one definition per metric, name an owner, and print the rule in a note on every report.
TimingOne report is pulled on day 3 and another on day 5. Late entries land in only one.Pick a cutoff date, print it on every report, and refresh them all from the same snapshot.
SourceOne report comes from the ledger, another from an operational system or a different extract.Build every report from one source, or reconcile the sources to a control total each month.
Copy-pasteA number pasted from last month's file looks right until something changes upstream.Link to the data. If a value must be pasted, label it and add a check that flags when it goes stale.
OverridesAn accrual or correction lives in a side file, so only one report sees it.Record adjustments as labeled rows in the data, with a reason and an owner.

Find your own gap in an hour

You do not need to fix everything at once. Pick one disagreement and walk it through.

  1. Pick one number that two reports disagree on. Start with a single metric, not the whole package.
  2. Put both numbers side by side with their as-of dates and their sources. Sometimes the gap closes right here.
  3. Walk the difference through the five causes. Size each one from the data, the same way you would for a variance bridge. Whatever is left over is unexplained, and you show it as such.
  4. Fix the biggest cause at its source. Changing one report to match the other only moves the disagreement. Changing the shared definition or the data removes it.

Two cells worth adding to every report

These cost a minute to add and answer the first two questions anyone asks. Assume SourceName, AsOfDate and ControlTotal are named cells, and your data sits in a table called Data.

="Source: "&SourceName&" | As of "&TEXT(AsOfDate,"mmm d, yyyy")

A stamp that prints where the numbers came from and when they were pulled.

=IF(ABS(SUM(Data[Amount])-ControlTotal)<0.005,"Ties to control total","DOES NOT TIE")

A control check against the figure in the source system. If the report drifts from it, the cell says so before anyone else notices.

A report you can defend

  • Every metric has one written definition and an owner.
  • Every report prints its as-of date and its source.
  • Numbers are linked, not pasted.
  • Adjustments live in the data as labeled rows, not in a file beside it.
  • One source of truth feeds many views.

Reports that never quite agree?

We trace the gap, fix it at the source and build monthly reporting that ties out every time. Start with a free 30 minute strategy session.

Book a free strategy session