CBPR Plus MT MX Equivalence
CBPR Plus MT MX Equivalence
March 2025
Confidentiality: Public
Introduction
The intention of this Cross-Border Payment Reporting plus The CBPR+ messages that are introduced during the
(CBPR+) MT to MX equivalent table is to document the coexistence period are not subject to changes until the
collection of ISO 20022 messages supported on Swift’s end of MT/MX coexistence. That is, unless the Swift
InterAct FINplus service in comparison with the legacy MT community agrees to implement a change following
Category 1, 2 and 9 messages. the identification of a significant defect or regulatory
requirement.
All CBPR+ Usage Guidelines are included in one collection
published on MyStandards. All payment messages within This does not prevent the CBPR+ message suite from
this collection contain a single transaction to enable having additional messages provisioned during the
management of the end-to-end transaction. maintenance release cycle. The maintenance releases
of CBPR+ messages are communicated through the
The general intention is to retire all legacy MT Category 1, annual Standards Release process described on
and 2 and 9 messages used outside of a FIN User Group. swift.com.
Details on the targeted retirement date are included within Where message translation is provided, the translation
this document for each message. documentation can be found on the CBPR+ landing
page ‘Translation Portal’ button.
It should be noted that:
For more information on the messages that are in
scope of Transaction Manager Release 1, as well as
- FIN MT messages that are due to be retired completely
other ISO 20022 messages for which Swift provides
from the network will be subject to a NACK as of the
in-flow translation, please refer to the Transaction
retirement date detailed in this document;
Manager Service Description or the In-flow Translation
Service Overview respectively.
- FIN MT messages that are described to be “Deprecated,
but supported” are those which will no longer be
maintained by Swift as of the date detailed in this
document, but may still be used;
March 2025
Confidentiality: Public
CBPR+ - Inventory of messages – No equivalent and Category 1
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation Portal’ button.
CBPR+ - Inventory of messages – No equivalent and Category 2
MT 200 pacs.009.001.08
MT 201 pacs.009.001.08
MT 202 pacs.009.001.08
MT 202 (with pacs.009.001.08 - ADV
Reimbursement Agents – November 2025
Fields 53 and 54)
MT 202 COV pacs.009.001.08 COV Published on MyStandards
March 2023
MT 202 /RETN/ pacs.004.001.09
MT 203 pacs.009.001.08
MT 204 pacs.010.001.03 Deprecated, but supported after
November 2025
MT 205 pacs.009.001.08
November 2025
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation
Portal’ button.
CBPR+ - Inventory of messages – No equivalent and Category 2 (contd…)
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation
Portal’ button.
CBPR+ - Inventory of messages – No equivalent and Category 9
MT 900 camt.054.001.08
MT 910
MT 920 camt.060.001.05
Deprecated, but
MT 935 camt.053.001.08 Published on MyStandards supported after
MT 940 camt.053.001.08 March 2023
November 2025
MT 941 camt.052.001.08
MT 942
MT 950 camt.053.001.08
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page
‘Translation Portal’ button.
CBPR+ Portfolio-
November 2023
March 2025
Confidentiality: Public
CBPR+ - Inventory of messages – No equivalent and Category 1
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation
Portal’ button.
CBPR+ - Inventory of messages – No equivalent and Category 2
* This Usage Guideline covers a scenario specific to Central Counterparty (CCP) for margin payments
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation
Portal’ button.
CBPR+ Portfolio-
November 2024
March 2025
Confidentiality: Public
CBPR+ - Inventory of messages – No equivalent and Category 1 and 2
Deprecated, but
MT 190 camt.105.001.02 (Single Transaction) Published on MyStandards November 2024 supported after
MT 191 camt.106.001.02 (Single Transaction) November 2025
Deprecated, but
MT 112 camt.109.001.01 Published on MyStandards November 2024 supported after
November 2025
Note that Swift does not provide translation capabilities for all messages in scope – where message translation is provided, the translation documentation can be found on the CBPR+ landing page ‘Translation
Portal’ button.
Exceptions and
Investigations
November 2024
March 2025
Confidentiality: Public
Exceptions and Investigations - Inventory of messages – Category 1 and 2
Deployment FIN MT
Business Messages Usage Guidelines Date in FINplus Retirement date
*camt.110 and camt.111 will be available on an opt-in basis from November 2024 for early adopters and will be part of CBPR+ portfolio by SR2025
for the wider community
CBPR+ Portfolio-
November 2025
March 2025
Confidentiality: Public
CBPR+ - Inventory of messages – No equivalent and Category 1
admi.024.001.01 November
MT 299 Work in Progress TBD
(“Notification of Correspondence”) 2025
Exceptions and
Investigations
November 2025
March 2025
Confidentiality: Public
Exceptions and Investigations - Inventory of messages – Category 1 and 2
Deployment FIN MT
Business Messages Usage Guidelines Date in FINplus Retirement date
March 2025
Confidentiality: Public
List of MT messages not in scope of the migration
MT Message Name
March 2025
MT198
Proprietary message This message type is used by financial institutions, with their own offices, with other financial institutions
and/or with corporate customers with which they have established bilateral agreements
MT 298
It is used as an envelope for a specified message included in it.
It allows for the definition of a unique format for which another message type is not available or applicable.
Proprietary message
It also allows financial institutions to use message types which are awaiting live implementation on the
SWIFT system.
For use of messages in the corporate-to-bank environment, see the MT message implementation guide
and the message matrix for corporate customers available on www.swift.com.
MT n90
MT n91
These messages for categories 3, 4, 5, 6, 7 and 8 are out of scope
MT n92
Common* n message types
MT n95
These messages for category 9 (for non-payment usage) are out of scope
MT n96
MT n98
MT n99
* The common group consists of messages which are common to all message categories, that is, each of the common group messages may be
used in each of the message categories.