Trial Balance Tallies, but Financial Statements Do Not: How to Find the Difference

Scope: General reconciliation workflow; corporate examples use Schedule III Division I. Verification date: 11 October 2026.

Why a balanced trial balance can still produce a difference

Debit and credit totals agreeing tells you that the trial balance is arithmetically balanced. It does not establish that every ledger has entered the financial statements once, under the right heading and with the right sign. Differences can arise after import, during grouping, in a detailed schedule or when an adjustment reaches one report but not another.

The useful question is: at which stage did the figures stop agreeing? A disciplined investigation is usually quicker than repeatedly changing figures until the balance sheet appears correct. This is particularly important when using a Schedule 3 financial builder, because automated presentation still depends on complete and correctly classified inputs.

Build a four-stage control bridge

1. Source: record the approved trial balance date, ledger count and debit/credit totals.
2. Import: compare those controls with the imported dataset. Investigate omitted sheets, duplicate rows, totals treated as ledgers and incorrect signs.
3. Grouping: assign each ledger to a reporting head. Keep unmapped and excluded amounts visible in the reconciliation.
4. Finalisation: connect adjustments and supporting schedules to the statements. Record which approved working determines the final amount.

Maintain a small exception register containing the reporting head, TB amount, schedule amount, difference, explanation, proposed entry and review status. An unexplained difference remains an open item even if it is small.

A practical fixed-asset example

Assume, for illustration, that the depreciation ledger contains ₹2,40,000, while the reviewed fixed asset register calculates ₹2,65,000. The difference is ₹25,000. If the PPE note uses the register but the profit and loss statement uses the ledger, the two reports have different depreciation bases.

First test the register's opening values, additions, useful lives, dates and disposals. If ₹2,65,000 is approved as the correct book charge, document the ₹25,000 adjustment and its impact on depreciation expense and accumulated depreciation. If the register is incorrect, repair it instead. The fact that one calculation is more detailed does not automatically make it correct.

Check the common hidden causes

• A credit balance in debtors or debit balance in creditors has been presented without assessing its nature.
• Closing stock is included through both the TB and a separate stock working.
• Current-year and comparative-year columns have been interchanged.
• The source uses rupees while an imported working uses lakhs.
• A note is manually edited without updating its supporting calculation.
• Rounding is applied at inconsistent stages.

Check these causes against actual records. Do not automatically net balances or reclassify every opposite balance: an advance, refund, credit note and posting error require different decisions.

Final review checklist

Re-export the approved TB, retain an adjustment listing and compare the final note totals with the face statements. Review comparatives separately. Examine the generated PDF as well as the on-screen figures; a hidden row or missing table can create a delivery problem even when the calculations agree.

For teams using assureOffice, treat grouping suggestions and generated statements as review material. Resolve exceptions in the underlying working, retain the reason for the change and generate the output again. A clear reconciliation is more valuable than a balance sheet made to tally by an unexplained entry.

Use a controlled correction log

Give each reconciling item a reference, amount, cause and resolution. Distinguish source-book corrections from reporting reclassifications. If an expense ledger was omitted from import, repair the population and rerun the checks. If a loan was mapped to the wrong statement head, retain the classification rationale and correct the mapping.

After every material change, repeat the bridge using the same source version and units. Mark an item resolved only when the corrected figure appears in both the working and the exported document. This prevents an on-screen correction from being mistaken for a completed financials review.

Related articles

• Fixed Asset Register Reconciliation: Matching PPE, Depreciation and the General Ledger
• assureOffice Financials: Checks after Import and before Export
• Year-end Accounting Adjustments: Accruals, Prepayments and Cut-off Checks

Sources and references

• ICAI Guidance Note on Division I — Non Ind AS Schedule III
• assureOffice — assureFinancials features