How to keep accounts payable clerks ready for an AI agent’s 90-day recertification

Brief clerks on what changed before the agent's new certificate takes effect, not after the first odd invoice. Every 90 days the agent is recertified on your own invoices, and its depth, and with it what it may match, post and pay, can move. Clerks need a short change note, worked examples of the new held items and a plan for the day a run fails.

What changes for accounts payable clerks at each recertification?

The agent's certificate lapses after 90 days. Recertification replays it against real invoices from your own ledger and a short run keeps the highest depth it cleared, so the result is rarely all or nothing. Matching invoices to purchase orders needs depth 3, proposing the payment run is a draft at depth 2, and payments above the customer's limit stay with a person.

For clerks, three things can shift. The tolerance within which the agent posts matched invoices can narrow. The agent can drop a depth, so work that used to post arrives as a draft. And a new refusal can appear, for example the agent declining to act on a supplier bank-detail change that arrived by email. An emailed request is external provenance, and an external claim cannot authorise a payment.

The worst case is a run that clears no depth. The agent drops to depth 1 the same day and every invoice it used to post arrives as a draft. If that lands in the last week of the month, clerks face the full volume by hand.

Who owns the cycle?

The AP supervisor owns clerk readiness: the calendar, the briefing and cover. Whoever builds and certifies the agent owns the recertification itself. The financial controller owns the customer's own limits, such as the value above which any payment is held. These three need to meet once per cycle, ideally a week before the expiry date.

The steps for each 90-day cycle

1. Person (AP supervisor): fix the date. Put the certificate expiry in the AP calendar and move the recertification away from month-end close and the main payment runs.
2. Agent, depth 1: report the cycle. The agent lists invoices posted, drafted, held and refused in the last 90 days, with the bound that decided each verdict.
3. Person (builder): recertify. The agent is replayed against recent invoices, including duplicates, partial deliveries and credit notes.
4. Person (builder and supervisor): write the change note. One page: the agent's depth before and after, any new held threshold, any new refusal, and what each means at the clerk's desk.
5. Agent, depth 2: draft practice items. The agent drafts six anonymised held invoices that reflect the changes. The supervisor checks them before use.
6. Person (supervisor): brief the clerks. Twenty minutes, worked through the practice items. Clerks say what they would do and why.
7. Person (each clerk): confirm. A short sign-off that they have read the note, with three check questions.
8. Person (supervisor): watch the first week. Sample held items cleared under the new certificate and correct misunderstandings early.

Clerks who approve held payments should be certified to do so. Whether that is required is covered in do accounts payable clerks need a certificate to approve AI agent actions.

What should clerks retrain on each time?

Not everything. Retrain on the deltas and on the two skills that decay fastest.

The first is reading a held invoice. A held item shows the draft, the deciding bound and the facts the agent used, each with its provenance. A clerk should check whether the bank details came from the supplier master, which is sealed, or from an attachment, which is external.

The second is respecting refusals. If the agent refused to change a supplier's bank details from an email, the clerk's job is to verify through the supplier's known contact, not to push the change through by hand. The refusal is the control working.

Any new capability or depth gets its own worked example. A clerk who used to check every posting and now reviews only exceptions needs to learn what an exception report shows and what it leaves out.

Which controls make the cycle reliable, and what evidence do they leave?

• Change note per cycle. Evidence: a dated note, linked to the certificate.
• Clerk sign-off. Evidence: a named confirmation and check answers per clerk.
• First-week sample. Evidence: the supervisor's sample of cleared items, with corrections.
• Cover for a failed run. Evidence: a written fallback plan naming who takes extra drafts.
• Practicum records for new approvers. Evidence: a log, using the practicum log template for accounts payable clerks.

What should you measure?

Three figures per cycle. The number of held invoices cleared within the same day, before and after recertification. The number of corrections the supervisor made in the first-week sample. And the number of bank-detail changes made outside the verification route, which should be zero.

If corrections spike after a cycle, the change note was unclear or the briefing was skipped.

Where does readiness usually slip?

It slips when clerks learn about a depth change from the queue. An agent that dropped from depth 3 to 2 doubles their credit-note drafts overnight, and they assume something is broken.

It slips when the briefing is generic. "The agent was recertified" tells a clerk nothing. "Credit notes over the tolerance are now held for you" tells them what to do.

And it slips when accountability is vague. Clerks should know where their responsibility starts, as are accounts payable clerks accountable for an AI agent's mistakes explains. The same rhythm works in other teams; compare keeping paralegals ready for recertification.

Where the Academy fits

Pryme Intelligence Academy's Operator track includes a module on keeping knowledge current and one on running the rhythm, which cover exactly this cycle. Clerks who approve held payments can earn Certified Pryme Operator, valid 12 months, so each person's certificate spans about four of the agent's 90-day cycles. More is in the guide to AI literacy and certification for people who work with agents.