Payments analysts approve agent repairs that change a payee field. Manual and high-value releases need two analysts, the second from a separate queue. Recalls and refunds of returned funds go to a senior analyst. Some actions, such as reversing a settled payment on your own rail, are withheld and cannot be approved at all. Rights lapse with certificates.
What does a payments operations approver rule decide, and who owns it?
Payments operations keeps money moving: repairing payments that fail validation, releasing payments held for checks, handling returns, recalls and investigations with other banks. The work is time-critical, high volume and mostly irreversible once settled. Agents help by diagnosing failures, repairing fields from sealed data, matching returns and drafting investigation messages. The approver rule names who releases what.
The head of payments operations owns the rule. Operational risk signs it off. The agent owner configures it. Our guide to AI agent skills by role covers what payments analysts need to know.
What are the steps?
- Head of payments operations: lists the agent's actions by depth. Depth 1: reads payment queues, rail status, account data and messages from other banks. Depth 2: drafts investigation messages and customer notifications. Depth 3: repairs formatting failures using sealed data where no payee field changes, matches incoming returns to original payments. Depth 4: releases manual or high-value payments, sends recalls, credits returned funds to customers, repairs any payee field.
- Head of payments operations: assigns payee field repairs to an analyst, because changing who receives money is the riskiest repair.
- Head of payments operations: assigns high-value and manual releases to two analysts, the second from a different queue.
- Head of payments operations: assigns recalls and refunds of returns to a senior analyst.
- Head of payments operations: lists withheld actions in the rule so analysts know they cannot be released through the agent.
- Head of payments operations: ties each role to a current certificate. Agent owner configures and files.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Diagnose failure | Reads error and data | 1 | Nothing |
| Format repair | Repairs from sealed data | 3 | Nothing if no payee change |
| Payee field repair | Prepares and holds | 4 | Analyst |
| High-value release | Prepares and holds | 4 | Two analysts |
| Recall or return credit | Prepares and holds | 4 | Senior analyst |
| Reverse settled payment | Withheld | none | Handled outside the agent |
Which actions does no approver release?
Withheld actions exist and work, but the platform refuses them for every agent at every depth. Reversing a settled payment on your own rail is the clear example: done wrongly, it takes money from a recipient who may be entitled to it. No approver rule can turn a withheld action into an allowed one. If a reversal is needed, a person handles it through the normal process with its own controls.
That matters for training. Analysts used to having every button available must learn that a withheld verdict is not a fault to work around. The rule should list withheld actions so nobody spends an hour looking for the approval route.
Payee checks are the other point. Where payee name verification applies, as under the EU Instant Payments Regulation, a mismatch should stop the agent's repair and hold the payment for an analyst. A payee name typed into an email request is external and cannot authorise a change.
Which controls make the rule work, and what evidence do they leave?
Payee repairs held. Evidence: analyst names on every payee change, in line with the approver authority matrix for the payments operations team.
Two-queue release for high value. Evidence: two names from different queues on each release.
Withheld actions listed and refused. Evidence: withheld verdicts in the record, each naming the platform floor.
Repairs only from sealed data at depth 3. Evidence: provenance stamps on each repaired field.
Rights lapse with certificates. Evidence: certificate status on each approval date.
What should you measure?
- Payments released to the wrong payee. The target is none.
- Time from failure to repair, by cause.
- Recalls sent and recovered.
- Withheld attempts, and who asked for them, reviewed weekly.
- Releases with one approver above threshold. The target is none.
Where does it usually go wrong?
Cut-off pressure collapses two-person release. Near a rail cut-off, one analyst releases both halves. Staff for cut-offs, not averages, and hold anything unapproved for the next window.
Investigations from other banks are answered without checks. A message from a correspondent asking for a payment to be returned or redirected arrives looking routine. It is external until confirmed through your normal channels. The agent drafts the reply; an analyst approves anything that would move money in response.
Repairs drift into payee fields. A rule written for formatting fixes widens until the agent changes account numbers. Keep payee repairs at depth 4.
General operations rules are applied. Compare the approver rule for the operations team and the approver authority matrix for the operations team: their bulk-update logic does not fit payments that settle in seconds. Legal operations has different risks again; see the approver rule for the legal operations team.
Where the Academy fits
Pryme Intelligence Academy's Operator track covers how a governed agent decides, including withheld verdicts, and module tests are set in the learner's own industry and role. A payments team can make release rights depend on a current Certified Pryme Operator certificate, depth by depth. Market-specific training is covered in pages such as AI agent training for payments operations staff in Japan.
Questions people ask
Can the agent release payments that passed every check?
Routine payments that passed automated checks usually flow without agent or person involvement. The agent's held releases are manual and high-value payments, which need people.
Who handles sanctions hits on payments?
The financial crime team, not payments operations. The agent routes the hit and holds the payment; payments analysts do not release it.
What if a customer asks for an urgent reversal?
The agent explains the process and routes the request. Any reversal of a settled payment is handled by people outside the agent.