Payments operations staff review an agent's decisions by reading the record, identifying which of the five bounds decided, checking the provenance of every fact that moved money, and then approving, editing or declining with a reason. Much of the effort goes to repairs, matches and returns the agent completed alone, where silent errors accumulate.
What decisions does an agent make in payments operations?
Day to day, the agent works mostly at depth 3, inside the firm's own limits:
- Repairing failed payments, such as fixing a formatting error in a reference or an address field.
- Matching incoming credits to invoices or customer accounts.
- Processing returns when a receiving bank rejects a payment.
- Investigating queries from customers or counterparties and drafting replies.
- Preparing payment batches for release by a person or, where certified, releasing low-value items itself at depth 4.
Each decision is filed in an append-only record with the verdict, the sources, the brief version and the bound that decided.
What are the review steps?
- Read the record. Start from the filed decision, not the dashboard tile.
- Find the deciding bound. Role scope, certificate, sources, the firm's own limits, platform guardrails. For an allowed repair, ask which bound it came closest to.
- Trace provenance. A remittance advice from the payer's bank is signed. A customer's note saying "this is for invoice 4471" is declared. A matching decision built on declared references alone is weaker than one confirmed against the sealed ledger.
- Check the money. Did the right amount go to the right account at the right time, or land in the right place on the ledger?
- Decide and record the reason.
What should a reviewer look for in each decision type?
| Decision type | What can go wrong | What to check |
|---|---|---|
| Repair | The fix changed something material, not only format | Compare original and repaired fields |
| Match | Credit applied to the wrong customer or invoice | Reference, amount, payer name against ledger |
| Return | Funds returned to the wrong originator | The original payment record |
| Batch preparation | Duplicate or stale payment included | Duplicate window, approval dates |
| Query reply | Promise the firm cannot keep | Wording against the firm's policy |
A worked example
Take a payment institution whose agent matches incoming credits to merchant accounts at depth 3. During a weekly sample, an analyst finds a credit of 2,400 matched to a merchant whose account name is similar to, but not the same as, the payer name on the credit. The reference field was blank; the agent matched on amount and a partial name.
The decision was within the firm's limits, which allowed matching on amount plus name similarity. The analyst edits the match to "unapplied, pending investigation", records the reason, and contacts the correct merchant, identified from the original invoice. She then raises the pattern. The process owner tightens the firm's limits so that credits without a reference and without an exact name match are held instead of matched. The record shows the before and after, which is what an auditor will want to see.
What makes payments review hard?
Volume. A busy desk processes thousands of decisions a day. Sample by risk, not at random: weight towards near-misses on the amount limit, partial name matches and decisions resting on declared or external facts.
Speed. Cut-off pressure pushes reviewers towards quick approvals. Response targets should be staffed so reviewers are not forced to choose between speed and checking.
Certificate status. Certificates lapse after 90 days, and a certification run that clears no depth drops the agent to depth 1 the same day. If that happens on a busy day, every repair arrives as a draft. Know the dates.
Independence. The person who set a batch up should not be the one who reviews the agent's release of it.
Building these habits across a team is covered in how to train the payments operations team to review agent decisions. Operations managers take the aggregate view of the same queue; see how operations managers review an agent's decisions. Collections teams review similar matching work; see how collections agents review decisions. For a market-specific plan, see payments operations training in Japan, and for every role, AI agent skills by role.
Questions people ask
Should reviewers check allowed decisions at depth 4 more often?
Yes. Depth 4 actions move money and are hard to undo, so their sample should be larger and reviewed sooner.
What if a sampled error has already caused a loss?
Treat it as an incident: contain it, recover what you can, record what happened and why, and change the bound that let it through.
Can a reviewer edit a decision that has already been executed?
They record a correcting decision, such as reversing a ledger match, which is itself filed. The original decision stays in the record unchanged.