Messaging

FIN

Error Codes
This reference guide lists the error codes and abort notifications returned by FIN in case of message validation errors or other conditions such as protocol violations or delivery issues.

23 July 2010

FIN

Table of Contents
Preface.................................................................................................................................................... 4 About this document ........................................................................................................................... 4 Audience ............................................................................................................................................. 4 Significant changes............................................................................................................................. 4 Chapter 1 Introduction ............................................................................................................................ 6 Chapter 2 Numeric Codes ...................................................................................................................... 7 2.1 General ......................................................................................................................................... 7 2.2 Logout/Quit Acknowledgement Errors .......................................................................................... 7 2.3 Re-Login Request Errors .............................................................................................................. 7 2.4 Retrieval Errors ............................................................................................................................. 8 2.5 Message Status .......................................................................................................................... 10 2.6 Abort Reasons ............................................................................................................................ 12 2.7 FIN and General Purpose Application Session Termination....................................................... 13 2.8 Report Errors .............................................................................................................................. 14 2.9 Bulk Retrieval Errors Codes........................................................................................................ 14 Chapter 3 Alphanumeric Codes............................................................................................................ 16 3.1 General ....................................................................................................................................... 16 3.2 A Codes - Abort at Application-Interface Level ........................................................................... 16 3.3 A Codes - Re-select Error Codes ............................................................................................... 17 3.4 B Codes - Copy Service Errors................................................................................................... 17 3.5 C, D and E Codes - Conditional Semantic Error Codes ............................................................. 18 3.6 G Codes - Service-specific Validation....................................................................................... 167 3.7 H Codes - Basic Header and Application Header Validation .................................................... 169 3.8 K Codes - Code Words Validation in Generic Fields ................................................................ 170 3.9 L Codes - LOGIN Errors ........................................................................................................... 171 3.10 M Codes - Message Errors ..................................................................................................... 171 3.11 P Codes - Protocol Errors ....................................................................................................... 172 3.12 R Codes - Re-login/Re-select Errors ...................................................................................... 173 3.13 S Codes - System-initiated Abort Errors ................................................................................. 173 3.14 S Codes - Select Errors .......................................................................................................... 174 3.15 T Codes - Text Validation ....................................................................................................... 175 3.16 U Codes - User Header Validation.......................................................................................... 191 3.17 U Codes - User Abort Codes .................................................................................................. 191

Error Codes

Table of Contents

3.18 V Codes - System Message Errors and Message Block Format Errors ................................. 192 3.19 X Codes - FINCopy Message Validation (01 - 27) and Delayed NAK Error Codes (30 - 99) . 195 3.20 Y Codes - UNK Error Codes ................................................................................................... 196 3.21 Z Codes - Trailer Validation .................................................................................................... 196 Legal Notices ...................................................................................................................................... 198

23 July 2010

FIN

Preface
About this document
This reference guide lists the error codes and abort notifications returned by FIN in case of message validation errors or other conditions such as protocol violations or delivery issues.

Audience
This book describes the FIN Error Codes. It should be read by: users who wish to gain an understanding of the FIN service developers who need background information on elements of FIN The reader is expected to have an understanding of FIN messaging, which is described in the FIN Service Description and the FIN Operations Guide.

Significant changes
The following tables list all significant changes to the content of the FIN Error Codes since the 24 July 2009 edition. These tables do not include editorial changes that SWIFT makes to improve the usability and comprehension of the document. New information Addition of field 86A for MT 605 Addition of MTs 541, 543, 578, and 586 in Error Code C28 Addition of MT 707 in Error Code C71 Addition of MT 600 in Error Code D36 Addition of MT 321 in Error Code D92 Addition of MT 564 in Error Code E24 Addition of currency code EEK (Estonia) in Error Code E76 Addition of MT 620 in Error Codes T03, T04 Addition of MT 306 in Error Code T14 Addition of MT 600 in Error Code T47 New abort reason S76 New V codes for system messages errors when processing MT 047 (V69, V70, V71) and MT 077 (V72, V73, V74) Location Error Codes C05 Error Code C28 Error Code C71 Error Code D36 Error Code D92 Error Code E24 Error Code E76 Error Codes T03 and T04 Error Code T14 Error Code T47 Section 3.13, S Codes - System-initiated Abort Errors Section 3.18, V Codes - System Message Errors and Message Block Format Errors

Error Codes

Preface

Updated information BIC/BEI change. BIC now stands for business identifier code. The concept of BEI (business entity identifier) has been removed. Financial institution BIC replaces the former BIC concept. Non-financial institution BIC replaces the former BEI concept. Update text of Error Codes B01, C02, C50, C58, C59, C65, C80, C89, D29, D36, D56, D57, E03, E37, E41, E77, E78, E79, E80, E82, E84, E87, K17, M75, T39, U00, V62

Location Changes apply throughout the document

Section 3.4, B Codes - Copy Service Errors Section 3.5.1, C Error Codes Section 3.5.2, D Error Codes Section 3.5.3, E Error Codes Section 3.8, K Codes - Code Words Validation in Generic Fields Section 3.10, M Codes - Message Errors Section 3.15, T Codes - Text Validation Section 3.16, U Codes - User Header Validation Section 3.18, V Codes - System Message Errors and Message Block Format Errors

Error Codes C29, C38, C39, C41, C87, D07, D25, E99, H55 again available

Section 3.5.1, C Error Codes Section 3.5.2, D Error Codes Section 3.5.3, E Error Codes Section 3.7, H Codes - Basic Header and Application Header Validation

Deleted information Deletion of references to MTs 308, 645, 810, 812, 813, 820, 821, 822, and 823 Cancel feature deimplemented Deletion of message 03 Deletion of section 2.7 Message Cancellation Reasons Deletion of MT 535 in Error Code E58 Deletion of MT 535 in Error Code E59

Location Changes apply throughout the document Section 2.1, General Section 2.5, Message Status Chapter 2, Numeric Codes Error Code E58 Error Code E59

23 July 2010

FIN

Chapter 1 Introduction
The FIN error codes are divided into the following groups: Validation error codes Conditional semantic error codes Abort error codes All input messages are validated for syntax and semantic errors by the system. If there is an error, a validation error code is returned in the logical (negative) acknowledgement or in an MT 019 Abort Notification. Abort error codes give the reason why an application or the logical connection has been discontinued. They are generated following the recognition of a certain condition and not necessarily due to errors in a message. Abort error codes can come from the system or from a user's terminal. For reference purposes, the error codes have been placed in two chapters. Chapter 2, Numeric Codes, contains all the errors that are represented by two- or three-digit codes. Error codes in Chapter 3, Alphanumeric Codes, have the following format: <code><nn> where <code> is a letter designating the error type and <nn> identifies the particular error.

Error Codes

Chapter 2 Numeric Codes

Chapter 2 Numeric Codes

2.1 General
Numeric codes are used for: Logout/Quit Acknowledgement errors (field 401) Re-Login Request errors (fields 280, 331 and 333) Retrieval errors (field 421) Message status (field 431) Abort reasons (field 432) FIN and General Purpose Application session termination (field 443) Report errors (field 461)

2.2 Logout/Quit Acknowledgement Errors

The following error codes are returned in field 401 of Logout and Quit acknowledgements. Logout and Quit Commands are always positively acknowledged and the session (General Purpose Application or FIN) closed. However, one of the following error codes can be included in the acknowledgement. Incorrect time/day The Logout Command can include the time/day inhibitor which prevents the next Login occurring before the time/day specified. The time/day in the format DDHHMM cannot be more than 7 days after the current date. 02 Training trailer missing The trailer block is only present if the message is sent by a training logical terminal. If the Logout Command is sent from a training logical terminal, it must contain a Training trailer. 03 Input sequence number error Each message sent from a logical terminal has an input sequence number. The first message sent in the General Purpose Application will always have an input sequence number of 000001, whereas the first message sent in FIN will have an input sequence number value of the last input sequence number+1 sent from that logical terminal. This error will be returned in the acknowledgement of a Logout or Quit Command when the input sequence number of that command is incorrect.

01

2.3 Re-Login Request Errors

The following error codes are returned in fields 280, 331, and 333 of acknowledgements, session history reports, and daily check reports: Re-Login Request received while logical terminal is active on the Logical Terminal Control association

010

23 July 2010

FIN

011 012 013 014 015 016 017 019

Logical Terminal Control state error, unable to recover the logical terminal session Re-Login Request authentication failed Re-Login Request semantic error Re-Login Request format error Re-Login Request login request number is incorrect Multiple Re-Logins from user Re-Login Request received while the logical terminal is in unrecoverable state Re-Login Request, session recovery information: incorrect General Purpose Application session number Re-Login Request, session recovery information: incorrect input sequence number Re-Login Request, session recovery information: input sequence number-ACK greater than input sequence number Re-Login Request, session recovery information: input sequence number-ACK less than the lower bound Re-Login Request, session recovery information: incorrect output sequence number Re-Login Request, session recovery information: incorrect window size Re-Login Request, login and re-login protocol versions are not the same Re-Login Request, logical terminal does not belong to Sign Distinguished Name (DN) organisation Re-Login Request, the Live destination that owns the Test and Training destination does not belong to Sign Distinguished Name (DN) organisation

020 021

022

023 024 026 027

028

2.4 Retrieval Errors

The following codes are returned in field 421 of message retrievals: Message has no text block Message was encrypted and no key or the wrong key was supplied by the user

000 002

Error Codes

Chapter 2 Numeric Codes

003 004

Empty report (no messages found) Logical terminal is not authorised to retrieve the message, that is the requester is neither the sender nor the receiver of the original message Text lost due to Slice Processor recovery History lost due to Slice Processor recovery Target message is a retrieval report (MTs 021 or 023) Invalid MT received by Slice Processor pseudo logical terminal (system) Invalid <application-id> received by Slice Processor pseudo logical terminal (system) Invalid date in retrieval criteria tag (system) Invalid time in retrieval criteria tag (system) End daytime before start daytime Target message older than 124 days (for range retrieval, daytime used) <branch-code> is not 'XXX' Invalid destination for report (tag 102). The logical terminal must have the same destination as the sender of the retrieval request or be a SWIFT logical terminal, and must be enabled for the application in which the retrieval message is to be sent Invalid input retrieval by receiver or output retrieval by sender (only single message input reference/message output reference allowed) Invalid synonym retrieval (synonym is not sender or receiver of message) Unknown target logical terminal Request received at wrong Slice Processor (system) Could not retrieve message input reference in message output reference retrieval (system) No delivery attempt in message input reference retrieval by receiver On-line text read error (system) On-line history read error (system)

005 006 007 010 011 012 013 014 015 016 018

019

020 021 022 023 032 033 034

23 July 2010

FIN

035 036 037 038 040 041 043

Text read error from archival (system) History read error from archival (system) Partial report - major system recovery in progress Unable to retrieve text and history from archival because of system problems The limits for group retrieval (99 messages in one request) have been exceeded Message could not be decrypted (system) The logical terminals in the beginning message input reference/message output reference and the ending message input reference/message output reference in a range retrieval request are not the same, in tag 252 (message input reference range) or 254 (message output reference range) Illogical use of field 152 <1st-isn> or field 153 <1st-osn>. input sequence number or output sequence number already included as component in message input reference(s) or message output reference(s) Message text not retrievable (message not successfully delivered) Off-line retrieval not allowed for Test and Training messages The text of local test mode messages is not retrievable Retrieval message too long Retrieval period specified exceeds 10 days Retrieval report problem. Contact your Customer Support Centre

044

045 046 047 048 049 099

2.5 Message Status

The message status is returned in field 431 of non-delivery warnings, undelivered message reports, and retrieved messages. Delivered Rejected by destinee Aborted

01 02 04

10

Error Codes

Chapter 2 Numeric Codes

07 08 10

No delivery attempt One or more unsuccessful attempts Message not delivered (that is no delivery history) for one of the following reasons: Message negatively acknowledged on input Message is Login, Select, Quit or Logout Request Message was sent in local test mode (not deliverable) Message is MT 097 (processed directly by Slice Processor and never delivered to any logical terminal, and so does not have a delivery history)

12 31 32 33 34 35 37 38 41 44 47 48 49 50-99

Intercepted Authorised by the copy service server and delivered Not authorised by the copy service server and aborted by the system Copy message is aborted and not delivered to the copy service server Authorised by the copy service server but aborted by the system Not yet authorised/refused by the copy service server Authorised by the copy service server but no delivery attempted Authorised by the copy service server but one or more unsuccessful delivery attempts Copy service bypassed and message delivered Copy service bypassed but message aborted by the system Copy service bypassed but no delivery attempted Copy service bypassed but one or more unsuccessful delivery attempts Refused by central institution. Abort notification MT 019 contains an alphanumeric abort code These codes are specific to each FINCopy service. Contact your respective service provider for the meaning of each code within the range 50-99. For Euro Banking Association (EBA) Processing, only the following codes are used: 70 Refusal from the Clearing Computer, and delivery aborted; the Sender of the payment message should also receive an MT 998 / SMT n75 Error Message from the Clearing Computer giving further reasons for the refusal.

23 July 2010

11

FIN

71

Refusal from the Clearing Computer because of a message format error that prevented normal processing, and delivery aborted.

99

System error

2.6 Abort Reasons

The following codes are returned in field 432 of abort notifications and, for the FINCopy service, Message Refusals: Message too old (remained undelivered for n days) Too many unsuccessful delivery attempts Destination disabled Operator aborted Message could not be recovered after a major system failure because it was user encrypted Message type incompatible with computer-based terminal mode Message is too old, but was authorised Too many delivery attempts, but message was authorised Destination is disabled, but message was authorised Message is too long, but was authorised Message is too old and was bypassed Too many delivery attempts and the message was bypassed Destination is disabled and the message was bypassed Message is too long and was bypassed Message is too old and was not authorised Copy message to the copy service server was aborted FINCopy service parameter(s) incorrectly defined in FIN

01 02 03 04 05 06 11 12 13 14 21 22 23 24 32 33 35

12

Error Codes

Chapter 2 Numeric Codes

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.

Note:

All undefined numeric codes are reserved for use by FIN.

2.7 FIN and General Purpose Application Session Termination

The following codes are returned in field 443 of Service Message 12 and Service Message 14 (for further details see the FIN System Messages): Normal termination Application Control or Logical Terminal Control has aborted Application Control or Logical Terminal Control has terminated normally System timed out message output reference ACK QUIT or LOGOUT received while outstanding input messages Input message/Service message after reception of a QUIT or LOGOUT Input window violation (more outstanding input messages than window size) System timed out on association establishment Reception of a SELECT from a logical terminal that already has a FIN session Association establishment request failed authentication Message output reference ACK Basic Header error Too many messages input in a session. Maximum is 500000. Too many messages output in a session. Maximum is 500000. Message output reference ACK from wrong synonym As for 052 but due to receipt of a Re-Login Request, rather than a Login Request As for 052 but on a different Regional Processor

000 001 002 004 006 007 008 009 010 011 014 015 016 020 025 051

23 July 2010

13

FIN

052

Reception of a login from a logical terminal for which the system has already processed a login transmitted over a different Logical Terminal Control on the same Regional Processor. The existing session is aborted and the new session established. SELECT with bad text block AP ABORT REQUEST with bad text block

053 054

2.8 Report Errors

The following codes are returned in field 461 of Delivery Subset Status Reports and Undelivered Message Reports: Empty report End of undelivered report System undergoing major recovery or system not completely synchronised yet Too many undelivered messages User on fall back Regional Processor, cannot generate report System internal problems, contact your Customer Support Centre

001 002 003 004 005 099

2.9 Bulk Retrieval Errors Codes

The following codes are returned in field 144 of Bulk Retrieval Responses (MT 025): Retrieval only partially complete Invalid <start-date-time> Invalid <end-date-time> Invalid retrieval time range Retrieval aborted due to system error Retrieval aborted due to communication error Retrieval aborted by SWIFT

03 11 12 13 14 15 16

14

Error Codes

Chapter 2 Numeric Codes

19

Retrieval complete The text of messages that were sent to the retrieving BIC more than 124 days ago cannot be retrieved. If those messages were received by the retrieving BIC less than 124 days ago, the file contains the message output reference of the history and the message input reference of the text.

20 21 22

Retrieval aborted due to system error (Test and Training destination - attempt to use tape) Retrieval aborted due to system error (FIN/FIN Bridge key error) Retrieval aborted due to system error (missing master BIC)

23 July 2010

15

FIN

Chapter 3 Alphanumeric Codes

3.1 General
This chapter contains the codes for the following error types: Code A A B C C, D and E G H K L M P Error Type Abort at Application Interface Level Errors Re-select Errors Copy Service Errors Dialout Errors Conditional Semantic Errors Service-specific Validation Errors Basic Header and Application Header Validation Errors Code Words Errors in Generic Fields LOGIN Errors Message Errors Protocol Errors R S S T U U V X Y Z Code Error Type Re-login/Re-select Errors System-initiated Abort Errors Select Errors Text validation (Block 4) Errors User Header Validation Errors User Abort Errors System Message or Message Block Format Errors Delayed NAK Errors and FINCopy Service Message Refusals User Negative Acknowledgement Errors Trailer Validation Errors

Note: Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.

3.2 A Codes - Abort at Application-Interface Level

These codes are in the format Ann, where 'nn' is copied from the last two characters in an AI-ABORT indication:

Note: Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.
A01 A02 A03 A04 A05 Application interface congestion at association time Duplicate source reference for the same pair of transport service access points Mismatched references Protocol error Application entity not attached to application interface service access point

16

Error Codes

Chapter 3 Alphanumeric Codes

A06 A07 A08 A16 A53 A57 A59 A60 A61 A90

Unknown application interface service access point Unknown association reference Unauthorised access to a dedicated Public Switched Telephone Network (PSTN) port Two Logical Terminal Control associations for same connection Data in invalid association state DISASSOCIATE in invalid association state CONFIRM in invalid association state Unknown application interface data protocol unit User-initiated application interface close In General Purpose Application , this indicates any application interface error In FIN, unexpected CLOSE of transport connection

A99

In General Purpose Application , this indicates any application interface error In FIN, unexpected CLOSE of transport connection

3.3 A Codes - Re-select Error Codes

A56 Re-select NAK error code (in field tag 503) to indicate that the logical terminal is not in a recoverable state. The computer-based terminal should execute a fresh select procedure.

3.4 B Codes - Copy Service Errors

Note: Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.
B01 Message contains Value-Added Service server id but sender or receiver, or both, are not members of the service. Available. 103:LCH is present in the message but the sender, or receiver, or both, are not activated on Accord, or the message is not allowed for LCH. or

B02 B03

23 July 2010

17

FIN

103:TPS is present in the message but the sender is not a member of TPS, or the message is not allowed for TPS. or 103:DER is present in the message but the sender, or the receiver, or both are not members of DER, or the message is not allowed for DER. B04 B05 Available. Either a system error has occurred, in which case, the user should contact its local Customer Support Centre for further information or it was not possible to generate a copy message as none of the fields to be copied were present in the original message.

3.5 C, D and E Codes - Conditional Semantic Error Codes

Note
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. The following abbreviations are used: M = Mandatory (must be present) O = Optional (may be present) U = Unauthorised (must not be present) Y = Yes (is present) N = No (is not present) NA = Not applicable

3.5.1 C Error Codes

C00 C01 Not used. MTs 102, 104 and 107 If field 19 is present in sequence C, then it must equal the sum of the amounts in all occurrences of field 32B in sequence B. MTs 201, 203, 204 and 559 The amount in field 19 must equal the sum of the amounts in all occurrences of field 32B or 34A. MT 256 If field 19 is present in sequence C, then it must equal the sum of the amounts in all occurrences of field 32J in sequence B.

18

Error Codes

Chapter 3 Alphanumeric Codes

MT 824 Field 19 at the completion of each outer repetitive sequence must equal the sum of the products of subfields 1 and 3 in all occurrences of field 68A from its respective inner repetitive sequence(s). C02 The currency code must be the same for all occurrences of indicated fields in the entire message. See the SWIFT Standards Category volumes for the indicated fields in each message. Examples: The following list explains how Error code C02 is applied in specific message types: MT 321. The currency code in the amount fields (fields 19A in sequence B) must be the same for all occurrences of this field in the message. MTs 320 and 330. The currency code in the amount fields, except for fields 33B and 33E in sequence G, must be the same for all occurrences of these fields in the message. MT 350. The currency code in the amount fields 32B and 34B in sequence B must be the same. Special Cases: The following MTs apply Error code C02 in an exceptional manner (for example, either based on the presence of another field OR individually to separate groups of fields within the MT): MTs 103 and 103+. If field 71G is present, the currency code in the fields 71G and 32A must be the same. MTs 104 and 107. The currency code in fields 32B and 71 G in sequences B and C must be the same for all occurrences of these fields in the message. The currency code in field 71F in sequences B and C must be the same for all occurrences of this field in the message. MT 320. The currency codes in the amount fields 32B, 32H, and 34E in sequence B, and field 71F in sequence H, must be the same. MT 620. If field 32H is present, then the currency code must be the same as the currency code in field 32B.

C03

The number of decimal digits in the amount component is checked against the maximum allowed for the corresponding currency. This check is mostly applied to fields containing both the amount and the currency code components. Examples: field 32A in MT 103, and in MT 256, sequence C field 32B in MTs 104 and 107, sequences B and C This check also applies, among others, to: field 19 in MTs 102, 104, 107, 201, 203, 204 and 559 where the corresponding currency is the one used in field 32B or 34A field 19 in MT 405 where the corresponding currency is the one used in field 32a field 19 in MT 824 where the corresponding currency is the one used in corresponding occurrences of field 68A field 32J in sequence B, and to field 19 in sequence C, in MT 256 where the corresponding currency is the one used in field 32A

23 July 2010

19

FIN

field 33B in MT 103, and in MTs 104 and 107, sequence B field 71F in MT 103, and in MTs 104 and 107, sequences B and C field 71G in MT 103, and in MTs 104 and 107, sequences B and C field 72 Reject/Return in MT 103, and in MTs 104 and 107, sequence A

Note: Error code C03 should be applied only to field 68A in MT 824 if subfield 5 is present.
C04 MTs 503, 504 and 506 In sequence B, if field :19B::TEXA is not present, then field :19B::TCRL is mandatory; otherwise field :19B::TCRL is optional. Sequence B If field :19B::TEXA is ... Not present Present C05 Then field :19B::TCRL is ... Mandatory Optional

Identifier Code must be a financial institution BIC. This error code applies to all types of BICs referenced in a FIN message, including SWIFT BICs, Non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations. See the table below for the list of MTs affected. MT 101 Field 52A 56A 57A 102 52A 53A 54A 57A 103 52A 53A 54A 55A 56A 57A The same validation applies to the generic MT 103 without tag 119, and other variants, such as the MT 103 REMIT and the MT 103+ Sequence(s) A, B B B A, B C C B The same validation applies to the generic MT 102 without tag 119, and the MT 102+ Qualifier Comments

20

Error Codes

Chapter 3 Alphanumeric Codes

MT 104

Field 52A 53A 57A

Sequence(s) A, B C B

Qualifier

Comments The same validation applies to the generic MT 104 without tag 119, and the MT 104 RFDD

Note: For sequence C, see Error code C96.

107

52A 53A 57A

A, B C B

110

52A 53A 54A

111, 112 200, 201 202, 203

52A 56A 57A 52A 53A 54A 56A 57A 58A

202 COV

52A 53A 54A 56A 57A 58A 52A 56A 57A

A A A A A A B B B B A A

204

53A 57A 58A

23 July 2010

21

FIN

MT 205

Field 52A 53A 56A 57A 58A

Sequence(s)

Qualifier

Comments

205 COV

52A 53A 56A 57A 58A 52A 56A 57A

A A A A A B B B A A A B B B

207

51A 52A 52G 56A 57A 58A

210

52A 56A

256 300

57A 53AJ 56AJ 57AJ

C B1, B2, D B1, B2, D B1, B2, D D1, D2, D3 D1, D2, D3 D1, D2, D3 B, E B, E B, E

303

53AJ 56AJ 57AJ

304

53AJ 56AJ 57AJ

22

Error Codes

Chapter 3 Alphanumeric Codes

MT 305

Field 53A 56A 57A

Sequence(s)

Qualifier

Comments

306

53AJ 56AJ 57AJ 84AJ 86AJ

C, E, J C, E, J C, E, J B C, E, J B3a D1 C, D, E, F, I C, D, E, F, I C, D, E, F, I C, D, E, F, I C1 C, D, E, F C, D, E, F C, D, E, F C, D, E, F C, D, F C, D, F C, D, F C, D, F C C C C D, G, L, M D, G, L, M D, G, L, M D, G, L, M CDEA INT2 INTE ACCW CDEA INTE ACCW CDEA INTE ACCW

307

95P 95P

320

53AJ 56AJ 57AJ 86AJ

321 330

95P 53AJ 56AJ 57AJ 86AJ

340

53AJ 56AJ 57AJ 86AJ

341, 350

53AJ 56AJ 57AJ 86AJ

360

53A 56A 57A 86A

23 July 2010

23

FIN

MT 361

Field 53A 56A 57A 86A

Sequence(s) D, G, J, K, L, M D, G, J, K, L, M D, G, J, K, L, M D, G, J, K, L, M C, E C, E C, E C, E L, M L, M L, M L, M J, K, L, M J, K, L, M J, K, L, M J, K, L, M

Qualifier

Comments

362

53A 56A 57A 86A

364

53A 56A 57A 86A

365

53A 56A 57A 86A

400

52A 53A 54A 57A 58A

405

52A 53A 56A 57A

A, B B3, C B3, C B A

416 450, 455, 456 502 504

53A 52A

95P 95P

C2 C2a1, E1

ACCW PAYE ACCW PAYE

24

Error Codes

Chapter 3 Alphanumeric Codes

MT 505 507 513 514 515 516 518 528, 529 540, 541, 542, 543, 544, 545, 546, 547 559 566 578 582

Field 95P 95P 95P 95P 95P 57A 95P 95P 95P

Sequence(s) B2a1, D1 B1b1 D2 C2 D2 B C2 C2 E2

Qualifier ACCW PAYE ACCW PAYE ACCW PAYE ACCW PAYE ACCW PAYE

Comments

ACCW PAYE ACCW PAYE ACCW PAYE

57A 95P 95P 56A 57A D2a E2 B B B5b E1 B B, C B, C B, C B, C ACCW PAYE ACCW ACCW ACCW PAYE

586 588 600

95P 95P 53A 56A 57A 86A 87A

601

53A 56A 57A

23 July 2010

25

FIN

MT 604

Field 56A 82A 86A 87A 88A

Sequence(s)

Qualifier

Comments

605

82A 86A 87A 88A

606

82A 87A 88A

607

82A 87A

620

53AJ 56AJ 57AJ 86AJ

C, D, E, F C, D, E, F C, D, E, F C, D, E, F B, C B C

643 644 646 700

57A 57A 57A 41A 42A 51A 53A 57A

705

41A 57A

707

52A

26

Error Codes

Chapter 3 Alphanumeric Codes

MT 710

Field 41A 42A 51A 52A 53A 57A

Sequence(s)

Qualifier

Comments

720

41A 42A 52A 57A

730, 734 740

57A 41A 42A 58A

742

52A 57A 58A

750 752

57A 53A 54A

754

53A 57A 58A

756

53A 54A

768, 769 800

57A 51A 52A 53A 54A

801

51A

23 July 2010

27

FIN

MT 802

Field 52A 53A 54A

Sequence(s)

Qualifier

Comments

824 900 910

51A 52A 52A 56A

985 n90 n91

57A 52A 52A 57A

C06

MT 210 Either field 50a or field 52a, but not both, must be present in a repetitive sequence. MTs 710 and 720 Either field 52a or field 50B, but not both, must be present. If field 52a is ... Present Not present MT 910 Either field 50a or field 52a, but not both, must be present. Not allowed Mandatory Then field 50B is ...

C07

MT 516 Either field 35A or 35N must be present.

C08 C09

Available. MT 430 In each occurrence of sequence A, if field 33a is present, then field 32a must be present.

C10

MT 422 At least one of the fields 72, 75 or 76 must be present.

C11

MT 400 If field 57a is present, fields 53a and 54a must be present.

28

Error Codes

Chapter 3 Alphanumeric Codes

C12

MTs 707 and 747 When field 32B or 33B is present, field 34B must be present. Conversely, when field 34B is present, either field 32B or field 33B must be present.

C13

MT 750 If any of fields 33B, 71B or 73 is present, field 34B must be present.

C14

MTs 559, 582 and 754 Either field 53a or 57a, but not both, may be present.

C15

MT 747 At least one of the fields 31E, 32B, 33B, 34B, 39A, 39B, 39C, 72 or 77A must be present.

C16

MT 707 If field 23 is present, field 52a must be present.

C17

MT 734 If field 73 is present, field 33a must be present.

C18

MT 752 If fields 32B and 71B are present, field 33a must be present.

C19

MT 754 Either field 72 or field 77A, but not both, may be present.

C20

MT 601 Field 53a may be present only if field 34P is present.

C21

MT 506 If sequence C is not present, then sequence D is mandatory. If one or more occurrence of sequence C is/are present, then sequence D is optional. If sequence C is ... Not present Present (once or more) Mandatory Optional Then sequence D is ...

C22

MT 920 If field 12 contains 942, field 34F must be present in the same repetitive sequence.

C23

MTs 920 and 942 When only one field 34F is present, subfield 2 must not be used. When both fields 34F are present, subfield 2 of the first 34F must contain D, and subfield 2 of the second 34F must contain C. In MT 920, this applies to each repetitive sequence.

23 July 2010

29

FIN

C24

MT 940 If field 86 is present in any occurrence of the repetitive sequence, it must be preceded by a field 61.

C25

MT n92 Field 79 or a copy of at least any fields of the original message or both must be present. If field 79 is ... Present Not present Then copy of any field(s) of original message is ... Optional Mandatory (that is, minimum one field, any field)

Note: SWIFT does not validate the relationship between the copied fields and the original message, hence, any valid field is correct. The system will negatively acknowledge the MT n92 with Error code C25 if there is no more field after field 11S.
C26 MT 430 At least one of the optional fields 32a or 74 must be present. C27 MTs 940, 941, 942, 950, 970 and 972 The first two characters of the three-character currency code in fields 60F, 60M, 62F, 62M, 64, 65, 90C and 90D, in MTs 940, 941, 942, 950, 970 and 972, and field 34F in MT 942 must be the same for all occurrences of these fields. C28 MT 541, 543, 578 A value date must only be provided for cash/securities split settlement. That is, in any occurrence of subsequence E3, if value date field :98a::VALU is present, then in sequence E field :22F::STCO//SPST must be present, and settlement amount field :19A::SETT must be present in the same subsequence E3. In any occurrence of subsequence E3 if field :98a::VALU is ... Present Not present MT 544, 545, 546, 547 A value date must only be provided with an effective settlement amount, that is, in any occurrence of subsequence E3, if value date field :98a::VALU is present, then settled amount field :19A::ESTT must be present in the same subsequence. Subsequence E3 if field :98a::VALU is ... Present Not present Subsequence E3 then field :19A::ESTT is ... Mandatory Optional Sequence E then field :22F::STCO//SPST (with DSS not present) Mandatory Optional In the same occurrence of subsequence E3 and field :19A::SETT is ... Mandatory Optional

30

Error Codes

Chapter 3 Alphanumeric Codes

Note: MTs 544, 545, 546, and 547, see Network Validated Rule 287 (Error code E87). MTs 545 and 547, see Network Validated Rule 292 (Error code E92).
MT 586 A value date must only be provided for cash/securities split settlement. That is, in any occurrence of subsequence B5c, if value date field :98a::VALU is present, then in subsequence B5 field :22F::STCO//SPST must be present, and settlement amount field :19A::SETT must be present in the same subsequence B5c. In any occurrence of subsequence B5c if field :98a::VALU is ... Present Not present C29 C30 Available. MT 707 At least one of the fields 31E, 32B, 33B, 34B, 39A, 39B, 39C, 44A, 44E, 44F, 44B, 44C, 44D, 79 or 72 must be present. C31 MTs n95 and n96 Either field 79 or a 'copy of any field(s) of the original message to which this message relates', but not both, may be present. Subsequence B5 then field :22F::STCO//SPST (with DSS not present) is ... Mandatory Optional In the same occurrence of subsequence B5c and field :19A::SETT is ... Mandatory Optional

Note: SWIFT does not validate the relationship between the copied fields and the original message; hence any valid fields other than 79 are accepted.
C32 MTs 300, 303, 304, 306, 320, 330, 340, 350, 360, 361, 362, 364, 365, 405, 582, 600, 620, and 643 An optional sequence of fields was used. However, a field that is required (that is, indicated by an 'OR') or a field that is mandatory (that is, indicated by 'Mandatory in ...') within this sequence is missing. C33 MTs 768 and 769 If field 71B is present, field 32a must be present. C34 MT 769 Either field 33B or 39C, but not both, must be present. C35 MTs 643, 644, 646 and 649 Either field 21 or 29B must be present. C36 MTs 643 and 646 Subfield 2 (<DATE2>) of field 31F must be present in each occurrence of sequence B.

23 July 2010

31

FIN

C37

MT 577 Subfield 2 (<DATE2>) of field 67A must not be present.

C38 C39 C40

Available. Available. MT 920 The currency code must be the same for each occurrence of the indicated fields within each repetitive sequence.

C41 C42

Available. MT 824 The currency code in each of the fields 68A of a sequence of fields 68A preceding a field 19 must be the same.

C43

MT 646 Either field 32N or 33N must be present.

C44

MT 646 If fields 32N and 33N are present in sequence C, field 34a must be present in sequence C.

C45

MT 646 If field 23 contains REPRINC or PREPRINC, field 32N must be present in sequence C.

C46

MT 646 If field 23 contains INT, field 33N must be present in sequence C.

C47

MT 643 If field 23 contains LOAN/DRAWDOWN or FINARR/DRAWDOWN, sequence B must not be present.

C48

MT 643 If field 23 contains LOAN/RENEWAL or FINARR/RENEWAL, sequence B must be present.

C49

MT 456 If field 71B is present, the values in fields 32a and 33D must be different.

C50

MTs 540, 541, 542, and 543 If field 36B is present in minimum one occurrence of sequence A1, then the type of settlement transaction must be a pair-off or a turn-around, that is, sequence E field :22F::SETR//PAIR or :22F::SETR//TURN must be present.

32

Error Codes

Chapter 3 Alphanumeric Codes

In sequence A1 if field :36B: is ... Present

Then in sequence E field :22F::SETR must be ... :22F::SETR//PAIR and DSS must not be present or :22F::SETR//TURN and DSS must not be present NA

Not present C51 MT 643

If field 23 contains LOAN/DRAWDOWN or LOAN/RENEWAL, field 31R must be present. C52 C53 Available. MT 643 If field 71C is present in any sequence B, field 34a must be present in the same sequence. C54 MT 644 Either field 36 or field 37(A-F) must be present in any sequence B. C55 MT 644 In any sequence B, the currency code in fields 33B and 34a must be the same. C56 C57 Available. MT 646 If field 34N is present in any sequence B, field 31F in the same sequence B and field 33N in sequence C must be present. C58 MT 300 In field 77D of sequence A, if the code /VALD/ is present, then it must appear in the first 6 characters of the first line and in no other place, and it must be followed by a date expressed as YYYYMMDD and the "end_of_line" separator, that is, ":77D:/VALD/"YYYMMDD"CrLf". See rule 59. MT 304 In field 72 of sequence C, if the code /VALD/ is present, then it must appear in the first 6 characters of the first line and in no other place, and it must be followed by a date expressed as YYYYMMDD and the "end_of_line" separator, that is ":72:/VALD/"YYYMMDD"CrLf". See rule 59. MT 646 If field 34N is present in any sequence B, the total amount given in field 33N must equal the total amount of all occurrences of field 34N amounts in sequence B.

23 July 2010

33

FIN

C59

MT 300 In sequence A, if field 77D is present and if the first six (6) characters of the first line are equal to /VALD/, then the second line must be present and it must contain "/SETC/" in the first 6 characters, followed by a valid ISO 4217 currency code and the end of line separator, that is, "/SETC/"<CUR>"CrLf". Conversely, in sequence A, if field 77D is present, and the second line is present, and the first six (6) characters of the second line are equal to /SETC/, then the first six (6) characters of the first line must be equal to /VALD/. The code "/SETC/" is not allowed in other places than the first 6 characters of the second line. See rule 58. MT 304 In sequence C, if field 72 is present and if the first six (6) characters of the first line are equal to /VALD/, then the second line must be present and it must contain "/SETC/" in the first 6 characters, followed by a valid ISO 4217 currency code and the end of line separator, that is, "/SETC/"<CUR>"CrLf". Conversely, in sequence C, if field 72 is present, and the second line is present, and the first six (6) characters of the second line are equal to /SETC/, then the first six (6) characters of the first line must be equal to /VALD/. The code "/SETC/" is not allowed in other places than the first 6 characters of the second line. See rule 58. MT 321 In sequence B, the presence of field 19A and of the Next Interest Due Date (field :98A::INTR) depends on the Type of Loan/Deposit Event (field :22H::TLDE) in sequence A as follows: In sequence A if field :22H::TLDE Indicator is ... CONF ROLL MATU MT 800 The amounts in fields 34B and 32A must be the same. Sequence B then field :98A::INTR is ... Sequence B and field :19A::SETT is ... Sequence B and field :19A::RODI is ... Sequence B and field :19A::CINT is ... Sequence B and field :19A::NINT is ... Mandatory Mandatory Not allowed

Mandatory Mandatory Not allowed

Not allowed Mandatory Mandatory

Not allowed Optional Not allowed

Not allowed Optional Optional

C60

MT 307 In sequence A, the presence of field :22H::APER and the presence of field :22H::NEGR depend on the field :22H::CRTR as follows: In sequence A if field :22H::CRTR Indicator is ... ASET AFWD Sequence A then field :22H::APER is ... Not allowed Mandatory Sequence A and field :22H::NEGR is ... Optional Mandatory

34

Error Codes

Chapter 3 Alphanumeric Codes

MT 321 In sequence A, the presence of field :99B:: depends on the presence of field :22H::BLOC as follows: In sequence A if field :22H::BLOC is ... Present Not present MT 643 In each sequence B, the currency code in fields 32P, 33a and 34a must be the same. C61 MT 307 In sequence A, the presence of field :22H::PAFI depends on field :22H::APER as follows: In sequence A if field :22H::APER Indicator is ... OPEF NOPE Field :22H::APER not present MT 321 In sequence B, the presence of field :98A::LDFP depends on the value of field :22H::TLDE as follows: In sequence A if field :22H::TLDE Indicator is ... MATU Not MATU MT 643 In each sequence C, the currency code in fields 32B and 33B must be the same. C62 MT 307 The presence of sequence C depends on field :22H::APER as follows: In sequence A if field :22H::APER Indicator is ... OPEF NOPE Field :22H::APER not present MT 321 In sequence B, the presence of field :99B::DAAC depends on the presence of field :98A::LDFP as follows: Not allowed Mandatory Not allowed Then sequence C is ... Sequence B then field :98A::LDFP is ... Not allowed Optional Sequence A then field :22H::PAFI is ... Not allowed Mandatory Not allowed Mandatory Not allowed Sequence A then field :99B:: is ...

23 July 2010

35

FIN

In sequence B if field :98A::LDFP is ... Present Not present C63 MT 307 Mandatory

Sequence B then field :99B::DAAC is ...

Not allowed

In sequence A, the presence of the qualifier UNKN in field :22H::NEGR//UNKN depends on the content of field :22H::CRTR, of field :22H::APER and of field :22H::PAFI as follows: In sequence A if field :22H:: is ... CRTR//ASET CRTR//AFWD and APER//OPEF CRTR//AFWD and APER//NOPE and PAFI//PAIN CRTR//AFWD and APER//NOPE and PAFI//FINA MT 321 In sequence A, if field 99B is present, then all qualifiers must be present. C64 MT 307 The presence of sequence D depends on the value of field 22H as follows: In sequence A If field :22H::CRTR is ... ASET ASET ASET AFWD AFWD AFWD AFWD C65 MT 567 If the message is a cancellation request status (:23G::CAST), then, in every occurrence of sequence A2 Status, a cancellation processing status must be reported (:25D::CPRC...). And field :22H::APER is ... NA per rule 60 NA per rule 60 NA per rule 60 OPEF NOPE NOPE NOPE And field :22H::PAFI is ... NA per rule 61 NA per rule 61 NA per rule 61 NA per rule 61 PAIN FINA FINA And field :22H::NEGR is ... NETC GRSC Not present NETC or GRSC or UNKN NETC or GRSC or UNKN NETC GRSC Then sequence D is ... Not allowed Optional Optional Not allowed Then field :22H::NEGR//UNKN is ...

Optional Not allowed Not allowed Not allowed Not allowed Mandatory Not allowed

36

Error Codes

Chapter 3 Alphanumeric Codes

If the message is an instruction status (:23G::INST) then, in every occurrence of sequence A2 Status, an instruction processing status (:25D::IPRC...) must be reported. If the message is corporate action event processing status (:23G::EVST), then, in every occurrence of sequence A2 Status, an event status (:25D::EPRC...) must be reported. In sequence A if field 23G is ... CAST INST EVST C66 MT 643 The number of occurrences of sequence C must be equal to or greater than the number of occurrences of sequence B. C67 MT 516 In sequence A, either field 83C or 87a but not both, may be present. C68 MTs 202 COV and 205 COV In sequence B, if field 56a is present, then field 57a must also be present. C69 MT 507 In each occurrence of sequence B, if present, if subsequence B1 is present, the presence of subsequences B1a and B1b depends on the value of field :22H::COLL in sequence B as follows: In each occurrence of sequence B If subsequence B1 is ... And in sequence B field :22H::COLL//Status is ... CCOL SCOL BCOL (NA see Error code C70) Not present NA Then subsequence B1a is ... And subsequence B1b is ... Then, in every occurrence of sequence A2 Status, field :25D must be ... :25D::CPRC... :25D::IPRC... :25D::EPRC...

Present

Not allowed Mandatory NA

Mandatory Not allowed NA

NA

NA

Note:
C70 MT 507

Rule C70 takes precedence over rule C69.

In each occurrence of sequence B, the presence of subsequence B1 depends on the value of fields :25D::COLL//<Status> and :22H::COLL//<Indicator> as follows:

23 July 2010

37

FIN

In each occurrence of sequence B If field :25D::COLL/ [8c]/4!c Data Source Scheme [8c] is ... Not present And field :25D::COLL/[8c]/4!c is ... :25D::COLL//ACCT :25D::COLL//ACCT :25D::COLL//ACCT :25D::COLL//REJT Present NA And field :22H::COLL//4!c is ... BCOL CCOL SCOL NA BCOL CCOL SCOL
[1]

Then subsequence B1 is ... Not allowed Mandatory [1] Mandatory [1] Not allowed Not allowed Optional [1] Optional [1]

See Error code C69 for additional checks. Rule C70 takes precedence over rule C69.

C71

MTs 528 and 529 In sequence. B, field 36B::SETT cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence B if field :36B::SETT is ... Repeated Not repeated MT 535 In each occurrence of subsequence B1, field 93B::AGGR cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence B1 if field :93B::AGGR is ... Repeated Not repeated MT 536 In each occurrence of subsequence B1a2, field 36B::PSTA cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence B1a2 if field :36B::PSTA is ... Repeated Not repeated Then one occurrence of :36B::PSTA must be ... :36B::PSTA//FAMT NA And the other occurrence of :36B::PSTA must be ... :36B::PSTA//AMOR NA Then one occurrence of :93B:AGGR must be ... :93B::AGGR//FAMT and DSS must not be present NA And the other occurrence of :93B::AGGR must be ... :93B::AGGR//AMOR and DSS must not be present NA Then one occurrence of :36B::SETT must be ... :36B::SETT//FAMT NA And the other occurrence of :36B::SETT must be ... :36B::SETT//AMOR NA

38

Error Codes

Chapter 3 Alphanumeric Codes

MT 537 In each occurrence of subsequence B2b, field 36B::PSTA cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence B2b if field :36B::PSTA is ... Repeated Not repeated MTs 540, 541, 542, and 543 In each occurrence of sequence. C, field 36B::SETT cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence C if field :36B::SETT is ... Repeated Not repeated MTs 544, 545, 546, and 547 In each occurrence of sequence C, field 36B::ESTT cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence C if field :36B::SETT is ... Repeated Not repeated MT 548 In sequence. B, field 36B::SETT cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence B if field :36B::SETT is ... Repeated Not repeated MT 564 In each occurrence of subsequence B2, field 93B::ELIG cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence B2 if field :93B::ELIG is ... Repeated Not repeated Then one occurrence of :93B:ELIG must be ... :93B::ELIG//FAMT and DSS must not be present NA And the other occurrence of :93B::ELIG must be ... :93B::ELIG//AMOR and DSS must not be present NA Then one occurrence of :36B::SETT must be ... :36B::SETT//FAMT NA And the other occurrence of :36B::SETT must be ... :36B::SETT//AMOR NA Then one occurrence of :36B::ESTT must be ... :36B::ESTT//FAMT NA And the other occurrence of :36B::ESTT must be ... :36B::ESTT//AMOR NA Then one occurrence of :36B::SETT must be ... :36B::SETT//FAMT NA And the other occurrence of :36B::SETT must be ... :36B::SETT//AMOR NA Then one occurrence of :36B::PSTA must be ... :36B::PSTA//FAMT NA And the other occurrence of :36B::PSTA must be ... :36B::PSTA//AMOR NA

23 July 2010

39

FIN

MT 565 In subsequence B2, field 93B::ELIG cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence B2 if field :93B::ELIG is ... Repeated Not repeated MT 566 In sequence B, field 93B::ELIG cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence B if field :93B::ELIG is ... Repeated Not repeated MT 567 In sequence B, field 36B::STAQ or QREC cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence B if field :36B::STAQ or QREC is ... Repeated Then one occurrence of :36B:STAQ or QREC must be ... :36B::STAQ//FAMT or :36B::QREC//FAMT Not repeated MT 568 In sequence B, field 93B::ELIG cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Sequence B if field :93B::ELIG is ... Repeated Not repeated MT 584 In each occurrence of subsequence B2b, field 36B::TRAD cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Then one occurrence of :93B:ELIG must be ... :93B::ELIG//FAMT and DSS must not be present NA And the other occurrence of :93B::ELIG must be ... :93B::ELIG//AMOR and DSS must not be present NA NA And the other occurrence of :36B::STAQ or QREC must be ... :36B::STAQ//AMOR :36B::QREC//AMOR NA Then one occurrence of :93B:ELIG must be ... :93B::ELIG//FAMT and DSS must not be present NA And the other occurrence of :93B::ELIG must be ... :93B::ELIG//AMOR and DSS must not be present NA Then one occurrence of :93B::ELIG must be ... :93B::ELIG//FAMT and DSS must not be present NA And the other occurrence of :93B::ELIG must be ... :93B::ELIG//AMOR and DSS must not be present NA

40

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence B2b if field :36B::TRAD is ... Repeated Not repeated MT 707

Then one occurrence of :36B:TRAD must be ... :36B::TRAD//FAMT NA

And the other occurrence of :36B::TRAD must be ... :36B::TRAD//AMOR NA

If field 79 is present, it cannot appear more than twice (maximum 2 occurrences). C72 MT 537 In each occurrence of subsequence C2, field 36B::PSTA cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence C2 if field :36B::PSTA is ... Repeated Not repeated MT 564 In each occurrence of subsequence E1, field 36B::ENTL cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence E1 if field :36B::ENTL is ... Repeated Not repeated MT 565 In sequence. D, field 36B::QINS or QREC cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. When used with format option C, the qualifiers QINS and QREC cannot be repeated. Sequence if field :36B::QINS or QREC is ... Repeated Then one occurrence of :36B::QINS or QREC must be ... :36B::QINS//FAMT :36B::QREC//FAMT Not repeated NA And the other occurrence of :36B::QINS or QREC must be ... :36B::QINS//AMOR :36B::QREC//FAMT NA Then one occurrence of :36B::ENTL must be ... :36B::ENTL//FAMT NA And the other occurrence of :36B::ENTL must be ... :36B::ENTL//AMOR NA Then one occurrence of :36B::PSTA must be ... :36B::PSTA//FAMT NA And the other occurrence of :36B::PSTA must be ... :36B::PSTA//AMOR NA

Note:

Therefore the only valid repetitions are:

:36B::QINS//FAMT :36B::QINS//AMOR

or

23 July 2010

41

FIN

:36B::QREC//FAMT :36B::QREC//AMOR MT 566 In each occurrence of subsequence D1, field 36B::PSTA cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence D1 if field :36B::PSTA is ... Repeated Not repeated MT 584 In each occurrence of subsequence C1c, field 36B::TRAD cannot appear more than twice (maximum 2 occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR. Subsequence C1c if field :36B::TRAD is ... Repeated Not repeated C73 MT 536 A reference to the previously received message must be specified for each transaction reported, that is, in each occurrence of subsequence B1a Transaction, field 20C::RELA must be present in one and only one occurrence of subsequence B1a1 Linkages; field 20C::RELA is not allowed in all other occurrences of subsequence B1a1. MT 537 A reference to the previously received message must be specified for each transaction reported, that is, in each occurrence of subsequence B2 Transaction, field 20C::RELA must be present in one and only one occurrence of subsequence B2a Linkages; field 20C::RELA is not allowed in all other occurrences of subsequence B2a. MTs 544, 545, 546, 547, and 548 A reference to the previously received message must be specified, that is, field 20C::RELA must be present in one and only one occurrence of subsequence A1 Linkages; field 20C::RELA is not allowed in all other occurrences of subsequence A1. C74 MT 537 A reference to the previously received message must be specified for each transaction reported, that is, in each occurrence of sequence C Transaction, field 20C::RELA must be present in one and only one occurrence of subsequence C1 Linkages; field 20C::RELA is not allowed in all other occurrences of subsequence C1. Then one occurrence of :36B::TRAD must be ... :36B::TRAD//FAMT NA And the other occurrence of :36B::TRAD must be ... :36B::TRAD//AMOR NA Then one occurrence of :36B::PSTA must be ... :36B::PSTA//FAMT NA And the other occurrence of :36B::PSTA must be ... :36B::PSTA//AMOR NA

42

Error Codes

Chapter 3 Alphanumeric Codes

C75

MT 104 The presence of field 23E in sequence B, depends on the presence and content of field 23E in sequence A as follows: If field 23E is present in sequence A and contains RFDD, then field 23E must be present in all occurrences of sequence B. If field 23E is present in sequence A and does not contain RFDD, then field 23E must not be present in any occurrence of sequence B. If field 23E is not present in sequence A, then field 23E must be present in all occurrences of sequence B. Sequence A if field 23E is ... Present and = RFDD Present and not = RFDD Not present Sequence B if field 23E is ... Mandatory in all occurrences Not allowed Mandatory in all occurrences

Note:
C76 MT 104

See Error codes C94 and C96.

Field 50a (option A or K) must be present either in sequence A or in each occurrence of sequence B, but must never be present in both sequences, nor absent from both sequences. Sequence A if field 50a (option A or K) is ... Present Not present C77 MTs 730, 768 and 769 Either field 25 or field 57a, but not both, may be present. C78 MTs 730, 768 and 769 Either field 32D or field 57a, but not both, may be present. C79 MTs 305 and 601 Field 31C may be present only if subfield 3 of field 23 contains A. C80 MT 608 The commodity code must be the same for all occurrences of the indicated fields in the entire message. C81 MTs 103, 103+, 202, 202 COV (sequence A), 203, 205, 205 COV (sequence A) and 582 If field 56a is present, then field 57a must also be present. In every occurrence of sequence B, then field 50 (option A or K) is ... Not allowed Mandatory

23 July 2010

43

FIN

C82

MTs 104 and 107 In sequence A, if field 23E is present and contains RTND, then field 72 must be present. In all other cases (that is field 23E is not present, or field 23E does not contain RTND), field 72 is not allowed. Sequence A If field 23E is ... Present and = RTND Present and not = RTND Not present Mandatory Not allowed Not allowed Then field 72 is ...

C83

MT 935 Either field 23 or field 25, but not both, must be present in any repetitive sequence.

C84

MT 303 In sequence A, the presence of field 21 depends on field 22A as follows: Sequence A If field 22A is ... AMNA AMND CANC DUPL NEWT Mandatory Mandatory Mandatory Optional Optional Then field 21 is ...

C85

MT 609 Field 68B must be present when the immediately preceding field 23 contains SPOTS or FORWARDS.

C86

MT 609 Field 68C must be present when the immediately preceding field 23 contains OPTIONS.

C87 C88

Available. MT 305 The currency code in subfield 4 of field 23 must be the same as the currency code in field 32B.

C89

MTs 600, 601, 604, 605, 606, 607, 608 and 609 A maximum of 6 decimal digits is permitted in the following: field 32F in MTs 600, 601, 604, 605, 606 and 607; fields 60F, 60M, 61, 62F, 62M, 64 and 65 in MT 608; and subfield 6 of fields 68B and 68C in MT 609.

44

Error Codes

Chapter 3 Alphanumeric Codes

MT 620 A maximum of 6 decimal digits is permitted in the subfields "amount" of sequence B: field 32F, index 18, field 32R, index 19, field 34J, index 21, and of sequence G: field 33J, index 52, and field 33J, index 54. C90 MTs 700, 710, 720 and 740 If field 42a is used, the only combinations that are allowed are field 42M (on its own) or field 42P (on its own) or both fields 42C and 42(A or D). C91 MT 608 Subfield 4 of field 61 must not be present. C92 MT 303 Sequences B and C are mutually exclusive. Field 94A in sequence A specifies which type of transaction is allocated and thus which one of the two sequences must be present: Sequence A if field 94A is ... FORX FXOP C93 MT 600 Either sequence B or C, but not both, must be present. C94 MT 104 If field 23E in sequence A is present and contains RFDD, then field 119 of the User Header must be present and contain RFDD. If field 23E in sequence A is not present or does not contain RFDD, then field 119 of the User Header must not be present. Sequence A if field 23E is ... Present and = RFDD Present and not = RFDD Not present User Header then field 119 is ... Mandatory and must contain RFDD Not allowed Not allowed Then sequence B is ... Mandatory Not allowed Then sequence C is ... Not allowed Mandatory

Note:

This error code takes precedence over Error codes C75 and C96.

MTs 503, 504, 505, 506 and 507 The User Header is mandatory and must contain a field 119 with a valid code that is identical to that contained in subfield 2 of field :22a::COLA//4!c in sequence A.

Note:

The rule 94 must be applied even if the DSS is present in field :22F::COLA.

23 July 2010

45

FIN

C95

MT 303 In sequence C, the presence of field 30X depends on field 23B as follows: Sequence C If field 23B is ... CLAM or PTAM CLEU or PTEU Mandatory Not allowed Then field 30X is ...

C96

MT 104 If field 23E is present in sequence A and contains RFDD, then: field 21R in sequence A is optional fields 21E, 50a (option A or K), 52a, 71F and 71G must not be present in sequence B sequence C must not be present Otherwise, that is in sequence A, field 23E does not contain RFDD or field 23E is not present: in sequence A, field 21R must not be present and in sequence B, the fields 21E, 50a (option A or K), 52a, 71F and 71G are optional and sequence C must be present Sequence A If field 23E is ... Then field 21R is ... Sequence B And fields 21E, 50a (option A or K), 52a, 71F and 71G are ... Not allowed Optional Optional And sequence C is ...

Present and = RFDD Present and not = RFDD Not present

Optional Not allowed Not allowed

Not allowed Mandatory Mandatory

Note: 1. See Error codes D75, C94 and D80. 2. Error code C96 takes precedence over Error code D80.
C97 MT 303 The presence of sequence D depends on the value of field 22A in sequence A as follows: Sequence A if field 22A is ... AMNA, AMND, DUPL or NEWT CANC Mandatory Optional Then sequence D is ...

46

Error Codes

Chapter 3 Alphanumeric Codes

MT 504 The presence of sequence D is mandatory when in any occurrence of sequence C, subsequence C1 is present and subsequence C1a is not present: In sequence(s) C If in one or more occurrence(s) of sequence C: subsequence C1 is present and an internal subsequence C1a is not present Mandatory Then sequence D is ...

Note:
MT 505

See Error code D49.

The presence of sequence C is mandatory when in any occurrence of sequence B, subsequence B1 is present and subsequence B1a is not present: In sequence(s) B If in one or more occurrence(s) of sequence B: subsequence B1 is present and an internal subsequence B1a is not present Mandatory Then sequence C is ...

Note:
C98

See Error code D49.

MTs 306, 320, 330 , 340, and 620 In a sequence, field 15a may not be the only field, that is if field 15a is present, then at least one other field in the sequence must be present. The following lists the sequences per message type: Message type 306 320, 330 340 620 I H E H Sequence

C99

MT 303 In each occurrence of sequence D, the presence of subsequence D3 depends on field 94A of sequence A as follows: Sequence A if field 94A is ... FORX FXOP MT 504 Sequence E is mandatory when in any occurrence of sequence C, subsequence C2 is present and subsequence C2a is not present. Then subsequence D3 is ... Not allowed Mandatory

23 July 2010

47

FIN

In sequence(s) C If in one or more occurrence(s) of sequence C: subsequence C2 is present and an internal subsequence C2a is not present Mandatory

Then sequence E is ...

Note:
MT 505

See Error code D50.

Sequence D is mandatory when in any occurrence of sequence B, subsequence B2 is present and subsequence B2a is not present. In sequence(s) B If in one or more occurrence(s) of sequence B: subsequence B2 is present and an internal subsequence B2a is not present Mandatory Then sequence D is ...

Note:

See Error code D50.

3.5.2 D Error Codes

Note
Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.

D00 D01

Not used. MT 303 If subfield 1 of field 39P contains CURR, the number of decimal digits in subfield 3 is checked against the maximum allowed for the corresponding currency in subfield 2.

D02

MTs 304, 360, 361, 362, 364 and 365 In sequence A, the presence of field 21 depends on field 22A as follows: Sequence A If field 22A is ... AMND CANC DUPL NEWT Mandatory Mandatory Optional Optional Then field 21 is ...

48

Error Codes

Chapter 3 Alphanumeric Codes

MTs 306 and 340 In sequence A, the presence of field 21 depends on field 22A as follows: Sequence A If field 22A is ... AMND CANC NEWT MT 341 In sequence A, the presence of field 21 depends on field 22A as follows: Sequence A If field 22A is ... AMND CANC SETT MT 350 In sequence A, if field 22A contains ADVC, then field 21 is optional; otherwise field 21 is mandatory: Sequence A If field 22A is ... ADVC Not = ADVC D03 MT 304 In sequence A, the presence of fields 17O and 17N depend on field 94A as follows: Sequence A If field 94A is ... ASET AFWD Then field 17O is ... Not allowed Mandatory Then field 17N is ... Not allowed Mandatory Optional Mandatory Then field 21 is ... Mandatory Mandatory Optional Then field 21 is ... Mandatory Mandatory Optional Then field 21 is ...

Note:
MT 535

See also Error codes D04 and D29.

If field :94a:: is present in sequence B, then fields :93B::AGGR and :94a::SAFE are not allowed in any occurrence of subsequence B1b: Sequence B if field :94a: is ... Present Not present Then in any occurrence(s) of subsequence B1b, field :93B::AGGR and field :94a::SAFE are ... Not allowed Optional

23 July 2010

49

FIN

D04

MT 304 In sequence A, the presence of field 17F depends on field 17O as follows: Sequence A If field 17O is ... Y N Not present Not allowed Mandatory Not allowed Then field 17F is ...

Note:
MT 535

See also Error codes D03 and D29.

If field :93B::AGGR is present in subsequence B1b, then :field 94a::SAFE must be present in the same subsequence B1b: Sequence B1b if field :93B::AGGR is ... Present Not present D05 MT 535 In each occurrence of subsequence B1b, if field :93B::AVAI or/and :93B::NAVL is/are present, then :field :93B::AGGR must be present in the same occurrence of subsequence B1b. MTs 700, 705, 707, 710, 720, 740 and 747 Either field 39A or field 39B, but not both, may be present. D06 MTs 700, 705, 707, 710 and 720 Either field 44C or 44D but not both, may be present. D07 D08 D09 D10 D11 D12 D13 Available. Available. Available. Available. Available. Available. MTs 503, 504 and 506 In subsequence B1, fields 16R and 16S may not be the only fields present. If both fields 16R and 16S are present, then at least one other field of the same subsequence must be present. Then in same subsequence B1b, field :94a::SAFE is ... Mandatory Optional

50

Error Codes

Chapter 3 Alphanumeric Codes

D14 D15 D16

Available. Available. MT 306 The presence of subsequence B1 and of sequence C depends on the values of Type of Event (subfield 1 of field 22K) in sequence A as follows: Sequence A if subfield 1 of field 22K is ... CLST CONF KNIN KNOT OTHR TRIG Then subsequence B1 is ... Optional Mandatory Not allowed Not allowed Optional Not allowed And sequence C is ... Optional Mandatory Not allowed Not allowed Optional Not allowed

D17

MTs 102 and 102+ Field 50a must be present either in sequence A or in each occurrence of sequence B, but it must never be present in both sequences, nor be absent from both sequences.

D18

MT 102 (not 102+) If a field 52a, 26T or 77B is present in sequence A, then that field must not be present in any occurrence of sequence B. When a field 52a, 26T or 77B is present in any occurrences of sequence B, that field must not be present in sequence A. Sequence A if field 52a is ... Present Not present Sequence A if field 26T is ... Present Not present Sequence A if field 77B is ... Present Not present In each occurrence of sequence B then field 52a is ... Not allowed Optional In each occurrence of sequence B then field 26T is ... Not allowed Optional In each occurrence of sequence B then field 77B is ... Not allowed Optional

23 July 2010

51

FIN

MT 102+ If a field 52A, 26T or 77B is present in sequence A, then that field must not be present in any occurrence of sequence B. When a field 52A, 26T or 77B is in any occurrence of sequence B, that field must not be present in sequence A. Sequence A if field 52A is ... Present Not present Sequence A if field 26T is ... Present Not present Sequence A if field 77B is ... Present Not present D19 MT 102+ If in the transaction headers the country codes of both the Sender's and Receiver's BIC are present in the list D19_CC (see note 2), then in each occurrence of sequence B the following apply: If field 57A is not present, then the IBAN format (ISO-13616, see note 1) is mandatory in subfield_1 Account of field 59a in this occurrence of sequence B. If field 57A is present and the country code of the BIC in 57A (note) is present in the list D19_CC, then the IBAN format is mandatory in subfield_1 Account of field 59a in this occurrence of sequence B. In all other cases, the presence of the IBAN format is optional and its format is not validated in subfield_1 Account of field 59a. In each occurrence of sequence B then field 52A is ... Not allowed Optional In each occurrence of sequence B then field 26T is ... Not allowed Optional In each occurrence of sequence B then field 77B is ... Not allowed Optional

Note: 1. <IBAN> format special validation. 2. D19_CC list of country codes : AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP, GR, HU, IE, IS, IT, LI, LT, LU, LV, MC, MQ, MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA.

52

Error Codes

Chapter 3 Alphanumeric Codes

In transaction headers, If country code of Emitter's BIC present in D19_CC And country code of Receiver's BIC present in D19_CC

In each occurrence of sequence B, And field 57A present in this occurrence of sequence B And country code of field 57A is present in D19_CC Then in this occurrence of sequence B in field 59a the <IBAN> format in subfield_1 Account is ... Mandatory Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Optional Optional

Yes Yes No No Yes Yes No No Yes Yes No No

Yes No Yes No Yes No Yes No Yes No Yes No

No No No No Yes Yes Yes Yes Yes Yes Yes Yes

NA NA NA NA Yes Yes Yes Yes No No No No

Note: This validation rule applies to all types of BICs that are referenced in field 57A: SWIFT BIC, NON-SWIFT BIC, Master, Synonym, LIVE destination, Test and Training destination.
MT 103+ If in the transaction headers the country codes of both the Sender's and Receiver's BIC are present in the list D19_CC (see note 2), then in each occurrence of sequence B the following apply: If field 57A is not present, then the IBAN format (ISO-13616, see note 1) is mandatory in subfield_1 Account of field 59a If field 57A is present and the country code of the BIC in 57A (note) is present in the list D19_CC, then the IBAN format is mandatory in subfield_1 Account of field 59a In all other cases, the presence of the IBAN format is optional and its format is not validated in subfield_1 Account of field 59a.

Note: 1. <IBAN> format special validation. 2. D19_CC list of country codes : AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP, GR, HU, IE, IS, IT, LI, LT, LU, LV, MC, MQ, MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA.

23 July 2010

53

FIN

In transaction headers, If country code of Emitter's BIC present in D19_CC Yes Yes No No Yes Yes No No Yes Yes No No and country code of Receiver's BIC present in D19_CC Yes No Yes No Yes No Yes No Yes No Yes No and field 57A present and country code of field 57A is present in D19_CC NA NA NA NA Yes Yes Yes Yes No No No No then in field 59a the <IBAN> format in subfield_1 Account is ... Mandatory Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Optional Optional

No No No No Yes Yes Yes Yes Yes Yes Yes Yes

Note: This validation rule applies to all types of BICs that are referenced in field 57A: SWIFT BIC, NON-SWIFT BIC, Master, Synonym, LIVE destination, Test and Training destination.
D20 MTs 102 and 102+ Field 71A must be present either in sequence A or in each occurrence of sequence B, but it must never be present in both sequences, nor be absent from both sequences.

Note:
D21

This error code takes precedence over Error codes D50, E13 and E15.

MTs 104 and 107 In each occurrence of sequence B, if field 33B is present, then the currency code or the amount, or both, must be different between fields 33B and 32B.

D22

MT 102 and 102+ Field 36 (sequence A or sequence B) must be present in the message if there is any sequence B which contains a field 33B with a currency code different from the currency code in field 32B; in all other cases field 36 is not allowed in the message. When a field 36 (sequence A or sequence B) is required, EITHER field 36 must be present in sequence A and not in any sequence B, OR it must be present in every sequence B which contains fields 32B and 33B with different currency codes and must not be present in sequence A or any other sequence B.

54

Error Codes

Chapter 3 Alphanumeric Codes

In sequence A If field 36 is present

In sequence B Then in minimum one occurrence of sequence B field 33B must be present, and currency codes in fields 32B and 33B must be different. And field 36 is not allowed in any occurrence of sequence B

In sequence A

In each occurrence of sequence B If field 33B is ... And currency codes in fields 32B and 33B are ... Equal Not equal Not present NA Then field 36 is ...

If field 36 is not present

Present

Not allowed Mandatory Not allowed

D23

MT 304 The presence of sequence D depends on field 17O as follows: Sequence A if field 17O is ... Y N Not present Then sequence D is ... Not allowed Mandatory Not allowed

D24

MT 306 In sequence A, if field 12F contains VANI, then at least field 17A or field 17F must contain Y. Both fields may contain Y. Sequence A If field 12F is ... And field 17A is ... And field 17F is ... Then this combination of codes is ... Not allowed Allowed Allowed Allowed Allowed

VANI VANI VANI VANI Not = VANI D25 D26 Available. MT 306

N N Y Y NA

N Y N Y NA

In sequence A, the values allowed for field 12E depend on the value of field 12F as follows:

23 July 2010

55

FIN

Sequence A If field 12F is ... BINA DIGI NOTO VANI D27 MT 306 In sequence A, the allowed values for subfield 1 of field 22K depend on fields 12F and 17A as follows: Sequence A If field 12F is ... VANI VANI Not = VANI Not = VANI N Y N Y And field 17A is ... Then the allowed values for subfield 1 of field 22K are ... CONF, CLST, OTHR CONF, CLST, KNIN, KNOT, OTHR CONF, CLST, TRIG, OTHR CONF, CLST, KNIN, KNOT, TRIG, OTHR Then the allowed values for field 12E are ... AMER, EURO EURO EURO AMER, BERM, EURO

D28

MT 306 In sequence A, the presence of fields 30U and 29H depends on the value of subfield 1 of field 22K as follows: Sequence A If subfield 1 of field 22K is ... CONF or CLST Any other value Then field 30U is ... Not allowed Mandatory And field 29H is ... Not allowed Optional

D29

MT 304 The presence of sequence E depends on fields 17F and 17N as follows: Sequence A Then sequence E is ... If field 17F is ... Y Y Y And field 17N is ... Y N Not present Mandatory Not allowed Not allowed (this case is already negatively acknowledged, see Error codes D03 and D04) Not allowed

Y or N

56

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A Then sequence E is ... If field 17F is ... N And field 17N is ... Not present Not allowed (this case is already negatively acknowledged, see Error codes D03 and D04) Not allowed Not allowed

Not present Not present

Y or N Not present

Note:
MT 507

See also Error codes D03 and D04.

The presence of sequence B depends on the value of field :25D::4!c//<Status> in sequence A and the value of field :13A::Link//<Number Id> in subsequence A2 as follows: Sequence A If field :25D::4!c/[8c]/ 4!c Qualifier is ... And field :25D::REST/ [8c]/4!c Data Source Scheme [8c] is ... Not present And field :25D::REST/[8c]/ 4!c is ... Subsequence A2 and field :13A::LINK//3!c is ...

Then sequence B is ...

REST

:25D::REST//ACCP 503 :25D::REST//ACCT 503 :25D::REST//ACCP 504 :25D::REST//ACCT 504 :25D::REST//ACCP 505 :25D::REST//ACCT 505 :25D::REST//SUBR NA :25D::REST//REJT NA NA NA NA

Optional Optional Mandatory Mandatory Optional Optional Optional Not allowed Optional Not allowed Not allowed

Present CPRC IPRC NA NA

NA NA NA

Note:
MT 567

See Error code D52.

If the message is an instruction status or a cancellation request status (:23G:INST or CAST), AND sequence B is present, then sequence B should contain a CA option number and code (:13A::CAON and :22a::CAOP are mandatory). In sequence A if field :23G: is ... INST or CAST and sequence B is ... Present Not present then sequence B, field :13A::CAON is ... Mandatory NA and sequence B, field :22a::CAOP is ... Mandatory NA

23 July 2010

57

FIN

In sequence A if field :23G: is ... EVST D30 MT 306

and sequence B is ... NA

then sequence B, field :13A::CAON is ... NA

and sequence B, field :22a::CAOP is ... NA

The presence of sequences D and G depends on the value of field 12F in sequence A as follows: Sequence A if field 12F is ... VANI Not = VANI D31 MT 306 If sequence D is present, that is if field 12F in sequence A contains VANI (see Error code D30), then the presence of fields 30P and 30Q depends on the value of field 12E in sequence A as follows: Sequence A If field 12E is ... VANI And field 12E is ... AMER BERM Sequence D Then field 30P is ... Mandatory Not allowed And field 30Q is ... Not allowed Mandatory (that is at least one occurrence must be present) Not allowed Then sequence D is ... Mandatory Not allowed And sequence G is ... Not allowed Mandatory

EURO D32 MT 306

Not allowed

The presence of sequence E depends on the values of field 12F and subfield 1 of field 22K in sequence A as follows: Sequence A If field 12F is ... VANI BINA or DIGI NOTO NOTO D33 MT 306 In sequence D, if present, that is, if field 12F in sequence A contains VANI (see Error code D30), then the allowed values for field 26F in sequence D depend on the value of field 17F in sequence A as follows: And subfield 1 of field 22K is ... Any value Any value Not = TRIG TRIG Then sequence E is ...

Not allowed Mandatory Mandatory Not allowed

58

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A If field 12F is ... VANI Y N D34 MT 306 If field 17F is ...

Sequence D Then the allowed values for field 26F are ... NETCASH NETCASH, PRINCIPAL

In sequence E, if present (see also Error code D32), the presence of field 30H depends on the value of subfield 1 of field 22K and on the Expiration Style (field 12E) in sequence A as follows: If sequence E is ... Sequence A and subfield 1 of field 22K is ... TRIG Not = TRIG Not present D35 MTs 360 and 361 In sequence A, if field 14A contains OTHER, field 77D must be present. D36 MTs 306, 360 and 361 In sequence A, if subfield 1 of field 77H contains OTHER, field 77D must be present: Sequence A If subfield 1 of field 77H is ... OTHER Not = OTHER MT 340 The presence of sequence E and field 72 in sequence E depends on the value of field 14F in sequence B as follows: Sequence B if field 14F is ... OTHER Not = OTHER Then sequence E is ... Mandatory Optional Sequence E and field 72 is ... Mandatory Optional Mandatory Optional Then field 77D is ... NA Sequence A and field 12E is ... AMER AMER or EURO NA Sequence E then field 30H is ... Mandatory Not allowed NA

Present

Note:

Because field 14F is variable length (1 to 24 characters), it must be coded

:14F:OTHER<CrLf>.

In all other cases, the condition will not be true, that is Not = OTHER applies, for example:
:14F: :14F:OTHER OTHER<CrLf> (leading blanks) <CrLf> (trailing blanks)

:14F:OTHERWISE<CrLf>

23 July 2010

59

FIN

MT 600 The presence of field 77D depends on the value of Type of Agreement (subfield 1 of field 77H) as follows: Sequence A if subfield 1 of field 77H is ... OTHER Not=OTHER MT 601 The presence of field 77D depends on the value of Type of Agreement (subfield 1 of field 77H) as follows: If subfield 1 of field 77H is ... OTHER Not=OTHER D37 MT 340 The presence of sequence E and field 72 in sequence E depends on the value of field 14D in subsequence B2 as follows: Subsequence B2 if field 14D is ... OTHER Not = OTHER Then sequence E is ... Mandatory Optional Sequence E and field 72 is ... Mandatory Optional then field 77D is ... Mandatory Optional Sequence A then field 77D is ... Mandatory Optional

Note:

Because field 14D is variable length (1 to 24 characters), it must be coded

:14D:OTHER<CrLf>.

In all other cases, the condition will not be true, that is Not = OTHER applies, for example:
:14D: :14D:OTHER OTHER<CrLf> (leading blanks) <CrLf> (trailing blanks)

:14D:OTHERWISE<CrLf> MTs 360 and 361 In sequences B, C, E and F, if field 14D contains OTHER, field 37N must be present in the respective sequence. D38 MTs 360 and 361 In sequences C and F, if field 14F contains OTHER, field 37N must be present in the respective sequence. D39 MTs 360 and 361 In sequences C and F, if field 14J contains OTHER, field 37N must be present in the respective sequence.

60

Error Codes

Chapter 3 Alphanumeric Codes

D40

MTs 360 and 361 In sequences C and F, if subfield 1 of field 14G contains O, field 37N must be present in the respective sequence.

D41

MTs 360 and 361 In sequences C and F, if subfield 2 of field 38E contains O, field 37N must be present in the respective sequence.

D42

MT 340 The presence of sequence E and field 72 in sequence E depends on the value of the second component of subfield 1 of field 38G in subsequence B2 as follows: Subsequence B2 if second component of subfield 1 of field 38G is ... O Not = O MTs 360 and 361 If subsequence C3 or F3 is present, and if subfield 2 or subfield 4 of field 38G or field 38H contains O, then field 37N must be present in the respective sequence C or F. Then sequence E is ... Sequence E and field 72 is ... Mandatory Optional

Mandatory Optional

D43

MT 306 The presence of sequence F depends on the value of field 17A in sequence A as follows: Sequence A if field 17A is ... Y N Mandatory Not allowed Then sequence F is ...

D44

MT 306 In sequence F, the presence of field 37L depends on the value of field 22G as follows: Sequence F If field 22G is ... SKIN or SKOT DKIN or DKOT Not allowed Mandatory Then field 37L is ...

Note:

See also Error code D43.

23 July 2010

61

FIN

D45

MTs 360 and 361 If subsequence B1 is present, the presence of fields 32M (in each occurrence of the internal loop), 17F and 14D depends on field 37U in sequence B as follows: If in sequence B field 37U is ... If subsequence B1 is present, then in each occurrence of the internal loop, field 32M is ... Not allowed Mandatory If subsequence B1 If subsequence B1 is present, then field is present, then field 14D is ... 17F is ...

Present Not present

Mandatory Not allowed

Mandatory Not allowed

Note:
D46 MT 306

The presence of subsequence B1 is determined by Error code E41.

In sequence G, the presence of field 37P depends on the value of field 22J as follows: Sequence G If field 22J is ... SITR DBTR Not allowed Mandatory Then field 37P is ...

Note:
D47 MT 306

See also Error code D30.

The presence of sequence H depends on the value of field 17F in sequence A as follows: Sequence A if field 17F is ... Y N D48 MTs 360 and 361 In sequences L and M, for all occurrences of fields 53a, 56a and 57a the following rules apply: If in sequence L or M field 57a is ... Present Not present D49 MTs 102 and 102+ If the country codes of both the Sender's and the Receiver's BIC belong to the D49_CC list, then field 33B is mandatory in each occurrence of sequence B, otherwise field 33B is optional. D49 CC list of country codes: AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP, GR, HU, IE, IS, IT, LI, LT, LU, LV, MC, MQ, MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA Then in the same sequence fields 53a and 56a are ... Optional Not allowed Mandatory Not allowed Then sequence H is ...

62

Error Codes

Chapter 3 Alphanumeric Codes

If Emitter's BIC country code present in D49_CC Yes Yes No No

And Receiver's BIC country code present in D49_CC Yes No Yes No

In each occurrence of sequence B, then field 33B is ... Mandatory Optional Optional Optional

Note:

See Error code D51.

MTs 103 and 103+ If the country codes of both the Sender's and the Receiver's BIC belong to the D49_CC list, then field 33B is mandatory, otherwise field 33B is optional. D49 CC list of country codes: AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP, GR, HU, IE, IS, IT, LI, LT, LU, LV, MC, MQ, MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA. If Emitter's BIC country code present in D49_CC Yes Yes No No And Receiver's BIC country code present in D49_CC Yes No Yes No Then field 33B is ...

Mandatory Optional Optional Optional

Note:
MT 504

See Error code D51.

Sequence D is not allowed when for all occurrences of sequence C, either subsequence C1 is not present or C1a is present in all occurrences of C1. If sequence D is ... Present Then in sequence(s) C In one or more occurrence(s) of sequence C: subsequence C1 must be present and an internal subsequence C1a must not be present

Note:
MT 505

See Error code C97.

Sequence C is not allowed when for all occurrences of sequence B, either subsequence B1 is not present or B1a is present in all occurrences of B1. If sequence C is ... Present Then in sequence(s) B In one or more occurrence(s) of sequence B: subsequence B1 must be present and an internal subsequence B1a must not be present

Note:

See Error code C97.

23 July 2010

63

FIN

D50

MTs 102 and 102+ If field 71A in sequence A contains SHA, then fields 71F are optional and field 71G is not allowed in any occurrence of sequence B. In sequence A If field 71A is ... SHA In each occurrence of sequence B Then fields 71F are ... Optional And field 71G is ... Not allowed

If field 71A in sequence B contains SHA, then fields 71F are optional and field 71G is not allowed in the same occurrence of sequence B. In sequence B If field 71A is ... SHA In the same occurrence of sequence B Then fields 71F are ... Optional And field 71G is ... Not allowed

Note: See Error codes D20, E13 and E15. Error code D20 takes precedence over Error codes D50, E13 and E15.
MTs 103 and 103+ If field 71A contains SHA, then field(s) 71F is(are) optional and field 71G is not allowed. If field 71A is ... SHA Then field 71F is ... Optional And field 71G is ... Not allowed

Note:
MT 504

See Error codes E13 and E15.

Sequence E is not allowed when, for all occurrences of C, either subsequence C2 is not present, or C2a is present in all occurrences of C2. If sequence E is ... Present Then in sequence(s) C In one or more occurrence(s) of sequence C: subsequence C2 must be present and an internal subsequence C2a must not be present

Note:
MT 505

See Error code C99.

Sequence D is not allowed when for all occurrences of sequence B, either subsequence B2 is not present or subsequence B2a is present in all occurrences of B2. If sequence D is ... Present Then in sequence(s) B In one or more occurrence(s) of sequence B: subsequence B2 must be present and an internal subsequence B2a must not be present

Note:
D51

See Error code C99.

MTs 102 and 102+ If either field 71F (at least one occurrence) or field 71G is present in an occurrence of sequence B, then field 33B is mandatory in the same occurrence of sequence B.

64

Error Codes

Chapter 3 Alphanumeric Codes

In each occurrence of sequence B If field 71F is ... Present Present Not present Not present
[1]

And field 71G is ... Present Not present Present Not present

Then field 33B is ... Rejected [1] Mandatory Mandatory Optional

The presence of both fields 71F and 71G is not allowed: see Error codes D50, E13 and E15.

MTs 103 and 103+ If either field 71F (at least one occurrence) or field 71G is present, then field 33B is mandatory; otherwise field 33B is optional. If field 71F is ... Present Present Not present Not present
[1]

And field 71G is ... Present Not present Present Not present

Then field 33B is ... Rejected [1] Mandatory Mandatory Optional

The presence of both fields 71F and 71G is not allowed, see Error codes D50, E13 and E15.

D52

MT 507 Field :13a::LINK must be present in one and only one occurrence of subsequence A2.

Note:
D53 MT 507

See also Error code D53.

Field :20C::RELA must be present in the same occurrence of subsequence A2 where field :13a::LINK is present. D54 MT 101 If field 36 is present, then field 21F must be present. Sequence B If field 36 is ... Present Not present D55 MTs 360 and 361 In sequences B, C, E and F, if field 14A contains OTHER, field 37N must be present in the respective sequence. D56 MT 320 The presence of fields 32H and 30X in sequence B depends on the value of field 22B in sequence A as follows: Mandatory Optional Then field 21F is ...

23 July 2010

65

FIN

Sequence A If field 22B is ... CONF MATU ROLL MT 330

Sequence B Then field 32H is ... Not allowed Mandatory Mandatory And field 30X is ... Mandatory Not allowed Mandatory

The presence of fields 32B, 32H and 30X in sequence B depends on the value of field 22B in sequence A as follows: Sequence A If field 22B is ... CHNG CINT CONF SETT MT 620 In sequence B, the presence of fields 32a (index 19, field 32H, R) and 30X depends on the value of field 22B in sequence A as follows: Sequence A if field 22B is ... CONF MATU ROLL D57 MTs 102, 102+, 104 and 107 In sequence C, in field 71G, Amount must not equal '0' . MTs 103 and 103+ In field 71G, Amount must not equal '0' . MT 320 The values allowed for field 32H in sequence B depend on the values of fields 22B in sequence A and 17R in sequence B as follows: Sequence A If field 22B is ... MATU MATU Not = MATU L B NA Sequence B And field 17R is ... Then field 32H must be ... Negative or zero Positive or zero NA Sequence B then field 32a (index 19, field 32H, R) is ... Not allowed Mandatory Mandatory Sequence B and field 30X is ... Mandatory Not allowed Mandatory Then field 32B is ... Mandatory Mandatory Mandatory Not allowed Sequence B And field 32H is ... Mandatory Mandatory Not allowed Mandatory And field 30X is ... Optional Optional Not allowed Mandatory

Note:

See Error code D56.

66

Error Codes

Chapter 3 Alphanumeric Codes

MT 330 The values allowed for field 32H in sequence B depend on the values of fields 22B in sequence A and 17R in sequence B as follows: Sequence A If field 22B is ... SETT SETT Not = SETT L B NA Sequence B And field 17R is ... Then field 32H must be ... Negative or zero Positive or zero NA

The presence of N in subfield 1 of field 32H specifies a negative amount. The absence of N in subfield 1 of field 32H specifies a positive amount.

Note:
MT 620

See Error code D56.

In sequence B, the values allowed for field 32a (index 19, field 32H, R) depend on the values of fields 22B in sequence A and 17R in sequence B as follows: Sequence A if field 22B is ... MATU MATU Not = MATU L B NA Sequence B and field 17R is ... Sequence B then field 32a (index 19, field 32H, R) must be ... Negative or zero Positive or zero NA

Note:
D58 MT 360

See rule 156.

Depending on the contents of subfield 1 of field 23A in sequence A, only the following combinations of optional sequences B, C, E, and F are allowed: Sequence A subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER COLLARSLLR Then sequence B is ... Mandatory Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Then sequence C is ... Not allowed Mandatory Not allowed Mandatory Mandatory Not allowed Mandatory Not allowed Mandatory Mandatory Then sequence E is ... Mandatory Not allowed Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Then sequence F is ... Not allowed Mandatory Mandatory Not allowed Not allowed Mandatory Not allowed Mandatory Mandatory Mandatory

23 July 2010

67

FIN

Note:
D59

See Error codes E41 and E42.

MTs 360 and 361 If subsequence E1 is present, the presence of fields 32M (in each occurrence of the internal loop), 17F and 14D, depends on field 37U in sequence E as follows: If in sequence E field 37U is ... If subsequence E1 is present, then in each occurrence of the internal loop field 32M is ... Not allowed Mandatory If subsequence E1 If subsequence E1 is present, then field is present, then field 14D is ... 17F is ...

Present Not present D60 MT 101

Mandatory Not allowed

Mandatory Not allowed

In each occurrence of sequence B, if field 33B is present and 'amount' in field 32B is not equal to zero, then field 36 must be present, otherwise field 36 is not allowed. In each occurrence of sequence B Sequence B if field 33B is ... Present Sequence B and amount in field 32B is ... Equal to zero Not equal to zero Not present MTs 320, 330, and 620 In sequence B, if field 30F is present, then field 38J in sequence B is mandatory; otherwise field 38J is not allowed. Sequence B If field 30F is ... Present Not present MT 341 In sequence B, if field 30V is present, then field 38D in sequence B is mandatory; otherwise field 38D is not allowed. Sequence B If field 30V is ... Present Not present Mandatory Not allowed Then field 38D is ... Mandatory Not allowed Then field 38J is ... NA Sequence B then field 36 is ... Not allowed Mandatory Not allowed

68

Error Codes

Chapter 3 Alphanumeric Codes

D61

MT 101 If there is only one debit account, the ordering customer must be identified in field 50a index 5 (option F, G or H) in sequence A. Conversely, if multiple debit accounts are used, they must be identified for every transaction in field 50a index 15 (option F, G or H) of sequence B. Consequently, field 50a (option F, G or H) must be present in either sequence A (index 5) or in each occurrence of sequence B (index 15), but must never be present in both sequences, nor be absent from both sequences. Sequence A if field 50a index 5 (option F, G or H) is ... Present Not present In every occurrence of sequence B then field 50a index 15 (option F, G or H) is ... Not allowed Mandatory

D62

MT 101 Field 50a (option C or L) may be present in either sequence A or each occurrence of sequence B, but must not be present in both sequences A and B. Sequence A if field 50a (option C or L) is ... Present Not present Sequence B then field 50a (option C or L) is ... Not allowed Optional in any occurrence

D63

MTs 101, 102 (not 102+), 103 (not 103+), 104, 107, 405 and 416 Field 51A is valid only in FileAct. (This special error code is required to indicate to FileAct users that they have included in a FIN message a field that is reserved for FileAct.)

D64

MT 101 Field 52a must not be present in both sequences A and B. Sequence A if field 52a is ... Present Not present Not allowed Optional Sequence B then field 52a is ...

D65

MTs 101 and 207 In each occurrence of sequence B, if field 56a is present then field 57a must be present. If field 56a is ... Present Not present Mandatory Optional Then field 57a is ...

D66

MT 101 Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of CMTO, PHON, OTHR or REPA.

23 July 2010

69

FIN

MT 207 Subfield 2 of field 23E is only allowed when subfield 1 of this field consists of CMTO, PHON or OTHR. D67 MT 101 In each occurrence of sequence B, when field 23E is used more than once, the following combinations are not allowed. CHQB CHQB CHQB CHQB CHQB CHQB CHQB CHQB CHQB CMSW CMSW CMTO CORT CORT CORT CORT EQUI EQUI EQUI NETS Example: Valid :23E:CMSW :23E:CORT Invalid :23E:CHQB :23E:URGP with with with with with with with with with with with with with with with with with with with with CMSW CMTO CMZB CORT URGP REPA RTGS NETS PHON CMTO CMZB CMZB CMSW CMTO CMZB REPA CMSW CMTO CMZB RTGS

:23E::PHON :23E::NETS MT 103 (not 103+)

:23E:NETS :23E:RTGS

When field 23E is used more than once, the following combinations are not allowed:

70

Error Codes

Chapter 3 Alphanumeric Codes

SDVA SDVA INTC INTC REPA REPA REPA CORT CORT HOLD PHOB PHON PHOI MT 103+

with with with with with with with with with with with with with

HOLD CHQB HOLD CHQB HOLD CHQB CORT HOLD CHQB CHQB TELB TELE TELI

When field 23E is used more than once, the following combination is not allowed: REPA MT 207 CMSW CMSW CMTO CORT CORT CORT NETS D68 MT 101 For each occurrence of sequence B, if field 33B is present in sequence B, its currency code must be different from the currency code in field 32B of the same occurrence of sequence B. Examples: Valid :32B:USD1000, :33B:CHF1000, . . . :32B:CHF1200, Invalid :32B:USD1000,00 :33B:USD1000, . . . :32B:CHF1200, with with with with with with with CMTO CMZB CMZB CMSW CMTO CMZB RTGS with CORT

23 July 2010

71

FIN

Valid :33B:USD1000, D69 MTs 320 and 620

Invalid :33B:CHF1000,00

If field 22B in sequence A contains MATU, then field 30F in sequence B is not allowed; otherwise field 30F is optional. Sequence A if field 22B is ... MATU Not = MATU MT 330 If field 22B contains SETT in sequence A, then field 30F in sequence B is not allowed; otherwise field 30F is optional. Sequence A if field 22B is ... SETT Not = SETT MT 340 If at least one occurrence of field 22B in subsequence B2 contains OTHR, then sequence E and field 72 in sequence E are mandatory; otherwise (that is no occurrence of field 22B contains OTHR), field 72 in sequence E is optional. Subsequence B2 if at least one field 22B is ... = OTHR Otherwise (that is no occurrence of field 22B contains OTHR) D70 MT 300 In sequence A, the presence of field 21 depends on the value of field 22A as follows: Sequence A If field 22A is ... AMND CANC DUPL EXOP NEWT MTs 320, 330 and 620 In sequence A, the presence of field 21 depends on the values of fields 22B and 22A as follows: Mandatory Mandatory Optional Optional Optional Then field 21 is ... Then sequence E is ... Mandatory Optional Sequence E and field 72 is ... Mandatory Optional Not allowed Optional Sequence B then field 30F is ... Not allowed Optional Sequence B then field 30F is ...

72

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A If field 22B is ... CONF CONF Not = CONF D71 MTs 502, 514 and 518 If field :22F::DBNM//VEND is present in sequence C, then it is mandatory to specify a vendor: that is, one occurrence of sequence D must contain :95a::VEND. If sequence C is ... And in sequence C if field :22F::DBNM//VEND is ... [1] Present Present Mandatory that is, sequence D must be present minimum once Optional Optional Then sequence D is ... And in one occurrence of sequence D field :95a::VEND is ... Mandatory [2] And if field 22A is ... NEWT Not = NEWT Any value Then field 21 is ... Optional Mandatory Mandatory

Not present Not present

[1]

Optional Optional

NA

If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule does not apply. :95a::VEND mandatory in only one occurrence of sequence D, see rule 284.

[2]

MTs 513 and 515 If field :22F::DBNM//VEND is present in sequence D, then it is mandatory to specify a vendor: that is, one occurrence of sequence E Other Parties must contain a party field :95a::VEND. If sequence D is ... And in sequence D if field :22F::DBNM//VEND is ... [1] Present Present Mandatory that is, sequence E must be present minimum once Optional Optional Then sequence E is ... And in one occurrence of sequence E field :95a::VEND is ... Mandatory [2]

Not present Not present

[1]

Optional Optional

NA

If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule does not apply. :95a::VEND mandatory in only one occurrence of sequence E, see rule 284.

[2]

MTs 528 and 529 If field :22F::DBNM//VEND is present in sequence C, then it is mandatory to specify a vendor: that is, one occurrence of sequence D Other Parties must contain a party field :95a::VEND:

23 July 2010

73

FIN

In sequence C if field :22F::DBNM//VEND is ... [1] Present

Then sequence D is ...

And in one occurrence of sequence D field :95a::VEND is ... Mandatory [2]

Mandatory that is, sequence D must be present minimum once Optional

Not present
[1]

Optional

If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule does not apply. :95a::VEND mandatory in only one occurrence of sequence D, see rule 284.

[2]

MTs 540, 541, 542 and 543 If field :22F::DBNM//VEND is present in sequence E, then it is mandatory to specify a vendor: that is, one occurrence of sequence F Other Parties must contain a party field :95a::VEND: In sequence E if field :22F::DBNM//VEND is ... [1] Present Mandatory that is, sequence F must be present minimum once Optional Then sequence F is ... And in one occurrence of sequence F field :95a::VEND is ... Mandatory [2]

Not present
[1]

Optional

If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule does not apply. :95a::VEND mandatory in only one occurrence of sequence F, see rule 284.

[2]

D72

MT 320 and 620 In sequence A, if field 94A is present and contains AGNT, then field 21N in sequence A is mandatory; otherwise it is optional. Sequence A If field 94A is ... AGNT BILA BROK Not present MTs 330 and 350 In sequence A, if field 94A is present and contains AGNT, then field 21N in sequence A is mandatory; otherwise it is optional. Sequence A If field 94A is ... AGNT Mandatory Then field 21N is ... Mandatory Optional Optional Optional Then field 21N is ...

74

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A If field 94A is ... BILA Not present D73 MTs 104 and 107 When present in sequence A, fields 21E, 26T, 77B, 71A, 52a and 50a (option C or L) must, independently of each other, not be present in any occurrence of sequence B. When present in one or more occurrences of sequence B, fields 21E, 26T, 77B, 71A, 52a and 50a (option C or L) must not be present in sequence A. Sequence A if field 26T is ... Present Not present Sequence A if field 77B is ... Present Not present Sequence A if field 71A is ... Present Not present Sequence A if field 52a is ... Present Not present Sequence A if field 21E is ... Present Not present Sequence A if field 50a (option C or L) is ... Present Not present Not allowed Optional Sequence B then field 50a (option C or L) is ... Not allowed Optional Not allowed Optional Sequence B then field 21E is ... Not allowed Optional Sequence B then field 52a is ... Not allowed Optional Sequence B then field 71A is ... Not allowed Optional Sequence B then field 77B is ... Sequence B then field 26T is ... Optional Optional Then field 21N is ...

23 July 2010

75

FIN

D74

MT 300 The presence of sequence C and fields 88a and 71F depends on field 94A as follows: Sequence A if field 94A is ... Not present AGNT BILA BROK MT 306 The presence of sequence I and fields 88a and 71F in sequence I depends on the value of field 94A in sequence A as follows: Sequence A if field 94A is ... Not present BROK Not = BROK MT 320 and 620 The presence of sequence H and fields 88a and 71F in sequence H depends on the value of field 94A in sequence A as follows: Sequence A if field 94A is ... Not present AGNT BILA BROK MT 340 The presence of sequence E and fields 88a and 71F in sequence E depends on the value of field 94A in sequence A as follows: Sequence A if field 94A is ... Not present BROK Not = BROK Then sequence E is ... Optional Mandatory Optional Sequence E and field 88a is ... Optional Mandatory Optional Sequence E and field 71F is ... Not allowed Optional Not allowed Then sequence H is ... Optional Optional Optional Mandatory Sequence H and field 88a is ... Optional Optional Optional Mandatory Sequence H and field 71F is ... Not allowed Not allowed Not allowed Optional Then sequence I is ... Optional Mandatory Optional Sequence I and field 88a is ... Optional Mandatory Optional Sequence I and field 71F is ... Not allowed Optional Not allowed Then sequence C is ... Optional Optional Optional Mandatory Sequence C and field 88a is ... Optional Optional Optional Mandatory Sequence C and field 71F is ... Not allowed Not allowed Not allowed Optional

76

Error Codes

Chapter 3 Alphanumeric Codes

MTs 360 and 361 The presence of fields 88a and 71F in sequence N and, therefore, the presence of sequence N itself, depend on field 94A in sequence A as follows: Sequence A if field 94A is ... Not present AGNT BILA BROK D75 MTs 103 and 103+ If field 33B is present and the currency code is different from that of field 32A, then field 36 must be present; otherwise field 36 is not allowed. If field 33B is ... Present And currency code in field 33B is ... Not = currency code in field 32A = currency code in field 32A Not present MTs 104 and 107 In any occurrence of sequence B, if field 33B is present and the currency codes in fields 32B and 33B are different, then field 36 must be present. Otherwise, field 36 must not be present. Sequence B If field 33B is ... Not present Present, and <field 32B currency code> NOT = <field 33B currency code> Present, and <field 32B currency code> = <field 33B currency code> D76 MT 300 The presence of sequence D depends on field 17U in sequence A as follows: Sequence A if field 17U is ... Not present Y N Then sequence D is ... Not allowed Mandatory Not allowed Not allowed Mandatory Not allowed Then field 36 is ... NA Then field 36 is ... Mandatory Not allowed Not allowed Then sequence N is ... Optional Optional Optional Mandatory Sequence N with field 88a is ... Optional Optional Optional Mandatory Sequence N with field 71F is ... Not allowed Not allowed Not allowed Optional

23 July 2010

77

FIN

D77

MT 104 If field 21E is present in sequence A, then field 50a (option A or K) must also be present in sequence A. In each occurrence of sequence B, if field 21E is present, then field 50a (option A or K) must also be present in the same occurrence. Sequence A If field 21E is ... Present Not present Then field 50a (option A or K) is ... Mandatory Optional (see Error code D76) Sequence B If field 21E is ... Present Not present MT 107 If field 21E is present in sequence A, then field 50a (option A or K) must also be present in sequence A. In each occurrence of sequence B, if field 21E is present, then field 50a (option A or K) must also be present in the same occurrence. Sequence A If field 21E is ... Present Not present Then field 50a (option A or K) is ... Mandatory Optional (see Error code D86) Sequence B If field 21E is ... Present Not present Then field 50a (option A or K) is ... Mandatory Optional (see Error code D86) Then field 50a (option A or K) is ... Mandatory Optional (see Error codes C76, C96)

D78

MT 416 Field 23E must be present either in sequence A or in each occurrence of sequence B but not in both. Sequence A if field 23E is ... Present Not present Not allowed Mandatory in each occurrence of sequence B Sequence B then field 23E is ...

D79

MTs 102 and 102+ If field 71G is present in one or more occurrences of sequence B, then field 71G is mandatory in sequence C.

78

Error Codes

Chapter 3 Alphanumeric Codes

If in any occurrence of sequence B field 71G is ... Present MTs 104 and 107 Mandatory

Sequence C then field 71G is ...

If field 71F is present in one or more occurrences of sequence B, then it must also be present in sequence C, and vice-versa. If field 71G is present in one or more occurrences of sequence B, then it must also be present in sequence C, and vice-versa. Sequence B if field 71F is ... Present Not present Sequence B if field 71G is ... Present Not present D80 MT 104 If sequence C is present and if the amount in field 32B of sequence C is equal to the sum of amounts of fields 32B of sequence B, then field 19 must not be present; otherwise, field 19 must be present. Mandatory Not allowed Mandatory Not allowed Sequence C then field 71G is ... Sequence C then field 71F is ...

Note:
MT 107

See also Error code C96.

If the amount in field 32B of sequence C is equal to the sum of amounts of the fields 32B of sequence B, then field 19 must not be present; otherwise field 19 must be present. MT 256 If the amount in field 32A of sequence C is equal to the sum of the amounts of the fields 32J of sequence B, then field 19 must not be present; otherwise (that is the amount in field 32A of sequence C is not equal to the sum of the amounts of fields 32J of sequence B), field 19 must be present. D81 MTs 104, 107, 256 and 416 Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of OTHR. MT 306 Subfield 2 of field 22K, that is '/'35x, is mandatory when subfield 1 of this field C consists of OTHR; otherwise subfield 2 is not allowed. MT 405 Subfield 2 of field 23C is allowed only when subfield 1 of this field consists of OTHR. Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of OTHR. Subfield 2 of field 23F is allowed only when subfield 1 of this field consists of OTHR. MTs 700, 710, and 720 Subfield 2 of field 40E, that is, "/"35x, is only allowed when subfield 1 of this field consists of OTHR.

23 July 2010

79

FIN

MT 760 Subfield 2 of field 40C is only allowed when subfield 1 of this field consists of 'OTHR'. D82 MTs 104, 107 and 207 The first component in line 1 of field 72 must consist either /RETN/ or /REJT/. D83 MT 416 When present in sequence A, fields 71F and 77A must, independently of each other, not be present in any occurrence of sequence B. Conversely, when not present in sequence A, fields 71F and 77A are, independently of each other, optional in any occurrence of sequence B. Sequence A if field 71F is ... Present Not present Sequence A if field 77A is ... Present Not present D84 MT 740 Either field 58a or 59, but not both, may be present. If field 58a is ... Present Not present D85 MT 330 In sequence B, if field 30X is present, then field 34E is mandatory; otherwise field 34E is not allowed. Sequence B If field 30X is ... Present Not present D86 MT 107 Fields 23E and 50a (option A or K) must, independently of each other, be present either in sequence A or in each occurrence of sequence B but not in both. Sequence A if field 23E is ... Present Not present In each occurrence of sequence B then field 23E is ... Not allowed Mandatory Mandatory Not allowed Then field 34E is ... Not allowed Optional Then field 59 is ... Then in each occurrence of sequence B field 71F is ... Not allowed Optional Then in each occurrence of sequence B field 77A is ... Not allowed Optional

80

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if field 50a (option A or K) is ... Present Not present MT 405

In each occurrence of sequence B then field 50a (option A or K) is ... Not allowed Mandatory

Fields 23E and 50D must, independently of each other, be present either in sequence A or in each occurrence of sequence B, but not both. Sequence A if field 23E is ... Present Not present Sequence A if field 50D is ... Present Not present D87 MT 405 When present in sequence A, fields 26T, 77B, 71A, 50L and 52a must, independently of each other, not be present in any occurrence of sequence B. Conversely, when not present in sequence A, fields 26T, 77B, 71A, 50L and 52a are, independently of each other, optional in any occurrence of sequence B. Sequence A if field 26T is ... Present Not present Sequence A if field 77B is ... Present Not present Sequence A if field 71A is ... Present Not present Sequence A if field 52a is ... Present Not present In each occurrence of sequence B then field 26T is ... Not allowed Optional In each occurrence of sequence B then field 77B is ... Not allowed Optional In each occurrence of sequence B then field 71A is ... Not allowed Optional In each occurrence of sequence B then field 52a is ... Not allowed Optional In each occurrence of sequence B then field 23E is ... Not allowed Mandatory In each occurrence of sequence B then field 50D is ... Not allowed Mandatory

23 July 2010

81

FIN

Sequence A if field 50L is ... Present Not present D88 MT 405

In each occurrence of sequence B then field 50L is ... Not allowed Optional

Independently of each other, if fields 71F and 71G are present in one or more occurrence of sequence B, then they must also be present in sequence C. Conversely, if fields 71F and 71G are not present in any occurrence of sequence B, then they must not be present in sequence C. Sequence B if field 71F is ... Present in one or more occurrences of sequence B And sequence C is ... Present Not present In sequence C then field 71F is ... Mandatory NA Not allowed NA In sequence C then field 71G is ... Mandatory NA Not allowed NA

Not present in any occurrence Present of sequence B Not present Sequence B if field 71G is ... Present in one or more occurrences of sequence B. And sequence C is ... Present Not present

Not present in any occurrence Present of sequence B. Not present D89 MT 405

If sequence C is present and the sum of the fields 32a in sequence B equals the amount indicated in field 32a in sequence C, then field 19 must not be present in sequence C. If sequence C is present and the sum of the fields 32a in sequence B does not equal the amount indicated in field 32a in sequence C, then field 19 must be present in sequence C and must equal the sum of all the fields 32a in sequences B. D90 MT 405 The presence of subsequences A1 and B1 is dependent on the presence and the content of subfield 1 of field 23E in the same sequence A and B respectively. Sequence A if field 23E is ... BACC BAAV BNAC RCPT PRNO OTHR Subsequence A1 is ... Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed

82

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if field 23E is ... Not present Sequence B if field 23E is ... BACC BAAV BNAC RCPT PRNO OTHR Not present D91 MT 405

Subsequence A1 is ... Not allowed Subsequence B1 is ... Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed Not allowed

If field 71A contains either SHA or BEN, field 17A must be used. If field 71A contains OUR, field 17A must not be used. If field 71A is not present, field 17A is optional. Sequence A If field 71A is ... SHA BEN OUR Not present Mandatory Mandatory Not allowed Optional Sequence B If field 71A is ... SHA BEN OUR Not present D92 MT 321 In subsequence B3, all orders of field 95a are optional, but at least one order (any one) must be present. MT 530 In each occurrence of sequence B, all orders of field 20C are optional, but at least one order (any one) must be present. Mandatory Mandatory Not allowed Optional Then field 17A is ... Then field 17A is ...

23 July 2010

83

FIN

MT 568 All orders of field 70a are optional, but at least one order (any one) must be present. D93 MT 102 (not 102+) If field 23 contains CHQB, then subfield 1 must not be present in field 59a. In all other cases, it is mandatory. MT 530 In each occurrence of sequence B, all orders of field 22F are optional, but at least one order (any one) must be present. D94 MT 405 The presence of fields 22D and 22E is dependent on the presence and the content of subfield 1 of field 23E as follows. Sequence A If field 23E is ... BACC BAAV BNAC RCPT PRNO OTHR Not present Then field 22D is ... Mandatory Mandatory Mandatory Not allowed Not allowed Optional Not allowed Sequence B If field 23E is ... BACC BAAV BNAC RCPT PRNO OTHR Not present D95 MT 405 In sequences A and B, depending on the content of field 23E, only the following code word combinations may be used in fields 22D and 22E: Sequence A Field 23E is ... BACC CPAY Field 22D is ... PNPY Field 22E is ... Then field 22D is ... Mandatory Mandatory Mandatory Not allowed Not allowed Optional Not allowed Then field 22E is ... Optional Optional Optional Optional Optional Optional Not allowed Then field 22E is ... Optional Optional Optional Optional Optional Optional Not allowed

84

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A Field 23E is ... BAAV BNAC BNAC BNAC BNAC RCPT PRNO OTHR CPAY CACC CACP CACP CPAY Not allowed Not allowed Any valid code word Sequence B Field 23E is ... BACC BAAV BNAC BNAC BNAC BNAC RCPT PRNO OTHR D96 MT 300 If sequence D is present, field 16A must equal the number of internal repetitions in sequence D (that is block of fields: 17A - 58a). MTs 306, 320, 340, 360, 361 and 362 Field 18A must equal the number of repetitions that immediately follows. D97 MT 103 Subfield 2 of field 23E is allowed only when subfield 1 consists of PHON, PHOB, PHOI, TELE, TELB, TELI , HOLD or REPA. MT 103+ Subfield 2 of field 23E is only allowed when subfield 1 consists of REPA. D98 MT 101 If field 21R is present in sequence A, then in each occurrence of sequence B, the currency code in fields 32B must be the same. CPAY CPAY CACC CACP CACP CPAY Not allowed Not allowed Any valid code word Field 22D is ... PNPY PNPY PNAC PNAP PNPY PNPY Any valid code word Any valid code word Any valid code word Field 22E is ... Field 22D is ... PNPY PNAC PNAP PNPY PNPY Any valid code word Any valid code word Any valid code word Field 22E is ...

23 July 2010

85

FIN

MT 103 (not 103+) If field 23E is repeated, the codes must appear in the following order: SDVA INTC REPA CORT HOLD CHQB PHOB TELB PHON TELE PHOI TELI

Note: The first code does not need to be SDVA. There may be gaps. See also Error codes D67 and E46.
MT 103+ If field 23E is repeated, the codes must appear in the following order: SDVA INTC REPA CORT

Note: The first code does not need to be SDVA. There may be gaps. See also Error code E46.
D99 MT 564 If field :70E::NAME is used in sequence D, then field :22F::CAEV//CHAN must be present in sequence A and field :22F::CHAN//NAME must be present in sequence D. In sequence D if field :70E::NAME is ... Present Not present MT 566 If field :70E::NAME is used in sequence C, then field :22F::CAEV//CHAN must be present in sequence A and field :22F::CHAN//NAME must be present in sequence C. Then sequence A field :22F::CAEV//CHAN is ... Mandatory, and DSS must not be present NA And sequence D, field :22F::CHAN//NAME is ... Mandatory, and DSS must not be present NA

86

Error Codes

Chapter 3 Alphanumeric Codes

In sequence C if field :70E::NAME is ... Present Not present

Then sequence A field :22F::CAEV//CHAN is ... Mandatory, and DSS must not be present NA

And sequence C field :22F::CHAN//NAME is ... Mandatory, and DSS must not be present NA

3.5.3 E Error Codes

Note
Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.

E00 E01

Not used. MT 103 (not 103+) If field 23B contains SPRI, field 23E can contain only SDVA, TELB, PHOB, or INTC. If field 23B is ... SPRI Not = SPRI MT 103+ If field 23B contains SPRI, field 23E can contain only SDVA and INTC. If field 23B is ... SPRI Not = SPRI MT 564 In sequence A, if field :22F::CAEV//RHDI is present, then sequence C is not allowed. In sequence A, if field :22F::CAEV//RHTS is present, then sequence C is mandatory. In sequence A if field :22F::CAEV [1] is ... :22F::CAEV//RHDI :22F::CAEV//RHTS Other
[1]

Then field 23E is ... Optional. It can contain only SDVA, TELB, PHOB or INTC Optional

Then field 23E is ... Optional. It can contain only SDVA or INTC Optional

Then sequence C is ...

Not allowed Mandatory Optional

If the Data Source Scheme is present in field :22F::CAEV then the conditional rule does not apply.

23 July 2010

87

FIN

E02

MTs 103 and 103+ If field 23B contains SSTD or SPAY, field 23E must not be used. If field 23B is ... SSTD SPAY Not = SSTD and not = SPAY MT 564 In sequence A, if field :23G:REPE is present, then when sequence C is present, field :36a::QINT is mandatory. In sequence A if field :23G:REPE is ... Present And sequence C is ... Then in sequence C field :36a::QINT is ... Mandatory NA Optional Not allowed Not allowed Optional Then field 23E is ...

Present Not present

Not present E03 MT 103 (not 103+)

Optional

If field 23B contains SPRI, SSTD or SPAY, field 53a must not be used with option D. If field 23B is ... SPRI, SSTD or SPAY Other code MT 564 In sequence A, if field :22F::CAEV//OTHR is present, then sequence F must be present, and field :70E::ADTX must be present in the message. Sequence A if field :22F::CAEV//OTHR is ... Present Not present
[1]

Then field 53a ... Must not be used with option D (that is, only options A and B may be used) Optional

Then sequence F is ...

[1]

And in sequence F field :70E::ADTX is ... Mandatory NA

Mandatory NA

If the Data Source Scheme is present in field :22F::CAEV//OTHR, then the conditional rule does not apply.

E04

MT 103 (not 103+) If field 23B contains SPRI, SSTD or SPAY and field 53a is present with option B, subfield 1, Party Identifier (['/'<DC>]['/'34x] 'CRLF') must be present in field 53B. MT 103+ If field 53a is present with option B, subfield 1, Party Identifier (['/'<DC>]['/'34x] 'CRLF') must be present in field 53B.

88

Error Codes

Chapter 3 Alphanumeric Codes

E05

MT 103 (not 103+) If field 23B contains SPRI, SSTD or SPA, field 54a can be used with option A only. If field 23B is ... SPRI, SSTD or SPAY Other code Then field 54a is ... Optional with option A only (options B and D are not allowed) Optional

E06

MT 103 (not 103+) If field 55a is present, then both fields 53a and 54a must also be present. If field 36 is present, then field 33B must be present, and vice-versa. Therefore, fields 36 and 33B must be either both present, or both absent. If field 55a is ... Present Not present MT 103+ If field 55A is present, then both fields 53A and 54A must also be present. If field 55A is ... Present Not present MT 564 If field :22F::CAEV//RHDI is present in sequence A, then field :22F::RHDI must be present in sequence D or in at least one occurrence of sequence E, but not in both D and E. In sequence A if field :22F::CAEV//RHDI [1] is ... Present Present and :22F::RHDI is present And if sequence D is ... Then sequence E and field :22F::RHDI are ... Then field 53a is ... Option A Mandatory Optional And field 54A is ... Mandatory Optional Then field 53a is ... Mandatory Optional And field 54a is ... Mandatory Optional

Sequence E is optional, and field :22F::RHDI is not allowed in all occurrences of sequence E

Present and :22F::RHDI is not Sequence E is mandatory present (minimum one occurrence), and field :22F::RHDI is mandatory in at least one occurrence of sequence E Not present Sequence E is mandatory (minimum one occurrence), and field :22F::RHDI is mandatory in at least one occurrence of sequence E NA

Not present
[1]

NA

If the Data Source Scheme is present in field :22F::CAEV then the conditional rule does not apply.

23 July 2010

89

FIN

MT 566 If field :22F::CAEV//RHDI is present in sequence A, then sequence C is Mandatory and field :22F::RHDI must be present in sequence C. In sequence A if field :22F::CAEV//RHDI is ... Present Not present
[1]

Then sequence C is ...

[1]

And in sequence C field :22F::RHDI is ...

Mandatory Optional

Mandatory Optional

If the Data Source Scheme is present in field :22F::CAEV//RHDI then the conditional rule does not apply.

E07

MT 103 (not 103+) If field 23B contains SPRI, SSTD or SPAY, field 55a can be used with option A only. If field 23B is ... SPRI, SSTD or SPAY Other code Then field 55a is ... Optional with option A only (options B and D are not allowed) Optional

E08

MT 381 If the message is a cancellation (that is, if the Function of the Message -field 23G- is CANC), then subsequence A1 Linkages must be present at least once, and a reference to the previous message must be specified in the Linkage section (that is, field :20C::PREV must be present minimum once in that message). Sequence A if field :23G: is ... CANC Not = CANC
[1]

Then subsequence A1 is ...

And in minimum one occurrence of subsequence A1 field :20C::PREV is ... Mandatory [1] Optional

Mandatory, that is, minimum one occurrence of A1 Optional

It does not need to be present in all occurrences of A1.

MTs 500, 513, 514, 518, 519, 528, 529, 535, 536, 537, 538, 549, 565, 575, 576, 584, 586 and 587 If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... Then subsequence A1 is ... And in at least one occurrence of subsequence A1 field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1

CANC

Mandatory (minimum one occurrence of A1 must be present)

90

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if field 23G is ...

Then subsequence A1 is ...

And in at least one occurrence of subsequence A1 field :20C::PREV is ... NA

NEWN MTs 502

Optional

If the message is a cancellation or a replacement, that is, Function of the Message (field 23G) is CANC or REPL, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... CANC or REPL Then subsequence A1 is ... Mandatory (minimum one occurrence of A1 must be present) And field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1 NA

NEWN MTs 503, 504, 505, 506 and 569

Optional

If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then subsequence A2 (Linkages) must be present at least once in the message, and in one and only one occurrence of A2, field :20C::PREV must be present; consequently, in all other occurrences of A2, field :20C::PREV is not allowed. Sequence A if subfield 1 of field 23G is ... CANC Then subsequence A2 is ... And field :20C::PREV is ...

Mandatory (minimum one occurrence of A2 must be present)

Mandatory in one occurrence of subsequence A2, and not allowed in all other occurrences of subsequence A2. NA

NEWM MTs 508 and 524

Optional

If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then subsequence A1 (Linkages) must be present in the message, and field :20C::PREV must be present in A1. Sequence A if field 23G is ... CANC NEWN MTs 501, 515 and 517 If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then field :20C::PREV must be present in one and only one occurrence of A1; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Then subsequence A1 is ... Mandatory Optional And field :20C::PREV is ... Mandatory NA

23 July 2010

91

FIN

Sequence A if field 23G is ... CANC

Then field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1. NA

NEWN MT 527

If subfield 1 of field 23G contains REPL in sequence A, then sequence B is not allowed; otherwise sequence B is mandatory. Sequence A if subfield 1 of field 23G is ... REPL NEWM CANC MTs 540, 541, 542 and 543 If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... CANC Then subsequence A1 is ... Mandatory (minimum one occurrence of A1 must be present) And field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1. NA Then sequence B is ... Not allowed Mandatory Mandatory

NEWN or PREA MTs 544, 545, 546 and 547

Optional

If the message is a cancellation or a reversal, that is, Function of the Message (field 23G) is CANC or RVSL, then field :20C::PREV must be present in one and only one occurrence of subsequence A1; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... CANC or RVSL Then field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1 NA

NEWM MT 558

In sequence A, the presence of subsequence A2 depends on the value of subfield 1 of field 23G as follows:

92

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A If value of field :23G:4!c[/4!c] subfield 1 is ... ADVD Not ADVD MTs 564 and 568 If the message is a cancellation, a replacement, an eligible balance notification, a withdrawal or a reminder, that is, Function of the Message (field 23G) is CANC, REPL, REPE, WITH or RMDR, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... CANC, REPL, REPE, WITH, or RMDR Then subsequence A1 is ... Mandatory (minimum one occurrence of A1 must be present) And field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1 NA Then subsequence A2 is ... Not allowed Mandatory

NEWM MTs 566 and 588

Optional

If the message is a reversal, that is, Function of the Message (field 23G) is REVR, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... REVR Then subsequence A1 is ... Mandatory (minimum one occurrence of A1 must be present) And field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1 NA

NEWN MT 578

Optional

If the message is a cancellation or a removal, that is, Function of the Message (field 23G) is CANC or REMO, then subsequence A1 (Linkages) must be present at least once in the message, and in one and only in one occurrence of A1, field :20C::PREV must be present; consequently, in all other occurrences of A1, field :20C::PREV is not allowed. Sequence A if field 23G is ... CANC or REMO Then subsequence A1 is ... Mandatory (minimum one occurrence of A1 must be present) And field :20C::PREV is ... Mandatory in one occurrence of subsequence A1, and not allowed in all other occurrences of subsequence A1 NA

NEWN

Optional

23 July 2010

93

FIN

E09

MT 103 (not 103+) If field 23B contains SPRI, SSTD or SPAY, field 57a can be used with option A, option C or option D. In addition, in option D, subfield 1, Party Identifier, (['/'<DC>]['/'34x] 'CRLF') must be present. If field 23B is ... SPRI, SSTD or SPAY Then field 57a is ... Allowed only with options A, C or D (in option D, Party Identifier ['/'<DC>]['/'34x] 'CRLF' is mandatory) Optional

Other code MT 564

If the message is a replacement (:23G::REPL) or an eligible balance notification (:23G::REPE), then the message cannot contain entitlements; that is, in field :25D::PROC, the code word ENTL is not allowed. Sequence A if field :23G: is ... REPL REPE Then in field :25D::PROC the code word ENTL is ... Not allowed

Note:
E10

Rule 209 must be applied even if the DSS is present in field :25D::PROC.

MTs 103 (not 103+) If field 23B contains SPRI, SSTD or SPAY, subfield 1, Account, in field 59a is mandatory. MTs 102+, 103+, 104 and 107 Subfield 1, Account, of field 59a is mandatory.

Note:
E11 MT 564

Rule 210 takes precedence over rule 119 (MTs: 102+, 103+).

If the message is an additional business process (:23G::ADDB) then sequence D Corporate Action Details is mandatory, and in sequence D, field :22F::ADDB is mandatory, only one occurrence is allowed, and it must contain the code word CLAI (Claim or Compensation), TAXR (Tax Refund) or REVR (Notification or Reversal). Sequence A if field :23G: is ... ADDB Then sequence D is ... Mandatory And in sequence D field :22F::ADDB is ... Mandatory, only one occurrence And in sequence D field :22F::ADDB// must be ... CLAI, or TAXR, or REVR

Note:
E12

Rule 211 must be applied even if the DSS is present in field :22F::ADDB.

MT 103 (not 103+) Either field 70 or 77T, but not both, may be present. If field 70 is ... Present Not present Then field 77T is ...

94

Error Codes

Chapter 3 Alphanumeric Codes

If field 70 is ... Not present E13 MTs 102 and 102+ Optional

Then field 77T is ...

If field 71A in sequence A contains OUR, then field 71F is not allowed and field 71G is optional in any occurrence of sequence B. In sequence A If field 71A is ... OUR In each occurrence of sequence B Then field(s) 71F is(are) ... Not allowed And field 71G is ... Optional

If field 71A in sequence B contains OUR, then field 71F is not allowed and field 71G is optional in the same occurrence of sequence B. In sequence B If field 71A is ... OUR In the same occurrence of sequence B Then field(s) 71F is(are) ... Not allowed And field 71G is ... Optional

Note:

See Error codes D20, D50 and E15.

MTs 103 and 103+ If field 71A contains OUR, then field 71F is not allowed and field 71G is optional. If field 71A is ... OUR Then field 71F is ... Not allowed And field 71G is ... Optional

Note:
E14

See Error codes D50 and E15.

MTs 528 and 529 If field :22F::FXCX//FXNO or FXYE is present in sequence C, then the message must be a cancellation, that is, Function of the Message in sequence A (field 23G) is CANC. If field :22F::FXCX//SINO is present in sequence C, then the message must be new, that is, Function of the Message in sequence A (field 23G) is NEWM: Sequence C if field :22F::FXCX is ... [1] FXNO FXYE SINO Not present
[1]

In sequence A then field :23G:4!c is ... CANC CANC NEWM NA

If the Data Source Scheme is present in field :22F::FXCX// then the conditional rule does not apply.

MTs 540, 541, 542 and 543 If field :22F::FXCX//FXNO or FXYE is present in sequence E, then the message must be a cancellation, that is, Function of the Message in sequence A (field 23G) is CANC. If field :22F::FXCX//SINO is present in sequence E, then the message must be new, that is, Function of the Message in sequence A (field 23G) is NEWM:

23 July 2010

95

FIN

Sequence E if field :22F::FXCX [1] FXNO FXYE SINO Not present

[1]

In sequence A then field :23G:4!c is ... CANC CANC NEWM NA

If the Data Source Scheme is present in field :22F::FXCX// then the conditional rule does not apply.

E15

MTs 102 and 102+ If field 71A in sequence A contains BEN, then at least one occurrence of field 71F is mandatory in each occurrence of sequence B and field 71G is not allowed. In sequence A If field 71A is ... BEN In each occurrence of sequence B Then field(s) 71F is(are) ... Mandatory And field 71G is ... Not allowed

If field 71A in sequence B contains BEN, then at least one occurrence of field 71F is mandatory in the same occurrence of sequence B and field 71G is not allowed. In sequence B If field 71A is ... BEN In the same occurrence of sequence B Then field(s) 71F is(are) ... Mandatory And field 71G is ... Not allowed

Note: See Error codes D20, D50 and E13. Error code D20 takes precedence over Error codes D50, E13 and E15.
MTs 103 and 103+ If field 71A contains BEN, then at least one occurrence of field 71F is mandatory and field 71G is not allowed. If field 71A is ... BEN Then field 71F is ... Mandatory (at least one occurrence) And field 71G is ... Not allowed

Note:
E16

See Error codes D50 and E13.

MTs 103 and 103+ If field 23B contains SPRI, field 56a must not be used. If field 23B is ... SPRI Not allowed Then field 56a is ...

E17

MT 103 (not 103+) If field 23B contains SSTD or SPAY, field 56a can be used with either option A or option C. If option C is used, it must contain a clearing code.

96

Error Codes

Chapter 3 Alphanumeric Codes

If field 23B is ... SSTD or SPAY Not = SPRI, SSTD and SPAY E18 MT 103 (not 103+)

Then field 56a is ... Allowed with option A or C (if option C: the first 2 characters of first line must be //) Optional

If any field 23E contains CHQB, subfield 1, Account, in field 59a is not allowed. E19 E20 E21 E22 E23 E24 Available. Available. Available. Available. Available. MT 564 If in all occurrences of sequence E, subsequence E1, and subsequence E2, are not present, then in sequence D field :98a::PAYD is optional, in all other cases, field 98a::PAYD, in sequence D, is not allowed. If And (in the message) sequence subsequence E1 is ... D is ... Present Present Present Not present Not present Not present E25 MT 256 If field 37J is present, then field 71G must also be present. Sequence B If field 37J is ... Present Not present E26 MT 256 If field 71L is present in sequence C, then the amount specified in field 71L must be equal to the sum of all occurrences of field 71F in sequence B. Mandatory Optional Then field 71G is ... NA And (in the message) subsequence E2 is ... Present Not present Present Not present NA Then in sequence D, field :98a::PAYD is ... Not allowed Not allowed Not allowed Optional NA

23 July 2010

97

FIN

E27

MT 256 If field 71J is present in sequence C, then the amount specified in field 71J must be equal to the sum of all occurrences of field 71G in sequence B.

E28

MT 256 Field 21 must be present either in sequence A or in each occurrence of sequence B but not in both. Sequence A if field 21 is ... Present Not present Not allowed Mandatory in each occurrence of sequence B Sequence B then field 21 is ...

E29

MT 256 If field 71F is present in any occurrence of sequence B, then field 71L must be present in sequence C, and vice versa if field 71F is absent from all occurrences of sequence B, then field 71L is not allowed in sequence C. Sequence B if field 71F is ... Present in any occurrence Not present in any occurrence Mandatory Not allowed Sequence C then field 71L is ...

E30

MT 256 If field 71G is present in any occurrence of sequence B, then field 71J must be present in sequence C, and vice versa if field 71G is absent from all occurrences of sequence B, then field 71J is not allowed in sequence C. Sequence B if field 71G is ... Present in any occurrence Not present in any occurrence Mandatory Not allowed Sequence C then field 71J is ...

E31

MT 256 If field 71H is present in any occurrence of sequence B, then field 71K must be present in sequence C, and vice versa if field 71H is absent from all occurrences of sequence B, then field 71K is not allowed in sequence C. Sequence B if field 71H is ... Present in any occurrence Not present in any occurrence Mandatory Not allowed Sequence C then field 71K is ...

E32

MT 256 If field 71K is present in sequence C, then the amount specified in field 71K must be equal to the sum of all occurrences of field 71H in sequence B.

98

Error Codes

Chapter 3 Alphanumeric Codes

E33

MT 364 The presence of sequences B and E depends on subfield 1 of field 23A in sequence A as follows: Sequence A if subfield 1, of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER COLLARSLLR Then sequence B is ... Then sequence E is ...

Mandatory Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed

Mandatory Not allowed Not allowed Mandatory Not allowed Not allowed Not allowed Not allowed Not allowed Not allowed

Note: See Error code E34 for additional subsequence(s) and field(s) semantic checks.
MT 365 The presence of sequences B and E depends on subfield 1 of field 23A in sequence A as follows: Sequence A if subfield 1, of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT Then sequence B is ... Then sequence E is ...

Mandatory Not allowed Mandatory Not allowed

Mandatory Not allowed Not allowed Mandatory

Note: See Error code E34 for additional subsequence(s) and field(s) semantic checks.
E34 MT 364 In sequence A, the presence of fields 32G and 22D and, in sequences B and E, the presence of field 37P depend on field 22B in sequence A as follows: Sequence A If field 22B is ... PTRC PTRM Then field 32G is ... Mandatory Mandatory Then field 22D is ... Mandatory Mandatory If sequence B is If sequence E is present, then present, then field 37P is ... field 37P is ... Mandatory Not allowed Mandatory Not allowed

23 July 2010

99

FIN

Sequence A If field 22B is ... RCPN TERM Then field 32G is ... Not allowed Not allowed Then field 22D is ... Mandatory Not allowed

If sequence B is If sequence E is present, then present, then field 37P is ... field 37P is ... Mandatory Not allowed Mandatory Not allowed

Note:
MT 365

The presence of sequences B and E is determined by Error code E33.

In sequence A, the presence of fields 32G, 33E and 22D and, in sequences B and E, the presence of field 37P, depend on field 22B in sequence A as follows: Sequence A If field 22B is ... Then field 32G is ... Then field 33E is ... Then field 22D is ... If sequence B is present, then field 37P is ... Mandatory Not allowed Mandatory Not allowed If sequence E is present, then field 37P is ... Mandatory Not allowed Mandatory Not allowed

PTRC PTRM RCPN TERM

Mandatory Mandatory Not allowed Not allowed

Mandatory Mandatory Not allowed Not allowed

Mandatory Mandatory Mandatory Not allowed

Note:
E35 MT 306

The presence of sequences B and E is determined by Error code E33.

In sequences C (if present) and E, (if present - see rule 132), and J (if present), if field 56a is not present, then field 86a in the same sequence C, E or J is not allowed; otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Sequence E If field 56a is ... Not present Present Not allowed Optional Sequence J If field 56a is ... Not present Present Not allowed Optional Then field 86a is ... Then field 86a is ... Then field 86a is ...

Note:

See also Error code D32.

100

Error Codes

Chapter 3 Alphanumeric Codes

MT 320 In sequences C, D, E (if present), F (if present), and I (if present), if field 56a is not present, then field 86a in the same sequence is not allowed; otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Sequence D If field 56a is ... Not present Present Not allowed Optional Sequence E If field 56a is ... Not present Present Not allowed Optional Sequence F If field 56a is ... Not present Present Not allowed Optional Sequence I If field 56a is ... Not present Present MT 330 In sequences C, D, E (if present) and F (if present), if field 56a is not present, then field 86a in the same sequence is not allowed; otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Sequence D If field 56a is ... Not present Present Not allowed Optional Then field 86a is ... Then field 86a is ... Not allowed Optional Then field 86a is ... Then field 86a is ... Then field 86a is ... Then field 86a is ... Then field 86a is ...

23 July 2010

101

FIN

Sequence E If field 56a is ... Not present Present Not allowed Optional Sequence F If field 56a is ... Not present Present MT 340 In sequences C, D, and F, if field 56a is not present, then field 86a in the same sequence is not allowed; otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Sequence D If field 56a is ... Not present Present Not allowed Optional Sequence F If field 56a is ... Not present Present MTs 341 and 350 In sequence C, if field 56a is not present, then field 86a is not allowed; otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Then field 86a is ... Not allowed Optional Then field 86a is ... Then field 86a is ... Then field 86a is ... Not allowed Optional Then field 86a is ... Then field 86a is ...

102

Error Codes

Chapter 3 Alphanumeric Codes

MTs 360, 361, 362, 364 and 365 Within a specific sequence, or within an internal loop, the presence of field 86a depends on field 56a as follows: If, in a sequence, or an internal loop, field 56a is ... Present Not present MT 620 In sequences C, D, E (if present) and F (if present), if field 56a is not present, then field 86a in the same sequence is not allowed, otherwise field 86a is optional. Sequence C If field 56a is ... Not present Present Not allowed Optional Sequence D If field 56a is ... Not present Present Not allowed Optional Sequence E If field 56a is ... Not present Present Not allowed Optional Sequence F If field 56a is ... Not present Present E36 MTs 364 and 365 In sequence A, if field 22D contains OTHR, field 37N must be present. E37 MT 509 Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2. Not allowed Optional Then field 86a is ... Then field 86a is ... Then field 86a is ... Then field 86a is ... Then, in the same sequence, or the same internal loop, field 86a is ... Optional Not allowed

23 July 2010

103

FIN

In each occurrence of subsequence A2 Status In each occurrence of subsequence A2a Reason (if present) if field :24B:: is ... :24B::REJT Then in subsequence A2 Status field :25D:: must be ... [1] :25D::CPRC//REJT or :25D::IPRC//REJT or :25D::RPRC//REJT :25D::MTCH//NMAT :25D::AFFM//NAFI :25D::CPRC//REPR or :25D::IPRC//REPR or :25D::RPRC//REPR

:24B::NMAT :24B::NAFI :24B::REPR

[1]

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

MT 537 Within each occurrence of subsequence B1, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence B. In each occurrence of sequence B Status In each occurrence of subsequence B1 Reason (if present) if field :24B:: is ... :24B::CAND :24B::CANP :24B::CGEN :24B::PACK :24B::NMAT :24B::PEND :24B::PENF :24B//REPR :24B::PPRC
[1]

Then in sequence B Status, field :25D:: must be ... [1] :25D::IPRC//CAND :25D::IPRC//CANP :25D::IPRC//CGEN :25D::IPRC//PACK :25D::MTCH//NMAT or :25D::INMH//NMAT :25D::SETT//PEND :25D::SETT//PENF :25D::IPRC//REPR :25D::IPRC//PPRC

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

Within each occurrence of subsequence C3a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence C3 Status: In each occurrence of sequence C3 Status In each occurrence of subsequence C3a Reason (if present) if field :24B:: is ... :24B::CAND Then in sequence C3 Status, field :25D:: must be ... [1] :25D::IPRC//CAND

104

Error Codes

Chapter 3 Alphanumeric Codes

In each occurrence of sequence C3 Status In each occurrence of subsequence C3a Reason (if present) if field :24B:: is ... :24B::CANP :24B::CGEN :24B::PACK :24B::NMAT :24B::PEND :24B::PENF :24B::REPR :24B::PPRC
[1]

Then in sequence C3 Status, field :25D:: must be ... [1] :25D::IPRC//CANP :25D::IPRC//CGEN :25D::IPRC//PACK :25D::MTCH//NMAT or :25D::INMH//NMAT :25D::SETT//PEND :25D::SETT//PENF :25D::IPRC//REPR :25D::IPRC//PPRC

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

MT 548 Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2. In each occurrence of subsequence A2 Status In each occurrence of subsequence A2a Reason (if present) if field :24B:: is ... :24B::CAND :24B::CANP :24B::CGEN :24B::DEND Then in subsequence A2 Status field :25D:: must be ... [1] :25D::IPRC//CAND or :25D::CPRC//CAND :25D::IPRC//CANP or :25D::CPRC//CANP :25D::IPRC//CGEN :25D::CPRC//DEND or :25D::CALL//DEND or :25D::TPRC//DEND :25D::MTCH//NMAT or :25D::INMH//NMAT :25D::IPRC//PACK or :25D::CPRC//PACK or :25D::TPRC//PACK :25D::SETT//PEND :25D::SETT//PENF :25D::IPRC//REPR

:24B::NMAT :24B::PACK

:24B::PEND :24B::PENF :24B::REPR

23 July 2010

105

FIN

In each occurrence of subsequence A2 Status In each occurrence of subsequence A2a Reason (if present) if field :24B:: is ... :24B::REJT Then in subsequence A2 Status field :25D:: must be ... [1] :25D::IPRC // REJT or :25D::CPRC // REJT or :25D::SPRC // REJT or :25D::TPRC//REJT :25D::CALL//CACK :25D::IPRC//PPRC :25D::TPRC//MOPN

:24B::CACK :24B::PPRC :24B::MOPN

[1]

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

MT 549 Within each occurrence of sequence B, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of the same occurrence of sequence B. In each occurrence of sequence B If field :24B:: is present and is ... Then field :25D:: is mandatory and must be ... [1] :24B::NMAT :24B::PEND :25D::MTCH//NMAT or :25D::INMH//NMAT :25D::MTCH//NMAT or :25D::EPRC//PEND or :25D::SETT//PEND or :25D::RPRC//PEND :25D::SETT//PENF :25D::IPRC//REJT or :25D::CPRC//REJT or :25D::RPRC//REJT or :25D::RERC//REJT or :25D::REST//REJT or :25D::TPRC//REJT :25D::CPRC//DEND or :25D::RPRC//DEND or :25D::CALL//DEND or :25D::TPRC//DEND :25D::IPRC//CAND or :25D::CPRC//CAND :25D::IPRC//CANP or :25D::CPRC//CANP :25D::IPRC//CGEN :25D::AFFM//NAFI

:24B::PENF :24B::REJT

:24B::DEND

:24B::CAND :24B::CANP :24B::CGEN :24B::NAFI

106

Error Codes

Chapter 3 Alphanumeric Codes

In each occurrence of sequence B If field :24B:: is present and is ... Then field :25D:: is mandatory and must be ... [1] :24B::PACK :25D::IPRC//PACK or :25D::CPRC//PACK or :25D::RPRC//PACK or :25D::RERC//PACK or :25D::TPRC//PACK :25D::CALL//CACK :25D::CPRC//REPR or :25D::IPRC//REPR or :25D::RPRC//REPR :25D::IPRC//PPRC :25D::TPRC//MOPN Not applicable

:24B::CACK :24B::REPR

:24B::PPRC :24B::MOPN Field :24B:: is not present

[1]

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

MT 567 Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2 Status. In each occurrence of subsequence A2 Status In each occurrence of subsequence A2a Reason (if present) if field :24B:: is ... :24B::CAND :24B::CANP :24B::PACK :24B::PEND :24B::REJT
[1]

Then in subsequence A2 Status field :25D:: must be ... [1] :25D::IPRC//CAND or :25D::CPRC//CAND :25D::CPRC//CANP :25D::IPRC//PACK or :25D::CPRC//PACK :25D::IPRC//PEND or :25D::EPRC//PEND :25D::IPRC//REJT or :25D::CPRC//REJT

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

MT 584 Within each occurrence of subsequence B2, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of the same occurrence of subsequence B2. In each occurrence of sequence B2 Status If field :24B:: is ... :24B::NMAT Then field :25D:: must be ... [1] :25D::MTCH//NMAT

23 July 2010

107

FIN

In each occurrence of sequence B2 Status If field :24B:: is ... :24B::REJT :24B::NAFI Not present
[1]

Then field :25D:: must be ... [1] :25D::IPRC//REJT :25D::AFFM//NAFI NA

If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

E38

MT 362 The currency code of the fields 33F and 32H in sequence B must be the same. The currency codes of the fields 33F and 32H in sequence D must be the same.

E39

MT 362 In sequences B and D, the presence of fields 37J and 37L depends on subfield 1 of field 23A in sequence A as follows:

Note:

The presence of sequences B and D is determined by Error code E47.

If COLLARBYER or COLLARSLLR is used in the field 23A in sequence A, then: in each sequence B and D that is present, a minimum of one field 37J or 37L must be present if both sequences B and D are present, and if only one letter option is present in the first sequence (for example, 37J is the only 37 <letter-option> used in sequence B), then the other letter option must be present in the second sequence. (In this case, 37L must be present in sequence D.)
1. If sequences B and D are present: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER In sequence B field 37J must be ... Not allowed Optional Not allowed Optional Mandatory Not allowed Not allowed Not allowed Present Present Not present In sequence B field 37L must be ... Not allowed Optional Not allowed Optional Not allowed Not allowed Mandatory Not allowed Present Not present Present And in sequence D field 37J must be ... Not allowed Optional Optional Not allowed Not allowed Mandatory Not allowed Not allowed And in sequence D field 37L must be ... Not allowed Optional Optional Not allowed Not allowed Not allowed Not allowed Mandatory

Either 37J or 37L or both is/are mandatory Optional Mandatory Mandatory Optional

108

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if subfield 1 of field 23A is ... COLLARSLLR

In sequence B field 37J must be ... Present Present Not present

In sequence B field 37L must be ... Present Not present Present

And in sequence D field 37J must be ...

And in sequence D field 37L must be ...

Either 37J or 37L or both is/are Mandatory Optional Mandatory Mandatory Optional

2. If sequence B is not present: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER COLLARSLLR 3. If sequence D is not present: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER COLLARSLLR In sequence B field 37J must be ... Not allowed Optional Not allowed Optional Mandatory Not allowed Not allowed Not allowed In sequence B field 37L must be ... Not allowed Optional Not allowed Optional Not allowed Not allowed Mandatory Not allowed In sequence D field 37J must be ... Not allowed Optional Optional Not allowed Not allowed Mandatory Not allowed Not allowed In sequence D field 37L must be ... Not allowed Optional Optional Not allowed Not allowed Not allowed Not allowed Mandatory

either 37J or 37L or both is/are mandatory either 37J or 37L or both is/are mandatory

Either 37J or 37L or both is/are mandatory Either 37J or 37L or both is/are mandatory

23 July 2010

109

FIN

E40

MT 340 In sequence A, the presence of field 14C depends on the value of subfield 1 of field 77H as follows: Sequence A If subfield 1 of field 77H is ... ISDA Not = ISDA MT 361 The content of field 77H, in sequence A, determines the presence of: fields 14G and 37R in the subsequences C1 and F1 subsequences C2 and F2. Sequence A if subfield 1 of field 77H is ... AFB Then if subsequence C1 is present, fields 14G and 37R are ... Not allowed Then if subsequence F1 is present, fields 14G and 37R are ... Not allowed Then subsequences C2 and F2 are ... Mandatory Not allowed Then field 14C is ...

Not allowed

Note: 1. The presence of subsequences B, C, E and F is determined by Error code E43. 2. The presence of subsequences C1, C2, F1 and F2 is determined by Error code E41.
E41 MT 340 In sequence B, the presence of subsequence B1 depends on the value of subfield 1 of field 77H in sequence A as follows: Sequence A if subfield 1 of field 77H is ... AFB DERV EMA FRABBA ISDA OTHR MTs 360 and 361 The presence of field 37U in sequences B and E and the presence of subsequences B1, C1, C2, C3, E1, F1, F2 and F3 depend on the content of subfield 1 of field 77H and on the content of field 14F as documented in the following five tables. According to the Codes D58 and E43 the following combinations of the sequences B, C, E and F are allowed: Error code D58, MT 360: BE(5), CF(1 and 2), BF(3), CE(4), C(1) and F(2). Mandatory Not allowed Not allowed Mandatory Not allowed Not allowed Then subsequence B1 is ...

110

Error Codes

Chapter 3 Alphanumeric Codes

Error code E43, MT 361: BE(5), CF(1 and 2), BF(3) and CE(4).

Note: 1. See Error codes D45, D59 and E40 for additional subsequence(s) and field(s) conditional checks. 2. For each valid sequence combination, a table (below) indicates the checks to apply. 3. For the combination CF, both tables 1 and 2 must be applied.
1. If sequence C is present: If sequence C is present and ... In sequence A if subfield 1 of field 77H is ... ISDA And in sequence C if field 14F is ... FRF-TAM-CDC FRF-T4M-CDC FRF-T4M-CDCCOMP FRF-TAG-CDC FRF-TAG-CDCCOMP FRF-TMP-CDCAVERAG FRF-SWAP-AMR FRF-SWAP-TMP-IF FRF-SWAP-TMP-M FRF-SWAP-T4M-AMR FRF-CAP-TAM FRF-CAP-T4M FRF-FLOOR-TAM FRF-FLOOR-T4M Then subsequences C1, C2 and C3 are ...

Not allowed

AFB

Not allowed

Else 2. If sequence F is present: If sequence F is present and ... In sequence A if subfield 1 of field 77H is ... ISDA And in sequence F if field 14F is ... FRF-TAM-CDC FRF-T4M-CDC FRF-T4M-CDCCOMP FRF-TAG-CDC FRF-TAG-CDCCOMP FRF-TMP-CDCAVERAG FRF-SWAP-AMR FRF-SWAP-TMP-IF FRF-SWAP-TMP-M FRF-SWAP-T4M-AMR FRF-CAP-TAM FRF-CAP-T4M FRF-FLOOR-TAM FRF-FLOOR-T4M

C1 is mandatory C2 and C3 are optional

Then subsequences F1, F2 and F3 are ...

Not allowed

AFB

Not allowed

23 July 2010

111

FIN

If sequence F is present and ... In sequence A if subfield 1 of field 77H is ... Else 3. If sequences B and F are present: If sequences B and F are present and ... Sequence A if subfield 1 of field 77H is ... ISDA Sequence F and if field 14F is ... FRF-TAM-CDC FRF-T4M-CDC FRF-T4MCDCCOMP FRF-TAG-CDC FRF-TAGCDCCOMP FRF-TMPCDCAVERAG FRF-SWAPAMR FRF-SWAPTMP-IF FRF-SWAPTMP-M FRF-SWAPT4M-AMR FRF-CAP-TAM FRF-CAP-T4M FRF-FLOORTAM FRF-FLOORT4M And subsequence F1, F2 and F3 are ... Not allowed And in sequence F if field 14F is ... Then subsequences F1, F2 and F3 are ...

F1 is mandatory F2 and F3 are optional

Then subsequence B1 is ...

Sequence B and field 37U is ...

Not allowed

Mandatory

AFB

Not allowed

Mandatory

Not allowed

Else

Mandatory

Optional

F1 is mandatory F2 and F3 are optional

112

Error Codes

Chapter 3 Alphanumeric Codes

4. If sequences C and E are present: If sequences C and E are present and ... Sequence A if subfield 1 of field 77H is ... ISDA Sequence C if field 14F is ... FRF-TAM-CDC FRF-T4M-CDC FRF-T4MCDCCOMP FRF-TAG-CDC FRF-TAGCDCCOMP FRF-TMPCDCAVERAG FRF-SWAPAMR FRF-SWAPTMP-IF FRF-SWAPTMP-M FRF-SWAPT4M-AMR FRF-CAP-TAM FRF-CAP-T4M FRF-FLOORTAM FRF-FLOORT4M And subsequences C1, C2 and C3 are ... Not allowed

Then subsequence E1 is ...

Sequence E and field 37U is ...

Not allowed

Mandatory

AFB

Not allowed

Mandatory

Not allowed

Else

Mandatory

Optional

C1 is mandatory C2 and C3 are optional

5. If sequences B and E are present: Subsequence B1 is ... Mandatory Subsequence E1 is ... Mandatory E42 MT 360 In sequences C and F, the presence of fields 37J and 37L depends on subfield 1 of field 23A in sequence A as follows: Sequence B if field 37U is ... Optional Sequence E if field 37U is ... Optional

Note:

The presence of sequences C and F is determined by Error code D58.

If COLLARBYER or COLLARSLLR is used in the field 23A in sequence A, then: In each sequence C and F that is present, a minimum of one field 37J or 37L must be present

23 July 2010

113

FIN

If both sequences C and F are present, and if only one letter option is present in the first sequence (for example, 37J is the only 37 <letter-option> used in sequence C), then the other letter option must be present in the second sequence. (In this case, 37L must be present in sequence F.)
1. If sequences C and F are present Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER Sequence C field 37J must be ... NA Optional NA Optional Mandatory NA Not allowed NA Present Present Not present COLLARSLLR Present Present Not present 2. If sequence C is not present: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER NA Optional Optional NA NA Mandatory NA Not allowed NA per rule 158 Sequence F field 37J must be ... NA Optional Optional NA NA Not allowed NA Mandatory Sequence F field 37L must be ... Sequence C field 37L must be ... NA Optional NA Optional Not allowed NA Mandatory NA Present Not present Present Present Not present Present Sequence F and field 37J must be ... NA Optional Optional NA NA Mandatory NA Not allowed Sequence F and field 37L must be ... NA Optional Optional NA NA Not allowed NA Mandatory

Either 37J or 37L or both is/are mandatory Optional Mandatory Mandatory Optional

Either 37J or 37L or both is/are mandatory Optional Mandatory Mandatory Optional

114

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if subfield 1 of field 23A is ... COLLARSLLR 3. If sequence F is not present: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT CAPBUYER CAPSELLER FLOORBUYER FLOORSLLER COLLARBYER COLLARSLLR E43 MT 361 NA

Sequence F field 37J must be ... NA per rule 158

Sequence F field 37L must be ...

Sequence C field 37J must be ... NA

Sequence C field 37L must be ...

Optional NA Optional Mandatory NA Not allowed NA NA per rule 158 NA per rule 158

Optional NA Optional Not allowed NA Mandatory NA

Depending on the value in subfield 1 of field 23A in sequence A, only the following combinations of the optional sequences B, C, E and F are allowed: Sequence A if subfield 1 of field 23A is ... FIXEDFIXED FLOATFLOAT FLOATFIXED FIXEDFLOAT Then sequence B is ... Mandatory Not allowed Mandatory Not allowed Then sequence C is ... Not allowed Mandatory Not allowed Mandatory Then sequence E is ... Mandatory Not allowed Not allowed Mandatory Then sequence F is ... Not allowed Mandatory Mandatory Not allowed

Note: See Error codes E40 and E41 for additional subsequence(s) and field(s) semantic checks.
E44 MT 103 (not 103+) If field 56a is not present, no field 23E may contain TELI or PHOI. If field 56a is ... Not present Then in each occurrence of field 23E, subfield 1 must not contain ... TELI or PHOI

23 July 2010

115

FIN

E45

MT 103 (not 103+) If field 57a is not present, no field 23E may contain TELE or PHON. If field 57a is ... Not present Then in each occurrence of field 23E, subfield 1 must not contain ... TELE or PHON

E46

MTs 101 and 207 In each occurrence of sequence B, if field 23E is repeated, it must not contain the same code more than once, with the exception of OTHR. OTHR may be repeated. MTs 103 and 103+ If field 23E is repeated, it must not contain the same code more than once.

E47

MT 350 If sequence D is present, at least one of the subsequences D1 or D2 must be present. In sequence D, if subsequence D1 is ... Present Not present MT 362 At least one of the sequences B or D must be present. If sequence B is ... Present Not present Optional Mandatory Then sequence D is ... Optional Mandatory Then subsequence D2 is ...

E48

MT 362 At least one of the sequences C or E must be present. If sequence C is ... Present Not present Optional Mandatory Then sequence E is ...

Note:
MT 504

See Error code E49.

In each occurrence of subsequence C1a, the presence of subsequence C1a1 depends on the presence of field :22F::STCO//NSSP as follows: In each occurrence of subsequence C1a, if field :22F::STCO//NSSP is ... [1] Not present Present
[1]

In the same occurrence of subsequence C1a, then subsequence C1a1 is ... Optional Mandatory

This Error code does not apply if the Data Source Scheme is present.

116

Error Codes

Chapter 3 Alphanumeric Codes

MTs 505 and 507 In each occurrence of subsequence B1a, the presence of subsequence B1a1 depends on the presence of field :22F::STCO//NSSP as follows: In each occurrence of subsequence B1a, if field :22F::STCO//NSSP is ... Not present Present
[1]

[1]

In the same occurrence of subsequence B1a, then subsequence B1a1 is ... Optional Mandatory

This Error code does not apply if the Data Source Scheme is present.

E49

MT 362 When subfield 2 of field 23A contains NET, either sequence C or E must be present, but not both. In these circumstances, this error code takes precedence over Error code E48. MT 504 In each occurrence of subsequence C2a, the presence of subsequence C2a1 depends on the presence of field :22F::STCO//NSSP as follows: In each occurrence of subsequence C2a, if field :22F::STCO//NSSP is ... Not present Present
[1]

[1]

In the same occurrence of subsequence C2a, then subsequence C2a1 is ... Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

MT 505 In each occurrence of subsequence B2a, the presence of subsequence B2a1 depends on the presence of field :22F::STCO//NSSP as follows: In each occurrence of subsequence B2a, if field :22F::STCO//NSSP is ... Not present Present
[1]

[1]

In the same occurrence of subsequence B2a, then subsequence B2a1 is ... Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

MT 507 In each occurrence of subsequence B1b, the presence of subsequence B1b1 depends on the presence of field :22F::STCO//NSSP as follows: In each occurrence of subsequence B1b, if field :22F::STCO//NSSP is ... [1] Not present Present
[1]

In the same occurrence of subsequence B1b, then subsequence B1b1 is ... Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

E50

MT 362 When subfield 2 of field 23A contains NET, fields 30F to 57a in sequence C or E must occur only once. This means that field 18A in sequence C must contain 1 (see Error code E48).

23 July 2010

117

FIN

Note:
MT 504

See also Error code D96.

In sequence D, the presence of subsequence D1 depends on the presence of field :22F::STCO//NSSP as follows: Sequence D if field :22F::STCO//NSSP is ... [1] Not present Present
[1]

Then subsequence D1 is ...

Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

MT 505 In sequence C, the presence of subsequence C1 depends on the presence of field :22F::STCO//NSSP as follows: Sequence C if field :22F::STCO//NSSP is ... Not present Present
[1]

Then subsequence C1 is ...

[1]

Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

E51

MT 362 When subfield 2 of field 23A contains GROSS, fields 30F to 57a in sequence C and E cannot occur more than three times. This means that field 18A in sequence C must contain a value less than 4 (see Error code E48).

Note:
MT 504

See also Error code D96.

In sequence E, the presence of subsequence E1 depends on the presence of field :22F::STCO//NSSP as follows: Sequence E if field :22F::STCO//NSSP is ... [1] Not present Present
[1]

Then subsequence E1 is ...

Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

MT 505 In sequence D, the presence of subsequence D1 depends on the presence of field :22F::STCO//NSSP as follows: Sequence D if field :22F::STCO//NSSP is ... Not present Present
[1]

Then subsequence D1 is ...

[1]

Optional Mandatory

This error code does not apply if the Data Source Scheme is present.

118

Error Codes

Chapter 3 Alphanumeric Codes

E52

MTs 502, 514, 518, 528 and 529 In subsequence C1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence C1 If field :95a::PSET is ... Present Not present MTs 513 and 515 In subsequence D1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence D1 If field :95a::PSET is ... Present Not present MT 536 In subsequence B1a2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence B1a2a If field :95a::PSET is ... Present Not present MT 537 In subsequence B2b1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence B2b1 If field :95a::PSET is ... Present Not present Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional

In subsequence C2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sequence. Subsequence C2a If field :95a::PSET is ... Present Not present Then field :97a::SAFE is ... Not allowed within the same occurrence Optional

MTs 540, 541, 542, 543, 544, 545, 546, 547 and 548 In subsequence E1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence.

23 July 2010

119

FIN

Subsequence E1 If field :95a::PSET is ... Present Not present MT 548 In subsequence B1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence B1 If field :95a::PSET is ... Present Not present MT 575 In subsequence B1a4, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence B1a4 If field :95a::PSET is ... Present Not present MT 586 In subsequence B5a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence B5a If field :95a::PSET is ... Present Not present E53 MT 502 In sequence B, if field :22H::BUSE//SWIT is present, then subsequence A1 is mandatory, and field :20C::PREV must be present in a minimum of one occurrence of subsequence A1. Sequence B If field :22H::BUSE//SWIT is ... Present Subsequence A1 Then subsequence is ... Mandatory, that is, minimum one occurrence of A1 Optional And field :20C::PREV is ... Mandatory, that is, must be present in minimum one occurrence of A1 Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional Then field :97a::SAFE is ... Not allowed within the same occurrence Optional

Not present

120

Error Codes

Chapter 3 Alphanumeric Codes

MT 515 In sequence C, if field :22H::BUSE//SWIT is present, then field :20C::PREV must be present in a minimum of one occurrence of subsequence A1. Sequence C if field :22H::BUSE//SWIT is ... Present Not present MT 575 In subsequence C2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. Subsequence C2a If field :95a::PSET is ... Present Not present E54 MT 101 In each occurrence of sequence B, the presence of fields 33B and 21F is dependent on the presence and value of fields 32B and 23E as follows: In each occurrence of sequence B If amount in field 32B is ... Equal to zero And field 23E is ... Present and code = EQUI Present and code not =EQUI Not present Not equal to zero E55 MT 306 In sequence B, the use of option F for field 30a depends on the value of field 12E in sequence A as follows: Sequence A if field 12E is ... EURO Not EURO E56 MTs 535 and 536 If in sequence A, field :17B::CONS contains Y, then in every occurrence of sequence B, field :97a::SAFE and field :17B::ACTI are mandatory. Mandatory Optional Sequence B then field 30F is ... NA Then field 33B is ... Mandatory Not allowed Not allowed Optional And field 21F is ... Optional Not allowed Not allowed Optional Then field :97a::SAFE is ... Not allowed in the same subsequence Optional Then field :20C::PREV is ... Mandatory, that is, must be present in minimum one occurrence A1 Optional

23 July 2010

121

FIN

This error code applies only when sequence B is present as per Error code E66, that is, in sequence A, field :17B::ACTI contains Y. Sequence A if field :17B::ACTI is ... Then sequence B is ... And sequence A if field :17B::CONS is ... Then in every occurrence of sequence B field :97a::SAFE and field :17B::ACTI are ... Mandatory Not allowed NA

Mandatory, that is, at least one occurrence Not allowed

Y N NA

N E57 MTs 101, 210 and 910

Identifier Code must be a non-financial institution BIC.

Note: This error code applies to all types of BICs referenced in a FIN message, that is, SWIFT BIC, Non-SWIFT BIC, Master, Synonym, Live destinations and Test and Training destinations. This error code is the opposite of Error code C05.
This error code applies to the following fields: MT 101 A A B B 210 910 E58 MT 502 In sequence B, either field :36B::ORDR or field :19A::ORDR must be present, but not both. Sequence B If field :36B::ORDR is ... Present Not present MT 509 In sequence B, either a quantity (field 36B::) or an amount (field 19A::) must be present, but not both: Sequence B If field :36B:: is ... Present Not present Then field :19A:: is ... Not allowed Mandatory Then field :19A::ORDR is ... Not allowed Mandatory Sequence 50C 50G 50C 50G 50C 50A Field

122

Error Codes

Chapter 3 Alphanumeric Codes

MT 576 In each occurrence of subsequence B2, either an ordered quantity (field :36B::ORDR) or an ordered amount (field :19A::ORDR) must be present, but not both; in addition, if field 36B is present then field 19A must not be present, and vice versa if field 19A is present then field 36B must not be present. In each occurrence of subsequence B2 if field :36B:: is ... Present Not present E59 MT 517 If field 23G does not contain CANC, then field 13A must be present and contain 515 in minimum one occurrence of subsequence A1. Sequence A if subfield 1 of field 23G is ... CANC Not = CANC
[1]

In the same occurrence of subsequence B2 then field :36B::ORDR is ... Mandatory NA

In the same occurrence of subsequence B2 and field :19A: is ... Not allowed :19A::ORDR is mandatory

Then in at least one occurrence of subsequence A1 field 13A is ... Optional Mandatory and must contain 515 [1]

It does not need to be present in all occurrences of A1.

E60

MT 506 In each occurrence of subsequence D1, the presence of field :70C::RATS depends on the presence of field :94B::RATS as follows: In each occurrence of subsequence D1 If field :94B::RATS is ... Present Not present MT 569 In each occurrence of subsequence C1a1A, the presence of field :70C::RATS depends on the presence of field :94B::RATS as follows: In each occurrence of subsequence C1a1A if field :94B::RATS is ... Present Not present In the same occurrence of subsequence C1a1A then field :70C::RATS is ... Mandatory Not allowed Then field :70C::RATS is ... Mandatory Not allowed

E61

MTs 514, 528 and 529 When field :22F::PRIC is present, field :90a::DEAL must also be present.

23 July 2010

123

FIN

Sequence B If field :22F::PRIC is ... Present Not present E62 MTs 502, 514, 518, 528 and 529 In each subsequence C3, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequence C3 If field :92B::EXCH is ... Present Not present MTs 513 and 515 In subsequence D3, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RES is not allowed. Subsequence D3 If field :92B::EXCH is ... Present Not present Then field :19A::RESU is ... Mandatory Not allowed Then field :19A::RESU is ... Mandatory Not allowed Then field :90a::DEAL is ... Mandatory Optional

MTs 540, 541, 542, 543, 544, 545, 546, 547 and 578 In subsequence E3, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequence E3 If field :92B::EXCH is ... Present Not present MT 564 In subsequence E2, if field :92B::EXCH is present, the corresponding field :19B::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequence E2 If field :92B::EXCH is ... Present Not present Then field :19B::RESU is ... Mandatory Not allowed Then field :19A::RESU is ... Mandatory Not allowed

124

Error Codes

Chapter 3 Alphanumeric Codes

MT 566 In subsequence D2, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19B::RESU is not allowed. Subsequence D2 If field :92B::EXCH is ... Present Not present MT 584 In subsequences B2b2 and C1c2, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequences B2b2 and C1c2 If field :92B::EXCH is ... Present Not present MT 586 In subsequence B5c, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequence B5c If field :92B::EXCH is ... Present Not present MT 588 In (sub)-sequences C2 and E, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same subsequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed. Subsequence C2 If field :92B::EXCH is ... Present Not present Then field :19A::RESU is ... Mandatory Not allowed Sequence E If field :92B::EXCH is ... Present Not present Then field :19A::RESU is ... Mandatory Not allowed Then field :19A::RESU is ... Mandatory Not allowed Then field :19A::RESU is ... Mandatory Not allowed Then field :19B::RESU is ... Mandatory Not allowed

23 July 2010

125

FIN

E63

MTs 587 and 588 In sequence B, it is mandatory to provide an Issue Date/Time (:98a::ISSU) OR a Release Date/ Time (:98a::RELD). Both dates may be provided. Sequence B If field :98a::ISSU is ... Present Not present Optional Mandatory Then field :98a::RELD is ...

E64

MT 502 If the Function of the Message (field :23G:) is CANC and the Ordered Quantity (field :36B::ORDR) is present, then the Quantity to Cancel (field :36B::CANC) must be present in the order details sequence. If the Function of the Message (field :23G:) is CANC and the Ordered Amount (field:19A::ORDR) is present, then the Amount to Cancel (field :19A::CANC) must be present in the order details sequence. If the Function of the Message is not CANC, the Quantity to Cancel and the Amount to Cancel are not allowed. Sequence A if field :23G is ... NEWM REPL CANC Sequence A if field :23G is ... NEWM REPL CANC Sequence B and field :36B::ORDR is ... Present Present Present Sequence B and field :19A::ORDR is ... Present Present Present Sequence B then field :36B::CANC is ... Not Allowed Not Allowed Mandatory Sequence B then field :19A::CANC is ... Not Allowed Not Allowed Mandatory

Note: In sequence B fields 36B::ORDR and 19A::ORDR are mutually exclusive, see rule 258.
MT 527 In sequence A, if field :20C::CLCI is not present, then field :20C::TRCI is mandatory; otherwise field :20C::TRCI is optional. Sequence A If field :20C::CLCI is ... Not present Present E65 MT 527 If sequence A field :22a::COLA// is other than SLEB and sequence B is present, then field :19A::TRAA must be present. Then field :20C::TRCI is ... Mandatory Optional

126

Error Codes

Chapter 3 Alphanumeric Codes

If sequence B is ... Present

And sequence A field :22a::COLA is ... SLEB Not SLEB [1]

Then sequence B field : 19A::TRAA is ... Optional Mandatory NA

Not present
[1]

NA

If DSS is present then conditional rule does not apply.

MT 558 If sequence A field :22a::COLA// is other than SLEB, then in sequence B field :19A::TRAA must be present. Sequence A if field :22a::COLA is ... SLEB Not SLEB [1]
[1]

Then sequence B field :19A::TRAA is ... Optional Mandatory

If DSS is present then conditional rule does not apply.

MT 584 Sequences B and C are mutually exclusive and must not both be present in the same message. Sequence B is ... Present Not present E66 MTs 535, 536, 538 and 586 If field :17B::ACTI in sequence A contains N, then sequence B must not be present; otherwise, sequence B is mandatory. Sequence A if field :17B::ACTI is ... N Y MT 537 In sequence A General Information, if the Activity Flag (field :17B::ACTI) indicates no information to be reported, that is, N, then sequence B Status and sequence C Transactions must not be present. If the Activity Flag (field :17B::ACTI) indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per status (field :22H::STST//STAT), then sequence B Status is mandatory and sequence C Transactions is not allowed. If the Activity Flag (field :17B::ACTI) in sequence A General Information indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per transaction (field :22H::STST//TRAN), then sequence B Status is not allowed and sequence C Transactions is mandatory. Not allowed Mandatory Sequence B is ... Not allowed Optional Sequence C is ...

23 July 2010

127

FIN

Sequence A If field :17B::ACTI is ... N N Y Y MT 569

And sequence A field :22H::STST is ... STAT TRAN STAT TRAN

Then sequence B is ... Not allowed Not allowed Mandatory Not allowed

And sequence C is ... Not allowed Not allowed Not allowed Mandatory

In each occurrence of subsequence C1a1, the presence of subsequence C1a1A depends on the value of field :17B::SECU//<Flag> as follows: In each occurrence of subsequence C1a1 if field :17B::SECU//1!a is ... N Y MT 575 If field :17B::ACTI in sequence A contains N, then sequence B and sequence C must not be present; otherwise, sequences B and C are optional. Sequence A If field :17B::ACTI is ... N Y MT 576 If field :17B::ACTI in sequence A contains N, then sequence B must not be present. Sequence A If field :17B::ACTI is ... N Y E67 MT 535 If field 17B::ACTI//Y is present (see rule C1, Error code E66), and if field :22F::STTY//ACCT is present, then at least one occurrence of subsequence B1 is required. Not allowed Mandatory Sequence B is ... Sequence B is ... Not allowed Optional Sequence C is ... Not allowed Optional In the same occurrence of subsequence C1a1 then subsequence C1a1A is ... Not allowed Mandatory

128

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if field :17B::ACTI is ... Y

Then sequence B is ...

And sequence A, if field :22F::STTY//ACCT is ... Present, and DSS is not present in field :22F::STTY//ACCT

Then subsequence B1 is ...

Mandatory

Mandatory, that is minimum one occurrence must be present in the message [1]

Not present, or DSS is present in field :22F::STTY/.../ACCT N

[1]

Optional

Not allowed

NA

B1 is NOT mandatory in every occurrence of sequence B.

MT 576 Field :97a::SAFE must be present in sequence A, or in all occurrences of subsequence B2c, but not both. Sequence A if field :97a::SAFE is ... Present Not present Then subsequence B2c is ... Optional Mandatory (that is minimum one occurrence of subsequence B2c) [1]
[1]

And in all occurrences of subsequence B2c field :97a::SAFE is ... Not allowed Mandatory

The upper sequences :<B, B2> are also mandatory.

MT 584 Field :97a::SAFE must be present in sequence A, or in all occurrences of subsequence B2b1 in sequence B, or in all occurrences of subsequence C1c1 in sequence C. Considering that sequence A is mandatory, and sequences B and C are optional and mutually exclusive (see Error code E65), since field 97a must be present in one and only one sequence, the following validation is implemented: Sequence A if field :97a::SAFE is ... Present Then subsequence B2b1 or C1c1 is ... Then in subsequence B2b1 or C1c1 field :97a::SAFE is ...

If sequence B is present, then Not allowed in any B2b1 B2b1 is optional If sequence C is present, then Not allowed in any C1c1 C1c1 is optional Sequences B and C not present NA

23 July 2010

129

FIN

Sequence A if field :97a::SAFE is ... Not present

Then subsequence B2b1 or C1c1 is ...

Then in subsequence B2b1 or C1c1 field :97a::SAFE is ...

If sequence B is present, then Mandatory in all occurrences of B2b1 B2b1 is mandatory [1] If sequence C is present, then Mandatory in all occurrences of C1c1 C1c1 is mandatory [1] If sequences B and C are not present, then Error code E67

[1]

The upper sequences (<B, B2, B2b> or <C, C1, C1c>) are mandatory too.

Note:
E68

Sequence B and sequence C are mutually exclusive, see Error code E65.

MTs 503, 504, 505, 506, 507 and 527 In sequence A, if field :20C::SCTR is not present, then field :20C::RCTR is mandatory; otherwise field :20C::RCTR is optional. Sequence A If field :20C::SCTR is ... Not present Present MT 558 In sequence A, if field :20C::CLTR is not present, then field :20C::TCTR is mandatory, otherwise field :20C::TCTR is optional. Sequence A If field :20C::CLTR is ... Not present Present MT 584 Subsequence B2a in sequence B must be present when field :20C::MAST is not present in subsequence B2. Subsequence B2 if field :20C::MAST is ... Not present Present Subsequence B2a is ... Mandatory (minimum one occurrence) Optional Then field :20C::TCTR is ... Mandatory Optional Then field :20C::RCTR is ... Mandatory Optional

E69

MTs 535 and 536 If field :17B::ACTI in sequence B contains N, then subsequence B1 must not be present. In all other cases, subsequence B1 is mandatory. This error code applies only when sequence B is present per Error code E66, that is in sequence A, field :17B::ACTI contains Y.

130

Error Codes

Chapter 3 Alphanumeric Codes

Sequence A if field :17B::ACTI is ...

Then sequence B is ...

If sequence A field 17B::CONS is ...

Then in each occurrence of sequence B field 97a::SAFE and field 17B::ACTI are ... NA Mandatory

In every occurrence of sequence B if field :17B::ACTI is ...

In the same occurrence of sequence B then subsequence B1 is ...

N Y

Not allowed Mandatory that is, minimum one occurrence

NA Y

NA Y

NA Mandatory that is, minimum one occurrence Not allowed Mandatory that is, minimum one occurrence

N N Not allowed (impact: rule 269) <-- Rule 256 --> Not present per (Rule 256)

<-- Rule 266 -->

<-- Rule 269 -->

Note:
MT 584

The Rules 266 and 256 take precedence over Rule 269.

If field :17B::ACTI in sequence A contains N, then sequences B and C must not be present. Sequence A if field :17B::ACTI is ... N Y E70 MTs 528 and 529 If field :22F::DBNM is present in sequence C and field :22H::REDE//DELI is present in sequence B, then one occurrence of subsequence C1 must contain :95a::BUYR. If field :22F::DBNM is present in sequence C and field :22H::REDE//RECE is present in sequence B, one occurrence of subsequence C1 must contain field :95a::SELL. In sequence C if field :22F::DBNM is ... Present And sequence B field :22H::REDE is ... DELI RECE Not present NA Then in one occurrence of subsequence C1 ... Field :95a::BUYR is mandatory Field :95a::SELL is mandatory NA see rule 280 Sequences B and C are ... Not allowed See Error code E65

Note:

See rule 284.

MTs 540 and 541 If field :22F::DBNM is present in sequence E, then one occurrence of subsequence E1 must contain :95a::SELL.

23 July 2010

131

FIN

In sequence E if field :22F::DBNM is ... Present Not present

Then in one occurrence of subsequence E1 ... Field :95a::SELL is mandatory NA

Note:

See rule 284.

MTs 542 and 543 If field :22F::DBNM is present in sequence E, then one occurrence of subsequence E1 must contain :95a::BUYR. In sequence E if field :22F::DBNM is ... Present Not present Then in one occurrence of subsequence E1 ... Field :95a::BUYR is mandatory NA

Note:
E71

See rule 284.

MTs 503, 504, 505, 506 and 507 In each occurrence of subsequence A1, if field :22F::AGRE is not present, then field :70C::AGRE is mandatory; otherwise field :70C::AGRE is optional. In each occurrence of subsequence A1 If field :22F::AGRE is ... Not present Present Then field :70C::AGRE is ... Mandatory Optional

E72

MTs 503 and 504 In each occurrence of subsequence C3, if field :22H::BCOL//LCOL is present, then field :98B::EXPI//OPEN is not allowed; otherwise field :98B::EXPI//OPEN is optional. In each occurrence of subsequence C3 If field :22H::BCOL//LCOL is ... Present Not present MT 505 In each occurrence of subsequence B3, if field :22H::BCOL//LCOL is present, then field :98B::EXPI//OPEN is not allowed; otherwise field :98B::EXPI//OPEN is optional. In each occurrence of subsequence B3 If field :22H::BCOL//LCOL is ... Present Then field :98B::EXPI//OPEN is ... Not allowed Then field :98B::EXPI//OPEN is ... Not allowed Optional

132

Error Codes

Chapter 3 Alphanumeric Codes

In each occurrence of subsequence B3 If field :22H::BCOL//LCOL is ... Not present MT 506 In each occurrence of subsequence D3, if field :22H::BCOL//LCOL is present, then field :98B::EXPI//OPEN is not allowed; otherwise field :98B::EXPI//OPEN is optional. In each occurrence of subsequence D3 If field :22H::BCOL//LCOL is ... Present Not present MT 569 In each occurrence of subsequence C1a1, the presence of field :98a::SETT depends on the value of field :17B:COLL as follows: In each occurrence of subsequence C1a1 If field :17B::COLL is ... Y N E73 MTs 513 and 515 If field :19A::SETT is present in sequence C, it must not be present in any occurrence of subsequence D3. Sequence C If field :19A::SETT is ... Present Not present MTs 514 and 518 If field :19A::SETT is present in sequence B, it must not be present in any occurrence of subsequence C3. Sequence B if field :19A::SETT is ... Present Not present MT 584 Within each occurrence of subsequence B2b, if field :19A::SETT is present, it must not be present in any occurrence of subsequence B2b2. Then for each occurrence of subsequence C3 field :19A::SETT is ... Not allowed Optional Then for each occurrence of subsequence D3 field :19A::SETT is ... Not allowed Optional Then field :98a::SETT is ... Mandatory Not allowed Then field :98B::EXPI//OPEN is ... Not allowed Optional Then field :98B::EXPI//OPEN is ... Optional

23 July 2010

133

FIN

Within each occurrence of subsequence B2b If field :19A::SETT is ... Present Not present Then for each occurrence of subsequence B2b2 field :19A::SETT is ... Not allowed Optional

Within each occurrence of subsequence C1c, if field :19A::SETT is present, it must not be present in any occurrence of subsequence C1c2. Within each occurrence of subsequence C1c If field :19A::SETT is ... Present Not present Then for each occurrence of subsequence C1c2 field :19A::SETT is ... Not allowed Optional

Note:
E74 MT 502

Sequences B and C are mutually exclusive (see Error code E65).

In sequence B, field :22F::TOOR and/or field :90a::LIMI must be present. Sequence B if field :22F::TOOR is ... Present Not present Then subsequence B1 is ... Optional Mandatory (that is, minimum one occurrence of subsequence B1) Subsequence B1 and field :90a::LIMI is ... Optional Mandatory in at least one occurrence of subsequence B1

E75

MTs 528 and 529 If field 19A::SETT is specified in both sequences B and C3, it must contain the same value, that is Sign, Currency and Amount must be identical.

E76

For specific message types, if the value date is after 31 December 2001, then the 13 European currencies must not be used as the currency of settlement. If the value date is after 31 December 2006, then the currency code SIT (Slovenia) must not be used as the currency of settlement. If the value date is after 31 December 2007, then the currency codes CYP (Cyprus) and MTL (Malta) must not be used as the currency of settlement. If the value date is after 31 December 2008, then the currency code SKK (Slovakia) must not be used as the currency of settlement. If the value date is after 31 December 2010, then the currency code EEK (Estonia) must not be used as the currency of settlement. See the table below, where generic means that field 119 is not present in the User Header. MT [1] 101 Field with Value Date [2] 30 in sequence A Field with Currency Code 32B in each occurrence of sequence B

134

Error Codes

Chapter 3 Alphanumeric Codes

MT [1] 102 generic 102+ 103 generic 103+ 103 (REMIT) 104 generic 104 (RFDD) 107 200 201 202 202 COV 203 204 205 205 COV 207 210 400 405

Field with Value Date [2] 32A in sequence C 32A

Field with Currency Code 32A in sequence C 32A

30 in sequence A 30 in sequence A 30 in sequence A 32A 30 32A 32A 30 30 in sequence A 32A 32A 30 in sequence A 30 33A 32C in each occurrence of subsequence B3 32D in sequence C

32B in each occurrence of sequence B 32B in sequence C (see Error code C96) 32B in each occurrence of sequence B 32B in sequence C 32A 32B in each occurrence 32A 32A 32B in each occurrence 32B in each occurrence of sequence B 32A 32A 32B in each occurrence of sequence B 32b in each occurrence 33A 32C in each occurrence of subsequence B3 32D in sequence C 32A in each occurrence 32A 33C 33D 33D in each occurrence 19A with qualifier SETT in sequence C Field 19A with qualifier SETT in each occurrence of subsequence D3 19A with qualifier SETT in sequence B 19A with qualifier SETT in each occurrence of subsequence C3

450 455

32A in each occurrence 32A 33C 33D

456 513

33D in each occurrence [98a with qualifier SETT in sequence C]

[3]

514

[98a with qualifier SETT in sequence B]

[3]

23 July 2010

135

FIN

MT [1] 515

Field with Value Date [2] 98a with qualifier SETT in sequence C
[3]

Field with Currency Code 19A with qualifier SETT in sequence C 19A with qualifier SETT in each occurrence of subsequence D3 19A with qualifier SETT in sequence B 19A with qualifier SETT in each occurrence of subsequence C3 19A with qualifier SETT in sequence B 19A with qualifier SETT in each occurrence of subsequence C3 19A with qualifier SETT in sequence B 19A with qualifier SETT in each occurrence of subsequence C3 19A with qualifier SETT in each occurrence of subsequence E3 19A with qualifier SETT in each occurrence of subsequence E3 19A with qualifier ESTT in subsequence E3

518

98a with qualifier SETT in sequence B

[3]

528

98a with qualifier SETT in sequence B

[3]

529

98a with qualifier SETT in sequence B

[3]

541

98a with qualifier SETT in sequence B

[3]

543

98a with qualifier SETT in sequence B

[3]

545

[98a with qualifier SETT in sequence B]

[3]

547

[98a with qualifier SETT in sequence B] [3]

19A with qualifier ESTT in subsequence E3

564

98a with qualifier PAYD in subsequence E2

[3]

19B with qualifier ENTL in each occurrence of subsequence E2 Seq E2 Cash Movements Field 19B Qualifier ENTL (each occurrence)

Seq E2 Cash Movements Field 98a Qualifier VALU

[3]

566 584

98a with qualifier POST in subsequence D2 [98a with qualifier SETT in subsequence B2b]
[3]

19B with qualifier PSTA in each occurrence of subsequence D2 19A with qualifier SETT in each occurrence of subsequence B2b 19A with qualifier SETT in each occurrence of subsequence B2b2

[98a with qualifier SETT in subsequence C1c] [3]

19A with qualifier SETT in each occurrence of subsequence C1c 19A with qualifier SETT in each occurrence of subsequence C1c2

730 734 742

32D 33A 34A

32D 33A 34A

136

Error Codes

Chapter 3 Alphanumeric Codes

MT [1] 752 754 756 768 769 800 802 900 910
[1]

Field with Value Date [2] 33A 34A 33A 32D 32D 32A in sequence B 32A 32A 32A 33A 34A 33A 32D 32D

Field with Currency Code

32A in sequence B 32A 32A 32A

Generic means that there is no tag 119 in the User Header. Values in parentheses indicate the value of tag 119. Fields shown in square brackets are optional. The validation for this error code is not performed if the Value Date component is not present. For example, if field :98B:: is used, the validation is not performed.

[2] [3]

E77

MT 564 In each occurrence of sequence E, field :92a::, the qualifiers TAXC, GRSS, and NETT may only be repeated with letter option J. MT 566 In sequence D, field :92a::, the qualifiers TAXC, GRSS, and NETT may only be repeated with letter option J.

E78

MT 564 In each occurrence of sequence E: if field :92J:: GRSS is present more than once, then for each occurrence of field :92J:: GRSS, the Rate Type Code must be different if field :92J::TAXC is present more than once, then for each occurrence of field :92J::TAXC, the Rate Type Code must be different if field:92J:: NETT is present more than once, then for each occurrence of field :92J:: NETT, the Rate Type Code must be different if field :92J:: TAXE is present more than once, then for each occurrence of field :92J:: TAXE, the Rate Type Code must be different

Note: 1. Rule 278 must be applied even if the DSS is present in field :92J::. 2. See rule 277.
MT 566 In sequence D: if field :92J:: GRSS is present more than once, then for each occurrence of field :92J:: GRSS, the Rate Type Code must be different

23 July 2010

137

FIN

if field :92J::TAXC is present more than once, then for each occurrence of field :92J::TAXC, the Rate Type Code must be different if field:92J:: NETT is present more than once, then for each occurrence of field :92J:: NETT, the Rate Type Code must be different if field :92J::TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different

Note: 1. Rule 278 must be applied even if the DSS is present in field :92J::. 2. See rule 277.
E79 MT 549 In sequence A, field :98a::STAT and field :69a::STAT are mutually exclusive. Sequence A If field :98a::STAT is ... Present Not present MT 564 In each occurrence of sequence E, if field :22F::CAOP//OTHR is present, then in the same occurrence of sequence E, field :70E::ADTX is mandatory. In each occurrence of sequence E if field :22F::CAOP//OTHR is ... Present Not present
[1]

Then field :69a::STAT is ... Not allowed Optional

[1]

In the same occurrence of sequence E then field :70E::ADTX is ... Mandatory Optional

This error code does not apply if the Data Source Scheme is present in field :22F::CAOP//OTHR.

MT 565 In sequence D, if field :22F::CAOP//SPLI is present, then field :70E::INST is mandatory in the same sequence. In sequence D If field :22F::CAOP//SPLI is ... [1] Present Not present
[1]

Then field :70E::INST is ... Mandatory (that is, minimum one occurrence) Optional

This error code does not apply if the Data Source Scheme is present in field :22F::CAOP//SPLI.

E80

MTs 528 and 529 If field :22F::DBNM is NOT present in sequence C, then it is mandatory to specify a place of settlement: one occurrence of subsequence C1 Settlement Parties must contain party field :95a::PSET.

138

Error Codes

Chapter 3 Alphanumeric Codes

In sequence C, if field :22F::DBNM is ... Not present Present

Then in one occurrence of subsequence C1 ... Field :95a::PSET is mandatory NA see rule 270

Note: See rule 284 (that is, :95a::PSET must be present in only one occurrence of C1).
MT 549 Sequence B Statement by Status/Reason and/or by Financial Instrument and sequence C Statement by Instruction Reference are mutually exclusive. If sequence B is ... Present Not present MT 564 In each occurrence of sequence E, if field :92J::TAXE is present, then field :92F::GRSS must be present in the same sequence occurrence. MT 566 In sequence D, if field :92J::TAXE is present, then field :92F::GRSS must be present. E81 MTs 508 and 524 In sequence B, the third component of field :93A::FROM must be different from the third component in field :93A::TOBA. MT 538 Within each occurrence of subsequence B2, the third component of field :93A::FROM must be different from the third component in all occurrences of field :93A::TOBA in subsequence B2a. E82 MT 535 In each occurrence of subsequence B1, if NO subsequence B1b is present, then both fields Price (field :90a:) and Holding Value (field :19A::HOLD) must be specified in subsequence B1. In each occurrence of subsequence B1, if one or more occurrences of subsequence B1b are present, then both fields Price (field :90a:) and Holding Value (field :19A::HOLD) must be specified in each occurrence of subsequence B1b. This check only applies when the statement refers to an accounting statement (see rule 267), that is, if field :22F::STTY//ACCT is present. In every occurrence of subsequence B1 if subsequence B1b is ... Not present Present once or more Then, in the same occurrence of subsequence B1 field :90a: is ... Mandatory Optional And the same occurrence of subsequence B1 field : 19A::HOLD is ... Mandatory Optional And in every occurrence of subsequence B1b field :90a: is ... NA Mandatory And in every occurrence of subsequence B1b field :19A::HOLD is ... NA Mandatory Then sequence C is ... Not allowed Optional

23 July 2010

139

FIN

E83

MT 307 The following fields cannot appear more than once in the message: Subsequence B3 :19B::BUYE :19B::SELL :95a::CDEA :95a::INTE :95a::ACCW :95a::BENM MTs 503 and 504 In each occurrence of sequence C, the presence of subsequences C1, C2 and C3 depends on the value of field :22H::COLL<Indicator> as follows: In each occurrence of sequence C If field :22H::COLL//4!c is ... BCOL CCOL SCOL MT 505 In each occurrence of sequence B, the presence of subsequences B1, B2 and B3 depends on the value of field :22H::COLL as follows: In each occurrence of sequence B If field :22H::COLL is ... BCOL CCOL SCOL MT 506 In each occurrence of sequence D, the presence of subsequences D1, D2 and D3 depends on the value of field :22H::COLL as follows: In each occurrence of sequence D If field :22H::COLL is ... BCOL CCOL SCOL MT 536 In subsequence B1a2, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be specified. Then subsequence D1 is ... Not allowed Not allowed Mandatory And subsequence D2 is ... Not allowed Mandatory Not allowed And subsequence D3 is ... Mandatory Not allowed Not allowed Then subsequence B1 is ... Not allowed Not allowed Mandatory And subsequence B2 is ... Not allowed Mandatory Not allowed And subsequence B3 is ... Mandatory Not allowed Not allowed Then subsequence C1 is ... Not allowed Not allowed Mandatory And subsequence C2 is ... Not allowed Mandatory Not allowed And subsequence C3 is ... Mandatory Not allowed Not allowed Subsequence D1

140

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence B1a2 If field :22H::PAYM is ... APMT Not = APMT MT 537 In subsequence B2b and C2, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be specified. Subsequence B2b If field :22H::PAYM is ... APMT Not = APMT Then field :19A::PSTA is ... Mandatory Optional Sequence C2 If field :22H::PAYM is ... APMT Not = APMT MT 548 In sequence B, if field :22H::PAYM//APMT is used, then field :19A::SETT must be specified. Sequence B If field :22H::PAYM is ... APMT Not = APMT MT 578 In sequence B, if field :22H::PAYM//APM is used, then one occurrence of sequence E3 must contain field :19A::SETT. Sequence B if field :22H::PAYM is ... APMT Not = APMT Then sequence E3 is ... And, in one occurrence of subsequence E3 field :19A::SETT is ... Mandatory Optional Then field :19A::SETT is ... Mandatory Optional Then field :19A::PSTA is ... Mandatory Optional Then field :19A::PSTA is ... Mandatory Optional

Mandatory Optional

Note:
MT 586

See Error code E87.

In sequence B, if field :22H::PAYM//APMT is used, then field :19A::SETT must be specified. Sequence B if field :22H::PAYM is ... APMT Not = APMT Then subsequence B5c is ... Mandatory Optional And in one occurrence of subsequence B5c field :19A::SETT is ... Mandatory Optional

23 July 2010

141

FIN

Note:
E84 MT 307

See Error code E87.

In each occurrence of sequence B3, the following party fields cannot appear more than once: Sequence B3a :95a::CDEA :95a::INTE :95a::ACCW :95a::BENM MT 321 In each occurrence of sequence C, the following party fields for sequence C1 cannot appear more than once: Subsequence C1 :95a::CDEA :95a::INT2 :95a::INTE :95a::ACCW :95a::BENM MTs 502, 514, and 518 The following party fields, for sequences C1 and C2, cannot appear more than once in sequence C. The following party fields in sequence D cannot appear more than once in a message. Subsequence C1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL Subsequence C2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence D :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::VEND :95a::TRAG

142

Error Codes

Chapter 3 Alphanumeric Codes

MTs 528 and 529 The following Party Fields, for sequences C1 and C2, cannot appear more than once in sequence C. The following Party Fields for sequence D cannot appear more than once in a message. Subsequence C1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 504 In each occurrence of sequence C, for subsequences C1a1 and C2a1, the following party fields cannot appear more than once: Subsequence C1a1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL In sequences D and E, for subsequences D1 and E1, the following party fields cannot appear more than once: Subsequence D1 :95a::BUYR :95a::DEAG :95a::ACCW :95a::BENM Subsequence E1 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence C2a1 Subsequence C2 :95a::ACCW :95a::BENM :95a::PAYE Sequence D :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::VEND :95a::TRAG

23 July 2010

143

FIN

Subsequence D1 :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 505 :95a::PAYE :95a::DEBT

Subsequence E1

In each occurrence of sequence B, for subsequences B1a1 and B2a1, the following party fields cannot appear more than once: Subsequence B1a1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL In sequences C and D, for subsequences C1 and D1, the following party fields cannot appear more than once: Subsequence C1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence D1 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence B2a1

144

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence C1 :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 507

Subsequence D1

In each occurrence of sequence B, for subsequences B1a1 and B1b1, the following party fields cannot appear more than once: Subsequence B1a1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 513 The following party fields for sequences D1 and D2 cannot appear more than once in sequence D. The following party fields for sequence E cannot appear more than once. Subsequence D1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL Subsequence D2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence E :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::VEND :95a::TRAG :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence B1b1

23 July 2010

145

FIN

MT 515 The following party fields for sequences D1 and D2 cannot appear more than once in sequence D. The following party fields for sequence E cannot appear more than once. Subsequence D1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 536 In each occurrence of subsequence B1a, in subsequence B1a2, the following party fields cannot appear more than once. Subsequence B1a2a :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 537 The following party fields cannot appear more than once in the same occurrence of subsequence B2b. Subsequence B2b1 :95a::BUYR Subsequence D2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence E :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::VEND :95a::TRAG

146

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence B2b1 :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL The following party fields cannot appear more than once in the same occurrence of subsequence C2. Sequence C2a :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 540 The following party fields cannot appear more than once in a message. Subsequence E1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET Subsequence E2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence F :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::TRAG :95a::VEND

23 July 2010

147

FIN

Subsequence E1 :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MTs 542, 544, 546

Subsequence E2

Sequence F

The following party fields cannot appear more than once in a message. Subsequence E1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 541 The following party fields cannot appear more than once in a message. Subsequence E1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL Subsequence E2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence F :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::TRAG :95a::VEND Subsequence E2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence F :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::TRAG :95a::VEND :95a::QFIN

148

Error Codes

Chapter 3 Alphanumeric Codes

MTs 543, 545, 547 The following party fields cannot appear more than once in a message. Subsequence E1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 548 The following party fields cannot appear more than once in the same occurrence of sequence B. Subsequence B1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 575 The following party fields cannot appear more than once in the same occurrence of subsequence B1a. Subsequence B1a4 :95a::BUYR :95a::DEAG :95a::DECU Subsequence E2 :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Sequence F :95a::EXCH :95a::MEOR :95a::MERE :95a::TRRE :95a::TRAG :95a::VEND :95a::QFIN

23 July 2010

149

FIN

Subsequence B1a4 :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 575 The following party fields cannot appear more than once in the same occurrence of subsequence C2. Subsequence C2a :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL MT 578 The following party fields cannot appear more than once in a message. Subsequence E1 :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence E2

150

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence E1 :95a::REI1 :95a::REI2 :95a::SELL MT 586

Subsequence E2

The following party fields cannot appear more than once in the same occurrence of sequence B. Subsequence B5a :95a::BUYR :95a::DEAG :95a::DECU :95a::DEI1 :95a::DEI2 :95a::PSET :95a::REAG :95a::RECU :95a::REI1 :95a::REI2 :95a::SELL E85 MTs 503 and 504 In each occurrence of subsequence C2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator> as follows: In each occurrence of subsequence C2 If field :22H::DEPO//4!c is ... FIXT CLNT MT 505 In each occurrence of subsequence B2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator> as follows: In each occurrence of subsequence B2 If field :22H::DEPO//4!c is ... FIXT CLNT MT 506 In each occurrence of subsequence D2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator> as follows: Then field :98A::TERM is ... Mandatory Not allowed Then field :98A::TERM is ... Mandatory Not allowed :95a::ACCW :95a::BENM :95a::PAYE :95a::DEBT Subsequence B5b

23 July 2010

151

FIN

In each occurrence of subsequence D2 If field :22H::DEPO//4!c is ... FIXT CLNT MTs 528 and 529 If field :22F::DBNM is NOT present in sequence C, and if field :22H::REDE is DELI in sequence B, then one occurrence of field :95a::REAG must be present in subsequence C1. If field :22F::DBNM is NOT present in sequence C, and if field :22H::REDE is RECE in sequence B, then one occurrence of field :95a::DEAG must be present in subsequence C1. In sequence C if field :22F::DBNM is ... Not present And sequence B field :22H::REDE is ... DELI Then in one occurrence of subsequence C1 Field :95a::REAG is mandatory see rule 284 Field :95a::DEAG is mandatory see rule 284 NA Then field :98A::TERM is ... Mandatory Not allowed

RECE

Present MT 537

NA

If field :22H::REDE//DELI is present in subsequence B2b and subsequence B2b1 is used, then it is mandatory to specify field :95a::REAG in one occurrence of subsequence B2b1. If field :22H::REDE//RECE is present in subsequence B2b and subsequence B2b1 is used, then it is mandatory to specify field :95a::DEAG in one occurrence of subsequence B2b1. Subsequence B2b if field :22H::REDE is ... DELI Subsequence B2b if field :22H::REDE is ... RECE And if subsequence B2b1 is ... Present And if subsequence B2b1 is ... Present Then in one occurrence of subsequence B2b1 field :95a::REAG is ... Mandatory Then in one occurrence of subsequence B2b1 field :95a::DEAG is ... Mandatory

If the instruction is a delivery (:22H::REDE//DELI in sequence C2) and the Settlement Parties sequence C2a is used, then it is mandatory to specify a Receiving Agent: one occurrence of the settlement parties sequence C2a must contain party field :95a::REAG. If the instruction is a receipt (:22H::REDE//RECE in sequence C2) and the Settlement Parties sequence C2a is used, then it is mandatory to specify a Delivering Agent: one occurrence of the settlement parties sequence C2a must contain party field :95a::DEAG. Sequence C2 if field :22H::REDE is ... DELI And if sequence C2a is ... Then in one occurrence of sequence C2a field :95a::REAG is ... Mandatory

Present

152

Error Codes

Chapter 3 Alphanumeric Codes

Sequence C2 if field :22H::REDE is ... RECE MT 548

And if sequence C2a is ...

Then in one occurrence of sequence C2a field :95a::DEAG is ... Mandatory

Present

If field :22H::REDE//DELI is present in sequence B and subsequence B1 is used, then it is mandatory to specify field :95a::REAG in one occurrence of subsequence B1. If field :22H::REDE//RECE is present in sequence B and subsequence B1 is used, then it is mandatory to specify field :95a::DEAG in one occurrence of subsequence B1. Sequence B if field :22H::REDE is ... DELI Sequence B if field :22H::REDE is ... RECE MT 578 If field :22H::REDE//DELI is present in sequence B, then it is mandatory to specify field :95a::DEAG in one occurrence of subsequence E1. If field :22H::REDE//RECE is present in sequence B, then it is mandatory to specify field :95a::REAG in one occurrence of subsequence E1. Sequence B if field :22H::REDE is ... DELI Sequence B if field :22H::REDE is ... RECE MT 586 Within each occurrence of sequence B, if field :22H::REDE//DELI is present in sequence B, then it is mandatory to specify field :95a::DEAG in one occurrence of subsequence B5a. Within each occurrence of sequence B, if field :22H::REDE//RECE is present in sequence B, then it is mandatory to specify field :95a::REAG in one occurrence of subsequence B5a. Sequence B if field :22H::REDE is ... Then in the same occurrence of sequence B in one occurrence of subsequence B5a field :95a::DEAG is ... Mandatory Then in one occurrence of subsequence E1 field :95a::DEAG is ... Mandatory Then in one occurrence of subsequence E1 field :95a::REAG is ... Mandatory And if subsequence B1 is ... Then in one occurrence of subsequence B1 field :95a::REAG is ... Mandatory Then in one occurrence of subsequence B1 field :95a::DEAG is ... Mandatory

Present And if subsequence B1 is ...

Present

DELI

23 July 2010

153

FIN

Sequence B if field :22H::REDE is ... RECE E86

Then in the same occurrence of sequence B in one occurrence of subsequence B5a field :95a::REAG is ... Mandatory

MTs 502, 504, 505, 507, 513, 514, 515, 518, 528, 529, 536, 537, 540, 541, 542, 543, 544, 545, 546, 547, 548, 575, 578 and 586 If, in a sequence (identified in the second and third columns in the table below), a qualifier from either the Deliverers or Receivers list is present in a subsequence (as identified in the fourth column), then each qualifier shown below that qualifier in the same list must be present in another occurrence of that subsequence. MT(s) In each occurrence of sequence In each occurrence of subsequence For all occurrences of subsequence(s) Fields :95a:: all qualifiers must belong to the list(s) Deliverers and/ or Receivers from bottom up and with no gap (See Example below) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s)

502, 514, 518 504

C C (R) D

NA NA NA NA NA NA NA NA B1 (R) B2 (R) C2 NA

C1 C1a1 D1 B1a1 C1 B1a1 D1 C1 B1a2a B2b1 C2a E1

505

B (R) C

507 513, 515 528, 529 536 537 540, 541, 542, 543, 544, 545, 546, 547 548 575

B (R) D C B (R) B (R) C (R) E

B B (R) C (R)

NA B1a (R) NA NA NA

B1 B1a4 C2a E1 B5a

:95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s) :95a::qualifier(s)

578 586

E B (R)

This check applies to every occurrence of a repetitive sequence (as denoted by (R) in column 2 and 3). For example, in MT 504, if sequence C is present more than once, this check applies to each occurrence of sequence C. In MT 536, if sequence B is present more than once, this check

154

Error Codes

Chapter 3 Alphanumeric Codes

applies to each occurrence of sequence B, and if subsequence B1 is present more than once, this applies to each occurrence of subsequence B1. The following table lists the Deliverers and Receivers. For each subsequence, the presence of a qualifier requires the presence, in other subsequences, of all the qualifiers listed below it. Deliverers List Code DEI2 DEI1 DECU SELL DEAG [1]
[1]

Receivers List Code REI2 REI1 RECU BUYR REAG [1] Qualifiers Receiver's Intermediary 2 Receiver's Intermediary 1 Receiver's Custodian Buyer (Receiver) Receiving Agent

Qualifiers Deliverer's Intermediary 2 Deliverer's Intermediary 1 Deliverer's Custodian Seller (Deliverer) Delivering Agent

The Delivering and Receiving Agents apply only for MTs 502, 513, 514, 515, 518.

Example: For MT 536: in each occurrence of sequence B, in each occurrence of subsequence B1, if field :95a::DEI2 is present in subsequence B1a2a, then field :95a::DEI1 must be present in another subsequence B1a2a, and field :95a::DECU must be present in another subsequence B1a2a, and field :95a::SELL must be present in another subsequence B1a2a. Similarly if field :95a::REI2 is present in subsequence B1a2a, then field :95a::REI1 must be present in another subsequence B1a2a, and field :95a::RECU must be present in another subsequence B1a2a, and field :95a::BUYR must be present in another subsequence B1a2a. E87 MT 540 The following Amount fields cannot appear in more than one occurrence of the Amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::BOOK :19A::CHAR :19A::COUN :19A::COAX :19A::DEAL

23 July 2010

155

FIN

Subsequence E3 :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MT 541 The following Amount fields cannot appear in more than one occurrence of the Amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LADT

156

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence E3 :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MT 542 The following Amount fields cannot appear in more than one occurrence of the Amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::BOOK :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL

23 July 2010

157

FIN

Subsequence E3 :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MT 543 The following Amount fields cannot appear in more than one occurrence of the Amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR

158

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence E3 :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MTs 544 and 546 The following amount fields cannot appear in more than one occurrence of the amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::BOOK :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::ESTT :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST

23 July 2010

159

FIN

Subsequence E3 :19A::REGF :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MTs 545 and 547 The following amount fields cannot appear in more than one occurrence of the amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::ESTT :19A::EXEC :19A::ISDI :19A::LADT :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SHIP :19A::SPCN

160

Error Codes

Chapter 3 Alphanumeric Codes

Subsequence E3 :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH MT 578 The following amount fields cannot appear in more than one occurrence of the amounts subsequence E3. Subsequence E3 :19A::ACCA :19A::ACRU :19A::ANTO :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX

23 July 2010

161

FIN

Subsequence E3 :19A::VATA :19A::WITH MT 586 The following amount fields cannot appear in more than one occurrence of the amounts subsequence B5c. Subsequence B5c :19A::ACCA :19A::ACRU :19A::ANTO :19A::CHAR :19A::COAX :19A::COUN :19A::DEAL :19A::EXEC :19A::ISDI :19A::LEVY :19A::LOCL :19A::LOCO :19A::MARG :19A::OTHR :19A::POST :19A::REGF :19A::SETT :19A::SHIP :19A::SPCN :19A::STAM :19A::STEX :19A::TRAN :19A::TRAX :19A::VATA :19A::WITH E88 MTs 540, 541, 542 and 543 If sequence C is present once, field :19A::SETT must not be present in sequence C.

162

Error Codes

Chapter 3 Alphanumeric Codes

MTs 544, 545, 546 and 547 If sequence C is present once, field :19A::ESTT must not be present in sequence C. E89 MTs 540 and 542 If sequence C is present two or more times, field :19A::SETT must be present in every occurrence of sequence C or in none. In the former case, when sequence C is present two or more times and field :19A::SETT is present in every occurrence of sequence C, then: field :19A::SETT must be present in one occurrence of subsequence E3 the sum of all occurrences of field :19A::SETT in sequence C must be equal to field :19A::SETT in subsequence E3 the currency code in fields 19A::SETT in sequences C and E3 must be the same for all occurrences of these fields in the message MTs 544 and 546 If sequence C is present two or more times, field :19A::ESTT must be present in every occurrence of sequence C or in none. In the former case, when sequence C is present two or more times and field :19A::ESTT is present in every occurrence of sequence C, then: field :19A::ESTT must be present in one occurrence of sequence E3 the sum of all occurrences of field :19A::ESTT in sequence C must be equal to field :19A::ESTT in subsequence E3 the currency code in fields 19A::ESTT in sequences C and E3 must be the same for all occurrences of these fields in the message MTs 541 and 543 If sequence C is present two or more times, field :19A::SETT must be present in every occurrence of sequence C or in none. In the former case, when sequence C is present two or more times and field :19A::SETT is present in every occurrence of sequence C, then: the sum of all occurrences of field :19A::SETT in sequence C must be equal to field :19A::SETT in subsequence E3 the currency code in fields 19A::SETT in sequences C and E3 must be the same for all occurrences of these fields in the message MTs 545 and 547 If sequence C is present two or more times, field :19A::ESTT must be present in every occurrence of sequence C or in none. In the former case, when sequence C is present two or more times and field :19A::ESTT is present in every occurrence of sequence C, then: the sum of all occurrences of field :19A::ESTT in sequence C must be equal to field :19A::ESTT in sequence E3 the currency code in fields 19A::ESTT in sequences C and E3 must be the same for all occurrences of these fields in the message

23 July 2010

163

FIN

E90

MT 307 Repetitive subsequence B3 must be present exactly twice in the message.

Note:
MT 321

Conditional Rule 290 takes precedence over 284 and 291.

One occurrence of sequence C must have the following value: :22H::PRIT//APFM One occurrence of sequence C must have the following value: :22H::PRIT//APCP MTs 540, 541, 542 and 543 In sequence A, if field :99B::TOSE is present, then field :99B::SETT must be present. Sequence A If field :99B::TOSE is ... Present Not present E91 MT 307 In each occurrence of sequence B3, the presence of the repetitive subsequence B3a depends on the content of :22H::NEGR as follows: In sequence A if field :22H::NEGR is ... GRSC NETC or UNKN Field :22H::NEGR not present MT 321 Taking into account rules 284 and 290, in each occurrence of sequence C, the presence of the different parties (that is, field 95a::CDEA, and field 95a::ACCW) in subsequence C1 depends on the content of field 22H in sequence C as follows: In each occurrence of sequence C, if field :22H::PRIT is ... APCP or IPCP APFM or IPFM MT 504 It is mandatory to specify a Delivery Agent for subsequences C1a1 and D1. In each occurrence of sequence C, if subsequence C1a1 is present, then field :95a::DEAG must be present in one and only one occurrence of subsequence C1a1 within the same occurrence of sequence C. In sequence D, if present, if subsequence D1 is present, then field :95a::DEAG must be present in one and only occurrence of subsequence D1. Then in one occurrence of subsequence C1 field ... 95a::CDEA is mandatory 95a::ACCW is mandatory Then in each occurrence of sequence B3 subsequence B3a is ... Mandatory Not allowed Mandatory Then field :99B::SETT is ... Mandatory Optional

Note:

See also Error code E84.

164

Error Codes

Chapter 3 Alphanumeric Codes

MTs 540, 541, 544 and 545 If field :22F::DBNM is NOT present in sequence E, then it is mandatory to specify a Delivering Agent and a place of settlement: one occurrence of subsequence E1 Settlement Parties must contain party field :95a::DEAG and another one must contain party field :95a::PSET. E92 MT 307 Taking into account rule 291: in each occurrence of sequence B3, the presence of field 95a in sequence B3a depends on the content of field 19B in sequence B3 as follows: In each occurrence of sequence B3, if field :19B:: is ... And if subsequence B3a is present (that is, is mandatory per rule 291) then ... In one occurrence of subsequence B3a, field ... 95a::CDEA is mandatory 95a::ACCW is mandatory And in all other optional occurrence(s) of B3a, field ...

BUYE SELL MT 321

95a::INTE is optional 95a::INTE is optional

95a::ACCW is optional 95a::CDEA is optional

95a::BENM is not allowed 95a::BENM is optional

In a message, the following sequence C fields cannot appear more than once: Sequence C :22H::PRIT//APFM :22H::PRIT//APCP :22H::PRIT//IPFM :22H::PRIT//IPCP MTs 541 and 543 It is mandatory to specify one occurrence of subsequence E3 with field :19A::SETT. MTs 545 and 547 It is mandatory to specify one occurrence of subsequence E3 with field :19A::ESTT. E93 MT 507 It is mandatory to specify a Receiving Agent for subsequence B1a1. In each occurrence of sequence B if present, if subsequence B1a1 is present, then field :95a::REAG must be present in one and only one occurrence of subsequence B1a1 within the same occurrence of sequence B.

Note:

See also Error code E84.

MTs 542, 543, 546 and 547 If field :22F::DBNM is NOT present in sequence E, then it is mandatory to specify a Receiving Agent and a place of settlement: one occurrence of the settlement parties subsequence E1 must contain party field :95a::REAG and another one must contain party field :95a::PSET.

23 July 2010

165

FIN

E94

MT 564 If field :97C::SAFE//GENR is present in any occurrence of subsequence B2, then: subsequence B2 Account Information must not be repeated in the message field 93a must not be present in subsequence B2 the Quantity of Financial Instrument, that is, field 36B, must not be present in subsequence E1 Securities Movement the Amount, that is, field 19B, must not be present in subsequence E2 Cash Movement In subsequence B2 if field :97C::SAFE//GENR is ... Present Not present Then subsequence B2 is ... And in subsequence B2 field 93a is ... Not allowed Optional And in any occurrence of subsequence E1 field 36 B is ... Not allowed Optional And in any occurrence of subsequence E2 field 19B is ... Not allowed Optional

Not repetitive min-Max=1-1 Repetitive minMax=1-n

E95

MT 575 Within each occurrence of sequence B1, if field :17B::ACTI contains N, then subsequence B1a within that subsequence B1 is not allowed. If field 17B::ACTI contains Y, then subsequence B1a is mandatory. Subsequence B1 if field :17B::ACTI is ... N Y Then subsequence B1a is ... Not allowed Mandatory

E96

MT 575 Within subsequence B1a, subsequence B1a2 and subsequence B1a3 are mutually exclusive. If subsequence B1a2 is ... Present Not present Then subsequence B1a3 is ... Not allowed Mandatory

E97

MT 503 In sequence B, the presence of field :95a::EXPP depends on the value of field :22H::COAL//<Indicator> in sequence A as follows: Sequence A if field :22H::COAL//4!c is ... INIT VARI TERM Sequence B then field :95a::EXPP is ... Mandatory Mandatory Not allowed

166

Error Codes

Chapter 3 Alphanumeric Codes

MTs 587, 588 and 589 In sequence A, if field :22H::DERE contains CONV, then field :22F::CNVT and field :22F::CNVF must be specified and field 12a must not be present. If field 22H::DERE does not contain CONV, then field 12a must be present. Sequence A If in field :22H::DERE Indicator is ... CONV Not = CONV E98 MT 588 If field :17B::PRER contains Y, sequence C must also be present. If field :17B::PRER contains N, sequence C must not be present. Sequence A if field :17B::PRER is ... Y N E99 Available. Mandatory Not allowed Then sequence C is ... Then field :22F::CNVT is ... Mandatory Optional Then field :22F::CNVF is ... Mandatory Optional Then field 12a is ...

Not allowed Mandatory

3.6 G Codes - Service-specific Validation

Australian PDS service: MT 103 The letter option of the 'selected field' is neither A nor C, nor D. MT 202 The letter option of the 'selected field' is not A nor D. G02 MT 103 or MT 202 The format of the 'selected field letter option A' is invalid. G03 MT 103 or MT 202 The format of the 'selected field letter option D' is invalid. G04 MT 103 The 'selected field' is missing, that is at least one of the following fields must be present: 56a, 57a G18 MT 103 The format of the 'selected field letter option C' is invalid.

G01

23 July 2010

167

FIN

Canadian Large Value Transfer Service (LVTS): If 2 LVTS members (that is sender and receiver are LVTS subscribers and the first six characters of their destination id, that is SWIFT BIC are different, that is not the same institution) exchange an MT 103 or an MT 205 and the currency code used in the field 32A is CAD, then field 103 must be present in the User Header and it must contain the code CAD.

G05

Miscellaneous - Message Specific REMIT: In MT 103, the field 77T and the tag 119 with the code word REMIT (in the User Header) must either be both present or both absent. Continuous Linked Settlement (CLS): In MT 300 eligible for the FINCopy service CLS or CLT, any field 53a present in sequence B must be used with option A. In MT 300 eligible for the FINCopy service CLS or CLT, both fields 57a in subsequences B1 and B2 must be used with option A, and field 57a of subsequence B1 must contain the CLSB BIC. In MT 300 eligible for the FINCopy service CLS or CLT, if field 17U is used it must contain the value N. In MT 300 eligible for the FINCopy service CLS or CLT, any field 56a present in sequence B must be used with option A. In MT 304 sent to the CLSB server, field 94A must contain ASET. In MT 304 sent to the CLSB server, any field 53a present in sequence B must be used with option A. In MT 304 sent to the CLSB server, both fields 57a in sequence B must be used with option A and must contain the CLSB BIC.

G06

G07

G08

G09

G10

G13 G16

G17

Note:
G19 G20 G21 G22

Field 57A, index 19 is mandatory.

In MT 305 eligible for the FINCopy service CLS or CLT, field 53a must be used with option A. In MT 305 eligible for the FINCopy service CLS or CLT, field 56a must be used with option A. In MT 305 eligible for the FINCopy service CLS or CLT, field 57A must be present. In MT 305 eligible for the FINCopy service CLS or CLT, when emitter and receiver are both CLS or CLT members, then field 57A must contain CLSB****.

168

Error Codes

Chapter 3 Alphanumeric Codes

G23

In MT 305 eligible for the FIN Copy service CLS or CLT, when emitter is CLS or CLT member and receiver is not, and field 34R is present, then field 57A must contain CLSB****; when emitter is CLS or CLT member and receiver is not, and field 34P is present, then field 56A must contain CLSB****. In MT 305 eligible for the FINCopy service CLS or CLT, both fields 56A and 57A must not contain the CLSB BIC at the same time.

G24

3.7 H Codes - Basic Header and Application Header Validation

H01 H02 H03 H04 H09 H10 H15 H20 H21 H25 H26 H30 H40 H50 Basic Header not present or format error block 1 Application identifier not A (General Purpose Application) or F (FIN) Invalid service message identifier (unknown or not allowed from user) Available

Bad logical terminal address or application not enabled for the logical terminal Bad session number Error in the input sequence number Error in the message sender's branch code. Application header format error or not present when mandatory Input/output identifier not 'I' (on input from logical terminal) Message type does not exist for this application This priority does not exist for this message category Destination address error: Destination not known to the system (includes branch code) Destination not enabled for this application User to SWIFT message MT 090 sent to incorrect destination

H51

Invalid sender or receiver for message type or mode: Incompatibility between message type and sender or receiver System message sent to a receiver other than SWFTXXXX

23 July 2010

169

FIN

Receiver not in the same mode (live/training) as sender Sender is not in the right mode for this MT, either live user sending MTs 072 or 073, or Test & Training user in Full Function Mode sending MT 073 Either sender or receiver is not in possession of a BKE certificate

H52

MT 072, selection of Test & Training mode/version, MT 077 Additional Selection Criteria for FIN are not allowed while a FIN session is open. Available Delivery option error Obsolescence period error Any other format error in the Basic Header or in the Application Header. This code applies to errors that are not explained in the other H error codes. Error can be one of the following: Invalid receiver destination (invalid character or logical terminal identification is not 'X') Invalid date or time (not numeric or not within range).

H55 H80 H81 H98

H99

3.8 K Codes - Code Words Validation in Generic Fields

Knn Code word error in a generic field. The 2 digits "nn" indicate the field id. The invalid code word is located either: right after the Data Source Scheme, that is, after the ending "/", for example: K17 MT 500 sequence B1 :17B::CALL//A (reject A) K22 MT 500 sequence A :22F::INST//DERA (reject DERA) K90 MT 500 sequence B1 :90B::INDC//ACTA/USD123, (reject ACTA) K93 MT 564 sequence B2 :93C::BLOK//FAMA/ELIG/123, (reject FAMA) or further into the field, for example: K93 MT 564 sequence B2 :93C::BLOK//FAMT/ELIA/123, (reject ELIA) This check applies to: MTs 307, 321, 380, 381, 500-510, 513-515, 517-519, 524, 527-530, 535-538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586-589.

Note:

K17 applies also to field :17B:: in MTs n92, n95 and n96.

170

Error Codes

Chapter 3 Alphanumeric Codes

3.9 L Codes - LOGIN Errors

L01 L02 L03 Login Request received while previous Login Request still pending Slice Processor recovery in progress Session already open on another Regional Processor, and that Regional Processor is recovering Destination takeover in progress Unable to close previous session due to recovery in progress at Slice Processor or old Regional Processor Login presented before time/day expressed in previous logout Logical terminal inhibited (that is temporarily unable to work with SWIFT). Call your Customer Support Centre. Logical terminal does not belong to Sign Distinguished Name (DN) organisation Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN) organisation Login NAK error code (field tag 503) to indicate that the login with recovery option is not currently supported Logical terminal is not in recoverable state. Computer-based terminal should execute fresh Login procedure

L04 L05

L30 L35

L38 L39

L55

L56

3.10 M Codes - Message Errors

M50 M60 M71 M72 Message length exceeded Non-SWIFT character encountered Logical terminal does not belong to Sign Distinguished Name (DN) organisation Logical terminal's owning master destination does not belong to sign Distinguished Name (DN) organisation Signatures present but not required for this message type Signatures not present but required for this message type

M73 M74

23 July 2010

171

FIN

M75 M76 M77

Signatures not present but required by this Copy service Signatures present but not allowed by this FINCopy service Unable to decode the Signature block

3.11 P Codes - Protocol Errors

P16 P18 P20 P21 P23 P24 P27 P28 P29 P30 P32 P33 P34 P35 P36 P37 P38 P39 Unexpected user data received Input message sent when session was selected for output only Input message sent when session was selected for output only Re-Select/Re-Login, logical terminal not in reconnect ready state Re-Select Request format error Re-Select Request semantic error Select message received when Re-Select expected Session recovery not attempted: logical terminal did not select recovery option at Login Session not recovered: connection failure while waiting for Application Control associate request Application session not in recoverable state Re-Select error - Session Number mismatch Re-Select error - F330 input sequence numbercomputer-based terminalfailed validation Re-Select error - F330 input sequence number-ACKcomputer-based terminal failed validation Re-Select error - F330 output sequence numbercomputer-based terminal failed validation Re-Select error - F330 output sequence number-ACKcomputer-based terminal failed validation Re-Select error - Window size mismatch Re-Select error - Select state mismatch Re-Select error - Subsets mismatch

172

Error Codes

Chapter 3 Alphanumeric Codes

P40 P41

Re-Select error - LT-directed field mismatch A logical terminal shared delivery subset request has been received, but cannot be processed since the function is permanently active for that particular logical terminal Logical terminal does not belong to Sign Distinguished Name (DN) organisation Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN) organisation Timeout expired on a response to a primitive sent to the user

P42 P43

PRI

3.12 R Codes - Re-login/Re-select Errors

R01 R02 R03 R04 LOGOUT/QUIT received while session is recovering Replay of SELECT-ACK Replay of Re-SELECT-ACK Timeout for Re-Login with outstanding output sequence number-ACKs

3.13 S Codes - System-initiated Abort Errors

S01 S02 S03 S04 S05 User aborted by system in order to do a destination takeover Must execute delivery instructions redefinition Level 3 recovery User failed to LOGOUT within the time limit requested by the system In FIN, the system needs to abort the user session for a limited time In General Purpose Application, select received for inhibited logical terminal S06 S51 S53 S54 Test and Training session aborted because its master has been changed Unable to decode Public Key Infrastructure Signature Block in Login Request Login must contain level 2 of Sign Distinguished Name (DN) Invalid signature size in Login Request

23 July 2010

173

FIN

S55

System error - Level 2 of Sign Distinguished Name (DN) in Login Request must contain 8 characters Login ACKs contain invalid field tag System error, invalid association ident Signature syntax error Signature semantic error Session aborted because subsets sharing mode change was requested using MT 077

S56 S59 S71 S72 S76

3.14 S Codes - Select Errors

S10 S11 S12 S13 S14 S15 S16 S17 Incorrect application identifier (application disabled or unknown) Incorrect select state Output state selected but not logged on to primary Regional Processor Output state selected but neither LT-directed messages nor delivery subsets were selected. LT-directed flag either invalid or 'Y' but output state not requested Delivery subsets selected but output state not requested Window size error The delivery subset selected is invalid for one of the following reasons: the delivery subset does not exist the delivery subset has already been selected in non-shared mode by another logical terminal of the same destination the delivery subset is already being used in shared mode and a logical terminal of the same destination working in non-shared mode has attempted to select it

S19 S20 S21

System is reorganising the delivery subsets as a result of a delivery instructions redefinition No delivery subset allowed in a Test & Training LTM-SELECT command. Remove Application Request sent by Regional Processor to computer-based terminal to indicate that FIN session at Regional Processor was not established

174

Error Codes

Chapter 3 Alphanumeric Codes

S30 S31 S35

Select presented before time/day specified in last QUIT More than 30 delivery subsets defined Logical terminal inhibited (that is temporarily unable to work with SWIFT). Call your Customer Support Centre. Bad Trailer Block in Select message A delivery subset has been specified twice in the Select Request Logical terminal does not belong to Sign Distinguished Name (DN) organisation Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN) organisation Unable to decode Public Key Infrastructure Signature Block in Select Request Select must contain level 2 of Sign Distinguished Name (DN) Invalid Signature size in Select Request Level 2 of Sign Distinguished Name (DN) in Select Request must contain 8 characters Select ACKs contain invalid field tag Invalid association identification

S36 S42 S43 S44

S61 S63 S64 S65 S66 S68

3.15 T Codes - Text Validation

T00 T01 Not used. Code word error. This check applies to: field 39B, in MTs 700, 705, 707, 710, 720, 740 and 747

T02

Unable to ascertain reason for NAK. Contact your Customer Support Centre immediately for advice.

T03

Code word error. This check applies to: subfield 3, field 26C, in MTs 600, 601, 604, 605, 606, 607, 608, 609 and 620

23 July 2010

175

FIN

subfield 1, field 38B, in MT 405

T04

Code word error. This check applies to: subfield 4, field 26C, in MTs 600, 601, 604, 605, 606, 607, 608, 609 and 620. subfield 2, field 38B, in MT 405.

T05

Code word error. This check applies to: subfield 3, field 38B, in MT 405 subfield 4, field 68B, in MT 609

T06

Code word error. This check applies to: subfield 1 field 32F in MTs 600, 601, 604, 605, 606, 607, 620 subfield 1 field 32R, in MT 620 subfield 1 field 33J, in MT 620 subfield 1 field 34J, in MT 620 subfield 3 field 60F, 60M, 62F, 62M, 64 or 65, in MT 608 subfield 5 field 68B or 68C in MT 609 or any of the above fields in common groups n92, n95 or n96.

T07

Code word error. This check applies to: subfield 3, field 33G

T08

Code word error. This check applies to: field 23, in MTs 102+ and 609. field 71A, in MTs 101, 102, 103, 104, 107, 405, 740, or in any message appended in common groups MTs n92, n95 or n96

T09

Code word error. This check applies to: subfield 3, field 23, in MTs 305 and 601 subfield 3, field 68C, in MT 609, or in any message appended in common groups MTs n92, n95 or n96

176

Error Codes

Chapter 3 Alphanumeric Codes

T10 T11 T12

The repetitive sequence occurred more than the maximum number of times permitted. The repetitive sequence occurred less than the minimum number of times permitted. Field, line, subfield or component content error. Or, the format Reject/Return is not allowed for field 72 in this MT Or when 'ISIN' is used at the beginning of line one in field 35B it must be in 'upper case'.

T13

This field tag is not expected at this location in this MT. Either a mandatory field is missing, or the sequence of fields is incorrect, or the given field is not allowed at this point in this MT, or a Field Separator CrLf: (Carriage_return Line_feed Colon) is not immediately followed by a valid SWIFT field id. (for example, field tag is invalid), or an end-of-text sequence (CrLf-) was encountered when not expected, or more than one end-of-text sequence (CrLf-) occurs in this message. Or it may be the invalid combination of fields that are used in the message that is causing the Error code T13. Or in a common group message (that is MT n92, n95 or n96), within the list of "Copy of any field(s) of the original message", there are generic fields and non-generic fields that are not allowed to be mixed in the same message. Or, in one of the ISO 15022 messages an optional sequence of fields was used, however, a field or a field qualifier that is required (that is indicated by an "OR", or "minimum 1") within that sequence is missing, or field 16R is present but its related code word is inappropriate. Or, in a qualifier table, for a particular generic field (that is nn), in a repeatable order, there is a list of "OR" qualifiers, but more than one qualifier has been used in the repetitions of the generic field, in this sequence.

Note: If there is a list of options, a different option may be used in a repeated field, as long as it is with the same qualifier.
T14 The first subfield [N] (negative indicator) must not be used when the amount, number, UTC indicator or number count component is equal to 0. This check applies to: field 19A in MTs 321 502, 506, 513, 514, 515, 518, 527, 528, 529, 535, 536, 537, 540, 541, 542, 543, 544, 545, 546, 547, 548, 558, 564, 566, 567, 569, 574IRSLST, 575, 578, 584, 586, 587 and 588. field 32H in MTs 306, 320, 330, 340, 362, and 620. field 32N in MT 646. field 32R in MT 620. field 33N in MT 646. field 34E in MTs 320, 330, 341, and 620. field 34J in MT 620. field 34N in MT 646. field 35H in MT 581. field 36E in MT 564. field 37G in MTs 320, 330, 362, 620, and 644.

23 July 2010

177

FIN

field 37M in MTs 340, 341, 362 and 644. field 37R in MTs 341, 360, 361, 362 and 644. field 92A in MTs 321, 500, 501, 502, 506, 508, 513, 514, 515, 518, 519, 524, 527, 528, 529, 535, 538, 540, 541, 542, 543, 544, 545, 546, 547, 558, 564, 565, 566, 568, 569, 574IRSLST, 576, 578, 584, 586, 587 and 588. field 92E in MTs 564, and 566. field 93B in MTs 501, 535, 536, 564, 565, 566 and 568. field 93C in MTs 535, 564, 565, 566 and 568. field 93D in MT 575. field 98D in MTs 564 and 566. field 98E in MTs 500-510, 513-515, 517, 518, 519, 524, 527, 528, 529, 530, 535-538, 540-548, 558, 569, 574-IRSLST, 574-W8BENO, 575, 576, 578, 584, 586-589. field 99A in MTs 506, 513, 514, 515, 518, 528, 529, 535, 536, 540, 541, 542, 543, 544, 545, 546, 547, 564, 569, 575, 578 and 586. or any of the above fields or 60A or 60B in common groups MTs n92, n95 and n96.

T15 T16

Sign is not valid. (<SIGN> must be either + or -.) Time offset is not valid. (<OFFSET> has the same format as time <HHMM>; it must be 00<=HH<=13 and 00<=mm<=59.) Field, line, subfield, or component consists of blanks, ('CrLf') or missing mandatory line, subfield or component. This check applies to: field 11R and 11S; the first component must have the format 3!n (fixed length), and must be within the range 100-999. field 12, and MT = 105; this component must have the format 3!n (fixed length), and must be within the range 100-999. field 12, and MT NOT= MT105; this component must have the format 3!n (fixed length), see T88 for additional special exception checks. field 61; if the first character of subfield 6 is S, then the next 3 characters must have the format 3!n (fixed length), and must be within the range 100-999.

T17

T18

T19 T20

Available. Code word error. This check applies to: subfield 1, component 3, field 32K or 33K.

T21

Available.

178

Error Codes

Chapter 3 Alphanumeric Codes

T22

A common reference mismatch exists between field 22, subfield 2, component 2, and: field 36 in MT 305 subfield 2, field 33G, in MT 600 subfield 2, field 32B, in MT 601 Or, a common reference mismatch exists between field 22C, component 2, and: field 30P, YYMM of YYYYMMDD, in MTs 360, 361, 362, 364 and 365. field 36, sequence B, in MT 300 field 36, sequence B, in MT 303 field 36A, sequence C, in MT 303 field 36, sequence D, or field 37U, sequence G, in MT 306 field 37G, sequence B, in MTs 320 and 330 field 37M, sequence B in MTs 340 and 341 field 37J, sequence B, in MT 350

Note: The above check is not applied to MTs appended to common group MTs n92, n95 and n96.
T23 Subfield 8 in field 61, subfield 5 in field 66A or subfield 6 in field 26C is too long or contains only //; or subfield 2 in fields 26A or 26B is too long or contains only /. Subfield 7 in field 61, subfield 4 in field 66A, subfield 5 in field 26C, subfield 1 in fields 26A or 26B is missing or is too long. Subfields 7 or 8 in field 61, subfield 4 or 5 in field 66A, subfield 5 or 6 in field 26C, subfield 1 or 2 in fields 26A or 26B has improper content. The data content of this field may not contain a / as its first character, nor as its last character; nor may it contain // (two consecutive slashes) anywhere within its contents. This check applies to: field 13B fields 20, 20C and 20D fields 21, 21A, 21F, 21G, 21P and 21R field 94B fields 95Q, 95R, 95S, 95T, 95U

T24

T25

T26

Note: If the field has multiple lines, each line is validated independently; each line must not begin with a '/', nor end with a '/', nor contain '//'.
T27 T28 BIC incorrectly formatted or invalid. SWIFT BIC is not a valid destination.

23 July 2010

179

FIN

T29 T30

SWIFT BIC contains an invalid branch code. Excessive line(s), subfield(s) or component(s) were found in this field. (CrLf: or CrLf- not found or line, subfield or component length greater than defined length). The line, subfield or component separator or delimiter (CrLf, blank, slash, or double slash) is missing or incorrect. The system is expecting a particular subfield, component or component separator. In most situations, the error occurred in the message text at the line number reported. However, in some situations, the error occurred in the message text at the previous line. If the first character of a field does not belong to the right character set, the system returns Error code T32, for example: Field :20: :20: Format 16x 16x Invalid data ;ABC ^ABC

T31

T32

In this case, ';' is not part of the <X> character set; '^' is not part of the <X>, <Y> and <Z> character sets. T33 Field, line or subfield error. Length of field, line, subfield, or component contents is too long. Example: Field Format 6a Format AAAAAA(CrLf) Invalid data ACTUAAA(CrLf)

or consists of one or more hidden characters, for example, trailing blank(s), Example: Field Format 6a 6a 5!a 6x Format A(CrLf) ACTUAL(CrLf) OTHER(CrLf) /AC:ee(CrLf) Invalid data ACTUAe(CrLf) ACTUALe(CrLf) OTHERe(CrLf) /AC:eee(CrLf)

Where 'e' = hidden blank character ('trailing blank') or contains one or more embedded character(s) that is inconsistent with the defined field format, or a character does not belong to the correct character set. Example: Field Format 9a Format AAAAAAAAA Invalid data AAAAeAAAA(CrLf)

180

Error Codes

Chapter 3 Alphanumeric Codes

Field Format 5a 5a Where:

Format OTHER OTHER

Invalid data O1HER(CrLf) O:HER(CrLf)

'e' = blank (space) character '1' = numeric character ':' = special character (not an alphabetic character) ';' = Not in the <X> character set

T34

Length of field, line, subfield, or component contents is too short, or a character does not belong to the right character set. Code word error. This check applies to: subfield 1, field 26C

T35

T36

Code word error. This check applies to: field 14A in MTs 360 and 361 field 14D in MTs 320, 330, 340, 350, 360, 361, and 620. field 14J in MTs 360 and 361 field 17A in MTs 300, 303, 306, 360, 361 and 405 field 17F in MTs 304, 306, 340, 360, 361 and 405 field 17G in MT 304 field 17N in MT 304 field 17O in MT 304 field 17T in MT 300 field 17U in MT 300 field 22A in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, 360, 361, 362, 364, 365, and 620 field 23B in MTs 103 and 303 field 94A in MTs 300, 303, 304, 305, 306, 320, 330, 340, 341, 350, 360, 361, 362, 364, 365, 600, 601, and 620

T37

Code word error.

23 July 2010

181

FIN

This check applies to: subfield 2, field 35H contains an invalid code word or currency code, when used with MT 581, and with any message appended in common groups MT n92, n95, or n96

T38 T39

Time illogical. Time of UTC Indicator (HH[MM]) is not in the valid range (00<=HH<=23, 00<=MM<=59). This check applies to: field 98E in MTs 500-510, 513-515, 517, 518, 519, 524, 527-530, 535-538, 540-548, 558, 569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586-589. field 98F in MT 564.

T40 T41 T42

Missing amount/number or incorrect amount/number first character. Available. Code word error. This check applies to: subfield 3 field 35U

T43

The amount/number subfield must contain one decimal separator which is a decimal comma, and no other punctuation/separator is permitted. The decimal separator in the amount/number subfield or component is missing, is not a comma and/or more than one comma is present. The SWIFT BIC exists but it is not enabled for FIN, or the BIC is active but is not published in the current BIC directory, or it is not cutover. Invalid non-SWIFT BIC. A Test and Training destination must not be used in a live message. The data part of a code word /OCMT/ or /CHGS/ is being validated, but the ending separator (that is the third slash '/') is missing, in one of the following Euro-Related Information (ERI) fields: field 61 field 72 field 77A field 79 field 86 or Code word error. This check applies to: subfield 1, field 14G, in MTs 360 and 361

T44

T45 T46 T47

182

Error Codes

Chapter 3 Alphanumeric Codes

subfield 1, field 22, in MT 305 subfield 1, field 23A, in MTs 360, 361, 362, 364 and 365 subfield 1, field 23E, in MTs 101, 103 (not 103+), 104, 107, 207, 256, 405 and 416 subfield 1, field 39P, in MT 303 subfield 9, field 61, duplicated code words: /OCMT/ or /CHGS/ field 72 (narrative), duplicated code words: /OCMT/ or /CHGS/ field 72 (structured), duplicated code words: /OCMT/ or /CHGS/or /INS/ field 77A, duplicated code words: /OCMT/ or /CHGS/ line 1, field 77D, sequence C in MT 303 subfield 1, field 77H, in MTs 306, 340, 360, 361, 600 and 601 field 79, duplicated code words: /OCMT/ or /CHGS/ field 86, duplicated code words: /OCMT/ or /CHGS/

T48

Code word error. This check applies to: subfield 2, field 14G, in MTs 360 and 361 subfield 1, field 22K, in MT 306 subfield 2, field 23A, in MTs 360, 361, 362, 364 and 365 field 23D, in MTs 340 and 341 subfield 1, field 23E, in MT 103+ subfield 2, field 38E, in MTs 360 and 361 subfield 2 or subfield 4, field 38G, in MTs 340, 360 and 361 subfield 2 or subfield 4, field 38H, in MTs 360 and 361

T49 T50

Available. Date error EITHER Invalid Date subfield. This check applies to all MTs with a Date subfield. OR Invalid year <YY> in a Value Date subfield of the MTs that are candidate for the Value Date Ordering process. The valid range for <YY> is: 00-60 for the years 2000-2060 80-99 for the years 1980-1999

23 July 2010

183

FIN

This check applies to: field 30, in MTs: 101, 104, 107, 110, 111, 112, 201, 203, 204, 207, 210, 256 field 32A, in MTs: 102, 103, 110, 111, 112, 200, 202, 205, 256, 910

T51 T52 T53

Code word 'C', 'D', 'RC', 'RD', 'EC' or 'ED' error. Invalid currency code or price code PCT, REN or YLD. Code word error. This check applies to: component 1, subfield 6 of field 61.

T54

The format of the first line of Field 50F (Party Identifier) is invalid. This check applies to: field 50F in MTs 101, 102, 102+, 103, 103+, 202 COV, 205 COV, 210, 910 This check applies to all MTs containing field 50F, when appended to Common Group MTs n92, n95, n96.

T55

Code word error. This check applies to Subfield 1, component 1: field 50F in MTs 101, 102, 102+, 103, 103+, 202 COV, 205 COV, 210, 910 This check applies to all MTs containing field 50F, when appended to Common Group MTs n92, n95, n96.

T56

Code word error, syntax error, or format error. This check applies to Subfield 2, Lines 2-5: field 50F in MTs 101, 102, 102+, 103, 103+, 202 COV, 205 COV, 210, 910 This check applies to all MTs containing field 50F, when appended to Common Group MTs n92, n95, n96.

T57

Code word error. This check applies to: subfield 1 of field 31X.

T58

Code word error. This check applies to: subfield 1 field 35A, 35N or 35S.

T59

Code word error.

184

Error Codes

Chapter 3 Alphanumeric Codes

This check applies to: field 40E in MTs 700, 710, and 720 field 40F in MT 740

T60

Code word error. This check applies to: field 26F, in MT 306 field 40A, in MTs 700 and 705 field 40C in MT 760

T61

Code word 'D' or 'M' error. This check applies to: field 32K, subfield 1, in MTs 400, 405, 410, 416, 420, 422 and 430 subfield 1, field 33K, in MT 430 subfield 2, field 37(A-F), in MTs 516, 644, and 646 subfield 1, field 38J, in MTs 320, 330, and 620

T62

Either the first subfield ([<DATE2>[<HHMM>]]) or the second subfield (7!a), but not both, must be present. If optional subfield 1 is used, component 1 <DATE2> of this subfield must be present. Field 31X. Component 2 of field 22C or subfield 2, component 2 of field 22 error. When the last character of this component contains zero (0) and the preceding character is not a one (1), then the entire component must consist of zeros (0000). This check applies to: All MTs containing field 22 or field 22C, when appended to common group MTs n92, n95, n96

T63

T64

Code word error. This check applies to: line 1, field 40B, in MTs 710 and 720 field 12F, in MT 306

T65 T66

Available. Code word error. This check applies to: field 12E, in MT 306 line 2, field 40B, in MTs 710 and 720

23 July 2010

185

FIN

T67

Code word error. This check applies to: field 17R, in MTs 320, 330, and 620 field 17V, in MT 306 field 49, in MTs 700, 710 and 720

T68

Code word error. This check applies to: subfield 1, field 24D, in MTs 300, 306, 320, 330, 340, 360, 361, and 620 subfield 2, field 41A, in MTs 700, 705, 710, 720 and 740 subfield 2, field 41D, in MTs 700, 705, 710, 720 and 740

T69 T70

Available. Either the Account number ('/'34x) or the Place ('CrLf'35x['CrLf'35x]0-3) or both must be present. This applies to field 82S. Example: Valid :82S: BE/ACC NO 123 :82S: BE/ACC NO 123 SOCIETE GENERALE :82S: US/ACC NO 123 CHASE BANK 5TH AVENUE N.Y. CITY USA :82S: FR CREDIT LYONNAIS :82S: US CHASE BANK 5TH AVENUE N.Y. CITY USA Invalid :82S: BE :82S: BE/ :82S: /ACC NO 123

T71

Code word error. This check applies to: field 22D in MTs 360, 361, 364, 365 and 405 field 22E in MT 405 field 22G, in MT 306

T72

Code word error.

186

Error Codes

Chapter 3 Alphanumeric Codes

This check applies to: field 22J, in MT 306 subfield 1, field 23C, in MT 405 subfield 1, field 23F, in MT 405

T73

Invalid country code. See the BIC Directory General Information - Country Codes. This check applies to: field 50F in MTs 101, 102, 102+, 103, 103+, 202 COV, 205 COV, 210, 910. field 59, 59A, subfield IBAN, in MTs 102+ and 103+. field 82S, subfield 1, in MT 405 field 94C, 2!a (Country Code), in MTs 500, 501, 502, 508, 510, 513, 514, 515, 518, 519, 524, 528, 529, 535, 536, 537, 538, 540, 541, 542, 543, 544, 545, 546, 547, 548, 564, 565, 566, 567, 568, 574IRSLST, and 574W8BENO field 95C, 2!a (Country Code), in MTs 502, 504, 505, 507, 513, 514, 515, 518, 528, 529, 536, 537, 540, 541, 542, 543, 544, 545, 546, 547, 548, 575, 578 and 586 field 94D; 2!a (Country Code), in MTs 500, 501, 510, 519, 535, 574IRSLST, and 574W8BEBO field 95S, 2!a (Country Code), in MTs 500, 501, 502, 504, 505, 507, 510, 513, 514, 515, 518, 519, 528, 529, 540, 541, 542, 543, 544, 545, 546, 547, 565, 566, 576, 578, 584, 586, 587, 588, and 589.

T74

The currency code must be the same for each indicated subfield in the field. This check applies to: subfields 7 and 10, field 68B and subfields 7, 9 and 11, field 68C

T75

In MTs 405, n92, n95 and n96, field 38B. When subfields 1 and 2 contain MONT/OTHR, then subfield 3 is mandatory; otherwise subfield 3 is not allowed. Example: Valid :38B: MONT/OTHER/01 :38B: QUAR/LBDP Invalid :38B: MONT/OTHR :38B: MONT/OTHR/ :38B: QUAR/LBDP/01

T76

The first character in the first line of this field must be a /, and there must be at least another line, but no more than 5 lines. This applies to field 50H. Example: Valid :50H:/X X Invalid :50H:X X Invalid :50H:/X Invalid :50H:/X X X

23 July 2010

187

FIN

Valid :50H:/X X X X X T77

Invalid

Invalid

Invalid X X X

If the first character of the first line of this component or sub component is a /, there must be at least another line, but not more than 5 lines; otherwise, no more than 4 lines are allowed. This applies to: fields 42D 50K (50-58)D 59 (Note: in MTs 102_STP, 103_STP, 104 and 107, conditional rule 210 takes precedence, that is, "the first character of the first line must be /", see Conditional Semantic Error code E10) (82-88)D

T78

Invalid or duplicated code word, or a mandatory code word is missing. This check applies to: subfield 1 of each line, field 53J, in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, and 620 subfield 1 of each line, field 56J, in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, and 620 subfield 1 of each line, field 57J, in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, and 620 subfield 1 of each line, field 58J, in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, and 620 subfield 1 of each line, field 82J, in MTs 300, 303, 304, 305, 306, 320, 330, 350, 600, 601, and 620 subfield 1 of each line, field 83J, in MTs 300, 303, 304, 305, 306, 320, 330, 350, 360, 361, 362, 364, 365, 600, 601, and 620 subfield 1 of each line, field 84J, in MTs 300, 306, 320, 330, and 620 subfield 1 of each line, field 85J, in MTs 300, 320, 330, and 620 subfield 1 of each line, field 86J, in MTs 306, 320, 330, 340, 341, 350, and 620 subfield 1 of each line, field 87J, in MTs 300, 303, 304, 305, 306, 320, 330, 350, 600, 601, and 620 subfield 1 of each line, field 88J, in MTs 300, 320, and 620

T79

Available.

188

Error Codes

Chapter 3 Alphanumeric Codes

T80

<Field 72 Reject/Return> or <Field 79 Reject/Return>: code word error, or mandatory code word is missing, or code word not in the proper sequence.

Note:
T81

This check applies to MTs 10x, 11x, 20x, 195, 199, 295 and 299.

Format of field 72 Reject/Return is not allowed in this message. This check applies to: field 72, MTs 102+ and 103+

T82

Euro-Related Information (ERI) format is not allowed in this field in this message. This check applies to: field 72, MT 102+ and 103+

T83 T84 T85

Available. Available. Code word error. This check applies to : field 23G, subfield 2, in MTs 307, 321, 380, 381, 500-510, 513-515, 517-519, 524, 527-530, 535-538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586-589, or in any message appended in common groups n92, n95, or n96

T86

Code word error. This check applies to: subfield 1, field 23G, in MTs 307, 321, 380, 381, 500-510, 513, 514, 515, 517-519, 524, 527-530, 535, 536, 537, 538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586, 587, 588, 589, or in any message appended in common groups n92 n95, or n96

T87

In a generic field: Colon ":" as a delimiter is not present at the expected position.

T88

Field 12 in MT 920 may consist only of 940, 941, 942, or 950 Field 12 in MT 973 may consist only of 971, 972, or 998

T89

In a generic field: qualifier is invalid qualifier is duplicated

23 July 2010

189

FIN

mandatory qualifier is missing qualifier format or syntax error

T90

In a generic field: issuer code format or syntax error mandatory issuer code is missing invalid generic field format

T91

In a generic field: Slash "/" as delimiter is not present at the expected position

T92

Code word error. This check applies to: field 16R in ISO 15022 MTs field 16S in ISO 15022 MTs.

T93

Code word error. This check applies to subfield 1, field 30J, in MT 306, or in any message appended in common groups n92, n95, or n96 field 22B in MTs 320, 330, 364, 365, and 620

T94

In field 22, subfield 2, or in field 22C, in the components 1 and 3, the values '0' and '1' are not permitted in <LC1> or <LC2>, however the value '0' is allowed in the second (rightmost) position if the sender or the receiver is a Test and Training user.

Note:
T95

This check is applied only to 'common group messages'.

In field 22, subfield 2, or in field 22C, components 1 and 3 do not contain the bank code and location code of the message emitter, or/and the bank code and location code of the message receiver.

Note:
T96 T97

This check is applied only to 'non-common group messages'.

In field 22, subfield 2, or in field 22C, components 1 and 3 are not in alphabetical sequence. Code word error. This check applies to: subfield 2, field 28E, in MTs 506, 527, 535, 536, 537, 538, 558, 569, 574W8BENO, 574IRSLST, 575, 576, 584, and 586

T98

Available.

190

Error Codes

Chapter 3 Alphanumeric Codes

T99

Available.

3.16 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 "{". U01 U02 U03 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: 103 Service identifier 113 Banking priority 108 Message user reference 119 Validation flag 115 Addressee information

U07 U08 U09

User Header not authorised in system message 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.

3.17 U Codes - User Abort Codes

The following codes are returned in field 441 of Service Message 13, Service Message 15, Service Message 33 and Service Message 35. For further details, see the FIN System Messages. Login positive acknowledgement/select positive acknowledgement validation error after ReLogin/Re-Select Input message to re-play not available Output sequence number-ACK to re-play not available

U02

U03 U04

23 July 2010

191

FIN

U05 U06

Input sequence number-ACK re-played not valid Output message re-played not valid

3.18 V Codes - System Message Errors and Message Block Format Errors
V01 V02 Invalid text block This field tag is not expected at this location in this MT. Either a mandatory field is missing, or the sequence of fields is incorrect, or the given field is not allowed at this point in this MT Minimum iterations of a field/component not satisfied Invalid date field Invalid time field Invalid message input reference/message output reference Generic error for failure of check against a character set, or line, subfield or component request is empty Generic error for failure of range check on a field Invalid report option End of block character '}' not found, or line, subfield or component greater than defined length Invalid logical terminal address, or invalid destination Invalid generation time option in MT 044 Component content error, for example, invalid broadcast selection criteria, or invalid broadcast heading code, or invalid broadcast heading text, or invalid country code Selection MT 073 error, syntax, duplicate Future version not available on the system (Test and Training) Invalid application ID Session History Request for disabled application

V03 V04 V05 V06 V07

V08 V09 V10 V11 V12 V13

V14 V15 V20 V21

192

Error Codes

Chapter 3 Alphanumeric Codes

V22 V23 V24 V25 V26 V30 V31 V32

Empty report Invalid receiving pseudo logical terminal Logical Terminal History or Undelivered Change Request received in invalid application Empty report in a message sample request (Test and Training) Field 221 in MT 085 contains an invalid SWIFT Integrated Circuit Card number Destination is not value date sensitive Specified value date does not refer to the past Specified cut-off time does not refer to the past 12 hours

Note:
V40

V50 - V68 are error codes issued for MT 047 errors.

The start time in MT 024 Bulk Retrieval Request is not within the last 124 days; or the end-time is earlier than the start time; or the end-time is earlier than the current-time The range between the start and end time in MT 024 Bulk Retrieval Request exceeds allowed limit (24 hours for Live, 1 hour for Test and Training) The sending BIC in MT 024 Bulk Retrieval Request has not subscribed to the bulk retrieval service Incorrect delivery subset mnemonic (not unique, may not start with 'LTDIR') Message priority/category/type assigned to more than one delivery subset No message types assigned to this subset Message category/type not available for this destination Mismatch message category/type and priority Not all message category/types assigned Once a message category has been specified in a delivery subset, specific messages from that category may not be specified in subsequent subsets Missing priority-assignment in the MT 047 command This MT 047 is replaced by a subsequent MT 047

V41

V42

V50 V51 V52 V53 V54 V55 V56

V57 V58

23 July 2010

193

FIN

V59 V60 V61 V62

Same priority is defined within a subset more than once More than 30 delivery subsets specified Service code assigned to more than one delivery subset Incorrect or invalid service code or message type specified in MT 047, only the service codes defined in the User Header Field Tag 103 are allowed in MT 047 Branch code with same priority assigned to more than one delivery subset Incorrect or invalid branch code specified in MT 047 Invalid combination of branch code - priority Field tag with same priority assigned to more than one delivery subset Incorrect or invalid field tag specified in MT 047 Invalid combination of field tag - priority Missing subset sharing field tag 348 or invalid value for field tag 348 Only category/message type/VAS code and branch codes can be combined This error code will be returned if both the following conditions are true for a specific subset: 1. The subset contains field 349 with value 1 AND 2. The subset contains field 347

V63 V64 V65 V66 V67 V68 V69 V70

V71

Incomplete combined criteria This error code will be returned if a subset has field tag 349 with value 1 AND any of the following conditions is true: 1. The subset does not contain field tag 346 (branch code) OR 2. The subset does not contain any category/message type/VAS code

V72

MT 077 with field 118:N is not allowed if delivery subset sharing has not been requested using field tag 348 in MT 047 MT 077 with field 118 is not allowed. MT 047 must be used to change the delivery subset sharing mode One of these error conditions occurred: 1. The customer defined its sharing mode (field 348 of MT 047) as "N" or "O" and sent an MT 077 with field 118:Y or 118:N

V73

194

Error Codes

Chapter 3 Alphanumeric Codes

2. The customer defined its sharing mode (field 348 of MT 047) as "L" and sent an MT 077 with field 118:N 3. The customer has its delivery subset parameter set to yes and is sending an MT 077 with field 118:Y

V74

Overflow mode already set by a previous MT 077 The following error condition occurred: 1. The customer previously set the overflow mode via an MT 077 and is trying to set it again

V99

System undergoing major recovery or system not completely synchronised yet, or the destination, or some message types are being intercepted

3.19 X Codes - FINCopy Message Validation (01 - 27) and Delayed NAK Error Codes (30 - 99)
X01 X02 X03 Message type not allowed for this service FINCopy service identifier is not valid Either sender or receiver, or both, is/are not subscriber(s) of this service (for example, a FINCopy service) Available Currency code is mandatory and not present Value date is mandatory and not present Currency code is different from service currency code Value date is not within the range specified for the service FINCopy service is closed Sender is not a FINCopy server destination for the service requested Message type is not allowed in this service mode FINCopy service is already open FINCopy service is already closed

X04 X05 X06 X07 X08 X09 X20 X21 X26 X27

23 July 2010

195

FIN

X28

The BIC in the level 2 of the Sign Distinguished Name (DN) (the Sign Distinguished Name (DN) organisation) does not match the central institution destination of the live FINCopy service Attempt to authorise message input reference of another FINCopy service Mismatch between FINCopy destination and the service code Refusal code is out of allowed range for FINCopy server (70-89) Authorised or refused message input reference is not found in the system Message is already aborted by the FINCopy server Message is already authorised by the FINCopy server Message is already aborted by the system Message is already bypassed by the system Central institution signature is required in MT 097 Authorisation Central institution signature is not allowed in MT 097 Authorisation Date field is not valid (for example, future start date or start time later than cut-off time) System cannot generate report because more than 39920 messages are pending authorisation (998 sections of 40 messages each) System is unable to process the request at this time System error (software or data inconsistency)

X30 X31 X32 X35 X36 X37 X38 X39 X40 X41 X46 X47

X48 X99

3.20 Y Codes - UNK Error Codes

Y01 Checksum failure

3.21 Z Codes - Trailer Validation

Note: Similar error codes are used by other SWIFT services, such as Accord, or Processing for Euro Banking Association (EBA), and can have different meanings. The error codes used by each of the services are described in the respective service documentation.
Z00 Block 5 format error

196

Error Codes

Chapter 3 Alphanumeric Codes

Z01 Z04 Z05 Z06 Z98

Invalid trailer sequence (or Training trailer used as LIVE message) Checksum trailer error Possible Duplicate Emission trailer error Training-trailer error Trailer not compatible with message type

23 July 2010

197

FIN

Legal Notices
Copyright Copyright S.W.I.F.T. SCRL ("SWIFT"), Avenue Adle 1, B-1310 La Hulpe, Belgium, or its licensors, 2010. All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices. Confidentiality This publication contains SWIFT or third-party confidential information. Do not disclose this publication outside your organisation without the prior written consent of SWIFT. Disclaimer 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 version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTReady, and Accord. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners.

198

Error Codes