Accounts Payable Controls Checklist: Vendor Master to Payment Run
Most AP losses come from a gap between steps, not a failure inside one. This checklist covers the whole chain.
Short answer
An accounts payable controls checklist covers six areas: the vendor master (who can add or change suppliers), invoice entry (duplicates, matching, coding), approval (limits and segregation), the payment run (review before release), bank detail changes (independent verification) and review evidence (who checked what, and when). Test each area monthly and keep the evidence.
Only a small, named group can add or change suppliers, and none of them can approve invoices or release payments.
Every new supplier is checked before the first payment: legal name, address, tax registration, bank details on letterhead or a verified portal. See new supplier onboarding checks.
A report of all vendor master changes is reviewed every month by someone who didn't make them.
Duplicate suppliers are searched for and merged or blocked. See vendor master cleanup.
Dormant suppliers are blocked so they can't be reused for a fake invoice. See ghost vendor detection.
2. Invoice entry
Invoices arrive through one controlled channel, not to individual inboxes.
Each invoice is checked for duplicates before entry: same supplier and number, same amount and date, and near-matches. See finding duplicate invoices in Excel.
PO invoices are matched to the order and goods receipt. See three-way match.
Non-PO invoices go to the budget holder for coding and approval.
Price and quantity differences above your tolerance are held, not paid.
A simple Excel duplicate test on supplier and invoice number:
Every change request is verified by calling the supplier on a number already held on file, never one in the request. See callback verification.
The change is entered by one person and approved by another.
The first payment to new bank details is flagged in the payment run review.
The supplier's usual contact is told the change has been made, by a separate channel.
6. Review evidence
A control you can't evidence is a control you can't prove. Keep, for each month:
the signed vendor master change report;
the duplicate check results and how each hit was cleared;
approved payment run reports with reviewer name and date;
call-back records for every bank detail change;
the AP subledger to general ledger reconciliation. See AP reconciliation.
How to use this checklist
Mark each control as in place, partly in place or missing.
For each missing control, name an owner and a date.
Test a sample each month: pick a few payments and trace them back through approval, entry and the vendor master.
Review the whole list at least once a year, or after any change of system or team.
Common gaps
The same person can change bank details and release payments.
Duplicate checks only look for exact invoice numbers, so "INV-104" and "104" both get paid.
Vendor master change reports exist but nobody signs them.
Out-of-cycle payments skip the review that normal runs get.
Checklist
Vendor master access limited and separate from approval and payment
Monthly vendor master change report reviewed and signed
Duplicate check run before every invoice is entered
Approval limits matrix written and followed
Payment run reviewed and released by different people
Every bank detail change verified by call-back to a number on file
Monthly evidence pack kept for every control
Sample of payments traced back each month
UK and US
UK teams say "purchase ledger" and "supplier"; US teams say "accounts payable" and "vendor". Listed US companies test these controls under the SOX framework; other businesses use them as good practice or because their auditors expect them. Check the current requirements that apply to your business.
AI Software · do it in seconds
AI Vendor Master Audit
Audits the supplier master file with an on-device AI and 28 tests: lookalike duplicates written differently, bank-detail changes before payments, vendors matching employees, and a risk score for every vendor. Runs in your browser on your own computer: nothing is uploaded.
The Accounts Payable Control System runs four duplicate-invoice tests, supplier master fraud checks and a three-way match on every invoice, with a payment run release gate that blocks release while exceptions are open. Excel, no macros, one-time price.
Restricted vendor master access, duplicate checks before entry, matching and approval limits, independent review and release of payment runs, verified bank detail changes and a monthly AP reconciliation.
How often should AP controls be tested?
Run the routine checks every month and test a sample of payments end to end. Review the whole control set at least once a year or after a system change.
Who should review vendor master changes?
Someone who cannot make the changes themselves and does not release payments, such as the financial controller.