Balance Sheet Reconciliation Guide for Modern Teams

It's day six of close. Two balance sheet reconciliations are still red on the dashboard, the controller is chasing a late bank feed, and the audit pack is due on Tuesday. The spreadsheet says the figures are nearly there, but nobody can explain which source supports the remaining difference or who approved the adjustment.

That situation is common because teams often treat reconciliation as a month-end chore. A stronger approach treats it as an evidence chain, designed in Odoo 19 Accounting so every reported balance can be traced, reviewed and supported without rebuilding the story under pressure.

Table of Contents

• What Balance Sheet Reconciliation Actually Means
• Why Reconciliation Is a Legal and Audit Control in the UK
  •      ->What auditors expect to see
• Common Account Types You Need to Reconcile
• A Practical Month-End Reconciliation Checklist
  •      ->T-5 to T-3 preparation
  •      ->T-2 to close
  •      ->Day +3 follow-up
• Common Pitfalls and How to Prevent Them
• KPIs and Evidence Chains That Prove Reconciliation Works
• Running Reconciliation in Odoo and Adding AI Assist
  •      ->A controlled matching sequence
  •      ->Add AI without surrendering judgement
• Rollout Plan and FAQ for Finance Leaders
  •      ->Frequently asked questions

What Balance Sheet Reconciliation Actually Means

Balance sheet reconciliation is the process of proving that a general ledger balance agrees with the records and documents that should support it. The ledger is one layer. The sub-ledger or external source is another, such as a bank statement, supplier portal, payroll register or fixed asset register. The third layer is the supporting trail, including an invoice, contract, statement, payment record or calculation schedule.

The important point is that reconciliation isn't just matching transactions. A proof-of-cash exercise may compare an internal cash record with a bank statement. A transaction-matching exercise may pair a payment with an invoice. Balance sheet reconciliation goes further by asking whether the ending balance is complete, correctly classified and supported.

A reliable evidence chain follows this route:

1. Trial balance to account balance. Confirm which general ledger accounts make up the reported line.
2. Account balance to source record. Agree the ledger with the relevant sub-ledger, bank statement or external schedule.
3. Source record to document. Retain the invoice, contract, statement, register or approval that explains the balance.
4. Difference to resolution. Record the reconciling item, owner, explanation and corrective action.
5. Review to certification. Have a second person challenge the conclusion and sign off the evidence.

In Odoo 19, that chain can begin with the general ledger and continue through bank statements, partner ledgers, payment matching and document attachments. The Odoo suspense account guidance is particularly useful when a difference has been posted temporarily but hasn't yet been explained.

Practical rule: A reconciliation is complete only when another person can reproduce your conclusion from the attached evidence.

This is why a well-designed process can help teams streamline finance operations. The objective isn't merely to clear a dashboard. It's to let a controller answer an auditor's question by opening the reconciliation, viewing the source transaction, reading the explanation and checking the approval in one controlled workflow.

Why Reconciliation Is a Legal and Audit Control in the UK

UK companies don't reconcile balance sheet accounts merely because finance teams prefer tidy files. The statutory reporting framework requires accounts to present a reliable financial position. The Companies Act 2006 requires individual company accounts to include a balance sheet at the end of the financial year, and group accounts to include a consolidated balance sheet for the parent and subsidiaries.

The same framework matters directly to reconciliation. Subsidiary undertakings must be included in consolidation unless excluding them isn't material to a true and fair view. Finance teams therefore need confidence that entity trial balances, subsidiary balances, intercompany positions and consolidated reporting lines agree before statutory filing.

The legal framework was operationalised through the Large and Medium-sized Companies and Groups (Accounts and Reports) Regulations 2008, which specify balance sheet formats for UK companies. The true and fair view requirement has been a core UK accounting milestone since the Companies Act came into force in 2007, and it remains the foundation for balance sheet tie-outs, intercompany eliminations and month-end sign-off.

What auditors expect to see

A signed reconciliation without evidence is weak control documentation. Auditors need to understand the source of the balance, the nature of outstanding differences, the review performed and the reason an item remains open.

UK public-sector audit evidence makes this practical risk clear. One local-government audit file recorded that bank and balance sheet reconciliations weren't completed within 10 days of month-end, despite that deadline being specified in ex-Capita terms. The file also noted that completed reconciliations weren't always reviewed by a second officer, and stated that reconciliations should be performed, authorised and fully documented, with suspense items investigated and cleared promptly. The audit file also recorded a significant unreconciled UK Sport Grant control account balance of £217k, which was adjusted after review.

A controller should build an audit preparedness guide around these records rather than assemble them after the auditor asks. Odoo can support that approach when reconciliation records, journal explanations and source documents remain connected to the accounting entry.

For a wider view of how systems can support compliance, see this guide to financial reporting software. The system won't create a true and fair view by itself. It will, however, make missing evidence and unresolved differences harder to overlook.

Common Account Types You Need to Reconcile

Choose reconciliation frequency by control risk and external dependency, not by account number. Cash depends on an external bank record, intercompany depends on another entity's ledger, and accruals depend on management judgement. Each needs a different control response.

Cash and bank accounts deserve the closest attention. Trace every balance to a bank statement and investigate deposits in transit, uncleared payments, bank fees, returns and chargebacks. For high-volume flows, daily reconciliation is sensible. Lower-risk accounts may use a weekly cadence, consistent with the practical guidance on cash reconciliation.

Intercompany accounts create the greatest consolidation risk. One entity's receivable must agree with the other entity's payable, including currency, timing, tax treatment and reference. Quarterly confirmations can work for stable positions, but groups should review significant movements sooner.

Receivables and payables require sub-ledger control. Compare the partner ledger with aged receivables, aged payables, customer payments and supplier statements. A weekly aged-item review helps prevent old balances from becoming accepted just because they have rolled forward. The UK SME accounts payable and receivable guide provides useful context for structuring those controls.

Accruals and prepayments are evidence-heavy because the ledger balance often depends on a schedule or contract. Check the calculation, service period, release pattern and remaining support. A monthly review is usually appropriate.

Fixed assets and depreciation should reconcile the asset register to the general ledger. Check additions, disposals, transfers and depreciation postings, then retain purchase and disposal evidence.

VAT and payroll control accounts are time-sensitive and should be reviewed monthly against returns, payroll reports and payment records. Suspense and clearing accounts are diagnostic accounts. A balance that remains unexplained usually points to a posting, mapping or integration failure rather than a healthy permanent position.

Teams moving beyond disconnected spreadsheets may consider a managed app for accounting workflows, but the design still matters. High-risk accounts should use maker-checker approval even when matching is automated.

A Practical Month-End Reconciliation Checklist

Use the following as a working close schedule. Adapt the owner and reviewer names to your finance team, but keep the control objective visible beside each Odoo action.

T-5 to T-3 preparation

• T-5, control the cut-off: Review open AP and AR posting activity, communicate the cut-off and confirm the inventory close plan. In Odoo, check accounting configuration and outstanding vendor bills and customer invoices. Owner prepares, controller reviews.
• T-4, collect evidence: Gather bank statements, loan agreements, lease schedules, supplier statements, payroll reports, fixed asset movements and intercompany confirmations. Attach documents to the relevant Odoo records where possible.
• T-3, establish the baseline: Run the trial balance and identify all reconcilable accounts. Create the exception log before investigation begins. Record the account owner, reviewer, balance, source, difference, explanation and due date.

T-2 to close

• T-2, reconcile bank and cash: Open Accounting > Accounting > Bank Journals and review imported statement lines. Use Bank Synchronization where available, then inspect the Bank Reconciliation report. Match by amount, date, reference and counterparty before handling exceptions manually.
• T-2, check partner control accounts: Use Accounting > Reporting > Partner Ledger to compare receivables and payables with the general ledger. Investigate old credits, unapplied payments and supplier statement differences.
• T-1, review intercompany: Compare each entity's reciprocal balance and document timing or currency differences. Escalate any unexplained difference that could affect consolidation.
• T-1, review VAT and payroll: Agree VAT control accounts to the relevant return workings and payroll balances to payroll reports and payment evidence.
• T-1, roll forward fixed assets: Compare additions, disposals and depreciation in the asset register with the general ledger. Confirm that each material movement has a document.
• T-1, challenge accruals and prepayments: Recalculate schedules, check contracts and confirm that releases belong to the correct period.
• T-1, clear suspense: Investigate every suspense and clearing item. Don't certify an unexplained balance merely because it is old.

During the review, use this simple exception format:

Escalate immediately when an item is unexplained, affects a statutory line, suggests duplicate posting or exceeds the organisation's approved materiality policy. A UK government reconciliation template requires a detailed explanation and supporting papers where differences between two bodies exceed £200,000. The template offers a useful evidence standard for significant differences.

For practical bank-control design, review this guide to bank reconciliation software for UK businesses.

Day +3 follow-up

Reopen unresolved exceptions, respond to auditor PBC requests and confirm that final reconciliations, journal explanations and source documents remain attached in Odoo. The controller should review post-close journals and record why each one was necessary.

Common Pitfalls and How to Prevent Them

A spreadsheet can show that two cells differ, but it rarely explains whether the cause is timing, mapping, duplication or missing evidence. In a UK close cycle, that distinction determines whether the controller posts a correction, waits for an external record or escalates a control concern.

The most damaging habit is carrying a difference forward without changing its status. A reconciling item can be valid, but it must have a clear cause, owner, expected resolution and reviewer challenge.

Automation doesn't remove control risk. It can increase that risk if incorrect mappings or matching rules process transactions quickly and consistently. Odoo 19 should therefore use exact matching rules first, with manual review for split payments, partial references, settlement batches and unusual counterparties.

A spreadsheet remains reasonable for a very small entity, a dormant period or a temporary investigation. Once several bank feeds, entities, currencies, sub-ledgers and reviewers are involved, an automation architecture is easier to defend because it preserves lineage, exception routing and approval history.

KPIs and Evidence Chains That Prove Reconciliation Works

A fast close can still contain unsupported balances, stale exceptions or journals posted after approval. In Odoo 19, the dashboard should test whether each reported balance has a usable evidence chain, not just whether the workflow shows “done”. Completion by the agreed close day is useful, but it should sit beside evidence quality and exception handling.

Use an evidence attachment rate as a direct test. For statutory accounts, target 95% or higher. A lower result signals missing statements, schedules or confirmations that an auditor may challenge. Record aged unreconciled items, post-sign-off journals and the time-to-resolve for aged exceptions. Set a documented benchmark for resolution during close planning, then investigate accounts that repeatedly miss it rather than accepting carry-forward differences.

Each KPI should answer a control question:

• Completion status identifies owners who have not performed the review by the close deadline.
• Aged exceptions and time-to-resolve show whether items are being investigated or carried forward.
• Post-sign-off journals test whether approval occurred before the ledger was stable.
• Evidence attachment rate shows whether a second reviewer can reproduce the conclusion.
• Resolution ownership confirms that every open item has an accountable person and next action.

Write materiality thresholds into the planning file. For a £5m revenue SME reporting under FRS 102, a 5% profit-before-tax benchmark can be defensible when documented and applied consistently.

The chain may begin with an Odoo trial balance and end with a bank statement, supplier confirmation, payroll report or fixed asset schedule. Group reporting may also require treasury data and external institutional measures. The ONS reported UK external assets of £15,061.7bn and liabilities of £15,183.8bn at 31 March 2026 in The ONS release. That comparison shows why internal ledger evidence sometimes needs alignment with external measures beyond the close timetable.

Running Reconciliation in Odoo and Adding AI Assist

Start in Odoo 19 by configuring the bank connection under Accounting > Configuration > Online Synchronization. If a live connection isn't available, import the statement through Accounting > Bank > Bank Statements and confirm the statement period, account and closing balance before matching lines.

Open the reconciliation workflow from the relevant bank journal and use the Payments Matching widget. Odoo describes bank reconciliation as matching bank statement lines with internal ERP transactions, with the expected result that the bank balance in Odoo agrees with the bank statement balance. Most transactions should reconcile automatically, leaving exceptions for manual review, as explained in Odoo's Accounting cheat sheet.

A controlled matching sequence

1. Match exact candidates first. Use amount, date, reference and counterparty.
2. Review proposed matches. Confirm that the transaction belongs to the right partner and account.
3. Handle partial or split settlements. Match components only when the supporting evidence explains the split.
4. Post unmatched items deliberately. Use a manual journal entry for bank fees, FX differences, returns or other confirmed items, with an explanation and attachment.
5. Review the report. Use the Bank Reconciliation report under Reporting > Accounting to identify incomplete accounts and outstanding exceptions.
6. Check group positions. Compare intercompany accounts across entities and record elimination evidence before consolidation.

Odoo's year-end guidance says to reconcile all balance sheet accounts, including agreeing bank balances in Odoo with actual bank statement balances. It also recommends the Bank Reconciliation report, Aged Receivables and Aged Payables for close, and calls out the optional Payments Matching feature for validating open vendor bills and customer invoices against payments. The year-end procedure is useful even when your monthly process is more frequent.

Add AI without surrendering judgement

AI should triage exceptions, not certify them without review. A monthly Cron job can flag lines still unmatched after five days, classify a likely cause such as timing, mapping or a potential fraud signal, and route the item to a reviewer queue in Odoo Discuss. The statement line, ledger entry, matching history and supporting document should travel with the task.

That design makes AI an assistant to the control owner. It doesn't decide whether a disputed intercompany position, unusual journal or missing document is acceptable. For a UK-focused discussion of this model, see AI for Odoo ERP.

Rollout Plan and FAQ for Finance Leaders

Use a staged rollout rather than automating every account at once.

• Days 1 to 30: Baseline the current close, map reconcilable accounts, identify evidence gaps and configure bank feeds in Odoo.
• Days 31 to 60: Enable automated matching and AI exception triage for the five highest-risk balance sheet accounts. Review every proposed rule.
• Days 61 to 90: Extend the workflow to material accounts, embed evidence chains in the audit file and retrain the AI using resolved exceptions.

Frequently asked questions

How should we set materiality under FRS 102 and the Companies Act 2006? Use a documented, entity-specific judgement based on the financial statements, risk and reporting context. Don't adopt a generic threshold without approval.

What evidence do auditors expect beyond a signed reconciliation? They may need the ledger extract, source statement or sub-ledger, reconciling-item analysis, journal support and proof of reviewer challenge.

When shouldn't we automate? Keep manual certification for one-off M&A balances, disputed intercompany positions and year-end stocktake tie-ins that require physical verification.

ERP Artists can help map your Odoo 19 reconciliation controls, configure bank and sub-ledger workflows, build integrations and add AI-assisted exception routing without removing human approval. Visit ERP Artists to discuss a UK-focused reconciliation design, implementation plan or Odoo finance review.