Accounting Audit Trail: What Records the Company Should Retain

A ledger entry is changed after month-end; the team needs to identify who changed it and when. The useful result is a working that explains the facts, the calculation or classification, and the evidence behind the conclusion. This guide shows how to prepare that working and where a reviewer should investigate before accepting the result.

Scope and applicable period

Indian company or LLP compliance, as identified in the article, with FY 2025–26 illustrative records. Use the current notified rules and relevant form for the actual reporting period.

Verification date: 11 October 2026. Figures and rates identified as assumptions are teaching examples; apply the stated conditions and the actual facts to a real assignment.

The key principle

An accounting audit trail is evidence of changes to the books, not simply a list of users who can open the software. For company financial years beginning on or after 1 April 2023, the accounting-software requirement and the auditor’s reporting responsibility must be evaluated separately. Identify every system that maintains books, including interfaces, and establish whether relevant changes are logged and the trail can be disabled.

Worked example

The ₹15,000 change may be legitimate, but the reviewer needs the underlying invoice, approval and effect on the locked reporting period. Check whether linked postings and imported transactions are also covered. A screenshot of a configuration setting does not prove that logging operated throughout the year. Preserve evidence in an accessible form and evaluate retention, tampering and gaps with the statutory auditor; do not describe an application as compliant merely because it displays an edit history.

A practical sequence

List the systems and interfaces maintaining the books and establish the relevant financial-year scope. Inspect logging operation and access controls, then sample changes around close and during the year.

Link significant events to original and revised support. Document gaps and retention arrangements with the auditor.

Keep a record of what was inspected and when; relying only on a vendor’s feature page does not establish that the entity’s installation operated as required.

Build one evidence file with separate legal conclusions

Corporate compliance often uses the same source records as the accounts, but each filing, approval and auditor-reporting requirement has its own purpose. Establish the entity type and applicable rules before selecting a form or threshold. Reconcile submitted figures to approved source records and retain the actual acknowledgement. Keep accounting recognition, statutory approval and filing status separate in the working. A completed form does not establish that the underlying transaction was properly authorised or correctly accounted for. Review changed ownership, contracts and business facts instead of carrying forward last year’s conclusion without support.

Evidence checklist

Keep the following records linked to the same entity, period and working version. Identify missing items explicitly; a checked box should mean the document was examined and supports the stated conclusion.

• System inventory
• Logging configuration and access records
• Transaction change evidence
• Original and revised supporting document
• Retention and backup procedure

Common mistakes and how to avoid them

• Treating a login history as a transaction trail. Compare the conclusion with the system inventory and resolve any conflicting facts.
• Checking only the main accounting screen. Trace the affected item to the transaction change evidence before finalising the working.
• Assuming a PDF financial report proves compliance. Use the retention and backup procedure to make the final position and remaining exceptions clear.

Before you finalise

Recheck the example’s assumptions against the actual assignment, resolve the identified exceptions and make the final figure or conclusion traceable to its source. Preserve the reviewed version and the reason for material changes. For this task, the retention and backup procedure should agree with the conclusion presented to the client, reviewer or authority.

Frequently asked question

Does a financial-statement builder replace the books-of-account audit trail? No. Review the systems that maintain the underlying books and assess the builder’s role separately.

Sources and further reading

• ICAI — Audit Trail Implementation Guide, revised 2024
• Companies Act, 2013 — India Code

Related guide: Tally ledger hygiene before schedule iii financials.