ISO 20022 Migration in the US: What's Changing (and What's Just Been Delayed)

The ISO 20022 migration is the biggest shift in payment messaging in a generation, and for US finance teams, it has just become more confusing rather than less. The industry-wide deadline to stop accepting unstructured addresses in payment messages, originally targeted for November 2026, has been pushed back by both Swift and the Federal Reserve.

For US businesses, three different payment rails, Fedwire and CHIPS, ACH and FedNow, and cross-border Swift payments, are each on their own timeline. Treating them as one deadline is the single most common mistake we see finance teams make.

What is ISO 20022 migration?

ISO 20022 migration is the global banking industry's shift from the older MT payment messaging standard to ISO 20022, a structured, XML-based format that carries far richer payment data, including addresses broken into separate fields rather than free text.

Banks worldwide have been replacing MT with ISO 20022 for both payment instructions and account reporting. For US businesses, the practical change shows up first in how beneficiary and debtor addresses are formatted: a single free-text line is no longer enough, addresses need to be broken into structured elements (building number, street, town, country) or, at minimum, a hybrid format where town and country sit in their own fields**, with any remaining address detail (street, building number) limited to a maximum of two free-text lines of 70 characters each. ERPs that export addresses split across three or four lines will fail hybrid validation even after the structured fields are added correctly. 

Why this is happening

Structured addresses improve data quality. They let banks screen payments for sanctions and financial crime more reliably, route them with fewer manual interventions, and reduce the investigation time when something goes wrong. It's an industry-wide move, driven by banks and payment schemes rather than by a single regulator, which is part of why the timeline varies so much by network, and by payment rail.

The Swift and Fedwire ISO 20022 migration timeline: what's confirmed, what's deferred

Swift's core MT-to-ISO 20022 messaging migration for cross-border payments (CBPR+) was completed in November 2025. Fully unstructured addresses were still tolerated at that stage. The next milestone, a hard requirement for fully structured or hybrid postal addresses, was due in November 2026.

This is the most important update for anyone tracking this topic: the structured address requirement that was due to take effect in November 2026 has been officially deferred, and no new date has been confirmed.

On August 27, 2026, Swift announced it was extending the deadline after industry-wide requests for more time, and will confirm a new timeline by December 2026 at the latest.

The Federal Reserve followed the same day. Its Fedwire Funds Service notice (published August 27, 2026) confirms that the November 2026 release, which included removing the fully unstructured postal address option in favor of a mandatory hybrid format for all parties across all message types, has been rescheduled to November 2027. The Fed's notice explicitly credits Swift's decision and describes "a coordinated approach across major peer market infrastructures to preserve global interoperability."

One distinction worth being precise about: it's the address requirement that's deferred, not ISO 20022 itself. 

The underlying ISO 20022 messaging migration (the shift from MT to XML-based MX messages, pacs.008, pain.001 and so on) is already live and isn't going anywhere, for Fedwire since July 14, 2025 and for CHIPS since April 8, 2024. What's been pushed back is specifically the rule that would have rejected messages still carrying a free-text-only <AdrLine> instead of structured fields like <TwnNm> (town name) and <Ctry> (country). This also applies beyond Swift and Fedwire: the European Payments Council (EPC) runs a parallel, aligned structured-address requirement across all five SEPA scheme rulebooks, and its Payment Scheme Management Board also deferred that deadline on September 9, 2026, shortly after Swift's own announcement, with a new date expected in October 2026. So a US business making SEPA payments into the eurozone, through a European subsidiary for instance, is in the same position as one making Swift cross-border payments: the direction is confirmed, the date isn't.

US payment rails: three different timelines

If your payments are purely domestic ACH or FedNow transfers, the pressure has eased considerably, since neither rail was ever on a firm ISO 20022 structured-address deadline. If you regularly send or receive international payments via Swift, or your bank routes Fedwire or CHIPS payments with enhanced data, this is still very much live, it's just no longer pinned to a specific November 2026 date.

What to check on your side

Whatever your payment mix, a few checks are worth doing now rather than waiting for a firm date to reappear:

1. Check your file format. Confirm your ERP or accounting system can produce payment files your bank will accept once structured or hybrid addresses become mandatory.

2. Check your beneficiary data. Every payee record should hold city and country as separate fields, not merged into one address line.

3. Ask your bank directly. Deadlines vary by bank and by payment rail, and some banks may hold to earlier internal timelines regardless of the industry-wide extension.

4. Keep testing. Where your bank offers a validation option, send a sample payment with a structured address now. The Federal Reserve's own Fedwire ISO 20022 Implementation Center is a good example of what a structured testing process looks like, its DIT2 test environment and readiness resources are built for participating financial institutions, but the guidance is accessible to everyone else through their bank.

What this means if you pay through Agicap

The answer depends on how your payments reach Agicap in the first place, and it's worth being precise about the difference between two separate things: formatting the payment message (Agicap's job) and cleaning the underlying address data (the customer's job, whichever route the payment takes).

• •

• If you create your payments directly in Agicap, Agicap builds the correctly formatted ISO 20022 message on your behalf, rolling out the structured address format bank by bank ahead of each bank's own deadline, so most of that technical work happens behind the scenes. What Agicap can't do is invent data that isn't there: if a beneficiary's city and country were never captured as separate fields in the first place, Agicap has no source to pull structured data from. That's why the one thing worth checking is that city and country are stored as separate fields in your beneficiary data, not combined into a single address line, before the format is ever built.

• •

• If your payments are created outside Agicap, in your ERP or accounting software, and then routed through Agicap, the same logic applies one step earlier: that system needs to export an ISO 20022-compliant file with structured or hybrid addresses already in place. Agicap routes the payment through to your bank, but it can't retroactively parse or restructure address data that arrives already flattened into free text.

Either way, the deferral doesn't remove the underlying task: fixing address data at the source is a master-data project.

The bottom line

The November 2026 deadline you may have read about elsewhere has moved, but the direction of travel hasn't changed. Structured payment data is still where the industry is heading, on Fedwire and CHIPS, on Swift, and eventually on ACH and FedNow too. The businesses that keep cleaning up their beneficiary data and testing their file formats now won't be scrambling when the next date is confirmed, whenever that turns out to be.

If your payments run through multiple banks and systems, it's worth checking now whether your setup can handle a structured-address requirement before it's mandatory.

Explore how Agicap handles multi-bank connectivity and payment routing to see where the gaps might be.

Frequently Asked Questions About ISO 20022 Migration

Is the ISO 20022 structured address requirement limited to cross-border Swift payments, or does it reach Fedwire too?

It reaches Fedwire as well, on a coordinated timeline. The Federal Reserve aligned Fedwire's own structured/hybrid-address requirement with Swift's date, originally set for November 23, 2026. Following Swift's August 27, 2026 deferral, the Fed rescheduled the Fedwire release the same day, to November 2027, citing "a coordinated approach across major peer market infrastructures." CHIPS, which completed its own ISO 20022 messaging migration on April 8, 2024, has not published a separate structured-address deadline as of this writing. If your organization also makes SEPA payments, through a European subsidiary for instance, the European Payments Council delayed that requirement too, on September 9, 2026, with a new date expected at its October 2026 meeting.

Does a hybrid ISO 20022 address need more than just the country field?

Yes. A hybrid address requires both city and country as separate, structured fields. A country code on its own doesn't meet the minimum bar, even under the more lenient hybrid format.

My bank has already flagged structured address changes to me, does the Swift deferral cancel that?

Not necessarily. Banks can enforce parts of the structured-address requirement ahead of, or independently from, the industry-wide Swift/CBPR+ timeline. Confirm the exact date and scope your bank referenced rather than assuming the recent deferral automatically applies to your own banking relationship.

Is Fedwire affected by the ISO 20022 migration timeline?

Fedwire itself migrated to ISO 20022 messaging on July 14, 2025. A separate, later requirement to phase out unstructured addresses in favor of a mandatory hybrid format was aligned with the November 2026 Swift deadline and has been deferred alongside it, with the Federal Reserve rescheduling it to November 2027.

Do ACH and FedNow have a confirmed ISO 20022 deadline?

Not currently. ISO 20022 adoption for the ACH network remains voluntary, supported by Nacha's mapping guidance rather than a mandate. FedNow was built as ISO 20022-native from launch, so no separate structured-address deadline applies to these domestic retail rails at this time.