Find disclosure information that never appears in the trial balance

A trial balance supplies recorded amounts, but it does not contain every fact needed for financial-statement notes. Ask the accountant to identify the applicable disclosure requirements, then request the contracts, commitments, relationships, and events that support them. The disclosure checklist should fit the entity, framework, and reporting period rather than copy another company's finished notes.

IAS 1 includes explanatory notes in a complete IFRS statement set. Their content requires more than agreement with ledger totals. Keep the framework and effective requirements visible in the preparation plan, including any changes the company has adopted, so the request population is based on the actual reporting obligation.

Legal or procurement teams may hold commitments and guarantees; operations may know about restrictions or idle assets; company administrators may hold ownership changes. Identify the owner of each relevant fact and request supporting documents. A generic request to finance can miss information that never generated an accounting transaction.

IAS 24 includes related-party commitments and relationships in its IFRS disclosure context. That provides one example of why a zero closing balance does not settle completeness. Ask the responsible owners about relevant arrangements during the reporting period, then have the accountant determine what must be disclosed.

Record whether an owner confirmed no relevant activity, supplied information, or did not respond. State the period and population covered by each response. A blank checklist field should not be interpreted as a negative confirmation. Where the source records are incomplete, identify the limitation and obtain the accountant's plan to address it.

For a hypothetical procurement review, the ledger contains no balance for an equipment order that has not yet been delivered. The signed agreement may still contain a future purchase commitment relevant to disclosure assessment. Provide the agreement, cancellation terms, amount, and dates. The example identifies evidence to review, not a universal conclusion that every order must appear in the notes.

Use prior notes as an inventory of subjects to reconsider, not as proof that the current period has the same facts. Check agreements that ended, new categories of transactions, changed risks, and new reporting requirements. Remove stale wording only after confirming why it no longer applies. Add new disclosures based on the accountant's assessment rather than expanding boilerplate indiscriminately.

Keep each proposed note connected to an evidence owner and source record. Separate quantified schedules from narrative judgments and have the appropriate reviewer assess both. A table can tie perfectly while the accompanying description misstates a restriction or condition. Read the note against the actual terms, including any unresolved question.

Once disclosure subjects are assessed, reconcile amounts to statements and supporting schedules. Check that narrative references, dates, currency units, and comparative facts use the approved sources. Retain the decision for items considered but not disclosed where that judgment needs documentation. The reason should be specific to the framework and facts.

Archive the completed request register, significant source documents, accounting conclusions, and final notes with the statement version. The next preparer should be able to identify who knows each non-ledger fact and what changed since the last report. That record complements the numerical tie-out by showing that the team searched for relevant information outside the accounting balances.