There are no items in your cart
Add More
Add More
Item Details | Price |
---|
In this post let us get a bird’s eye view of the broad message categories which are undergoing migration from MT to MX in CBPR+ usage.
Let us understand in detail what exactly are the deadlines associated with CBPR+ migration as of July 2025 announcement by SWIFT. Keep in mind, these deadlines are subject to change. First the deadline of 22nd November, 2025. Which messages fall under this deadline? Let’s understand.
These payment instruction messages, when used cross border, must be migrated to the corresponding MX messages by November 2025.
So, in Cat 1 - MT 102 and its variants and MT 103 and its variants.
In Cat 2 - MT 200, 201, 202, 202 Cov, 203, 205 and 205 Cov. All these messages must be migrated to the corresponding MX messages of pacs.008, pacs.009 and its variants.
Also all rejects and returns related to these messages must also be migrated to pacs.002 and pacs.004.
Updated price list from SWIFT includes charges for contingency measures mentioned in 1 and 2 above, to encourage ISO 20022 migration. Charges may increase, with prior notice.
Now, we know that one of the main aims of migration from MT to MX is to gain access to granular and structured data.
Thus, by November 2026, the unstructured address format will no longer be allowed in MX messages. Either the hybrid address format or the fully structured format will be allowed.
Another pain point of payment messages is exceptions and investigations, i.e, when a payment message does not get processed at one go and requires more information and involves queries and responses.
To address that swift has included new E&I MX messages which will be centrally handled using a process called case management and these messages will be routed directly to the relevant party skipping the intermediaries.
As a first step for its implementation, by November 2026, all banks must mandatorily be able to receive the camt.110 (Investigation Request) message and by November 2027, all banks must be able to both send a camt.111 (Investigation Response) and receive a camt.110.
Also, for corporate to bank messages and vice-versa, there is no end of coexistence decided as of now.
In this way, step by step, the CBPR+ migration will continue increasing its scope until all the MT messages will get replaced by the more advanced MX messages.
WANT TO READ MORE?
Already signed up/ logged in? Then you are all set!
Basics of Payments | SWIFT MT/ MX Payment Message Types with examples | SWIFT GPI
CBPR+ Usage Guidelines | XML and Messages Schema | Messages Structure | MX Messages Examples
The Ultimate No-Nonsense Guide to SWIFT MT and ISO 20022 MX Message Types