Balanced Books Can Still Be Wrong

Stories Inc.'s ledger balances before the close adjustments. It balances after them too. The difference is what the balances can withstand when someone asks for their support.

A premature sale and an equipment purchase posted to expense each have matching accounting entries. A trial balance can establish arithmetic equality while leaving those errors intact. OpenStax's trial-balance explanation describes that initial check. The close goes further: it connects the ledger to evidence and makes unresolved differences visible.

Start with the same period and version

Suppose the receivables specialist sends a customer-balance report at noon. An accountant reverses the premature $5,000 sale at two. Comparing that earlier report with the later ledger creates a difference that says nothing about whether the adjustment was right.

The team first establishes the account, period, reporting scope and extraction time. It then compares records from a consistent version or identifies the intervening entries. This mundane step prevents a reconciliation from becoming a hunt through incompatible reports.

Customer and supplier detail commonly sits in subledgers. A control account is the general-ledger total supported by those detailed records. The receivables control account, for example, should connect to the customer balances after all relevant postings have transferred.

If the totals disagree, the accountant traces unposted items, failed transfers or direct journals to the control account. Microsoft Dynamics' period-end procedure illustrates the dependency: complete other modules, verify posting, make adjustments and prepare reports. The exact workflow varies by system.

Give each difference a supported explanation

Stories Inc.'s cash ledger shows $53,000 before close. The bank statement contains a $100 fee missing from the ledger. The accountant checks the statement entry and period, records the fee, and reduces cash to $52,900. The journal reference becomes part of the reconciliation.

A cheque already recorded by Stories but not cleared by the bank needs different treatment. It is a timing item; posting the payment again would duplicate it. The reconciliation preserves its identifying details and follows it through later clearance. OpenStax's bank-reconciliation explanation distinguishes timing differences from adjustments to the books.

The same discipline applies beyond cash. For the delivery payable, the $2,700 invoice should connect to completed deliveries, agreed rates and supported extra charges. Agreement between an invoice and a ledger entry establishes consistency; it does not establish that the supplier charged the right amount. The reviewer also checks that the earlier $2,400 accrual was cleared.

An unexplained difference should not disappear into “miscellaneous expense” merely to make a schedule reach zero.

What the reconciliation package contains

For each significant balance, the preparer leaves a short, usable record:

In our case, the inventory schedule explains $12,000 remaining after purchases, sales, shortage and write-down. The equipment register explains $31,400 net equipment through cost and accumulated depreciation. The insurance schedule explains why $11,000 of coverage remains. Each schedule should tie to the version of the ledger used for the reviewed report.

Support must also answer the right question. Counting books addresses quantity. Assessing their recoverable value addresses measurement. Delivery evidence addresses whether a recorded sale belongs in October. Two systems can agree because both contain the same premature invoice; neither system supplies the missing delivery evidence.

Review ends with a disposition

The reviewer decides whether to accept the supported balance, require an adjustment, or hold the relevant conclusion pending more evidence. The decision considers materiality and the nature of the issue, not just its size. A small discrepancy can still reveal a broken process.

A recent, documented bank timing item may be accepted for follow-up. An unsupported delivery accrual large enough to change the interpretation of the month needs evidence or correction before approval. These are illustrative judgments, not universal monetary thresholds.

Review also compares the adjusted result with operations, previous periods and expectations. An unexpectedly low delivery expense might reveal a missed supplier accrual; it might also reflect fewer deliveries or a changed rate. The reviewer asks which explanation the evidence supports. The budget is a comparison, not an accounting target.

A changed ledger changes the review task

Once the bank fee is posted, the team refreshes the cash reconciliation and reports affected by it. If a later adjustment changes inventory, tax or the group submission, those affected schedules and approvals must be revisited too. An earlier sign-off does not automatically cover a later version.

After approval, posting restrictions protect the reviewed period. Authorized reopening should identify the change and its downstream effects, then preserve the revised report version.

For Maya, a completed reconciliation therefore means more than matching totals: the balance has support, the differences have decisions, and the report she is reading is the version that was reviewed.

← Make judgment reviewable | Define the reporting boundary →

Fictional teaching example. Personal views based on public sources; no confidential employer information or employer endorsement. Accounting policies and business circumstances require case-by-case analysis.