Table of contents
CBPR+ impacts on the industry
How has the ISO 20022 implementation for cross-border impacted different players in the industry?
ISO 20022 impacts all financial institutions active in cross-border payments as well as market infrastructures and corporates, though only the cross-border payments and reporting messages were subject to the CBPR+ migration timelines.
End of CBPR+ coexistence
When did the CBPR+ coexistence period end?
The coexistence period ended on 22 November 2025.
Read our FAQs category on MT to ISO 20022 and ISO 20022 to MT translation, and Knowledge Base article 6000054 for more information. See the roadmap for the adoption of CBPR+ ISO 20022 non-instruction messages.
Where can I go for help if I have any issue after the End of Coexistence?
If you experience any issue since the weekend, refer to our troubleshooting guide for messages that may be Negatively Acknowledged (NAK’ed) after the end of coexistence: Swift ISO 20022 end of coexistence troubleshooting guide (English)
You can also find translations of this guide in French; Spanish, Russian, Japanese and Mandarin on the ISO 20022 support page.
Sending
- For assistance with issues sending FIN messages since 22 November 2025 refer to KB 6000394 - Contingency Processing FIN Network Validated Rules Troubleshooting Guide.
- For assistance with Payment Instructions Flows since the end of coexistence weekend.
Receiving
- For assistance with issues receiving FINplus ISO 20022 messages, please refer to KB 5026230 - FINplus Aborts Troubleshooting Guide.
- For information on in-flow translation, how it works, translation results and configuration, please access our In-Flow Translation Guide.
What do I need to do now if I haven’t fully migrated?
If you haven’t fully made the transition for some or all of your flows and are relying on contingency processing or in-flow translation, you should start planning your move to ISO 20022 in 2026. We strongly recommend full adoption of ISO 20022 for payment instruction messages to minimise operational, business and financial impacts. We have lots of resources to support you with this transition, such as the CBPR+ Project Navigator which allows you to plan, track and manage your migration with a structured step-by-step journey. This tool provides a detailed list of activities for each project phase, along with pointers to supporting documentation. Project Navigator can be accessed by owners of a swift.com MySwift account.
Contingency processing and in-flow translation service are chargeable as of 1st of January 2026, see Pricing and Invoicing - Price List for Swift Messaging and Solutions for more information.
Receiving – In-flow translation
If you have made the transition to ISO 20022 and are ready to opt out of in-flow translation, before you submit your request to opt-out of the Live service, you must test the opt-out in the FINplus pilot current or future on all your downstream systems to ensure that none of the internal downstream systems are expecting the embedded MT when you receive ISO 20022. You can opt-out of In-flow in the pilot service here.
After opting-out, there is no immediate rollback available.
Sending – Conversion processing
If an MT is sent by your institution, the message will automatically be subject to additional validation and conversion processing as there is no opt-in. From 1st January these converted messages will be chargeable so ensure you do not send any MTs after this date if you want to avoid charges. See also details about available local solutions in What is the difference between contingency processing for MT senders, the in-flow translation service, local translations with Swift Translator and Transaction Manager? or contact your third party provider.
Should you have any questions, please contact your account manager.
What do I need to do now if I have fully migrated the payment instructions messages?
Start preparing for the November 2026 CBPR+ changes. See the roadmap for the adoption of CBPR+ ISO 20022 non-instruction messages.
Should you have any questions, please contact your account manager.
Tools available for CBPR+ messages
What standards management tools are available and where can they be found?
MyStandards is a web-based platform provided by Swift to facilitate the management and implementation of ISO 20022 (and MT) standards and related market practice information. This collaborative platform provides access to the published guidelines (CBPR+ or market infrastructure-related guidelines), user testing via the Readiness Portal, and access to the Translation Rules, all available in MyStandards.
Test environments for CBPR+ messages
What are the different testing environments available for CBPR+ messages?
There are two messaging services available for the testing of CBPR+ messages:
- the FINplus Pilot Current service replicates the same message versions and features as the FINplus Live service
- the FINplus Pilot Future service is used to introduce the new message versions and features that will be implemented on the FINplus Live service at the next Standards Release.
For more information, read the FINplus Service Description.
Cost of CBPR+ migration
What is the cost of the CBPR+ migration? Are there extra fees?
The pricing for ISO 20022 messages has been published in an updated Price List for Messaging and Solutions.
From 1 January 2026, additional charges will be automatically applied for contingency processing for MT senders and the in-flow translation service for payment instruction messages. Those charges are not included in the Fixed fee nor in Swift Essentials.
Swift may decide to increase these charges in the future with prior notice, to ensure continued momentum to complete the migration. Such review will be subject to Swift’s standard governance rules as well as the usual customer notification timelines.
How is gpi impacted
How is gpi impacted by the ISO 20022 migration? If my institution is using MT for gpi confirmations and tracking today, when should I implement ISO 20022 for gpi?
MT 199 and MT 299 involved in the tracking of transactions (Tracker-to-User and User-to-Tracker) by the GPI Tracker (GPI, g4C, Universal Confirmations and Swift Go) will still be supported post-November 2025. No end date has been defined yet. However, MT 199 and MT 299 messages are deprecated and new features will only be made available in ISO 20022 trck message and API formats. New customer implementations of tracking should not use MT n99 formats, and we recommend users adapt existing implementations to ISO 20022 or API to benefits from new capabilities.
What if I get NAKs or aborts
What should I do if my messages are NAKed or aborted by the FINplus service?
CBPR+ messages sent over the FINplus services are validated against the CBPR+ Usage Guidelines, plus other generic InterAct controls. In case of validation failures, the sender receives back a NAK as part of the InterAct response. For initial guidance on validation error codes, see Knowledge Base article 5025423. For the full list of possible error codes, see the SwiftNet Link Error Codes.
The sender of CBPR+ messages can also receive abort (xsys.012) messages due to business validation rules applied by Transaction Manager or in case of issues with the delivery of the message to the recipient. Troubleshooting information is available in Knowledge Base articles 5025819 and 5026230.
Do I need to do anything for my messages to be subject to contingency processing?
Yes, you need to ensure your messages follow the additional validation rules. See our end of coexistence guide for details on what you need to do.
