Mon – Sat: 9:00 AM – 7:00 PM IST
Quality

What is an audit trail in ERP?

The record of who changed what, when — and the discipline of logging enough without logging everything.

In short

An audit trail records changes to data and documents: who made the change, when, what the value was before and after. In an ERP this spans document flow (which order produced which delivery and invoice) and change logs on master and transactional data. It exists so that a question about a number can be answered with evidence.

Why It Matters

Why this matters in practice

Audit trails are built for the day someone asks why a price changed, who approved a credit note, or when a bank detail was altered. The common failure is at both extremes: logging nothing of consequence, or logging everything so completely that finding the one relevant change is impractical and the database grows unmanageably.

Answers who changed what, when, and from what value
Document flow links transactions along the process chain
Supports both statutory audit and internal investigation
Retention is a policy decision, not a technical default
How It Works

How it works in practice

1

Document flow

The chain from order through delivery to invoice, navigable in both directions. This is what answers process questions.

2

Change logs on master data

Supplier bank details, customer credit limits, prices and material master fields. These are the high-risk fields.

3

Approval records

Who approved what, at what value, and when. Workflow history is part of the trail.

4

User and access logging

Who had which authorisation when, which matters when investigating after the fact.

5

Retention policy

How long each category is kept, aligned to statutory requirements and to database growth.

Worked example

A worked example: correcting by reversal rather than by edit

A posted invoice has the wrong amount. Two responses are available, and they differ in what they leave behind.

Editing the document in place produces a correct invoice and destroys the evidence that it was ever wrong. If the original was sent to a customer, their copy and yours now differ with no record of why. If the error was systematic, there is no trace to find the others. And from a control perspective, a system that permits editing posted documents permits altering history, which is precisely what an auditor is testing for.

Reversing the original and posting a corrected document leaves three records: the original, the reversal and the correction. The financial outcome is identical. The difference is that the history is intact, the reason is recorded, and the pattern is detectable if it recurs. This is why well-configured ERP systems prevent editing posted documents at all — the restriction is not an inconvenience to work around, it is the control.

Key terms

The vocabulary, briefly

Term What it means
Change log The record of what changed, from what value to what, by whom and when.
Immutability The property that a record cannot be altered after the fact, only superseded.
Reversal Correcting a posted document by posting its opposite, preserving both.
Segregation of duties Separating roles so no one person can both initiate and approve.
Retention How long audit records are kept, which is usually a statutory question.
What Goes Wrong

Common mistakes worth avoiding

Change logging switched off for performance

It is often disabled during implementation for speed and never re-enabled. Verify it before go-live.

Logging everything indiscriminately

Noise makes the trail unusable and the database large. Log the fields that matter.

Shared user accounts

A trail that says a change was made by a shared account identifies nobody.

No retention policy

Logs either grow without limit or get purged without regard to statutory periods.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Changes to master data by user Who is changing what. Unusual volumes or timings are worth a look.
Document reversals by reason High rates point at a process fault upstream of the correction.
Segregation of duties conflicts Users holding incompatible permissions. Should be reviewed, not assumed.
Audit log gaps Periods with no logging, which usually mean logging was disabled rather than that nothing happened.
FAQ

Questions we are asked about this

Anything that moves money or controls risk: bank details, credit limits, prices, tax codes, approval limits and tolerance settings. Logging every field equally buries these.
No. Document flow shows how transactions link along a process. Change logs show modifications to data. A complete audit capability needs both.
Financial postings and their reversals, master data changes for customers, suppliers, items, bank details and prices, permission and role changes, approval actions, and access to sensitive data. Bank detail changes deserve particular attention, since altering a supplier's bank account is the mechanism behind a common and expensive fraud. Logging everything indiscriminately produces volume nobody reviews, so prioritise by what would matter in an investigation.
As long as the underlying records they relate to, which for financial data is typically governed by statutory retention periods in your jurisdiction. Where sector regulation applies — pharmaceutical manufacturing, financial services — retention may be longer and the format may be prescribed. Decide retention deliberately and configure archiving accordingly, because the default is often either indefinite growth or silent purging.
Logging has a cost, and it is usually modest relative to its value. Where it becomes significant is logging changes to very high-volume transactional tables indiscriminately. The practical approach is to log what matters — financial documents, master data, permissions — at full detail, and to be selective about high-volume operational data. This is a design decision rather than an on-off switch.
They should not be able to, and verifying that is one of the more useful control tests you can run. If administrators can delete or alter audit logs, the logs provide no assurance against the people most able to cause harm. Separating log storage from the application, or writing to append-only storage, is the structural answer. Checking who holds that permission today is a five-minute exercise worth doing.
Related

Where to read next

What is three-way matching?

Read more

What is sub-ledger accounting?

Read more

Our ERP software solutions

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.