ISO 20022 structured address remediation in which agents prove every field and a maker and a checker sign every change before 14 November
Every client and payee address structured, proven and signed twice before 14 November.
See one case, screen by screen ↓ISO 20022 Structured Address Remediation turns the free-text addresses in a bank's client and beneficiary master into ISO 20022 structured address fields before the 14 November 2026 deadline. Seven agents split each address into elements, prove each one from postal reference data, the party's own payments and its documents, check the Swift CBPR+ and Fedwire rules and screen the result in test mode. A payments data analyst approves as maker and a checker signs every change, with the before and after kept.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
ISO 20022 structured address rules take effect on 14 November 2026: Swift stops carrying cross-border payments whose party addresses are fully unstructured, with no contingency, and US banks expect Fedwire and CHIPS on the same date. The problem is not the message. It is the client and beneficiary master, where tens of thousands of addresses sit as one block of free text from old wire templates, client files and branch forms.
Today the master is dumped into spreadsheets and parsed with scripts and postal libraries, and post boxes, districts and renamed towns fail silently. Analysts check doubtful rows against the wire archive one at a time, and nobody records which source proved which field. Treasury clients are emailed lists of payees and their replies are retyped. Then the cleaned file is bulk-loaded, often without a second person and without the old value kept beside the new one, and the errors surface as rejected payments in the repair queue.
Estimated split for one beneficiary address that a script cannot finish, by hand and with the solution.
Seven agents parse, prove and rule-check every address; an analyst approves and a checker signs.
Thursday 22 October 2026, 08:05 ET, 23 days before the deadline, at Corvane National Bank. Its beneficiary master holds 61,900 addresses to structure. Here is one morning, screen by screen, in the working solution.
Priya's morning starts on one line: 38,412 of 61,900 beneficiary addresses structured, then what sits with a checker, with clients, with the agents and proposed to retire. The morning brief cites every figure: 3,120 addresses read overnight, 1,900 at 95% or higher in batch B-1022-03, and 6,214 of last month's 48,960 payments that would be rejected. One notice says Brazil's postal reference data did not load at 06:00, with Retry.
“If 14 November were today”: 6,214 payments, $1.84 billion.
Kessler GmbH, a payee of the treasury client Brightwater Marine Components, sits in the master as KESSLER GMBH / POSTFACH 12 04 33 / 80331 MUENCHEN / DE. Each word is tinted the color of the field it became: post box 12 04 33, postcode 80331, town MUENCHEN and country DE, 97% overall. The street is empty, and the screen says why.
“A post-box address. No source holds a street, and a post box needs none.”
Each field carries numbered citations to the German postal reference data, the payments the bank has sent and received for Kessler, and Kessler's invoice RE-2026-0712 in document imaging. Priya opens one: an incoming pacs.008 of 2 September 2026 from Kessler's bank, with the same post box, postcode, town and country in their own elements.
“Structured by Kessler's own bank. The strongest proof there is: the party's bank already uses this address.”
The agents' run shows eight steps, from reading the master record to screening the new address in test mode, and why it came to her: policy AP-04 §3.2 asks for a person when an address is a post box with no street. Priya approves as maker. The change waits for Gloria Achebe, the checker, and the before and after are kept.
“You cannot check your own change.”
For Shree Ganesh Textiles, the master and the postal reference data say the town is Ankleshwar; a pacs.008 from the payee's bank of 19 August 2026 says Bharuch. The agents do not pick. The analyst sees both with their citations and a Use button beside each.
“The sources disagree on the town.”
The batch holds 1,900 beneficiary addresses proven at 95% or higher: 1,644 fully structured and 256 hybrid, by confidence band and country. The sampling agent picked 25 for her to read, covering every top country, the hard patterns, the largest payees and the lowest confidences, each with why it was picked and its before and after. Approve stays off until the sample is read.
One wrong item holds the whole batch and widens the next sample to 80.
Gloria marks all 25 correct and approves with the reason “Sample 25 of 25 correct”. The 1,900 changes are written under change request CR-26-1022-031, the before and after of each record is kept for five years, the addresses are re-screened in production with no new alert, and 1,900 payment templates are updated.
Forecast: 6,214 → 5,102 payments that would be rejected, 12.7% → 10.4%.
Every new address is screened in test mode first. Overnight, structuring changed 18 results: 6 new potential matches went to Nadia, such as Tavria Agro Trade LLC, now a potential match on a region-based program, and 12 false alerts disappeared, such as Front Range Hydraulics LLC on Havana Street in Denver, with 7 alerts in 12 months.
Remediation never clears or decides a match.
37 of Brightwater's payees cannot be proven from the bank's records. The outreach agent drafts one request in the treasury management portal to Laura Brandt at Brightwater, due Thursday 5 November, with what the bank has and what it proposes for each payee. Ben approves the sending; the agent reminds on day 5 and tells the relationship manager on day 8.
Client requests never mention sanctions screening.
Every morning the last 30 days of payments are replayed against the new rules. After batch B-1022-03, 5,102 of 48,960 would be rejected, 10.4% and $1.52 billion, against a target under 1%. Helen sees them by rail (Swift 3,614, Fedwire 1,082, CHIPS 406), by client, by reason and by country, and 9,870 dormant payees proposed to retire instead of clean.
The same ISO 20022 structured address program, seen by the five people who carry it: what their day looked like, and what it looks like now.
Seven agents parse, prove and rule-check every address; an analyst approves and a checker signs.
Splits each free-text address into ISO 20022 elements by the country's address format, and explains every element it leaves empty.
Proves each element against postal reference data, the payments the bank has sent to and received from that party, and the documents in imaging, and scores confidence per element.
Checks the Swift CBPR+ and Fedwire rules: town and country present, no address line in a fully structured address, at most two lines of 70 for a hybrid one, no duplication, the payment character set. Builds the pacs.008 address.
Screens each new address in test mode against the same lists as production and compares the result with today's.
Drafts one pre-filled request per client in the treasury management portal, chases on a schedule and reads replies back into proposals.
Builds batches by confidence band and picks a risk-weighted sample for the checker; holds a batch when a sample item is wrong.
Replays 30 days of payments against the new rules, orders the work by money at risk, proposes dormant payees to retire, projects the finish and drafts the steering report.
Make, check, report. The agents propose; a named person decides.
Ask about any address, batch, client request or the forecast, or say what to draft. Every answer cites its source.
Why is the street empty for Kessler GmbH?
Kessler GmbH has a post-box address. The master, the German postal reference, Kessler's own bank and its invoice all give Postfach 12 04 33, 80331 MUENCHEN and no street. A fully structured address needs town and country, not a street.
Which clients put the most payments at risk on 14 November?
Replaying the last 30 days, 6,214 of 48,960 payments would be rejected. By payments: Brightwater Marine Components (412), Halvorsen Grain Exporters (288), Calloway Medical Devices (241). By value: Sable Ridge Energy Partners ($204.6M across 9 payees).
Draft a request to Brightwater for the addresses we cannot prove
The draft is ready: 37 payee addresses, each pre-filled with what we could prove, due Thu 5 Nov, to Laura Brandt in the client portal. It does not mention screening. Ben Thornquist approves the sending.
Will we finish before 14 November?
At this week's pace, 2,310 approvals a business day, the beneficiary master is done by Fri 30 Oct and the client master by Mon 2 Nov. The risk is what clients must answer: 412 beneficiary and 302 client addresses.
13 screens from the working solution, on its sample data. Pick one to see it large.
What Corvane configures for the address program. Every change is a governed change: an administrator proposes it, the program manager approves it, and both are on the audit trail.
| Setting | Default | Choose from |
|---|---|---|
| Batch threshold | 95% or higher goes to a checker in a batch | Any confidence, as a percentage |
| Always a person below | 80% | Any confidence, as a percentage |
| Post box with no street needs a person | On (policy AP-04 §3.2) | On · Off |
| Prefer fully structured; hybrid only when the street cannot be proven | On | On · Off |
| Sample for a batch | 25 up to 2,000 · 40 up to 5,000 · 80 after a hold | Any sample size |
| Decide and check within | Needs a person 3 business days · checker 1 business day | Any number of business days; overdue items go to the program manager |
| Client reminders | Reminder on day 5 · relationship manager on day 8 | Any day |
| Keep every change and its evidence | 5 years | Five years or more |
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 of where the working minutes on one doubtful address go · “typical” = published figures (an industry study of failed payments: $12.10 average cost of a failed payment, name and address errors behind 21% of failures, 72% of firms checking them by hand). Rules named: Swift CBPR+ Standards Release 2026, removal of the unstructured postal address (14 November 2026); the payments market practice group's hybrid postal address guidance; the Fedwire Funds Service ISO 20022 address rules; BSA recordkeeping, 31 CFR 1010.430. Corvane National Bank, its clients, payees, banks, identifiers and the people named on this page are fictional: characters and sample data in the working solution.
ISO 20022 Structured Address Remediation turns the free-text addresses in a bank's client and beneficiary master into ISO 20022 structured address fields before the 14 November 2026 deadline. Seven agents split each address into elements, prove each one from postal reference data, the party's own payments and its documents, check the Swift CBPR+ and Fedwire rules and screen the result in test mode. A payments data analyst approves as maker and a checker signs every change, with the before and after kept.
From 14 November 2026 Swift accepts only fully structured or hybrid postal addresses for parties and agents in cross-border payments, with town and country at a minimum. A fully structured address carries no address line; a hybrid one keeps town and country structured with at most two free-text lines of 70 characters, and an element must not be repeated in a line. There is no contingency: a message that breaks the rule is rejected.
It prefers fully structured and uses hybrid only when the street cannot be proven. The rules agent checks either form before anything is proposed, and the setting is the bank's to change. An address that is a post box with no street, or whose sources disagree, goes to a person.
The verification agent proves each element against three sources: postal reference data, the payments the bank has sent to and received from that party, and the invoices and forms in document imaging. A structured pacs.008 from the payee's own bank is the strongest proof. Every value is cited, and the analyst clicks a citation to read the passage.
Yes. A structured town or region can produce a new potential match, and a false alert can disappear. Every new address is screened in test mode first; in the demo, 18 results changed overnight. Changed results go to the sanctions team, and the solution never clears or decides a match or mentions screening to a client.
The outreach agent drafts one request per treasury client in the client portal, with each proposed address already filled in for the client to confirm or correct. The implementation manager approves the sending, the agent reminds on day 5 and tells the relationship manager on day 8, and replies are read back into proposals.
Yes. The agents propose and never change the master on their own. Every change has a maker and a checker, a batch is approved only after the checker reads its sample, retirements need a second approval from the program manager, and every edit, rejection or return carries a reason code on the audit trail.
The Agentic Solution Engine builds and deploys ISO 20022 Structured Address Remediation from your requirements and documents: your address policy, your roles and SLAs, and the systems it connects to. It goes live once every quality gate has passed. We'll walk you through it first on a sample of your own addresses.
Every wire’s travel rule data checked for meaning, and every gap chased to a fix.
1-min demoWire Inquiry & Payment Tracking'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 demoWe'll run ISO 20022 Structured Address Remediation on a sample of your own client and beneficiary addresses.