ERPNext Audit Trail vs Apragya: Version History You Configure, or a Log That Is Always On
For finance heads and IT leads at Indian manufacturers running or evaluating ERPNext who want an audit trail that needs little setup to be complete.
ERPNext audit trail questions often come from companies preparing for a statutory audit. ERPNext is an open source ERP built on the Frappe framework, used widely by Indian manufacturers and traders, and it can keep a version history of changes on documents where change tracking is turned on.
Its submit, cancel and amend pattern also keeps cancelled documents visible. How complete the trail is depends on how your deployment is configured and maintained, so check with your implementation partner.
This page compares the two approaches, walks through an illustrative manufacturer and says who should stay with ERPNext.
An example: a Rajkot engine parts manufacturer
Take an illustrative manufacturer with 220 staff, closing its books quarterly. The auditor asked for every change to supplier bank details in the year, after a payment went to a wrong account at another company.
One quarter, from close to audit
Quarter closed
Posting refused after close.Log filtered
Supplier record changes pulled.Changes read
Who edited each supplier, and when.Approvals checked
Each change had a reviewer.Export shared
CSV sent to the auditor.
Two edits to the affected supplier turned up in the year, each with the named user, the time and the IP address. Account numbers were stored encrypted and shown only as the last four digits. The auditor closed the query the same afternoon.
Where a configured audit trail can fall short
Tracking left off
Change tracking is enabled on some document types and not others.
Upgrades and custom code
Custom scripts can change records in ways the history misses.
Direct database edits
A quick fix at the database level leaves no trail.
Evidence gathered late
Version entries are compiled by hand when the auditor asks.
How the audit trail works in Apragya
Step 1 of 5
Who, what and when
Every change request is logged with the user, role, action, record, time and IP address.
- Who, what and when: Every change request is logged with the user, role, action, record, time and IP address.
- Record timeline: Records keep a timeline of creation, status changes, approvals and agent runs.
- Integrity check: Every log entry carries a keyed check, so a later edit to the log is detectable.
- Posted means fixed: Posted journals are never edited or deleted; they are voided with a reason or reversed.
- Search and export: Admins filter the log by user, action or record and export it as CSV or JSON.
Choosing audit trail software in India
ERPNext suits companies that want an open source ERP they can shape, with a team to configure and maintain it, including its change tracking. Apragya suits companies that want the log always on across every app, without deciding document by document.
ERPNext and Apragya on audit trail
| Feature | ERPNext | Apragya |
|---|---|---|
| How it is enabled | Change tracking set per document type | Always on for actions across apps |
| Cancelled or posted records | Cancel and amend keeps originals | Void or reverse with a linked entry |
| Tamper evidence | Depends on your hosting | Keyed integrity check on each entry |
| Supplier bank numbers | Check your configuration | Stored encrypted, last four shown |
| Export | Reports you configure | CSV or JSON for admins |
Checked against public information on 16 September 2026.
What sets Apragya's tamper proof audit log apart
Integrity check
Later edits to a log entry can be detected.
Every app
Purchase, HR, payroll, CRM and accounts share one log.
Closed periods
Posting into a closed period is refused.
Sub-feature access
Deleting drafts or reversing entries are separate permissions.
Agent actions
AI agent runs are recorded alongside user actions.
Hosting choice
Cloud, or VPC and on-premise for Enterprise.
See Apragya vs ERPNext, API access in Apragya vs ERPNext and the ERPNext alternative page.
Testing an audit trail
- List the records your auditor asks about most.
- Change one of each in a test company.
- Check the log shows the user, the record and the time.
- Close a test period and try to post into it.
- Export the log and review it with the auditor.
A short test in a copy of your data avoids surprises in the audit.
What it costs to start
ERPNext audit trail and Apragya, answered
Should we stay with ERPNext?
Does Apragya need tracking switched on per record type?
Can we move from ERPNext at a period start?
Is the log itself protected?
Does Apragya meet the Companies Act rule?
What does it cost to start?
An audit trail you do not have to switch on
Make a test change in Apragya and read the log it leaves.