Pain001

Research briefing

ISO 20022 in 2026: Deadlines, Data and What Comes Next

The migration is done. Swift has deferred the structured-address deadline, and the data work still decides who gets paid first. Every date, with primary sources.

7 min readLast reviewed

Executive summary. The format migration is done: Swift ended MT–MX coexistence for cross-border payment instructions on 22 November 2025, Fedwire has run on ISO 20022 since 14 July 2025, and more than 98% of payment instructions on Swift now use the standard. The data work is not done. On 27 August 2026 Swift deferred all payments changes planned for Standards Release 2026, including the rule that would have rejected fully unstructured postal addresses from November 2026, because large parts of the industry were not ready. Swift will announce the new timing by December 2026 at the latest. The date moved; the requirement did not. Every claim below links to a primary or corroborating source, checked on 23 September 2026.

01. Coexistence is over#

SWIFT's MT/ISO 20022 coexistence period for cross-border payment instructions (CBPR+) ended on 22 November 2025. MT103 traffic moved to pacs.008, and MT202 and MT202COV to pacs.009. Swift confirmed completion on 25 November 2025 (press release).

Only payment instructions switched. Cash-management reporting still runs in parallel: MT940, MT942 and MT950 statements continue alongside camt messages until November 2028 (Swift implementation FAQ). Corporate-to-bank traffic can keep using MT101, and Swift has set no deadline for corporates to move to SCORE+ (Swift call to action).

02. The structured-address deadline, deferred#

The community decided in 2023 that CBPR+ payment messages would stop accepting fully unstructured postal addresses with Standards Release 2026 in November 2026. On 27 August 2026 Swift deferred that requirement, together with every other payments change in the release, after several communities asked for more time. Swift is consulting banks, central banks, market infrastructures and corporates, and will publish the new timing by December 2026 at the latest (Swift, 27 August 2026).

The target has not changed. Accepted addresses will be structured or hybrid: a hybrid address carries town name and country in structured elements (<TwnNm>, <Ctry>), with up to two 70-character address lines for the rest. Hybrid has been allowed since November 2025, and the Payments Market Practice Group's guideline is at version 1.12 of 5 March 2026 (PMPG v1.12). Swift's own April 2026 data showed 61.2% of payments with unstructured debtor addresses and 62.9% with unstructured creditor addresses (Swift call to action), which is why the deadline moved.

Swift is explicit that the extension is not a pause: structured addresses already flow across the network, and it asks institutions to keep going. The bottleneck is customer master data, not message formatting. Pain001 generates structured and hybrid address elements today; the remediation work lives in your vendor files, and it is the same work whatever date Swift announces.

03. MT101 between banks: also deferred#

Standards Release 2026 would also have retired the interbank MT101 relay, the request-for-transfer flow between banks, in favour of CBPR+ pain.001 version 9, with multi-transaction MT101s rejected and single transactions converted during a contingency period (Swift call to action). That change is one of the deferred payments changes, so MT101 continues to work between banks after November 2026 until Swift sets a new date.

The direction is unchanged, which is where the Pain001 MT101 loader fits: parse the MT101, regenerate it as pain.001.001.09, and validate it against the official XSD on your own infrastructure, with no dependency on in-network conversion you do not control.

04. What is still dated#

  • 12 June 2027. The non-payments part of Standards Release 2026 goes live: all MT messages except Category 1, ISO 20022 securities and funds messages, tracker messages, and exceptions and investigations (Swift update, 21 September 2026). The requirement to receive camt.110 investigations moves with it.
  • November 2027. Investigations move to camt.110 and camt.111 through Swift Case Management, replacing the MT n92, n95 and n96 formats (Swift E&I FAQ). Fedwire's next ISO 20022 release, first planned for November 2026, is also now November 2027 (Federal Reserve, 27 August 2026). In the UK, purpose codes become mandatory on all CHAPS payments (Bank of England policy statement).
  • November 2028. MT statements (MT940, MT942, MT950) end alongside camt reporting (Swift implementation FAQ).

05. The rails, region by region#

  • United States. Fedwire moved to ISO 20022 in a single day on 14 July 2025 (Federal Reserve, On the Wire, August 2025). CHIPS migrated on 8 April 2024 (The Clearing House). FedNow raised its transaction limit to $10 million in November 2025 and settled almost 5.0 million payments worth $274.7 billion in the second quarter of 2026 (Federal Reserve); the Richmond Fed counted 1,725 participating institutions in the first quarter (Richmond Fed).
  • Euro area. T2 has run on ISO 20022 since March 2023. The Instant Payments Regulation is fully in force for euro-area payment service providers: receiving since 9 January 2025, and sending plus Verification of Payee since 9 October 2025, for standard and instant credit transfers alike (ECB). The ECB announced cross-currency settlement in TIPS between euro, Swedish krona and Danish krone on 10 June 2026 (ECB).
  • United Kingdom. CHAPS has run on ISO 20022 since June 2023. Since May 2025, purpose codes are required on interbank and property payments and LEIs on interbank payments; from November 2027 purpose codes extend to all CHAPS payments (Bank of England). The retail New Payments Architecture, as procured, was cancelled; renewal now runs through the Payments Vision Delivery Committee (Bank of England).
  • Asia-Pacific and the Gulf. Singapore's MEPS+ (2022), Australia's RITS (March 2023, RBA) and Hong Kong's CHATS (2024) are on ISO 20022. Japan's BOJ-NET, on the standard since 2015, moved to the 2019 message versions in November 2025 (Bank of Japan). The UAE's ISO-native Aani instant scheme reported 74 participants and more than 12.5 million users in April 2026 (Al Etihad Payments), and has chosen Montran for its cross-border gateway (Montran).

06. Beyond compliance: what the data is for#

  • Identity. The active LEI population passed 3 million in the first quarter of 2026 (GLEIF), and the FSB recommends LEI use in cross-border payments.
  • Speed. ACI Worldwide forecasts 575.1 billion real-time transactions a year by 2028, 27.1% of all electronic payments (ACI Worldwide, 2024).
  • Progress. The FSB's October 2025 review found that satisfactory global improvement is unlikely by the 2027 deadline for the G20 cross-border targets (FSB). Structured data is a prerequisite for closing that gap, which is why the CPMI updated its harmonised ISO 20022 data requirements in February 2026 (BIS CPMI).
  • Fraud. In a Swift experiment with 13 institutions, a federated-learning model trained on synthetic data from 10 million transactions found known fraud about twice as effectively as a model trained on one institution's data (Swift). Rich, structured payment data is what makes that kind of model possible.
  • Agents. Mastercard Agent Pay, Visa's Trusted Agent Protocol and Google's AP2 are building the authorisation layer for AI-agent commerce, and the Linux Foundation's x402 Foundation launched in July 2026 with Visa, Mastercard and Stripe among its members (Linux Foundation). At the file layer, where corporate credit transfers are initiated, pain001-mcp lets an agent generate and validate pain.001 files locally, against the official schema.

07. What to do this quarter#

  1. Audit address data now. Count beneficiaries with free-text-only addresses. The deferral buys time to fix them, not a reason to stop.
  2. Plan for the dates that stand. June 2027 for investigations and the non-payments release, November 2027 for CHAPS purpose codes and case management, November 2028 for statements.
  3. Regenerate, do not translate. Move remaining MT101 flows to validated pain.001.001.09 on your own timetable, before Swift sets one.
  4. Validate before the bank does. A --dry-run gate in CI catches schema and rulebook failures at commit time, at no cost.

Swift will publish the new structured-address timing by December 2026, and this page will be updated when it does.

References#

  • Swift (2025). Global financial community completes switch to ISO 20022. swift.com
  • Swift (2026). Swift accepts community request to extend structured address migration for ISO 20022 payment messages (27 August 2026, updated 21 September 2026). swift.com
  • Swift (2026). ISO 20022 in bytes: call to action for November 2026. swift.com
  • PMPG (2026). Hybrid Postal Address, v1.12 (5 March 2026), published by the Payments Market Practice Group. swift.com
  • Federal Reserve Financial Services (2026). Fedwire Funds Service November 2026 release rescheduled. frbservices.org
  • European Central Bank (2025 to 2026). Instant Payments Regulation; TIPS cross-currency settlement. ecb.europa.eu
  • Bank of England (2025). Expanding mandatory ISO 20022 enhanced data in CHAPS from 2027. bankofengland.co.uk
  • CPMI (2026). Harmonised ISO 20022 data requirements for enhancing cross-border payments: updated report. bis.org
  • FSB (2025). G20 Roadmap for Cross-border Payments: consolidated progress report. fsb.org
  • GLEIF (2026). The LEI in numbers: active LEI population surpasses 3 million in Q1 2026. gleif.org
  • ACI Worldwide (2024). Prime Time for Real-Time. aciworldwide.com