SWIFT Standard Release 2023
This document contains the description of the changes implemented on the product for Standard MT and MX Release 2023 with the timeline associated.
Standard Release 2023 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 updated, 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
The 2023 Standard MT release impacts the following list of messages on our product:
-
MT300
-
MT700/MT707/MT710/MT760/MT767
MT Release Change Requests
| Message Types (MT) | Short description of the modification | Product Impact |
| MT 300 |
CR 001892 Add new code to field 22L across Category 3 and Category 6 messages. To allow reporting in Switzerland of derivatives trades with a jurisdiction reporting code for the Swiss Financial Market Infrastructure Act. Code FMIA is already being populated in field 22L by SWIFT users, this change seeks to add the code to the user handbook. Impact level: 1 |
No impact on payment processing. Only the validations of the Inbound and Outbound formats are impacted. |
| MT 300 |
CR 001899 Address the business need of identifying a non-ISO currency in a message. Extension of field to align with ISO 24165 which includes an extra check character for the 8-character digital token identifier.
Impact level: 2- |
|
| MT 760 |
CR 001651 Add a new field dedicated to the bank of the beneficiary that could be used (if any) when a Local Guarantee is requested alternatively to field 57 of sequence B that could be used in case of Direct Guarantee issuance. Enhancement to new structured MT 760. Impact level: 2+ |
|
|
MT 760 MT 767 |
CR 001773 Add usage rule for transmission outside SWIFT network. To clarify the practice of using the SWIFT message in "pretty print" to advise the beneficiary or applicant. Impact level: 1 |
|
| MT 760 |
CR 001784 Add an optional subfield for country subdivision after country in field 44H. For a number of countries, the law cannot be specified by a country code only. For example, UK where you have to specify England, or Scotland, etc. For the USA, where you have to specify the state. Impact level: 2+ |
|
| MT 767 |
CR 001797 Add optional field for reference of Advising Bank. It is a consistency requirement because the reference is assigned by advising bank and already present in field 23 of MT 760. Impact level: 2+ |
|
| MT 760 MT 767 |
CR 001850 Increase the length of field 24G and allow Z-character set. In many countries, the 6 lines of 35 digits are not enough to detail the contact and address information where the guarantee should be sent or collected and there are issues due to the limited character set where some characters like @ which are important part of name and address are currently not allowed. Impact level: 2+ |
|
| MT 767 |
CR 001851 Add a missing NVR in MT 767 (similar to NVR C6 for MT 700): "In sequence A, if field 22A is ISCA or ICCA, then, in sequence B, fields 24E and 24G are not allowed". The rule must have been part of the previous SR and was found missing. This is a technical change. This change request appears to be similar to CR 001882. Impact level: 2+ |
|
| MT 760 |
CR 001852 MT 760 field 39D (Additional Amount Information) update to name/format/definition and addition of codes. The definition and name of field 39D in MT 760 is not clear and has caused a lot of confusion in the trade finance community. A change in definition and name will ease the use of the field and STP of information on the core trade systems. The change applies to both sequences B and C of MT 760. Impact level: 2- |
|
| MT 760 |
CR 001853 MT 760 field 44H (Governing Law and/or Place of Jurisdiction) update to name and definition. Precise name and definition of field 44H. This CR is an extension to CR#1784 approved earlier (yet to be implemented). Impact level: 2- |
|
| MT 760 |
CR 001854 MT 760 field 51 (Obligor/Instructing Party) update to definition. Modify definition of field 51 in sequence C to avoid confusion with respect to the role of Obligor/Instructing Party. Impact level: 2- |
|
|
MT 700 MT 707 MT 710 |
CR 001856 Increase the length of fields 50, 59, 44A, 44B, 44E, 44F of MT 700 and similar. Increase the length of fields to allow for more information. Impact level: 2- |
|
| MT 710 |
CR 001857 Add a new field for INSTRUCTIONS FROM INTERMEDIARY BANK. Change would make MT 710 more clear for intermediary and advising banks. Impact level: 2+ Updates to the Standards Release Guide as of 24 February 2023
|
|
| MT 767 |
CR 001882 Rule C3 in MT 767 about 24G and 24E to be compliant with rules in MT 760. This is a technical change. The missing NVR must be implemented. This change request appears to be similar to CR 001851. Impact level: 2+ |
|
| MT 760 |
CR 001885 Field 41a should not be allowed in sequence C for DEPU undertaking. To include code DEPU (available in field 22D) along with DGAR in the NVR C11 so that the field 41a (Available With) is available only for Standby Letter of Credit STBY. Impact level: 2- Updates to the Standards Release Guide as of 24 February 2023
|
MX Release impact
The 2023 Standard MX release on the product allows receiving the new following message formats:
-
Camt.107/108/109
-
Camt.055/058
-
Pacs.003/010
-
Pain.008
MX Release new Message Types
| Message Type | Name | MT Equivalent | Product Impact |
| Camt.107 | Cheque Presentment Notification | MT 110 | New formats are available for CBPR+ transformation. To use these formats please contact the IBM Payments Center. |
| Camt.108 | ChequeCancellationOrStopRequest | MT 111 | |
| Camt.109 | ChequeCancellationOrStopReport | MT 112 | |
| Camt.055 | CustomerPaymentCancellationRequest | New | |
| Camt.058 | NotificationToReceiveCancellationAdvice | MT 292 | |
| Pacs.003 | FIToFICustomerDirectDebit | MT 107 | |
| Pacs.010 | Margin Collection – Interbank Direct Debit | MT 204 | |
| Pain.008 | CustomerDirectDebitInitiation | MT 104 |
Standard Release 2023 Timeline
Implementation
The Product implementation for the Standard MT and MX changes is scheduled from June to August 2023.
Client Testing in UAT
Starting on 31 Aug 2023:
-
The Standard MT Release 2023 will be activated. All MT messages processed in that environment will follow the new format validations.
-
The new format introduced for the Standard MX Release 2023 will be available on Client Request.
Client tests need to be completed before 13 Nov 2023.
Production Go Live
The Production Go Live is scheduled for 19 Nov 2023.
For any questions or if you require any assistance, please don’t hesitate to contact the IBM Payments Center.