Start with why it was held. The agent's record names the bound that stopped it, which tells the clerk what to check: the payment limit, a bank detail change, a failed match or a suspected duplicate. The clerk confirms the facts against the system of record, then approves, edits or declines with a reason.
What kinds of action does an AP agent hold?
Most AP agents run at depth 3 for routine work, matching invoices to purchase orders and goods receipts and scheduling payment within the customer's limits. Paying money is depth 4, so anything outside the routine is held for a named person. The common held items are:
- Payments above the clerk's or the agent's limit, held by the customer's own limits.
- First payments to a new supplier, held because there is no payment history to compare.
- Changes to supplier bank details, the single most important hold in AP.
- Invoices that fail the three-way match: price, quantity or receipt does not agree.
- Suspected duplicates: same supplier, similar amount, similar date or reference.
Each one calls for a different check. Opening the invoice and eyeballing it misses the reason the agent stopped.
What should the clerk check, item by item?
| Held because | What to check | Where the truth lives |
|---|---|---|
| Amount above limit | Purchase order value, approvals on the PO, budget owner | The purchasing system, a sealed source |
| New supplier | Supplier onboarding completed, due diligence on file | The supplier master file |
| Bank detail change | Whether the change was verified by call-back to a contact already on file | The supplier master and its change log, never the email |
| Match failure | Which line failed, and whether a credit note or revised receipt explains it | The goods receipt and PO |
| Possible duplicate | Earlier payment's reference, amount, date and status | The general ledger and payment history |
The provenance column is where clerks earn their place. An invoice that arrives by email is an external fact. A request to update bank details in that email is also external. An external claim cannot authorise a payment, so no amount of matching makes an emailed bank change safe to approve without verification through a known channel.
How should the clerk decide?
Approve when every fact the agent relied on traces to a sealed or signed source and the held reason is resolved, for instance the budget owner has approved the over-limit amount.
Edit when the action is right in principle but a detail is wrong: pay the amount actually received rather than the amount invoiced, or move the payment date to the agreed terms. The edit and its reason go into the record.
Decline when a fact cannot be confirmed, the bank change was not verified, or the invoice is a duplicate. Decline with a reason code and a sentence: "Declined: bank details changed by email on the invoice, call-back to the number on file not yet completed."
The reason is what the next clerk, the auditor and the agent's owner will read. Recurring corrections should be fed back; how to teach accounts payable clerks to bank corrections that improve an AI agent covers that habit.
An example: the urgent supplier email
Take a distribution company's AP queue on a Thursday. The agent holds a payment of 40,000 to a long-standing haulier. The record says the bank details on the invoice differ from the supplier master, and the email asked for urgent payment before the weekend.
The clerk does not reply to the email. They ring the haulier on the number in the supplier master, learn that the haulier has not changed banks, and decline the payment with that reason. They report the email as suspected fraud. The original invoice is then paid to the details on file. The record shows the hold, the call-back, the decline and the report: a complete account of a near miss.
Which controls keep the hold meaningful?
- No bulk approval of depth 4 holds. Each payment is decided individually.
- Approval rights match authority. The clerk can only release payments up to their own limit; above it, the hold routes on.
- Bank changes are always held. This is a customer limit that should not be relaxed for convenience.
- Training ties to rights. Many businesses only let clerks approve held payments once they hold a current reviewer certificate.
Compare how other roles handle their holds in how compliance officers handle an action an AI agent has held, and see the market detail for AP clerks in logistics in Germany. The full role map is in AI agent skills by role.
Where the Academy fits
The Operator track in Pryme Intelligence Academy trains this exact routine on the real product: reading the decision chain, checking provenance, and approving, editing or declining with a reason. Module tests are set in the learner's own industry and role, so an AP clerk practises on held supplier payments. The practicum is two weeks of real review decisions in which a missed red line fails the candidate.
Questions people ask
Can the clerk approve a held payment just because the PO matches?
Only if the hold was about the match. If the hold was about bank details or a new supplier, the match does not resolve the reason it was held.
What if the supplier is pressing for payment?
Urgency is a common feature of payment fraud. Verify first through a known channel; the record will show why the payment waited.
Should the clerk fix the supplier master themselves?
Only if their role allows it and the change has been verified. Many businesses separate updating bank details from approving payments to them.