Start with the history you need to review
Edit Log records activities on vouchers and supported masters, including creation, alteration and deletion. A reviewer can inspect versions, activity, username and date/time. It supplies evidence to investigate a change; the report alone does not explain the business reason or establish approval.
Begin with three questions: which company data is under review, which accounting period matters, and when were the changes made? Keep these answers with the review. A voucher dated last month can be altered today, so its voucher date and modification date need separate attention.
This guide follows Tally Solutions' Edit Log documentation, checked November 16, 2026. The official download page showed Release 7.2 for both products. Check your installed product and release against the current vendor download before following instructions.
Choose optional or always-on logging
| Product | Logging behaviour | Decision to confirm |
|---|---|---|
| Standard TallyPrime | Edit Log is optional; an authorised administrator can enable or disable it. | Is that control acceptable for your review requirements? |
| Dedicated TallyPrime Edit Log | Logging is always on, with no enable/disable option. | Do you need the product that prevents disabling? |
Tally's official FAQ confirms that the same licence works for both. Do not buy another licence solely because you need Edit Log. Silver versus Gold is a separate decision about access and users.
If keeping both applications installed, follow the vendor's installation guidance and use different installation folders. An upgrade or migration needs its own compatibility, backup and subscription checks. This review checklist does not authorise a change to production data.
Enable and verify on a test copy
For a new company in standard TallyPrime
- On Create Company, press F12 (Configure) and set Set Edit Log applicability to Yes.
- Set Enable Edit Log to Yes, then press Y or Enter to confirm.
- Complete company setup and make the sample checks below before starting normal entry.
These are the current Create Company instructions. Dedicated TallyPrime Edit Log needs no additional enable setup. For an existing company, get release-specific guidance for its current settings before altering them; do not assume the new-company screen is identical.
For an existing business, first take a recoverable backup and identify the exact company and data folder. Run the acceptance exercise on a clearly labelled test copy kept away from live data. Record the installed product, release and logging state before any proposed switch.
History has a starting point: enabling logging today does not reconstruct earlier changes made before it was enabled. Earlier data from releases before 2.1 also lacks that historical activity trail. Document the gap for the reviewer rather than treating current logging as proof of continuous past coverage.
Check a voucher and its previous version
The supported master scope is Groups, Ledgers and Stock Items, alongside vouchers. Do not assume that every master or company setting has a field-by-field history. The individual Edit Log view explains the version comparison.
A worked review example
Illustrative test data: voucher S-104 is dated October 28 with an amount of ₹10,000. On November 5, a named user changes it to ₹12,000. This is a training example, not a customer record or an instruction to alter an actual sale.
- Open the sample voucher in alteration mode and press Alt+Q (Edit Log). Check the activity, username and timestamp against the test notes.
- Select the altered version and press Enter. Compare it with the previous version: the amount change should be highlighted in red.
- Use F12 and Show altered values only to focus the comparison. Check whether another field changed too; an amount difference is not the whole review.
- Record the observed before/after values and ask for the supporting reason and approval. Close the review without resaving live vouchers merely to inspect them.
A Resaved (No Changes) activity records reacceptance without changed data. There is no difference to drill into for that version. It is not the same as an unexplained amount alteration. Tally also documents logging caused by voucher renumbering; investigate the activity before classifying it as a manual correction.
Avoid the summary date-filter trap
Open Alt+G > Edit Log Summary – Voucher Types, or Gateway of Tally > Display More Reports > Edit Log Summary. Drill from voucher type to month, voucher and version differences. F5 (All Vouchers) includes non-altered voucher totals for context.
In the example, the voucher-report period must include October 28, while F8 (Version Period) must include the November 5 modification. Filtering only for November-dated vouchers can miss a change to an October voucher. Save both period settings with your review evidence.
An empty default report is not proof of no changes. By default, the summary excludes migration activity and versions involving e-Invoice, e-Way Bill and bank reconciliation detail changes. Use Ctrl+B (Basis of Values) to inspect and include the relevant activities and versions before drawing a conclusion.
For masters, open Alt+G > Edit Log Summary – Master-wise, or use Ctrl+H (Change View). The User-wise Voucher/Master Summary appears only when company security is enabled. Use individual named users for accountable testing; a shared login weakens the meaning of a recorded username.
These report controls follow the current TallyHelp summary guide. Record any user/activity filters as well as dates so another reviewer can reproduce the selection.
Investigate missing history before changing settings
Check the company, product, release, logging start point, both periods and excluded versions first. Then inspect Alt+K (Company) > Edit Log for Activities Affecting Edit Log: migration, repair and split events, plus enable/disable events in standard TallyPrime.
This activities report is not a company-master audit trail for company-detail or feature-setting changes. Backup/restore retains logged records, and a split retains relevant transaction/master logs, as described in the vendor FAQ. Neither process recreates previously unlogged changes.
Finish with an acceptance check and handover
Our suggested acceptance check turns a setting into observable evidence. On the test copy, agree the following with the person responsible for the books before repeating any approved setup in production:
- Create and alter one sample voucher under a named user. Confirm both versions and the expected values in Alt+Q.
- Change one sample ledger and verify its master history. If deletion testing is needed, use a disposable test record only.
- Find the sample in Summary with both periods and the relevant filters recorded. Have a second person repeat the lookup.
- Check logging state and Activities Affecting Edit Log. Note any historical gaps and agree who will resolve them.
- Record backup location, restore-check result, reviewer, check date and exceptions. Keep production and test copies clearly distinguishable.
If a test fails, keep the observed result: for example, the voucher is present but the expected altered version is missing, or the amount difference appears under an unexpected username. Capture the company, sample reference and filter settings. Stop the proposed rollout and investigate on the copy before accepting the setup.
For an older unexplained change, ask the reviewer what other evidence is needed, such as the source invoice and documented approval. A matching closing balance does not explain who changed one voucher. Keep any unresolved exception in the handover rather than quietly widening filters until the report looks reassuring.
Hand over the company identifier, installed release/product, review periods, logging start evidence, sample references, report configurations and unresolved questions. Include the business explanation separately from the system log. Agree a practical ongoing review owner and frequency with your accountant.
Each edit adds logged data, so avoid unnecessary resaves or unwanted renumbering. Test representative everyday work and data size before changing a large live company. Do not accept a blanket promise that logging can never affect performance.
Confirm requirements with your accountant or auditor
Ask whether your business needs always-on logging and what records the reviewer expects. This guide explains product behaviour; it does not decide legal applicability, exemptions or whether your entire accounting process meets an audit requirement.
For background, read why audit trail matters and our audit-trail glossary. Use company-creation guidance for setup context and version history when checking an older installation.
Last verified: November 16, 2026 against the linked official Tally Solutions sources. The worked example and acceptance checklist are Mark IT's review suggestions. By Mark IT Solutions, a Mumbai-based Tally partner.