The Trial Balance Balances but the Financial Statements Are Wrong: How to Review Them in Accounting Systems?

The Trial Balance Balances but the Financial Statements Are Wrong: How to Review Them in Accounting Systems

📅 16/11/2026

When you generate a trial balance from an accounting system, equal debit and credit totals do not prove that the financial statements are correct. Accounts may be misclassified, documents may be incomplete, or recognition may occur at the wrong time. Identifying the problem begins by tracing classifications, cutoff dates, and adjustments, rather than simply looking for an arithmetic difference.

An accountant at a service company prints a trial balance with equal debit and credit totals. Nevertheless, the income statement shows an implausible profit, and some liabilities appear among assets. An incorrect entry can balance perfectly: an expense recorded as an asset, revenue recognized twice with a corresponding receivable, or a liability included in revenue. The accounting system therefore needs a well-organized chart of accounts, detailed reports, and a review of supporting documents.

This article explains a practical, step-by-step approach to diagnosing the problem, with examples from businesses operating in Saudi Arabia. It identifies the documents needed to resolve each issue and the testing criteria to apply after any correction. The article addresses a specific accounting problem in its operational context and does not treat technology as a substitute for professional judgment or original documentation.

How Can You Identify Trial Balance Errors in an Accounting System?

Start by defining the date as of which the figures must be correct and the scope of the accounts, customers, or branches included in the review. Keep a copy of the initial report, then separate source records from entries and aggregations. An accounting system helps bring these references together when permissions, accounts, and data are configured correctly. However, producing a single report does not replace comparing both sources and investigating the reasons for exceptions.

Practical application: Book a practical demonstration of the resolution workflow in the accounting system

Steps for Reviewing Financial Statements and Account Classifications

1. Review Account Classifications and Financial Statement Mapping

When reports indicate that a loan balance appears in revenue or a fixed asset appears in operating expenses, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is an account with the correct balance that is mapped to an inappropriate financial statement line. Do not treat it as a conclusion before reviewing the evidence, however; a data-entry error can coexist with a legitimate timing difference. Determine the effect on revenue, expenses, assets, and liabilities, and establish whether the result changes an aggregate account or only its underlying detail.

Do not start with a summary report without its details. The documents you need here are the chart of accounts, grouping codes, trial balance, and resulting financial statements. Use them to reconstruct the transaction workflow in chronological order, then test the mapping between each account and its type, whether asset, liability, revenue, or expense. Prioritize cases by materiality, age, and transactions involving an external party. If an entry is necessary, link it to supporting documentation, approval, and user permissions, while retaining the original entry information for traceability and subsequent review.

Practical example: A short-term loan of SAR 80,000 appears in service revenue because of incorrect mapping. Case closure criterion: The presentation changes appropriately without changing the overall total of the entries. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: A Guide to Reading Financial Reports

2. Examine Incorrect Entries That Still Balance

This step becomes important when you notice that the financial statements differ even though there is no difference between total debits and credits. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is that both sides of a transaction were posted to incorrect accounts, leaving the erroneous entry balanced. It requires independent supporting evidence. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, link the diagnosis to the transaction source, the approver, and the date, not just to the amount of the difference.

The review requires more than a screenshot from the software. Use the journal, entry supporting documents, user records, and amendment log. Allocate one column to the source of evidence, another to the financial impact, and a third to the explanation accepted by management. Apply the following step: sample large and unusual entries and review the substance of the transaction and the original document. Do not delete the original transaction to make the records look clean. Instead, use a correction workflow that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.

Practical example: A piece of office equipment is recorded as an immediate expense, although the capitalization policy needs to be considered. Case closure criterion: The debit and credit accounts reflect the nature of the transaction, rather than a desire to close the account. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Financial Reports Required from the System

3. Revenue Cutoff at Period-End

The situation may not seem significant at first: December revenue jumps because invoices relate to services that will be provided later. However, it reveals a potential weakness involving the invoice date not necessarily being the date on which revenue is recognized for accounting purposes, and its accumulation may affect another report or a collection or payment decision. It is better to isolate questionable transactions from valid ones and identify the time frame and responsible party before searching thousands of entries. Make a single document with a clear reference number the unit of review, then roll up the result to the aggregate account when finished.

Start with a single auditable file containing service contracts, completion records, invoices, and collection records. First exclude differences that have been shown to belong to another period or account, then link recognition to the completion of the service and the related obligations, in accordance with the applicable policy and standards. Place document reference numbers next to each other to make it easy to track each item without searching again. Do not combine multiple errors into a single reconciliation line if their causes differ. A solution that cannot be explained is not a sound basis for a reliable financial close.

Practical example: An annual maintenance subscription is paid in advance and appears entirely as income in a single month. Case closure criterion: Revenue is allocated to the correct periods while the tax invoice is retained. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Organizing General Ledger Accounts and Reconciliations

Try the Digital Business accounting system

Next step for your business: Compare system plans before moving away from manual spreadsheets

4. Identify Accrued and Prepaid Expenses

The accounting question here is not merely why one figure does not equal another, but why the profit margin is unusual because outstanding supplier invoices have not arrived. This draws attention to an expense that has been incurred but not recorded, or a prepayment recorded entirely as an expense. If an external party is involved, such as a customer, bank, or supplier, obtain its evidence. If the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can still be explained months after it is made.

Assemble the following evidence file: lease and service contracts, payroll records, receipt records, and incoming invoices. Ideally, each document should have an original reference number and date and be linked to the same transaction in the general ledger or system record. Then carry out the practical action: prepare a schedule of accruals and prepaid expenses and record them based on documented evidence. Record the comparison results in a separate statement with columns for the amount, source date, and processing status. Avoid personal notes that a reviewer would struggle to understand. If a document is incomplete, flag the transaction for follow-up instead of assuming information that the relevant party has not confirmed.

Practical example: Quarterly rent is paid in one installment but relates to three months. Case closure criterion: Expenses are matched to the actual period of benefit rather than the payment date. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Sales and Purchases Accounting Details

5. Verify Inventory and Cost of Sales

The investigation starts with the warning sign the accountant encounters: profit increases despite declining inventory, or a negative cost appears. A common mistake is to jump to a corrective entry before understanding the source, because this can move the difference to another account rather than resolve it. The issue to investigate is that inventory has been issued without a corresponding cost transaction, or costing is inconsistent. Review the transaction date and the associated branch or account, then ask whether the event actually occurred or whether it was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.

To confirm or rule out the cause, obtain the item movement report, costing policy, stocktake records, invoices, and returns. Match documents by invoice or voucher number, amount, and bank or inventory reference where available, rather than by totals alone. The appropriate action in this case is to reconcile inventory value with the general ledger account and cost transactions for the same period. If more than one explanation emerges, test each separately and keep a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.

Practical example: Month-end returns restore the quantity but do not adjust the cost by the appropriate amount. Case closure criterion: Cost of goods sold agrees with the quantities issued and their carrying value. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: A Guide to Organizing Warehouses and Stocktaking

Next step for your business: Create an account to try organizing your business data

6. Fixed Assets and Depreciation

When reports indicate that expenses are lower than usual while assets have not been depreciated for several months, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is a missing periodic depreciation run or the incorrect classification of small purchases. Do not treat it as a conclusion before reviewing the evidence, however; a data-entry error can coexist with a legitimate timing difference. Determine the effect on revenue, expenses, assets, and liabilities, and establish whether the result changes an aggregate account or only its underlying detail.

Do not start with a summary report without its details. The documents you need here are the asset register, dates of use, depreciation method, and entries. Use them to reconstruct the transaction workflow in chronological order, then review the dates on which assets were available for use, their useful lives, and the approved policies. Prioritize cases by materiality, age, and transactions involving an external party. If an entry is necessary, link it to supporting documentation, approval, and user permissions, while retaining the original entry information for traceability and subsequent review.

Practical example: A machine begins operating in the middle of the year, but no depreciation is calculated for it. Case closure criterion: The asset register agrees with the asset account and accumulated depreciation in the general ledger. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Understanding Customer and Supplier Account Statements

7. Accounts Receivable and Allowances

This step becomes important when you notice that the balance sheet presents large receivables that are unlikely to be collected in full. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is that old or disputed balances have not been assessed for recoverability. It requires independent supporting evidence. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, link the diagnosis to the transaction source, the approver, and the date, not just to the amount of the difference.

The review requires more than a screenshot from the software. Use receivables aging, balance confirmations, follow-up records, and subsequent collections. Allocate one column to the source of evidence, another to the financial impact, and a third to the explanation accepted by management. Apply the following step: analyze collections and disputes, and determine the appropriate treatment in accordance with the policy and standards. Do not delete the original transaction to make the records look clean. Instead, use a correction workflow that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.

Practical example: A customer has stopped paying for several months, yet the balance is still treated as an ordinary receivable. Case closure criterion: The estimate of credit losses does not rely solely on invoice age without supporting evidence. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: How to Calculate Value Added Tax

8. Tax and Accounting Entries

The situation may not seem significant at first: the value added tax balance in the general ledger does not match what you understand from the sales report. However, it reveals a potential weakness involving mixing tax with revenue or failing to distinguish exempt transactions from taxable transactions, and its accumulation may affect another report or a collection or payment decision. It is better to isolate questionable transactions from valid ones and identify the time frame and responsible party before searching thousands of entries. Make a single document with a clear reference number the unit of review, then roll up the result to the aggregate account when finished.

Start with a single auditable file containing details of output and input tax, notices, returns, and invoices. First exclude differences that have been shown to belong to another period or account, then review tax accounts and transaction classifications, taking into account documents supporting deductions. Place document reference numbers next to each other to make it easy to track each item without searching again. Do not combine multiple errors into a single reconciliation line if their causes differ. A solution that cannot be explained is not a sound basis for a reliable financial close.

Practical example: Purchases are recorded entirely as expenses including tax, without showing deductible input tax. Case closure criterion: A reconciliation statement is produced between the general ledger balances and the tax return, with an explanation for every adjustment. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Procurement System Functions

Digital Business solutions for business management

Next step for your business: Request a demonstration of how to monitor controls and reports

9. Interbranch Transactions and Reciprocal Accounts

The accounting question here is not merely why one figure does not equal another, but why amounts due between branches appear twice in the combined financial statements. This draws attention to a missing counterpart entry or duplicated internal presentation during aggregation. If an external party is involved, such as a customer, bank, or supplier, obtain its evidence. If the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can still be explained months after it is made.

Assemble the following evidence file: interbranch transfer entries, reciprocal balances, and reports for each branch. Ideally, each document should have an original reference number and date and be linked to the same transaction in the general ledger or system record. Then carry out the practical action: review the reciprocal accounts and resolve differences before generating combined reports. Record the comparison results in a separate statement with columns for the amount, source date, and processing status. Avoid personal notes that a reviewer would struggle to understand. If a document is incomplete, flag the transaction for follow-up instead of assuming information that the relevant party has not confirmed.

Practical example: The head office charges an expense to a branch, but the branch does not record the corresponding entry. Case closure criterion: Internal accounts are eliminated in the appropriate aggregation without erasing the branch transaction. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Project and Contracting Accounting Management

10. Review and Analyze Financial Statements Before Approval

The investigation starts with the warning sign the accountant encounters: the error recurs because the statements are generated with one click and without trend analysis. A common mistake is to jump to a corrective entry before understanding the source, because this can move the difference to another account rather than resolve it. The issue to investigate is that reliance on the appearance of the report instead of relating it to business activity and material changes. Review the transaction date and the associated branch or account, then ask whether the event actually occurred or whether it was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.

To confirm or rule out the cause, obtain a 12-month comparison, margin indicators, large balances, and an approval memorandum. Match documents by invoice or voucher number, amount, and bank or inventory reference where available, rather than by totals alone. The appropriate action in this case is to set review thresholds for unusual changes and require explanations supported by documents. If more than one explanation emerges, test each separately and keep a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.

Practical example: A company’s margin increases by ten percentage points despite no price increase or change in costs. Case closure criterion: A memorandum explains the differences in profitability, liquidity, and receivables compared with previous periods. Do not approve the resolution before verifying the result in the detailed report and the associated document.

For more on this stage: Accounting Solution Features

Practical Example: How Incorrect Account Classification Leads to Misleading Financial Statements

An accountant at a service company prints a trial balance with equal debit and credit totals. Nevertheless, the income statement shows an implausible profit, and some liabilities appear among assets. Do not assume that the first difference you discover explains every figure. Create a working copy containing the balance or report before correction, then link it to the original document and record the dates and users. If the review reveals two different causes, separate them into two independent cases. One may require an accounting correction, while the other may be a timing difference that does not require a new entry.

Start with the highest-risk items and then complete the list in order: test the mapping between each account and its type, whether asset, liability, revenue, or expense; prepare a schedule of accruals and prepaid expenses and record them based on documented evidence; analyze collections and disputes and determine the appropriate treatment in accordance with the policy and standards; set review thresholds for unusual changes and require explanations supported by documents. After each step, produce a new detailed report rather than relying on a change in the total. Have the accounting manager or reviewer sign off on the reason for the correction and its effect on the period, and assign someone to follow up on cases that still lack adequate documentation.

Summary Comparison Table: Before and After Correction

Type of ErrorPotential ImpactReview Method
Initial observationA loan balance appears in revenue or a fixed asset appears in operating expenses.Test the mapping between each account and its type, whether asset, liability, revenue, or expense.
Decisive evidenceItem movement report, costing policy, stocktake records, invoices, and returns.Cost of goods sold agrees with the quantities issued and their carrying value.
Status after correctionA memorandum explains the differences in profitability, liquidity, and receivables compared with previous periods.Set review thresholds for unusual changes and require explanations supported by documents.

Trial Balance Error Review Checklist Before Approving Financial Statements

• Define a single cutoff date and a list of accounts, branches, or suppliers included in the review.

• Retain the report and documents as they were before any amendment or posting.

• Match records at the individual transaction level, not merely at the total level.

• Classify each difference as a timing issue, a recording error, or a matter requiring professional judgment.

• Do not post a reconciliation entry without clear supporting documentation and approval from the authorized person.

• Regenerate the detailed report and entries, and document that the cause has been resolved.

• Assign an owner and review date to remaining cases, and record why they have not been closed.

• Keep a copy that can be rechecked when preparing or auditing financial statements.

Ready to Try the System?

Start your free trial or speak with the sales team to help choose the right solution.

Frequently Asked Questions

Does a balanced trial balance mean there are no errors?

No. Both sides of an incorrect entry can be equal, or an entire entry may be missing from the records.

Where should I start when profit is unusually high?

Review non-recurring revenue, followed by deferred expenses, inventory, depreciation, and accruals.

Should errors be corrected with a single combined entry?

It is preferable to make traceable corrective entries for each material cause in accordance with the business’s policy and the responsible person’s review.

Why should I review the chart of accounts?

Because account classification affects the presentation of the balance sheet, income statement, and reports even if the balance is correct.

What is the role of monthly comparisons?

They reveal unusual changes in ratios and balances and may indicate a problem that arithmetic balance does not reveal.

Conclusion: Correct the Source Before Changing the Report

Success in resolving the problem is not measured by making a single difference disappear from the screen, but by the ability to trace each transaction, understand its effect, and prevent recurrence. Use an accounting system to bring accounts, documents, and reports together in a clear workflow, then link approval of the correction to a responsible person and a test. Above all, the results of reports must be capable of being rechecked. This is the difference between a figure that appears correct and accounting data that can be relied on for operations and decisions.

If you would like to test this workflow using your own business data: Start a trial of the accounting solution that suits your team

Manage Your Business with Greater Flexibility

Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.

Free Trial Without a Credit Card
24-Hour Technical Support
Compatible with ZATCA Requirements