Payments operations analysts use this log to record every payment exception they decide during a two-week practicum: the payment, the rail, the exception, what the AI agent proposed or refused, the analyst's decision and reason, a supervisor's independent call, and any red line. Withheld reversals get their own handling. The template and four sample exceptions follow.
Which exceptions reach a payments analyst?
In a typical payments operation, the AI agent repairs routine formatting faults at depth 3 within rules, such as a missing reference or a mistyped field it can correct from a sealed source. It holds the rest for a named person:
- Payee name mismatches. Under the EU Instant Payments Regulation, payment service providers must verify the payee's name, and a partial or failed match needs a decision.
- Possible duplicates. Same amount, same payee, close together.
- Returns and recalls. A payment came back, or the sender asks for it back.
- Screening holds. These go to the sanctions team; payments operations must not release them.
- Reversal requests. Reversing a payment that has already settled on the firm's own rail is withheld at the platform floor for every agent at every depth.
The last two test something specific: knowing which decisions are not yours. A withheld verdict means the action exists and works, but is refused on purpose. The analyst's job is to find the right alternative route, not a workaround. Setup is covered in how to run a two-week practicum for payments operations staff.
How do analysts fill it in?
The AI agent pre-fills payment details, the rail, the exception and its verdict. The analyst checks the source behind each fact: the core ledger and the rail's own messages are sealed; the receiving bank's name-check response is signed; a customer's instruction by phone is declared; an email from someone claiming to be the beneficiary is external. Then the analyst records a decision and reason. The supervisor records theirs without seeing the analyst's.
The practicum log template
Header: analyst; supervisor with a current certificate; rails in scope (instant, batch, international); dates; bar of at least 95 correct in every 100 and no missed red line.
Red lines
- Releasing a payment with a failed or partial name match without resolving it with the payer.
- Releasing or altering a payment under a screening hold.
- Trying to achieve a withheld reversal by another route, such as a manual offsetting entry.
- Releasing a confirmed duplicate.
| Field | Entry |
|---|---|
| No. and time | |
| Payment ID and rail | |
| Amount | |
| Exception type | Repair, name mismatch, duplicate, return, recall, screening, reversal |
| AI agent's proposal and verdict | Allowed, held, refused, withheld; deciding bound |
| Key facts and provenance | |
| Analyst's decision | Release, repair, return, contact payer, refer, decline |
| Reason | |
| Supervisor's decision | |
| Match | Yes / no / defensible |
| Red line | None / caught / missed |
Four sample exceptions
Take a sample payment institution processing instant payments in the euro area. Values are illustrative.
No. 112. Instant payment of 2,400 to "J Smith Plumbing Ltd"; the name check returns a close match, "J. Smith Plumbing Limited". AI agent: hold. Analyst: release; the variation is formatting. Supervisor: release. Match: yes.
No. 113. Payment of 15,000 to a supplier; name check returns no match. The payer's finance team emails to say the supplier "changed its trading name". Analyst: release on the strength of the email. Supervisor: hold; call the payer on the number on file and ask them to confirm with the supplier through a known contact. Match: no. Red line 1: missed.
No. 114. A customer asks to reverse a settled payment of 600 sent in error. AI agent: withheld. Analyst: explain to the customer that the payment cannot be reversed; raise a recall request to the receiving bank. Supervisor: same. Match: yes. Red line 3: caught, because the analyst used the proper route.
No. 115. Two payments of 980 to the same payee four minutes apart, different references. AI agent: hold as possible duplicate. Analyst: contact the payer; both are valid invoices; release. Supervisor: same. Match: yes.
Entry 113 fails the bar. The email was external and arrived on the same channel the payer's request came through; it could not confirm anything.
How does this log relate to others?
Operations managers see the same exceptions as backlog and coverage questions; the practicum log for operations managers records those decisions one level up. Caseworkers have a very different queue but face the same pressure to clear it; the log for caseworkers shows how the reason column keeps decisions honest. For the wider picture of literacy and certification, see AI literacy and certification for people who work with agents.
Questions people ask
Can an analyst override a withheld verdict in an emergency?
No. Withheld is a platform decision, not a setting. The analyst's job is to use the alternative route, such as a recall, and record it.
Should screening holds appear in the log at all?
Yes, as entries where the correct decision is "refer to the sanctions team". Logging them shows the analyst knows where their authority stops.
Does the analyst need a certificate to release held payments afterwards?
That is the firm's decision, depth by depth. See do payments operations staff need a certificate to approve AI agent actions and, on responsibility, are payments operations staff accountable for an AI agent's mistakes.