Sebastien Rousseau

Topic hub

ISO 20022 for banks: a migration guide

ISO 20022 is the messaging standard now used by CHAPS, T2, the Fedwire Funds Service and Swift cross-border payments. The rail migrations are done; the work left is data quality, from structured addresses to purpose codes and LEIs. This hub gives verified dates, reading paths by role and practical answers for banks planning the next releases.

At a glance

The facts that matter

  • CHAPS and the Bank of England's RTGS system migrated to ISO 20022 on 19 June 2023. Source (checked 2026-11-10)
  • T2 launched in March 2023, replacing TARGET2, and uses ISO 20022 in common with T2S, TIPS and ECMS. Source (checked 2026-11-10)
  • The Fedwire Funds Service migrated to ISO 20022 in July 2025. Source (checked 2026-11-10)
  • On 27 August 2026 Swift delayed its November 2026 Standards Release, and the Bank of England deferred its November 2026 RTGS release in full. Source (checked 2026-11-10)
  • The EPC will keep accepting unstructured addresses in all five SEPA schemes beyond 15 November 2026; no new end date is set yet. Source (checked 2026-11-10)
  • The CPMI targets full alignment with its harmonised ISO 20022 data requirements for cross-border payments by end-2027 at the latest. Source (checked 2026-11-10)

Roadmap

Dates to plan around

  1. CHAPS and RTGS migrate to ISO 20022. Source
  2. Fedwire Funds Service migrates to ISO 20022. Source
  3. Swift delays its November 2026 Standards Release; the Bank of England defers its November 2026 RTGS release, including CHAPS messaging changes. Source
  4. EPC rulebook updates remove the 15 November 2026 end date for unstructured addresses across its payment schemes. Source
  5. Bank of England expands mandatory Purpose Codes to all CHAPS payments, for initiation channels within direct participants' control. Source
  6. CPMI target for full alignment with harmonised ISO 20022 data requirements for cross-border payments (end-2027 at the latest). Source

Latest thinking

Latest articles

All 77 articles

FAQ

Questions and answers

What is ISO 20022?

ISO 20022 is the financial messaging standard now used by CHAPS, T2 and the Fedwire Funds Service, and by Swift for cross-border payments. It carries richer, structured data than the MT and proprietary formats it replaced.

Is the ISO 20022 migration finished?

The rail migrations are: T2 went live in March 2023, CHAPS on 19 June 2023 and Fedwire in July 2025, and Swift MT/MX coexistence for cross-border payments ended in November 2025. What remains is data work, such as structured addresses, purpose codes and LEIs.

What happened to the November 2026 structured-address deadline?

It was postponed. Swift delayed its November 2026 Standards Release on 27 August 2026, the Bank of England deferred its November 2026 RTGS release in full, and the EPC removed its 15 November 2026 end date for unstructured addresses without setting a new one.

Should banks pause address remediation?

No. The requirement has been deferred, not withdrawn: the Bank of England expects a 12-month deferral, subject to confirmation, and the EPC will set a new end date in due course. Address quality is an upstream customer-data problem that takes longer to fix than the message layer.

What is the difference between structured, hybrid and unstructured addresses?

A structured address puts each component in its own element, such as StrtNm, TwnNm and Ctry. A hybrid address puts at least Town Name and Country in structured fields and the rest in up to two free-text AdrLine elements. An unstructured address uses free-text lines only.

What enhanced data does CHAPS require?

Since May 2025 the Bank of England has mandated Purpose Codes and LEIs for payments between financial institutions, and Purpose Codes for property transactions. From November 2027 Purpose Codes extend to all CHAPS payments, while structured remittance will not be mandated from that date.

What are the CPMI harmonised ISO 20022 data requirements?

They are a common set of ISO 20022 data requirements for cross-border payments, published by the BIS Committee on Payments and Market Infrastructures under the G20 programme. Full alignment is targeted for end-2027 at the latest.

Which ISO 20022 messages matter most for payments teams?

Corporates initiate payments with pain.001; banks exchange customer credit transfers as pacs.008, institution transfers as pacs.009 and returns as pacs.004. Investigations now run on structured camt messages such as camt.029 instead of MT free-format messages.

Where does the business value of ISO 20022 come from?

From using the structured data, not just carrying it. Structured party data improves sanctions screening and reduces manual repair, and structured investigation messages shorten exception handling, but only if the back office keeps the data instead of mapping it back to legacy formats.