Ventrax
Compliance
What an audit trail needs to survive a dispute
Not a log of clicks. A record of who held authority, what they were shown, and when they decided — reconstructable years later.
Most systems that advertise an audit trail produce a list of clicks. Who opened what, when. That is a debugging tool, and it is nearly useless the day a transaction is challenged.
A dispute asks harder questions.
The four questions a dispute actually asks
Who had the authority to approve this, at that time? Not who holds the role today. Staff change. The person who approved a ₦300m discount in 2024 may have left, been promoted, or had their limit reduced since. The record has to say what their authority was then.
What were they looking at when they decided? An approval given against a ₦320m sale means nothing if the figure was later changed to ₦280m. The material facts at the moment of decision have to be part of the record.
What evidence existed before it was allowed to proceed? Title verification, identity checks, a signed offer. Not a tick saying "checked" — the actual document, with a hash, so it can be shown to be the same document.
Could anybody have altered the record afterwards? Including an administrator. If the answer is yes, the trail proves nothing.
Why "who clicked what" fails
Because it records the interface, not the decision. Two years later nobody cares which screen was open. They care whether the person was permitted to authorise that amount and what they knew.
An audit trail is not a history of the software. It is evidence about a business decision, and it should read that way to a lawyer.
What to insist on
- Append-only records for approvals, signatures and financial movements. Correcting something creates a new entry that supersedes the old one; it never edits it away.
- The policy version stamped on the transaction. Reconstructing why an approval routed the way it did must not depend on querying today's settings, because those have changed.
- Signatures bound to a document version and a hash. "She signed a different version" is then answerable rather than arguable.
- Separation of duties enforced by the system. The person who raised it cannot approve it — as a rule that cannot be bypassed, not as a policy everyone is told about.
The honest limit
None of this makes you right. It makes you able to show what happened, which is a different and more achievable thing. If the underlying decision was poor, a perfect audit trail documents a poor decision very clearly.
That is still worth having. Most disputes are lost not because someone did the wrong thing, but because nobody could demonstrate what was done at all.