PrymeIntelligence

AI agent skills by role·Answer

What should accounts payable clerks never let an AI agent do?

Accounts payable clerks should never let an AI agent change supplier bank details, pay new suppliers, release payment runs or clear fraud holds. Why.

Seven things, each because it would let an agent pay the wrong party or weaken the check on it. Accounts payable clerks should never let an agent change supplier bank details, set up and pay a new supplier, release a payment run, pay a suspected duplicate, clear a fraud hold, approve payments, or pay unmatched invoices above the threshold.

What are the seven red lines?

1. Changing supplier bank details on a request. An emailed letter, a phone call or a message on a supplier portal is an external claim, and an external claim cannot authorise a payment or change where one goes. Bank detail fraud is the most common way money leaves an AP function wrongly. Verification belongs to a person who calls the supplier on a number already held.

2. Creating a new supplier and paying it in the same cycle. New supplier set-up needs due diligence, a verified bank account and a named approver. An agent can draft the set-up form; a person completes it. Paying a brand-new supplier immediately is the shape of many frauds.

3. Releasing the payment run. Releasing money is depth 4: hard to undo. Even where an agent is certified at depth 4 for small payments to verified suppliers, the run as a whole, and anything above the agent’s limit, should be released by a named approver.

4. Paying an invoice flagged as a possible duplicate. Duplicates look nearly identical by design, sometimes with a changed reference or date. If the agent is unsure, the clerk decides. Recovering a duplicate payment costs far more than the minute it takes to check.

5. Clearing a fraud hold or payment block. Holds are placed for reasons the agent may not see: an investigation, a dispute, a legal instruction. Only the person or team who placed it, or someone with that authority, should lift it.

6. Approving its own drafted payment, or another agent’s. The preparer and the approver must be different, and an agent is never the approver of a held action. Otherwise the control disappears.

7. Paying without a matched order and receipt above the threshold. Below a small value, firms may allow non-PO invoices to be paid within limits. Above it, a person confirms the goods or services were received and the cost was agreed.

Why do these stay with a person rather than a better agent?

Because performance is not the issue. An agent working within five bounds, role scope, certificate, sources, the firm’s own limits and the platform guardrails, catches most of these cases and refuses them. But each red line protects against a situation where the agent’s inputs themselves may be wrong or manipulated. A forged letter, a spoofed email domain, a supplier who is real but compromised. A person can step outside the inputs: call, check, question.

They also carry accountability. When an auditor asks who authorised a payment to a changed account, the answer must be a name.

How do these red lines appear in practice?

Rarely labelled. Take an AP clerk at a logistics firm. A held item shows an ordinary haulier invoice, matched to a purchase order and receipt, held only because it is above the agent’s payment limit. The clerk opens the facts and sees the bank account on the payment proposal differs from last month’s. The supplier record was changed three days earlier, by a colleague, on the strength of an email.

The agent had treated the supplier record as sealed because it came from the supplier master. The clerk declines, escalates to the AP manager, and the supplier is called on the number from the original contract. The email was fraudulent.

The lesson for the team: the red line applies to the record change, not just to the payment. The detailed review method is in how AP clerks review an agent’s decisions.

How do clerks enforce red lines day to day?

Write them in the firm’s own limits, so the agent refuses or holds them automatically. Keep a one-page list at every reviewer’s desk with an example of each. Decline and escalate, never edit-and-approve. Record the reason so the pattern can be seen. Calibrate as a team monthly using real held items.

Clerks who hold these lines are why AP stays safe with agents; see why accounts payable clerks are the real control. It also answers a common worry, covered in will AI agents replace accounts payable clerks?. For market differences, compare AP clerk training in UK logistics and in Kenya. The overview is in AI agent skills by role.

Where the Academy fits

Red lines are central to the Operator track of Pryme Intelligence Academy. Its practicum is two weeks of real review decisions, and the standard includes no missed red line, signed off by a Pryme assessor. Module tests are set in the learner’s own industry and role, so an AP clerk is tested on payment cases.

Questions people ask

Can a red line be relaxed for trusted suppliers?

Not for bank detail changes. Trust is exactly what fraudsters exploit. Other limits, such as non-PO thresholds, can be set per supplier through governance.

What if a manager asks me to approve quickly?

Decline and escalate anyway. The record shows who approved, and urgency is a common feature of payment fraud.

Should the agent ever contact suppliers about bank changes?

It can draft an acknowledgement saying the change is being verified. The verification call is a person’s job.

Train the people who run your agents.

Pryme Intelligence Academy: free courses on the real product, audio lessons, labs in a free workspace, and certificates anyone can check on VerifyDoc.ai. Teams get seats, an admin view and a free readiness assessment.