Payments teams work to cut-off times, so every recertification must be ready before the first cut-off it affects. Every 90 days the payments agent is recertified on your own payment flows, and its rights to repair, release and return payments can change. Staff need the new limits and rules, practice on held payments, and a fallback plan that protects the day's cut-offs.
What changes for payments operations staff?
A payments agent usually investigates exceptions at depth 1, reading the payment, the account and the scheme rules. It repairs payment messages with missing or malformed fields at depth 2, or at depth 3 for a narrow set of well-defined repairs. It releases routine payments at depth 4, because moving money is hard to undo, but only within the business's own limits and only where certification supports it. Returns, recalls and payments with sanctions hits are held for a named person.
Recertification re-runs the agent's cases on recent flows. The release capability is the one staff feel most. If the replay found the agent releasing payments with doubtful repairs, the agent's depth drops and every payment it would have sent arrives held. On a busy day that is hundreds of extra decisions before cut-off.
Some things never move. Reversing a payment that has settled on the platform's own rail is withheld at the platform floor, for every agent at every depth. A payment instruction or bank-detail change that arrives by email is external provenance and cannot authorise a payment. In the EU, the Instant Payments Regulation requires providers to verify the payee's name, and a mismatch is something staff must handle, not the agent. More on the mechanism is in what recertification is.
Who owns readiness?
The payments operations manager owns staff readiness and cut-off cover. The builder owns recertification. The head of payments owns the business's own limits, such as release values and corridors. The IT administrator owns the connections to the payment systems.
Steps for each cycle
- Person (payments operations manager): set the date away from month-end, payroll days and scheme change weekends.
- Agent, depth 1: report the cycle. Exceptions investigated, repairs made, payments released and held, returns and recalls, refusals, with the deciding bound for each.
- Person (senior analyst): sample released payments whose messages the agent repaired.
- Person (builder): recertify on recent flows, including the sampled repairs.
- Person (manager and builder): write the change note: release limits by corridor, repair types allowed, new held reasons.
- Person (manager): build the cut-off fallback: who clears held payments if the agent's depth drops, by cut-off.
- Agent, depth 2: draft practice payments, checked by the senior analyst.
- Person (manager): brief staff by shift, and review held payments in the first fortnight.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Exception investigation | Reads payment, account and rules | 1 | Judging the cause |
| Message repair | Repairs defined fields | 2 or 3 | Non-standard repairs |
| Routine release | Releases within limits | 4 | Setting limits |
| Release above limit | Drafts only | refused | Making the payment |
| Return or recall | Prepares and holds | held | Approving |
| Settled-payment reversal | Withheld at the platform floor | withheld | Recovery by other routes |
What should staff practise?
Held payments under time pressure. Read the deciding bound first. "Held: repair not certified" means checking the repair. "Refused: above limit" means a person makes the payment. "Held: source external" means the instruction did not come from a trusted channel.
Payee name mismatches. Practise the decision and the record of why.
Fallback day. Walk through the first hour after the agent drops to depth 1: who takes which cut-off, which payments go first.
Withheld actions. Staff should explain to colleagues why a settled payment on the platform's own rail cannot be reversed by the agent, and what the recovery route is instead.
Controls and the evidence they leave
- Repair sample each cycle. Evidence: the sample and findings.
- Change note with corridor limits. Evidence: dated note agreed with the head of payments.
- Cut-off fallback. Evidence: the plan and the rota it produced.
- Named approval on held payments. Evidence: approvals in the append-only record.
- Practicum for new approvers. Evidence: the practicum log template for payments operations staff.
What to measure
Payments that missed cut-off, and why. Held payments by reason and waiting time. Repaired payments later returned by the receiving bank. And payments released on external instructions, which should be zero. Missed cut-offs in the week after a cycle are the clearest sign that the fallback or the briefing failed.
Where does readiness slip?
The cycle lands on a payroll day. A failed run turns the busiest day into a manual one.
Staff approve held payments in bulk to meet cut-off. Bulk approval hides the one payment that should have stopped. The fallback plan should provide enough people that this is never necessary.
Limits by corridor change without notice. Staff then see held payments in a currency that used to flow and assume a fault. Who answers when a payment goes wrong is set out in are payments operations staff accountable for an AI agent's mistakes. IT administrators run the connection side of the same cycle; see keeping IT administrators ready for recertification.
Where the Academy fits
Pryme Intelligence Academy's Operator track is built for people who clear held actions every day. The Certified Pryme Operator practicum is two weeks of real review decisions, at least 95 in every 100 correct with no missed red line, signed off by a Pryme assessor, which suits a desk that approves money movement. A business can make approval rights for depth 4 actions depend on a current certificate. More in the guide to AI literacy and certification for people who work with agents.
Questions people ask
Can the agent release payments outside business hours?
Only within its certified depth and the business's own limits. Many teams set a low value limit overnight, so releases above it are refused and made by staff on shift.
What happens to payments in flight if the agent drops to depth 1?
Released payments stay released. Payments not yet released are refused, and staff make them.
Should staff see the agent's repair before approving?
Yes. The held item shows the original message, the repair and the rule applied.