A trial balance review is useful because it is the last consolidated view before the financial statements. It is also easy to overclaim, because balance is an arithmetic property, not evidence of accuracy.
Bookkeeping Operations
What a clean trial balance can and cannot prove
A research brief on trial balances, separating a report that balances from a ledger that is accurate, complete, and correctly classified.
Published · 3 listed sources
Table of contents
Key takeaways
- A balanced trial balance proves debits equal credits, not that the ledger is correct.
- Separate completeness, accuracy, classification, and period cutoff when reviewing.
- Use supporting schedules and reconciliations, not the trial balance alone.
- Record the review and the exceptions, not only the final total.
The trial balance reports that debits equal credits, and the close moves on. The report is clean, the totals agree, and nobody asks whether the ledger contains the right transactions in the right accounts. A balanced report can hide a wrong account, a missing invoice, or a duplicated entry.
What the review can show
The review can show that the ledger is internally consistent. It can show unusual balances, accounts with no activity, and balances that changed sharply from the prior period. It can show the accounts that need a supporting schedule.
Those facts support a focused review. A balance that moved by an unexpected amount is a question worth asking, even when the total is unchanged.
What the review cannot show
The review cannot show that every transaction was recorded. A missing invoice leaves the ledger balanced and incomplete. The trial balance does not contain a field for what is absent.
It cannot show that a transaction was posted to the correct account. A payment coded to the wrong expense category balances just as neatly as a correct one, and the classification error only appears when someone reviews the detail.
It cannot show that the period cutoff was applied correctly. An invoice dated the first of next month can be posted to the current period and the report will still balance.
Methodology
This brief reviews public guidance on internal control, recordkeeping, and financial reporting, and maps it to a private month-end review. The sources support documentation and review discipline; they do not prescribe an account structure or a materiality threshold.
We tested the proposed checks against four common cases: a missing vendor invoice, a duplicated bank transaction, an expense posted to the wrong category, and a payroll accrual recorded in the wrong period. Each case produced a balanced trial balance.
Completeness checks
Completeness is tested against source records, not against the trial balance. Compare the accounts payable ledger to the vendor statements, the receivable ledger to the invoices issued, and payroll to the register.
Record the comparison and any unreconciled difference. A completeness check that is not documented becomes an assertion that the report is complete, which is the claim the review is meant to test.
Accuracy and classification
Accuracy is tested by tracing a sample of entries to supporting documents, and classification by reviewing the account mapping for large or unusual items. Neither test requires a full re-entry of the ledger.
Sample the largest items and the items that changed category from the prior month. Those two groups catch most material misclassifications without reviewing every transaction.
Cutoff and accruals
Check the transactions around the period boundary. A sale or expense recorded in the wrong period distorts both months, and the trial balance will not reveal it.
Review the accrual schedule and the subsequent payments in the following period. A payment that clears an accrual is evidence the estimate was reasonable; a payment that clears nothing is a question.
Reporting the review
A useful summary records the period, the accounts reviewed, the source records used, the exceptions found, and the reviewer. The final total is not the conclusion; the exceptions and their resolution are.
Phrase findings as questions where the evidence is incomplete. "The consulting balance rose 40 percent with no matching invoice in the sample; can we confirm the accrual?" is more useful than a verdict.
Account mapping review
Classification review starts with the chart of accounts and the mapping rules. A rule that sends a common vendor to a general expense account will produce a consistent-looking error every month.
Review the largest accounts and the accounts that changed most from the prior period. Trace a sample of entries to the invoice or receipt, and record whether the mapping matched the nature of the cost.
The role of reconciliations
The trial balance is supported by reconciliations, not replaced by them. Bank, receivable, payable, and payroll reconciliations each test a different part of the ledger.
A trial balance review without the reconciliations is an arithmetic check. A review with them is a control. The distinction should be stated plainly in the close checklist so no one assumes the stronger claim.
Materiality in a small ledger
Small entities often skip a materiality threshold because the amounts are modest. That is a mistake when a small error changes a covenant, a tax position, or a client's decision.
Set a threshold in advance with the client and record it. The threshold does not excuse errors below it; it directs attention to the accounts where an error would matter.
A worked example
A ledger balances at month end. The consulting expense is up 40 percent, and the payable balance includes one vendor with no invoice in the file. The trial balance is clean; the review is not done.
Tracing the vendor finds an invoice posted twice, with one copy coded to consulting and one to professional fees. The total is correct only because the duplicate offsets an unrecorded invoice. The balance did not reveal either error.
Reviewer independence
The person who prepared the ledger should not be the only reviewer. In a small team, the owner or a second bookkeeper can review the reconciliations and the exception log.
Record the reviewer and the date. Independence is limited in a small firm, but the record still shows that a second look happened and what it covered.
Documentation and retention
Keep the review evidence with the close file: reconciliations, the exception log, the reviewer, and the date. Retention should follow the client agreement and applicable rules.
The record does not need to include every transaction. It needs to show what was tested, what was found, and who concluded. That is enough for a later reviewer to repeat the work.
Account balance analytics
Compare each significant account to the prior month and to the same month last year. A movement that the business cannot explain is worth a question, even when the balance is small.
Record the explanation beside the account. The note is the evidence that the movement was reviewed, and it prevents the next reviewer from repeating the inquiry.
What to ask the client
Some questions belong to the client: whether an accrual is expected, whether a large balance is unusual, whether a vendor invoice is valid. The review should surface those questions early rather than at the reporting deadline.
List the questions with the supporting balance and the date asked. A question that is not recorded is easy to forget and hard to resolve before the deadline.
Limits and appropriate use
This brief is a method note, not an empirical study. It does not establish a materiality threshold or a standard review programme. Results depend on the quality of the source records and the scope of the sample.
Small entities may not have every supporting schedule, and the review should say so rather than imply a completeness that the records cannot support. The absence of evidence is itself a finding.
Conclusion
A clean trial balance is a starting point for the close, not a conclusion. Used with reconciliations, ledgers, and cutoff checks, it supports a review that tests accuracy and completeness. Used alone, it certifies arithmetic and leaves the ledger unexamined.