SWIFT / Learning brief
The ISO 20022 migration timeline
Your notes
In simple terms / 01
What this means in plain language
The move from MT to ISO 20022 is a dated schedule, not a single switch: CBPR+ coexistence from March 2023, CHIPS in 2024, Fedwire's cut-over on 14 July 2025, the end of cross-border MT coexistence in November 2025, mandatory structured or hybrid addresses from 15 November 2026, and later statement-message retirements through 2027-2028.
The world's banks are moving their payment messages from the old MT format to ISO 20022, and they are doing it on a published schedule rather than all at once. For years the two formats run side by side, an overlap called coexistence, so a payment can start in one format and finish in the other. The schedule has a handful of dates worth memorising: cross-border coexistence began in March 2023, the US systems CHIPS and Fedwire moved in 2024 and 2025, cross-border MT payment messages were retired in November 2025, structured addresses become mandatory on 15 November 2026, and a few remaining message types retire through 2027 and 2028. Which date matters depends on which rail your payment travels.
Complete lesson / 02
Understand the full idea, step by step
The switch from MT to ISO 20022 is often described as a moment. It is not — it is a schedule that runs across several years, and different parts of it belong to different bodies. This lesson gives you the dates that matter and, more usefully, teaches you to ask 'which rail, which milestone?' before you assume a payment world is finished changing.
If everyone agreed to move to ISO 20022, why not just switch on one day and be done?
Because every bank, every screening system, and every archive would have to be ready on the exact same midnight — an impossible ask across thousands of institutions and time zones. Instead the industry ran a coexistence period: for years both formats travel the network, so a payment can leave in MT and arrive in ISO 20022. The schedule is the price of not breaking payments while you rebuild them.
The migration, milestone by milestone
March 2023 — CBPR+ coexistence begins: banks can send and receive ISO 20022 for cross-border payments over SWIFT while still using MT.
2024 — CHIPS, the private-sector US high-value clearing house, migrates its messaging to ISO 20022.
14 July 2025 — the Fedwire Funds Service completes a single-day cut-over to ISO 20022.
November 2025 — cross-border coexistence ends: in-scope legacy MT payment and cash-reporting messages are retired and the MT-to-MX translation service is withdrawn.
15 November 2026 — a fully unstructured postal address is no longer permitted; a structured or hybrid address becomes mandatory, aligned with that year's Standards Release.
2027-2028 — the remaining MT category 9xx statement messages and 1xx and direct-debit-style messages retire on their own schedule.
Who owns which date
- Cross-border coexistence
- SWIFT ISO 20022 adoption programme — began March 2023, ended November 2025
- CHIPS cut-over
- The Clearing House — 2024
- Fedwire cut-over
- Federal Reserve Financial Services — 14 July 2025
- Address mandate
- CBPR+ usage guidelines — structured or hybrid required from 15 November 2026
Why the address date is the one to watch now
The most disruptive remaining milestone is not a message retirement — it is the address rule. From 15 November 2026 a payment may no longer carry a fully unstructured postal address; the address must be structured (each part in its own labelled element) or hybrid (a town and country structured, the rest as text). The work is not in the message software but in the customer channels, where addresses are still often captured as free-text lines. An address typed loosely at the front door now fails downstream, so the fix has to happen where the data is first entered.
The gateway fallback goes away
During coexistence, many banks leaned on translation: receive ISO 20022, convert it to MT for an older internal system, and convert back on the way out. When the cross-border coexistence period ended in November 2025, the SWIFT MT-to-MX translation service for in-scope payments was withdrawn. Translation between formats still happens inside banks for legacy interfaces, but 'we will translate it at the gateway' is no longer a network-provided safety net for those cross-border flows. That raises the value of screening the richest available format before any lossy step.
COMMON CONFUSION
“Once cross-border MT was retired in November 2025, ISO 20022 migration was finished.”
November 2025 ended coexistence for in-scope cross-border payment instructions on SWIFT only. Domestic high-value systems moved on their own dates, the mandatory address change lands in November 2026, and remaining statement and other MT messages retire through 2027-2028. Different rails finish at different times.
STRICTLY SPEAKING
The dates here summarise programmes owned by different bodies and revised more than once. SWIFT sets the cross-border coexistence schedule, each market infrastructure sets its own domestic cut-over, and address rules ride the annual Standards Release. When a date is load-bearing for a decision, confirm it against the operator's current notice rather than a summary like this one.
FOR NOW, REMEMBER
- The migration is a dated schedule, not a single switch; coexistence let MT and ISO 20022 run together before the old format retired rail by rail.
- Cross-border coexistence over SWIFT ran from March 2023 to November 2025; CHIPS moved in 2024 and Fedwire on 14 July 2025.
- From 15 November 2026 a fully unstructured postal address is no longer permitted — structured or hybrid becomes mandatory, changing data capture in customer channels.
- Always ask 'which rail, which milestone?': one flow can be fully migrated while another the same bank runs is not.
TRY IT YOURSELF
It is December 2025. A colleague says 'ISO 20022 migration is complete, we can decommission all our MT statement handling.' Why should you push back?
The migration made translation and truncation everyday operational concerns. Next, see exactly what happens when rich ISO 20022 data has to fit MT fields and back — and why the address is the emblematic case.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
The migration is a dated schedule, not one switch: coexistence let MT and ISO 20022 run side by side before the old format was retired rail by rail.
- 02
Cross-border coexistence over SWIFT began in March 2023 and ended in November 2025, when in-scope legacy MT payment and cash-reporting messages were retired and the MT-to-MX translation service was withdrawn.
- 03
From 15 November 2026 a fully unstructured postal address is no longer permitted; a structured or hybrid address becomes mandatory, which changes how customer channels must capture data.
Practical use cases / 04
Where you would use this
A payments team maps each of its message flows to its own deadline, because a rail can be fully migrated while another the same bank uses is not.
A screening team plans for the withdrawal of gateway translation after November 2025, so it screens the richest available format rather than relying on a translated MT copy.
A channels team rebuilds an address capture form ahead of 15 November 2026 so free-text addresses are replaced by structured or hybrid fields before the mandate bites.
Worked example / 05
Put the idea into a real situation
Illustrative example: Bank Alfa still lets corporate customers type a beneficiary address as three free-text lines. During coexistence this survived, because a gateway could translate an ISO 20022 message down to an MT one and back. After the cross-border coexistence period ended in November 2025 that translation fallback was withdrawn for in-scope payments, and Bank Alfa now sends ISO 20022 directly. Looking ahead to 15 November 2026, when a fully unstructured address is no longer permitted, Bank Alfa rebuilds its online form so a customer enters the street, building number, town, and country in separate fields. A payment to a supplier at Nordbank that once arrived with a squashed, truncated address line now carries a clean, labelled address a screening engine can read element by element. All institutions named here are fictional.
Evidence & review / 07
Evidence & review
SWIFT cross-border payments and reporting (CBPR+), plus the US high-value systems CHIPS and Fedwire; address rules follow the CBPR+ guidelines and annual Standards Release cycle.
What this brief simplifies: The renovation framing and single milestone list compress a schedule owned and revised by several bodies; confirm any load-bearing date against the operator's current notice.
Sources for this brief5
- Official requirement
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · CBPR+ coexistence (March 2023) and end of coexistence (November 2025)
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
- Official requirement
Fedwire Funds Service ↗ — Federal Reserve Financial Services · Fedwire Funds Service ISO 20022 implementation, 14 July 2025
The Fedwire Funds Service completed its ISO 20022 implementation on 14 July 2025.
- Scheme-specific rule
CHIPS ↗ — The Clearing House · CHIPS ISO 20022 migration, 2024
CHIPS migrated to ISO 20022 messaging in April 2024; participant rules are not fully public.
- Official requirement
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · structured/hybrid address requirement from 15 November 2026
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Milestones are summarised at concept level; the later statement-message retirements run on per-operator and market-practice schedules that have been revised over time.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.