Balance Sheet Reconciliation: Template and Best Practices

Deepak Anchala
Co-Founder and CEO, Adopt AI6 November 2026

A balance sheet reconciliation template gives every account the same structure: the ledger balance, the balance a third party or subledger supports, the difference, and an explanation for each item that sits between them. If you own the close, you probably have a folder of these worksheets, each built a little differently by whoever prepared it last. This post gives you one format to standardize on, a worked example, and the practices that keep the file reviewable.
What a balance sheet reconciliation proves
The general ledger says an account holds $184,300. A reconciliation shows that something outside the ledger agrees, or explains why it does not. That outside source is a bank statement for cash, a subledger for receivables and payables, a depreciation schedule for fixed assets, a lender statement for debt.
An unreconciled balance is an assertion nobody has tested. Auditors test it. So does the first person who asks why prepaid expenses grew by $60,000 in a quarter with no new contracts.
The template
Copy these fields into a sheet. Put one account per tab or one reconciliation per row in a tracking file.
Header block
| Field | What goes in it |
|---|---|
| Entity | The legal entity the account belongs to |
| Account name and number | As written in the chart of accounts |
| Period end | The close date being reconciled |
| Account owner | The person accountable for the balance |
| Risk rating | High, medium, or low, which sets review depth and cadence |
Balance block
| Field | What goes in it |
|---|---|
| GL balance | From the trial balance at period end |
| Supporting balance | From the statement, subledger, or schedule |
| Source and date | Where the support came from and when it was pulled |
| Difference | GL balance minus supporting balance |
| Unexplained difference | Must be zero before sign-off |
Reconciling items block
| Field | What goes in it |
|---|---|
| Description | One line a stranger could understand |
| Amount | Signed, with the side it sits on |
| Type | Timing, error, or adjustment needed |
| Date originated | Drives the age of the item |
| Owner | The person who resolves it |
| Expected clear date | When it should disappear |
| Journal entry reference | Required for adjustments and errors |
Sign-off block
| Field | What goes in it |
|---|---|
| Prepared by, date | The preparer's name and the date |
| Reviewed by, date | A second person, dated |
| Review notes | Questions asked and how they were answered |
A worked example: accrued expenses
Take an accrued expenses account with a GL balance of $212,400. The supporting schedule lists 14 accruals that total $205,900.
| Item | Amount | Type | Owner |
|---|---|---|---|
| Difference (GL minus schedule) | 6,500 | ||
| Legal fees accrued twice, October and November | 4,200 | Error, journal entry needed | Staff accountant |
| Software renewal accrued in schedule, not yet posted | (1,300) | Adjustment needed | AP lead |
| Bonus accrual true-up booked in GL, missing from schedule | 3,600 | Schedule update | Controller |
| Unexplained difference | 0 |
Check the arithmetic: 4,200 minus 1,300 plus 3,600 equals 6,500. The unexplained line is zero, so the reviewer moves on to the question that matters, which is whether those three items are right.
Best practices that keep reconciliations reviewable
Reconcile to an outside source, not to another ledger report. A schedule built from the GL tests nothing. Pull the statement, the subledger, or the contract.
Rank accounts by risk and set the cadence from the rank. Cash, clearing accounts, and intercompany balances move the most and hide errors the longest. Prepaids and fixed assets move slowly and can follow the monthly calendar.
Give every reconciling item an owner and an age. An item with no owner stays open. An item older than 60 days is a signal to the reviewer that a timing difference has turned into an error.
Write the explanation for a reader who was not there. "Timing" is not an explanation. "Wire sent 10/30, received 11/2" is.
Keep preparer and reviewer separate. The person who prepared a reconciliation cannot review it. If a two-person team makes that hard, rotate the roles by account.
Lock the file after sign-off. Changes after approval need a new version and a new review, with the reopened items visible. A reconciliation that changes after approval gives an auditor no reason to trust it.
Tie the reconciliation list to the close calendar. Each account should have a due date and a status you can see in one place. If you do not have a close calendar yet, start with a close calendar template.
Where spreadsheets stop scaling
The template above works for 20 accounts. At 200 accounts across several entities, the work is pulling statements, matching lines, and chasing owners for explanations, and the review gets squeezed to the last two days of the close.
Adopt prepares the reconciliation: agents pull the supporting balance, match the lines, and list what does not tie, with the evidence for each item. A named person reviews, approves, and signs off, and nothing posts to the ledger without that approval. The reviewer spends the close on the exceptions instead of on assembling the file. See how that works for account reconciliation, or sign up free to try it on your own accounts.
FAQs
Related Articles

The Accountant Shortage in Numbers: What It Means for Your 2027 Close

How to Automate Invoice Data Extraction and Categorization from PDFs

See it running on your workflows
Automate your accounting workflows

