Balance Sheet Account Reconciliation Example for Beginners

Balance sheet account reconciliation is the process of comparing internal accounting records with an external source to confirm that balances, transactions, and supporting details agree. For finance teams, this is a core control for month-end close, exception management, and audit readiness.

This beginner-friendly example uses a cash account, but the same approach applies to bank reconciliation, vendor reconciliation, customer reconciliation, and other balance sheet accounts.

What balance sheet account reconciliation means

In a typical reconciliation workflow, finance teams compare:

• Side A: your internal records, such as the general ledger, ERP export, or subledger
• Side B: the external record, such as a bank statement, vendor statement, payment gateway report, or marketplace settlement report

The goal is to identify what matches, what is partially matched, what is missing on either side, and what needs review before the account can be considered reconciled.

For a cash account, Side A is usually the books or general ledger, while Side B is the bank statement.

A simple cash account reconciliation example

Assume a finance team is reconciling the cash account for April.

Records on Side A: internal books

Records on Side B: bank statement

At first glance, most items match. The difference is a bank fee of 50 and a deposit in transit that appears on the books but has not yet cleared the bank.

Step-by-step balance sheet account reconciliation process

1. Gather the records

Start with the internal ledger and the external statement for the same period. For other balance sheet accounts, the external source might be a vendor statement, customer statement, marketplace settlement, or payment gateway report.

Make sure the files cover the same period and that the source data is complete before you begin matching.

2. Map the key fields

Before matching transactions, identify the important columns:

• Date
• Amount
• Reference or identifier
• Description
• Any supporting fields needed for matching or enrichment

In a structured reconciliation platform, these fields are mapped once and reused for future periods. Supporting files can also be added if you need lookups, merging, or enrichment before reconciliation.

3. Compare opening balances

The opening balance should match on both sides.

If it does not, the difference may point to:

• a missed prior-period transaction
• an adjustment that was not posted
• a carry-forward error
• a file issue

A mismatch at the opening balance stage should be investigated before moving further.

4. Match transactions

Next, compare individual transactions by amount, identifier, and description.

Typical outcomes include:

• Fully matched: the transaction appears on both sides and the amount agrees
• Partially matched: the reference matches, but the amount differs
• Unmatched: the transaction appears on one side only
• Skipped: the row was excluded because it was incomplete, invalid, or unusable

A finance team may also need to handle one-to-many or many-to-one matching, especially when fees, refunds, deductions, or grouped settlements are involved.

5. Review open items

Any item that does not match cleanly should be reviewed as an open item.

In this example:

• The bank fee on Side B is 250, while books show 300
• The deposit in transit on Side A has not yet appeared on the bank statement

These are common reconciliation differences, not necessarily errors. The task is to identify the reason and document the outcome clearly.

6. Investigate errors and timing differences

Some differences are timing-related. Others are actual errors.

Examples include:

• missing postings
• duplicate entries
• incorrect amounts
• reversed entries
• fees or deductions not yet recorded
• refunds or returns that were not mapped correctly

This is where exception management matters. Teams should separate timing differences from true accounting issues so the right action can be taken.

7. Confirm the ending balance

Once matched items, open items, and adjustments are accounted for, the reconciled ending balance should agree with the external record or the expected accounting position.

If it does not, the reconciliation needs another review pass to find missing items or data issues.

8. Document the result

A complete reconciliation should leave behind an audit trail.

That documentation should show:

• the source files used
• the period reconciled
• matched records
• partially matched records
• unmatched records
• skipped records
• manual adjustments or manual matches
• the final reconciliation summary

This is important for internal control, month-end close, and audit support.

What a good reconciliation report should show

A useful reconciliation report should not only show a final number. It should also explain how the result was reached.

A strong report usually includes:

• total summary
• fully matched items
• partially matched items
• unmatched items
• skipped items
• transaction-level detail
• filters for investigation
• downloadable Excel output

For finance teams, this transparency is often more valuable than a simple pass/fail result.

Common challenges in balance sheet account reconciliation

Even a basic balance sheet reconciliation can become difficult when the file volume grows or the source systems do not line up cleanly.

Common issues include:

• large files that are hard to review in Excel
• inconsistent references across systems
• missing or late files
• repeated manual formulas and copy-paste work
• different people preparing reports in different ways
• open items that stay unresolved for too long
• time spent rebuilding the same reconciliation every month

These problems slow down close cycles and make it harder to maintain a consistent audit trail.

How reconciliation software helps finance teams

A structured reconciliation platform can replace repeated spreadsheet work with a reusable workflow.

With Cointab, finance teams can:

• upload Side A and Side B files
• map fields once and reuse the setup
• add supporting data when needed
• create derived columns using AI-generated Excel-style formulas
• run reconciliation manually or on a schedule
• review matched, partially matched, unmatched, and skipped records
• manually match exceptions when business context is clear
• download audit-ready Excel reports
• reuse the same reconciliation for future periods
• automate data input and output through email, SFTP, or API

This is useful for balance sheet accounts that recur every month, such as cash, bank, receivables, payables, settlements, and vendor balances.

When to automate recurring balance sheet reconciliations

Automation is especially helpful when the same reconciliation is repeated across periods or across many accounts.

It can support workflows such as:

• bank vs books reconciliation
• vendor statement reconciliation
• customer statement reconciliation
• marketplace settlement reconciliation
• payment reconciliation
• intercompany reconciliation

For recurring work, the team sets up the reconciliation once, then runs the same logic again for each new period with updated files.

A practical takeaway for beginners

If you are new to balance sheet account reconciliation, start with one account and one clean example. Focus on the sequence:

1. collect the files
2. map the fields
3. compare opening balances
4. match records
5. review differences
6. document the final position

Once the process is clear, the same framework can be used for more complex reconciliations with multiple files, grouped transactions, and recurring exceptions.

FAQ

What records are used in balance sheet account reconciliation?

Usually, finance teams compare an internal source such as the general ledger or subledger with an external source such as a bank statement, vendor statement, customer statement, or settlement report.

Is balance sheet reconciliation the same as bank reconciliation?

Bank reconciliation is one type of balance sheet account reconciliation. Balance sheet reconciliation is broader and can include cash, bank, receivables, payables, settlements, and other balance sheet accounts.

What if the opening balance does not match?

An opening balance mismatch should be investigated before the reconciliation continues. It may point to a prior-period miss, an unposted adjustment, or a data issue in one of the files.

Can recurring reconciliations be automated?

Yes. Reconciliation workflows can be reused and automated so teams can run the same process each period instead of rebuilding it from scratch.

What should be included in an audit-ready reconciliation report?

An audit-ready report should include the source files, period, matched items, partial matches, unmatched items, skipped items, adjustments, and the final reconciliation summary.