Accounts payable clerks review an agent's decisions in a fixed order: open the record, see the verdict, find the bound that decided it, check the facts against the ledger and supplier master, then approve, edit or decline with a reason. Payments the agent completed on its own get the same discipline, by sample.
What does the clerk actually review?
Three streams of decisions reach an AP clerk:
- Held actions, which wait for the clerk before anything happens. These are the urgent ones.
- Refused actions, where the agent stopped because the request was outside its bounds, for example an invoice from a supplier not on the master file. Someone has to deal with the underlying invoice.
- Allowed actions, routine matches and scheduled payments the agent completed at depth 3. These are reviewed by sample, because a decision the agent was allowed to make can still be wrong.
Most teams spend their attention on the first stream. The third is where slow problems hide: a matching rule that is slightly off, applied correctly a thousand times.
What are the steps?
- Read the verdict and the deciding bound. The record states which of the five bounds decided: the agent's role scope, its certificate, its sources, the customer's own limits or the platform guardrails. That tells you what kind of problem you are looking at.
- List the facts the agent used. Invoice, purchase order, goods receipt, supplier record, payment terms. Note where each came from. The PO and receipt are sealed from the purchasing system; the invoice is usually external.
- Check the facts that matter for this verdict. For a match decision, the line values. For a payment, the bank details against the supplier master. For a duplicate, the earlier payment.
- Compare with policy. Payment terms, approval limits, early payment discount rules.
- Decide. Approve, edit or decline, within your own authority.
- Write the reason. One sentence that a colleague, an auditor or the agent's owner can act on.
- Flag patterns. If you have made the same correction three times this week, the agent's sources or limits need changing, not just the individual items.
What may the agent do, and what stays with the clerk?
| Decision | Agent | Clerk |
|---|---|---|
| Match invoice to PO and receipt within tolerance | Does it, depth 3 | Samples it |
| Schedule payment within terms and the customer's limits | Does it, depth 3 | Samples it |
| Pay above limit, a new supplier, or after a bank change | Drafts and holds | Decides |
| Pay to details from an emailed invoice without verification | Never | Verifies through a known channel |
| Resolve a supplier dispute | Drafts a summary | Handles the relationship |
The line between the first two rows and the third is set by the business, not the agent. What accounts payable clerks should never let an AI agent do lists the hard limits.
An example: a sample that found a pattern
Take an AP team in a logistics firm that reviews a sample of 20 allowed payments each week. One week, a clerk notices that three payments to different suppliers took an early payment discount the suppliers had not offered. The record shows the agent applied the discount from a default terms field in the supplier master, a sealed source, which had been filled in wrongly when the suppliers were set up.
The agent behaved correctly given its sources. The fix is in the data. The clerk edits the three payments before they are released, records the reason, and raises the master data error with the supplier team. Without the sample review, the pattern would have continued until a supplier complained.
Which controls make the review count?
- Reviewers have authority to decline. Access to the queue is not enough.
- Samples are random and recorded. Clerks do not choose the easy ones.
- Reasons are mandatory. An approval with no reason is indistinguishable from a rubber stamp.
- Time per decision is watched. A sudden drop suggests people have stopped reading.
- Rights follow training. Clerks who approve depth 4 holds should hold a current reviewer certificate, such as Certified Pryme Operator from Pryme Intelligence Academy, and lose approval rights while it is lapsed.
Training the whole team to work this way is covered in how to train the accounts payable team to review AI agent decisions. The local rules that shape AP review in Asia are in the brief on AP clerks in logistics in Singapore. Whether review work is a lasting part of the job is answered in will AI agents replace accounts payable clerks. The role map is in AI agent skills by role.
Questions people ask
How many allowed decisions should a clerk sample?
Enough to see patterns within a week or two. Start with a fixed number per week and increase it after any change to the agent, its sources or its limits.
What if the clerk disagrees with a refusal?
A refusal means the action was outside the agent's bounds. The clerk handles the invoice manually if it is legitimate, and raises a change request if the bound itself looks wrong.
Is reviewing the agent's work slower than doing it manually?
For held items, about the same per item, but there are far fewer of them. The time saved on routine matching is what pays for careful review.