Tally audit trail (edit log) — mandatory compliance under Rules 2023

The legal basis

Rule 3(1) of the Companies (Accounts) Rules 2014, as amended by the Companies (Accounts) Amendment Rules 2021 (notified 24-March-2021, effective 1-April-2023 after two postponements), requires:

"Every company which uses accounting software for maintaining its books of account, shall use only such accounting software which has a feature of recording audit trail of each and every transaction, creating an edit log of each change made in books of account along with the date when such changes were made and ensuring that the audit trail cannot be disabled."

The rule applies to every company registered under the Companies Act 2013 — irrespective of size, turnover or industry. There's no exemption for small companies, OPCs, or section-8 companies.

What "audit trail" actually means

The MCA didn't issue a technical specification, but the intent is clear from the rule text plus subsequent ICAI guidance:

• Every change to a transaction must be logged — voucher modification, voucher deletion, narration edit, amount change, date change, ledger reassignment
• User identity — who made the change (Tally user ID)
• Timestamp — when the change was made (date + time)
• Before / after values — what changed (old value vs new value)
• Cannot be disabled — once turned on, must remain on for the entire financial year
• Cannot be edited / deleted — the log itself must be tamper-proof

Enabling edit log in Tally Prime 4.0+

Pre-4.0 versions of Tally Prime (and Tally.ERP 9) do not have native edit log. If you're on those, you must either (a) upgrade to Tally Prime 4.0+ or (b) implement an external audit-trail wrapper, which is impractical. Upgrade is the only sensible route.

What the auditor must report — Sec 143(3)(b)

From FY 23-24 audit reports, the statutory auditor must include a clause under Sec 143(3)(b) confirming the company maintains an audit trail. The ICAI's Guidance Note on Audit Trail (October 2023) prescribes specific reporting language:

Auditor finding	Reporting in Sec 143(3)(b)
Audit trail enabled all 12 months	"The accounting software used by the Company for maintaining its books of account has a feature of recording audit trail (edit log) facility, the same has operated throughout the year, and there is no instance of audit trail being tampered with."
Trail enabled mid-year	"…operated for the period [DD-MM-YYYY] to [DD-MM-YYYY], being [N] months out of the year." Plus a qualification.
Trail not enabled / disabled	Qualified opinion: the company has not complied with proviso to Rule 3(1).
Trail enabled but disabled mid-year	Qualified — disabling itself is a violation of the rule
Software has no trail feature	Qualified — company must migrate to compliant software

Five common pitfalls we see

1. Multiple Tally companies — only one has edit log

When a Pvt Ltd has multiple Tally companies (one per branch / GSTIN), edit log must be enabled on each separately. Most clients enable on the main company and forget the others. The audit qualifies on the un-enabled ones.

2. "Maintain Edit Log" set to Yes, but old vouchers don't show

Edit Log captures changes from the moment it's enabled — it doesn't retroactively log historical changes. If you enabled it on 15 April 2025, only changes from 15 April onwards are in the log. Auditor will check enable-date and report accordingly.

3. Tally Prime versions older than 4.0

Tally Prime 1.0 / 2.0 / 3.0 do not have a native edit log. Many clients running older versions assume the audit-trail "is somewhere in there". It isn't. License upgrade to 4.0+ is mandatory.

4. Backups overwriting edit log

If you restore an older Tally backup (which is sometimes done to recover from data corruption), the edit log of the period between backup and restore is lost. The auditor cannot retroactively confirm the trail. Practical fix: take daily backups, never restore selectively, document any restore in writing.

5. Shared user accounts

Edit log captures the Tally user ID making the change. If all 5 employees use one shared "admin" login, the log says "admin" did everything — useless for forensic tracking. The Tally implementation should set up individual users with role-based access. We do this as part of every Tally implementation.

What about Tally.ERP 9?

Tally.ERP 9 (the predecessor to Tally Prime) does not have a native edit log feature comparable to Prime 4.0+. While there are limited "alteration history" reports, they don't meet the Companies Act rule's "cannot be disabled" + "cannot be tampered" requirements. If a Pvt Ltd is still on Tally.ERP 9 in FY 25-26, the auditor will qualify the Sec 143(3)(b) report. Migration to Tally Prime 4.0+ is essentially mandatory.

Penalty for non-compliance

The Companies Act doesn't prescribe a direct fine for "no audit trail" — but the consequences are real:

• Qualified audit report — flagged to ROC, to lenders, to PE investors during DD
• The director's "Responsibility Statement" under Sec 134(5) becomes harder to sign with full confidence
• For listed companies, SEBI's LODR Regulation 33 has parallel disclosure requirements
• Tax officers, ROC, GST, ED — if any investigate the entity, "no audit trail" is grounds for additional scrutiny and adverse inference
• Insurance / lender / investor covenants increasingly include audit-trail as a condition precedent

The migration checklist (if you're behind)

1. Confirm Tally Prime version (Help → About). If < 4.0, upgrade.
2. Enable Edit Log via F11 → Maintain Edit Log = Yes. Restart company.
3. Set up individual users with passwords (F3 → User Roles).
4. Remove shared admin login from non-admin staff.
5. Document the enable-date in writing (we issue a one-page memorandum for our clients).
6. Inform the statutory auditor of the enable date for accurate Sec 143(3)(b) reporting.
7. If multiple Tally companies, enable on each.
8. Disable any restore-from-backup workflows; switch to forward-only recovery.

The Finclar position

The audit-trail rule is one of the most consequential MCA changes for SMEs in recent years — it forced a generational accounting-software upgrade. We've migrated 28 clients from Tally.ERP 9 → Tally Prime 4.0+ in the last 12 months for this reason alone. The cost (₹81K Gold + 1-2 days of implementation effort) is real but small relative to the cost of a qualified audit report. If you're a Pvt Ltd still running ERP 9 or pre-4.0 Prime, the time to migrate is now — or risk a qualified report that follows you for years on ROC public records.