Doing nothing is not neutral

Every month without transaction-level reconciliation makes the next one harder. Where the cost of waiting shows up, and what breaking it looks like in weeks, months and quarters.

The Actuals teamActuals · 2 min read

Standing still feels safe. The close gets done, a little later each month, with a few more manual fixes than the one before. It holds, until month end lands on a volume spike, or an auditor asks a question no one can answer.

For high-volume businesses, waiting is a decision too. Every month without transaction-level reconciliation adds another month of unexplained balances, manual fixes and firefighting instead of analysis. The problem does not stay the same size. It compounds.

Where the cost shows up

The cost of inertia rarely appears as one line. It shows up in four places.

  • Operational drag. People spend their days on reconciliation and manual fixes. Excel files grow, insight gets worse and morale drops.
  • Financial leakage. Unexplained balances, late write-offs and ad-hoc corrections quietly eat into margins and add friction at the audit.
  • Payments risk. Small mismatches turn into incidents. A new PSP or a product change brings errors to light late, when they are expensive to fix.
  • Credibility. Executives and auditors need numbers they can trace. Without that, trust in the reported figures erodes.

What it looked like at one company

A publicly listed betting company handled millions of transactions a day across several payment providers. Then an acquisition multiplied its volumes roughly a hundredfold, almost overnight. Millions moved into transitory accounts with no clear audit trail. The ERP could not keep up, spreadsheets took minutes to open, and mismatches went unnoticed until they became real problems.

Once reconciliation moved to transaction level and was automated, mismatches surfaced fast. Developers could fix the root causes before they grew. That change came within weeks.

Weeks, months, quarters

Breaking inertia does not need a big programme. It needs a target and the right order of work.

  • Weeks. Stop the worst manual work, get visibility and catch the largest mismatches. A short pilot shows the impact.
  • Months. Tighten the month-end close, reduce manual controls and build a process you can repeat.
  • Quarters. Automate journalising end to end and scale without hidden costs.

Underneath that timeline sits one rule. Bring transactions, payments, settlements and bank flows into one model at transaction level, and reconcile there. Keep the exceptions apart in transparent transitory accounts. Post to the ERP only once the transactions are clean and the exceptions are handled.

The timeline is yours to pick

Postponing the fix buys a calm month now and more complexity later. Whether you plan for weeks, months or quarters, that choice decides the outcome.

A step that takes 15 minutes: the Actuals scan shows where your numbers first stop matching.

In practiceHow many days of your close go to explaining differences?

Written by

The Actuals teamActuals