ISO 20022 MIGRATION HUB
Understanding ISO 20022
Message Formats & Technical Specifications
What You Need to Do?
WHAT IS ISO 20022?
ISO 20022 is the new global standard for financial messaging, replacing the legacy SWIFT MT format for all interbank cross-border and high-value payments, customer payment instructions and associated cash reporting. It uses XML-based messages (referred to as MX) which can carry richer, more structured, and more granular payment data than was possible with fixed-length MT messages.
The migration – driven jointly by the financial industry and SWIFT – ran from March 2023 to November 2025, at which point all financial institutions completed the transition to ISO 20022 XML for cross-border payments. Most major domestic market infrastructures (RTGS and CSM) completed their own migrations before or during this period.
SINCE 22 NOVEMBER 2025: All financial institutions have successfully transitioned from SWIFT MT interbank messages to ISO 20022 XML for all cross-border payments. BNP Paribas completed all migration milestones as a frontrunner institution.
THE CORE CHANGE
Instead of processing payment messages through FIN MT messaging (with its rigid, character-limited fields), banks and market infrastructures now use ISO 20022's data-rich XML standard. This standard can carry substantially more payment information in a structured and machine-readable format.
COMPARISON TABLE: LEGACY MT VS ISO 20022 XML
BUSINESS BENEFITS
The richer, structured, and granular data delivered by ISO 20022 XML messages unlocks significant operational and compliance improvements across the entire payment lifecycle.
AUTOMATION & EFFICIENCY | Enriched data sets promote end-to-end automation through the transaction lifecycle and increase machine-readability – enabling faster processing and straight-through processing (STP).
COMPLIANCE & FINANCIAL CRIME | Structured data leads to fewer false-positive hits in sanctions/compliance screening and more efficient fight against money laundering and terrorism financing.
INTEROPERABILITY | High-value and real-time payment systems converge on a common financial language, enabling frictionless cross-border (instant) payments with aligned formats across market infrastructures.
RECONCILIATION & REPORTING | Improved data quality supports reconciliation processes, centralised accounts payable and receivable, and treasury centralisation — enabling more accurate forecasting and faster treasury decisions.
IMPACT ON CORPORATES
With the adoption of ISO 20022 in the payments, market infrastructures and financial institutions commit to structure the populated data of ordering and beneficiary customers in clearly defined address elements.
As payment initiator, only you have all the details of your counterparties. It is therefore critical that you are capable of providing this data in a structured way, for the payment types that require it.
The payment methods in scope are described in the FAQ.
ADDRESS FORMAT OPTIONS
Payments using unstructured postal address formats will soon be rejected by SWIFT and other market infrastructures.
Two options are valid for formatting a postal address in a client-to-bank 'pain' message.
OPTION 1
FULLY STRUCTURED (RECOMMENDED) | All address attributes are provided in dedicated XML elements. The minimum mandatory fields are Country (ISO 2-letter code) and Town Name. All other fields are optional but recommended where available.
XML Example – Structured
OPTION 2
SEMI-STRUCTURED / HYBRID | Country and Town Name are mandatory structured fields. All other address attributes may be provided in structured elements or in up to 2 unstructured address lines (max 70 characters each). Structured elements must NOT be repeated in the AdrLine fields.
XML Example – Semi-Structure
AVAILABLE STRUCTURED POSTAL ADDRESS ELEMENTS (PAIN.001 V2019)
PAIN.001 VERSIONS
BNP Paribas recommends using XML as the single format for all payment types. The pain.001 format is recommended regardless of version, but version 9 (v2019) is the most recent and complete.
KEY ADDITIONS IN PAIN.001.001.09 (VERSION 2019)
- 14 structured postal address fields (vs. 8 in v3 and 6 in v2)
- Structured fields to identify Ultimate Parties (Ultimate Debtor, Ultimate Creditor)
- Structured Remittance Information with new Line Details element (full granularity per invoice)
- Dedicated UETR field – Unique End-to-End Transaction Reference tracking payment from initiation to settlement
- Legal Entity Identifier (LEI) identification for legal entities – improves AML-CFT controls and sanctions screening
- Proxy element to accommodate alias/proxy identifiers
WHAT YOU NEED TO DO
The need to provide debtor and creditor addresses varies depending on the payment type and the countries involved.
Whether you plan to adopt ISO 20022 XML fully or simply comply with the address structuring requirements, the following steps will help ensure a smooth transition.
FAQ, NEWSLETTER AND MORE
- FAQ > ACCESS HERE
- List of countries requiring the address of the counterparty > ACCESS HERE
- ISO 20022 for Corporates newsletter – September 2026 > ENGLISH VERSION ACCESS HERE | FRENCH VERSION ACCESS HERE
- ISO 20022 Structured Addresses Short Guidelines > ACCESS HERE
BNP Paribas is your partner throughout this transition. Your dedicated Cash Management Officer and our team of experts are available to guide you through every step. Contact your Cash Management Officer or visit www.cashmanagement.bnpparibas.com for further guidance including the online Currency Guide and country-specific address requirements.