Table of contents
CBPR+ impacts on the industry
How does ISO 20022 implementation for cross-border impact different players in the industry?
ISO 20022 will impact all financial institutions active in cross-border payments as well as market infrastructures and corporates, though only the cross-border payments and reporting messages are subject to the CBPR+ migration timelines. Organizations will have to consider and implement solutions to process and store richer and more structured ISO 20022 messages that will impact the core payment application, middleware, reconciliation, AML/KYC, archiving, reporting applications, messaging interface and acquisition channels.
To extract and realize the true benefits of ISO 20022, it needs to be implemented end-to-end. Payment MIs from major reserve currencies are live or plan to adopt ISO 20022 for domestic clearing and settlement, while the Corporate to Bank Market Practices (CGI) continues to promote wider acceptance of ISO 20022.
For further insights on opportunities ISO 20022 offers, make sure to read our ‘Supercharge your payments business with ISO 20022’ ebook.
End of CBPR+ coexistence in November 2025
Is November 2025 still the end of CBPR+ coexistence?
At its March 2024 meeting, the Swift Board re-confirmed the community’s commitment to ending the coexistence period in November 2025, emphasising that priority should be given to payment instruction messages to ensure operational continuity and interoperability.
For more details, see Knowledge Base article 6000054.
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.
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.
