How to Do Balance Sheet Account Reconciliation

Day three of close is when weak reconciliations become visible. The controller has a stack of account files, two balances lack a clear explanation, and the reviewer wants a walkthrough before noon. The spreadsheet says “complete.” The evidence does not.

How to do balance sheet account reconciliation is straightforward: compare each general ledger balance with the right independent support, explain every difference, post required corrections, and retain a traceable approval record. Balance sheet reconciliation verifies the accuracy, completeness, and validity of statement of financial position accounts by comparing the general ledger with bank statements, subledgers, and other system records, as documented in Stanford’s balance sheet account reconciliation guidance.

The hard part isn’t matching two numbers. The hard part is proving what was compared, who performed the work, what differed, and how each difference was resolved. A reconciled balance without that evidence is a guess with a signature.

Table of Contents

• What Balance Sheet Account Reconciliation Actually Is
  • Matching numbers is only the beginning
• Preparing the Reconciliation Before You Touch a Number
  • Build the account-to-source map
  • Lock the comparison conditions
• Matching Techniques and How to Classify Every Difference
  • Use a strict difference taxonomy
• Manual Reconciliation vs Deterministic Automation
• Exception Handling and Human Approval Routing
  • Keep the journal entry attached to the exception
• Capturing Evidence That Withstands Audit Testing
  • Design the evidence record
• A Reconciliation Checklist You Can Run Next Close
  • Preparation at T+3
  • Matching and resolution at T+5
  • Evidence lock at T+7

What Balance Sheet Account Reconciliation Actually Is

Balance sheet account reconciliation is the controlled comparison of a general ledger balance with independent financial evidence at a defined point in time. The residual must be explained, supported, assigned, and resolved or deliberately carried forward under review.

A balance sheet account carries into future reporting periods. That makes an unreconciled item more dangerous than a close-day nuisance. One stale posting can distort several later periods before anyone notices. Stanford describes reconciliation as comparing one or more asset or liability balances on the statement of financial position with another source of financial data, which makes the underlying support as important as the final tie-out.

Matching numbers is only the beginning

A controller should ask four questions for every account:

• What supports the balance? Identify the bank statement, subledger, register, schedule, confirmation, or transaction listing.
• What was compared? Record the account, period, currency, source balance, and general ledger balance.
• What differed? Log each variance instead of burying it in a spreadsheet comment.
• How was it resolved? Classify the item, document the investigation, post the correction when required, and capture approval.

A useful general ledger guide from MyOfficeOps helps frame the ledger tie-out mechanics. The broader control remains the same: every balance needs a defensible path back to source evidence.

Practical rule: A green status means nothing unless a reviewer can reproduce the comparison and follow every exception to resolution.

Reconciliation belongs inside the monthly and year-end close cycle. The preparer compares internal records with external or independent evidence, investigates discrepancies, and posts adjusting entries where needed. A checklist can organize that work, but only an evidence design can make the result survive testing.

Preparing the Reconciliation Before You Touch a Number

Preparation starts with ownership, source authority, cut-off, and storage. A team that defines those elements before matching begins produces cleaner evidence and fewer avoidable exceptions.

The preparer should pull a system-generated trial balance for the period and isolate every balance sheet account that is not zero or self-evident. Each account needs a named preparer and an independent reviewer before work starts. Segregation of duties isn’t a decorative control. The person who builds the reconciliation should not be the sole person who approves it.

Build the account-to-source map

The independent source must match the account’s economic substance.

The preparer should also decide whether the account requires a subledger tie-out or a transaction listing that explains the full balance. Independent reconciliation guidance distinguishes those methods. A bank account may need transaction-level matching, while a fixed asset account may need a register tied to additions, disposals, and depreciation.

Lock the comparison conditions

The reconciliation record should state the cut-off date, currency, ledger version, and source-report date. Without those fields, two correct reports can appear inconsistent because they were generated at different times or under different exchange-rate assumptions.

Expected reconciling items should be listed before the comparison. Typical examples include outstanding cheques, deposits in transit, accruals, and intercompany eliminations. The list is not permission to accept unexplained differences. It is a hypothesis that the source evidence must confirm.

Storage needs the same discipline. A folder per account, a version-controlled spreadsheet, or a reconciliation platform record can work. The supporting documents, working file, and signed-off file should live together under one identifiable reconciliation record. Memory is not a storage convention, despite its continued popularity during close.

Matching Techniques and How to Classify Every Difference

A valid reconciliation matches detailed ledger activity to independent records, ages every residual, and assigns each difference to one defined category. Anything outside the approved categories remains unresolved and blocks sign-off.

The preparer should begin with the final general ledger balance, then drill into transaction detail. Line-by-line matching is appropriate for high-volume or high-risk accounts. Balance-level comparison can support stable accounts only when the underlying schedule explains the full balance and the reviewer can inspect the basis.

Rounding tolerances may be predefined for immaterial differences. A tolerance must never conceal an unexplained posting, duplicate, or classification error. The reconciliation should preserve the original variance and document why the tolerance applies.

Use a strict difference taxonomy

A timing difference is not automatically harmless. An old outstanding cheque can signal a stale liability, an unrecorded void, or a control failure. The owner must confirm why the item remains open and state the expected reversal or clearing date.

Missing postings, duplicates, and true errors require action. The journal entry should reference the reconciliation ID and supporting documents. The reviewer should be able to see the original difference, the proposed correction, and the post-entry result without reconstructing the work from email.

Every unexplained residual is a control exception, not a formatting problem.

Manual Reconciliation vs Deterministic Automation

Manual reconciliation relies on spreadsheet manipulation and memory. Deterministic automation executes predefined comparisons, records each result, and routes exceptions without removing human judgment. The right question isn’t whether an accountant remains involved. The right question is whether the accountant spends time investigating evidence or rebuilding it.

Industry research cited in finance automation guidance reports that manual reconciliation can take about 115 minutes per complex account, while automated systems can reduce the work to about 8 minutes, an implied 93% reduction in labor cost per line item. Those figures appear in HighRadius’ balance sheet reconciliation process guidance.

Automation doesn’t make a bad control defensible. A black-box agent can produce a matching result that no reviewer can reproduce. Deterministic automation is different. It runs versioned rules, records the source data used, logs matches and exceptions, and preserves the human approval that resolves judgment-based items.

Teams managing multiple entities also need explicit treatment for currency, exchange rates, and intercompany activity. Guidance on managing multi-entity currency accounts provides useful context for designing those account rules.

The threshold for automation is operational, not fashionable. Once the account population exceeds what one analyst can prepare and defend within five business days, spreadsheet coordination becomes a close risk. Finance leaders comparing approaches should also review deterministic versus probabilistic finance automation before approving an architecture.

Exception Handling and Human Approval Routing

Every unresolved difference should become a structured exception with an owner, deadline, category, resolution path, and expected reversal date. Approval belongs inside the workflow, not in a separate email thread.

The exception object should contain:

• Account and ledger balance, including the comparison date and currency.
• Independent source balance, with a link to the underlying report.
• Difference amount and category, using timing, missing posting, duplicate, or true error.
• Assigned owner and due date, so the item cannot sit anonymously.
• Resolution type and reversal date, where the item remains open by design.
• Approval status, including the approving user and timestamp.

Routing rules should reflect responsibility. Differences above the organization’s materiality threshold should go to the controller. Payroll-related exceptions should route to the payroll lead. Intercompany differences should reach a shared queue with both entities tagged. The workflow should escalate overdue items rather than waiting for the next close meeting.

Keep the journal entry attached to the exception

Suppose a bank fee is missing from the ledger. The preparer documents the statement line, creates the journal entry, and submits it to the designated approver. After approval, the entry posts to the ledger, and the system attaches the posted entry and confirmation back to the original reconciliation.

That sequence creates one execution record. It shows detection, investigation, approval, posting, and closure. A separate email approval creates a second record that someone must reconcile later. The bank reconciliation exception handler template illustrates the routing pattern without turning approval into an informal side channel.

The related process can also be reviewed in this walkthrough:

Capturing Evidence That Withstands Audit Testing

Audit-defensible reconciliation evidence proves the comparison, the variance, the investigation, the resolution, and the approval. A final balance alone is not enough because an auditor tests the control activity, not merely its outcome.

The audit record should answer four questions without a supplementary interview:

1. Which source documents were used?
2. What were the source and ledger balances at the comparison date?
3. What explains each reconciling item?
4. Where is the support for the explanation and correction?

A spreadsheet can show a clean ending balance while hiding the path that produced it. A preparer may overwrite a formula, paste a new report, or resolve an item in email. The final file can look polished while remaining difficult to reproduce.

Design the evidence record

Deterministic reconciliation captures evidence as the work happens. Each match, exception, journal entry, approval, and system write receives a traceable record with the responsible user and execution time. The system should retain the workflow version that produced the result, because a reviewer may need to understand which predefined logic applied during the period.

Institutional controls guidance treats reconciliations as primary audit evidence and emphasizes aged reconciling-item monitoring. The practical implication is clear: open items need aging, ownership, explanation, and follow-up history, not just a carried-forward balance.

Each account’s evidence pack should retain these linked artefacts:

• Source report: Bank statement, subledger, register, schedule, or confirmation.
• General ledger extract: The exact ledger population and balance used.
• Exception list: Every difference, category, owner, and due date.
• Resolution journal: Posted or proposed entries with support.
• Approval record: Reviewer identity, decision, timestamp, and comments.
• Reconciliation ID: The common key connecting the entire record.

SOX-related environments require documented control procedures, segregation of duties, detailed audit trails, and management evaluation of internal controls over financial reporting within 90 days before each reporting period, as described in guidance on SOX compliance through automated SAP balance sheet reconciliation. Evidence design should therefore be treated as a control requirement from the start.

A Reconciliation Checklist You Can Run Next Close

A practical close cadence moves from preparation to matching, exception resolution, evidence capture, and sign-off. The checklist operationalizes the workflow. It doesn’t replace the classification and evidence standards described above.

Preparation at T+3

• Confirm cut-off: Lock the period, currency, ledger version, and source-report dates.
• Assign ownership: Name the preparer, reviewer, and exception owners.
• Pull prior evidence: Retrieve the prior reconciliation and open-item register.
• Gather support: Collect bank statements, subledgers, schedules, confirmations, and transaction listings.
• Check system readiness: Confirm that relevant subledgers have closed before the balance is tested.

Running the reconciliation before subledgers close creates false exceptions. The ledger and its source may be correct at different points in the close cycle.

Matching and resolution at T+5

• Tie the balances: Compare the trial balance and general ledger, then compare the general ledger with the relevant subsidiary ledger or source system.
• Match detail: Use line-level comparison where account activity or risk requires it.
• Classify every residual: Mark each item as timing, missing posting, duplicate, or true error.
• Route exceptions: Assign named owners, deadlines, resolution types, and reversal dates.
• Post corrections: Prepare supported journal entries and route them through the approval workflow.

The month-end close checklist template can provide a reusable operating shell. The accounting policy still determines the account scope, materiality treatment, and reviewer authority.

Evidence lock at T+7

• Capture approval: Require a timestamped reviewer sign-off inside the workflow.
• Lock the evidence pack: Preserve the source ledgers, reconciliation, supporting schedules, exception list, journal entries, and approval log.
• Review aged items: Confirm that carried-forward differences have current explanations and owners.
• Record completion: Mark the reconciliation complete only after unresolved differences are properly accounted for.

Rollout should begin with a small set of high-volume accounts. The controller can standardize the template, validate the evidence fields, and train preparers before extending the same pattern across entities. Loopfour, the deterministic finance workflow automation platform, can execute predefined reconciliation steps across existing finance systems, route exceptions for human approval, and retain execution evidence for each action.

Loopfour provides deterministic reconciliation workflows that connect source systems, compare balances, route exceptions, and preserve approval evidence as the work runs. Visit Loopfour to assess a governed approach for the next close and replace spreadsheet rework with an auditable operating record.