TallyPrime Edit Log: Complete Guide to Tracking Changes, Deleted Transactions & User Activities

TALLYPRIME GUIDE

TallyPrime Edit Log: Complete Guide to Tracking Changes, Deleted Transactions & User Activities

Understand how Edit Log helps you track created, altered, deleted and resaved transactions and masters, compare versions, identify users and investigate changes in company data.

What is Edit Log?
TallyPrime vs TallyPrime Edit Log
What Does Edit Log Track?
Tracking Transactions and Masters
How to Open Edit Log for a Voucher
How to Compare Versions
How to Check Deleted Transactions
Edit Log Summary
Master-wise Edit Log Summary
User-wise Analysis
e-Invoice, e-Way Bill and Bank Reconciliation
Migration, Repair and Company Activities
Voucher Number Renumbering and Import
Best Practices
Frequently Asked Questions
Conclusion

What is Edit Log in TallyPrime?

TallyPrime Edit Log is a facility that maintains a history of activities performed on supported transactions and masters. It helps you identify what changed, who performed the activity, and when the activity occurred.

For example, if a Sales Invoice was originally recorded for AED 10,000 and later altered, Edit Log can help you investigate the different versions and identify the changes between them.

In simple words: Edit Log helps answer three important questions: What changed? Who changed it? When was it changed?

TallyPrime vs TallyPrime Edit Log

It is important to understand the distinction between regular TallyPrime and TallyPrime Edit Log.

Feature	TallyPrime	TallyPrime Edit Log
Edit Log	Available	Available
Can Edit Log be disabled?	Yes, depending on configuration	No
Transaction tracking	Supported	Supported
Master tracking	Supported	Supported
Version comparison	Available	Available
Audit and internal control	Useful	Designed for continuous Edit Log requirements

TallyPrime Edit Log is intended for organisations that require a continuous trail of activities, including scenarios where audit-trail requirements are important.

What Does Edit Log Track?

1. Created

When a supported transaction or master is created and saved, the creation activity can be recorded.

2. Altered

When an existing transaction or master is modified and saved, the activity is recorded as Altered. The versions can then be compared to identify the changes.

3. Deleted

When a supported transaction or master is deleted, the deletion activity can be recorded. This is particularly useful when investigating a transaction that no longer appears in the normal books.

4. Resaved (No Changes)

A transaction or master may be opened and saved without any actual modification. Such an activity can appear as Resaved (No Changes).

Important: A Resaved (No Changes) version has no actual data difference to compare with the previous version.

Tracking Transactions and Masters

Transactions

Edit Log can be investigated from several locations, including individual voucher alteration, Day Book, Edit Log Summary and voucher-type-wise reports.

Masters

Edit Log also provides master-level tracking for supported masters such as:

Groups
Ledgers
Stock Items

This can help investigate changes to customer or supplier ledgers, stock items and accounting groups.

How to Open Edit Log for a Voucher

Open the required voucher in Alteration Mode.
Press Alt + Q to open Edit Log.
Review the versions and activities displayed.
Check the username, date and time of the activity.
Select the required version and press Enter.
Review the differences between the selected version and the previous version.

Information	What it tells you
Version	Identifies the recorded version
Activity	Created, Altered, Deleted, Resaved, etc.
Username	User associated with the activity
Date & Time	When the activity occurred

How to Compare Two Versions of a Transaction

Version comparison is one of the most useful parts of Edit Log.

For example:

Field	Original Version	Altered Version
Quantity	100 Nos.	80 Nos.
Amount	AED 10,000	AED 8,000

Selecting the relevant version allows you to compare it with the previous version. Changed values are highlighted so that the alteration can be identified quickly.

You can also use F12 (Configure) and configure Show Altered Values Only according to the level of detail required.

How to Check Deleted Transactions Using Edit Log

One of the most common practical uses of Edit Log is investigating transactions that appear to be missing from the books.

Press Alt + G.
Open Edit Log Summary – Voucher Types.
Select the relevant voucher type.
Set the required period.
Review the activities and versions.
Drill down to the relevant transaction.
Review the activity, username, date and time.

Important: Edit Log should be treated as an audit-support and investigation facility. The exact availability of historical information depends on product version, configuration, migration, repair and other company-data events.

Edit Log Summary

Edit Log Summary provides a consolidated view of voucher and master activities. Instead of checking individual transactions one by one, you can start with a summary and drill down to the required detail.

The summary can help identify vouchers or masters that were:

Created
Altered
Deleted
Resaved

Voucher Type-wise Summary

The Voucher Type-wise Summary provides a high-level view of activity by voucher type. You can use the available report configurations to review altered, non-altered and total vouchers.

Monthly Summary

After selecting a voucher type, you can drill down to a monthly summary and investigate activity for a particular period.

Month	Altered Vouchers	Deleted Vouchers
April	25	2
May	31	1
June	18	3

Master-wise Edit Log Summary

Master-wise Edit Log Summary helps review activities involving supported masters.

Groups
Ledgers
Stock Items

You can drill down from the summary to an individual master and review its versions and recorded activities.

Example: Customer Ledger

Suppose a customer ledger originally has a credit period of 30 days and it is later changed to 60 days. The ledger's Edit Log can help identify the alteration and compare the relevant versions.

User-wise Edit Log Analysis

When multiple users work on the same company, user-wise analysis becomes especially useful.

With appropriate security configuration, activities can be associated with specific usernames.

User	Altered Vouchers
Accountant 1	35
Accountant 2	18
Manager	7

If Security Control is not enabled, activities may appear under Unknown (Security not enabled).

e-Invoice, e-Way Bill and Bank Reconciliation Activities

Edit Log Summary provides configuration options for activities associated with areas such as:

e-Invoice
e-Way Bill
Bank Reconciliation

Depending on the report configuration and Basis of Values, these activities can be included or excluded from the summary view.

Why is this useful? A voucher may not have a conventional accounting alteration, while associated compliance or reconciliation information may have changed. Reviewing the appropriate Edit Log configuration can provide additional visibility.

Company Activities, Migration and Data Repair

Company-level activities

TallyPrime provides company-level Edit Log information for activities that can affect transaction and master Edit Logs, including certain data migration, repair, import and split activities.

Changes made through Company Alteration are treated differently and are not covered by the Company Edit Log report in the same manner.

Data Migration

When data is migrated to an Edit Log-enabled environment, Edit Logs can be generated for supported transactions and masters. Migration-related activities can also be recorded.

Migration Exceptions

Migration exceptions can have an impact on existing Edit Log information for affected vouchers or masters. TallyHelp documents scenarios where existing logs may be removed for items that become part of an exception and new logs may be created after resolution.

Data Repair

Data repair requires special attention. TallyHelp states that repairing company data can remove Edit Log information relating to the data being repaired.

Best practice before migration or repair: Take a complete backup, understand the potential Edit Log impact, preserve the original data where required, and document the operation for audit purposes.

Voucher Number Renumbering and Import

Voucher numbering can have an unexpected impact on Edit Log activity.

For example, if automatic numbering causes subsequent vouchers to be renumbered after a voucher is inserted or deleted, the affected vouchers may generate additional Edit Log entries.

Before large imports or changes to voucher numbering, review:

Voucher numbering method
Insertion and deletion behaviour
Source voucher numbers
Potential renumbering of subsequent vouchers
Backup and recovery plan

Where appropriate, consider a numbering approach that avoids unnecessary mass renumbering and therefore unnecessary Edit Log generation.

Why Can Edit Log Increase Company Data Size?

Every recorded alteration can add historical information to company data. If users repeatedly alter the same voucher or master, multiple versions can accumulate.

For example:

Created → Altered → Altered → Altered → Resaved

Frequent unnecessary alterations can therefore contribute to larger company data. Businesses should follow disciplined data-entry and alteration practices.

Practical Examples

Example 1: Finding Who Changed a Sales Invoice

A Sales Invoice was originally recorded for AED 25,000. Later, management finds that the amount is AED 22,500.

Open the Sales Invoice.
Enter alteration mode.
Press Alt + Q.
Review the Edit Log versions.
Check the username and date/time.
Select the altered version.
Compare it with the previous version.

Example 2: Investigating a Missing Sales Invoice

If a user cannot find an invoice in the normal Day Book, management can use Edit Log Summary to investigate whether the voucher was deleted or otherwise modified.

Example 3: Investigating a Ledger Change

If a customer's credit period or other master information appears different from what management expected, open the ledger's Edit Log and review the relevant versions.

Important Edit Log Shortcuts

Shortcut	Function
Alt + Q	Open Edit Log for an individual voucher/master where supported
Alt + G	Go To and open Edit Log Summary
F5	Switch between available summary views such as all/altered items
F8	Version Period
F9	All Versions / Configured Versions where supported
Ctrl + H	Change View
Ctrl + B	Basis of Values
F12	Configure

Best Practices for Using Edit Log

Use individual user accounts: Configure Security Control so activities can be associated with the correct users.
Review Edit Log periodically: Management can review unusual alteration or deletion patterns.
Avoid unnecessary alterations: Repeated changes increase historical Edit Log information.
Review voucher numbering: Avoid configurations that unnecessarily renumber large numbers of vouchers.
Take backups before major data operations: Especially before migration, repair or large imports.
Document repair and migration activities: Maintain appropriate records for audit and internal-control purposes.

Important Limitations and Considerations

Edit Log is powerful, but it should not be misunderstood as an unlimited historical database.

The information available can depend on:

TallyPrime product and release
Edit Log configuration
Security configuration
Data migration history
Data repair
Migration exceptions
Company configuration and data-management activities

For businesses with statutory or audit requirements, Edit Log should be used together with appropriate backup, security and data-management procedures.

Frequently Asked Questions

Can I find who deleted a transaction in TallyPrime?

Where the relevant Edit Log information is available, you can investigate the deleted transaction and review the recorded activity, username and date/time.

Can I see what was changed in an invoice?

Yes. Select the relevant Edit Log version and compare it with the previous version. Changed values can be highlighted for easier identification.

Can Edit Log track ledger changes?

Yes. Supported masters such as ledgers, stock items and groups can be tracked.

Can I see all changes made by one particular user?

With appropriate security configuration, user-wise summaries can help review activities associated with individual users.

Can I view all versions of a voucher?

Yes. Use the All Versions option in the relevant Edit Log report where available.

Why can't I compare a Resaved (No Changes) version?

Because there is no actual data difference between that version and the previous version.

Can Edit Log be disabled in TallyPrime Edit Log?

No. Edit Log cannot be disabled in the TallyPrime Edit Log product. Regular TallyPrime has different configuration options.

Is Edit Log useful for internal audit?

Yes. It provides visibility into transaction and master activities and can be a useful internal-control and audit-support facility.

Conclusion

TallyPrime Edit Log is much more than a facility for checking deleted vouchers.

It provides a structured history of activities across supported transactions and masters, helping businesses investigate:

Who created a transaction
Who altered it
Who deleted it
When the activity occurred
What information changed
Which masters were modified
What happened during certain data-management activities

The simple formula: Record → Track → Compare → Investigate

For businesses that require strong data transparency and internal control, understanding and correctly using Edit Log is an important part of managing TallyPrime company data.