An audit trail is the connected evidence that allows a transaction, decision or record change to be traced from origin through completion. It combines source documents, system events, approvals, versions and reconciliations so a reviewer can reconstruct what occurred.
What makes an audit trail complete?
- A stable transaction or record identifier
- The initiating request and source documents
- Material changes with dates and responsible identities
- Approvals, rejections, overrides and reasons
- Downstream execution and external references
- Final reconciliation or disposition
Audit trail vs. audit log
An Audit Log records selected system events. An audit trail is the broader chain of evidence across systems and documents. Several logs, approvals and external records may form one trail.
How should records be connected?
Carry the same business reference through the quotation, order, invoice, approval, payment and reconciliation process. Where systems use different identifiers, maintain an explicit mapping rather than relying on names, dates or amounts alone.
What breaks traceability?
Common breaks include overwritten values, approvals detached from the final version, exported files without source metadata and payments recorded without bank or provider references. Manual steps need evidence standards just as automated steps do.
