A payments operations practicum puts the analyst on the live exceptions queue for ten working days. They decide every payment the agent holds, such as name-check mismatches and releases above limit, while an assessor marks each call. The bar is 95 correct in every 100 and no missed red line, starting with any release resting on an unverified instruction.
What is being tested, and who owns it?
Payments agents are good at the repetitive part of exceptions: repairing a malformed reference, matching a return to its original, chasing a missing field. What they hold is the part that needs judgement and carries loss: a payee name that does not match the account, a beneficiary changed by email, a release above the customer's limit. The analyst's skill is deciding those holds quickly and correctly while money waits.
The head of payments operations owns the practicum, with financial crime setting the fraud-related red lines. The assessor should be an experienced analyst outside the trainee's reporting line. The guide to AI literacy and certification for people who work with agents explains how practical assessment fits alongside written tests.
What are the steps?
- Person (head of payments operations): pick the exceptions queue. Live payments, not a test environment. The agent should work at depth 3 on repairs and at depth 4 only with a person's approval.
- Person (financial crime): set the red lines. Releasing a payment where the beneficiary's details came from an external source such as an emailed invoice; overriding a failed payee name check without a documented call-back; releasing above the analyst's authority; any attempt to get round a withheld action.
- Agent, depth 3: repairs routine exceptions. Format errors, missing references, returns matched to originals, all within bounds.
- Agent, depth 2: drafts the investigation note for each hold. What failed, which sources it checked, and the provenance of each fact.
- Person (analyst): decides every held payment. Release, repair, return or escalate, with a reason.
- Agent, depth 4: releases only after a named approval. Moving money is hard to undo; the verdict records who approved.
- Person (assessor): marks each decision within the day. Red-line holds are checked before release while the practicum runs.
- Person (head of payments operations with assessor): sign off or extend.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Repairs | Fixes format and reference errors | 3 | Sampling repairs for accuracy |
| Investigation note | Drafts what failed and why | 2 | Reading the sources behind it |
| Name-check mismatch | Holds the payment | 2 | Call-back and release decision |
| Changed beneficiary | Holds; external claims cannot authorise | 2 | Verifying through a known channel |
| Release | Executes after approval | 4 | The approval |
| Reverse a settled payment on own rail | Withheld at the platform floor | n/a | Recovery through the proper process |
Which controls matter, and what evidence do they leave?
External claims cannot authorise a payment. An invoice that arrives by email carrying new bank details is external evidence. The agent will not treat it as authority, and neither should the analyst. The evidence is a call-back note naming the known number used.
Payee name verification is respected. In the EU, payment service providers must verify the payee's name for instant payments. A mismatch override needs a documented reason. The verdict holds both the mismatch result and the analyst's reason.
Withheld means withheld. Reversing a settled payment on the institution's own rail is withheld for every agent at every depth. An analyst who asks a colleague to do it by hand outside the workspace has failed the practicum. The record will show the attempt to request it.
Authority limits live in the workspace. The analyst's release limit is one of the customer's own limits, so the verdict names it when it decides.
What should be measured?
- Accuracy against the 95 in 100 bar.
- Red-line misses: zero.
- Time to decide by hold reason, especially for payments close to a cut-off. Correct but late can still mean a missed settlement window.
- Call-back discipline: every changed-beneficiary release carries a call-back note.
- Return quality: returned payments carry a reason the sender can act on.
Keep the marks in the practicum log template for payments operations staff.
Where does a payments practicum usually go wrong?
Pressure from cut-off times. Analysts learn to clear the queue before the window closes. Under that pressure the name-check override becomes routine. Assessors should look closely at decisions made in the last half hour before each cut-off.
No fraud attempts in two weeks. A good fortnight may bring no changed-beneficiary requests. Replay past ones in a training workspace and label them, so the analyst is tested on the case that matters most.
The analyst carries the blame alone. If an agent's repair introduced the error and the analyst missed it, the review should ask what the analyst could have seen. Read whether payments operations staff are accountable for an AI agent's mistakes before setting the tone with trainees.
The operations managers' practicum covers the person who staffs this queue, which is a different test from deciding what is in it.
Where the Academy fits
The Academy's Operator certificate includes a practicum of two weeks of real review decisions, at least 95 in every 100 correct and no missed red line, signed off by a Pryme assessor. Tests are set in the learner's industry and role, so payments analysts are tested on held payments. A payments business can choose to make release approval depend on a current certificate.
Questions people ask
Should practicum analysts release payments above a set amount?
Not alone. Most teams set a lower release limit for the practicum and route anything above it to a senior. The analyst still decides, and the senior confirms.
What counts as a missed red line if the payment was genuine?
The decision still counts. Releasing a changed-beneficiary payment without a call-back is a red-line miss even if the new details turn out to be correct. The practicum marks the decision, not the luck.
How long should the practicum be for part-time staff?
Long enough to see the same range of holds a full-time analyst sees in ten days. Count decisions and hold types, not calendar days.