Tally Edit Log: Review Changes around the Closing Date
A practical guide to tally edit log, with a worked example, evidence checklist, common mistakes and steps to prepare a defensible working.
AI Summary
An entry dated March is altered in April after the first financials export. 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
Practical software and accounts workflow. Features depend on the actual product, edition, subscription and version. The example illustrates a control or computation, not certification of an installation.
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
TallyPrime Edit Log records relevant creation, alteration and deletion events in supported masters and transactions. Review the actual product edition, configuration and version. The official FAQ states that printing or exporting Edit Log is not supported; therefore plan on-screen inspection and appropriate review documentation rather than inventing an export command. Software functionality and the company-law compliance conclusion require separate assessment.
Worked example
| Item | Value or fact | What it means |
|---|---|---|
| Original expense voucher | ₹50,000 | Before close |
| Altered voucher | ₹65,000 | After review date |
| Change | ₹15,000 | Inspect reason and support |
| Deleted voucher | Separate event | Check effect on financial totals |
Open the relevant transaction or master history using the product’s supported views and compare changes with the closing checklist. A ₹15,000 alteration may be valid but it can invalidate an earlier reviewed trial balance. Reconcile the revised ledger and rerun affected financial workings. Maintain a review record describing the inspected events and unresolved items without representing it as a native exported log. Ask the auditor what evidence is needed for statutory reporting and retention; the article cannot certify a particular installation.
A practical sequence
Confirm the supported TallyPrime edition and version and inspect the relevant Edit Log views. Select changes around the close date and other risk periods, then trace altered or deleted entries to support.
Reconcile effects on the previously reviewed trial balance. Record the inspection and follow-up findings using an appropriate review method.
Do not describe that record as a native log export or assume unsupported filter options; use the controls actually available in the installation.
Validate the output as well as the operation
Software can organise or calculate data quickly, but its result depends on the input population, configuration and the user’s decisions. Retain the original source, test a few known records and reconcile control totals after import or transformation. Check version support before distributing formulas or prescribing menu commands. Review missing, duplicated and unusually changed records rather than focusing only on a successful operation. When a workflow requires approval, access control or retention, confirm the actual product capability and supplement it with a documented team procedure where needed. A technically successful import is not the final accounting review.
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.
- Product version and edition
- Relevant transaction/master history
- Original and revised documents
- Close-date trial balance snapshots
- Reviewer findings
Common mistakes and how to avoid them
- Claiming native Edit Log export is available. Compare the conclusion with the product version and edition and resolve any conflicting facts.
- Reviewing alterations but ignoring deletions. Trace the affected item to the original and revised documents before finalising the working.
- Assuming an earlier approval covers later changes. Use the reviewer findings 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 reviewer findings should agree with the conclusion presented to the client, reviewer or authority.
Frequently asked question
Does Edit Log automatically explain why an entry changed? The log identifies events; the business reason and supporting document still need investigation.
Sources and further reading
- TallyHelp — Edit Log FAQ
- TallyHelp — Edit Log for masters and transactions
- ICAI — Audit Trail Implementation Guide, revised 2024
Related guide: Tally ledger hygiene before schedule iii financials.