What should accounts payable clerks learn before working with AI agents?

Before an agent touches a single invoice, an accounts payable clerk should learn five things: how far the agent may act, how it decides each action, what a held payment means, why an emailed bank letter can never authorise a payment, and how to review a draft properly. Without these, the clerk either rubber-stamps or redoes the agent’s work.

Which five things matter most?

1. Depth: how far the agent may act

Each action needs its own depth. In accounts payable, a typical starting point looks like this:

Depth is earned on evidence from the firm’s own past invoices, not switched on. Certificates lapse after 90 days, and a run that clears no depth drops the agent to depth 1 the same day, so matching can return to clerks without warning. Clerks should know what that looks like.

2. The decision chain

Every action meets five bounds at once: the agent’s role scope, its certificate, its sources, the firm’s own limits (such as payment thresholds and tolerance bands) and the platform guardrails. The lowest wins, and the verdict names which bound decided. A clerk who can read that name knows whether a held invoice is a tolerance issue, a missing purchase order or a supplier the agent may not pay.

3. Held, refused and withheld

Held means drafted and waiting for a named person: the clerk’s queue. Refused means the action was outside the agent’s bounds; the clerk may still process it manually under their own authority. Withheld means the platform refuses it on purpose for every agent at every depth. Clerks should not try to route around refusals by re-submitting differently.

4. Provenance of supplier data

This is the most important lesson for AP. Every fact reaching the agent is stamped: sealed (from the ledger or supplier master), signed (from a verified party), declared (stated by someone, unverified) or external (an emailed invoice or letter). An external claim cannot authorise a payment.

So when a supplier emails new bank details on letterhead, the agent will not change the supplier record, and the clerk must not either without verifying through a known contact. This is where most payment fraud starts.

5. How to review a draft

Read the facts, not just the total. Check the purchase order and receipt the agent matched, the tax treatment, the coding, and any declared or external facts it relied on. Approve, edit, decline or escalate, and note why when changing something. Those notes improve the agent’s brief before its next certification.

What does good review look like on a real invoice?

Take an AP clerk at a logistics firm. A held invoice from a haulier is 600 over the purchase order. The agent has matched it to a receipt for the right loads and flagged that the excess appears to be a fuel surcharge not in the contract. The clerk checks the contract, finds the surcharge clause was added in a variation the agent could not see, and approves with a note asking for the variation to be added to the agent’s sources.

That one note means the next surcharge matches automatically.

What stays with the clerk?

Paying new suppliers, any change of bank details, invoices without a purchase order above a set value, duplicates the agent is unsure about, and disputes with suppliers. Also judgement on anything unusual: a sudden change in invoice frequency, or a familiar supplier with an unfamiliar address.

The detailed review method is in how accounts payable clerks review an AI agent’s decisions. Why the clerk, not the agent, is the safeguard is argued in why accounts payable clerks are the real control.

How do market rules change the training?

Tax treatment, e-invoicing practice and data rules vary by country. Compare AI agent training for AP clerks in Singapore logistics with the same role in Germany. Other roles follow a similar pattern; see what caseworkers should learn first and the overview in AI agent skills by role.