Hands reviewing a balance sheet over a desk
Close · Rationalisation

The Reconciliations Nobody Would Notice

Reconciliations get added when something goes wrong and are almost never removed when the risk disappears. The portfolio accumulates, and the effort goes to the wrong accounts.

Key Takeaways
  • Reconciliation portfolios grow by addition after incidents and are rarely reviewed for continued relevance.
  • The result is effort spread evenly across accounts with very different risk profiles.
  • The useful test is what would go undetected if a given reconciliation stopped, which is answerable per account.
  • Some reconciliations exist because another control was missing, and fixing that control removes the need entirely.
  • ChatFin makes low risk reconciliations effectively free, which changes the calculation rather than settling it.

Reconciliation portfolios have a characteristic history. Something went wrong, a reconciliation was added to catch it, and it has been performed every month since by people who were not there when the decision was made.

That is a reasonable way to accumulate controls and a poor way to allocate effort, because nothing ever removes an item from the list.

The consequence is a portfolio where a high risk account and a dormant one receive similar attention, and where the total effort is large enough that the high risk accounts get less scrutiny than they deserve.

Reconciliation
Close
Risk
Rationalisation
Controls
ChatFin
01

The test that works

Asking whether a reconciliation is useful produces a defensive answer, because the person performing it reasonably assumes the question is about their work.

A better question is what would go undetected if this reconciliation stopped, and how long it would take for that thing to surface some other way.

For a high risk account the answer is specific and uncomfortable. For an inherited one the answer is frequently that nothing would go undetected, or that anything material would be caught within days by another control.

That reframing matters because it makes the assessment about risk rather than about effort, and it produces answers people are willing to give honestly.

The framing also protects the exercise from becoming a cost reduction conversation. A rationalisation presented as risk allocation gets cooperation from the people who perform the work. The same exercise presented as efficiency gets defensive answers and an inventory that survives intact.

02

What a reconciliation is worth

Four factors determine whether a reconciliation earns its place, and they are worth scoring rather than debating.

Applied across a portfolio they sort it quickly, and the scoring conversation is more productive than an open discussion about whether each item is necessary:

Volume and value of activity. A dormant account and a high throughput one carry entirely different exposure regardless of balance.
Whether another control would catch it. Many reconciliations duplicate a check performed elsewhere, which nobody has noticed because both were added separately.
Time to detection through another route. If a problem would surface within days anyway, a monthly reconciliation adds little.
History of findings. A reconciliation that has produced nothing in three years is either protecting against something that stopped happening or is not looking properly.
03

Two reasons to keep a reconciliation with no findings

A clean history is not automatically a reason to stop, and distinguishing the two cases prevents removing something that is working.

The question is whether the absence of findings is evidence of safety or evidence of blindness, and the person performing the reconciliation usually knows which it is if they are asked directly.

Keep it

It is preventing the problem

The reconciliation is known to be performed, and that knowledge deters the behaviour it was designed to catch. Removing it removes the deterrent, not just the detection.

Question it

It cannot detect the problem

No findings because the method would not identify the issue even if it occurred. A reconciliation that ties by construction rather than by verification produces clean results indefinitely.

A finance professional working through receipts at a desk
Added after an incident, performed indefinitely by people who were not there.
04

Sorting the portfolio

The output is a portfolio sorted into three groups, with different treatment for each.

Most items land in the middle, which is the group where the treatment decision has changed most in the last few years.

GroupTreatmentEffect
High risk, high valueMore attention than currently, with deeper investigation of differencesWhere the effort released elsewhere should go
Routine, low judgementAutomated or reduced in frequency, with exception based reviewThe large middle, where most current effort sits
Inherited, no longer relevantRemoved, with the reasoning documentedSmall in number and the removal is what makes the exercise credible

Document the removal reasoning. Nobody remembers why an item was removed and somebody will ask.

05

Some reconciliations are a symptom

A category worth identifying separately is the reconciliation that exists because a control is missing somewhere upstream.

A monthly reconciliation catching coding errors is compensating for the absence of validation at the point of entry. One catching duplicate payments is compensating for a weak duplicate check. In both cases the reconciliation is the visible symptom of a gap elsewhere.

Fixing the upstream control removes the need for the reconciliation entirely, which is a considerably better outcome than automating it. It is also easy to miss, because the reconciliation works and nobody traces back to why it is necessary.

A reconciliation catching the same error every month is a symptom. Fix the control upstream and the reconciliation stops being needed.
"

Ask what would go undetected if it stopped. People answer that question honestly.

ChatFin
06

Running the review

Four steps, and the third is the one that makes it worth repeating.

Inventory the portfolio with findings history

Every reconciliation, its frequency, its owner and what it has found over the last three years. The history is the informative column.

Apply the detection test

What would go undetected if this stopped, and how long before it surfaced another way. Ask the person who performs it, framed as risk rather than as effort.

Identify the symptoms

Reconciliations compensating for a missing upstream control. Fixing the control is better than automating the reconciliation.

Reallocate, do not just reduce

Effort released should move to the high risk accounts rather than disappearing, or the exercise reads as a headcount conversation.

A woman reviewing documents with a calculator
Three years of findings history is the informative column in the inventory.
07

How ChatFin changes the calculation

Rationalising a portfolio is partly a cost decision, and automation changes one side of it substantially.

ChatFin performs reconciliation work across full populations continuously in NetSuite, SAP Business One, JD Edwards, Acumatica, Dynamics 365 and Sage Intacct, matching, grouping and isolating exceptions with reasons attached. For routine, low judgement reconciliations the marginal cost of performing one falls sharply.

That does not settle the question. A reconciliation with no detection value is still not worth performing, however cheap it becomes, because it produces output somebody has to look at.

What it does change is the middle group. Reconciliations that were candidates for reduction on cost grounds can be retained and performed more thoroughly, while the human effort released moves to the accounts where judgement is what is needed.

Full population rather than sampling. Routine reconciliations performed completely rather than partially.
Exceptions with reasons. Human attention goes to differences that need judgement, not to the matching.
Marginal cost falls. Which changes the treatment of the middle group without justifying reconciliations that detect nothing.
Before you budget for it

AI Cost Estimator for the CFO Office

Four inputs, a first year cost range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

How do we decide whether a reconciliation is worth performing?

Ask what would go undetected if it stopped and how long before that surfaced another way. It reframes the assessment around risk rather than effort, which produces more honest answers from the people who perform them.

Is a reconciliation with no findings a candidate for removal?

Not automatically. It may be preventing the problem through its known existence, or it may be unable to detect the issue by construction. Establishing which case applies is the necessary step before removing anything.

What is the most overlooked category?

Reconciliations that exist because an upstream control is missing. They catch the same error repeatedly, which looks like a working control and is actually a symptom. Fixing the upstream gap removes the need entirely.

Does automation make this exercise unnecessary?

No. It lowers the cost of performing routine reconciliations, which changes the treatment of the middle group. A reconciliation that detects nothing still produces output somebody has to review, so the rationalisation question remains.

General information only. It is not legal, accounting or tax advice, and rules change. Check your own position with your advisers before acting on it.

One question per reconciliation

Ask what would go undetected if it stopped.

Portfolios grow by addition and are rarely pruned. Scoring by volume, duplication, time to detection and findings history sorts them quickly and moves effort to where it matters.

ChatFin lowers the cost of the routine middle group, so effort released moves to accounts that need judgement rather than disappearing.

Book a Demo
See the platform
Take it to your own ledger

Move the reconciliation effort to where judgement is needed.

Bring your reconciliation inventory. We will show which are candidates for full population automation and what the exception queue would look like.

✓Runs on the ERP you already have, on the version you already run
✓Every posting prepared as a draft that a named person approves
✓Prompt, evidence and prepared payload logged for the audit file
Schedule a Demo
Confidential & private
Photos by Karola G, Mikhail Nilov and Pavel Danilyuk, free to use under the Pexels License (commercial use, no attribution required). Diagrams and product imagery © ChatFin.