Balance sheet reconciliation: How to avoid month-end surprises

Balance sheet reconciliation rarely fails loudly. It fails quietly, often through accruals rolled forward without review or a VAT control account opened too late. A monthly process should leave very little to discover at month-end.

Waiting until close turns reconciliation into a search-and-rescue operation under time pressure. Reconciling as the month moves turns close into verification, even when the team can't add headcount. This is general guidance for UK finance teams rather than a substitute for advice on your own circumstances, so it's worth checking specific statutory reporting obligations with your auditor or a qualified adviser before acting on them.

The UK regulatory backdrop that makes reconciliation a board-level concern

In the UK, reconciliation supports statutory obligations that have sharpened considerably in the last two years. The practical point for finance teams is straightforward: a reconciliation file isn't only a month-end working paper. It's part of the evidence behind the accounts, the audit, and the controls story the board may need to stand behind.

Accounts, records, and control evidence

Directors need to be satisfied that accounts give a true and fair view of the company's assets, liabilities, financial position, and profit or loss before they approve them. That requirement comes from the Companies Act 2006. Section 386 requires adequate accounting records to meet that standard, and your auditor has to give an opinion on whether you have kept them.

For fixed assets, the Large and Medium-sized Companies and Groups Regulations 2008 require you to disclose opening and closing balances and movements for each item, which makes fixed asset schedule reconciliation a statutory requirement.

Classification matters as much as completeness. Under FRS 102, the UK's principal accounting standard, you have to present current and non-current assets and liabilities separately on the balance sheet. Accurate classification depends on reconciled balances. Impairment calculations under the standard rely on a clean fixed asset schedule to get the carrying value right.

Governance pressure is rising too. The UK Corporate Governance Code is monitored by the Financial Reporting Council (FRC). It introduces Provision 29, which takes full effect for financial years beginning on or after 1 January 2026. It requires boards of premium-listed companies to make an explicit annual declaration on the effectiveness of their material internal controls as at the balance sheet date. Boards need to provide an attestation that their material controls are fit for purpose, ICAEW notes. Those controls extend beyond financial reporting into operational and compliance areas. If you are inside a listed group, monthly reconciliation gives the board evidence for that attestation.

VAT records and digital links

VAT adds another control account with its own record-keeping rules. Every VAT-registered business has to keep a VAT account recording output and input tax, and under VAT Notice 700/21 that account must show the link between the records and the figures on your return. You will need to keep records for at least six years.

Making Tax Digital (MTD) for VAT adds a constraint that catches more teams than it should. Once data is in the software you use to keep your VAT account, any further transfer between systems has to use digital links, and the rules don't permit manual transfer including copy and paste between software. The digital links requirement has applied since April 2021. Exporting figures from your VAT control account and pasting them into a bridging spreadsheet by hand creates both compliance and process risk.

Why month-end surprises usually arrive late and what causes them

Most finance teams know the feeling of opening a reconciliation early in close and finding the gap is larger than expected. The frustration comes from finding an old cause when you have little time to resolve it.

Balance sheet reconciliation means comparing the balances of every balance sheet account in your general ledger (GL) against the supporting documentation behind them. That support can include bank statements, subledger reports, invoices, loan schedules, and calculation schedules. The aim is to confirm each balance is accurate, complete, and valid before it flows into your financial statements. A bank reconciliation checks only your cash account against the bank statement. Balance sheet reconciliation covers the wider close, where unreconciled bank entries tend to cascade into everything else.

Reconciliation evidence file

Each account file should make the GL balance clear, include the supporting documentation behind it, and show that the balance has been checked for accuracy, completeness, and validity before it flows into the financial statements.

Common causes of late differences

The errors that cause month-end surprises tend to look familiar across teams. Timing differences are the most benign. Cheques issued but not cashed and deposits in transit are normal reconciling items; card charges may also post a day or two after the transaction.

Normal reconciling items accumulate into a balance that no longer ties out to anything if they aren't tracked. Subledger-to-GL mismatches are more dangerous. A sales invoice raised in the subledger but never transmitted to the GL because of a mapping issue, or a credit applied to a customer account that the GL never sees, will silently misstate receivables.

Accruals create another recurring problem. Rolling an accrued expense forward month after month without reassessing whether the obligation still exists is a common way expenses get overstated or duplicated. The same recurring mistakes show up across teams when accruals aren't recorded, reversals are missed, or an entire prepayment is posted as an immediate expense.

Suspense entries and year-end adjustments

Monthly reporting also drifts when the team relies only on year-end adjustments. Suspense accounts sit underneath all of this, and every item posted to suspense is an unanswered question. Suspense should be cleared to zero at year-end, which means you would want to identify and reallocate every entry rather than carry it forward.

Could your current process catch these before close? That single question separates teams that spend close verifying balances from teams that spend it hunting for causes under pressure.

Control points that create risk

Account data spread across ledgers, banking exports, subledgers, and working papers creates transfer points that need controls. Each handoff has to prevent omissions, duplicates, and mismatched records. Manual spreadsheet matching and ambiguous ownership compound the problem, especially when reconciliation waits until the close window opens. Issues then surface together, exactly when you have the least time to deal with them.

Building a monthly process that runs without a scramble

The teams that close calmly move the work earlier and remove ambiguity about who does what. A practical place to begin is with high-volume accounts, then ordering the rest by risk. Named account ownership keeps work moving without extra headcount.

Reconcile high-volume accounts throughout the month

For cash and card accounts with high transaction volumes, a daily or weekly reconciliation rhythm through the month is one of the most practical changes you can make. Small checks prevent a large exception queue at close. When you reconcile your bank account every few days, the final month-end step confirms that nothing moved since you last checked. You catch a duplicated payment or a missing deposit while the context is still fresh, instead of reverse-engineering it weeks later.

Spend data quality matters here. Reconciliation is only as fast as the data flowing into it is clean, and most reconciliation errors begin upstream, with a mistyped expense amount or a transaction that was never categorised. The documentation behind card and expense balances needs to exist before close. Otherwise, the team has to chase that evidence during it.

Work the accounts in risk order

Some accounts deserve more attention than others each month. A risk-based approach starts with the accounts most likely to contain compounding errors and most material to the statements. Bank accounts come first, because unreconciled bank entries cascade. Receivables and payables follow, then the accounts that genuinely move month to month.

A practical sequence for most mid-market teams looks like this:

• Cash and bank, reconciled to statements, ideally already current from your continuous routine

• Company cards and charge accounts, matched to statements

• Accounts payable and receivable, with the subledger agreed to the GL and checked for duplicate or missing entries

• VAT control account, reconciled to the return and HMRC records

• Accruals and prepayments, each one reassessed for whether the obligation still exists before it is carried forward

• Fixed assets, where no third-party statement exists to reconcile against, so a manual check confirming each asset exists is unavoidable

• Intercompany balances, cleared and agreed across entities

Low-risk, low-movement accounts can often sit outside the most pressured part of close. A dormant equity account whose balance hasn't changed in a year doesn't need reconciling under deadline pressure.

Give every account a named preparer and a named reviewer

Ambiguous ownership is where tasks fall through the cracks. Every reconciliation needs a named owner and a due date. A reviewer who isn't the preparer should check the work. This matters for more than tidiness. Segregation of duties is a core internal control: ideally, different people record transactions and reconcile them, and someone independent reviews, dates, and signs the reconciliation.

A three-person finance team may have one person who genuinely handles everything. Full segregation often falls outside the mid-market team's reality, and pretending otherwise helps no one. Compensating controls then matter: a secondary review of the reconciliation, periodic independent reperformance of the whole thing, and closer monitoring of payment transactions.

The first few months of insisting on a second pair of eyes will feel like friction you don't have time for. A second pair of eyes can catch the error before your auditor sees it. An error found by your auditor rather than by you points to a weakness in your control environment, which is precisely the thing Provision 29 now asks boards to attest against.

A pre-close routine that defuses the close before it starts

A calm close usually depends on work done before the period ends. In the final days of the month, one useful routine is to pay outstanding bills and send remaining invoices so the accounts payable (AP) and accounts receivable (AR) positions are stable. The team can then confirm that transactions are recorded in the correct period, reconcile key accounts ahead of time, and clear suspense and unidentified items while the context is still fresh.

Pre-close self-check

Before you lock the period, check whether the team has reconciled every balance sheet account, including zero balances. Confirm that ending balances match the GL and the financial statements, supporting documentation has been obtained and reviewed, and any unusual variances have been explained.

Clean answers mean the close file is ready for review. Unresolved answers mean the surprise is already in the building.

Does your current month-end actually have a pre-close phase, or does the work simply start when the period ends? For most teams the honest answer is the latter.

Where automation earns its place in reconciliation

Manual reconciliation scales badly. Manual matching and disconnected systems feed the late-cycle scramble.

Automation earns its place by clearing high-confidence matches automatically so your team only looks at exceptions. It also creates timestamped records of who reconciled what and when, and flags balances that changed so reviewers can see the likely driver. Reviewers get clearer evidence, and exceptions are easier to see before the period ends.

It's worth treating headline performance figures as directional, because most reconciliation performance statistics come from vendor case studies rather than independent research.

Mid-market teams face a real constraint: they need to achieve strong controls with a small team and without full segregation of duties. Clean upstream spend data does disproportionate work here. Spendesk is an all-in-one spend management platform consolidating company cards, expense management, accounts payable, procurement, and budgeting, which means transaction data is captured with receipts and coding attached at source rather than reconstructed weeks later. Invoice data is extracted on upload, and duplicates are flagged before they reach your payables queue, so less manual data entry takes time directly out of the part of close most likely to introduce error.

For example, Codat came to Spendesk wanting to take the manual effort out of close. The team cut its month-end process from a full day to 30 minutes, with everything it needs sitting in one place. That's the shape of the gain when the evidence is clean before reconciliation starts, rather than gathered during it.

What a surprise-free close actually depends on

The difference that appears at close usually started as a small unanswered question earlier in the month. A steady reconciliation rhythm keeps those questions visible while there's still time to resolve them.

Continuous reconciliation of high-volume accounts, a risk-based order of work, named owners with independent reviewers, and a genuine pre-close routine turn month-end into a confirmation exercise. The regulatory backdrop, covering the Companies Act's true and fair view, FRC Provision 29, and MTD's digital links, only raises the stakes on getting there.

For finance teams trying to make that shift without adding headcount, upstream data matters as much as the reconciliation itself. The quiet failures the close surfaces, the accrual rolled forward without review or the control account opened too late, almost always trace back to evidence that was never captured cleanly at source. See how Spendesk captures receipts, coding, and invoice data at the point of spend, so your team can spend month-end confirming balances rather than uncovering old problems.

Frequently asked questions about balance sheet reconciliation

Which related process covers company card and employee expense balances?

Balance sheet reconciliation confirms GL balances against supporting documentation. Card and employee expense balances often need a more specific expense reconciliation workflow first, so the balance sheet file starts with cleaner evidence.

Where should teams look if supplier invoice exceptions keep delaying AP?

Recurring supplier invoice exceptions usually point upstream. Finance teams can strengthen the AP stage with clearer three-way matching, better invoice data extraction, and duplicate checks before payables reach close.

What kind of software supports a wider reconciliation programme?

Teams may look at account reconciliation software for matching and review workflows, bookkeeping automation for reducing manual preparation, and accounting automation for cleaner coded data going into close.

How can finance teams connect reconciliation work to the broader month-end close?

Reconciliation is one part of the wider close. A month-end close checklist can help finance teams map reconciliation work against the rest of the close routine, so account review doesn't sit apart from the final reporting process.