How to Prepare Documents for Your Company's Statutory Audit

Start with the books you intend to present for audit. Complete your close review, reconcile control accounts and record known corrections. Keep unresolved balances on an exception list with an explanation and a named owner rather than making them disappear through unsupported entries.

Save a dated baseline of the trial balance, general ledger and draft financial statements. Record the accounting period, currency and version. Treat this as the starting point, not as a promise that no further adjustments will arise.

Ask the auditor for the initial document request list and preferred formats. Agree how records will be shared and who will answer questions. Use that list alongside the structure below; the documents needed will depend on the company's transactions and circumstances.

Use this as a preparation checklist, not a universal statutory filing list. Include each relevant category and explain any item marked not applicable. Your auditor's own request list takes precedence over this suggested structure.

Keep an exceptions summary covering missing records, disputed balances and significant events after year-end. Flag these for discussion instead of assuming that a ledger entry provides the whole explanation.

Give every schedule a reference and show its link to the trial balance. A reviewer should be able to move from the financial statement balance to the ledger breakdown, then to the underlying record without guessing which document belongs to which entry.

• ✓Show the account name, ledger code, reporting period and trial balance version.
• ✓Show opening balance, movements and closing balance where that helps explain the account.
• ✓Identify the customer, supplier, asset or transaction behind each component.
• ✓Add evidence references and explain differences between the schedule and ledger.
• ✓Record who prepared and checked the schedule, and which items remain unresolved.

For example, a supplier ageing should total to the payable ledger. If a supplier statement differs, attach a reconciliation identifying missing bills, payments in transit or disputed charges. Do not alter either record simply to make the totals agree.

The monthly bank reconciliation guide explains the matching routine to carry into year-end. The finance operations guides provide related routines for maintaining the records that feed these schedules.

Put one master index at the front of the shared folder. Give each schedule a stable reference, such as BANK-A for a bank reconciliation, and use related references for its statements and supporting items. Keep the naming rule short and consistent.

1. Record the reference, document title, period, owner, version and location in the index.
2. Keep working drafts separate from the copies supplied to the auditor.
3. Provide readable scans and complete statements. Check attachments before marking them available.
4. Supply calculation schedules in an agreed usable format, with formulas and source references intact.
5. When replacing a document, retain the earlier supplied version and explain what changed.

Illustrative example: a bank reconciliation references its closing statement and a list of uncleared payments. Each payment then points to its voucher and subsequent clearance evidence. The index connects the records rather than merely listing a pile of attachments.

Use named accounts and an agreed secure sharing channel. Keep editing rights with the people maintaining the folder; provide the audit team with viewing or downloading access appropriate to the work. Test access before the handover.

• Restrict payroll, personal information and sensitive agreements to the people who need them.
• Keep a record of who has access and review it when responsibilities change.
• Use read-only accounting access where suitable; never share passwords or OTPs.
• Agree how access will end after the engagement and how supplied records will be retained.

Maintain one request register instead of relying on scattered messages. Record the request reference, question, relevant account, owner, agreed response date, evidence supplied and current status. Link the response to the exact document version.

Separate awaiting records, supplied, further query and resolved. Uploading a file means supplied; it does not mean the question is resolved. Confirm closure with the auditor and record any remaining explanation.

Log proposed audit adjustments separately. After management review and approval, record accepted entries in the books, refresh affected schedules and issue a revised trial balance. Show the movement from the earlier version so nobody continues testing superseded figures.

• Sending invoices without schedules: attach a ledger breakdown showing how the documents support the balance.
• Treating payment evidence as the whole record: include the bill, agreement or other support explaining the transaction.
• Hiding missing documents: list the gap, the retrieval owner and any alternative evidence for the auditor to assess.
• Changing supplied schedules silently: issue a new version with a clear explanation.
• Preparing only year-end totals: keep transaction-level records available for further requests.

If accounts are still being reconstructed, describe the work as close remediation rather than audit-ready preparation. Companies with branches, complex contracts or sector-specific requirements should agree additional schedules with their auditor.

Your preparation handover is ready when schedules agree to the supplied books, evidence is traceable, exceptions are visible, access works and every outstanding request has an owner. Keep the folder current as questions and adjustments arise.

The auditor still examines the accounts, seeks explanations and issues the audit report. A complete folder does not establish a clean opinion. Confirm current statutory requirements with your chartered accountant or through the ICAI website. Review this guide quarterly and whenever relevant rules change.