The Cost of Reconciliation

Reconciliation is one of finance's oldest comfort words.

Two numbers do not agree. We investigate, identify the difference, make the necessary adjustment and reconcile them. The control has worked. The numbers agree. Everyone moves on.

Until next month.

The same reconciliation happens again.

When a control becomes a process

There is nothing inherently wrong with reconciliation. Bank accounts need it. Intercompany balances need it. Different systems, cut-off periods and accounting treatments will always create legitimate reasons for numbers to differ.

The question is not whether finance should reconcile.

The question is what happens when reconciliation becomes the normal way in which information is made reliable.

Consider a familiar month-end situation. Numbers arrive from different entities, systems and teams. Finance compares them, identifies mismatches, follows up for explanations, passes adjustments and finally produces a number everyone accepts.

The close is completed.
The reconciliation is cleared.
But what exactly was fixed?

Often, only the difference.

The architecture that created the difference remains untouched.

The comfort of closure

This is where reconciliation can become deceptive.

A completed reconciliation gives finance something extremely valuable: closure. There is a satisfying movement from disagreement to agreement, from unexplained to explained, from open item to closed item.

But closure can hide repetition.

If the same categories of differences appear every month, finance is no longer merely performing a control. It may be operating a compensating process for something upstream that has never been resolved.

A mapping problem survives because finance reconciles it. A data-definition problem survives because someone adjusts for it. A system interface issue survives because a spreadsheet bridges it. An intercompany process remains weak because teams know the differences will eventually be sorted out during close.

The better finance becomes at reconciling, paradoxically, the easier some underlying problems become to tolerate.

The Invisible cost

The cost is not limited to the hours spent matching numbers.

Reconciliation consumes attention. Experienced finance professionals spend time investigating differences rather than interpreting outcomes. Close calendars build in buffers because everyone expects mismatches. Knowledge accumulates around individuals who know which differences are "normal" and how they are usually resolved.

Eventually, the organisation starts measuring the efficiency of reconciliation instead of questioning its necessity.

That is an important distinction.

Reducing a reconciliation from four hours to two is an improvement.

Eliminating the reason it repeatedly exists may be transformation.

Control or dependency?

Not every recurring reconciliation should disappear. Some are essential controls and should remain precisely because independent verification matters.

But finance leaders should know which kind they are looking at.

Is this reconciliation validating a process that is fundamentally sound? Or is it compensating for a process that is fundamentally fragmented?

The spreadsheet may look identical.

The organisational implications are very different.

Perhaps that is the question worth adding to the close review. Not simply, "Are all reconciliations complete?" but occasionally, "Why do we still need this one?"

Because a finance function can become extremely efficient at correcting differences it should have stopped creating years ago.

Ledger Note

Reconciliation is a good control. It becomes an expensive operating model when we stop asking why there is something to reconcile.

The author is the Director & co-founder of FinAlyzer, where he focuses on building finance systems that scale with complexity. He works closely with CFOs and finance teams to design workflows for close, consolidation and reporting that prioritize structure, traceability and long-term trust.