Skip to content
Audit trail in accounting software: what the rule requires and how to check yours

Audit trail in accounting software: what the rule requires and how to check yours

November 18, 2026 • 6 min read • By Aicountly Editorial Team • Audit & Assurance

The audit trail rule for accounting software asks one simple question: if someone changes an entry in your books, can you show who changed it, what changed and when? For companies, this has been a legal requirement since 1 April 2023. If you run a company, or keep books for one, here is what the rule says, what auditors tend to ask for, and how to check your own audit trail before the year-end audit starts.

What the audit trail rule says

The Companies (Accounts) Rules, 2014 say that a company that keeps its books of account in software must use software that records an audit trail of every transaction. The software must create an edit log of each change made in the books, with the date of the change, and the audit trail feature must not be capable of being disabled. The requirement applies to financial years starting on or after 1 April 2023, so it covers FY 2026-27 as well.

The statutory auditor then reports on it. Under Rule 11(g) of the Companies (Audit and Auditors) Rules, 2014, the auditor's report says whether the company's accounting software had an audit trail feature, whether it operated throughout the year for all transactions, and whether anyone tampered with it. Because the auditor must comment, "we think it is on" is not a good enough answer.

This is general guidance, not professional advice. Confirm how the rule applies to your company, and what your auditor will test, with your chartered accountant.

Who needs to care

  • Companies that maintain books in software, including private limited companies and small companies. The rule sits under the Companies Act, so check with your CA before assuming a proprietorship or partnership firm is exempt from every part of it. Even where the law does not demand it, an edit log is good practice.
  • Accountants and bookkeepers who enter vouchers on behalf of a client company. Your actions are part of the trail.
  • Finance heads who approve entries or lock periods.

What a useful audit trail records

A trail that only says "something was edited" does not help an auditor. A useful one captures at least these points:

  1. Who: the user who made the change, not a shared login.
  2. When: date and time of the change.
  3. What: the record that changed (a voucher, a ledger, a series) and the old and new values of each field.
  4. Which action: created, edited, cancelled, deleted or imported.
  5. Where from: ideally the IP address or the device, which helps when you investigate an unusual change.

The problems auditors usually find

ProblemWhy it matters Shared loginsThe trail shows one user, so nobody can say who actually made a change. Edits after the books are closedEntries changed after you filed a return or finalised accounts need an explanation. Bulk changesOne bulk edit can touch hundreds of vouchers; you need to see all of them. Trail that cannot be exportedYou cannot hand evidence to the auditor if it is only visible on screen. Old data kept elsewhereEntries made in an earlier tool have a separate trail, or none.

How to check your audit trail in Smart Books

Smart Books has an Audit Trail page under Operations. We read the screen's code to confirm what it offers. Access is controlled by permission: you need audit read permission to open it, and a separate export permission to download it. If someone in your team sees an "Access denied" message, they need that permission from the company owner.

  1. Open Operations, then Audit Trail. You see a list of events with the source, action, entity, voucher, summary, actor and IP address.
  2. Filter the list. You can filter by source (activity, access or authentication), by a From and To date, by an exact action name such as voucher.update or voucher.cancel, by voucher number, or with a free-text search.
  3. Click an action to open the event detail. It shows when it happened, the severity, the entity and a field-by-field table of old and new values. For vouchers it also shows the voucher before and after the change, and the client IP and device details.
  4. Export to CSV if you hold the export permission. If the filtered trail is too large, Smart Books tells you that only the newest rows were exported, so you can narrow the date range and export the rest. A partial export will not pass for the whole trail.

A quick monthly routine: filter the previous month for cancel and update actions, scan the list for changes made after you filed returns, and open any event you cannot explain.

A year-end routine for audit trail readiness

  • Give every person who posts entries their own login, and remove access for people who have left.
  • Lock periods once returns are filed, so late edits are deliberate and visible.
  • Each month, review cancellations and edits to posted vouchers.
  • Before the audit, export the trail for the full financial year, one month at a time if it is large, and store the files with your audit papers.
  • Ask your auditor in advance which software and which modules they will test, including payroll, billing or inventory tools that feed your books.

Key takeaways

  • For companies, accounting software must keep an edit log of each change, and it must not be possible to switch it off. This applies from FY 2023-24 onwards.
  • Your statutory auditor reports on it under Rule 11(g), so test it before they do.
  • Use individual logins, lock closed periods and export the trail as evidence.
  • Review cancellations and edits monthly instead of once a year.

If your books are in Smart Books, the Smart Books Audit Trail page gives you the filters, the field-level detail and the CSV export described above. Pair it with a regular half-year book closing routine, and keep your bank reconciliation and GSTR-1 vs GSTR-3B reconciliation up to date, so that the trail records clean, explainable changes.

Related reading

audit trail accounting software statutory audit Companies Act Smart Books
Aicountly Editorial Team

Insights about accounting automation, ERP systems and business growth strategies.