Audit Trail
An audit trail in accounts payable is the time-stamped record of every action on an invoice or vendor, including who captured, edited, matched, approved and paid it and when, so each payment can be traced and explained.
Last updated
Quick answer
What is an audit trail in accounts payable?
An audit trail in accounts payable is the time-stamped record of every action on an invoice, vendor and payment: who captured, edited, matched, approved and paid it, when, and what changed. It links each payment to its invoice, purchase order, receipt and approvals, so auditors can confirm every payment was authorized and correct.
An audit trail records who did what to an invoice and when, from capture to payment. It lets auditors confirm that approvals happened before payment and lets finance teams trace duplicate or erroneous payments, which APQC benchmarking puts at 0.8% to 2% of annual disbursements.
Key Industry Data
- Duplicate or erroneous payments: 0.8% of annual disbursements at top performers, 2% at bottom performers: APQC Open Standards Benchmarking, via CFO.com (2020)
Definition
An AP audit trail links each payment back to its invoice, purchase order, receipt and approvals, and records every change along the way, such as an edited amount, a new bank account or an override of a matching exception. Auditors use it to test controls, and finance teams use it to investigate disputes, duplicate payments and fraud. It should be complete, time-stamped and not editable by the people whose actions it records.
What a complete AP audit trail records
Each entry answers four questions: who acted, what they did, when, and what changed. For an invoice that means when and how it arrived, every field edited after capture with the old and new value, the PO and receipt it was matched to, any tolerance override and the reason given, each approval or rejection, when it was posted to the ledger, and the payment that settled it.
The vendor master file needs its own trail. Changes to a vendor's bank account, address or tax ID are where payment fraud usually starts, so each change should show who made it, who approved it and when.
Document trail versus system log
The document trail is the paper chain: purchase order, goods receipt, invoice, approval and payment record. The system log is the electronic history of actions in the software. Auditors want both, connected. A signed approval email that cannot be tied to the invoice it approved is weak evidence; an approval recorded against the invoice with a user and timestamp is strong evidence.
How auditors use it
An auditor picks a sample of payments and walks each one backward to its approval, invoice, receipt and order, checking that each step happened, in the right order, by someone allowed to do it. They also go forward, from invoices to payments, to check nothing was paid twice. A complete trail turns a week of evidence requests into a report.
| Event | Record | Evidence an auditor asks for |
|---|---|---|
| Invoice received | Date, channel, original file | The invoice as the supplier sent it |
| Field edited after capture | User, time, old and new value | Why an amount or date changed |
| Matched to PO and receipt | Documents matched, variances, tolerance applied | That the invoice agrees with what was ordered and received |
| Exception overridden | User, time, reason | That a variance was reviewed, not missed |
| Approved or rejected | Approver, time, approval rule | Authorization by someone allowed to approve |
| Vendor bank details changed | Who changed, who verified, when | That the change was independently confirmed |
| Paid | Payment date, method, amount, run | Payment matches an approved invoice |
| System | Where to find the history |
|---|---|
| QuickBooks Online | The audit log records who added, changed or deleted transactions and when; each transaction also shows its own history. |
| Xero | Each transaction has a History and Notes section showing who created, edited and approved it. |
| NetSuite | The System Notes on each record list field changes with the user and date. |
| Business Central | The change log records field-level changes once it is turned on and set up for the tables you choose; posted entries carry the user ID. |
| Sage Intacct | Records keep an audit trail of who created and changed them and when. |
Approvals made by email outside these systems do not appear in their histories, which is the most common gap auditors find.
Why It Matters
Audit trails are how you prove controls worked. They support SOX testing at public companies and year-end audits everywhere else, answer supplier disputes, and are the first place to look when a payment goes to the wrong account. APQC benchmarking puts duplicate or erroneous payments at 0.8% to 2% of annual disbursements; the trail is how you find out which ones happened and why.
Examples
Tracing a payment
An auditor picks a $14,800 payment. The trail shows the invoice arrived by email on June 3, matched to PO 7781 the same day, was approved by the operations manager on June 5 and was paid on June 12.
Investigating a change
A vendor's bank account was changed on August 9. The trail shows which user made the change, when, and who approved it, which is the first thing to check if a payment goes to the wrong account.
An override explained
An invoice for $5,300 was matched to a $5,000 PO, a 6% variance against a 2% tolerance. The trail shows the buyer approved the override on May 14 with the note 'fuel surcharge agreed by phone', so the auditor can see the variance was reviewed rather than missed.
Common Mistakes
Approvals by email outside the system
An email saying 'OK to pay' is hard to tie to the invoice. Record approvals against the invoice so the user and time are captured with it.
Shared logins
If several people use one account, the trail shows the account, not the person. Give each user their own login.
Logs that users can edit
The people whose actions are recorded should not be able to change or delete the record.
No reason recorded on overrides
Require a short note whenever someone overrides a matching exception or approves outside the rules.
Ignoring the vendor master file
Track changes to vendor bank details and tax IDs as carefully as invoice changes, because that is where fraud often starts.
In Practice
- Make sure every user has their own login.
- Record approvals, edits and overrides in the AP system, not in email.
- Require a reason for every exception override.
- Review vendor bank detail changes monthly with the history of who made and approved them.
- Before an audit, pull a sample of payments and check you can trace each one to its invoice, PO, receipt and approval.
- Keep records for the period your jurisdiction and industry require.
Tools and Further Reading
- Segregation of duties: The control the audit trail provides evidence for.
- AP audit readiness assessment: Check how ready your AP records are for an audit.
- Two-way matching: The matching evidence an audit trail links to.
- Payment run: Where approval and release are recorded.
- Free accounts payable course: Seven self-paced modules covering the AP process, matching, approvals, paying bills, the close and AP metrics.
How Aequo AP Helps
Every invoice in Aequo AP keeps a history of who did what and when, from capture through coding, approval and sync to your accounting system, alongside a workspace-level log of system actions. Revealing a vendor's full tax ID needs owner or admin permission and is logged, and the controls monitor shows open segregation-of-duties conflicts and suspected duplicates.
Start Free TrialFrequently Asked Questions
What should an AP audit trail include?
Who created or changed each record, what changed, when, the before and after values, the approval chain, and the links between invoice, PO, receipt and payment.
Why do auditors need an AP audit trail?
To confirm that payments were authorized, matched to real purchases and approved by the right people before money left the business.
What is an example of an audit trail?
A payment record that links to the invoice, the PO it matched, the goods receipt, the manager who approved it with a timestamp, and the date it was paid.
What are the types of audit trail?
Broadly, the document trail (orders, receipts, invoices, payment records) and the system log (user actions in software). An AP audit trail connects the two.
How long should you keep AP records?
It depends on your jurisdiction and industry. Many US businesses keep supporting documents for at least seven years; check the requirement with your accountant or legal adviser.
Can an audit trail be edited?
It should not be editable by the people whose actions it records. If entries can be changed or deleted, auditors will not rely on it.
Category
complianceRelated Terms
Ready to automate your AP?
See how Aequo AP can transform your accounts payable process.