Standards Release Guide

Transcription

1 Standards Standards MT November 2016 Standards Release Guide Updates to the 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 2016

2 Standards MT November 2016 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 MT 306, network s, C1 correct network MT 350, index 6, field 22C, sequence A correct letter option Category 4 Collections and Cash Letters Category 5 Securities Markets MT 564, index 62, fields 98J and 98K, sequence E change order of subfields MT 569, index 9, field 95a, sequence A1 remove a qualifier MT 569, index 31, field 95a, sequence C1 add a qualifier Category 6 Commodities, Syndications, and Reference Data MT 600, network s, C5 correct network MT 601, network s, C4 correct network MT 604, network s, C2 correct network MT 605, network s, C2 correct network MT 606, network s, C1 correct network MT 607, network s, C1 correct network MT 608, network s, C2 correct network MT 609, network s, C4 correct network MT 620, network s, C12 correct network Category 7 Documentary Credits and Guarantees Category 8 Travellers Cheques Category 9 Cash Management and Customer Status Category n Common Group Messages...11 Legal Notices Updates to the Standards Release Guide

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

4 Standards MT November 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, 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 Standards MT User Handbook, to be published on 22 July 2016, will include corrections of typographical errors and editorial changes, which have no impact on implementation. Category Message Type Brief Description Type of change Category 3 MT 306 Correct network Correction Category 3 MT 350 Correct network in field 22C Correction Category 5 MT 564 Change format of field 98J and field 98K Correction Category 5 MT 569 Remove a qualifier Correction Category 5 MT 569 Add a qualifier Correction Category 6 MT 600 Correct network Correction Category 6 MT 601 Correct network Correction Category 6 MT 604 Correct network Correction Category 6 MT 605 Correct network Correction Category 6 MT 606 Correct network Correction Category 6 MT 607 Correct network Correction Category 6 MT 608 Correct network Correction Category 6 MT 609 Correct network Correction Category 6 MT 620 Correct network Correction 4 Updates to the Standards Release Guide

5 Updates by Category 2 Updates by Category 2.1 Category 1 Customer Payments and Cheques 2.2 Category 2 Financial Institution Transfers 2.3 Category 3 Foreign Exchange, Money Markets, and Derivatives MT 306, network s, C1 correct network Update the network C1: This rule is present in order to prevent the use of the MT 306 for plain vanilla options. The MT 305 must be used for those options until further notice. In sequence A, if field 12F contains the code VANI, then at least one of the following is required - field 17A with code Y or field 17F must contain the with code Y or sequence I is present. Both fields may contain the code Y. Therefore, the only allowed combination of codes in fields 17A and 17F, with the code VANI in field 12F, are as follows (Error code(s): D24): if field 12F is... then field 17A is... and field 17F is... VANI N Y VANI Y N VANI Y Y MT 350, index 6, field 22C, sequence A correct letter option Replace 37J with 37M in the following sentence in the network s: Party Suffix 1 and Party Prefix 2 are separated by four digits, which must consist of the rightmost non-zero digit of field 37JM in sequence B, preceded by the three digits to the left of it. If there are no digits to the left of it, the space must be zero filled (Error code(s): T22). 2.4 Category 4 Collections and Cash Letters 26 February

6 Standards MT November Category 5 Securities Markets MT 564, index 62, fields 98J and 98K, sequence E change order of subfields Move free format subfield (Identifier Code in 98J and Proprietary Code in 98K) to end of field, remove the double slash, insert a single slash after subfield Time: Option J :4!c/4!a2!a2!c[3!c]//8!n6!n/4!a2!a2!c[3!c] (Qualifier)( Identifier Code)(Date)(Time)(Identifier Code) Option K :4!c/8c/34x//8!n6!n/34x (Qualifier)(Data Source Scheme) (Proprietary Code)(Date)(Time) (Proprietary Code) MT 569, index 9, field 95a, sequence A1 remove a qualifier Remove the qualifier CLPB intended for the client of party B. Order M/O Qualifier R/N R Options Qualifier Description 1 M PTYA N P, Q, or R Party A or CLPA N P, Q, or R Party A's client or CLPB N P, Q, or R Party B's client or TRAG N P, Q, or R Triparty Agent 2 O ALTE N L Alternate ID MT 569, index 31, field 95a, sequence C1 add a qualifier Add the qualifier CLPB to identify the client of party B. Order M/O Qualifier R/N R Options Qualifier Description 1 M PTYB N P, Q, or R Party B 2 O CLPB N P, Q, or R Party B's client 2 3 O TRAG N P, Q, or R Triparty Agent 3 4 O ALTE N L Alternate ID 6 Updates to the Standards Release Guide

7 Updates by Category 2.6 Category 6 Commodities, Syndications, and Reference Data MT 600, network s, C5 correct network Update network C5: The use of FOZ, GOZ and TOZ in subfield Unit in sequences B and C, field 32F depends on the commodity in subfield Type in sequence A, field 26C as follows (Error code(s): D07). if Type in field 26C is... Sequence B then Unit in field 32F must be... Sequence C and Unit in field 32F must be MT 601, network s, C4 correct network Update network C4: The use of FOZ, GOZ and TOZ in subfield Unit in sequence A, field 32F depends on the commodity in subfield Type in sequence A, field 26C as follows(error code(s): D07). if Type in field 26C is... then Unit in field 32F must be February

8 Standards MT November MT 604, network s, C2 correct network Update network C2: The use of FOZ, GOZ and TOZ in subfield Unit in field 32F depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07). if Type in field 26C is... then Unit in field 32F must be MT 605, network s, C2 correct network Update network C2: The use of FOZ, GOZ and TOZ in subfield Unit in field 32F depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07). if Type in field 26C is... then Unit in field 32F must be... 8 Updates to the Standards Release Guide

9 Updates by Category MT 606, network s, C1 correct network Update network C1: The use of FOZ, GOZ and TOZ in subfield Unit in field 32F depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07). if Type in field 26C is... then Unit in field 32F must be MT 607, network s, C1 correct network Update network C1: The use of FOZ, GOZ and TOZ in subfield Unit in field 32F depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07). if Type in field 26C is... then Unit in field 32F must be MT 608, network s, C2 correct network Update network C2: The use of FOZ, GOZ and TOZ in subfield Unit in fields 60a, 62a, 64, and 65 depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07): 26 February

10 Standards MT November 2016 if Type in field 26C is... then Unit in fields 60a, 62a, 64 and 65 must be MT 609, network s, C4 correct network Update network C4: The use of FOZ, GOZ and TOZ in subfield Unit in field 68a depends on the commodity in subfield Type in field 26C as follows (Error code(s): D07). if Type in field 26C is then Unit in field68a must be MT 620, network s, C12 correct network Update network C12: The use of FOZ, GOZ and TOZ in subfield Unit in sequence B, fields 32F, 32R and 34J and in sequence G, field 33J of subsequence G1 and field 33J of subsequence G2 depends on the commodity in subfield Type in field 26C, in sequence A, as follows (Error code(s): D07): 10 Updates to the Standards Release Guide

11 Updates by Category if Type in field 26C is... Sequence B then Unit in fields 32F, 32R, and 34J must be... Subsequence G1 and Unit in field 33J must be... Subsequence G2 and Unit in field 33J must be... Neither GOZ nor TOZ Neither GOZ nor TOZ Neither GOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ GOZNeither FOZ nor TOZ 2.7 Category 7 Documentary Credits and Guarantees 2.8 Category 8 Travellers Cheques 2.9 Category 9 Cash Management and Customer Status 2.10 Category n Common Group Messages 26 February

12 Standards MT November 2016 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, Accord, 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. 12 Updates to the Standards Release Guide