How to set an approver rule for the accounts payable team

Write one line per agent action: who may approve it, up to what amount, with which certificate. In accounts payable, clerks approve held postings and supplier queries; payment runs need two people, neither of whom set the limit; supplier bank detail changes are always held and verified by someone other than the clerk who received the request.

What is an approver rule for accounts payable, and who owns it?

An approver rule says who may release each action an agent holds. The agent never decides who approves; it holds the action for a named role, and the rule decides which people hold that role. In accounts payable the stakes are plain: money leaves the business and is hard to recover. Our explainer on what accounts payable is covers the process itself.

The financial controller or head of AP owns the rule. The second line signs it off. The agent owner makes sure the agent holds the right actions for the right roles. Our guide to AI agent skills by role sets out what each approver needs to know.

What are the steps?

1. Head of AP: lists the agent's actions by depth. Depth 1: reads invoices and matches them to purchase orders and receipts. Depth 2: drafts supplier queries and payment proposals. Depth 3: posts matched invoices within tolerance and sends remittance advice. Depth 4: releases a payment run or changes supplier bank details.
2. Head of AP: assigns an approver role to each held action. Tolerance exceptions go to AP clerks. Payment runs go to the AP manager plus a second approver from finance. Bank detail changes go to a clerk who did not receive the request, after a call-back to a number already on file.
3. Head of AP: sets amount bands. Below a set amount, one approver; above it, two; above a higher amount, a finance director as second.
4. Head of AP: ties each role to a current certificate. For example: approving depth 3 exceptions needs a current operator-level certificate; approving depth 4 needs that plus two years in AP.
5. Second line: checks separation and signs off.
6. Agent owner: configures the holds so the agent routes each held action to the right role, and files the rule with the agent's record.

Which accounts payable actions need two people?

Two actions stand out. A payment run moves money in bulk, and an error repeats across every line. The approver who signs it should see the total, the count, any new payees and any line above the single-payment limit. A second approver checks the same view independently.

A supplier bank detail change is the classic fraud route. The request usually arrives by email, which is an external source and cannot by itself authorise anything. The agent holds the change, notes the provenance, and the approver confirms by calling the supplier on a number already held, not one in the email. The person who approves the change must not be the person who approves the next payment to that supplier on the same day.

Anything the platform withholds, such as reversing a settled payment on a rail where that is withheld, cannot be approved by anyone through the agent. A person handles it through the normal process.

Which controls make the rule work, and what evidence do they leave?

Named roles, named people. Evidence: the approver authority matrix for accounts payable, versioned.

Approval rights expire with the certificate. When an approver's certificate lapses, the agent stops routing held actions to them. Evidence: approver list compared with certificate expiry dates on the day of each approval.

No self-approval. The person who set the limit, built the agent or raised the request does not approve. Evidence: the verdict record names every approver.

Provenance shown at approval. The approver sees which facts are sealed (from the ledger), signed (from a verified supplier portal) or external (from an email). Evidence: the provenance stamps on the held action.

Call-back recorded for bank changes. Evidence: the number called and the person spoken to, on the held action.

What should you measure?

• Held exceptions per hundred invoices, by cause. A rise points to poor PO data or a tolerance set too tight.
• Payment runs released without a second approver. The target is none.
• Bank detail changes approved without a recorded call-back. The target is none.
• Approvals by people whose certificate had lapsed. The target is none.
• Time from hold to release on payment runs, against your payment terms.

The competency matrix for the accounts payable team shows whether you have enough certified approvers to cover leave and month end.

Where does it usually go wrong?

Month end collapses the separation. With half the team away, the AP manager approves both sides. Name deputies before month end, not during it.

Tolerance approvals become automatic. Clerks release every held posting because they always have. Sample them; a held posting released unchanged every time may mean the tolerance needs revisiting through the process owner, not ignoring.

Email treated as authority. A senior name on an email asking for an urgent payment is still external. The rule should say so in plain words.

Copying another team's rule. Lending and collections have their own risks; compare the approver rule for the lending team and the approver rule for the collections team to see how different the bands and roles look.

Where the Academy fits

Pryme Intelligence Academy's Operator track is built for AP clerks and team leads who review held actions every day, with module tests set in their own industry and role. Certified Pryme Operator is valid for 12 months, so an approver rule tied to it renews naturally. The admin view shows each person's certificate and expiry date.