Every reporting cycle, finance adjusts a number that operations already reported differently. A regional lead manually corrects a figure that the CRM captured one way and the ERP captured another. Someone in the CFO’s team spends half a day rebuilding a board pack slide because the source data shifted between Thursday and Monday.
None of this is logged as reconciliation. It’s logged as reporting. Or governance. Or “business as usual.” But it is reconciliation — the quiet, manual process of making numbers agree when the systems that produced them don’t.
The cost is significant and almost entirely unmeasured. Not because it’s hard to measure, but because most organisations don’t recognise it as a discrete process. It’s distributed across teams, embedded in workflows, and accepted as the price of operating at scale.
It’s not a reporting problem
The instinct is to fix reconciliation at the reporting layer. Better dashboards. Automated data pipelines. A single source of truth. These interventions sometimes help, but they rarely resolve the underlying issue — because the underlying issue isn’t in reporting. It’s in the architecture beneath it.
When two systems capture the same transaction differently — different timestamps, different categorisations, different rounding rules — every downstream report inherits that discrepancy. No amount of dashboard engineering will reconcile what was never aligned at the source.
This is a deterministic layer problem. The operational systems where data originates are producing inconsistent signals, and everything above them is compensating.
The compounding effect
Reconciliation doesn’t just consume time. It erodes confidence. When a CFO asks why this quarter’s number doesn’t match what was reported last month, and the answer is a five-minute explanation of data timing and source system logic, something breaks. Not the number — the trust.
Over time, leadership learns to treat reports as starting points for discussion rather than foundations for decisions. The board pack becomes a negotiation. Strategic reviews become alignment exercises. Decision-making slows, not because the decisions are harder, but because the information beneath them requires interpretation before it can be trusted.
This is the real cost of reconciliation: not the hours spent fixing numbers, but the confidence lost in the numbers themselves.
Measuring the unmeasured
The first step is recognising reconciliation as a process — one that can be mapped, costed, and architecturally addressed. In our diagnostic work, we routinely find that reconciliation overhead accounts for 15–30% of the time senior finance and operations teams spend on reporting. Not because the teams are inefficient, but because the architecture makes efficiency impossible.
The second step is tracing each reconciliation loop back to its origin. Most lead back to the deterministic layer: a system integration that was never completed, a data model mismatch that was papered over with a manual bridge, a categorisation that means one thing in the ERP and another in the CRM.
The third step is the one most organisations skip: fixing the architecture instead of the report. Stabilising the source systems so that the signals they emit are consistent before they reach the teams who interpret them.
Reconciliation is not a cost of doing business. It’s a symptom of architectural debt — and like all debt, it compounds until you address it structurally.
If reconciliation is consuming your leadership bandwidth, we should talk.
Begin a Conversation