Wire tracking on the first call: agents find the wire, trace every stop from the gpi tracker, Fedwire and the core, and write the sentence your officer may say, while a supervisor approves anything written about another bank
'Where is my wire' answered on the first call, with every stop of the route cited.
See one case, screen by screen ↓Wire Inquiry & Payment Tracking is wire tracking for bank service and payment operations teams: it answers "where is my wire" on the call from gpi, Fedwire and core data. Agents find the wire from whatever the caller has, draw its route stop by stop with every source cited, and write one sentence the officer may say, holding back what may not be told. A supervisor approves anything written about another bank, and every answer is logged with its evidence.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
Wire tracking at a community bank is still a manual trace. When a business customer calls to ask where a wire is, the treasury services officer finds the customer in the core banking system, finds the wire in the payments hub by date and amount, and emails the wire room. A deposit operations specialist reads the Fedwire OMAD to confirm the correspondent accepted it, logs in to the correspondent's portal to read its gpi tracker for the UETR, and looks for any request for information the correspondent forwarded. The customer gets a callback, often the next morning.
The answer is also a judgment made alone on the phone. Another bank's compliance reason for holding a wire may not be repeated, and an arrival date should not be promised without a basis, yet nothing on the screen says what may be told. A wire stuck for days is noticed when the customer calls a second time, the investigation with the correspondent starts when someone remembers, and the notes live in email and a free-text field, so nobody can show an examiner what was told to whom.
Estimated split of the minutes spent on one wire status question, by hand and with the agents, from the call to the logged answer. Our estimate, kept modest: about a 20-minute trace by hand, and the target of about 2 minutes with the agents. The officer still decides what is said and sent.
Six agents find the wire, trace its route, say what may be said and watch it to the end; the officer decides, and a supervisor approves anything written about another bank.
Thursday, October 22, 2026, 4:14 p.m. ET, at Tessaly Community Bank. Renée Hollis, owner of Hollis Carpentry LLC, calls about the $23,500 wire she sent the day before to her flooring supplier in Lisbon. Here is the wire inquiry, screen by screen, in the working solution.
Renée is on the line, verified at 4:13 p.m. Lena types what she has: "Where is the $23,500 wire for Hollis Carpentry?" On the same screen, today's numbers: 603 wires, 38 in flight, 5 held at another bank, 2 stuck over 24 hours, and 84 of 97 wire questions answered on first contact.
Where is the $23,500 wire for Hollis Carpentry?
The Search agent finds one wire: USD 23,500.00 on October 21 to Lisbon. Had Lena typed only "Hollis Carpentry wire", it would have asked back, the $23,500.00 to Lisbon on Oct 21 or the $2,350.00 to Porto on Oct 8. The Tracking agent reads the payments hub (released 3:04 p.m. Wednesday), the Fedwire gateway (Vellmar Bank, N.A. accepted at 3:06 p.m.), the gpi tracker and the correspondent's request for information. Each step is shown as it runs.
7 steps · 5 sources · confidence 0.93
The wire's route is drawn as a line: Tessaly Community Bank, sent Wednesday at 3:04 p.m.; Vellmar Bank, N.A., the correspondent, Fedwire accepted at 3:06 p.m. and sent on SWIFT gpi at 4:31 p.m.; Hallgrund Bank AG in Frankfurt, received Thursday at 10:12 a.m. and held 6 hours for a review; Banco Mirante, S.A. in Lisbon, expected Friday. A bar runs to the 24-hour mark, Friday at 10:12 a.m.
Lena clicks the gpi tracker chip under the answer. The record opens: UETR 3b7e1c04…d6b2, Hallgrund Bank AG, Thursday 10:12 a.m. ET, EUR 20,120.70 received, status ACSP with reason G003, pending documents or more information, no credit confirmation yet. Opening a source is recorded on the answer log.
The Answer agent writes the sentence under disclosure rules v4 and holds back two items beside it: Hallgrund's own screening reason, under rule DR-2, and the return risk, under DR-4. The arrival day says "expected", never "will", and its basis is the route's own history.
Your $23,500.00 payment to Madeiras Alvorinha is not lost. It reached our partner bank in Germany at 10:12 this morning and is waiting there on a routine review; they have asked for the invoice and the supplier's full street address.
Renée's next questions are answered on the same screen. How much will her supplier receive? EUR 20,105.70, after conversion at 0.8562 and Hallgrund's EUR 15.00 charge under shared charges, with Tessaly's $45.00 fee debited separately. Why tomorrow? Hallgrund held 15 Tessaly wires for information in 90 days and released 14 after the answer, a median 5 h 40 min later, and Banco Mirante credits a median 38 minutes after receipt.
Lena asks Renée for the invoice and the supplier's address by secure message; Renée uploads them at 4:19 p.m., and Tomas Brennan in the wire room answers Vellmar's request at 4:21 p.m. The written update is drafted from the approved wording "Intermediary review" v3. Because it speaks about another bank's review, it goes to the wire operations supervisor (DR-5).
Celia opens ST-26-0912 in her approvals queue, marked "Speaks about another bank", with the correspondent tracker, the uploaded invoice and the disclosure check beside it. She can edit, return it with a reason code, or approve and send; she approves at 4:23 p.m. Lena could not have approved her own draft.
Lena logs the call as answered on first contact, and the day's count moves from 84 to 85 of 97. The answer log keeps who asked, what was told, what was held back and why, and the evidence, ready for the FDIC examiner pack, the internal audit pack and the BSA officer pack.
If the wire is still held at its 24-hour mark, the Watch agent opens a payment investigation itself, as it did at 10:41 a.m. for Ridgeback Tile Supply Co.'s USD 61,200.00 wire to Monterrey. For INV-26-0419 the Investigation agent drafted a camt.110 status request to Vellmar, and the officer was told at 10:42 a.m. The request waits for Celia's approval.
No credit confirmation 24 hours after transfer to the beneficiary bank. Please confirm credit, or the reason for the delay and the expected date.
The same wire inquiry, seen by the people who take the call, trace the wire, approve what is written, run the branch and own the disclosure rules: what their day looked like, and what it looks like now.
Six agents find the wire, trace its route, say what may be said and watch it to the end; the officer decides, and a supervisor approves anything written about another bank.
Finds the wire from a name, an amount, a place, a date or a reference in the payments hub and the core, and asks back when two wires fit.
Reads the payments hub, the Fedwire gateway (IMAD and OMAD), the correspondent's gpi tracker and messages, and the core posting, draws the route stop by stop, and predicts the arrival from that route's own history.
Writes the sentence the officer may say and the Held back list, and drafts written updates from the approved statement wording.
Follows every wire in flight, flags holds, and at 24 hours stuck (4 hours for a domestic Fedwire) opens a payment investigation and tells the officer.
Drafts the status request to the correspondent (camt.110 or MT 199) and recall requests, and follows up.
Logs every answer with what was told, what was held back and the sources, and builds the export packs.
Approves statements about other banks and escalations. The agents propose; a named person decides.
The assistant answers about any wire your role may see, with the tracker, Fedwire and core records cited, holds back what may not be told, and opens the right screen.
Which held wires could miss their 24-hour mark tonight?
Two are already past it and both have investigations: Ridgeback Tile Supply, 29 hours at a bank outside gpi in Monterrey (INV-26-0419), and Delacroix Imports, 27 hours (INV-26-0417). Hollis Carpentry is at 6 hours; its mark is Friday 10:12 a.m., and the invoice is the fastest way to release it.
Why do we expect the Hollis wire tomorrow?
Hallgrund Bank AG released 14 of the 15 Tessaly wires it held for information in 90 days, a median 5 h 40 min after the answer, and Banco Mirante credits a median 38 minutes after receipt. The answer still says "expected", never "will": rule DR-4.
Prepare the FDIC examiner pack for October inquiries
Ready: 2,310 answers since Sep 23 with what was told, what was held back and why, the cited records, approvals with reason codes, and agent versions. Account numbers are masked, and restricted wires show the standard wording only.
12 screens from the working solution, on its sample data. Pick one to see it large.
What may be told and how fast are settings. Disclosure rules change only with the BSA officer; clocks and wording with the wire operations supervisor; every change is a new version with its approver.
| Setting | Default | Choose from |
|---|---|---|
| Disclosure rules | v4, approved by the BSA officer on Sep 14, 2026 | DR-1 our own processing may be told · DR-2 another bank's compliance reason never told · DR-3 restricted wires get standard wording · DR-4 no promise without a basis · DR-5 statements about another bank need the supervisor |
| Stuck mark, international | 24 hours | 12 hours or 48 hours |
| Stuck mark, domestic Fedwire | 4 hours with no credit advice after the OMAD | 2 hours or 8 hours |
| Answer confidence | 0.85 | 0.90 or 0.80; below it, the Answer agent hands the wire to a person |
| Inquiry clocks | 15 minutes on a call · 2 business hours in writing | 10 minutes · 4 business hours |
| Escalation | An open inquiry older than 1 hour goes to the supervisor | 2 hours |
| Statement wording | Intermediary review v3 · Credited v5 · Returned v2 · Document request v2 · Incoming not found v2 · Restricted standard v1 | Each version approved and dated, with its history |
| Data and privacy | Five years' retention, locked · account numbers masked to the last four | Call recordings kept 2 or 3 years · inquiry data never used to train models |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
Sources: Federal Reserve Financial Services, Fedwire Funds Service ISO 20022 implementation, July 14, 2025 · SWIFT, gpi and the Tracker (end-to-end tracking by UETR) · Regulation J, 12 CFR part 210, Subpart B · UCC Article 4A (uniformlaws.org) · 12 CFR 1005.33 (Remittance Transfer Rule, error resolution) · 31 CFR 1020.410 (funds transfer records kept five years) · 31 CFR 1020.320(e) (SAR confidentiality). "demo" = seen in the working solution, on its sample data · "target" = design goal, measured in the live solution · "estimated" = our estimate, kept modest. Tessaly Community Bank, Vellmar Bank, N.A., Hallgrund Bank AG, Banco Mirante, S.A., Hollis Carpentry LLC, Madeiras Alvorinha, Lda., Ridgeback Tile Supply Co., Delacroix Imports LLC, and the people, accounts and payment references named on this page are fictional: characters and sample data in the working solution.
Wire Inquiry & Payment Tracking is wire tracking for bank service and payment operations teams: it answers "where is my wire" on the call from gpi, Fedwire and core data. Agents find the wire from whatever the caller has, draw its route stop by stop with every source cited, and write one sentence the officer may say, holding back what may not be told. A supervisor approves anything written about another bank, and every answer is logged with its evidence.
The officer types what the caller gives, a name, an amount, a place or a date. The Search agent finds the wire and asks back when two fit; the Tracking agent reads the payments hub, the Fedwire IMAD and OMAD, the correspondent's gpi tracker and messages, and the core posting, and draws the route with a time, a status and a source at each stop. In the working solution's sample case, the answer was ready with 7 steps and 5 cited sources.
A UETR is the unique end-to-end reference that SWIFT gpi uses to track a payment across banks. Since the Fedwire Funds Service moved to ISO 20022 on July 14, 2025, domestic wires carry the UETR too, while the IMAD and OMAD still identify the Fedwire leg. The Tracking agent joins both, so one route covers the Fedwire leg to the correspondent and the gpi leg beyond it.
Its own status and plain facts, such as "waiting there on a routine review", but not another bank's compliance reason. The Answer agent follows the bank's versioned disclosure rules and shows the officer, side by side, what it held back and why. A restricted wire gets the standard wording only, and any written statement about another bank's actions goes to the wire operations supervisor first.
It depends on the route and on any review along it, so the solution never promises a day without a basis. The Tracking agent predicts the arrival from that route's own history: in the sample case, the intermediary released 14 of 15 held wires a median 5 h 40 min after the answer, and the beneficiary bank credits a median 38 minutes after receipt. The answer says "expected", never "will".
The Watch agent follows every wire in flight and flags each hold. At 24 hours stuck (4 hours for a domestic Fedwire) it opens a payment investigation, the Investigation agent drafts the status request to the correspondent (camt.110 or MT 199), and the officer is told before the customer calls back. Nothing reaches another bank until the supervisor approves, and a recall also needs the customer's written instruction.
Yes. The officer decides the next step on every inquiry, and the wire operations supervisor approves statements about another bank, escalations, recalls, resends, remittance notices and every batch of customer status updates; makers never approve their own work. Below 0.85 confidence, or when the gpi tracker is not answering, the Answer agent hands the wire to a person, and every override carries a reason code.
The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your disclosure rules, approved statement wording, roles and a sample of past wire inquiries, and it goes live once every quality gate has passed. We will walk you through it on your own wire inquiries first.
Transfer errors resolved in days, with every promise checked against delivery.
1-min demoNacha & Payment Rules SearchCited answers in seconds, and the actual deadline on a calendar, before a return is late.
1-min demoPayment InvestigationsWire inquiries answered in hours, not days, with every liability reply checked.
1-min demoWe'll run Wire Inquiry & Payment Tracking on a sample of your own past wire inquiries.