long-arrow-left
Back to the Blog

The Numbers Match. The Controls Don’t.

Cooper Barnard-Brown
June 24, 2026

A reconciliation can tie out and still leave the business exposed.

That is the uncomfortable part. The ledger agrees to the bank. The reviewer signs off. The month closes. On paper, the control looks complete.

But completion is not the same as control.

The real risk sits in what had to be accepted along the way: old reconciling items, recurring timing differences, unclear ownership, manual workarounds, and spreadsheets that only one person really understands. These issues rarely feel urgent in isolation. They become dangerous because they are normalised over time.

This is reconciliation debt: unresolved control weakness that keeps getting carried forward so the business can keep reporting.

For finance leaders, the close should be more than a deadline. It should be a signal. If the same items keep rolling forward, if the same accounts need manual adjustment, or if the same explanations appear every month, the reconciliation is telling the organisation something important.

The numbers may match. The controls may not.

Why should I care?

Most large organisations have reconciliation noise. Timing differences happen. Systems do not always speak cleanly to each other. Month-end is busy, and materiality matters.

The problem is not the existence of exceptions. The problem is when exceptions become permanent.

A $10,000 difference may be immaterial in one month. If it appears every month, across multiple entities, with no clear owner and no root cause analysis, it has become something else. It is no longer just a reconciling item. It is weak process discipline showing up in finance.

The Australian National Audit Office reported a bank reconciliation issue at the Department of Veterans’ Affairs for the period ended 30 June 2024, including $714.5 million in unpresented payments and $586.7 million in un-receipted deposits, with no breakdowns available to support those balances. Its analysis identified a $64.2 million adjustment to reported cash and cash equivalents.

That example matters because it came from a large public entity, not a small business with informal controls.

Scale does not remove reconciliation debt. It can give it more places to hide.

Reconciliation debt usually builds upstream.

Poor supplier data creates payment exceptions. Late receipting creates accrual noise. Fragmented bank feeds make matching harder. Intercompany charges get pushed through after the fact. Payroll changes are processed without clean governance. Project codes are updated late. Contract terms and billing data do not line up.

Finance then becomes the clean-up crew.

That cost does not always appear as a single line item. It shows up as overtime, rework, delayed reporting, audit friction, conservative provisions, unexplained variances, and senior people spending time on low-value investigation.

Deloitte’s controllership guidance points to a single standardised source of truth and a simplified system landscape as important foundations of a stronger close. PwC’s close-to-report guidance similarly emphasises accuracy, accountability, control, standardisation, bottleneck removal, and alignment with stakeholder needs.

The lesson is straightforward. A better close is not created by asking finance to work harder. It comes from better ownership, cleaner data, fewer manual hand-offs, and earlier visibility into exceptions.

That visibility needs to exist before the close, not only after it.

What you can do

The practical move is to treat reconciliations as a control signal, not an administrative task. That distinction matters because a control has to work in practice, not just exist on paper. The Australian Taxation Office’s guidance on testing controls separates design effectiveness from operational effectiveness, while Australian Prudential Regulation Authority Prudential Standard CPS 230 requires regulated entities to manage operational risk with effective internal controls, monitoring and remediation. Different contexts, same lesson: evidence of control matters more than the existence of a checklist.

Start with a short, disciplined review:

  1. Identify reconciliations that are late, manually adjusted, or repeatedly explained as “timing”.
  2. Separate new exceptions from ageing or recurring items.
  3. Assign a clear owner to every material unresolved difference.
  4. Track whether the root cause sits in finance, procurement, payroll, banking, billing, contracts, operations, or a system hand-off.
  5. Require reviewer challenge where items keep rolling forward.
  6. Use the pattern of exceptions to fix the upstream process, not just the month-end file.

This is where RedOwl’s core value matters. RedOwl captures, preserves and leverages organisational memory to deliver real-time governance. In practice, that means decisions, exceptions, approvals, patterns and context are not trapped in inboxes, spreadsheets or individual memory.

A human still needs to apply judgement. The point is to give that person better evidence, earlier.

Reconciliation debt is easier to manage when the organisation can see where exceptions came from, who touched them, what changed, what was approved, and whether the same issue has appeared before.

The best question is not only, “Did the reconciliation get done?”

It is, “What did we have to tolerate to make it match?”

Get in touch with the RedOwl team

Whether you have a question or need support, reach out and we’ll connect you with the right person.

Contact us