Skip to content
← Back to blog

Internal Controls in Accounts Payable: 10 Key Controls and Best Practices

April 17, 2026•9 min read•1,735 words

Written by Ademola Afolabi, Founder, Aequo AP. Reviewed and updated October 30, 2026.

The 10 internal controls every accounts payable process needs, from segregation of duties and vendor master changes to three-way matching, duplicate checks and payment release, with what auditors test and how small teams cover the gaps.

The key internal controls in accounts payable are: (1) segregation of duties, (2) controlled vendor master changes, (3) an approval authority matrix, (4) PO and three-way matching with tolerances, (5) duplicate invoice checks before payment, (6) one logged intake channel for invoices, (7) dual control over payment release, (8) restricted and reviewed system access, (9) regular reconciliations, and (10) a complete audit trail with period-end cut-off. Together they make sure you only pay real vendors, for goods and services you ordered and received, once, at the agreed price, with someone other than the payer signing off.

The rest of this guide explains each control, what it prevents, how a small team can run it, and what an auditor will ask to see. A printable 15-point checklist and the evidence auditors expect for each control follow the ten controls.

The 10 key AP internal controls at a glance

#ControlTypeWhat it prevents
1Segregation of dutiesPreventiveOne person creating, approving and paying a fictitious or inflated bill
2Vendor master change controlsPreventiveFake vendors and bank-detail fraud
3Approval authority matrixPreventiveSpending without the right sign-off
4PO and three-way matchingPreventivePaying for goods not ordered or not received, or at the wrong price
5Duplicate invoice checksPreventivePaying the same bill twice
6Single, logged intake channelPreventiveLost invoices, late fees and side-door bills
7Dual control over payment releasePreventiveUnauthorized or altered payment batches
8Restricted, reviewed system accessPreventive and detectiveAccess creep that quietly breaks segregation of duties
9ReconciliationsDetectiveErrors and duplicates that got through
10Audit trail and cut-offDetectiveUnexplained changes and unrecorded liabilities at period end

1. Segregation of duties

No single person should control a payment from vendor setup through to reconciliation. The five steps to separate are vendor setup, invoice entry, approval, payment release and reconciliation.

In a team of three to six people, full separation is rarely possible. Break the two most dangerous combinations first: vendor setup plus payment release, and invoice entry plus reconciliation. Where one person still covers two steps, add a compensating control, such as a controller reviewing every payment batch before it is released. See segregation of duties in accounts payable for a role map.

What auditors test: whether the system permissions match the documented roles, and whether anyone can complete a payment end to end.

2. Vendor master change controls

Most AP fraud starts in the vendor master file: a fictitious vendor, or a real vendor whose bank details were changed by a fraudster's email.

  • Verify new vendors before the first payment: legal name, address, tax ID from a W-9, and bank details confirmed with the vendor directly.
  • Confirm every bank-detail change by calling the vendor on a number you already had, never one from the change request.
  • Have someone other than the requester approve vendor additions and changes, and review a report of changes each month.
  • Deactivate vendors that have not been paid in 12 to 18 months, and merge duplicate vendor records.

See vendor fraud red flags for the warning signs.

3. Approval authority matrix

Write down who can approve what, by amount and by department or cost center, and make the system enforce it. A typical matrix sends smaller invoices to the budget owner, larger ones to a director and the largest to the CFO or owner, with a second approver above a threshold.

Keep the matrix short enough that people follow it, set rules for delegation when an approver is away, and review it when the org chart changes. Invoice approval routing covers the design in detail.

What auditors test: a sample of paid invoices, checked against the matrix in force on the approval date.

4. PO and three-way matching with tolerances

For goods, match each invoice to the purchase order and the receiving record before it can be paid; for services, a two-way match to the PO is common. Set tolerances for price and quantity differences, and send anything outside them to an exception queue with a named owner.

Overrides are where this control usually fails. If someone can push a mismatch through without a documented reason and approval, the control exists only on paper. See three-way matching for worked examples.

5. Duplicate invoice checks before payment

Check each invoice against invoices already entered or paid before it is approved: same vendor and invoice number, the same number after removing prefixes and leading zeros, and the same amount within a few days. Exact-match checks in accounting software miss many real duplicates, which differ by a character or arrive under a second vendor record.

APQC benchmarking puts duplicate or erroneous payments at 0.8% of annual disbursements for top performers and 2% for bottom performers. See how to handle and prevent duplicate payments.

6. One logged intake channel

Ask vendors to send invoices to one AP inbox or portal, not to individual buyers. Log every invoice on arrival with the date received. This stops invoices being paid outside the process, makes late-payment fees traceable, and gives you a complete population for cut-off at month end.

7. Dual control over payment release

The person who prepares a payment batch should not be the person who releases it at the bank. Use your bank's dual-authorization settings, set payment limits per user, and compare the released batch with the approved batch. Positive pay, where your bank checks presented checks against a list you send, adds a detective layer for check fraud.

8. Restricted and reviewed system access

Segregation of duties usually fails through access creep: temporary permissions granted at quarter-end that nobody removes. Give each user only the role they need in the AP tool, the accounting system and the bank portal, and review the user list every quarter. Remove leavers on their last day.

9. Reconciliations

Detective controls catch what the preventive ones miss:

  • AP subledger to general ledger every month.
  • Vendor statements for your largest vendors, which reveal missing invoices, unapplied credits and duplicate payments. See vendor statement reconciliation.
  • A periodic duplicate review of paid invoices for the last 12 to 24 months.

10. Audit trail and period-end cut-off

Every invoice should carry a record of who captured, coded, approved, changed and paid it, and when. At period end, review invoices received after the close and open POs with receipts but no invoice, so unrecorded liabilities are accrued. See the AP month-end close checklist.

Preventive vs detective: what a small team should do first

If you can only fix three things this quarter, fix the ones that stop money leaving:

  1. Separate vendor setup from payment release, with call-back verification of bank changes.
  2. Enforce the approval matrix in the system, not by email.
  3. Run duplicate checks before every payment run.

Then add the detective layer: monthly vendor statement reconciliation and a quarterly access review. Test yourself against what auditors look for with the AP audit readiness assessment and the accounts payable audit checklist.

Printable AP internal controls checklist

Use this to assess your control environment. Each control should be documented, applied every time and testable by an auditor.

  1. Segregation of duties between invoice entry, approval and payment release
  2. PO matching before payment for all goods purchases
  3. Vendor master changes approved by a second person
  4. Duplicate invoice checks before posting and before each payment run
  5. Approval limits by amount and expense category, enforced in the system
  6. Three-way match enforced for physical goods
  7. Exception escalation and resolution tracked against an SLA
  8. Payment batches reviewed and released under dual authorization
  9. Bank details verified for new vendors and for every bank-detail change
  10. AP subledger reconciled to the general ledger every month
  11. Role-based access to the AP system and banking portals, reviewed quarterly
  12. An audit trail for every approval, override and payment
  13. Invoices, POs, receipts and approvals retained for the required period
  14. Vendor statements reconciled periodically for your largest vendors
  15. Open payables aging reviewed, with outliers investigated

Evidence to keep for each control. Auditors want to see that a control exists, runs consistently and works:

  • Policy: a written description of the control, who owns it and how it operates
  • Execution: system logs, approval records, reconciliation sign-offs and exception reports
  • Monitoring: periodic review reports and control testing results
  • Remediation: a record of each control failure and the fix

Delegation rules. Approvers will be away. Pre-authorize delegations rather than allowing ad hoc ones, give every delegation an end date, make sure a delegate cannot approve their own expenses, and log delegated approvals separately so they can be sampled.

The findings auditors report most often: the same person entering and approving invoices, missing approval documentation, invoices paid without a PO match, vendor master changes without a second approval, no periodic duplicate payment review, and an AP subledger not reconciled to the GL each month.

How Aequo AP supports these controls

Aequo AP applies several of these controls in the workflow rather than in a policy document:

  • Approvals (control 3): route invoices by amount range, vendor, GL code or department to one or more approval steps, with reminders, escalation and delegation when an approver is away.
  • Matching (control 4): two-way and three-way matching against purchase orders and delivery notes, with tolerances set globally or per supplier. Invoices that fail a match become exceptions with a reason, an owner and an SLA.
  • Duplicates (control 5): each invoice is compared with past invoices from the same vendor, including near-identical invoice numbers and amounts within about 2%, and given a risk level with the evidence behind it.
  • Access (controls 1 and 8): owner, admin and member roles plus custom approval roles decide who can code, approve and sync. SAML single sign-on is available.
  • Monitoring and audit trail (controls 1 and 10): a controls monitor lists open segregation-of-duties conflicts, suspected duplicates, tolerance breaches and SLA breaches, and every invoice keeps a history of who did what and when.
  • Vendor tax IDs (control 2): request W-9s from vendors, and store tax IDs encrypted and masked on screen.

Approved bills sync to QuickBooks Online, Xero, FreshBooks, Zoho Books or Business Central; Oracle NetSuite and Sage Intacct connectors are in early access. Paying vendors from Aequo is coming soon, so payment release (control 7) stays in your bank or accounting system for now. See pricing or book a demo to see the controls monitor with your own invoices.

Ready to modernize your AP workflow?

See how Aequo automates invoice processing, exception management, and approvals for finance teams.