Business

Audit Trail Design: What a Business System Should Record and How to Keep It Trustworthy

November 11, 2026 · 5 min read · Etzal Group Team

When a figure in a report looks wrong, the first question is who changed it. When an auditor visits, the question is whether you can prove who approved a payment. When a customer disputes an order, you need to show what was entered and when. All three rely on an audit trail that was designed before the question was asked.

What an audit trail is

It is a chronological record of actions that matter to the business, each attributed to a person or system. It differs from technical logs, which exist to debug software. An audit trail exists to establish facts.

A useful entry answers six questions:

  • Who performed the action, as a named user or a named system account.
  • What action it was: created, changed, approved, deleted, exported, logged in.
  • Which record was affected, with its identifier.
  • When, with a consistent time zone.
  • From where: device or network address, and the channel such as web, mobile or API.
  • What changed: the value before and the value after.

The last item is the one most often missing. "Invoice 1042 was edited" is weak. "Amount changed from 12,500,000 to 21,500,000" is evidence.

What to record

Start with what an auditor, a manager or a customer could reasonably ask about:

  • Money. Creation, change, approval and cancellation of invoices, payments, refunds and journal entries.
  • Master data. Changes to customers, suppliers, bank details, price lists and tax settings.
  • Approvals. Who approved or rejected, with any comment.
  • Access. Logins, failed logins, password resets, and changes to roles and permissions.
  • Sensitive reads. Viewing or exporting payroll, identity data or bulk customer lists.
  • Deletions. What was removed, by whom, and ideally a retained copy.
  • Configuration. Changes to system settings and integrations.
  • Automated actions. What a scheduled job or an AI agent did, attributed to that agent and, where relevant, to the person who authorised it.

What not to record

  • Passwords, full card numbers and secret keys must never appear in the log.
  • Personal data beyond what is needed to identify the record. Reference the record by identifier where possible.
  • Every page view of ordinary data. It buries the important entries.

Making it trustworthy

An audit trail that can be edited proves nothing. Protect it:

  • Append only. Entries are added, never updated or removed through the application.
  • Written by the server. The record is created by the same operation that makes the change, so one cannot happen without the other.
  • Separate permissions. Application users, including administrators, cannot alter the log. Access to read it is itself restricted and recorded.
  • Separate storage for critical systems, so that compromising the application does not expose the log to tampering.
  • Tamper evidence. Chaining each entry to the previous one with a hash makes later changes detectable.
  • Synchronised clocks, so that sequences across systems can be reconstructed.

Attribution

Every action needs a real identity behind it.

  • No shared accounts. If three people use "admin", the log cannot say who did what.
  • Service accounts are named for their purpose and limited to it.
  • When an administrator acts on behalf of a user, record both identities.
  • When an AI agent acts, record the agent, the instruction that triggered it and the person who approved the action if approval was required.

Making it usable

A record nobody can search is of little help.

  • Show the history on the record itself: open an invoice and see who created, changed and approved it.
  • Provide a search by user, by record, by action and by date range.
  • Allow export for auditors, with the export itself logged.
  • Write entries in terms a business reader understands. "Status changed from Draft to Approved" is clearer than an internal code.

Retention and privacy

Decide how long each type of entry is kept, guided by tax, accounting and industry rules. Balance this against privacy obligations. Audit entries about a person are personal data, so limit who can read them and define what happens when the retention period ends.

Reviewing the trail

Recording is half of the control. Someone should look:

  • Alerts for unusual events: changes to bank details, many failed logins, large exports, approvals outside working hours.
  • A periodic review of privileged actions.
  • A check, during internal audits, that entries exist for a sample of real transactions.

Common mistakes

  • Logging that a change happened without the old and new values.
  • Logs stored where the people being audited can edit them.
  • Timestamps in mixed time zones.
  • Shared administrator accounts.
  • Adding the audit trail after launch, leaving a gap in history.
  • No record of deletions.

Build it in from the start

Adding an audit trail later is far harder than including it in the first design, because every write operation has to be revisited. Make it a requirement from the first version.

An audit trail with before and after values, protected storage and a readable history view is standard in the systems we build through Enterprise Software. If your auditors have raised findings about traceability, contact us.

Summary

Record who, what, which record, when, from where and the before and after values for everything involving money, master data, approvals and access. Make the log append-only and out of reach of those it describes, make it searchable, keep it as long as the rules require, and review it.

Frequently asked questions

What is the difference between an audit trail and application logs?

Application logs help developers diagnose technical problems and are usually kept for a short time. An audit trail records business-relevant actions by identifiable people, is kept for years, and must be complete and protected because it may be used as evidence.

How long should audit records be kept?

It depends on the type of record and the regulations that apply to your industry. Financial and tax-related records are commonly kept for many years. Confirm the periods with your finance and legal teams and configure retention per record type.

Should the audit trail record who viewed data, not only who changed it?

For sensitive data, yes. Access to salaries, health information, identity documents or large exports of customer data should be recorded. For ordinary records, logging every view creates noise and cost without much benefit.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.