GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
ISO 20022 ·

CBPR+ migration continues after the payment-instruction cutover

The 22 November 2025 deadline applied to in-scope FI-to-FI payment instructions, not every FIN message. Reporting, payment-initiation relay, correspondence and exceptions-and-investigations work follow separate roadmap milestones and service rules.

The end of payment-instruction coexistence was a major milestone, but it was not a blanket retirement of category 9 reporting messages, MT101, MT199 or every other FIN use case. Swift's current roadmap separates those conversations and describes different treatment: some messages are NAKed, some can enter temporary chargeable contingency conversion, and others remain on their own transition path.

Operations teams should therefore inventory by business conversation rather than write one decommission date against the entire FIN estate. Corporate initiation, bank-to-customer reporting, payment confirmations, correspondence, cancellations and investigations each need their own source, current milestone, receiving obligation and fallback decision. A system can be native ISO 20022 for CBPR+ payment instructions while still legitimately processing another MT category under a different roadmap.

Sources for this update2
  1. Official requirement

    CBPR+ roadmap beyond November 2025Swift · CBPR+ roadmap beyond November 2025, published 24 June 2026

    Current roadmap for post-coexistence CBPR+ work, including contingency processing, payment initiation relay, reporting and exceptions-and-investigations migration milestones. · Checked 2026-07-18

    Roadmap dates and message treatment are service-specific and can change. Recheck the current document before using a milestone in delivery planning.

  2. Official requirement

    Swift Standards MT (annual standards releases)Swift · Message-specific Standards Release and FIN treatment

    Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-18

    Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Public discussion

LOADING

Loading the discussion…