Revenew International logo

Accounts payable audit procedures are the specific tests and verification steps that turn a general commitment to payment accuracy into a repeatable, documented review. Where our guide to the accounts payable audit covers what these reviews are and why they matter, this article gets practical: which procedures to run, in what order, and how to structure them as a checklist your team can reuse.

The procedures below apply whether the review is performed internally or with an independent specialist, and whether the scope is a single business unit or an entire payment environment.

Before the Procedures: Scope and Data

Audit procedures are only as good as the data they run against. Before testing begins, define the review period, the entities and systems in scope, and the supplier categories to include. Then assemble the core data set: the accounts payable transaction file, supplier master records, purchase orders and receiving records, contracts and pricing schedules, credit memos, supplier statements, and payment history.

For a fuller treatment of scoping, objectives, and sequencing, see our step-by-step guide on how to audit accounts payable. The rest of this article assumes that groundwork is in place and focuses on the procedures themselves.

Core Accounts Payable Audit Procedures

Most effective reviews run procedures similar to these in sequence:

  • 1. Supplier master review. Test the supplier master for duplicate records, inconsistent naming, incomplete banking details, and inactive suppliers with recent payment activity. Duplicate supplier records are a leading enabler of duplicate payments.
  • 2. Duplicate payment testing. Test for exact duplicates, then for near-duplicates: same amount with different invoice numbers, same invoice across different payment methods, and the same obligation paid by different business units.
  • 3. Matching validation. Confirm that invoices were matched to purchase orders and receiving records before payment, and examine the exceptions where matching was bypassed or overridden.
  • 4. Contract price verification. Compare invoiced prices, rates, and markups against contract terms, including escalation clauses and effective dates. Pricing discrepancies concentrate where contracts are complex or recently renegotiated.
  • 5. Credit and statement reconciliation. Reconcile supplier statements against the ledger to surface unapplied credits, open balances, and missed rebates or volume discounts.
  • 6. Tax application review. Verify that sales and use tax was applied correctly by rate, jurisdiction, and taxability of the purchase, in both directions: tax paid where none was owed, and exposure where tax was owed but not paid.
  • 7. Payment-run and exception review. Examine off-cycle payments, rush payments, and manual exceptions, which bypass parts of the standard control framework and are associated with elevated error rates.
  • 8. Findings verification and documentation. Review each flagged transaction to confirm whether an error occurred, document the support for every validated finding, and record dollars identified separately from dollars recovered.

The Accounts Payable Audit Checklist

Condensed to a working checklist, a complete review confirms each of the following:

  • Review period, scope, and objectives documented
  • Complete data set assembled and validated for the period
  • Supplier master tested for duplicates and data quality
  • Duplicate and near-duplicate payment testing completed across all systems in scope
  • Matching compliance verified and exceptions examined
  • Invoiced prices verified against contract terms
  • Supplier statements reconciled; credits and rebates captured
  • Sales and use tax application reviewed
  • Manual and off-cycle payments examined
  • All findings verified, documented, and quantified
  • Root causes recorded for every confirmed finding
  • Recommendations issued and control improvements assigned an owner

Organizations that keep this checklist versioned and reuse it each cycle build an increasingly reliable picture of payment accuracy over time.

From Checklist to Audit Program

When run once, these procedures produce a snapshot. When executed on a schedule, they transform into an accounts payable audit program: a consistent discipline with defined scope, ownership, frequency, and reporting.

An audit program is important because payment environments are constantly changing. New suppliers are added, contracts are renewed, systems are migrated, and staff turnover occurs. Processes that were effective in last year’s environment may not be sufficient for this year’s. Mature programs also adapt their tools to match their transaction volumes; at an enterprise scale, reviews often encompass vast transaction populations. Using full-population analytics makes it feasible to conduct procedures such as duplicate testing and price verification at scale. Many organizations run the program internally, validate it periodically with an independent review, and add continuous monitoring where transaction volumes justify it. The step-by-step sequencing in our how to audit accounts payable guide provides a template for the internal cycle.

Conclusion

Accounts payable audit procedures are straightforward when considered individually. Their true value emerges when all procedures are conducted in sequence, using comprehensive data, following a set schedule, and carefully documenting the findings. The checklist above distinguishes between occasional audits of accounts payable and maintaining continuous awareness of payment accuracy.

Download the AP controls checklist to put these procedures to work, or request a No-Risk Review to see what a full-population review finds in your payment data.

Frequently Asked Questions

What are accounts payable audit procedures? Accounts payable audit procedures are the specific tests performed during an AP review: supplier master testing, duplicate payment testing, matching validation, contract price verification, credit and statement reconciliation, tax application review, exception review, and findings verification. Together they confirm that supplier payments were accurate, authorized, and consistent with contract terms.
What is included in an accounts payable audit checklist? A complete checklist covers scope and data preparation, supplier master quality, duplicate testing, matching compliance, contract pricing, credits and rebates, tax application, manual and off-cycle payments, and the verification, documentation, and root-cause analysis of all findings.
In what order should AP audit procedures be performed? Most reviews begin with the supplier master, because data quality issues there affect every later test, then proceed through duplicate testing, matching validation, price verification, statement reconciliation, tax review, and exception review, finishing with verification and documentation of findings.
How is an accounts payable audit program different from a one-time audit? A one-time audit produces a snapshot of payment accuracy for a defined period. An audit program repeats the procedures on a defined schedule with consistent scope, ownership, and reporting, which builds a reliable, comparable picture of payment accuracy over time.
Should audit procedures use sampling or full-population testing? Sampling can validate control design, but many payment errors occur too infrequently to appear in a sample. Full-population testing evaluates every transaction in the review period and is the more reliable approach for procedures like duplicate testing and contract price verification, particularly at high transaction volumes.
Who should perform accounts payable audit procedures? Internal audit and AP teams can run these procedures as part of routine governance. Organizations often add an independent specialist when transaction volumes are large, when systems are complex, or when leadership wants an objective validation of historical payment accuracy.
How often should accounts payable audit procedures be run? Frequency depends on transaction volume, complexity, and risk. Many organizations run the full procedure set annually, repeat targeted procedures more often, and trigger additional reviews after acquisitions, ERP implementations, or other significant changes to the payment environment.