Tally Edit Log is TallyPrime’s built-in audit trail. It records every change made to vouchers and masters, showing what was altered and when. Since 1 April 2023, companies covered by the Companies (Accounts) Amendment Rules must keep their books in software with an audit trail that cannot be switched off, and TallyPrime’s Edit Log is how Tally users meet this requirement.
This guide explains the rule in plain language, who it applies to, how Edit Log works in TallyPrime, and what your accounts team should do differently day to day. It is general guidance; confirm your specific position with your CA or auditor.
The Audit Trail Rule in Simple Words
The Ministry of Corporate Affairs amended the accounts rules so that, from 1 April 2023, companies using accounting software must use one that:
- Records an audit trail of every transaction
- Logs each change made to the books, along with the date of the change
- Does not allow the audit trail to be disabled
In practical terms: if someone edits a sales invoice from last month, the software should keep a record that the invoice was changed, rather than silently replacing the old version. Auditors are expected to report on whether the company complied.
Who Must Comply
| Type of business | Does the rule apply? |
|---|---|
| Private limited company | Yes |
| Public limited company | Yes |
| One Person Company (OPC) | Yes, as it is a company under the Companies Act |
| LLP | Not under these Companies Act rules; ask your CA whether you should adopt it anyway |
| Partnership firm or proprietorship | Not under these rules; still good practice |
So a Mandi Gobindgarh steel rolling mill registered as a private limited company must comply. A Jalandhar sports goods proprietorship is not covered by this specific rule, though an edit trail still helps it catch errors and misuse.
How Edit Log Works in TallyPrime
Edit Log arrived with the TallyPrime 2.x series in 2022 as a separate edition. When it is active for a company, TallyPrime keeps a history for vouchers and masters. You can open a voucher and see its log: when it was created, when it was altered, and what the earlier version looked like.
Things to understand:
- It works per company. Each company’s Edit Log setting is separate.
- It covers vouchers and masters. Changes to ledgers and stock items are tracked, not just transactions.
- It is meant to be permanent. The rule says the audit trail must not be disabled. Treat enabling Edit Log for a covered company as a one-way decision.
- It adds data. Keeping history makes the data file larger over time, which matters for backups and slow machines.
Our TallyPrime version history shows where Edit Log fits in the product’s timeline.
How to Enable Edit Log: Step by Step
Exact screens vary by release, so use TallyPrime’s Help and search “Edit Log” if a label differs.
- Confirm you are on TallyPrime, not Tally.ERP 9. ERP 9 does not have Edit Log. If you need to move, follow our guide on migrating from Tally ERP 9 to TallyPrime.
- Use the Edit Log edition or setting appropriate to your release. Check your product information screen for how your installation is set up.
- Take a full backup of the company before changing anything.
- Open the company’s features or settings and enable Edit Log for that company.
- Repeat for every company that is a company under the Companies Act. A group with three private limited companies needs it on all three.
- Test it. Create a dummy voucher, alter the amount, and open its Edit Log to confirm the change was captured. Then delete the test entry; the log of that action is fine to keep.
When should you have done it?
The rule applies from 1 April 2023. If a covered company has not yet enabled Edit Log, speak to your auditor straight away about how to handle the gap and start using it immediately.
What Changes for Your Accounts Team
Edit Log is not just a setting; it changes habits.
- Corrections leave a trace. Staff can still correct errors, but every correction is now visible. Encourage clear narration explaining why a voucher was altered.
- Backdated “adjustments” stand out. Last-minute changes to old months before audit will show up in the log.
- Separate user logins matter. If five people share one login, the log cannot show who made a change. Give every user their own login with suitable rights.
- Lock closed periods. Once a month’s GST is filed, restrict alterations to that period for most users.
For a Chandigarh CA firm handling client books, this also protects the firm: if a client’s staff alters entries after the CA’s review, the log shows it.
Practical Tips for Clean Compliance
- One person, one login. This is the single biggest improvement most offices can make.
- Use user rights. Let billing staff create invoices but not alter last month’s entries.
- Back up regularly. The log lives inside your data, so losing the data means losing the trail. TallyPrime 7.0 added automatic backups with TallyDrive; see our TallyDrive backup guide.
- Review the log monthly. Spend ten minutes checking which vouchers were altered and by whom.
- Keep historical data accessible. Do not delete old companies or split data carelessly. Ask your CA about how long records must be kept.
- Document your setup. Note when Edit Log was enabled for each company. Auditors may ask.
Edit Log on Tally on Cloud
Running TallyPrime on a cloud server helps with audit trail compliance in a few practical ways:
- Individual logins are easier. Each staff member gets their own server login and TallyPrime user, so changes are traceable to a person.
- One data set. There are no stray copies on laptops or pendrives where entries might be made outside the main books.
- Daily backups protect the log. A good Tally on Cloud setup includes daily server backups, so the trail survives a hardware failure.
- Auditor access. You can give your auditor a separate, limited login instead of sending data files around.
If data security is your concern, read is Tally on Cloud safe for the questions to ask any provider.
Common Misunderstandings
- “Edit Log stops us correcting mistakes.” It does not. You can still alter vouchers; the change is simply recorded.
- “Only big companies need it.” The rule is based on being a company under the Companies Act, not on size.
- “Turning it on later is fine.” The requirement started on 1 April 2023. Late adoption is a gap your auditor has to deal with.
- “A shared admin login is enough.” Technically the log works, but it cannot tell you which person made a change.
Frequently Asked Questions
What is Edit Log in TallyPrime?
Edit Log is TallyPrime’s audit trail feature. It records creation and alteration of vouchers and masters so you can see what changed and when.
From when is the audit trail mandatory?
For companies covered by the Companies (Accounts) Amendment Rules, the audit trail requirement applies from 1 April 2023.
Can Edit Log be turned off once enabled?
The rule says the audit trail must not be disabled for covered companies. Treat enabling it as permanent, and take a backup before you switch it on.
Does a partnership firm need Tally Edit Log?
The Companies Act rule applies to companies, not partnership firms or proprietorships. Many firms still use it as good practice; ask your CA.
Does Tally.ERP 9 support Edit Log?
No. Edit Log is a TallyPrime feature. Companies still on Tally.ERP 9 should migrate to TallyPrime to meet the requirement.
Will Edit Log slow down Tally?
It adds history to your data, so files grow over time. On a properly sized cloud server or a decent computer, most users will not notice a difference in daily work.
Need help setting up Edit Log, user rights and backups correctly? Sukam Apps, Jalandhar, has supported businesses since 2011. We host your licensed TallyPrime on cloud with separate logins for every user and daily backups, and train your team on-site in Hindi or Punjabi across Punjab, Chandigarh, Haryana, Himachal and Delhi NCR, or remotely across India with a dedicated account manager. WhatsApp +91 99142 49191 for a free demo, or visit our home page.
