Standards releases

Gain a clear picture of upcoming releases and manage the impact on your business using our dedicated tools

Release highlights

Standard MT Release 2019 - Business highlights

The annual MT Standards release ensures that the message types (MTs) exchanged by SWIFT users remain suitable for the business areas in which they are used, by enabling new business functionality and compliance with changing regulations.

 
 

Click here to learn more about high level, business information related to the changes made to MT messages as part of Standards Release 2019 (SR 2019).

0
White

Standard MT Release 2018 - Business highlights

The annual MT Standards release ensures that the message types (MTs) exchanged by SWIFT users remain suitable for the business areas in which they are used, by enabling new business functionality and compliance with changing regulations.

Click here to learn more about high level, business information related to the changes made to MT messages as part of Standards Release 2018 (SR 2018). An overview of SR 2018 is also available in 3 . 

0
White

Standard MT Release 2018 - Mandatory changes in category 1 and category 2

Please note that there are changes for Standards MT Release 2018 in category 1 and 2 that have a bigger implementation impact than most MT standards releases:

  • Field 121 in header block 3 will be mandated in MT 103, MT 103 STP, MT 103 REMIT, MT202, MT205, MT202 COV, MT 205 COV
  • Customers of the SWIFT global payments innovation (gpi) service can include field 111 in combination with field 121 (fields in header block 3) in messages where the receiver is not a SWIFT gpi customer. All users must be able to receive field 111 in combination with field 121 in all category 1 and 2 messages.

 
 

Read the following article to find out more on the changes and links to the related documentation or follow a dedicated . 

To ensure the community is aware of the changes and to provide you with all the information you need, SWIFT Standards has organised webinar sessions that have been recorded. More information can be found here.

0
White

Standard MT Release 2018 - BIC Implementation

The ISO 9362 Business Identifier Code (BIC) standard was revised in 2014. A transition period started in January 2015 and will end 18 November 2018.

All details of implementation changes and impact of the revised ISO 9362 BIC standard can be found in the below information paper:

 
 

Standards
Last update: 
11 January 2019

Information paper: ISO 9362:2014 – BIC Implementation

Changes and impacts
PDF iconDownload (111.05 KB)
  • Data standards
0
White

Standards MT Release 2018 and 2020: prepare for major changes related to Category 7 messages

A significant upgrade to Documentary Credits messages was performed in November 2018 as part of the continuous improvement of our standards.

Another upgrade, to the Guarantees/Standby LCs message,  is now planned for November 2020 (was deferred from 2019).

The latest documentation for the Category 7 Guarantees/Standby LCs messages can be found on the MT Release 2019 timeline here.

 
 
 

In addition to the above changes, we have also published the new MT 798 Trade Guidelines for corporate-to-bank communication V5.1.1 (18 May 2018).

To ensure the community is aware of the upcoming changes in SR 2020 and MT 798, SWIFT Standards has organized webinar sessions in the course of June 2018. The collateral used, slides, FAQ document and recording of the webinars are available here.

0
White

Free format options for fields 50 and 59 will not be removed in MT in SR 2020

During SR 2019 discussion, a change request submitted by the Payments Market Practice Group was accepted to no longer enforce format option F in MT party fields, but to enforce it when migrating to ISO 20022. ISO 20022 messages allow for more granular structure than the format option F in MT.

Screening the name and address of the ordering customer (payer) and beneficiary (payee) against sanctions lists is required to comply with AML and anti-terrorist financing regulations. Being able to distinguish the different parts of name and address in a structured way is required for handling banks to properly perform screening against sanctions lists issued by various authorities. 

 
 

Structuring underlying customer data has far-reaching consequences for banks’ payment processing systems and requires a multiyear effort. Banks must therefore continue their efforts in gathering the necessary input to update their systems.

0
White