Standards Release Guide

Size: px

Start display at page:

Download "Standards Release Guide"

Gordon Sanders
6 years ago
Views:

1 Standards Release Guide This document describes updates to the Standards Release Guide (SRG) that have been identified since the publication of the SRG in December February 2018

2 Table of Contents Table of Contents Preface Summary of Updates Updates by Category Category 1 Customer Payments and Cheques Category 2 Financial Institution Transfers Category 3 Foreign Exchange, Money Markets, and Derivatives Category 4 Collections and Cash Letters Category 5 Securities Markets Category 6 Commodities and Reference Data Category 7 Documentary Credits and Guarantees Category 8 Travellers Cheques Category 9 Cash Management and Customer Status Category n Common Group Messages... 9 Legal Notices February

3 Preface Preface About this document The (SRG) 2018 provides a list of updates to the Standards Release Guide (SRG) that was published in December The Standards Release Guide and the constitute the final documentation based on which SWIFT users and partners must implement SR The live date for SR 2018 is 18 November All updates mentioned in this document will appear in the Standards MT User Handbook, which is due for publication on 20 July Related documentation Standards Release Guide December 2017 Schedule for Highlights The complete schedule can be found on 23 February

4 Summary of Updates 1 Summary of Updates For each update, the type of change is provided: Clarification: an update to further explain a section of the Standards Release Guide, such as an update to the text of a network validated rule, to avoid misinterpretation. Correction: an update to remove or modify a change made during the standards specification phase, for example, correction of details in a diagram. Note The User Handbook, to be published on 20 July 2018, will include corrections of typographical errors and editorial changes, which have no impact on implementation. Category Message Type Brief Description Type of change Category 1 MT 192, MT 196 Update documentation Correction Category 2 MT 292, MT 292 Update documentation Correction Category 3 MT 300, MT 304, MT 305, MT 306, MT 340, MT 360, MT 361, MT 380, MT 381 Update usage rules Correction Category 5 MT 586 Update network validated rule Correction Category 7 MT 707 Update presence Correction Category 7 MT 754 Update optional structured format Correction All MT 198, MT 298, MT 398, MT 498, MT 598, MT 698, MT 798, MT 898, MT 998 Update documentation Correction 23 February

5 Updates by Category 2 Updates by Category 2.1 Category 1 Customer Payments and Cheques MT 192, update introductory text MT 196, update introductory text MT 198, update introductory text 2.2 Category 2 Financial Institution Transfers MT 292, update introductory text MT 296, update introductory text 23 February

6 Updates by Category MT 298, update introductory text 2.3 Category 3 Foreign Exchange, Money Markets, and Derivatives MT 300, index 13, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as 72 with code MT 304, index 15, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as 72 with code MT 305, index 26, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as72 with code MT 306, index 20, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as 72 with code MT 340, index 12, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as72 with code MT 360, index 19, field 77H, sequence A, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as72 with code MT 361, index 20, field 77H, sequence A, update usage rules 23 February

7 Updates by Category If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 39M as72 with code MT 380, index 27, field 22F, sequence C, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 94C as 70E with code /PSET/ followed by a two letter country code, for example :72:/PSET/:94C::COUN//TW MT 381, index 26, field 22F, sequence C, update usage rules If the "Offshore CNY Centre" is not Hong Kong, it can be specified in field 94C as 70E with code /PSET/ followed by a two letter country code, for example :72:/PSET/:94C::COUN//TW MT 398, update introductory text 2.4 Category 4 Collections and Cash Letters MT 498, update introductory text 2.5 Category 5 Securities Markets MT 586, Network Validated Rules, C14, update network validated rule This is a correction to the implementation of SR 2017 Change Request (CR) , which blocked the used of the new code RMDR with PORT as requested in CR The previous implementation of the network validated rule was too restrictive. With this update both change requests can be fully used. In sequence A, if field :23G::CANC/PORT is present or field :23G::NEWM/PORT is present, then field 95Q Subfunction in field 23G is PORT, then field 95Q is optional, otherwise it is not allowed (Error code(s): E12). Sequence A if Subfunction in field 23G is... Sequence A then field 95Q is... CANC/PORT Optional 23 February

8 Updates by Category Sequence A if Subfunction in field 23G is... Sequence A then field 95Q is... NEWM/PORT Any other value Optional Not allowed MT 598, update introductory text 2.6 Category 6 Commodities and Reference Data MT 698, update introductory text 2.7 Category 7 Documentary Credits and Guarantees MT 707, index 15, field 50, update presence Field 50 is impacted by network validation rule C1 in MT 707, which mandates at least 1 field to be present after field 22A. PRESENCE Optional Conditional (see rule C1) MT 754, index 6, field 73A, update optional structured format Square brackets were missing in the proposed structured format on lines 2-6 to indicate that additional information can optionally be added in Narrative. FORMAT Option A 6*35z (Narrative) 6*35x (Narrative) In addition to narrative text, the following line formats may be used: Line 1 /8c/[3!a13d][additional information] (Code)(Currency)(Amount)(Narrative) Lines 2-6 [//continuation of additional information] (Narrative) or [/8c/[3!a13d][additional information]] (Code)(Currency)(Amount)(Narrative) 23 February

9 Updates by Category MT 798, update introductory text 2.8 Category 8 Travellers Cheques MT 898, update introductory text 2.9 Category 9 Cash Management and Customer Status MT 998, update introductory text 2.10 Category n Common Group Messages There are no updates to the SRG 2018 for this category. 23 February

10 Legal Notices Legal Notices Copyright SWIFT All rights reserved. Disclaimer This publication constitutes advance information only and is not to be considered the final and complete standards documentation for the subject matter published herein. The information in this publication may change from time to time. You must always refer to the latest available version. SWIFT Standards Intellectual Property Rights (IPR) Policy - End-User License Agreement SWIFT Standards are licensed subject to the terms and conditions of the SWIFT Standards IPR Policy - End-User License Agreement, available at > About Us > Legal > IPR Policies > SWIFT Standards IPR Policy. Translations The English version of SWIFT documentation is the only official and binding version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: the SWIFT logo, SWIFT, SWIFTNet, Sibos, 3SKey, Innotribe, the Standards Forum logo, MyStandards, and SWIFT Institute. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners. 23 February

Message Usage Guidelines

Message Usage Guidelines Categories 3 and 6 MiFID II Delegated Act Article 59 Client Reporting For Standards MT November 2018 These usage guidelines provide information about Standards Categories 3 and 6 messages. In particular,