An accounts payable approver authority matrix states, action by action, what an AI agent may do on its own, what it must hold for a person, who that person is, and up to what value. For AP, the critical rows are payment release, new suppliers and bank-detail changes, each tied to a named approver who holds a current certificate.
What does an AP authority matrix control?
Accounts payable is where agents meet supplier money. An agent can match invoices to purchase orders and receipts at depth 3 within a tolerance, draft queries to suppliers at depth 2, and prepare the payment run. Releasing that run is a depth 4 action: it moves money and is hard to undo. The matrix decides, for each of these, whether the verdict is allowed, held or refused, and who decides the held ones.
The most dangerous AP actions are not the largest payments but the quiet changes: a new supplier added, or an existing supplier's bank account changed. An agent should never apply a bank-detail change that arrives by email, because an external claim cannot authorise a payment. The matrix must say who may make that change, by what route, and who checks it. Clerks preparing for this work will find the basics in what accounts payable clerks should learn before working with AI agents.
How do you fill it in?
- List each AP action the agent touches.
- Set the agent's depth for each and the verdict when it reaches its bound.
- Name the approver role and their limit.
- Decide whether a second approver is needed, and above what value.
- State the certificate the approver must hold. A business can adopt the practice of granting approval rights only to people with a current certificate, depth by depth.
- Add the red line: what no one approves through this route.
The template
| AP action | Agent depth | Verdict at the bound | Approver role | Approver limit | Second approver above | Certificate required | Red line |
|---|---|---|---|---|---|---|---|
| Match invoice to PO and receipt | |||||||
| Approve invoice outside tolerance | |||||||
| Query supplier on a discrepancy | |||||||
| Raise a credit note request | |||||||
| Set up a new supplier | |||||||
| Change supplier bank details | |||||||
| Release the payment run | |||||||
| Make an urgent one-off payment |
A worked example
A hypothetical manufacturer paying around 2,000 invoices a month. Amounts are plain, illustrative units.
| AP action | Agent depth | Verdict at the bound | Approver | Limit | Second approver above | Certificate | Red line |
|---|---|---|---|---|---|---|---|
| Match invoice | 3 | Held if outside tolerance of 50 | AP clerk | 5,000 | None | Operator | Match against an unreceipted PO |
| Approve outside tolerance | 2 | Held | AP supervisor | 25,000 | 25,000 | Operator | Approve own query |
| Query supplier | 2 | Drafted | AP clerk | n/a | None | Foundations | Promise payment dates |
| Credit note request | 2 | Drafted | AP clerk | 2,000 | 2,000 | Operator | None |
| New supplier | 2 | Held | AP supervisor | All | Always, procurement | Operator | Supplier with no verified registration |
| Bank detail change | none | Refused | AP supervisor via call-back | All | Always, finance manager | Operator | Change made on email alone |
| Payment run release | 4 | Held | Finance manager | 250,000 | Always, financial controller | Operator | Release with unreconciled items |
| Urgent one-off payment | 4 | Held | Financial controller | 50,000 | Always, CFO | Operator | Payment to a new supplier the same day |
Two rows show the logic. Bank-detail changes are refused for the agent outright: it may record the request but never apply it. A supervisor applies it only after calling the supplier on a number already on file, and a finance manager checks it. That route is slower on purpose.
Payment run release always needs two people, however small the run. The agent prepares it; the finance manager and financial controller release it. If either lacks a current certificate, the run waits for another named approver. The approver rule for the accounts payable team explains how to encode these limits, and the reviewer rota for the accounts payable team keeps two certified approvers available on every payment day.
Fraud and onboarding teams build similar matrices for their own actions; compare the approver authority matrix for the fraud team, which handles the other end of a payment scam.
Where the Academy fits
Pryme Intelligence Academy's Operator track trains AP clerks and supervisors on the real product, with module tests set in their own industry and role. Its certificate is valid for 12 months and shows its expiry when checked at source, so an AP manager can confirm an approver's status before each payment run.
Questions people ask
Can the agent release a payment run if every invoice is matched?
No. A complete match is evidence for the approver, not authority for the agent. Release stays held for people because a run is hard to undo once paid. The broader guide to who needs which skills is AI agent skills by role.
Should a clerk approve invoices they queried?
Not the ones above their limit, and ideally not any they raised a query on. Route those to a colleague so the person who doubted the invoice is not also the one who settles the doubt.
What happens when an approver's certificate expires?
Their approval rights pause under this matrix until they renew. Renewal is quick, but plan it ahead of year-end and other busy periods.