The wire transfer travel rule, checked for meaning on every wire, with every gap chased to a signed fix
Every wire’s travel rule data checked for meaning, and every gap chased to a fix.
See one case, screen by screen ↓It is wire transfer travel rule software for a bank's wire compliance team. Agents read every inbound and outbound wire of $3,000 or more, judge whether each field the travel rule requires holds a real value, draft the request to the sending bank, and keep each wire's record for five years. The Wire Compliance Analyst decides, the Wire Room Supervisor checks every hold, return and fix, and the BSA Officer approves every early correspondent review.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
The wire transfer travel rule says what must travel with every funds transfer of $3,000 or more: the originator's name, address and account, the amount, the execution date and the recipient's bank, with whatever recipient details were received (31 CFR 1010.410(f)). The recordkeeping rule says what the bank must keep, and that it must be found by name and account for five years. A payments hub checks that each field is filled. It cannot tell that “ONE OF OUR CLIENTS” names nobody, or that “PANAMA” is not an address, and the FFIEC BSA/AML Examination Manual tells examiners to check how the bank deals with fields that are missing, manifestly meaningless or incomplete.
So wire compliance teams find gaps by eye, chase the sending bank with free-text messages, track the answers in a spreadsheet, and lose the thread when a reply arrives on a different message type. Nobody keeps the count of which correspondents repeat, although the Federal Reserve's SR 09-09 expects a bank to consider restricting or ending a relationship where they do. Outbound gaps are the bank's own: an online-banking template that drops the originator address puts the gap on every wire it sends. And the bar is rising. SWIFT stops accepting fully unstructured postal addresses from November 2026, and FATF's revised Recommendation 16, now named Payment transparency, asks for standardized name, address and date of birth on cross-border payments above USD/EUR 1,000 by the end of 2030.
Estimated split of an analyst's working minutes on one gap, by hand and with the solution, where the analyst checks the agents' cited work and signs instead of researching. It leaves out the supervisor's check and the wait for the sending bank's reply.
Six agents judge every wire’s required fields, draft the request, keep each correspondent’s record and the five-year file; two people decide.
Thursday, October 22, 2026, at Corvane National Bank, a fictional US regional bank. At 10:14:32 ET, wire FTR-261022-0418 arrives on the SWIFT gateway as a pacs.008: USD 9,800.00 from Meridale Commercial Bank in Panama City for Larkspur Marine Supply LLC. Here is what happens next, screen by screen, in the working solution.
The Field agent lays the wire out as the nine fields 31 CFR 1010.410(f) requires, each with its rule paragraph, the value as received and a verdict. Seven are present. The originator name “ONE OF OUR CLIENTS” is meaningless, and the originator address “PANAMA” is incomplete: a country, with no street and no town.
“7 of 9 required fields meaningful”
Celia clicks the citation on the originator-name verdict. Library entry MV-03, “a generic reference to the sender's customer”, version 3, approved by Yvonne Calderwood on September 2, 2026, lists “ONE OF OUR CLIENTS”, “OUR CUSTOMER” and “ONE OF OUR CUSTOMERS”, and does not match a registered name that contains these words. It has 38 hits in the last 12 months, and a person has overturned it 0 times.
Each agent shows its plan, what it found, the sources it read, its confidence and who it handed to, with a Reject this finding button. The Disposition agent, at 88%, recommends a hold: Larkspur has received four wires from Meridale in 24 days, USD 38,750 in all, each under USD 10,000. The Request agent drafts the request on approved template RFI-ORIG v3 and schedules a chase for day 3.
Request agent: “Please send the originator's full name and full address (street, town, country) by Monday, October 26, 2026.”
The Trend agent counts 14 gaps in 212 wires this quarter, 6.6% against a peer median of 0.4%, up from 0.7% in Q2 and 1.4% in Q3. Of 13 earlier requests, 9 were answered in a median of 4 business days, 3 are unanswered and 1 wire was returned. That is over the repeat-offender rule, so it drafts a cited input to the due diligence review and proposes moving Meridale's review from March 2027 to November 16, 2026.
Celia clicks Send and hold and signs with reason code FTR-HLD-02, hold and request. The request goes to Meridale on the approved template, and the hold waits for a checker. She ticks both options: refer the pattern to transaction monitoring, for the BSA Officer's team to decide, and propose Meridale for an early review. Nothing about the referral leaves the bank.
“Template RFI-ORIG v3, as approved — goes now”
The decision screen shows the three options with their codes: hold the credit and request (recommended, 88%), credit now and request, or return to the sending bank. The maker panel shows Celia's signature at 10:21 with FTR-HLD-02, and the checker panel waits for Malcolm Terrell. The decision history lists her signature, the Request agent's draft and the Disposition agent's recommendation, each with its evidence.
“You signed this decision, so you cannot approve it. It waits for Malcolm Terrell.”
Malcolm opens the same wire and sees the proposal, its reason code, who proposed it, and that the request went to Meridale at 10:21. He approves the hold, and the funds stay in suspense until October 26. He could instead send it back with a reason.
“Hold the credit and request · FTR-HLD-02 — proposed by Celia Navarro. You are the checker.”
Yvonne approves the early review. Meridale's due diligence review moves from March 2027 to November 16, 2026, the record goes to the correspondent due diligence system, and Anders Holloway, the relationship manager, is asked to raise data quality with Meridale. He gets the data record, never the referral.
Outbound wire FTR-261022-0411, USD 48,250 to Stuttgart for Fennimore Tool & Die Inc., is missing the originator address. The Record agent finds it in the core record, verified March 2025, and proposes adding it before release, for the supervisor to approve. It also finds why: the online-banking template drops the address for payees saved before June 2026, which affects 37 business customers and 4 of today's 7 outbound gaps.
“Corvane is the sending bank, so this gap is Corvane's.”
The audit trail holds every agent finding, signature and approval with its evidence: Celia's request and proposed hold at 10:21, Malcolm's approval at 10:26 and Yvonne's at 10:31. Bettina filters by person or action and exports the OCC examiner pack, the internal audit pack or the BSA Officer pack. The wire's record, with its verdicts, request, both signatures and the hold, is kept until October 22, 2031.
The same Meridale wire, seen by the five people around it: what their day looked like, and what it looks like now.
Six agents judge every wire’s required fields, draft the request, keep each correspondent’s record and the five-year file; two people decide.
Reads every inbound and outbound wire of $3,000 or more (SWIFT pacs.008 and pacs.009 COV, and Fedwire) and marks each required field present, missing, meaningless or incomplete, citing the rule and the library entry it relied on.
Recommends credit and request, hold and request, or return, from the gap, the correspondent's record, the recipient's recent wires and the bank's rules, and flags patterns for transaction monitoring.
Drafts the request on the approved template in the correspondent's channel, a SWIFT investigation message or a Fedwire service message, sets the answer clock, chases on day 3, matches the reply to the wire by UETR and has the Field agent re-read it.
For the bank's own outbound gaps, finds the missing value in the core banking system or the channel profile, proposes the fix to the wire before cut-off, and names the channel that dropped it.
Keeps each correspondent's gap record against the peer median and drafts the cited input to its due diligence review and the early-review proposal for the BSA Officer.
Indexes five years of records by originator, recipient, account and UETR, answers record searches in plain words, builds examiner and law enforcement packs, and runs a retrievability self-test on old records.
Signs; the supervisor checks, the BSA Officer approves. The agents propose; a named person decides.
The analyst can ask the assistant about any item her role may see. It answers with the rule, the library entry and the wires cited, and acts: it opens the wire, filters the list or proposes a change for approval.
Why is “ONE OF OUR CLIENTS” meaningless?
It is present, but it names nobody. The travel rule asks for the name of the transmittor, and examiners test for originator fields that are missing or manifestly meaningless. The phrase is library entry MV-03, seen 31 times this year from 3 correspondents and never overturned by a person. Meridale used it on October 8 as well; that wire was returned when no reply came.
Which correspondents should be reviewed early?
One is over the rule, three are close. Meridale Commercial Bank has 14 gaps in 212 wires this quarter, 6.6% against a peer median of 0.4%, with 3 requests unanswered; its early review is drafted for November 16. Valdane Savings Bank is at 4.5%, Kestrin Bank Ltd at 2.5% and Ardmore Gulf Bank at 2.2%.
Find every wire to Larkspur Marine Supply LLC
11 wires since April 2022, every one retrievable by name and account. Four came from Meridale Commercial Bank in the last 24 days, USD 38,750, each under USD 10,000, two with the originator “ONE OF OUR CLIENTS”. Each record is kept five years from its execution date.
Hold every Meridale wire until the originator is named
Proposed, not applied. A disposition rule change needs the BSA Officer. On this quarter's traffic it would have held 14 of Meridale's 212 wires, the gaps only, for up to 2 business days each. The proposal has gone to Yvonne Calderwood with that impact attached.
13 screens from the working solution, on its sample data. Pick one to see it large.
Each change is proposed, then approved by the BSA Officer, and kept as a new version with who made it and why.
| Setting | Default | Choose from |
|---|---|---|
| Wires checked | $3,000 or more | $3,000 or more (31 CFR 1010.410(f)) · $1,000 or more (bank policy) |
| Also check cross-border wires from | $1,000 | $1,000 · $0, every cross-border wire · Off (bank policy, ready for FATF Recommendation 16) |
| First gap from a correspondent within range | Credit and request | Credit and request · Hold and request |
| Hold limit | 2 business days | 1 · 2 · 3 business days; then a return is proposed to the checker |
| Reminder to the sending bank | Day 3 | Day 2 · Day 3 · Day 4; non-response counted against the correspondent at day 10 |
| Repeat-offender rule | 2% and at least 10 gaps | 1% and at least 10 gaps · 2% and at least 10 gaps · 3% and at least 5 gaps, in a quarter |
| Confidence floor for “meaningless” | 90% | 85% · 90% · 95%; below it a person decides |
| Refer a pattern to transaction monitoring | On | Several wires under USD 10,000 to one recipient with a gap, within 30 days |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the split of one gap's working minutes) · “typical” = published rules (31 CFR 1010.410(f), the travel rule, for funds transfers of $3,000 or more; 31 CFR 1010.430(d), records kept five years). Other sources: the FFIEC BSA/AML Examination Manual; Federal Reserve SR 09-09; FATF, revised Recommendation 16, Payment transparency, June 2025; SWIFT's retirement of fully unstructured postal addresses from November 2026. Banks, companies, people, account numbers and references named on this page are fictional — characters and sample data in the working solution.
It is wire transfer travel rule software for a bank's wire compliance team. Agents read every inbound and outbound wire of $3,000 or more, judge whether each field the travel rule requires holds a real value, draft the request to the sending bank, and keep each wire's record for five years. The Wire Compliance Analyst decides, the Wire Room Supervisor checks every hold, return and fix, and the BSA Officer approves every early correspondent review.
For a funds transfer of $3,000 or more, the originator's bank sends the originator's name, address and account, the amount, the execution date and the recipient's bank, with the recipient details it received, and an intermediary bank passes on what it receives (31 CFR 1010.410(f)). The solution shows each wire as these nine fields, each with its rule paragraph and a verdict: present, missing, meaningless or incomplete.
The Field agent tests each value against a versioned library of meaningless values and against the context: the sending bank's own name, the customer record and the rest of the message. “ONE OF OUR CLIENTS” is marked meaningless, while “NA Holdings Ltd” and “Client Services Trust Ltd” are cleared as registered names, each with its reason. Below 90% confidence a person decides, and an override carries a reason code.
Every gap joins the sending bank's record, shown beside each wire: in the sample, Meridale's 14th gap this quarter, 6.6% of 212 wires against a peer median of 0.4%. Over the repeat-offender rule, the Trend agent drafts a cited input to the correspondent due diligence review and proposes an early review. The BSA Officer decides; the agent never restricts or ends a relationship.
Yes. When the bank is the sending bank, the gap is its own, so an outbound wire is not released with a required field missing. The Record agent finds the missing value in the core banking system, proposes the fix before the SWIFT or Fedwire cut-off for the supervisor to approve, and names the channel that dropped it, such as an online-banking template.
Each wire's record, with its verdicts, request, decision and both signatures, is kept five years from the execution date (31 CFR 1010.430(d)) and indexed by originator, recipient, account and UETR. The Retrieval agent answers a plain-words search, such as every wire to one customer since 2022, and builds the examiner or law enforcement pack. A self-test samples old records and retrieves them by name and by account.
People decide. Agents never hold, credit, return or release a wire, or change a customer record: an analyst signs and a supervisor approves, and nobody approves their own step. A referral to transaction monitoring never appears in a request, on the relationship manager's view or on any customer-facing view.
The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your disposition rules, request templates, approval limits and a sample of past wires, and it goes live once every quality gate has passed. We will walk you through it on your own wires first.
'Where is my wire' answered on the first call, with every stop of the route cited.
1-min demoRemittance Transfer Rule ComplianceTransfer 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 demoWe'll run it on a sample of your own past inbound and outbound wires.