This document provides advance information on changes to the FIN error codes related to SWIFT gpi and also as part of the Standards Release 2018. This document is an extract of the FIN Error Codes manual available on the UHB Online. Changes are highlighted in this document. 22 December 2017
Table of Contents Table of Contents Preface... 3 1 Message Status... 4 2 Abort Reasons... 5 3 C, D, and E Codes Conditional Semantic Error Codes... 6 3.1 C Error Codes... 6 3.2 D Error Codes... 6 4 G Codes - Service-specific Validation... 7 5 T Error Codes... 8 6 U Codes User Header Validation... 9 Legal Notices... 11 22 December 2017 2
Preface Preface About this document This document provides advance information on changes to the FIN error codes related to SWIFT gpi and also as part of the Standards Release 2018. This document is an extract of the FIN Error Codes manual available on the UHB Online. Changes are highlighted in this document. Intended audience This document is for the following audience: users who wish to gain an understanding of the FIN service developers who need background information on elements of FIN Related documentation FIN Operations Guide FIN Service Description Message Format Validation Rules 22 December 2017 3
Message Status 1 Message Status 31 32 The message status is returned in field 431 of non-delivery warnings, undelivered message reports, and retrieved messages. Authorised by the copy service or the subscriber to a SWIFT service Sanctions Screening over SWIFT service subscriber and delivered Not authorised by the copy service or the subscriber to a SWIFT servicesanctions Screening over SWIFT service subscriber and aborted by the system 33 Copy message is aborted and not delivered to the copy service 34 35 37 38 Authorised by the copy service or the subscriber to a SWIFT service Sanctions Screening over SWIFT service subscriber but aborted by the system Not yet authorised/refused by the copy service or the subscriber to a SWIFT service Sanctions Screening over SWIFT service subscriber Authorised by the copy service or the subscriber to a SWIFT servicesanctions Screening over SWIFT service subscriber but no delivery attempted Authorised by the copy service or the subscriber to a SWIFT servicesanctions Screening over SWIFT service subscriber but one or more unsuccessful delivery attempts 22 December 2017 4
Abort Reasons 2 Abort Reasons The following codes are returned in field 432 of abort notifications and, for the FINCopy service, Message Refusals: 50-ZZ 99 is pre-defined as 'system error'. All other alphanumeric codes (combination of 0-9 and A-Z) are specific to each FINCopy service. Contact your respective service provider for the meaning of each code. Code S1 is used by the SWIFT screening services to indicate that the message has been aborted on request of the subscribing user or by the screening service.code S1 is used by the Sanctions screening service to indicate that the message has been aborted on request of the subscribing user. Note All undefined numeric codes are reserved for use by FIN. 22 December 2017 5
C, D, and E Codes Conditional Semantic Error Codes 3 C, D, and E Codes Conditional Semantic Error Codes Note 3.1 C Error Codes Where a natural language expression would be too difficult to synthesise or too long, a matrix is provided. The row and column headers identify the elements involved (for example, field tags, code words, letter options). Matrices should be read from left to right and from top to bottom. C29 MT 199 (SWIFT gpi) In field 79, if line 5 is present, then the currency code in line 5, subfield 3 and the currency code in field 79, line 4 must be the same. MT 586 In field 23G, if subfield 1 is RMDR, then subfield 2 must be PORT. 3.2 D Error Codes D94 MT 199 (SWIFT gpi) In field 79, line 2, presence of subfield 2 (reason code) depends on subfield 1 (Status) as follows: In field 79, line 2 If subfield 1 is. Then subfield 2 is. ACSC Not allowed ACSP Mandatory RJCT Not allowed Available. D95 MT 199 (SWIFT gpi) In field 79, presence of line 3 subfield 2 (forwarded to) depends on line 2, subfield 2 (reason code) as follows: In field 79 If line2, subfield 2 is present Then line 3, subfield 2 is. (See error code D94) and is. 000 Mandatory 001 Optional 002 Not allowed 003 Not allowed 004 Not allowed Available. 22 December 2017 6
G Codes - Service-specific Validation 4 G Codes - Service-specific Validation Miscellaneous Message Specific G06 G26 G27 G28 Available. MT 502 The following qualifiers and codes must only be sent by users that are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of the Funds CUG and that send the MT 502 with any of these listed qualifiers and codes will receive a NAK: Sequence B, ORDRDET, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM, SUBS, SWIF, SWIT) Sequence B, ORDRDET, field 22H, qualifier CAOP Sequence B, ORDRDET, field 98a, qualifier NAVD Sequence B, ORDRDET, field 92A, qualifier SWRT Sequence C, SETDET, field 22F, qualifier SETR, funds code (REDM, SUBS) MT 509 The following qualifiers and codes must only be sent by users that are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of the Funds CUG and that send the MT 509 with any of these listed qualifiers and codes will receive a NAK: Sequence B, TRADE, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM,SUBS, SWIF, SWIT) MT 515 The following qualifiers and codes must only be sent by users that are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of the Funds CUG and that send the MT 515 with any of these listed qualifiers and codes will receive a NAK: Sequence C, CONFDET, field 98a, qualifier NAVD Sequence C, CONFDET, field 92A, qualifier (BAKL, ENTF, NAVR) Sequence C, CONFDET, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM, SUBS, SWIF, SWIT) Sequence C, CONFDET, field 22H, qualifier (CAOP, ECIO, TSTA) Subsequence C2, FIA, field 90B, qualifier TSMT Subsequence D3, AMT, field 19A, qualifier (BAKL, ENTF, EUTR) Sequence D, SETDET, field 22F, qualifier SETR, funds code (REDM, SUBS) For more information about MTs 502, 509, and 515, see the Category 5 Message Reference Guide, Volume 1. Use of field tags 111 and 121 is restricted to the SWIFT gpi Closed User Group. Use of field tag 121 is also restricted to the SWIFT gpi Closed User Group with the exception of MT 103, MT 103 REMIT, MT 103 STP, MT 202, MT 202 COV, MT 205, and MT 205 COV, where field 121 is mandatory. A request for cancellation was received for this message. 22 December 2017 7
T Error Codes 5 T Error Codes T83 Code word error. Field 79, line 2, subfield 1 in MT 199 (SWIFT gpi).available. T84 Code word error. Field 79, line 2, subfield 2 in MT 199 (SWIFT gpi)available. 22 December 2017 8
U Codes User Header Validation 6 U Codes User Header Validation U00 Incorrectly formatted user header: field tags in block 3 are not in the correct order; or valid field tag is present in block 3 but the colon ":" is not present immediately after the 3-digit field tag; or closing bracket "}' is not present for block 3. This error code will also be generated if the user header contains an invalid field tag, or if there is no field tag after the starting bracket "{". 103 Service identifier 113 Banking priority 108 Message user reference 119 Validation flag 423 Balance checkpoint date and time 106 Message input reference 424 Related reference 111 Service type identifier 121 Unique end-to-end transaction reference 115 Addressee information 165 Payment release information receiver (for FINInform services) 433 Sanctions screening information for the receiver 434 Payment controls information for the receiver U01 U02 U03 U07 U08 U09 Bad bank priority. Bad message user reference. User Header is either incorrectly formatted, (for example, does not contain the correct combination of opening or closing brackets "{" "}" in the correct positions) or does not contain at least one of the valid message tags. User Header not authorised in system messages, except for MT 097 following MIRS implementation. Invalid syntax, format, code word in tag 119, or field tag 119 is missing. Special validation is undefined for this message type. User has used tag 119 in a message that is not a candidate for special processing. Sender or receiver is not part of the MT 103 REMIT Message User Group. U10 Invalid syntax, format, date, time in tag 423. U11 Invalid message input reference format in tag 106. U12 U13 Invalid syntax, or format, or incorrect order of field tags 111 and 121, or field 111 is present without field 121., or only one of the field tags 111 and 121 is present. Mandatory field tag 121 is missing from header block 3 of the message, or field 121 is used in a message where it is not allowed, or field tag 121 is incorrectly formatted. Field tag 121 22 December 2017 9
U Codes User Header Validation must be formatted as xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx where x is any hexadecimal character (lower case only) and y is one of 8, 9, a, or b. 22 December 2017 10
Legal Notices Legal Notices Copyright SWIFT 2017. All rights reserved. Disclaimer This publication constitutes advance information only and is not to be considered the final and complete 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. 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. 22 December 2017 11