Payment Investigations Agent
Handles payment investigations, recalls and SWIFT gpi tracing through resolution.
Handles non-receipt cases: traces the payment across correspondents via gpi, responds to and raises MT199/camt.056 recalls, and answers inbound correspondent queries. Recalls and returns above the value threshold are held for an oversight agent to re-derive as a check and the accountable payments officer to approve. An event-log outside context tracks multi-day correspondent exchanges across the case lifecycle.
Authority
Recommend for approval
Team role
Provides specialist analysis
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Payments Operations
Desk workflow
Payment intake, then validation/screening, then STP or repair, then execution, then investigations/recalls. STP handles the clean ones; the repair queue (bad BIC, missing reference, formatting) is where the exception work sits: above-threshold repairs and recalls route through an oversight-agent re-derivation check to the accountable payments officer.
Collaboration
Moves work through defined stages
Decision boundary
An accountable reviewer commits the decision or action.
Systems and capabilities involved
SWIFT gpi tracker
Payment engine
Correspondent messaging (MT/camt)
Counterpart bank agent
where A2A-enabled
Oversight payments agent
re-derives large-value recalls as a check
Accountable payments officer
approves large-value recalls
Handoffs
What this role gives and receives
Capabilities offered
The handoffs name the next owner or specialist and the work that moves between them.
Receives from
External handoff
Customer-facing divisions (CCB / Commercial) for status updates
Context
What the role needs to do the work
- Current work
- The investigation case, the payment trail, outstanding queries.
- Prior interactions
- Prior investigations on this corridor / correspondent.
- Policies and reference
- SWIFT gpi tracing, recall/return rules, correspondent SLAs.
- Working method
- Investigation playbooks per case type (non-receipt, duplicate, recall).
Illustrative workflow
How the work moves
Starting point
Customer claim: a $0.5M wire sent 4 days ago hasn't arrived.
- 01
Trace via gpi: payment credited the intermediary, stalled at correspondent #2.
- 02
Identify a compliance hold at the correspondent; raise an inquiry (MT199).
- 03
Track the correspondent's response against its SLA.
Result
Pinpoints the stall to a correspondent compliance hold, opens an inquiry, and returns the customer a precise status with the location and reason for the stall.
Checks and boundaries
What must be tested or reviewed
- 01Recall/return actions above a value threshold are re-derived by the oversight agent as a check and approved by the accountable payments officer.
- 02Case-resolution time and customer-response SLA tracked per corridor.
- 03Immutable audit trail of every correspondent message sent/received.
Human authority
An accountable reviewer commits the decision or action.
Keep exploring