The record of who changed what, when — and the discipline of logging enough without logging everything.
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.
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.
The chain from order through delivery to invoice, navigable in both directions. This is what answers process questions.
Supplier bank details, customer credit limits, prices and material master fields. These are the high-risk fields.
Who approved what, at what value, and when. Workflow history is part of the trail.
Who had which authorisation when, which matters when investigating after the fact.
How long each category is kept, aligned to statutory requirements and to database growth.
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.
| 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. |
It is often disabled during implementation for speed and never re-enabled. Verify it before go-live.
Noise makes the trail unusable and the database large. Log the fields that matter.
A trail that says a change was made by a shared account identifies nobody.
Logs either grow without limit or get purged without regard to statutory periods.
| 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. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.