SWIFT Standard Release 2025
This document contains the description of the changes implemented on the product for Standard MT and MX Release 2025 with the timeline associated.
Standard Release 2025 Scope
Index of Level Impact
| Level | MT Description | MX Description |
| 0 | This is a minor change that does not impact the format of the message. For example, the scope of the message is updates, which may have an impact on some automated applications. | This is a minor change that does not impact the structure of the message but it may have an impact on some automated applications, for example, the scope of the message is updated. |
| 1 | This change relates to the use of the message format but does not affect the message structure or the FIN validation, for example, a definition or a usage rule is changed. | This change relates to the use of the message syntax but does not affect the message structure or the message validation, for example, a definition or a usage rule is changed. |
| 1+ | An existing message type is removed from the network. | An existing message is removed from the service. |
| 2- | The change has a small effect on the message structure and the FIN validation, for example, field formats, qualifiers, or codes are added or deleted. | The change has a small effect on the message syntax and the message validation, for example, simple data types are changed. |
| 2+ | The message layout or the FIN validation or both are significantly impacted, for example, fields or sequences (mandatory or optional) are added or deleted. | The message syntax or the message validation or both are significantly impacted, for example, an element or a message component or a message building block is added or deleted, or a validation rule is changed or added. |
| 3- | A new message type is created for use in a Message User Group (MUG) or the use of an existing message type is changed from use in a MUG to general use, that is, all users must be able to receive and process the new message. | A new message is added to the service. |
| 3 | A new message type is created for general use, that is, all users must be able to receive and process the new message. |
MT Release impact
MT Release Change Requests
| Message Types (MT) | Short description of the modification | IPC Wire Services Impact |
| MT 300, MT 304, MT 305, MT 306 |
CR 002089 Rename the term Value Date to Settlement Date. To align with ISDA documentation and terminology.
This is a documentation change only that improves the definition. There is no impact to users. |
No impact on payment processing or mappings. |
| MT 300, MT 304, MT 305, MT 306, MT 340, MT 341, MT 360, MT 361 |
CR 002350 Implement the correct character (x instead of a) so ISO 4914 Unique Product Identifiers can be accommodated in the various messages. The foreign exchange and commodities industry approved the implementation of ISO 4914 Unique Product Identifiers across various category 3 and 6 messages as part of Standards release 2024 (SR 2024) under CR 1929. Due to an error in the SR 2024 implementation, Unique Product Identifiers can still not be accommodated in these messages, this was due to an incorrect character being implemented.
This CR will correct the character so the ISO standard can be supported. It is purely a technical correction to the incorrect implementation during SR 2024.
This change is mandatory for users. |
No impact on payment processing or mappings. |
MX Release impact
MX Release new message types
| Message Type | Message Name | New Usage Identifier | IPC Wire Services Impact |
| admi.024.001.01 | Notification of Correspondence | swift.cbprplus.01 | New for SR2025. To use these formats please contact the IBM Payments Center. |
| camt.025.001.08 | Receipt | swift.cbprplus.01 | |
| camt.029.001.09 | Resolution of Investigation | swift.cbprplus.03 | Updated for hybrid postal address. |
| camt.052.001.08 | Bank To Customer Account Report | swift.cbprplus.03 | Usage guideline updated. |
| camt.053.001.08 | Bank To Customer Statement | swift.cbprplus.03 | Usage guideline updated. |
| camt.054.001.08 | Bank to Customer Debit Credit Notification | swift.cbprplus.03 | Usage guideline updated. |
| camt.055.001.08 | Customer Payment Cancellation Request | swift.cbprplus.02 | Usage guideline updated. |
| camt.056.001.08 | FI to FI Payment Cancellation Request | swift.cbprplus.03 | Usage guideline updated. |
| camt.057.001.06 | Notification To Receive | swift.cbprplus.03 | Usage guideline updated. |
| camt.058.001.08 | Notification To Receive Cancellation Advice | swift.cbprplus.02 | Usage guideline updated. |
| camt.060.001.05 | Account Reporting Request | swift.cbprplus.03 | Usage guideline updated. |
| camt.105.001.02 | Charges Payment Notification | swift.cbprplus.02 | Includes multiple charges version. |
| camt.106.001.02 | Charges Payment Request | swift.cbprplus.02 | Includes multiple charges version. |
| camt.107.001.01 | Cheque Presentment Notification | swift.cbprplus.02 | Usage guideline updated. |
| camt.108.001.01 | Cheque Cancellation or Stop Request | swift.cbprplus.02 | Usage guideline updated. |
| camt.109.001.01 | Cheque Cancellation or Stop Report | swift.cbprplus.02 | Usage guideline updated. |
| pacs.002.001.10 | FI to FI Payment Status Report | swift.cbprplus.03 | Usage guideline updated. |
| pacs.003.001.08 | FI to FI Customer Direct Debit | swift.cbprplus.02 | Usage guideline updated. |
| pacs.004.001.09 | Payment Return | swift.cbprplus.03 | Usage guideline updated. |
| pacs.008.001.08 | FI to FI Customer Credit Transfer | swift.cbprplus.03 | Usage guideline updated. |
| pacs.008.001.08 STP | FI to FI Customer Credit Transfer STP | swift.cbprplus.03 | Usage guideline updated. |
| pacs.009.001.08 ADV | FI Credit Transfer (Advice) | swift.cbprplus.adv.03 | Usage updated for SR2025. |
| pacs.009.001.08 COV | FI Credit Transfer (Cover) | swift.cbprplus.cov.03 | Usage guideline updated. |
| pacs.009.001.08 | FI Credit Transfer | swift.cbprplus.03 | Usage guideline updated. |
| pacs.010.001.03 | Interbank Direct Debit | swift.cbprplus.col.02 | Usage guideline updated. |
| pain.001.001.09 | Customer Credit Transfer Initiation | swift.cbprplus.03 | Updated with new hybrid postal address rules. |
| pain.002.001.10 | Customer Payment Status Report | swift.cbprplus.03 | Usage guideline updated. |
| pain.008.001.08 | Customer Direct Debit Initiation | swift.cbprplus.02 | Updated with new hybrid postal address rules. |
MX Release Change Requests
| Message Type | Short description of the modification | IPC Wire Services Impact |
| All CBPR+ usage guidelines |
CR 2006 Introduction of a hybrid (semi-structured) postal address option across CBPR+ usage guidelines for all parties and agents. The hybrid address will allow simultaneous usage of the unstructured AddressLine element and structured elements within PostalAddress. TownName and Country are mandatory elements within the PostalAddress when a hybrid address is used, just as they are when a fully structured address is used.
Until November 2025 (SR2023, SR2024) a fully unstructured address or fully structured address are allowed, except for ultimate debtor, ultimate creditor and initiating party where only fully structured address is allowed.
During November 2025 - November 2026 (SR2025) a fully unstructured address or fully structured address or hybrid address are allowed, except for ultimate debtor, ultimate creditor and initiating party where only fully structured address or hybrid address is allowed.
The unstructured AddressLine element within the hybrid address can be up to 2 lines of 70 characters (2*70).
Statements (camt.052, camt.053) and debit/credit notifications (camt.054) will be updated to accommodate all address options but will not restrict usage of the three options at any stage. Other address formats will also be permitted on statements and debit/credit notifications.
This change is mandatory for all users of CBPR+ usage guidelines. |
Mapping and UI updates will be implemented to enable the platform to accept, display and generate hybrid addresses. UAT tests are recommended. |
| camt.052, camt.053, camt.054 |
CR 2181 Support certain special characters across statements. To support the Securities industry where certain security identifiers may contain such characters that should be reported within a statement.
The Standards Working Group agreed that the CBPR camt.052, CBPR camt.053 and CBPR camt.054 should all be maintained.
This change is mandatory for users who use or receive the Financial Instrument Identification block within the CBPR camt.052, CBPR camt.053 and CBPR camt.054, the change would only be implemented for this block. |
Financial Instrument Identification block will be accepting new special characters: ! # & % * = ^ _ \ { | } ~ " ; @ [ \ ] $ > < ` (in addition to standard characters a-z, A-Z, 0-9, / - ? : ( ) . , ' + .) Mapping updates will be implemented to support the new characters. UAT tests are recommended. |
| All CBPR+ usage guidelines |
CR 2296 Update pattern in CBPR_DateTime and CBPR_Time data types. Correct existing pattern to enable an offset of +14:00 (compared to max +13:00 today).
This change is mandatory for users. |
Mapping updates will be implemented to support this new timezone. Clients need to make sure their systems will be able to accept timezone with +14:00. UAT tests are recommended. |
Future changes - SR 2026
| Message Type | Short description of the modification |
| All CBPR+ usage guidelines |
CR 2006 Introduction of a hybrid (semi-structured) postal address option across CBPR+ usage guidelines for all parties and agents. The hybrid address will allow simultaneous usage of the unstructured AddressLine element and structured elements within PostalAddress. TownName and Country are mandatory elements within the PostalAddress when a hybrid address is used, just as they are when a fully structured address is used. From November 2026 onwards (SR2026…) a fully structured address or hybrid address are allowed. The fully unstructured address is no longer permitted. The unstructured AddressLine data within the hybrid address can be up to 2 lines of 70 characters (2*70). This change is mandatory for all users of CBPR+ usage guidelines. This change has already been approved by the Payments Standards Working Group and will be implemented. |
Standard Release 2025 Timeline
Implementation
The Product implementation for the Standard MT and MX changes is scheduled from June to September 2025.
IPC Wire Services Client Testing in UAT
Starting on 22 September 2025, the SWIFT Standard MT and MX Releases 2025 will be activated. All MT and MX messages processed in that environment will follow the new format validations.
Client tests must be completed by November 7, 2025.
Note: As part of our transition from a bi-weekly release cadence to a 4-week release cycle, the SSR delivery in UAT, originally scheduled for September 8, has been rescheduled to September 22. This adjustment ensures alignment with our internal testing schedule and allows sufficient time for our teams to complete validation activities before release.
Production Go Live
The Production Go Live is scheduled for 22nd November 2025.
For any questions or if you require any assistance, please don’t hesitate to contact the IBM Payments Center.