◆ Supervised Router
Catches the wires and ACH batches that fall out (bad references, missing remittance data, format breaks, repair queues), infers the intended instruction, and repairs or returns them. Routes by ambiguity: clean repairs post straight through, ambiguous cases escalate to a senior payments agent, and high-value repairs gate on an oversight agent before release.
Memory
Working The exception payment + the context pulled to resolve it.
Episodic Prior exceptions for the same client/counterparty pair.
Semantic Payment formats (ISO 20022, SWIFT, ACH), repair rules, return reasons.
Procedural Repair playbooks refined from oversight-agent overrides.
Store Vector store + exception-resolution log
Orchestration
router-fanout MCPA2A
Harness · Managed Agents … session event-log per exception; context editing clears stale lookups on long investigation chains.
Tools
{ } Payment / repair platform API { } Client + counterparty records API ›_ Format + remittance parsing Code exec ⇄ Senior payments-agent escalation A2A
Evals & guardrails
- Cannot auto-release a repaired payment above a value threshold … an oversight agent re-derives and approves first.
- Daily replay against a gold set of resolved exceptions; precision/recall tracked.
- Full OpenTelemetry trace of every repair retained for audit.
Offline reflection
Consolidates repeated repairs for the same client into a standing rule (a remembered remittance mapping) so the same break stops recurring.
Frontier edge
- ▲On-device / edge inference: a local low-latency model sits on the real-time payment path, triaging and repairing without a round-trip, so straight-through cases never leave the rail.
- ▲Continual learning (eval-gated): each oversight-agent override becomes a self-edit to the repair rules, daily-replay-gated before it ships … the queue shrinks over time.
- ▲Self-improving fleet: a remittance mapping learned for one client's break pattern is shared across the exception-agent population between runs.
A sample run
Trigger An inbound wire lands with an unparseable beneficiary reference and no invoice number.
- 1Parse the remittance free-text; extract a probable invoice reference.
- 2Match the amount and remitter to an open receivable for the client.
- 3Confirm a prior exception for this remitter resolved the same way.
Output Repairs the payment with the matched reference and posts it; an unmatched high-value wire would instead hold and escalate to a senior payments agent with the candidates pre-ranked.
In numbers
9,800
Exceptions resolved / day
81%
Straight-through repair rate
22s
Avg. time per exception
Handoffs
Across ⇢ Operations → Payments for hold/release execution