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.

25 July 2014
FIN

Table of Contents
Preface.................................................................................................................................................... 4

About this document ........................................................................................................................... 4

Audience ............................................................................................................................................. 4

Significant changes............................................................................................................................. 4

Chapter 1 Introduction ............................................................................................................................ 5

Chapter 2 Numeric Codes ...................................................................................................................... 6

2.1 General ......................................................................................................................................... 0

2.2 Logout/Quit Acknowledgement Errors .......................................................................................... 6

2.3 Re-Login Request Errors .............................................................................................................. 6

2.4 Retrieval Errors ............................................................................................................................. 7

2.5 Message Status ............................................................................................................................ 9

2.6 Abort Reasons ............................................................................................................................ 11

2.7 FIN and General Purpose Application Session Termination....................................................... 12

2.8 Report Errors .............................................................................................................................. 13

2.9 Bulk Retrieval Errors Codes........................................................................................................ 14

Chapter 3 Alphanumeric Codes............................................................................................................ 15

3.1 General ......................................................................................................................................... 0

3.2 A Codes - Re-select Error Codes ............................................................................................... 15

3.3 B Codes - Copy Service Errors................................................................................................... 15

3.4 C, D, and E Codes - Conditional Semantic Error Codes ............................................................ 16

3.5 G Codes - Service-specific Validation....................................................................................... 158

3.6 H Codes - Basic Header and Application Header Validation .................................................... 160

3.7 K Codes - Code Words Validation in Generic Fields ................................................................ 161

3.8 L Codes - LOGIN Errors ........................................................................................................... 162

3.9 M Codes - Message Errors ....................................................................................................... 163

3.10 N Codes - Market Infrastructure Resiliency Service (MIRS) Errors ........................................ 163

3.11 P Codes - Protocol Errors ....................................................................................................... 165

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

3.13 S Codes - System-initiated Abort Errors ................................................................................. 167

3.14 S Codes - Select Errors .......................................................................................................... 167

3.15 T Codes - Text Validation ....................................................................................................... 169

3.16 U Codes - User Header Validation.......................................................................................... 184

3.17 V Codes - System Message Errors and Message Block Format Errors ................................. 185

2 Error Codes
 Table of Contents

3.18 X Codes - FINCopy Message Validation (01 - 27) and Delayed NAK Error Codes (30 - 99) . 188

3.19 Y Codes - UNK Error Codes ................................................................................................... 190

3.20 Z Codes - Trailer Validation .................................................................................................... 190

Chapter 4 FIN Errors........................................................................................................................... 191

4.1 Introduction ................................................................................................................................... 0

4.2 Abort Codes .............................................................................................................................. 191

4.3 Diagnostic Codes for SS100..................................................................................................... 193

4.4 Diagnostic Codes for SA100..................................................................................................... 195

Legal Notices ...................................................................................................................................... 199

25 July 2014 3
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.

For more information about the rules, the reader must consult the Message Format Validation Rules.

Significant changes
The following tables list all significant changes to the content of FIN Error Codes since the 26 July 2013
edition. These tables do not include editorial changes that SWIFT makes to improve the usability and
comprehension of the document.

New information Location

Addition of error codes C56 and E75 (no longer Error codes C56 and E75
available)

Addition of error code N34 Error code N34

Updated information Location

Update text of error codes C24, E06, E37, E41, E64,

E68, G06, H51, T14, T36, T67, T78, and T97 Section 3.4.1, C Error Codes
Section 3.4.3, E Error Codes

Section 3.5, G Codes - Service-specific

Validation

Section 3.6, H Codes - Basic Header and

Application Header Validation

Section 3.15, T Codes - Text Validation

4 Error Codes
 Chapter 1 Introduction

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.

Where two or more variants of a message exist, for example, MT 103, MT 103 STP and MT 103 REMIT, each
variant is referenced independently in an error code description. This means that mention of the MT 103 refers
only to the generic variant of the MT 103 and does not include either the MT 103 STP or the MT 103 REMIT.

25 July 2014 5
FIN

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.

01 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.

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:

010 Re-Login Request received while logical terminal is active on the Logical Terminal Control
association

6 Error Codes
 Chapter 2 Numeric Codes

011 Logical Terminal Control state error, unable to recover the logical terminal session

012 Re-Login Request authentication failed

013 Re-Login Request semantic error

014 Re-Login Request format error

015 Re-Login Request login request number is incorrect

016 Multiple Re-Logins from user

017 Re-Login Request received while the logical terminal is in unrecoverable state

019 Re-Login Request, session recovery information: incorrect General Purpose Application session
number

020 Re-Login Request, session recovery information: incorrect input sequence number

021 Re-Login Request, session recovery information: input sequence number-ACK greater than
input sequence number

022 Re-Login Request, session recovery information: input sequence number-ACK less than the
lower bound

023 Re-Login Request, session recovery information: incorrect output sequence number

024 Re-Login Request, session recovery information: incorrect window size

026 Re-Login Request, login and re-login protocol versions are not the same

027 Re-Login Request, logical terminal does not belong to Sign Distinguished Name (DN)
organisation

028 Re-Login Request, the Live destination that owns the Test and Training destination does not
belong to Sign Distinguished Name (DN) organisation

2.4 Retrieval Errors

The following codes are returned in field 421 of message retrievals:

000 Message has no text block

002 Message was encrypted and no key or the wrong key was supplied by the user

25 July 2014 7
FIN

003 Empty report (no messages found)

004 Logical terminal is not authorised to retrieve the message, that is the requester is neither the
sender nor the receiver of the original message

005 Text lost due to Slice Processor recovery

006 History lost due to Slice Processor recovery

007 Target message is a retrieval report (MTs 021 or 023)

010 Invalid MT received by Slice Processor pseudo logical terminal (system)

011 Invalid <application-id> received by Slice Processor pseudo logical terminal (system)

012 Invalid date in retrieval criteria tag (system)

013 Invalid time in retrieval criteria tag (system)

014 End daytime before start daytime

015 Target message older than 124 days (for range retrieval, daytime used)

016 <branch-code> is not 'XXX'

018 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

019 Invalid input retrieval by receiver or output retrieval by sender (only single message input
reference/message output reference allowed)

020 Invalid synonym retrieval (synonym is not sender or receiver of message)

021 Unknown target logical terminal

022 Request received at wrong Slice Processor (system)

023 Could not retrieve message input reference in message output reference retrieval (system)

032 No delivery attempt in message input reference retrieval by receiver

033 On-line text read error (system)

034 On-line history read error (system)

8 Error Codes
 Chapter 2 Numeric Codes

035 Text read error from archival (system)

036 History read error from archival (system)

037 Partial report - major system recovery in progress

038 Unable to retrieve text and history from archival because of system problems

040 The limits for group retrieval (99 messages in one request) have been exceeded

041 Message could not be decrypted (system)

043 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)

044 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)

045 Message text not retrievable (message not successfully delivered)

046 Off-line retrieval not allowed for Test and Training messages

047 The text of local test mode messages is not retrievable

048 Retrieval message too long

049 Retrieval period specified exceeds 10 days

099 Retrieval report problem. Contact your Customer Support Centre

2.5 Message Status

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

01 Delivered

02 Rejected by destinee

04 Aborted

25 July 2014 9
FIN

07 No delivery attempt

08 One or more unsuccessful attempts

10 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 Intercepted

29 Message held for approval prior to Bypass mode and aborted

31 Authorised by the copy service or Sanctions Screening over SWIFT service subscriber and
delivered

32 Not authorised by the copy service or Sanctions Screening over SWIFT service subscriber and
aborted by the system

33 Copy message is aborted and not delivered to the copy service

34 Authorised by the copy service or Sanctions Screening over SWIFT service subscriber but
aborted by the system

35 Not yet authorised/refused by the copy service or Sanctions Screening over SWIFT service
subscriber

37 Authorised by the copy service or Sanctions Screening over SWIFT service subscriber but no
delivery attempted

38 Authorised by the copy service or Sanctions Screening over SWIFT service subscriber but one
or more unsuccessful delivery attempts

41 Copy service bypassed and message delivered

44 Copy service bypassed but message aborted by the system

47 Copy service bypassed but no delivery attempted

48 Copy service bypassed but one or more unsuccessful delivery attempts

49 Refused by central institution. Abort notification MT 019 contains an alphanumeric abort code

10 Error Codes
 Chapter 2 Numeric Codes

50-99 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.

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:

01 Message too old (remained undelivered for n days)

02 Too many unsuccessful delivery attempts

03 Destination disabled

04 Operator aborted

05 Message could not be recovered after a major system failure because it was user encrypted

06 Message type incompatible with the FIN interface mode

11 Message is too old, but was authorised

12 Too many delivery attempts, but message was authorised

13 Destination is disabled, but message was authorised

14 Message is too long, but was authorised

21 Message is too old and was bypassed

22 Too many delivery attempts and the message was bypassed

23 Destination is disabled and the message was bypassed

24 Message is too long and was bypassed

25 July 2014 11
FIN

29 Message held for approval prior to Bypass mode and aborted

32 Message is too old and was not authorised

33 Copy message to the copy service server was aborted

35 FINCopy service parameter(s) incorrectly defined in FIN

50-ZZ 99 is pre-defined as 'system error'.

All other alphanumeric codes (combination of 0-9 and A-Z) are specific to each FINCopy
service. Contact your respective service provider for the meaning of each code.
Code S1 is used by the Sanctions screening service to indicate that the message has been
aborted on request of the subscribing user.
Note: All undefined numeric codes are reserved for use by FIN.

2.7 FIN and General Purpose Application Session Termination

The following codes are returned in field 443 of Service Message 14 (for further details see FIN System
Messages):

000 Normal termination

001 Application Control or Logical Terminal Control has aborted

002 Application Control or Logical Terminal Control has terminated normally

004 System timed out message output reference ACK

006 QUIT or LOGOUT received while outstanding input messages

007 Input message/Service message after reception of a QUIT or LOGOUT

008 Input window violation (more outstanding input messages than window size)

009 System timed out on association establishment

010 Reception of a SELECT from a logical terminal that already has a FIN session

011 Association establishment request failed authentication

014 Message output reference ACK Basic Header error

015 Too many messages input in a session. Maximum is 500000.

12 Error Codes
 Chapter 2 Numeric Codes

016 Too many messages output in a session. Maximum is 500000.

020 Message output reference ACK from wrong synonym

025 As for 052 but due to receipt of a Re-Login Request, rather than a Login Request

051 As for 052 but on a different Regional Processor

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.

053 SELECT with bad text block

054 AP ABORT REQUEST with bad text block

2.8 Report Errors

The following codes are returned in field 461 of Delivery Subset Status Reports, Undelivered Message
Reports, and Undelivered SSI Update Notification Reports:

001 Empty report

002 End of undelivered report

003 System undergoing major recovery or system not completely synchronised yet

004 Too many undelivered messages

005 User on fall back Regional Processor, cannot generate report

006 The message referenced in the request could not be found.

007 Invalid destination for report. The sender of the request must be the same as the sender of the
message referenced in the request.

008 No MTs 671 were found for the referenced MT 670.

009 Requesting logical terminal in invalid state

016 Branch code is not "XXX'

099 System internal problems, contact your Customer Support Centre

25 July 2014 13
FIN

2.9 Bulk Retrieval Errors Codes

The following codes are returned in field 144 of Bulk Retrieval Responses (MT 025):

03 Retrieval only partially complete

11 Invalid <start-date-time>

12 Invalid <end-date-time>

13 Invalid retrieval time range

14 Retrieval aborted due to system error

15 Retrieval aborted due to communication error

16 Retrieval aborted by SWIFT

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 Retrieval aborted due to system error (Test and Training destination - attempt to use tape)

21 Retrieval aborted due to system error (FIN/FIN Bridge key error)

22 Retrieval aborted due to system error (missing master BIC)

14 Error Codes
 Chapter 3 Alphanumeric Codes

Chapter 3 Alphanumeric Codes

3.1 General
This chapter contains the codes for the following error types:

Code Error Type Code Error Type

A Abort at Application Interface Level Errors P Protocol Errors

A Re-select Errors R Re-login/Re-select Errors

B Copy Service Errors S System-initiated Abort Errors

C Dialout Errors S Select Errors

C, D Conditional Semantic Errors T Text validation (Block 4) Errors

and E

G Service-specific Validation Errors U User Header Validation Errors

H Basic Header and Application Header U User Abort Errors

Validation Errors

K Code Words Errors in Generic Fields V System Message or Message Block

Format Errors

L LOGIN Errors X Delayed NAK Errors and FINCopy

Service Message Refusals

M Message Errors Y User Negative Acknowledgement Errors

N Market Infrastructure Resiliency Service Z Trailer Validation Errors

(MIRS) 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 - 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 FIN interface should execute a fresh select procedure.

3.3 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.

B02 Available.

25 July 2014 15
FIN

B03 103:TPS is present in the message but the sender is not a member of TPS, or the message is
not allowed for TPS.

B04 Available.

B05 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.4 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.

3.4.1 C Error Codes

C00 Not used.

C01 MTs 102, 102 STP, 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.
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.

16 Error Codes
 Chapter 3 Alphanumeric Codes

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, 103 REMIT, and 103 STP. 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 MTs 103, 103 REMIT, 103 STP 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, 102 STP, 104, 107, 201, 203, 204, and 559 where the corresponding
currency is the one used in field 32B or 34A

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

field 33B in MTs 103, 103 REMIT, 103 STP and in MTs 104 and 107, sequence B

field 71F in MTs 103, 103 REMIT, 103 STP and in MTs 104 and 107, sequences B and C

field 71G in MTs 103, 103 REMIT, 103 STP and in MTs 104 and 107, sequences B and C

field 72 Reject/Return in MTs 103, 103 REMIT, 103 STP 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 ... Then field :19B::TCRL is ...

Not present Mandatory

25 July 2014 17
FIN

Sequence B

If field :19B::TEXA is ... Then field :19B::TCRL is ...

Present Optional

C05 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 Field Sequence(s) Qualifier Comments

101 52A A, B

56A B

57A B

102 52A A, B

53A C The same validation applies to the

54A C MT 102 and the MT 102 STP

57A B

103 52A

53A

54A The same validation applies to the

MT 103, MT 103 REMIT, and the
55A MT 103 STP
56A

57A

104 52A A, B
Note: For sequence C, see
53A C
error code C96.
57A B

107 52A A, B

53A C

57A B

110 52A

53A

54A

111, 52A
112

200, 56A
201
57A

18 Error Codes
 Chapter 3 Alphanumeric Codes

MT Field Sequence(s) Qualifier Comments

202, 52A
203
53A

54A

56A

57A

58A

202 52A A
COV
53A A

54A A

56A A

57A A

58A A

52A B

56A B

57A B

204 53A B

57A A

58A A

205 52A

53A

56A

57A

58A

205 52A A
COV
53A A

56A A

57A A

58A A

52A B

56A B

57A B

207 51A A

52A A

25 July 2014 19
FIN

MT Field Sequence(s) Qualifier Comments

52G A

56A B

57A B

58A B

210 52A

56A

256 57A C

300 53AJ B1, B2, D

56AJ B1, B2, D

57AJ B1, B2, D

303 53AJ D1, D2, D3

56AJ D1, D2, D3

57AJ D1, D2, D3

304 53AJ B, E

56AJ B, E

57AJ B, E

305 53A

56A

57A

306 53AJ C, E, J

56AJ C, E, J

57AJ C, E, J

84AJ B

86AJ C, E, J

307 95P B3a CDEA INTE ACCW

95P D1 CDEA INTE ACCW

320 53AJ C, D, E, F, I

56AJ C, D, E, F, I

57AJ C, D, E, F, I

86AJ C, D, E, F, I

321 95P C1 CDEA INT2 INTE

ACCW

330 53AJ C, D, E, F

20 Error Codes
 Chapter 3 Alphanumeric Codes

MT Field Sequence(s) Qualifier Comments

56AJ C, D, E, F

57AJ C, D, E, F

86AJ C, D, E, F

340 53AJ C, D, F

56AJ C, D, F

57AJ C, D, F

86AJ C, D, F

341, 53AJ C
350
56AJ C

57AJ C

86AJ C

360 53A D, G, L, M

56A D, G, L, M

57A D, G, L, M

86A D, G, L, M

361 53A D, G, J, K, L,
M

56A D, G, J, K, L,
M

57A D, G, J, K, L,
M

86A D, G, J, K, L,
M

362 53A C, E

56A C, E

57A C, E

86A C, E

364 53A L, M

56A L, M

57A L, M

86A L, M

365 53A J, K, L, M

56A J, K, L, M

57A J, K, L, M

86A J, K, L, M

25 July 2014 21
FIN

MT Field Sequence(s) Qualifier Comments

370 95P B1 ACCW INT1 INT2

400 52A

53A

54A

57A

58A

416 53A A

450, 52A
455,
456

502 95P C2 ACCW INTM PAYE

504 95P C2a1, E1 ACCW INTM PAYE

505 95P B2a1, D1 ACCW INTM PAYE

507 95P B1b1 ACCW INTM PAYE

513 95P D2 ACCW INTM PAYE

514 95P C2 ACCW INTM PAYE

515 95P D2 ACCW INTM PAYE

516 57A B

518 95P C2 ACCW INTM PAYE

540, 95P E2 ACCW INTM PAYE

541,
542,
543,
544,
545,
546,
547

559 57A

566 95P D2a ACCW

578 95P E2 ACCW INTM PAYE

600 53A B

56A B, C

57A B, C

86A B, C

87A B, C

601 53A

56A

22 Error Codes
 Chapter 3 Alphanumeric Codes

MT Field Sequence(s) Qualifier Comments

57A

604 86A

87A

605 86A

87A

606 86A

87A

607 86A

87A

620 53AJ C, D, E, F

56AJ C, D, E, F

57AJ C, D, E, F

86AJ C, D, E, F

643 57A B, C

644 57A B

646 57A C

670 95P B1 ACCW INT1 INT2

700 41A

42A

51A

53A

57A

705 41A

57A

707 52A

710 41A

42A

51A

52A

53A

57A

720 41A

42A

25 July 2014 23
FIN

MT Field Sequence(s) Qualifier Comments

52A

57A

730, 57A
734

740 41A

42A

58A

742 52A

57A

58A

750 57A

752 53A

54A

754 53A

57A

58A

756 53A

54A

768, 57A
769

800 51A

52A

53A

54A

801 51A

802 52A

53A

54A

824 51A

900 52A

910 52A

56A

985 57A

n90 52A

24 Error Codes
 Chapter 3 Alphanumeric Codes

MT Field Sequence(s) Qualifier Comments

n91 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 ... Then field 50B is ...

Present Not allowed

Not present Mandatory

MT 910
Either field 50a or field 52a, but not both, must be present.

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

C08 MT 300
In fields listed below, the codes XAU, XAG, XPD and XPT are not allowed, as these are codes
for commodities for which the category 6 commodities messages must be used:

Subsequence B1, Amount Bought, field 32B Currency Amount,

Subsequence B2, Amount Bought, field 33B Currency Amount,

Sequence C, Optional General Information, field 71F Broker's Commission,

Sequence D, Split Settlement Details, field 32B Currency Amount.

MT 304
In fields listed below, the codes XAU, XAG, XPD and XPT are not allowed, as these are codes
for commodities for which the category 6 commodities messages must be used:

Subsequence B1, Amount Bought, field 32B Currency Amount,

Subsequence B2, Amount Bought, field 33B Currency Amount,

Sequence D, Accounting Information, field 32G Currency Amount,

Sequence E, Net Amount to be Settled, field 32G Currency Amount.

MT 305
In fields listed below, the codes XAU, XAG, XPD and XPT are not allowed, as these are codes
for commodities for which the category 6 commodities messages must be used:

32B Underlying Currency And Amount,

33B Counter Currency And Amount,

34a Premium Payment.

25 July 2014 25
FIN

MT 306
In fields listed below, the codes XAU, XAG, XPD and XPT are not allowed, as these are codes
for commodities for which the category 6 commodities messages must be used:

Subsequence B1, Premium Details, field 34B Premium Currency And Amount,

Sequence D, Vanilla Block, field 32B Put Currency And Amount,

Sequence D, Vanilla Block, field 33B Call Currency And Amount,

Sequence E, Payout Amount, field 33E Put Currency Amount,

Sequence G, Trigger Block, field 32Q Put Currency Pair,

Sequence H, Non Deliverable Option Block, field 32E Settlement Currency,

Sequence I, Additional Information, field 71F Broker's Commission,

Sequence J, Additional Amount, field 32H Currency Payment Amount.

C09 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.

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 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.

26 Error Codes
 Chapter 3 Alphanumeric Codes

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 ... Then sequence D is ...

Not present Mandatory

Present (once or more) Optional

C22 MT 920
If field 12 contains the value '942', at least field 34F Debit/(Debit and Credit) Floor Limit Indicator
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.

C24 MT 940
If field 86 is present in any occurrence of the repetitive sequence, it must be preceded by a field
61.
MT 942
If field 86 is present in any occurrence of the repetitive sequence, it must be preceded by a field
61.
Note: This rule does not apply for the field 86 if it is the last field in the message.
When field 86 is the last field in the message and it is not preceded by a field 61,
then it is considered to provide information about the message as a whole.

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 ... Then copy of any field(s) of original

message is ...

Present Optional

Not present Mandatory (that is, minimum one field, any

field)

25 July 2014 27
FIN

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 MTs 541, 543, and 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 Sequence E In the same occurrence of

subsequence E3 then field :22F::STCO//SPST subsequence E3
if field :98a::VALU is ... (with DSS not present) and field :19A::SETT is ...

Present Mandatory Mandatory

Not present Optional Optional

MTs 544, 545, 546, and 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 ... Then field :19A::ESTT is ...

Present Mandatory

Not present Optional

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 B5b, 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 B5b.

In any occurrence of Subsequence B5 In the same occurrence of

subsequence B5b then field :22F::STCO//SPST (with subsequence B5b
if field :98a::VALU is ... DSS not present) is ... and field :19A::SETT is ...

Present Mandatory Mandatory

28 Error Codes
 Chapter 3 Alphanumeric Codes

In any occurrence of Subsequence B5 In the same occurrence of

subsequence B5b then field :22F::STCO//SPST (with subsequence B5b
if field :98a::VALU is ... DSS not present) is ... and field :19A::SETT is ...

Not present Optional Optional

C29 Available.

C30 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.
Note: SWIFT does not validate the relationship between the copied fields and the
original message; hence any valid fields are accepted.

C32 MTs 300, 303, 304, 305, 306, 320, 330, 340, 341, 350, 360, 361, 362, 364, 365, 600, 601, 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.

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

C38 Available.

C39 Available.

C40 MT 920
The currency code must be the same for each occurrence of field 34F within each repetitive
sequence.

25 July 2014 29
FIN

C41 Available.

C42 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.

Sequence A1 Sequence E
if field :36B: is ... then field :22F::SETR must be ...

Present :22F::SETR//PAIR and DSS must not be

present
or
:22F::SETR//TURN and DSS must not be
present

Not present Not applicable

C51 MT 643
If field 23 contains LOAN/DRAWDOWN or LOAN/RENEWAL, field 31R must be present.

30 Error Codes
 Chapter 3 Alphanumeric Codes

C52 Available.

C53 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 MT 300
In sequence E, the presence of field 22Q depends on field 17Z as follows:

Sequence E

If field 17Z is ... Then field 22Q is ...

Y Mandatory

N Optional

Not present Optional

MTs 305 and 601

In sequence B, the presence of field 22Q depends on field 17Z as follows:

Sequence B

If field 17Z is ... Then field 22Q is ...

Y Mandatory

N Optional

Not present Optional

MT 306
In sequence K, the presence of field 22Q depends on field 17Z as follows:

Sequence K

If field 17Z is ... Then field 22Q is ...

Y Mandatory

N Optional

Not present Optional

MT 340
In sequence G, the presence of field 22Q depends on field 17Z as follows:

Sequence G

If field 17Z is ... Then field 22Q is ...

Y Mandatory

25 July 2014 31
FIN

Sequence G

If field 17Z is ... Then field 22Q is ...

N Optional

Not present Optional

MTs 341 and 600

In sequence D, the presence of field 22Q depends on field 17Z as follows:

Sequence D

If field 17Z is ... Then field 22Q is ...

Y Mandatory

N Optional

Not present Optional

MTs 360 and 361

In sequence O, the presence of field 22Q depends on field 17Z as follows:

Sequence O

If field 17Z is ... Then field 22Q is ...

Y Mandatory

N Optional

Not present Optional

C57 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 error code C59.
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 error code C59.
MT 305
In field 72 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 ":72:/VALD/"YYYYMMDD"CrLf".
See error code C59.

32 Error Codes
 Chapter 3 Alphanumeric Codes

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.

C59 MT 300
In sequence A, if field 77D is present, then:

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 six (6) characters, followed by a valid
ISO 4217 currency code and the end of line separator, that is, "/SETC/"<CUR>"CrLf".

if 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 any other place than the first six (6) characters of the
second line.

if the first six (6) characters of the third line are equal to /SRCE/, then the first six (6)
characters of the second line must be equal to "/SETC/".
the code "/SRCE/" is not allowed in any other place than the first six (6) characters of the
third line.

See error code C58.

MT 304
In sequence C, if field 72 is present, then:

if the first six (6) characters of the second line are equal to /SETC/, then it must be followed
by a valid ISO 4217 currency code and the end of line separator, that is, "/SETC/
"<CUR>"CrLf".
if 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 any other place than the first six (6) characters of the
second line.

if the first six (6) characters of the third line are equal to /SRCE/, then the first six (6)
characters of the second line must be equal to "/SETC/".

the code "/SRCE/" is not allowed in any other place than the first six (6) characters of the
third line.

See error code C58.

MT 305
In sequence A, if field 72 is present, then:

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 six (6) characters, followed by a valid
ISO 4217 currency code and the end of line separator, that is, "/SETC/"<CUR>"CrLf".

if 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 any other place than the first six (6) characters of the
second line.

if the first six (6) characters of the third line are equal to /SRCE/, then the first six (6)
characters of the second line must be equal to "/SETC/".

25 July 2014 33
FIN

the code "/SRCE/" is not allowed in any other place than the first six (6) characters of the
third line.

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:

Sequence A Sequence B
if field
:22H::TLDE Then field And field And field And field And field
is ... :98A::INTR is :19A::SETT :19A::RODI :19A::CINT is :19A::NINT
... is ... is ... ... is ...

CONF Mandatory Not allowed Not allowed Not allowed Mandatory

ROLL Mandatory Mandatory Optional Optional Mandatory

MATU Not allowed Mandatory Not allowed Optional Not allowed

MT 800
The amounts in fields 34B and 32A must be the same.

C60 MT 307
In sequence A, the presence of field :22H::APER and the presence of field :22H::NEGR
depends on the field :22H::CRTR as follows:

Sequence A

If field :22H::CRTR is ... Then field :22H::APER is ... And field :22H::NEGR is ...

ASET Not allowed Optional

AFWD Mandatory Mandatory

MT 321
In sequence A, the presence of field :99B:: depends on the presence of field :22H::BLOC as
follows:

Sequence A

If field :22H::BLOC is ... Then field :99B:: is ...

Present Mandatory

Not present Not allowed

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:

Sequence A

If field :22H::APER is ... Then field :22H::PAFI is ...

OPEF Not allowed

NOPE Mandatory

34 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A

If field :22H::APER is ... Then field :22H::PAFI is ...

Field :22H::APER not present Not allowed

MT 321
In sequence B, the presence of field :98A::LDFP depends on the value of field :22H::TLDE in
sequence A as follows:

Sequence A Sequence B
if field :22H::TLDE is ... then field :98A::LDFP is ...

MATU Not allowed

Not MATU Optional

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:

Sequence A Then sequence C

if field :22H::APER is ... is ...

OPEF Not allowed

NOPE Mandatory

Field :22H::APER not present Not allowed

MT 321
In sequence B, the presence of field :99B::DAAC depends on the presence of field :98A::LDFP
as follows:

Sequence B

If field :98A::LDFP is ... Then field :99B::DAAC is ...

Present Mandatory

Not present Not allowed

C63 MT 307
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:

Sequence A Then field :22H::NEGR//UNKN is ...

if field :22H:: is ...

CRTR//ASET Not allowed

CRTR//AFWD and APER//OPEF Optional

CRTR//AFWD and APER//NOPE and Optional

PAFI//PAIN

CRTR//AFWD and APER//NOPE and Not allowed

PAFI//FINA

25 July 2014 35
FIN

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:

Sequence A Then sequence

D is ...
If field And field And field And field
:22H::CRTR is :22H::APER is :22H::PAFI is ... :22H::NEGR is
... ... ...

ASET Not applicable Not applicable NETC Optional

per rule 60 per rule 61

ASET Not applicable Not applicable GRSC Not allowed

per rule 60 per rule 61

ASET Not applicable Not applicable Not present Not allowed

per rule 60 per rule 61

AFWD OPEF Not applicable NETC or GRSC Not allowed

per rule 61 or UNKN

AFWD NOPE PAIN NETC or GRSC Not allowed

or UNKN

AFWD NOPE FINA NETC Mandatory

AFWD NOPE FINA GRSC Not allowed

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...).
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.

Sequence A Then, in every occurrence of sequence A2

if field 23G is ... field :25D must be ...

CAST :25D::CPRC...

INST :25D::IPRC...

EVST :25D::EPRC...

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.

36 Error Codes
 Chapter 3 Alphanumeric Codes

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:

Sequence B (each occurrence)

If subsequence B1 And field Then subsequence And subsequence

is ... :22H::COLL//Status B1a is ... B1b is ...
is ...

Present CCOL Not allowed Mandatory

SCOL Mandatory Not allowed

BCOL Not applicable Not applicable

(Not applicable see
error code C70)

Not present Not applicable Not applicable Not applicable

Note: Error code C70 takes precedence over error code C69.

C70 MT 507
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:

Sequence B (each occurrence)

If field :25D::COLL/ And field And field Then subsequence

[8c]/4!c Data Source :25D::COLL/[8c]/4!c :22H::COLL//4!c is ... B1 is ...
Scheme [8c] is ... is ...

Not present :25D::COLL//ACCT BCOL Not allowed

:25D::COLL//ACCT CCOL Mandatory [1]

:25D::COLL//ACCT SCOL Mandatory [1]

:25D::COLL//REJT Not applicable Not allowed

Present Not applicable BCOL Not allowed

CCOL Optional [1]

SCOL Optional [1]

[1] See error code C69 for additional checks. Error code C70 takes precedence over error code
C69.

C71 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.

25 July 2014 37
FIN

Subsequence B1 Then one occurrence of And the other occurrence

if field :93B::AGGR is ... :93B::AGGR must be ... of :93B::AGGR must be ...

Repeated :93B::AGGR//FAMT and DSS :93B::AGGR//AMOR and

must not be present DSS must not be present

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :36B::PSTA is ... :36B::PSTA must be ... of :36B::PSTA must be ...

Repeated :36B::PSTA//FAMT :36B::PSTA//AMOR

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :36B::PSTA is ... :36B::PSTA must be ... of :36B::PSTA must be ...

Repeated :36B::PSTA//FAMT :36B::PSTA//AMOR

Not repeated Not applicable Not applicable

MTs 540, 541, 542, and 543

In 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 Then one occurrence of And the other occurrence

if field :36B::SETT is ... :36B::SETT must be ... of :36B::SETT must be ...

Repeated :36B::SETT//FAMT :36B::SETT//AMOR

Not repeated Not applicable Not applicable

MTs 544, 545, 546, and 547

In 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 Then one occurrence of And the other occurrence

if field :36B::SETT is ... :36B::ESTT must be ... of :36B::ESTT must be ...

Repeated :36B::ESTT//FAMT :36B::ESTT//AMOR

Not repeated Not applicable Not applicable

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.

38 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence B Then one occurrence of And the other occurrence

if field :36B::SETT is ... :36B::SETT must be ... of :36B::SETT must be ...

Repeated :36B::SETT//FAMT :36B::SETT//AMOR

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :93B::ELIG is ... :93B::ELIG must be ... of :93B::ELIG must be ...

Repeated :93B::ELIG//FAMT and DSS :93B::ELIG//AMOR and DSS

must not be present must not be present

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :93B::ELIG is ... :93B::ELIG must be ... of :93B::ELIG must be ...

Repeated :93B::ELIG//FAMT and DSS :93B::ELIG//AMOR and DSS

must not be present must not be present

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :93B::ELIG is ... :93B::ELIG must be ... of :93B::ELIG must be ...

Repeated :93B::ELIG//FAMT and DSS :93B::ELIG//AMOR and DSS

must not be present must not be present

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :36B::STAQ or QREC :36B::STAQ or QREC must of :36B::STAQ or QREC
is ... be ... must be ...

Repeated :36B::STAQ//FAMT or :36B::STAQ//AMOR

:36B::QREC//FAMT :36B::QREC//AMOR

Not repeated Not applicable Not applicable

25 July 2014 39
FIN

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 Then one occurrence of And the other occurrence

if field :93B::ELIG is ... :93B::ELIG must be ... of :93B::ELIG must be ...

Repeated :93B::ELIG//FAMT and DSS :93B::ELIG//AMOR and DSS

must not be present must not be present

Not repeated Not applicable Not applicable

MT 707
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 Then one occurrence of And the other occurrence

if field :36B::PSTA is ... :36B::PSTA must be ... of :36B::PSTA must be ...

Repeated :36B::PSTA//FAMT :36B::PSTA//AMOR

Not repeated Not applicable Not applicable

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 Then one occurrence of And the other occurrence

if field :36B::ENTL is ... :36B::ENTL must be ... of :36B::ENTL must be ...

Repeated :36B::ENTL//FAMT :36B::ENTL//AMOR

Not repeated Not applicable Not applicable

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 D Then one occurrence of And the other occurrence

if field :36B::QINS or QREC :36B::QINS or QREC must of :36B::QINS or QREC
is ... be ... must be ...

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

:36B::QREC//FAMT :36B::QREC//FAMT

Not repeated Not applicable Not applicable

40 Error Codes
 Chapter 3 Alphanumeric Codes

Note: Therefore the only valid repetitions are:

:36B::QINS//FAMT

:36B::QINS//AMOR

or

: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 Then one occurrence of And the other occurrence

if field :36B::PSTA is ... :36B::PSTA must be ... of :36B::PSTA must be ...

Repeated :36B::PSTA//FAMT :36B::PSTA//AMOR

Not repeated Not applicable Not applicable

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.

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.

25 July 2014 41
FIN

If field 23E is not present in sequence A, then field 23E must be present in all occurrences
of sequence B.

Sequence A Sequence B
if field 23E is ... then field 23E is ...

Present and = RFDD Mandatory in all occurrences

Present and not = RFDD Not allowed

Not present Mandatory in all occurrences

Note: See error codes C94 and C96.

C76 MT 104
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 In every occurrence of sequence B,

if field 50a (option A or K) is ... then field 50 (option A or K) is ...

Present Not allowed

Not present Mandatory

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 Unit must be the same for all occurrences of the indicated fields in the entire message.
Note: Error code D07 takes precedence over error code C80.

C81 MTs 103, 103 REMIT, 103 STP, 202, 202 COV (sequence A), 203, 205, and 205 COV
(sequence A)
If field 56a is present, then field 57a must also be present.

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 ... Then field 72 is ...

Present and = RTND Mandatory

42 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A

If field 23E is ... Then field 72 is ...

Present and not = RTND Not allowed

Not present Not allowed

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 ... Then field 21 is ...

AMNA Mandatory

AMND Mandatory

CANC Mandatory

DUPL Optional

NEWT Optional

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 Available.

C88 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.
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).

25 July 2014 43
FIN

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 Then sequence B is ... And sequence C is ...
if field 94A is ...

FORX Mandatory Not allowed

FXOP Not allowed Mandatory

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 User Header

if field 23E is ... then field 119 is ...

Present and = RFDD Mandatory and must contain RFDD

Present and not = RFDD Not allowed

Not present Not allowed

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.

C95 MT 303
In sequence C, the presence of field 30X depends on field 23B as follows:
Sequence C

If field 23B is ... Then field 30X is ...

CLAM or PTAM Mandatory

CLEU or PTEU Not allowed

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

44 Error Codes
 Chapter 3 Alphanumeric Codes

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 Sequence B
and fields 21E, 50a And sequence C is
If field 23E is ... Then field 21R is ... (option A or K), 52a, ...
71F and 71G are ...

Present and = RFDD Optional Not allowed Not allowed

Present and not = Not allowed Optional Mandatory

RFDD

Not present Not allowed Optional 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 Then sequence D is ...
if field 22A is ...

AMNA, AMND, DUPL or NEWT Mandatory

CANC Optional

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:
Sequence(s) C Then sequence D is ...

If in one or more occurrence(s) of sequence Mandatory

C:
subsequence C1 is present and
an internal subsequence C1a is not present

Note: See error code D49.

MT 505
The presence of sequence C is mandatory when in any occurrence of sequence B,
subsequence B1 is present and subsequence B1a is not present:
Sequence(s) B Then sequence C is ...

If in one or more occurrence(s) of sequence Mandatory

B:
subsequence B1 is present and
an internal subsequence B1a is not present

25 July 2014 45
FIN

Note: See error code D49.

C98 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 Sequence

300 E

305, 601 B

306 I, K

320, 330, 620 H

340 E, G

341, 600 D

360, 361 O

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 Then subsequence D3 is ...
if field 94A is ...

FORX Not allowed

FXOP Mandatory

MT 504
Sequence E is mandatory when in any occurrence of sequence C, subsequence C2 is present
and subsequence C2a is not present.

Sequence(s) C Then sequence E is ...

If in one or more occurrence(s) of sequence Mandatory

C:
subsequence C2 is present and an internal
subsequence C2a is not present

Note: See error code D50.

MT 505
Sequence D is mandatory when in any occurrence of sequence B, subsequence B2 is present
and subsequence B2a is not present.

Sequence(s) B Then sequence D is ...

If in one or more occurrence(s) of sequence Mandatory

B:
subsequence B2 is present and an internal
subsequence B2a is not present

Note: See error code D50.

46 Error Codes
 Chapter 3 Alphanumeric Codes

3.4.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 Not used.

D01 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 ... Then field 21 is ...

AMND Mandatory

CANC Mandatory

DUPL Optional

NEWT Optional

MTs 306 and 340

In sequence A, the presence of field 21 depends on field 22A as follows:
Sequence A

If field 22A is ... Then field 21 is ...

AMND Mandatory

CANC Mandatory

NEWT Optional

MT 341
In sequence A, the presence of field 21 depends on field 22A as follows:
Sequence A

If field 22A is ... Then field 21 is ...

AMND Mandatory

CANC Mandatory

SETT Optional

25 July 2014 47
FIN

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 ... Then field 21 is ...

ADVC Optional

Not = ADVC Mandatory

D03 MT 304
In sequence A, the presence of fields 17O and 17N depends on field 94A as follows:
Sequence A

If field 94A is ... Then field 17O is ... And field 17N is ...

ASET Not allowed Not allowed

AFWD Mandatory Mandatory

Note: See also error codes D04 and D29.

MT 535
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 Then in any occurrence(s) of subsequence
if field :94a: is ... B1b,
field :93B::AGGR and field :94a::SAFE are
...

Present Not allowed

Not present Optional

D04 MT 304
In sequence A, the presence of field 17F depends on field 17O as follows:
Sequence A

If field 17O is ... Then field 17F is ...

Y Not allowed

N Mandatory

Not present Not allowed

Note: See also error codes D03 and D29.

MT 535
If field :93B::AGGR is present in subsequence B1b, then field :94a::SAFE must be present in the
same subsequence B1b:
Sequence B1b Then in same subsequence B1b,
if field :93B::AGGR is ... field :94a::SAFE is ...

Present Mandatory

48 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence B1b Then in same subsequence B1b,

if field :93B::AGGR is ... field :94a::SAFE is ...

Not present Optional

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 MTs 600, 601, 604, 605, 606, and 607

When GOLD is defined in subfield 4 (Type) of field 26C, then the Unit in field 32F must not be
GOZ nor TOZ.
MT 608
When GOLD is defined in subfield 4 (Type) of field 26C, then the Unit GOZ and TOZ can not be
used in the following fields:

Field 60a Opening Balance (Option F&M),

Field 62a Closing Balance (Option F&M),

Field 64 Closing Available Balance,

Field 65 Forward Available Balance.

Note: See error code C80 for additional checks. Error code D07 takes precedence
over error code C80.
MT 609
The Unit in field 68a (Option B&C) must not be GOZ nor TOZ when GOLD is defined in subfield
4 (Type) of immediately preceding field 26C.
MT 620
When GOLD is defined in subfield 4 (Type) of field 26C, then the Unit GOZ and TOZ can not be
used in the following fields:

Mandatory Sequence B field 32a Currency and Principal Amount (Option F only),

Mandatory Sequence B field 32a Amount to be Settled (Option R only),

Mandatory Sequence B field 34a Currency and Interest Amount (Option J only),

Optional Sequence G Mandatory Subsequence G1 field 33a Transaction Currency and Net
Interest Amount (Option J only),

Optional Sequence G Optional Subsequence G2 field 33a Reporting Currency and Tax
Amount (Option J only).

D08 MT 670
In subsequence A2, either field :95P::SSIR or field :94C::SSIR or field :22H::SSIR must be
present:

25 July 2014 49
FIN

Subsequence A2

If field :95P::SSIR is ... Then field :94C::SSIR is ... And field:22H::SSIR is ...

Present Not allowed Not allowed

Not present Present Not allowed

Not present Mandatory

D09 MT 670
In sequence A, field :95P::SUBM must specify the same BIC as the Sender in the basic header.
If the branch code of the Sender's BIC is XXX, then the branch code is not required in field
:95P::SUBM. If the branch code of the Sender's BIC is not XXX, then the branch code in field
:95P::SUBM must be the same. If the branch code of :95P::SUBM is present, then the branch
code of the Sender's BIC must be the same.
Note: If the Sender's BIC is a Test and Training BIC then it's owning master's
registered BIC, and only its owning master's registered BIC, with or without a
branch code, is also allowed in field :95P::SUBM Submitting Party.

D10 Available.

D11 MT 370
In sequence B Netting Position Details, if subsequence B1 Cash Parties contains field
:95a::INT2 Second Intermediary then :95a::INT1 Intermediary must be present in another
subsequence B1 Cash Parties:
Subsequence B1 Then in another subsequence B1
if field :95a::INT1 is ... field :95a::INT2 ...

Present Optional

Not present Not allowed

MT 670
In each occurrence of sequence B, if subsequence B1 contains field :95a::INT2 then :95a::INT1
must be present in another subsequence B1:
Within each occurrence of sequence B In the same occurrence of sequence B
in subsequence B1 then in another subsequence B1
if field :95a::INT1 is ... field :95a::INT2 is ...

Present Optional

Not present Not allowed

D12 MT 670
In each occurrence of sequence B, in subsequence B1, field :95P::BENM or :95Q::BENM or
:95R::BENM must be present. All three may be present but once only.

D13 MTs 380 and 381

In sequence C, fields 16R and 16S may not be the only fields present. If both fields 16R and
16S are present, then at least one of the other fields of the sequence C must be present.

50 Error Codes
 Chapter 3 Alphanumeric Codes

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.
MT 670
In subsequence B2, fields 16R and 16S may not be the only fields present. If both fields 16R
and 16S are present, then at least one of the other fields of the same subsequence B2 must be
present.
In sequence C, fields 16R and 16S may not be the only fields present. If both fields 16R and
16S are present, then at least one of the other fields of the sequence C must be present.

D14 MT 670
In subsequence A2, if field :95P::SSIR is not present, then in subsequence B2 and sequence C,
field :22F:PMTH must not be present. In sequence C, field :22F::PMTH is only allowed when
subsequence B2, field :22F::PMTH is not present:
Subsequence A2 Subsequence B2 Sequence C
if field :95P::SSIR is ... then field :22F::PMTH is ... and field :22F::PMTH is ...

Present Present Not allowed

Present Not present Optional

Not present Not allowed Not allowed

D15 MT 670
In each occurrence of subsequence B1, fields :95P::ACCW, :95Q::ACCW and :95R::ACCW may
all be present but once only.
In each occurrence of subsequence B1, fields :95P::INT1, :95Q::INT1 and :95R::INT1 may all be
present but once only.
In each occurrence of subsequence B1, fields :95P::INT2, :95Q::INT2 and :95R::INT2 may all be
present but once only.

D16 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 Then subsequence B1 is ... And sequence C is ...

if subfield 1 of field 22K is
...

CLST Optional Optional

CONF Mandatory Mandatory

KNIN Not allowed Not allowed

KNOT Not allowed Not allowed

OTHR Optional Optional

TRIG Not allowed Not allowed

25 July 2014 51
FIN

D17 MTs 102 and 102 STP

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
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 Sequence B (each occurrence)

if field 52a is ... then field 52a is ...

Present Not allowed

Not present Optional

Sequence A Sequence B (each occurrence)

if field 26T is ... then field 26T is ...

Present Not allowed

Not present Optional

Sequence A Sequence B (each occurrence)

if field 77B is ... then field 77B is ...

Present Not allowed

Not present Optional

MT 102 STP
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 Sequence B (each occurrence)

if field 52A is ... then field 52A is ...

Present Not allowed

Not present Optional

Sequence A Sequence B (each occurrence)

if field 26T is ... then field 26T is ...

Present Not allowed

Not present Optional

Sequence A Sequence B (each occurrence)

if field 77B is ... then field 77B is ...

Present Not allowed

Not present Optional

52 Error Codes
 Chapter 3 Alphanumeric Codes

D19 MT 102 STP

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.
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, IL, IS, IT, LI, LT, LU, LV, MC, MQ,
MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA.

In transaction headers, In each occurrence of sequence B,

If country code And country And field 57A And country Then in this
of Emitter's BIC code of present in this code occurrence of
present in Receiver's BIC occurrence of field 57A sequence B
D19_CC present in of sequence B is present in in field 59a the
D19_CC D19_CC <IBAN>
format in
subfield_1
Account is ...

Yes Yes No Not applicable Mandatory

Yes No No Not applicable Optional

No Yes No Not applicable Optional

No No No Not applicable Optional

Yes Yes Yes Yes Mandatory

Yes No Yes Yes Optional

No Yes Yes Yes Optional

No No Yes Yes Optional

Yes Yes Yes No Optional

Yes No Yes No Optional

No Yes Yes No Optional

No No Yes No Optional

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.

25 July 2014 53
FIN

MT 103 STP
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, IL, IS, IT, LI, LT, LU, LV, MC, MQ,
MT, NL, NO, PL, PM, PT, RE, RO, SE, SI, SJ, SK, SM, TF and VA.

In transaction headers,

If country code and country and field 57A and country then in field 59a
of Emitter's BIC code of present code the <IBAN>
present in Receiver's BIC of field 57A format in
D19_CC present in is present in subfield_1
D19_CC D19_CC Account is ...

Yes Yes No Not applicable Mandatory

Yes No No Not applicable Optional

No Yes No Not applicable Optional

No No No Not applicable Optional

Yes Yes Yes Yes Mandatory

Yes No Yes Yes Optional

No Yes Yes Yes Optional

No No Yes Yes Optional

Yes Yes Yes No Optional

Yes No Yes No Optional

No Yes Yes No Optional

No No Yes No Optional

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 STP

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: This error code takes precedence over error codes D50, E13, and E15.

54 Error Codes
 Chapter 3 Alphanumeric Codes

D21 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 MTs 102 and 102 STP

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.

Sequence A Sequence B

If field 36 is present Then in minimum one occurrence of And field 36 is not

sequence B field 33B must be present, allowed in any
and currency codes in fields 32B and 33B occurrence of
must be different. sequence B

Sequence A Sequence B (each occurrence)

If field 33B is ... And currency codes Then field 36 is ...

in fields 32B and
33B are ...

If field 36 is not Present Equal Not allowed

present
Not equal Mandatory

Not present Not applicable Not allowed

D23 MT 304
The presence of sequence D depends on field 17O as follows:
Sequence A Then sequence D is ...
if field 17O is ...

Y Not allowed

N Mandatory

Not present 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. Therefore, the only allowed combination of codes in fields 17A and
17F, with the code VANI in field 12F, are as follows:

Sequence A

If field 12F is ... Then field 17A is ... And field 17F is ...

VANI N Y

VANI Y N

VANI Y Y

25 July 2014 55
FIN

D25 Available.

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

Sequence A

If field 12F is ... Then the allowed values for field 12E are ...

BINA AMER, EURO

DIGI EURO

NOTO EURO

VANI AMER, ASIA, BERM, EURO

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 ... And field 17A is ... Then the allowed values for
subfield 1 of field 22K are ...

VANI N CONF, CLST, OTHR

VANI Y CONF, CLST, KNIN, KNOT,

OTHR

Not = VANI N CONF, CLST, TRIG, OTHR

Not = VANI Y CONF, CLST, KNIN, KNOT,

TRIG, OTHR

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 Then field 30U is ... And field 29H is ...
...

CONF or CLST Not allowed Not allowed

Any other value Mandatory 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 ... And field 17N is ...

Y Y Mandatory

Y N Not allowed

56 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A
Then sequence E is ...
If field 17F is ... And field 17N is ...

Y Not present Not allowed (this case is already negatively

acknowledged, see error codes D03 and D04)

N Y or N Not allowed

N Not present Not allowed (this case is already negatively

acknowledged, see error codes D03 and D04)

Not present Y or N Not allowed

Not present Not present Not allowed

Note: See also error codes D03 and D04.

MT 507
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 Subsequence
A2
If And And field and field
field:25D::4!c/ field:25D::REST/ :25D::REST/[8c]/ Then
:13A::LINK//3!c sequence B is
[8c]/4!c [8c]/4!c 4!c is ... is ...
Qualifier is ... Data Source ...
Scheme [8c] is
...

REST Not present :25D::REST//ACCP 503 Optional

:25D::REST//ACCT 503 Optional

:25D::REST//ACCP 504 Mandatory

:25D::REST//ACCT 504 Mandatory

:25D::REST//ACCP 505 Optional

:25D::REST//ACCT 505 Optional

:25D::REST//SUBR Not applicable Optional

:25D::REST//REJT Not applicable Not allowed

Present Not applicable Not applicable Optional

CPRC Not applicable Not applicable Not applicable Not allowed

IPRC Not applicable Not applicable Not applicable Not allowed

Note: See error code D52.

MT 567
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).

25 July 2014 57
FIN

Sequence A And sequence B is Then sequence B, And sequence B,

if field :23G: is ... ... field :13A::CAON is field :22a::CAOP is
... ...

INST or CAST Present Mandatory Mandatory

Not present Not applicable Not applicable

EVST Not applicable Not applicable Not applicable

D30 MT 306
The presence of sequences D and G depends on the value of field 12F in sequence A as
follows:

Sequence A Then sequence D is ... And sequence G is ...

if field 12F is ...

VANI Mandatory Not allowed

Not = VANI Not allowed Mandatory

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 Sequence D

If field 12F is ... And field 12E is ... Then field 30P is ... And field 30Q is ...

VANI AMER Mandatory Not allowed

BERM Not allowed Mandatory (that is at

least one occurrence
must be present)

EURO Not allowed Not allowed

D32 MT 306
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 ... And subfield 1 of field 22K Then sequence E is ...
is ...

VANI Any value Not allowed

BINA or DIGI Any value Mandatory

NOTO Not = TRIG Mandatory

NOTO TRIG Not allowed

58 Error Codes
 Chapter 3 Alphanumeric Codes

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:

Sequence A Sequence D

If field 12F is ... And field 17F is ... Then the allowed values for field 26F are ...

VANI Y NETCASH

N NETCASH, PRINCIPAL

D34 MT 306
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 Sequence E
then field 30H is ...
And subfield 1 of And field 12E is ...
field 22K is ...

Present TRIG AMER Mandatory

Not = TRIG AMER or EURO Not allowed

Not present Not applicable Not applicable Not applicable

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 ... Then field 77D is ...

OTHER Mandatory

Not = OTHER Optional

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 Then sequence E is ... Sequence E

if field 14F is ... and field 72 is ...

OTHER Mandatory Mandatory

Not = OTHER Optional Optional

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

:14F:OTHER<CrLf>.

MT 600
The presence of field 77D depends on the value of Type of Agreement (subfield 1 of field 77H)
as follows:

25 July 2014 59
FIN

Sequence A

If subfield 1 of field 77H is ... Then field 77D is ...

OTHER Mandatory

Not = OTHER Optional

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 ... Then field 77D is ...

OTHER Mandatory

Not=OTHER Optional

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 Then sequence E is ... Sequence E

if field 14D is ... and field 72 is ...

OTHER Mandatory Mandatory

Not = OTHER Optional 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: OTHER<CrLf> (leading blanks)

:14D:OTHER <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.

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.

60 Error Codes
 Chapter 3 Alphanumeric Codes

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 Then sequence E is ... Sequence E
if second component of and field 72 is ...
subfield 1 of field 38G is ...

O Mandatory Mandatory

Not = O Optional Optional

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.

D43 MT 306
The presence of sequence F depends on the value of field 17A in sequence A as follows:

Sequence A Then sequence F is ...

if field 17A is ...

Y Mandatory

N Not allowed

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 ... Then field 37L is ...

SKIN or SKOT Not allowed

DKIN or DKOT Mandatory

Note: See also error code D43.

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:
Sequence B Subsequence B1 (if present)
If field 37U is ...
Then field 32M is ... And field 17F is ... And field 14D is ...

Present Not allowed Mandatory Mandatory

Not present Mandatory Not allowed Not allowed

Note: The presence of subsequence B1 is determined by error code E41.

25 July 2014 61
FIN

D46 MT 306
In sequence G, the presence of field 37P depends on the value of field 22J as follows:

Sequence G

If field 22J is ... Then field 37P is ...

SITR Not allowed

DBTR Mandatory

Note: See also error code D30.

D47 MT 306
The presence of sequence H depends on the value of field 17F in sequence A as follows:

Sequence A Then sequence H is ...

if field 17F is ...

Y Mandatory

N Not allowed

D48 MTs 360 and 361

In sequences L and M, for all occurrences of fields 53a, 56a and 57a the following rules apply:
Sequence L or M Then in the same sequence
if field 57a is ... fields 53a and 56a are ...

Present Optional

Not present Not allowed

D49 MTs 102 and 102 STP

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

If Emitter's BIC country And Receiver's BIC country In each occurrence of

code code sequence B,
present in D49_CC present in D49_CC then field 33B is ...

Yes Yes Mandatory

Yes No Optional

No Yes Optional

No No Optional

Note: See error code D51.

MTs 103, 103 REMIT, and 103 STP
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.

62 Error Codes
 Chapter 3 Alphanumeric Codes

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 And Receiver's BIC country Then field 33B is ...
code code present in D49_CC
present in D49_CC

Yes Yes Mandatory

Yes No Optional

No Yes Optional

No No Optional

Note: See error code D51.

MT 504
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 ... Then in sequence(s) C

Present In one or more occurrence(s) of sequence C:

subsequence C1 must be present and an
internal subsequence C1a must not be
present

Note: See error code C97.

MT 505
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 ... Then in sequence(s) B

Present 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.

D50 MTs 102 and 102 STP

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.

Sequence A Sequence B (each occurrence)

if field 71A is ...
Then fields 71F are ... And field 71G is ...

SHA Optional 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.

Sequence B In the same occurrence of sequence B

if field 71A is ..
Then fields 71F are ... And field 71G is ...

SHA Optional Not allowed

25 July 2014 63
FIN

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

If field 71A is ... Then field 71F is ... And field 71G is ...

SHA Optional Not allowed

Note: See error codes E13 and E15.

MT 504
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 ... Then in sequence(s) C

Present In one or more occurrence(s) of sequence C:

subsequence C2 must be present and an internal
subsequence C2a must not be present

Note: See error code C99.

MT 505
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 ... Then in sequence(s) B

Present In one or more occurrence(s) of sequence B:

subsequence B2 must be present and an internal
subsequence B2a must not be present

Note: See error code C99.

D51 MTs 102 and 102 STP

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.

Sequence B (each occurrence)

If field 71F is ... Then field 71G is ... And field 33B is ...

Present Present Rejected [1]

Present Not present Mandatory

Not present Present Mandatory

Not present Not present Optional

[1] The presence of both fields 71F and 71G is not allowed: see error codes D50, E13 and E15.
MTs 103, 103 REMIT, and 103 STP
If either field 71F (at least one occurrence) or field 71G is present, then field 33B is mandatory;
otherwise field 33B is optional.

64 Error Codes
 Chapter 3 Alphanumeric Codes

If field 71F is ... Then field 71G is ... And field 33B is ...

Present Present Rejected [1]

Present Not present Mandatory

Not present Present Mandatory

Not present Not present Optional

[1] 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: See also error code D53.

D53 MT 507
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 ... Then field 21F is ...

Present Mandatory

Not present Optional

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:

Sequence A Sequence B
if field 22B is ...
Then field 32H is ... And field 30X is ...

CONF Not allowed Mandatory

MATU Mandatory Not allowed

ROLL Mandatory Mandatory

MT 330
The presence of fields 32B, 32H and 30X in sequence B depends on the value of field 22B in
sequence A as follows:

25 July 2014 65
FIN

Sequence A Sequence B
if field 22B is ...
Then field 32B is ... And field 32H is ... And field 30X is ...

CHNG Mandatory Mandatory Optional

CINT Mandatory Mandatory Optional

CONF Mandatory Not allowed Not allowed

SETT Not allowed Mandatory Mandatory

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 Sequence B
if field 22B is ...
Then field 32a (index 19, And field 30X is ...
field 32H, R) is ...

CONF Not allowed Mandatory

MATU Mandatory Not allowed

ROLL Mandatory Mandatory

D57 MTs 102, 102 STP, 104, and 107

In sequence C, in field 71G, Amount must not equal '0' .
MTs 103, 103 REMIT, and 103 STP
In field 71G, Amount must not equal '0' .
MT 320
The values allowed for field 32H in sequence B depend on the values of field 22B in sequence A
and field 17R in sequence B as follows:

Sequence A Sequence B
if field 22B is ...
And field 17R is ... Then field 32H must be ...

MATU L Negative or zero

MATU B Positive or zero

Not = MATU Not applicable Not applicable

Note: See error code D56.

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 Sequence B
if field 22B is ...
And field 17R is ... Then field 32H must be ...

SETT L Negative or zero

SETT B Positive or zero

Not = SETT Not applicable Not applicable

66 Error Codes
 Chapter 3 Alphanumeric Codes

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: See error code D56.
MT 370
In sequence B Netting Position Details, field :19A::NETT, if the value of Amount is zero, then
field :22H::RECP must contain the code NOPA.
In sequence B Netting Position Details, field :19A::NETT, if the value of Amount is not zero, then
field :22H::RECP must not contain the code NOPA.

In sequence B Then in sequence B field 19A,

if second subfield of field 22H is ... subfield 4 Amount must be ...

NOPA Zero [1]

Not = NOPA Not zero [1]

[1] If subfield 4 (Amount) of field 19A = 0 (that is, zero value), then the letter N (Sign) in subfield 2
of field 19A is not allowed.
MT 620
In sequence B, the values allowed for field 32a index 19 (with option H or R) depend on the
values of fields 22B in sequence A and 17R in sequence B as follows:

Sequence A Sequence B
if field 22B is ...
And field 17R is ... Then field 32a (with option
H or R) must be ...

MATU L Negative or zero

MATU B Positive or zero

Not = MATU Not applicable Not applicable

Note: See error code D56.

D58 MT 360
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 Then sequence And sequence And sequence And sequence
if subfield 1 of B is ... C is ... E is ... F is ...
field 23A is ...

FIXEDFIXED Mandatory Not allowed Mandatory Not allowed

FLOATFLOAT Not allowed Mandatory Not allowed Mandatory

FLOATFIXED Mandatory Not allowed Not allowed Mandatory

FIXEDFLOAT Not allowed Mandatory Mandatory Not allowed

CAPBUYER Not allowed Mandatory Not allowed Not allowed

CAPSELLER Not allowed Not allowed Not allowed Mandatory

FLOORBUYER Not allowed Mandatory Not allowed Not allowed

FLOORSLLER Not allowed Not allowed Not allowed Mandatory

25 July 2014 67
FIN

Sequence A Then sequence And sequence And sequence And sequence

if subfield 1 of B is ... C is ... E is ... F is ...
field 23A is ...

COLLARBYER Not allowed Mandatory Not allowed Mandatory

COLLARSLLR Not allowed Mandatory Not allowed Mandatory

Note: See error codes E41 and E42.

D59 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:
Sequence E Subsequence E1 (if present)
if field 37U is ...
Then field 32M is ... And field 17F is ... And field 14D is ...

Present Not allowed Mandatory Mandatory

Not present Mandatory Not allowed Not allowed

D60 MT 101
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.
Sequence B (each occurrence)

If field 33B is ... Then amount in field 32B is And field 36 is ...
...

Present Equal to zero Not allowed

Not equal to zero Mandatory

Not present Not applicable Not allowed

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 ... Then field 38J is ...

Present Mandatory

Not present Not allowed

MT 341
In subsequence B1, if field 30V is present, then field 38D is mandatory; otherwise field 38D is
not allowed.

Subsequence B1

If field 30V is ... Then field 38D is ...

Present Mandatory

Not present 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 Sequence B (each occurrence)

if field 50a index 5 (option F, G or H) is ... then field 50a index 15 (option F, G or H) is
...

Present Not allowed

Not present 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 Sequence B
if field 50a (option C or L) is ... then field 50a (option C or L) is ...

Present Not allowed

Not present Optional in any occurrence

D63 MTs 101, 102, 103, 103 REMIT, 104, 107, 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 Sequence B
if field 52a is ... then field 52a is ...

Present Not allowed

Not present Optional

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 ... Then field 57a is ...

Present Mandatory

Not present Optional

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

25 July 2014 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 with CMSW

CHQB with CMTO

CHQB with CMZB

CHQB with CORT

CHQB with URGP

CHQB with REPA

CHQB with RTGS

CHQB with NETS

CHQB with PHON

CMSW with CMTO

CMSW with CMZB

CMTO with CMZB

CORT with CMSW

CORT with CMTO

CORT with CMZB

CORT with REPA

EQUI with CMSW

EQUI with CMTO

EQUI with CMZB

NETS with RTGS

Example:

Valid Invalid

:23E:URGP :23E:CHQB

:23E:CORT :23E:URGP

:23E:NETS

:23E:RTGS

MTs 103 and 103 REMIT

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

70 Error Codes
 Chapter 3 Alphanumeric Codes

SDVA with HOLD

SDVA with CHQB

INTC with HOLD

INTC with CHQB

REPA with HOLD

REPA with CHQB

REPA with CORT

CORT with HOLD

CORT with CHQB

HOLD with CHQB

PHOB with TELB

PHON with TELE

PHOI with TELI

MT 103 STP
When field 23E is used more than once, the following combination is not allowed:

REPA with CORT

MT 207

CMSW with CMTO

CMSW with CMZB

CMTO with CMZB

CORT with CMSW

CORT with CMTO

CORT with CMZB

NETS with RTGS

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 Invalid

:32B:USD1000, :32B:USD1000,00

:33B:CHF1000, :33B:USD1000,

. .
. .
. .

:32B:CHF1200, :32B:CHF1200,

25 July 2014 71
FIN

Valid Invalid

:33B:USD1000, :33B:CHF1000,00

D69 MTs 320 and 620

If field 22B in sequence A contains MATU, then field 30F in sequence B is not allowed;
otherwise field 30F is optional.

Sequence A Sequence B
if field 22B is ... then field 30F is ...

MATU Not allowed

Not = MATU Optional

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 Sequence B
if field 22B is ... then field 30F is ...

SETT Not allowed

Not = SETT Optional

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. If no occurrence of field 22B contains OTHR, field 72 in
sequence E is optional.

Subsequence B2 Then sequence E is ... Sequence E

if field 22B:OTHR is ... and field 72 is ...

Present at least once Mandatory Mandatory

Not present Optional Optional

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 ... Then field 21 is ...

AMND Mandatory

CANC Mandatory

DUPL Optional

EXOP Optional

NEWT Optional

MTs 320, 330, and 620

In sequence A, the presence of field 21 depends on the values of fields 22B and 22A as follows:

72 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A

If field 22B is ... And field 22A is ... Then field 21 is ...

CONF NEWT Optional

CONF Not = NEWT Mandatory

Not = CONF Any value Mandatory

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 Then sequence D And in one

field:22F::DBNM//VEND is ... occurrence of
is ... [1] sequence D
field :95a::VEND is
...

Present Present Mandatory Mandatory [2]

that is, sequence D
must be present
minimum once

Not present Optional Optional

Not present Not applicable Optional Optional

[1] If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule
does not apply.
[2] :95a::VEND mandatory in only one occurrence of sequence D, see error code E84.
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 Then sequence E is And in one

field:22F::DBNM//VEND ... occurrence of
is ... [1] sequence E
field :95a::VEND is
...

Present Present Mandatory Mandatory [2]

that is, sequence E
must be present
minimum once

Not present Optional Optional

Not present Not applicable Optional Optional

[1] If the Data Source Scheme is present in field :22F::DBNM//VEND, then the conditional rule
does not apply.
[2] :95a::VEND mandatory in only one occurrence of sequence E, see error code E84.
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:

25 July 2014 73
FIN

Sequence E Then sequence F is ... And in one occurrence of

if field:22F::DBNM//VEND is sequence F
... [1] field :95a::VENDis ...

Present Mandatory Mandatory [2]

that is, sequence F must be
present minimum once

Not present Optional Optional

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

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 ... Then field 21N is ...

AGNT Mandatory

BILA Optional

BROK Optional

Not present Optional

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 ... Then field 21N is ...

AGNT Mandatory

BILA Optional

Not present Optional

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 Sequence B
if field 26T is ... then field 26T is ...

Present Not allowed

Not present Optional

74 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A Sequence B
if field 77B is ... then field 77B is ...

Present Not allowed

Not present Optional

Sequence A Sequence B
if field 71A is ... then field 71A is ...

Present Not allowed

Not present Optional

Sequence A Sequence B
if field 52a is ... then field 52a is ...

Present Not allowed

Not present Optional

Sequence A Sequence B
if field 21E is ... then field 21E is ...

Present Not allowed

Not present Optional

Sequence A Sequence B
if field 50a (option C or L) is ... then field 50a (option C or L) is ...

Present Not allowed

Not present Optional

D74 MT 300
The presence of sequence C and fields 88a and 71F depends on field 94A as follows:
Sequence A Then sequence C is Sequence C
if field 94A is ... ...
And field 88a is ... And field 71F is ...

Not present Optional Optional Not allowed

AGNT Optional Optional Not allowed

BILA Optional Optional Not allowed

BROK Mandatory Mandatory Optional

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 Then sequence I is Sequence I

if field 94A is ... ...
And field 88a is ... And field 71F is ...

Not present Optional Optional Not allowed

BROK Mandatory Mandatory Optional

25 July 2014 75
FIN

Sequence A Then sequence I is Sequence I

if field 94A is ... ...
And field 88a is ... And field 71F is ...

Not = BROK Optional Optional Not allowed

MTs 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 Then sequence H is Sequence H

if field 94A is ... ...
And field 88a is ... And field 71F is ...

Not present Optional Optional Not allowed

AGNT Optional Optional Not allowed

BILA Optional Optional Not allowed

BROK Mandatory Mandatory Optional

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 Then sequence E is Sequence E

if field 94A is ... ...
And field 88a is ... And field 71F is ...

Not present Optional Optional Not allowed

BROK Mandatory Mandatory Optional

Not = BROK Optional Optional Not allowed

MTs 360 and 361

The presence of fields 88a and 71F in sequence N and, therefore, the presence of sequence N
itself, depends on field 94A in sequence A as follows:
Sequence A Sequence N
if field 94A is ... Then sequence N is
... And field 88a is ... And field 71F is ...

Not present Optional Optional Not allowed

AGNT Optional Optional Not allowed

BILA Optional Optional Not allowed

BROK Mandatory Mandatory Optional

D75 MTs 103, 103 REMIT, and 103 STP

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 ... And currency code Then field 36 is ...

in field 33B is ...

Present Not = currency code in field Mandatory

32A

76 Error Codes
 Chapter 3 Alphanumeric Codes

If field 33B is ... And currency code Then field 36 is ...

in field 33B is ...

= currency code in field 32A Not allowed

Not present Not applicable Not allowed

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 ... Then field 36 is ...

Not present Not allowed

Present, and <field 32B currency code> NOT Mandatory

= <field 33B currency code>

Present, and <field 32B currency code> = Not allowed

<field 33B currency code>

D76 MT 300
The presence of sequence D depends on field 17U in sequence A as follows:
Sequence A Then sequence D is ...
if field 17U is ...

Not present Not allowed

Y Mandatory

N Not allowed

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 ... Then field 50a (option A or K) is ...

Present Mandatory

Not present Optional (see error code D76)

Sequence B

If field 21E is ... Then field 50a (option A or K) is ...

Present Mandatory

Not present Optional (see error codes C76, C96)

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.

25 July 2014 77
FIN

Sequence A

If field 21E is ... Then field 50a (option A or K) is ...

Present Mandatory

Not present Optional (see error code D86)

Sequence B

If field 21E is ... Then field 50a (option A or K) is ...

Present Mandatory

Not present Optional (see error code D86)

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 Sequence B
if field 23E is ... then field 23E is ...

Present Not allowed

Not present Mandatory in each occurrence of sequence B

D79 MTs 102 and 102 STP

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

If in any occurrence of sequence B Sequence C

field 71G is ... then field 71G is ...

Present Mandatory

MTs 104 and 107

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 Sequence C
if field 71F is ... then field 71F is ...

Present Mandatory

Not present Not allowed

Sequence B Sequence C
if field 71G is ... then field 71G is ...

Present Mandatory

Not present Not allowed

78 Error Codes
 Chapter 3 Alphanumeric Codes

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.
Note: See also error code C96.
MT 107
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.
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.
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 Sequence B (each occurrence)

if field 71F is ... then field 71F is ...

Present Not allowed

Not present Optional

Sequence A Sequence B (each occurrence)

if field 77A is ... then field 77A is ...

Present Not allowed

Not present Optional

D84 MT 740
Either field 58a or 59, but not both, may be present.

25 July 2014 79
FIN

If field 58a is ... Then field 59 is ...

Present Not allowed

Not present Optional

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 ... Then field 34E is ...

Present Mandatory

Not present Not allowed

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 Sequence B (each occurrence)

if field 23E is ... then field 23E is ...

Present Not allowed

Not present Mandatory

Sequence A Sequence B (each occurrence)

if field 50a (option A or K) is ... then field 50a (option A or K) is ...

Present Not allowed

Not present Mandatory

D87 Available.

D88 MT 298/092
At least one occurrence of either sequence B, C, D, or E must be present.

D89 MT 298/092
In each occurrence of sequence E, if field 13H contains the value P (partial configuration
checkpoint), then field 17J must be present.

D90 MT 298/093
In each occurrence of sequence B, if field 21H is present, then fields 51, 54, and 12G are
mandatory

D91 Available.

80 Error Codes
 Chapter 3 Alphanumeric Codes

D92 MT 321
In subsequence B3, all qualifiers of field 95a are optional, but at least one qualifier (any one)
must be present.
MT 530
In each occurrence of sequence B, all qualifiers of field 20C are optional, but at least one
qualifier (any one) must be present.
MT 568
All qualifiers of field 70a are optional, but at least one qualifier (any one) must be present.
MTs 527 and 558
In sequence A, all qualifiers of field 98a are optional, but at least one qualifier (any one) must be
present.

D93 MT 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 qualifiers of field 22F are optional, but at least one
qualifier (any one) must be present.

D94 Available.

D95 Available.

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 MTs 103 and 103 REMIT

Subfield 2 of field 23E is allowed only when subfield 1 consists of
PHON, PHOB, PHOI, TELE, TELB, TELI , HOLD or REPA.
MT 103 STP
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.
MTs 103 and 103 REMIT
If field 23E is repeated, the codes must appear in the following order:

SDVA
INTC

REPA

25 July 2014 81
FIN

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 STP
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.

Sequence D Sequence A Sequence D,

if field :70E::NAME is ... then field and field
:22F::CAEV//CHAN is ... :22F::CHAN//NAME is ...

Present Mandatory, and DSS must Mandatory, and DSS must

not be present not be present

Not present Not applicable Not applicable

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.

Sequence C Sequence A Sequence C

if field :70E::NAME is ... then field and field
:22F::CAEV//CHAN is ... :22F::CHAN//NAME is ...

Present Mandatory, and DSS must Mandatory, and DSS must

not be present not be present

Not present Not applicable Not applicable

82 Error Codes
 Chapter 3 Alphanumeric Codes

3.4.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 Not used.

E01 MTs 103 and 103 REMIT

If field 23B contains SPRI, field 23E can contain only SDVA, TELB, PHOB, or INTC.

If field 23B is ... Then field 23E is ...

SPRI Optional. It can contain only SDVA, TELB,

PHOB or INTC

Not = SPRI Optional

MT 103 STP
If field 23B contains SPRI, field 23E can contain only SDVA and INTC.

If field 23B is ... Then field 23E is ...

SPRI Optional. It can contain only SDVA or INTC

Not = SPRI Optional

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//INFO is present, then sequence C is not allowed and
sequence E is not allowed.

Sequence A Then sequence C is ... And sequence E is ...

[1]
if field :22F::CAEV is ...

:22F::CAEV//RHDI Not allowed Not applicable

:22F::CAEV//RHTS Mandatory Not applicable

:22F::CAEV//INFO Not allowed Not allowed

Other Optional Optional

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

E02 MTs 103, 103 REMIT, and 103 STP

If field 23B contains SSTD or SPAY, field 23E must not be used.

If field 23B is ... Then field 23E is ...

SSTD Not allowed

25 July 2014 83
FIN

If field 23B is ... Then field 23E is ...

SPAY Not allowed

Not = SSTD and not = SPAY Optional

MT 564
In sequence A, if field :23G:REPE is present, then when sequence C is present, field :36a::QINT
is mandatory.

Sequence A And sequence C is ... Then in sequence C

if field :23G:REPE is ... field :36a::QINT is ...

Present Present Mandatory

Not present Not applicable

Not present Optional Optional

E03 MTs 103 and 103 REMIT

If field 23B contains SPRI, SSTD or SPAY, field 53a must not be used with option D.

If field 23B is ... Then field 53a ...

SPRI, SSTD or SPAY Must not be used with option D (that is, only
options A and B may be used)

Other code Optional

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 Then sequence F is ... Sequence F

if field :22F::CAEV//OTHR is ... [1] and field :70E::ADTX is ...

Present Mandatory Mandatory

Not present Not applicable Not applicable

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

E04 MTs 103 and 103 REMIT

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 STP
If field 53a is present with option B, subfield 1, Party Identifier (['/'<DC>]['/'34x] 'CrLf') must be
present in field 53B.

E05 MTs 103 and 103 REMIT

If field 23B contains SPRI, SSTD or SPA, field 54a can be used with option A only.

If field 23B is ... Then field 54a is ...

SPRI, SSTD or SPAY Optional with option A only (options B and D

are not allowed)

84 Error Codes
 Chapter 3 Alphanumeric Codes

If field 23B is ... Then field 54a is ...

Other code Optional

E06 MTs 103 and 103 REMIT

If field 55a is present, then both fields 53a and 54a must also be present.

If field 55a is ... Then field 53a is ... And field 54a is ...

Present Mandatory Mandatory

Not present Optional Optional

MT 103 STP
If field 55A is present, then both fields 53A and 54A must also be present.

If field 55A is ... Then field 53a is ... And field 54A is ...

Present Option A Mandatory Mandatory

Not present Optional Optional

MT 564
In sequence A, if field :22F::CAEV//RHDI is present, then sequence D must be present, and field
:22F::RHDI must be present in sequence D.

Sequence A Then sequence D is ... Sequence D

if field :22F::CAEV//RHDI [1] and field :22F::RHDI is ...
is ...

Present Mandatory Mandatory

Not present Not applicable Not applicable

[1] If the Data Source Scheme is present in field :22F::CAEV then the conditional rule does not
apply.
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.

Sequence A Then sequence C is ... Sequence C

if field :22F::CAEV//RHDI [1] and field :22F::RHDI is ...
is ...

Present Mandatory Mandatory

Not present Optional Optional

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

E07 MTs 103 and 103 REMIT

If field 23B contains SPRI, SSTD or SPAY, field 55a can be used with option A only.

If field 23B is ... Then field 55a is ...

SPRI, SSTD or SPAY Optional with option A only (options B and D

are not allowed)

25 July 2014 85
FIN

If field 23B is ... Then field 55a is ...

Other code Optional

E08 MT 370
If the message is a cancellation, that is, Function of the Message (field 23G) is CANC, or the
message is an amendment (that is, if the Function of the Message -field 23G- is AMND), 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 Then subsequence A1 is ... And in minimum one

if field :23G: is ... occurrence of subsequence
A1
field :20C::PREV is ...

AMND or CANC Mandatory, that is, minimum Mandatory [1]

one occurrence of A1

NEWM Optional Not applicable

[1] It does not need to be present in all occurrences of A1
MT 381
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, 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 Then subsequence A1 is ... And in minimum one

if field :23G: is ... occurrence of subsequence
A1
field :20C::PREV is ...

CANC Mandatory, that is, minimum Mandatory [1]

one occurrence of A1

Not = CANC Optional Optional

[1] It does not need to be present in all occurrences of A1.
MTs 500, 508, 513, 514, 518, 519, 535, 536, 537, 538, 549, 565, 575, 576, and 586
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 Then subsequence A1 is ... And in at least one

if field :23G: is ... occurrence of subsequence
A1
field :20C::PREV is ...

CANC Mandatory (minimum one Mandatory in one occurrence

occurrence of A1 must be of subsequence A1, and not
present) allowed in all other
occurrences of subsequence
A1

NEWN Optional Not applicable

86 Error Codes
 Chapter 3 Alphanumeric Codes

MTs 502
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 Then subsequence A1 is ... And field :20C::PREV is ...

if field :23G: is ...

CANC or REPL Mandatory (minimum one Mandatory in one occurrence

occurrence of A1 must be of subsequence A1, and not
present) allowed in all other
occurrences of subsequence
A1

NEWN Optional Not applicable

MTs 503, 504, 505, 506, and 569

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 Then subsequence A2 is ... And field :20C::PREV is ...

if subfield 1 of field :23G: is
...

CANC Mandatory (minimum one Mandatory in one occurrence

occurrence of A2 must be of subsequence A2, and not
present) allowed in all other
occurrences of subsequence
A2.

NEWM Optional Not applicable

MT 524
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 Then subsequence A1 is ... And field :20C::PREV is ...

if field :23G: is ...

CANC Mandatory Mandatory

NEWN Optional Not applicable

MTs 501 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.

Sequence A Then field :20C::PREV is ...

if field :23G: is ...

CANC Mandatory in one occurrence of subsequence

A1, and not allowed in all other occurrences
of subsequence A1.

NEWN Not applicable

25 July 2014 87
FIN

MT 515
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:
Sequence A Then field :20C::PREV is ...
if field :23G: is ...

CANC Mandatory in one occurrence of subsequence

A1, and not allowed in all other occurrences
of subsequence A1

NEWM or PREA Not applicable

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 Then sequence B is ...

if subfield 1 of field :23G: is ...

REPL Not allowed

NEWM Mandatory

CANC Mandatory

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 And field :20C::PREV is ...

Then subsequence A1 is ...
if field :23G: is ...

CANC Mandatory Mandatory in one occurrence

(minimum one occurrence of of subsequence A1, and not
A1 must be present) allowed in all other
occurrences of subsequence
A1.

NEWN or PREA Optional Not applicable

MTs 544, 545, 546, and 547

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 Then field :20C::PREV is ...

if field :23G: is ...

CANC or RVSL Mandatory in one occurrence of subsequence

A1, and not allowed in all other occurrences
of subsequence A1

NEWM Not applicable

88 Error Codes
 Chapter 3 Alphanumeric Codes

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

Sequence A

If value of field :23G:4!c[/4!c] subfield 1 is Then subsequence A2 is ...

...

ADVD Not allowed

Not ADVD Mandatory

MTs 564 and 568

If the message is a replacement, an eligible balance notification, or a reminder, that is, Function
of the Message (field 23G) is REPL, REPE, 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.
If the message is a cancellation or a withdrawal that is, Function of the Message (field 23G) is
CANC or WITH, then subsequence A1 (Linkages) is optional in the message, and field
:20C::PREV may only appear once in only one occurrences of A1; consequently, in all other
occurrences of A1, field :20C::PREV is not allowed.

Sequence A Then subsequence A1 is ... And field :20C::PREV is ...

if field :23G: is ...

REPL, REPE, or RMDR Mandatory (minimum one Mandatory in one occurrence

occurrence of A1 must be of subsequence A1, and not
present) allowed in all other
occurrences of subsequence
A1

CANC or WITH Optional Optional in one single

occurrence of subsequence
A1, and not allowed in all
other ocurrences of
subsequence A1

NEWM Optional Not applicable

MT 566
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 Then subsequence A1 is ... And field :20C::PREV is ...

if field :23G: is ...

REVR Mandatory (minimum one Mandatory in one occurrence

occurrence of A1 must be of subsequence A1, and not
present) allowed in all other
occurrences of subsequence
A1

NEWN Optional Not applicable

25 July 2014 89
FIN

MT 578
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 Then subsequence A1 is ... And field :20C::PREV is ...

if field :23G: is ...

CANC or REMO Mandatory (minimum one Mandatory in one occurrence

occurrence of A1 must be of subsequence A1, and not
present) allowed in all other
occurrences of subsequence
A1

NEWN Optional Not applicable

E09 MTs 103 and 103 REMIT

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 ... Then field 57a is ...

SPRI, SSTD or SPAY Allowed only with options A, C or D (in option

D, Party Identifier ['/'<DC>]['/'34x] 'CrLf' is
mandatory)

Other code Optional

MT 564
If the message is a replacement (:23G::REPL), then in sequence A, field :25D::PROC, the code
ENTL is not allowed and in sequence D field :22F::ADDB, the code CAPA is not allowed.
If the message is an eligible balance notification (:23G::REPE), then in sequence A, field
:25D::PROC, the code ENTL is not allowed and in sequence D field :22F::ADDB, the code
CAPA is optional.

Sequence A Then in field :25D::PROC And in sequence D,

if field :23G: is ... the code ENTL is ... in field :22F::ADDB,
the code CAPA is ...

REPL Not allowed without DSS Not allowed without DSS

REPE Not allowed without DSS Optional

E10 MTs 103 and 103 REMIT

If field 23B contains SPRI, SSTD or SPAY, subfield 1, Account, in field 59a is mandatory.
MTs 102 STP, 103 STP, 104, and 107
Subfield 1, Account, of field 59a is mandatory.
Note: Error code E10 takes precedence over error code D19 (MTs: 102 STP, 103
STP).

90 Error Codes
 Chapter 3 Alphanumeric Codes

E11 MT 564
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 Then sequence D is Sequence D

if field :23G: is ... ...
And field And field
:22F::ADDB is ... :22F::ADDB// must
be ...

ADDB Mandatory Mandatory, only one CLAI, or

occurrence
TAXR, or

REVR

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

E12 MTs 103 and 103 REMIT

Either field 70 or 77T, but not both, may be present.

If field 70 is ... Then field 77T is ...

Present Not present

Not present Optional

E13 MTs 102 and 102 STP

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.

Sequence A Sequence B (each occurrence)

if field 71A is ...
Then field(s) 71F is(are) ... And field 71G is ...

OUR Not allowed 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.

Sequence B In the same occurrence of sequence B

if field 71A is ...
Then field(s) 71F is(are) ... And field 71G is ...

OUR Not allowed Optional

Note: See error codes D20, D50 and E15.

MTs 103, 103 REMIT, and 103 STP
If field 71A contains OUR, then field 71F is not allowed and field 71G is optional.

If field 71A is ... Then field 71F is ... And field 71G is ...

OUR Not allowed Optional

Note: See error codes D50 and E15.

25 July 2014 91
FIN

E14 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:

Sequence E Sequence A
if field :22F::FXCX [1] then field :23G:4!c is ...

FXNO CANC

FXYE CANC

SINO NEWM

Not present Not applicable

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

E15 MTs 102 and 102 STP

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.

Sequence A Sequence B (each occurrence)

if field 71A is ...
Then field(s) 71F is(are) ... And field 71G is ...

BEN Mandatory 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.

Sequence B In the same occurrence of sequence B

if field 71A is ...
Then field(s) 71F is(are) ... And field 71G is ...

BEN Mandatory Not allowed

Note: See error codes D20, D50 and E13. Error code D20 takes precedence over
error codes D50, E13, and E15.
MTs 103, 103 REMIT, and 103 STP
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 ... Then field 71F is ... And field 71G is ...

BEN Mandatory (at least one Not allowed

occurrence)

Note: See error codes D50 and E13.

E16 MTs 103, 103 REMIT, and 103 STP

If field 23B contains SPRI, field 56a must not be used.

If field 23B is ... Then field 56a is ...

SPRI Not allowed

92 Error Codes
 Chapter 3 Alphanumeric Codes

E17 MTs 103 and 103 REMIT

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.

If field 23B is ... Then field 56a is ...

SSTD or SPAY Allowed with option A or C (if option C: the

first 2 characters of first line must be //)

Not = SPRI, SSTD and SPAY Optional

E18 MTs 103 and 103 REMIT

If any field 23E contains CHQB, subfield 1, Account, in field 59a is not allowed.

E19 Available.

E20 Available.

E21 MT 564
If field :92B::IDFX is present in any occurrence of sequence E, then sequence D must be
present and field :92a::DEVI must be present in sequence D.

Sequence E (any Then sequence D is ... Sequence D

occurrence) and field :92a::DEVI is ...
if field :92B::IDFX is ...

Present Mandatory Mandatory

Not present Not applicable Not applicable

E22 MT 564
If the message is new (:23G::NEWM) and if in sequence A field :25D::PROC the code ENTL is
present, then sequence D Corporate Action Details is mandatory, and in sequence D, field
:22F::ADDB is mandatory, and one occurrence of :22F::ADDB// ... must contain code CAPA.
Sequence And in field Then And in And in sequence D
A :25D::PROC sequence sequence field :22F::ADDB// ...
if field the code D is ... D
:23G: is ENTL is ... field
... :22F::ADDB
is ...

NEWM Present Mandatory Mandatory One occurrence must be CAPA and

without DSS DSS must not be present in that
occurrence

25 July 2014 93
FIN

If the message is new (:23G::NEWM) and if in sequence A field :25D::PROC the code ENTL is
not present, then in sequence D, in field :22F::ADDB// ... code CAPA is not allowed.
Sequence And in field And if And if in Then in sequence
A :25D::PROC sequence D is sequence D D
if field the code ENTL is ... ... field field :22F::ADDB//
:23G: is ... :22F::ADDB is ...
...

NEWM Not present or Present Present CAPA not allowed

present with DSS without DSS

Not present Not applicable

Not present Not applicable Not applicable

E23 MT 670
In sequence A, field :95P::TRAD may only be present once. Field :95Q::TRAD may only be
present once. Both fields :95P::TRAD and :95Q::TRAD may be present.

E24 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 sequence D is ... And (in the And (in the Then in sequence D,
message) message) field :98a::PAYD is
subsequence E1 is subsequence E2 is ...
... ...

Present Present Present Not allowed

Present Not present Not allowed

Not present Present Not allowed

Not present Not present Optional

Not present Not applicable Not applicable Not applicable

E25 MT 256
If field 37J is present, then field 71G must also be present.

Sequence B

If field 37J is ... Then field 71G is ...

Present Mandatory

Not present Optional

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.

94 Error Codes
 Chapter 3 Alphanumeric Codes

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 Sequence B
if field 21 is ... then field 21 is ...

Present Not allowed

Not present Mandatory in each occurrence of sequence B

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 Sequence C
if field 71F is ... then field 71L is ...

Present in any occurrence Mandatory

Not present in any occurrence Not allowed

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 Sequence C
if field 71G is ... then field 71J is ...

Present in any occurrence Mandatory

Not present in any occurrence Not allowed

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 Sequence C
if field 71H is ... then field 71K is ...

Present in any occurrence Mandatory

Not present in any occurrence Not allowed

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.

25 July 2014 95
FIN

E33 MT 364
The presence of sequences B and E depends on subfield 1 of field 23A in sequence A as
follows:
Sequence A Then sequence B is ... And sequence E is ...
if subfield 1, of field 23A is
...

FIXEDFIXED Mandatory Mandatory

FLOATFLOAT Not allowed Not allowed

FLOATFIXED Mandatory Not allowed

FIXEDFLOAT Not allowed Mandatory

CAPBUYER Not allowed Not allowed

CAPSELLER Not allowed Not allowed

FLOORBUYER Not allowed Not allowed

FLOORSLLER Not allowed Not allowed

COLLARBYER Not allowed Not allowed

COLLARSLLR 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 Then sequence B is ... And sequence E is ...
if subfield 1, of field 23A is
...

FIXEDFIXED Mandatory Mandatory

FLOATFLOAT Not allowed Not allowed

FLOATFIXED Mandatory Not allowed

FIXEDFLOAT 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 depends on field 22B in sequence A as follows:
Sequence A Sequence B (if Sequence E (if
present) present)
If field 22B is ... Then field 32G And field 22D is and field 37P is and field 37P is
is ... ... ... ...

PTRC Mandatory Mandatory Mandatory Mandatory

PTRM Mandatory Mandatory Not allowed Not allowed

96 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence A Sequence B (if Sequence E (if

present) present)
If field 22B is ... Then field 32G And field 22D is and field 37P is and field 37P is
is ... ... ... ...

RCPN Not allowed Mandatory Mandatory Mandatory

TERM Not allowed Not allowed Not allowed Not allowed

Note: The presence of sequences B and E is determined by error code E33.

MT 365
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 Sequence
Sequence B
E (if
If field 22B is Then field And field 33E And field (if present)
present)
... 32G is ... is ... 22D is ... and field 37P
and field
is ...
37P is ...

PTRC Mandatory Mandatory Mandatory Mandatory Mandatory

PTRM Mandatory Mandatory Mandatory Not allowed Not allowed

RCPN Not allowed Not allowed Mandatory Mandatory Mandatory

TERM Not allowed Not allowed Not allowed Not allowed Not allowed

Note: The presence of sequences B and E is determined by error code E33.

E35 MT 306
In sequences C (if present) and E, (if present - see error code D32), 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 ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence E

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence J

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Note: See also error code D32.

25 July 2014 97
FIN

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 ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence D

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence E

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence F

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence I

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

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 ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence D

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

98 Error Codes
 Chapter 3 Alphanumeric Codes

Sequence E

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence F

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

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 ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence D

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence F

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

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 ... Then field 86a is ...

Not present Not allowed

Present Optional

25 July 2014 99
FIN

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, Then, in the same sequence, or the same
field 56a is ... internal loop,
field 86a is ...

Present Optional

Not present Not allowed

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 ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence D

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence E

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

Sequence F

If field 56a is ... Then field 86a is ...

Not present Not allowed

Present Optional

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.

100 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence A2 Status (each occurrence)

In each occurrence of subsequence A2a Then in subsequence A2 Status

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::REJT :25D::CPRC//REJT or
:25D::IPRC//REJT or
:25D::RPRC//REJT

:24B::NMAT :25D::MTCH//NMAT

:24B::NAFI :25D::AFFM//NAFI

:24B::REPR :25D::CPRC//REPR or
:25D::IPRC//REPR or
:25D::RPRC//REPR
[1] If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.
MT 530
Within each occurrence of subsequence C1a Reason, 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 C1.

Sequence C Additional Information (each occurrence)

In each occurrence of subsequence C1a Then in subsequence C1 Status,

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::CAND :25D::IPRC//CAND

:24B::PACK :25D::IPRC//PACK

:24B::REJT :25D::IPRC//REJT
[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.

Sequence B Status (each occurrence)

In each occurrence of subsequence B1 Then in sequence B Status,

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::CAND :25D::IPRC//CAND

:24B::CANP :25D::IPRC//CANP

:24B::CGEN :25D::IPRC//CGEN

:24B::PACK :25D::IPRC//PACK

:24B::NMAT :25D::MTCH//NMAT or
:25D::INMH//NMAT

:24B::PEND :25D::SETT//PEND

:24B::PENF :25D::SETT//PENF

25 July 2014 101

FIN

Sequence B Status (each occurrence)

In each occurrence of subsequence B1 Then in sequence B Status,

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B//REPR :25D::IPRC//REPR

:24B::PPRC :25D::IPRC//PPRC
[1] 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:

Sequence C3 Status (each occurrence)

In each occurrence of subsequence C3a Then in sequence C3 Status,

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::CAND :25D::IPRC//CAND

:24B::CANP :25D::IPRC//CANP

:24B::CGEN :25D::IPRC//CGEN

:24B::PACK :25D::IPRC//PACK

:24B::NMAT :25D::MTCH//NMAT or
:25D::INMH//NMAT

:24B::PEND :25D::SETT//PEND

:24B::PENF :25D::SETT//PENF

:24B::REPR :25D::IPRC//REPR

:24B::PPRC :25D::IPRC//PPRC
[1] 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.

Subsequence A2 Status (each occurrence)

In each occurrence of subsequence A2a Then in subsequence A2 Status

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::CAND :25D::IPRC//CAND or
:25D::CPRC//CAND

:24B::CANP :25D::IPRC//CANP or
:25D::CPRC//CANP

:24B::CGEN :25D::IPRC//CGEN

:24B::DEND :25D::CPRC//DEND or
:25D::CALL//DEND or
:25D::TPRC//DEND

102 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence A2 Status (each occurrence)

In each occurrence of subsequence A2a Then in subsequence A2 Status

Reason (if present) field :25D::must be ... [1]
if field :24B:: is ...

:24B::NMAT :25D::MTCH//NMAT or
:25D::INMH//NMAT

:24B::PACK :25D::IPRC//PACK or
:25D::CPRC//PACK or
:25D::TPRC//PACK

:24B::PEND :25D::SETT//PEND

:24B::PENF :25D::SETT//PENF

:24B::REPR :25D::IPRC//REPR

:24B::REJT :25D::IPRC // REJT or

:25D::CPRC // REJT or
:25D::SPRC // REJT or
:25D::TPRC//REJT

:24B::CACK :25D::CALL//CACK

:24B::PPRC :25D::IPRC//PPRC

:24B::MOPN :25D::TPRC//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.

Sequence B (each occurrence)

If field :24B:: is present and is ... Then field :25D::is mandatory

and must be ... [1]

:24B::NMAT :25D::MTCH//NMAT or
:25D::INMH//NMAT

:24B::PEND :25D::MTCH//NMAT or
:25D::EPRC//PEND or
:25D::SETT//PEND or
:25D::RPRC//PEND

:24B::PENF :25D::SETT//PENF

:24B::REJT :25D::IPRC//REJT or
:25D::CPRC//REJT or
:25D::RPRC//REJT or
:25D::RERC//REJT or
:25D::REST//REJT or
:25D::TPRC//REJT

:24B::DEND :25D::CPRC//DEND or
:25D::RPRC//DEND or
:25D::CALL//DEND or
:25D::TPRC//DEND

25 July 2014 103

FIN

Sequence B (each occurrence)

If field :24B:: is present and is ... Then field :25D::is mandatory

and must be ... [1]

:24B::CAND :25D::IPRC//CAND or
:25D::CPRC//CAND

:24B::CANP :25D::IPRC//CANP or
:25D::CPRC//CANP

:24B::CGEN :25D::IPRC//CGEN

:24B::NAFI :25D::AFFM//NAFI

:24B::PACK :25D::IPRC//PACK or
:25D::CPRC//PACK or
:25D::RPRC//PACK or
:25D::RERC//PACK or
:25D::TPRC//PACK

:24B::CACK :25D::CALL//CACK

:24B::REPR :25D::CPRC//REPR or
:25D::IPRC//REPR or
:25D::RPRC//REPR

:24B::PPRC :25D::IPRC//PPRC

:24B::MOPN :25D::TPRC//MOPN

Field :24B:: is not present Not applicable

[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.

Subsequence A2 Status (each occurrence)

In each occurrence of subsequence A2a Then in subsequence A2 Status

Reason (if present) field :25D:: must be ... [1]
if field :24B:: is ...

:24B::CAND :25D::IPRC//CAND or
:25D::CPRC//CAND

:24B::CANP :25D::CPRC//CANP

:24B::PACK :25D::IPRC//PACK or
:25D::CPRC//PACK

:24B::PEND :25D::IPRC//PEND or
:25D::EPRC//PEND

:24B::REJT :25D::IPRC//REJT or
:25D::CPRC//REJT
[1] If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

104 Error Codes

 Chapter 3 Alphanumeric Codes

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 Sequence B Sequence D
if subfield 1 of
field 23A is ... Then field 37J And field 37L And field 37J And field 37L
must be ... must be ... must be ... must be ...

FIXEDFIXED Not allowed Not allowed Not allowed Not allowed

FLOATFLOAT Optional Optional Optional Optional

FLOATFIXED Not allowed Not allowed Optional Optional

FIXEDFLOAT Optional Optional Not allowed Not allowed

CAPBUYER Mandatory Not allowed Not allowed Not allowed

CAPSELLER Not allowed Not allowed Mandatory Not allowed

FLOORBUYER Not allowed Mandatory Not allowed Not allowed

FLOORSLLER Not allowed Not allowed Not allowed Mandatory

COLLARBYER Present Present Either 37J or 37L or both is/are

mandatory

Present Not present Optional Mandatory

Not present Present Mandatory Optional

COLLARSLLR Present Present Either 37J or 37L or both is/are

Mandatory

Present Not present Optional Mandatory

Not present Present Mandatory Optional

25 July 2014 105

FIN

2. If sequence B is not present:

Sequence A Sequence D
if subfield 1 of field 23A is
... Then field 37J must be ... And field 37L must be ...

FIXEDFIXED Not allowed Not allowed

FLOATFLOAT Optional Optional

FLOATFIXED Optional Optional

FIXEDFLOAT Not allowed Not allowed

CAPBUYER Not allowed Not allowed

CAPSELLER Mandatory Not allowed

FLOORBUYER Not allowed Not allowed

FLOORSLLER Not allowed Mandatory

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

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

3. If sequence D is not present:

Sequence A Sequence B
if subfield 1 of field 23A is
... Then field 37J must be ... And field 37L must be ...

FIXEDFIXED Not allowed Not allowed

FLOATFLOAT Optional Optional

FLOATFIXED Not allowed Not allowed

FIXEDFLOAT Optional Optional

CAPBUYER Mandatory Not allowed

CAPSELLER Not allowed Not allowed

FLOORBUYER Not allowed Mandatory

FLOORSLLER Not allowed Not allowed

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

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

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 ... Then field 14C is ...

ISDA Mandatory

Not = ISDA Not allowed

106 Error Codes

 Chapter 3 Alphanumeric Codes

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 Subsequence C1 (if Subsequence F1 (if And subsequences

if subfield 1 of field present) present) C2 and F2 are ...
77H is ... then fields 14G and and fields 14G and
37R are ... 37R are ...

AFB Not allowed Not allowed 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 Then subsequence B1 is ...

if subfield 1 of field 77H is ...

AFB Mandatory

DERV Not allowed

EMA Not allowed

FRABBA Mandatory

ISDA Not allowed

ISDACN Not allowed

OTHR Not allowed

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).

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.

25 July 2014 107

FIN

1. If sequence C is present:

Sequence A Sequence C Then subsequences C1, C2

if subfield 1 of field 77H is and field 14F is ... and C3 are ...
...

ISDA FRF-TAM-CDC Not allowed

FRF-T4M-CDC
FRF-T4M-CDCCOMP
FRF-TAG-CDC
FRF-TAG-CDCCOMP
FRF-TMP-CDCAVERAG

AFB FRF-SWAP-AMR Not allowed

FRF-SWAP-TMP-IF
FRF-SWAP-TMP-M
FRF-SWAP-T4M-AMR
FRF-CAP-TAM
FRF-CAP-T4M
FRF-FLOOR-TAM
FRF-FLOOR-T4M

Else C1 is mandatory
C2 and C3 are optional

2. If sequence F is present:
Sequence A Sequence F Then subsequences F1, F2
if subfield 1 of field 77H is and field 14F is ... and F3 are ...
...

ISDA FRF-TAM-CDC Not allowed

FRF-T4M-CDC
FRF-T4M-CDCCOMP
FRF-TAG-CDC
FRF-TAG-CDCCOMP
FRF-TMP-CDCAVERAG

AFB FRF-SWAP-AMR Not allowed

FRF-SWAP-TMP-IF
FRF-SWAP-TMP-M
FRF-SWAP-T4M-AMR
FRF-CAP-TAM
FRF-CAP-T4M
FRF-FLOOR-TAM
FRF-FLOOR-T4M

Else F1 is mandatory
F2 and F3 are optional

108 Error Codes

 Chapter 3 Alphanumeric Codes

3. If sequences B and F are present:

Sequence A Sequence F Then Sequence B And
if subfield 1 of and if field 14F subsequence and field 37U is subsequence
field 77H is ... is ... B1 is ... ... F1, F2 and F3
are ...

ISDA FRF-TAM-CDC Not allowed Mandatory Not allowed

FRF-T4M-CDC
FRF-T4M-
CDCCOMP
FRF-TAG-CDC
FRF-TAG-
CDCCOMP
FRF-TMP-
CDCAVERAG

AFB FRF-SWAP- Not allowed Mandatory Not allowed

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

Else Mandatory Optional F1 is mandatory

F2 and F3 are
optional

4. If sequences C and E are present:

Sequence A Sequence C Then Sequence E And
if subfield 1 of and field 14F is subsequence and field 37U is subsequences
field 77H is ... ... E1 is ... ... C1, C2 and C3
are ...

ISDA FRF-TAM-CDC Not allowed Mandatory Not allowed

FRF-T4M-CDC
FRF-T4M-
CDCCOMP
FRF-TAG-CDC
FRF-TAG-
CDCCOMP
FRF-TMP-
CDCAVERAG

25 July 2014 109

FIN

Sequence A Sequence C Then Sequence E And

if subfield 1 of and field 14F is subsequence and field 37U is subsequences
field 77H is ... ... E1 is ... ... C1, C2 and C3
are ...

AFB FRF-SWAP- Not allowed Mandatory Not allowed

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

Else Mandatory Optional C1 is mandatory

C2 and C3 are
optional

5. If sequences B and E are present:

Subsequence B1 is ... Sequence B
if field 37U is ...

Mandatory Optional

Subsequence E1 is ... Sequence E

if field 37U is ...

Mandatory Optional

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:
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
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 Sequence C Sequence C Sequence F Sequence F

if subfield 1 of then field 37J is and field 37L is and field 37J is and field 37L is
field 23A is ... ... ... ... ...

FIXEDFIXED Not applicable Not applicable Not applicable Not applicable

110 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence A Sequence C Sequence C Sequence F Sequence F

if subfield 1 of then field 37J is and field 37L is and field 37J is and field 37L is
field 23A is ... ... ... ... ...

FLOATFLOAT Optional Optional Optional Optional

FLOATFIXED Not applicable Not applicable Optional Optional

FIXEDFLOAT Optional Optional Not applicable Not applicable

CAPBUYER Mandatory Not allowed Not applicable Not applicable

CAPSELLER Not applicable Not applicable Mandatory Not allowed

FLOORBUYER Not allowed Mandatory Not applicable Not applicable

FLOORSLLER Not applicable Not applicable Not allowed Mandatory

COLLARBYER Present Present Either 37J or 37L or both is/are

mandatory

Present Not present Optional Mandatory

Not present Present Mandatory Optional

COLLARSLLR Present Present Either 37J or 37L or both is/are

mandatory

Present Not present Optional Mandatory

Not present Present Mandatory Optional

2. If sequence C is not present:

Sequence A Sequence F
if subfield 1 of field 23A is
... Then field 37J must be ... And field 37L must be ...

FIXEDFIXED Not applicable Not applicable

FLOATFLOAT Optional Optional

FLOATFIXED Optional Optional

FIXEDFLOAT Not applicable Not applicable

CAPBUYER Not applicable Not applicable

CAPSELLER Mandatory Not allowed

FLOORBUYER Not applicable Not applicable

FLOORSLLER Not allowed Mandatory

COLLARBYER Not applicable per rule 158

COLLARSLLR Not applicable per rule 158

3. If sequence F is not present:

Sequence A Sequence C
if subfield 1 of field 23A is
... Then field 37J must be ... And field 37L must be ...

FIXEDFIXED Not applicable Not applicable

25 July 2014 111

FIN

Sequence A Sequence C
if subfield 1 of field 23A is
... Then field 37J must be ... And field 37L must be ...

FLOATFLOAT Optional Optional

FLOATFIXED Not applicable Not applicable

FIXEDFLOAT Optional Optional

CAPBUYER Mandatory Not allowed

CAPSELLER Not applicable Not applicable

FLOORBUYER Not allowed Mandatory

FLOORSLLER Not applicable Not applicable

COLLARBYER Not applicable per rule 158

COLLARSLLR Not applicable per rule 158

E43 MT 361
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 Then sequence And sequence And sequence And sequence
if subfield 1 of B is ... C is ... E is ... F is ...
field 23A is ...

FIXEDFIXED Mandatory Not allowed Mandatory Not allowed

FLOATFLOAT Not allowed Mandatory Not allowed Mandatory

FLOATFIXED Mandatory Not allowed Not allowed Mandatory

FIXEDFLOAT Not allowed Mandatory Mandatory Not allowed

Note: See error codes E40 and E41 for additional subsequence(s) and field(s)
semantic checks.

E44 MTs 103 and 103 REMIT

If field 56a is not present, no field 23E may contain TELI or PHOI.

If field 56a is ... Then in each occurrence of field 23E,

subfield 1 must not contain ...

Not present TELI or PHOI

E45 MTs 103 and 103 REMIT

If field 57a is not present, no field 23E may contain TELE or PHON.

If field 57a is ... Then in each occurrence of field 23E,

subfield 1 must not contain ...

Not present TELE or PHON

112 Error Codes

 Chapter 3 Alphanumeric Codes

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, 103 REMIT, and 103 STP
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.

Sequence D, Then subsequence D2 is ...

if subsequence D1 is ...

Present Optional

Not present Mandatory

MT 362
At least one of the sequences B or D must be present.

If sequence B is ... Then sequence D is ...

Present Optional

Not present Mandatory

E48 MT 362
At least one of the sequences C or E must be present.

If sequence C is ... Then sequence E is ...

Present Optional

Not present Mandatory

Note: See error code E49.

MT 504
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, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] C1a,
then subsequence C1a1 is ...

Not present Optional

Present Mandatory
[1] This error code does not apply if the Data Source Scheme is present.
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, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] B1a,
then subsequence B1a1 is ...

Not present Optional

25 July 2014 113

FIN

In each occurrence of subsequence B1a, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] B1a,
then subsequence B1a1 is ...

Present Mandatory
[1] 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, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] C2a,
then subsequence C2a1 is ...

Not present Optional

Present Mandatory
[1] 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, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] B2a,
then subsequence B2a1 is ...

Not present Optional

Present Mandatory
[1] 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, In the same occurrence of subsequence

if field :22F::STCO//NSSP is ... [1] B1b,
then subsequence B1b1 is ...

Not present Optional

Present Mandatory
[1] 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).
Note: See also error code D96.

114 Error Codes

 Chapter 3 Alphanumeric Codes

MT 504
In sequence D, the presence of subsequence D1 depends on the presence of field
:22F::STCO//NSSP as follows:

Sequence D Then subsequence D1 is ...

[1]
if field :22F::STCO//NSSP is ...

Not present Optional

Present Mandatory
[1] 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 Then subsequence C1 is ...

[1]
if field :22F::STCO//NSSP is ...

Not present Optional

Present Mandatory
[1] 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: See also error code D96.
MT 504
In sequence E, the presence of subsequence E1 depends on the presence of field
:22F::STCO//NSSP as follows:

Sequence E Then subsequence E1 is ...

[1]
if field :22F::STCO//NSSP is ...

Not present Optional

Present Mandatory
[1] 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 Then subsequence D1 is ...

[1]
if field :22F::STCO//NSSP is ...

Not present Optional

Present Mandatory
[1] This error code does not apply if the Data Source Scheme is present.

25 July 2014 115

FIN

E52 MTs 502, 514, and 518

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present 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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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

116 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence E1

If field :95a::PSET is ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed within the same occurrence

Not present Optional

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 Subsequence A1
if field :22H::BUSE//SWIT is
... Then subsequence is ... And field :20C::PREV is ...

Present Mandatory, that is, minimum Mandatory, that is, must be

one occurrence of A1 present in minimum one
occurrence of A1

Not present Optional Optional

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.

25 July 2014 117

FIN

Sequence C Then field :20C::PREV is ...

if field :22H::BUSE//SWIT is ...

Present Mandatory, that is, must be present in

minimum one occurrence A1

Not present Optional

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 ... Then field :97a::SAFE is ...

Present Not allowed in the same subsequence

Not present Optional

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:

Sequence B (each occurrence)

If amount in field And field 23E is ... Then field 33B is ... And field 21F is ...
32B is ...

Equal to zero Present and code = Mandatory Optional

EQUI

Present and code not Not allowed Not allowed

=EQUI

Not present Not allowed Not allowed

Not equal to zero Not applicable Optional Optional

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 Sequence B
if field 12E is ... then field 30F is ...

EURO Mandatory

Not EURO Optional

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.
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.

118 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence A Then sequence B is And sequence A Then in every

if field :17B::ACTI is ... if field :17B::CONS occurrence of
... is ... sequence B
field :97a::SAFE and
field :17B::ACTI are
...

Y Mandatory, that is, at Y Mandatory

least one occurrence
N Not allowed

N Not allowed Not applicable Not applicable

E57 MTs 101 and 210

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 Sequence Field

101 A 50C

A 50G

B 50C

B 50G

210 50C

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 ... Then field :19A::ORDR is ...

Present Not allowed

Not present Mandatory

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 ... Then field :19A:: is ...

Present Not allowed

Not present Mandatory

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

25 July 2014 119

FIN

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 In the same occurrence of In the same occurrence of

subsequence B2 subsequence B2 subsequence B2
if field :36B:: is ... then field :36B::ORDR is ... and field :19A: is ...

Present Mandatory Not allowed

Not present Not applicable :19A::ORDR is mandatory

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 Then in at least one occurrence of

if subfield 1 of field 23G is ... subsequence A1
field 13A is ...

CANC Optional

Not = CANC Mandatory and must contain 515 [1]

[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:

Subsequence D1 (each occurrence)

If field :94B::RATS is ... Then field :70C::RATS is ...

Present Mandatory

Not present Not allowed

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 In the same occurrence of subsequence

if field :94B::RATS is ... C1a1A
then field :70C::RATS is ...

Present Mandatory

Not present Not allowed

E61 MT 514
When field :22F::PRIC is present, field :90a::DEAL must also be present.

Sequence B

If field :22F::PRIC is ... Then field :90a::DEAL is ...

Present Mandatory

Not present Optional

120 Error Codes

 Chapter 3 Alphanumeric Codes

E62 MTs 502, 514, and 518

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 ... Then field :19A::RESU is ...

Present Mandatory

Not present Not allowed

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 ... Then field :19A::RESU is ...

Present Mandatory

Not present Not allowed

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 ... Then field :19A::RESU is ...

Present Mandatory

Not present Not allowed

MT 564
If resulting amount (field :19B::RESU) is present in subsequence E2, then the corresponding
exchange rate (field :92B::EXCH) must be present in the same subsequence. If the resulting
amount is not present, then the exchange rate is optional. This check applies to subsequence
E2.

Subsequence E2

If field :19B::RESU is ... Then field :92B::EXCH is ...

Present Mandatory

Not present Optional

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 ... Then field :19B::RESU is ...

Present Mandatory

25 July 2014 121

FIN

Subsequence D2

If field :92B::EXCH is ... Then field :19B::RESU is ...

Not present Not allowed

MT 586
If an exchange rate (field :92B::EXCH) is present, the corresponding resulting amount (field
:19A::RESU) must be present in the same subsequence. If the exchange rate is not present,
then the resulting amount is not allowed. This check applies within each occurrence of
subsequence B5b.

Subsequence B5b

If field :92B::EXCH is ... Then field :19A::RESU is ...

Present Mandatory

Not present Not allowed

E63 MTs 502, 514, and 518

In each occurrence of sequence D, if field :95a::EXCH Stock Exchange or :95a::TRRE Trade
Regulator is present then field :97a:: is not allowed in the same sequence.

Sequence D (each occurrence)

If field :95a::EXCH or TRRE is ... Then field :97a:: is ...

Present Not allowed within the same occurrence

Not present Optional

MTs 513 and 515

In each occurrence of sequence E, if field :95a::EXCH Stock Exchange or :95a::TRRE Trade
Regulator is present then field :97a:: is not allowed in the same sequence.

Sequence E (each occurrence)

If field :95a::EXCH or TRRE is ... Then field :97a:: is ...

Present Not allowed within the same occurrence

Not present Optional

MTs 540, 541, 542, 543, 544, 545, 546, and 547
In each occurrence of sequence F, if field :95a::EXCH Stock Exchange or :95a::TRRE Trade
Regulator is present then field :97a:: is not allowed in the same sequence.

Sequence F (each occurrence)

If field :95a::EXCH or TRRE is ... Then field :97a:: is ...

Present Not allowed within the same occurrence

Not present Optional

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.

122 Error Codes

 Chapter 3 Alphanumeric Codes

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 Sequence B
if field :23G is ...
Then field :36B::ORDR is ... And field :36B::CANC is ...

NEWM Present Not Allowed

REPL Present Not Allowed

CANC Present Mandatory

Sequence A Sequence B
if field :23G is ...
Then field :19A::ORDR is ... And field :19A::CANC is ...

NEWM Present Not Allowed

REPL Present Not Allowed

CANC Present Mandatory

Note: In sequence B fields 36B::ORDR and 19A::ORDR are mutually exclusive,

see error code E58.

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.

If sequence B And sequence A Then sequence B

is ... field :22a::COLA is ... field : 19A::TRAA is ...

Present SLEB Optional

Not SLEB [1] Mandatory

Not present Not applicable Not applicable

[1] 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 Then sequence B

if field :22a::COLA is ... field :19A::TRAA is ...

SLEB Optional

Not SLEB [1] Mandatory

[1] If DSS is present then conditional rule does not apply.

25 July 2014 123

FIN

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 Then sequence B is ...
if field :17B::ACTI is ...

N Not allowed

Y Mandatory

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.

Sequence A Then sequence B is And sequence C is

... ...
If field :17B::ACTI is And field
... :22H::STST is ...

N STAT Not allowed Not allowed

N TRAN Not allowed Not allowed

Y STAT Mandatory Not allowed

Y TRAN Not allowed Mandatory

MT 569
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 In the same occurrence of subsequence

if field :17B::SECU//1!a is ... C1a1
then subsequence C1a1A is ...

N Not allowed

Y Mandatory

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 Then sequence B is ... And sequence C is ...

If field :17B::ACTI is ...

N Not allowed Not allowed

Y Optional Optional

124 Error Codes

 Chapter 3 Alphanumeric Codes

MT 576
If field :17B::ACTI in sequence A contains N, then sequence B must not be present.

Sequence A Then sequence B is ...

If field :17B::ACTI is ...

N Not allowed

Y Mandatory

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.

Sequence A Then sequence B is And sequence A, Then subsequence

if field :17B::ACTI is ... if field B1 is ...
... :22F::STTY//ACCT is
...

Y Mandatory Present, and DSS is Mandatory, that is

not present in field minimum one
:22F::STTY//ACCT occurrence must be
present in the
message [1]

Not present, or DSS Optional

is present in field
:22F::STTY/.../ACCT

N Not allowed Not applicable

[1] 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 Then subsequence B2c is And in all occurrences of

if field :97a::SAFE is ... ... subsequence B2c
field :97a::SAFE is ...

Present Optional Not allowed

Not present Mandatory (that is minimum Mandatory

one occurrence of
subsequence B2c) [1]
[1] The upper sequences :<B, B2> are also mandatory.

E68 MTs 503, 504, 505, 506, and 507

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 ... Then field :20C::RCTR is ...

Not present Mandatory

25 July 2014 125

FIN

Sequence A

If field :20C::SCTR is ... Then field :20C::RCTR is ...

Present 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.

Sequence A Then Sequence A Then in In every In the same

if field sequence B if each occurrence occurrence
:17B::ACTI is ... field:17B::CONS occurrence of of sequence
is ... is ... of sequence B B
sequence B if field then
field :17B::ACTI subsequence
:97a::SAFE is ... B1 is ...
and field
:17B::ACTI
are ...

N Not allowed Not applicable Not Not Not applicable

applicable applicable

Y Mandatory Y Mandatory Y Mandatory

that is, that is,
minimum minimum one
one occurrence
occurrence
N Not allowed

N Not allowed Not present Mandatory

(impact: rule per (Rule that is,
269) 256) minimum one
occurrence

<-- Rule 266 --> <-- Rule 256 --> <-- Rule 269 -->

Note: Error codes E66 and E56 take precedence over error code E69.

E70 MTs 540 and 541

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

Sequence E Then in one occurrence of subsequence

if field :22F::DBNM is ... E1 ...

Present Field :95a::SELL

is mandatory

Not present Not applicable

Note: See error code E84.

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

126 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence E Then in one occurrence of subsequence

if field :22F::DBNM is ... E1 ...

Present Field :95a::BUYR

is mandatory

Not present Not applicable

Note: See error code E84.

E71 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.

Subsequence A1 (each occurrence)

If field :22F::AGRE is ... Then field :70C::AGRE is ...

Not present Mandatory

Present 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.

Subsequence C3 (each occurrence)

If field :22H::BCOL//LCOL is ... Then field :98B::EXPI//OPEN is ...

Present Not allowed

Not present Optional

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.

Subsequence B3 (each occurrence)

If field :22H::BCOL//LCOL is ... Then field :98B::EXPI//OPEN is ...

Present Not allowed

Not present Optional

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.

Subsequence D3 (each occurrence)

If field :22H::BCOL//LCOL is ... Then field :98B::EXPI//OPEN is ...

Present Not allowed

Not present Optional

25 July 2014 127

FIN

MT 569
In each occurrence of subsequence C1a1, the presence of field :98a::SETT depends on the
value of field :17B:COLL as follows:

Subsequence C1a1 (each occurrence)

If field :17B::COLL is ... Then field :98a::SETT is ...

Y Mandatory

N Not allowed

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 Then for each occurrence of subsequence

if field :19A::SETT is ... D3
field :19A::SETT is ...

Present Not allowed

Not present Optional

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 Then for each occurrence of subsequence

if field :19A::SETT is ... C3
field :19A::SETT is ...

Present Not allowed

Not present Optional

E74 MT 502
In sequence B, field :22F::TOOR and/or field :90a::LIMI must be present.

Sequence B Then subsequence B1 is ... Subsequence B1

if field :22F::TOOR is ... and field :90a::LIMI is ...

Present Optional Optional

Not present Mandatory (that is, minimum Mandatory in at least one

one occurrence of occurrence of subsequence
subsequence B1) B1

E75 MT 502
In sequence B, if Original Ordered Quantity (field :36B::ORDR) is present more than once, then
Buy/Sell Indicator (field :22H::BUSE) must be present with Indicator code FPOO or IPOO or
IPPO.

Sequence B

If field :36B::ORDR is ... Then field :22H::BUSE ...

Not present or present only once May contain any indicator code

128 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence B

If field :36B::ORDR is ... Then field :22H::BUSE ...

Present more than once Indicator code must be FPOO or IPOO or

IPPO

MT 509
In sequence B, if either Deal Price (field 90a::DEAL) or Original Ordered Quantity (field
:36B::ORDR) are present more than once, then Buy/Sell Indicator (field :22H::BUSE) must be
present with Indicator code FPOO or IPOO or IPPO.

Sequence B

If field :90a::DEAL is ... If field :36B::ORDR is ... Then field :22H::BUSE ...

Not present or present only Not present or present only May contain any indicator
once once code

Present more than once Indicator code must be FPOO

or IPOO or IPPO

Present more than once Not applicable Indicator code must be FPOO
or IPOO or IPPO

MT 515
If either Deal Price (field 90a::DEAL) or Original Ordered Quantity (field :36B::ORDR) (in
sequence C), or Settlement Amount (field :19A::SETT) (in subsequence D3) are present more
than once, then in sequence C Buy/Sell Indicator (field :22H::BUSE) must be present with
Indicator code FPOO or IPOO or IPPO.

Sequence C Sequence C Subsequence D3 Sequence C

if field :90a::DEAL is if field :36B::ORDR if field :19A::SETT is then field
... is ... ... [1] :22H::BUSE ...

Present only once Not present or Not present or May contain any
present only once present only once indicator code

Present more than Indicator code must

once be FPOO or IPOO or
IPPO

Present more than Not applicable Indicator code must

once be FPOO or IPOO or
IPPO

Present more than Not applicable Not applicable Indicator code must
once be FPOO or IPOO or
IPPO
[1] Field :19A::SETT is not repetitive in subsequence D3, but subsequence D3 itself is repetitive.

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.

25 July 2014 129

FIN

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.
If the value date is after 31 December 2013, then the currency code LVL (Latvia) must not be
used as the currency of settlement.
See the table below for related MTs:

MT Field with Value Date [2] Field with Currency Code

101 30 in sequence A 32B in each occurrence of sequence B

102 32A in sequence C 32A in sequence C

102 STP

103 32A 32A

103 STP
103 REMIT

104 30 in sequence A 32B in each occurrence of sequence B

32B in sequence C (see error code C96)

104 (RFDD) [1] 30 in sequence A 32B in each occurrence of sequence B

107 30 in sequence A 32B in sequence C

200 32A 32A

201 30 32B in each occurrence

202 32A 32A

202 COV 32A 32A

203 30 32B in each occurrence

204 30 in sequence A 32B in each occurrence of sequence B

205 32A 32A

205 COV 32A 32A

207 30 in sequence A 32B in each occurrence of sequence B

210 30 32B in each occurrence

400 33A 33A

450 32A in each occurrence 32A in each occurrence

455 32A 32A

33C 33C

33D 33D

456 33D in each occurrence 33D in each occurrence

513 [98a with qualifier SETT in 19A with qualifier SETT in sequence C
[3]
sequence C] Field 19A with qualifier SETT in each
occurrence of subsequence D3

130 Error Codes

 Chapter 3 Alphanumeric Codes

MT Field with Value Date [2] Field with Currency Code

514 [98a with qualifier SETT in 19A with qualifier SETT in sequence B
[3]
sequence B] 19A with qualifier SETT in each occurrence of
subsequence C3

515 98a with qualifier SETT in 19A with qualifier SETT in sequence C
[3]
sequence C 19A with qualifier SETT in each occurrence of
subsequence D3

518 98a with qualifier SETT in 19A with qualifier SETT in sequence B
[3]
sequence B 19A with qualifier SETT in each occurrence of
subsequence C3

541 98a with qualifier SETT in 19A with qualifier SETT in each occurrence of
sequence B [3] subsequence E3

543 98a with qualifier SETT in 19A with qualifier SETT in each occurrence of
sequence B [3] subsequence E3

545 [98a with qualifier SETT in 19A with qualifier ESTT in subsequence E3
[3]
sequence B]

547 [98a with qualifier SETT in 19A with qualifier ESTT in subsequence E3
sequence B] [3]

564 98a with qualifier PAYD in 19B with qualifier ENTL in each occurrence of
subsequence E2 [3] subsequence E2

Seq E2 Cash Movements Seq E2 Cash Movements

Field 98a Qualifier VALU Field 19B Qualifier ENTL (each occurrence)
[3]

566 98a with qualifier POST in 19B with qualifier PSTA in each occurrence of
subsequence D2 subsequence D2

730 32D 32D

734 33A 33A

742 34A 34A

752 33A 33A

754 34A 34A

756 33A 33A

768 32D 32D

769 32D 32D

800 32A in sequence B 32A in sequence B

802 32A 32A

900 32A 32A

910 32A 32A

25 July 2014 131

FIN

[1] Text in parentheses indicates the value of tag 119.

[2] Fields shown in square brackets are optional.
[3] 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.

E77 MT 564
In each occurrence of sequence E and subsequence E2:

field :92F::GRSS cannot appear more than once, and field :92K::GRSS cannot appear
more than once, and both :92F::GRSS and :92K::GRSS cannot appear together.

field :92F::NETT cannot appear more than once, and field :92K::NETT cannot appear more
than once, and both :92F::NETT and :92K::NETT cannot appear together.

In each occurrence of subsequence E1 and subsequence E2, field :92A::TAXC cannot appear
more than once, and field :92F::TAXC cannot appear more than once, and field :92K::TAXC
cannot appear more than once, and none of the three fields :92A::TAXC, :92F::TAXC and
:92K::TAXC can appear in pair or all three together.
MT 566
In sequence D and in each occurrence of subsequence D2:

field :92F::GRSS cannot appear more than once.

field :92F::NETT cannot appear more than once.

In each occurrence of subsequence D1 and subsequence D2, field :92A::TAXC cannot appear
more than once, and field :92F::TAXC cannot appear more than once, and both :92A::TAXC and
:92F::TAXC cannot appear together.

E78 MT 564
In each occurrence of sequence E and subsequence E2:
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::TAXE is present more than once, then for each occurrence of field :92J::TAXE,
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.

In each occurrence of subsequence E1 and subsequence E2, if field :92J:: TAXC is present
more than once, then for each occurrence of field :92J:: TAXC, 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 error code E77.
MT 566
In sequence D and in each occurrence of subsequence D2:
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::TAXE is present more than once, then for each occurrence of field :92J::TAXE,
the Rate Type Code must be different.

132 Error Codes

 Chapter 3 Alphanumeric Codes

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

In each occurrence of subsequence D1 and subsequence D2, if field :92J:: TAXC is present
more than once, then for each occurrence of field :92J:: TAXC, 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 error code E77.

E79 MT 549
In sequence A, field :98a::STAT and field :69a::STAT are mutually exclusive.

Sequence A

If field :98a::STAT is ... Then field :69a::STAT is ...

Present Not allowed

Not present Optional

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 In the same occurrence of sequence E

if field :22F::CAOP//OTHR is ... [1] then field :70E::ADTX is ...

Present Mandatory

Not present Optional

[1] 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.
Sequence D

If field :22F::CAOP//SPLI is ... [1] Then field :70E::INST is ...

Present Mandatory (that is, minimum one occurrence)

Not present Optional

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

E80 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 ... Then sequence C is ...

Present Not allowed

Not present Optional

25 July 2014 133

FIN

MT 564
In each occurrence of sequence E and subsequence E2, if field :92J::TAXE is present, then field
:92F::GRSS must be present in the same sequence occurrence.
MT 566
In sequence D and in each occurrence of subsequence D2, if field :92J::TAXE is present, then
field :92F::GRSS must be present in the same sequence occurrence.

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 error code
E67), that is, if field :22F::STTY//ACCT is present.

In every Then, in the And the same And in every And in every
occurrence of same occurrence of occurrence of occurrence of
subsequence occurrence of subsequence subsequence subsequence
B1 subsequence B1 B1b B1b
if subsequence B1 field field :90a: is ... field
B1b is ... field :90a: is ... :19A::HOLD is :19A::HOLD is
... ...

Not present Mandatory Mandatory Not applicable Not applicable

Present once or Optional Optional Mandatory Mandatory

more

E83 MT 307
The following fields cannot appear more than once in the message:

Subsequence B3 Subsequence D1

:19B::BUYE :95a::CDEA

:19B::SELL :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:

134 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence C (each occurrence)

If field Then subsequence And subsequence And subsequence

:22H::COLL//4!c is ... C1 is ... C2 is ... C3 is ...

BCOL Not allowed Not allowed Mandatory

CCOL Not allowed Mandatory Not allowed

SCOL Mandatory Not allowed Not allowed

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:

Sequence B (each occurrence)

If field :22H::COLL Then subsequence And subsequence And subsequence

is ... B1 is ... B2 is ... B3 is ...

BCOL Not allowed Not allowed Mandatory

CCOL Not allowed Mandatory Not allowed

SCOL Mandatory Not allowed Not allowed

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:

Sequence D (each occurrence)

If field :22H::COLL Then subsequence And subsequence And subsequence

is ... D1 is ... D2 is ... D3 is ...

BCOL Not allowed Not allowed Mandatory

CCOL Not allowed Mandatory Not allowed

SCOL Mandatory Not allowed Not allowed

MT 536
In subsequence B1a2, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be
specified.

Subsequence B1a2

If field :22H::PAYM is ... Then field :19A::PSTA is ...

APMT Mandatory

Not = APMT Optional

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 ... Then field :19A::PSTA is ...

APMT Mandatory

25 July 2014 135

FIN

Subsequence B2b

If field :22H::PAYM is ... Then field :19A::PSTA is ...

Not = APMT Optional

Sequence C2

If field :22H::PAYM is ... Then field :19A::PSTA is ...

APMT Mandatory

Not = APMT Optional

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 ... Then field :19A::SETT is ...

APMT Mandatory

Not = APMT Optional

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 Then sequence E3 is ... And, in one occurrence of

if field :22H::PAYM is ... subsequence E3
field :19A::SETT is ...

APMT Mandatory Mandatory

Not = APMT Optional Optional

Note: See error code E87.

MT 586
In sequence B, if field :22H::PAYM//APMT is used, then field :19A::SETT must be specified.

Sequence B Then subsequence B5b is And in one occurrence of

if field :22H::PAYM is ... ... subsequence B5b
field :19A::SETT is ...

APMT Mandatory Mandatory

Not = APMT Optional Optional

Note: See error code E87.

E84 MT 307
In each occurrence of sequence B3, the following party fields cannot appear more than once:

Sequence B3a

:95a::CDEA

:95a::INTE

:95a::ACCW

136 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence B3a

: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

MT 370
In sequence B Net Position Details, the following party fields for subsequence B1 Cash Parties
cannot appear more than once:

Subsequence B1

:95a::INT2

:95a::INT1

: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 Subsequence C2 Sequence D

:95a::BUYR :95a::ACCW :95a::EXCH

:95a::DEAG :95a::BENM :95a::MEOR

:95a::DECU :95a::PAYE :95a::MERE

:95a::DEI1 :95a::DEBT :95a::TRRE

:95a::DEI2 :95a::INTM :95a::VEND

:95a::PSET :95a::TRAG

:95a::REAG

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

25 July 2014 137

FIN

MT 504
In each occurrence of sequence C, for subsequences C1a1 and C2a1, the following party fields
cannot appear more than once:

Subsequence C1a1 Subsequence C2a1

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

: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 Subsequence E1

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

:95a::PSET

:95a::REAG

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

MT 505
In each occurrence of sequence B, for subsequences B1a1 and B2a1, the following party fields
cannot appear more than once:

Subsequence B1a1 Subsequence B2a1

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

138 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence B1a1 Subsequence B2a1

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

: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 Subsequence D1

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

:95a::PSET

:95a::REAG

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

MT 507
In each occurrence of sequence B, for subsequences B1a1 and B1b1, the following party fields
cannot appear more than once:

Subsequence B1a1 Subsequence B1b1

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

:95a::PSET

:95a::REAG

25 July 2014 139

FIN

Subsequence B1a1 Subsequence B1b1

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

MTs 513 and 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 Subsequence D2 Sequence E

:95a::BUYR :95a::ACCW :95a::EXCH

:95a::DEAG :95a::BENM :95a::MEOR

:95a::DECU :95a::PAYE :95a::MERE

:95a::DEI1 :95a::DEBT :95a::TRRE

:95a::DEI2 :95a::INTM :95a::VEND

:95a::PSET :95a::TRAG

: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

140 Error Codes

 Chapter 3 Alphanumeric Codes

MT 537
The following party fields cannot appear more than once in the same occurrence of
subsequence B2b.

Subsequence B2b1

:95a::BUYR

: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

MTs 540 and 541

The following party fields cannot appear more than once in a message.

Subsequence E1 Subsequence E2 Sequence F

:95a::BUYR :95a::ACCW :95a::EXCH

:95a::DEAG :95a::BENM :95a::MEOR

:95a::DECU :95a::PAYE :95a::MERE

25 July 2014 141

FIN

Subsequence E1 Subsequence E2 Sequence F

:95a::DEI1 :95a::DEBT :95a::TRRE

:95a::DEI2 :95a::INTM :95a::TRAG

:95a::PSET :95a::VEND

:95a::REAG :95a::BRKR

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

MTs 542, 543, 544, 545; 546, and 547

The following party fields cannot appear more than once in a message.

Subsequence E1 Subsequence E2 Sequence F

:95a::BUYR :95a::ACCW :95a::EXCH

:95a::DEAG :95a::BENM :95a::MEOR

:95a::DECU :95a::PAYE :95a::MERE

:95a::DEI1 :95a::DEBT :95a::TRRE

:95a::DEI2 :95a::INTM :95a::TRAG

:95a::PSET :95a::VEND

:95a::REAG :95a::QFIN

:95a::RECU :95a::BRKR

: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

142 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence B1

: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

: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

25 July 2014 143

FIN

MT 578
The following party fields cannot appear more than once in a message.

Subsequence E1 Subsequence E2

:95a::BUYR :95a::ACCW

:95a::DEAG :95a::BENM

:95a::DECU :95a::PAYE

:95a::DEI1 :95a::DEBT

:95a::DEI2 :95a::INTM

:95a::PSET

:95a::REAG

:95a::RECU

:95a::REI1

:95a::REI2

:95a::SELL

MT 586
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

MT 670
In each occurrence of sequence B, in field 95a, each of the qualifiers ACCW, INT1 and INT2
may only be present in one iteration of subsequence B1.

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:

144 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence C2 (each occurrence)

If field :22H::DEPO//4!c is ... Then field :98A::TERM is ...

FIXT Mandatory

CLNT Not allowed

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:

Subsequence B2 (each occurrence)

If field :22H::DEPO//4!c is ... Then field :98A::TERM is ...

FIXT Mandatory

CLNT Not allowed

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:

Subsequence D2 (each occurrence)

If field :22H::DEPO//4!c is ... Then field :98A::TERM is ...

FIXT Mandatory

CLNT Not allowed

MT 537
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 And if subsequence B2b1 is Then in one occurrence of

if field :22H::REDE is ... ... subsequence B2b1
field :95a::REAG is ...

DELI Present Mandatory

Subsequence B2b And if subsequence B2b1 is Then in one occurrence of

if field :22H::REDE is ... ... subsequence B2b1
field :95a::DEAG is ...

RECE Present 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.

25 July 2014 145

FIN

Sequence C2 And if sequence C2a is ... Then in one occurrence of

if field :22H::REDE is ... sequence C2a
field :95a::REAG is ...

DELI Present Mandatory

Sequence C2 And if sequence C2a is ... Then in one occurrence of

if field :22H::REDE is ... sequence C2a
field :95a::DEAG is ...

RECE Present Mandatory

MT 548
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 And if subsequence B1 is ... Then in one occurrence of

if field :22H::REDE is ... subsequence B1
field :95a::REAG is ...

DELI Present Mandatory

Sequence B And if subsequence B1 is ... Then in one occurrence of

if field :22H::REDE is ... subsequence B1
field :95a::DEAG is ...

RECE Present Mandatory

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 Then in one occurrence of subsequence

if field :22H::REDE is ... E1
field :95a::DEAG is ...

DELI Mandatory

Sequence B Then in one occurrence of subsequence

if field :22H::REDE is ... E1
field :95a::REAG is ...

RECE Mandatory

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.

146 Error Codes

 Chapter 3 Alphanumeric Codes

Sequence B Then in the same occurrence of sequence

if field :22H::REDE is ... B
in one occurrence of subsequence B5a
field :95a::DEAG is ...

DELI Mandatory

Sequence B Then in the same occurrence of sequence

if field :22H::REDE is ... B
in one occurrence of subsequence B5a
field :95a::REAG is ...

RECE Mandatory

E86 MTs 502, 504, 505, 507, 513, 514, 515, 518, 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 In each For all Fields :95a:: all

occurrence of occurrence of occurrences of qualifiers must
sequence subsequence subsequence(s) belong to the
list(s)
Deliverers and/
or Receivers
from bottom up
and with no gap
(See Example
below)

502, 514, 518 C Not applicable C1 :95a::qualifier(s)

504 C (R) Not applicable C1a1 :95a::qualifier(s)

D Not applicable D1 :95a::qualifier(s)

505 B (R) Not applicable B1a1 :95a::qualifier(s)

C Not applicable C1 :95a::qualifier(s)

507 B (R) Not applicable B1a1 :95a::qualifier(s)

513, 515 D Not applicable D1 :95a::qualifier(s)

536 B (R) B1 (R) B1a2a :95a::qualifier(s)

537 B (R) B2 (R) B2b1 :95a::qualifier(s)

C (R) C2 C2a :95a::qualifier(s)

540, 541, 542, E Not applicable E1 :95a::qualifier(s)

543, 544, 545,
546, 547

548 B Not applicable B1 :95a::qualifier(s)

575 B (R) B1a (R) B1a4 :95a::qualifier(s)

C (R) Not applicable C2a :95a::qualifier(s)

25 July 2014 147

FIN

MT(s) In each In each For all Fields :95a:: all

occurrence of occurrence of occurrences of qualifiers must
sequence subsequence subsequence(s) belong to the
list(s)
Deliverers and/
or Receivers
from bottom up
and with no gap
(See Example
below)

578 E Not applicable E1 :95a::qualifier(s)

586 B (R) Not applicable B5a :95a::qualifier(s)

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
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 Receivers List

Code Qualifiers Code Qualifiers

DEI2 Deliverer's Intermediary 2 REI2 Receiver's Intermediary 2

DEI1 Deliverer's Intermediary 1 REI1 Receiver's Intermediary 1

DECU Deliverer's Custodian RECU Receiver's Custodian

SELL Seller (Deliverer) BUYR Buyer (Receiver)

DEAG [1] Delivering Agent REAG [1] Receiving Agent

[1] 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.

148 Error Codes

 Chapter 3 Alphanumeric Codes

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

:19A::EXEC

:19A::ISDI

:19A::LADT

:19A::LEVY

:19A::LOCL

:19A::LOCO

:19A::MARG

:19A::OTHR

: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

25 July 2014 149

FIN

Subsequence E3

: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

: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

150 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence E3

:19A::COAX

:19A::COUN

:19A::DEAL

:19A::EXEC

:19A::ISDI

:19A::LADT

:19A::LEVY

:19A::LOCL

:19A::LOCO

:19A::MARG

:19A::OTHR

: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

25 July 2014 151

FIN

Subsequence E3

:19A::ISDI

:19A::LADT

:19A::LEVY

:19A::LOCL

:19A::LOCO

:19A::MARG

:19A::OTHR

: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::COMT

:19A::COUN

:19A::DEAL

:19A::ESTT

:19A::EXEC

:19A::ISDI

152 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence E3

:19A::LADT

:19A::LEVY

:19A::LOCL

:19A::LOCO

:19A::MARG

:19A::OTHR

: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::COMT

:19A::COUN

:19A::DEAL

:19A::ESTT

:19A::EXEC

:19A::ISDI

:19A::LADT

:19A::LEVY

:19A::LOCL

25 July 2014 153

FIN

Subsequence E3

:19A::LOCO

:19A::MARG

:19A::OTHR

:19A::REGF

:19A::SHIP

:19A::SPCN

: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::ACRU

:19A::CHAR

:19A::COAX

:19A::DEAL

:19A::EXEC

:19A::LOCL

:19A::LOCO

:19A::OTHR

:19A::SETT

:19A::STAM

:19A::TRAX

:19A::WITH

MT 586
The following amount fields cannot appear in more than one occurrence of the amounts
subsequence B5b.

Subsequence B5b

:19A::ACRU

:19A::CHAR

154 Error Codes

 Chapter 3 Alphanumeric Codes

Subsequence B5b

:19A::COAX

:19A::DEAL

:19A::EXEC

:19A::LOCL

:19A::LOCO

:19A::OTHR

:19A::SETT

:19A::STAM

:19A::TRAX

:19A::WITH

E88 Available.

E89 MT 370
In sequence B, Netting Position Details, if field :22H::RECP indicator is PAYO or RECE, then
subsequence B1 Cash Parties must be present at least twice, once with field :95a:: ACCW and
once with field :95a:: BENM.
In sequence B, Netting Position Details, if field :22H::RECP indicator is NOPA, then
subsequence B1 Cash Parties must not be present.

E90 MT 307
Repetitive subsequence B3 must be present exactly twice in the message.
Note: Error code E90 takes precedence over error codes E84 and E91.
MT 321
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 524, 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 ... Then field :99B::SETT is ...

Present Mandatory

Not present Optional

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:

25 July 2014 155

FIN

Sequence A Sequence B3 (each occurrence)

if field :22H::NEGR then subsequence B3a is ...
is ...

GRSC Mandatory

NETC or UNKN Not allowed

Field :22H::NEGR not present Mandatory

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, In one occurrence of subsequence C1

if field :22H::PRIT is ... then field ...

APCP or IPCP :95a::CDEA is mandatory

APFM or IPFM :95a::ACCW is mandatory

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.
Note: See also error code E84.
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 And if subsequence B3a is present

occurrence of (that is, is mandatory per rule 291)
sequence B3, then ...
if field :19B:: is
... In one And in all other optional occurrence(s) of B3a,
occurrence of field ...
subsequence
B3a,
field ...

BUYE :95a::CDEA is :95a::INTE is :95a::ACCW is :95a::BENM is

mandatory optional optional not allowed

SELL :95a::ACCW is :95a::INTE is :95a::CDEA is :95a::BENM is

mandatory optional optional optional

MT 321
In a message, the following sequence C fields cannot appear more than once:

156 Error Codes

 Chapter 3 Alphanumeric Codes

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.

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

Subsequence B2 Then And in And in any And in any

if field subsequence subsequence occurrence of occurrence of
:97C::SAFE//GENR B2 is ... B2 subsequence subsequence
is ... field 93a is ... E1 E2
field 36 B is ... field 19B is ...

Present Not repetitive Not allowed Not allowed Not allowed

min-Max=1-1

Not present Repetitive min- Optional Optional Optional

Max=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.

25 July 2014 157

FIN

Subsequence B1 Then subsequence B1a is ...

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

N Not allowed

Y Mandatory

E96 MT 575
Within subsequence B1a, subsequence B1a2 and subsequence B1a3 are mutually exclusive.

If subsequence B1a2 is ... Then subsequence B1a3 is ...

Present Not allowed

Not present 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 Sequence B
if field :22H::COAL//4!c is ... then field :95a::EXPP is ...

INIT Mandatory

VARI Mandatory

TERM Not allowed

E98 Available.

E99 Available.

3.5 G Codes - Service-specific Validation

Australian PDS service:

G01 MTs 103, 103 REMIT, and 103 STP

The letter option of the 'selected field' is neither A nor C, nor D.
MT 202
The letter option of the 'selected field' is neither A nor D.

G02 MTs 103, 103 REMIT, 103 STP or MT 202

The format of the 'selected field letter option A' is invalid.

G03 MTs 103, 103 REMIT, 103 STP or MT 202

The format of the 'selected field letter option D' is invalid.

158 Error Codes

 Chapter 3 Alphanumeric Codes

G04 MTs 103, 103 REMIT, and 103 STP

The 'selected field' is missing, that is at least one of the following fields must be present: 56a,
57a

G18 MTs 103, 103 REMIT, and 103 STP

The format of the 'selected field letter option C' is invalid.

Canadian Large Value Transfer Service (LVTS):

G05 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.

Miscellaneous - Message Specific

G06 MT 103
Field 77T is not allowed.
MT 103 REMIT
Field 77T must be present.

G26 MT 502, MT 509, or MT 515 with a funds code in field :22H::BUSE may only be sent by users
that are members of the FIN Funds Closed User Group (CUG).
For more information about MTs 502, 509, and 515, see the Category 5 Message Reference
Guide, Volume 1.

Continuous Linked Settlement (CLS):

G07 In MT 300 eligible for the FINCopy service CLS or CLT, any field 53a present in sequence B
must be used with option A.

G08 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.

G09 In MT 300 eligible for the FINCopy service CLS or CLT, if field 17U is used it must contain the
value N.

G10 In MT 300 eligible for the FINCopy service CLS or CLT, any field 56a present in sequence B
must be used with option A.

G13 In MT 304 sent to the CLSB server, field 94A must contain ASET.

G16 In MT 304 sent to the CLSB server, any field 53a present in sequence B must be used with
option A.

25 July 2014 159

FIN

G17 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.
Note: Field 57A, index 19 is mandatory.

G19 In MT 305 eligible for the FINCopy service CLS or CLT, field 53a must be used with option A.

G20 In MT 305 eligible for the FINCopy service CLS or CLT, field 56a must be used with option A.

G21 In MT 305 eligible for the FINCopy service CLS or CLT, field 57A must be present.

G22 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****.

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****.

G24 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.

3.6 H Codes - Basic Header and Application Header Validation

H01 Basic Header not present or format error block 1

H02 Application identifier not A (General Purpose Application) or F (FIN)

H03 Invalid service message identifier (unknown or not allowed from user)

H04 - Available
H09

H10 Bad logical terminal address or application not enabled for the logical terminal

H15 Bad session number

H20 Error in the input sequence number

H21 Error in the message sender's branch code.

H25 Application header format error or not present when mandatory

H26 Input/output identifier not 'I' (on input from logical terminal)

H30 Message type does not exist for this application

160 Error Codes

 Chapter 3 Alphanumeric Codes

H40 This priority does not exist for this message category

H50 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

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

This error can also occur when a message is sent from a financial institution to a CORP or
TRCO and the sender is not subscribed to the SCORE FIN service.
See Knowledge Base tip 5018412.

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.

H55 Available

H80 Delivery option error

H81 Obsolescence period error

H98 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.

H99 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).

3.7 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)

25 July 2014 161

FIN

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, 370, 380, 381, 500-510, 513-515, 517-519, 524, 527-530, 535-538, 540-549,
558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, and 586.

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

3.8 L Codes - LOGIN Errors

L01 Login Request received while previous Login Request still pending

L02 Slice Processor recovery in progress

L03 Session already open on another Regional Processor, and that Regional Processor is
recovering

L04 Destination takeover in progress

L05 Unable to close previous session due to recovery in progress at Slice Processor or old Regional
Processor

L30 Login presented before time/day expressed in previous logout

L35 Logical terminal inhibited (that is temporarily unable to work with SWIFT). Call your Customer
Support Centre.

L38 Logical terminal does not belong to Sign Distinguished Name (DN) organisation

L39 Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN)
organisation

L55 Login NAK error code (field tag 503) to indicate that the login with recovery option is not
currently supported

L56 Logical terminal is not in recoverable state. The FIN interface should execute fresh Login
procedure

162 Error Codes

 Chapter 3 Alphanumeric Codes

3.9 M Codes - Message Errors

M50 Internal provisioning error: message length exceeded

M52 Internal provisioning error: too many processing rules are selected when processing a message

M53 Internal provisioning error: more than one VAS is provisioned for a rule

M60 Non-SWIFT character encountered

M71 Logical terminal does not belong to Sign Distinguished Name (DN) organisation

M72 Logical terminal's owning master destination does not belong to sign Distinguished Name (DN)
organisation

M73 Signatures present but not allowed for this message type

M74 Signatures not present but required for this message type

M75 Signatures not present but required by this Copy service

M76 Signatures present but not allowed by this FINCopy service

M77 Unable to decode the Signature block

M78 SSI - Invalid digest for SSI message, or mandatory digest for SSI message missing

M79 SSI - M digest verification error

M80 SSI - B digest verification error

M81 SSI - Internal error while processing SSI message

3.10 N Codes - Market Infrastructure Resiliency Service (MIRS)

Errors
N01 Receipt of multi-part message timed out

N02 Invalid multi-part checkpoint message

N03 A more recent checkpoint {0} has already been received

N04 Duplicate checkpoint identifier

25 July 2014 163

FIN

N05 The checkpoint identifier timestamp is in the future

N06 MIRS is not in dormant mode and cannot process checkpoint messages

N09 The MIRS server is temporarily unavailable. Please try again later.

N10 Missing account {0}

N11 Unknown account {0}

N12 Duplicate account {0}

N13 Incorrect currency for account {0}

N14 Total balance does not add up to 0 for currency {0}

N20 Details are missing for participant {0}

N21 Duplicate participant {0}

N22 Wrong BIC {0} associated to participant {1}

N23 Unknown type {0} for participant {1}

N24 Invalid currency {0} in daily limit for participant {1}

N25 Participant {0} owns account(s) and cannot be deleted

N26 Details are missing for group account {0}

N27 Duplicate group account {0}

N28 Invalid currency {0} for group account {1}

N29 Group account {0} has account(s) and cannot be deleted

N30 Details are missing for account {0}

N32 Unknown type {0} for account {1}

N33 Unknown group account {0} for account {1}

N34 No accounts assigned to group account {0}

164 Error Codes

 Chapter 3 Alphanumeric Codes

N35 Unknown participant {0} for account {1}

N36 Invalid currency {0} for account {1}

N37 Account {0} cannot be deleted: the balance is not equal to 0

N38 Invalid holiday date {0}

N39 Duplicate holiday date {0}

N40 Inconsistent daily limits for participant {0}

N41 Group account missing for account {0}

N42 Group account {0} used for multiple participants

N43 Group accounts are not supported for this MIRS instance

N44 The currency for account {0} cannot be changed because the balance is not 0

N45 The reporting required flag for account or group account {0} is set but the report destination for
participant {1} is not set

N46 The notification required flag for account {0} is set but the report destination for participant {1} is
not set

N47 The report destination for participant {0} cannot be removed because there are associated
accounts or group accounts with the reporting required or notification required flag set

3.11 P Codes - Protocol Errors

P16 Unexpected user data received

P18 Input message sent when session was selected for output only

P20 Input message sent when session was selected for output only

P21 Re-Select/Re-Login, logical terminal not in reconnect ready state

P23 Re-Select Request format error

P24 Re-Select Request semantic error

P27 Select message received when Re-Select expected

25 July 2014 165

FIN

P28 Session recovery not attempted: logical terminal did not select recovery option at Login

P29 Session not recovered: connection failure while waiting for Application Control associate request

P30 Application session not in recoverable state

P32 Re-Select error - Session Number mismatch

P33 Re-Select error - F330 input sequence numberFIN interface failed validation

P34 Re-Select error - F330 input sequence number-ACKFIN interface failed validation

P35 Re-Select error - F330 output sequence numberFIN interface failed validation

P36 Re-Select error - F330 output sequence number-ACKFIN interface failed validation

P37 Re-Select error - Window size mismatch

P38 Re-Select error - Select state mismatch

P39 Re-Select error - Subsets mismatch

P40 Re-Select error - LT-directed field mismatch

P41 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

P42 Logical terminal does not belong to Sign Distinguished Name (DN) organisation

P43 Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN)
organisation

PRI Timeout expired on a response to a primitive sent to the user

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

R01 LOGOUT/QUIT received while session is recovering

R02 Replay of SELECT-ACK

R03 Replay of Re-SELECT-ACK

R04 Timeout for Re-Login with outstanding output sequence number-ACKs

166 Error Codes

 Chapter 3 Alphanumeric Codes

3.13 S Codes - System-initiated Abort Errors

S01 User aborted by system in order to do a destination takeover

S02 Must execute delivery instructions redefinition

S03 Level 3 recovery

S04 User failed to LOGOUT within the time limit requested by the system

S05 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 Test and Training session aborted because its master has been changed

S51 Unable to decode Public Key Infrastructure Signature Block in Login Request

S53 Login must contain level 2 of Sign Distinguished Name (DN)

S54 Invalid signature size in Login Request

S55 System error - Level 2 of Sign Distinguished Name (DN) in Login Request must contain 8
characters

S56 Login ACKs contain invalid field tag

S59 System error, invalid association ident

S71 Signature syntax error

S72 Signature semantic error

S76 Session aborted because subsets sharing mode change was requested using MT 077

3.14 S Codes - Select Errors

S10 Incorrect application identifier (application disabled or unknown)

S11 Incorrect select state

S12 Output state selected but not logged on to primary Regional Processor

S13 Output state selected but neither LT-directed messages nor delivery subsets were selected.

25 July 2014 167

FIN

S14 LT-directed flag either invalid or 'Y' but output state not requested

S15 Delivery subsets selected but output state not requested

S16 Window size error

S17 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 System is reorganising the delivery subsets as a result of a delivery instructions redefinition

S20 No delivery subset allowed in a Test & Training LTM-SELECT command.

S21 Remove Application Request sent by Regional Processor to the FIN interface to indicate that
FIN session at Regional Processor was not established

S30 Select presented before time/day specified in last QUIT

S31 More than 30 delivery subsets defined

S35 Logical terminal inhibited (that is temporarily unable to work with SWIFT). Call your Customer
Support Centre.

S36 Bad Trailer Block in Select message

S42 A delivery subset has been specified twice in the Select Request

S43 Logical terminal does not belong to Sign Distinguished Name (DN) organisation

S44 Logical terminal's owning master destination does not belong to Sign Distinguished Name (DN)
organisation

S61 Unable to decode Public Key Infrastructure Signature Block in Select Request

S63 Select must contain level 2 of Sign Distinguished Name (DN)

S64 Invalid Signature size in Select Request

S65 Level 2 of Sign Distinguished Name (DN) in Select Request must contain 8 characters

168 Error Codes

 Chapter 3 Alphanumeric Codes

S66 Select ACKs contain invalid field tag

S68 Invalid association identification

3.15 T Codes - Text Validation

T00 Not used.

T01 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

T04 Code word error.

This check applies to:

subfield 4, field 26C, in MTs 600, 601, 604, 605, 606, 607, 608, 609 and 620.

T05 Code word error.

This check applies to:

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.

25 July 2014 169

FIN

This check applies to:

subfield 3, field 33G

T08 Code word error.

This check applies to:

field 23, in MTs 102 STP and 609.

field 71A, in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 104, 107, 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

T10 The repetitive sequence occurred more than the maximum number of times permitted.

T11 The repetitive sequence occurred less than the minimum number of times permitted.

T12 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.

170 Error Codes

 Chapter 3 Alphanumeric Codes

This check applies to:

field 19A in MTs 321, 370, 502, 506, 508, 513, 514, 515, 518, 527, 535, 536, 537, 538, 540,
541, 542, 543, 544, 545, 546, 547, 548, 558, 564, 566, 567, 569, 574IRSLST, 575, 578,
and 586.

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.

field 37M in MTs 340, 341, 362 and 644.

field 37R in MTs 341, 360, 361, 362 and 644.

field 90L in MTs 564-566

field 92A in MTs 321, 500, 501, 502, 506, 508, 513, 514, 515, 518, 519, 524, 527, 535, 538,
540, 541, 542, 543, 544, 545, 546, 547, 558, 564, 565, 566, 568, 569, 574IRSLST, 576,
578, and 586.
field 93B in MTs 501, 535, 536, 564, 565, 566, 567, and 568.

field 93C in MTs 535, 564, 565, 566 and 568.

field 93D in MT 575.

field 98D in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601.

field 98E in MTs 370, 500-510, 513-515, 517, 518, 519, 524, 527, 530, 535-538, 540-548,
558, 569, 574-IRSLST, 574-W8BENO, 575, 576, 578, and 586.

field 99A in MTs 370, 506, 513, 514, 515, 518, 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 Subfield Sign must be either + or -.

T16 Time offset is not valid. (<OFFSET> has the same format as time <HHMM>; it must be
00<=HH<=13 and 00<=mm<=59.)

T17 Field, line, subfield, or component consists of blanks, ('CrLf') or missing mandatory line, subfield
or component.

25 July 2014 171

FIN

T18 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.

T19 Field :94C::SSIR is not allowed more than 80 times in MT 670.

Field :95P::SSIR is not allowed more than 100 times in MT 670.

T20 Code word error.

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

T21 Code word error.

This check applies to:

field 13H in MT 298/091, 298/092

field 17C in MT 298/094

field 17D in MT 298/095

field 17F in MT 298/092

field 17G in MT 298/092

field 17J in MT 298/092

field 17K in MT 298/093

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

172 Error Codes

 Chapter 3 Alphanumeric Codes

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 /.

T24 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.

T25 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.

T26 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 22W

field 94B

fields 95Q, 95R, 95S, 95T, 95U, and 95V

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 BIC incorrectly formatted or invalid.

T28 SWIFT BIC is not a valid destination.

T29 SWIFT BIC contains an invalid branch code.

T30 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).

T31 The line, subfield or component separator or delimiter (CrLf, blank, slash, or double slash) is
missing or incorrect.

T32 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:

25 July 2014 173

FIN

Field Format Invalid data

:20: 16x ;ABC

:20: 16x ^ABC

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 Format Invalid data

6a AAAAAA(CrLf) ACTUAAA(CrLf)

or consists of one or more hidden characters, for example, trailing blank(s),

Example:

Field Format Format Invalid data

6a A(CrLf) ACTUAe(CrLf)

6a ACTUAL(CrLf) ACTUALe(CrLf)

5!a OTHER(CrLf) OTHERe(CrLf)

6x /AC:ee(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 Format Invalid data

9a AAAAAAAAA AAAAeAAAA(CrLf)

5a OTHER O1HER(CrLf)

5a OTHER O:HER(CrLf)

16x XXXXXXX XXX;XXX

Where:

'e' = blank (space) character

'1' = numeric character

':' = special character (not an alphabetic character)

';' = Not in the <X> character set

174 Error Codes

 Chapter 3 Alphanumeric Codes

T34 Length of field, line, subfield, or component contents is too short, or a character does not belong
to the right character set.

T35 Code word error.

This check applies to:

subfield 1, field 26C

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, and 361

field 17E in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17F in MTs 304, 306, 340, 360, and 361

field 17G in MT 304

field 17I in MTs 300 and 304

field 17L in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17N in MT 304

field 17O in MT 304

field 17Q in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17S in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17T in MT 300

field 17U in MT 300

field 17W in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17X in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17Z in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 22A in MTs 300, 303, 304, 306, 320, 330, 340, 341, 350, 360, 361, 362, 364, 365, and
620

field 22S, subfield 1, in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 23B in MTs 103, 103 REMIT, 103 STP, 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.

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

25 July 2014 175

FIN

T38 Time illogical.

T39 Time of UTC Indicator (HH[MM]) is not in the valid range (00<=HH<=23, 00<=MM<=59).
This check applies to:

field 98D in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 98E in MTs 370, 500-510, 513-515, 517, 518, 519, 524, 527, 530, 535-538, 540-548,
558, 564, 566, 569, 574IRSLST, 574W8BENO, 575, 576, 578, and 586.

T40 Missing amount/number or incorrect amount/number first character.

T41 Available.

T42 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.

T44 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.

T45 Invalid non-SWIFT BIC.

T46 A Test and Training destination must not be used in a live message.

T47 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

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, 103 REMIT, 104, 107, 207, 256, and 416

subfield 1, field 39P, in MT 303

176 Error Codes

 Chapter 3 Alphanumeric Codes

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 300, 304, 305, 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 STP

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 Available.

T50 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

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, 102 STP, 103, 103 REMIT, 103 STP, 110, 111, 112, 200, 202, 205,
256, 910

Note:
1. In <DATE4>, format YYYYMMDD, the value '0000' for YYYY is invalid.

25 July 2014 177

FIN

T51 Code word 'C', 'D', 'RC', 'RD', 'EC' or 'ED' error.

T52 Invalid currency code or price code PCT, REN or YLD.

T53 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 STP, 103, 103 REMIT, 103 STP, 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 STP, 103, 103 REMIT, 103 STP, 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 STP, 103, 103 REMIT, 103 STP, 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.

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

field 40F in MT 740

178 Error Codes

 Chapter 3 Alphanumeric Codes

T60 Code word error.

This check applies to:

field 26F, in MTs 305, 306, 601, or in any message appended in common groups n92, n95
or n96

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, 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. This check applies to field 31X.

T63 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

T64 Code word error.

This check applies to:

line 1, field 40B, in MTs 710 and 720

field 12F, in MT 306

T65 Code word error. This check applies to:

field 12D in MT 306

T66 Code word error.

This check applies to:

field 12E, in MT 306

line 2, field 40B, in MTs 710 and 720

T67 Code word error.

25 July 2014 179

FIN

This check applies to:

field 17H in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17P in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

field 17R, in MTs 320, 330, and 620

field 17V, in MT 306

field 17Y, in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

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 Available.

T70 Available.

T71 Code word error.

This check applies to:
field 22D in MTs 360, 361, 364, and 365

field 22G, in MT 306

T72 Code word error.

This check applies to:

field 22J, in MT 306

T73 Invalid country code. See the BIC Directory General Information - Country Codes.
This check applies to:

field 50F in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 202 COV, 205 COV, 210,
910.

field 59, 59A, subfield IBAN, in MTs 102 STP and 103 STP.

field 94C, 2!a (Country Code), in MTs 500, 501, 502, 508, 510, 513, 514, 515, 518, 519,
524, 535, 536, 537, 538, 540, 541, 542, 543, 544, 545, 546, 547, 548, 564, 565, 566, 567,
568, 574IRSLST, 574W8BENO, and 670

field 95C, 2!a (Country Code), in MTs 502, 504, 505, 507, 513, 514, 515, 518, 527, 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
574W8BENO

180 Error Codes

 Chapter 3 Alphanumeric Codes

field 95S, 2!a (Country Code), in MTs 500, 501, 502, 504, 505, 507, 509, 510, 513, 514,
515, 518, 519, 540, 541, 542, 543, 544, 545, 546, 547, 565, 566, 576, 578, and 586.

T74 The currency code must be the same for each indicated subfield in the field.
This check applies to:

subfields 6 and 8, field 68B and subfields 6, 7 and 8, field 68C

T75 Available.

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 Invalid Invalid Invalid

:50H:/X :50H:X :50H:/X :50H:/X

X X X

:50H:/X X

X X

X X

T77 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, error code E10 takes precedence, that
is, "the first character of the first line must be /", see error code E10)

(81-89)D

91D

96D

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

25 July 2014 181

FIN

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 81J, in MTs 300, 304, and 305

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

subfield 1 of each line, field 89J, in MTs 300, 304, and 305

subfield 1 of each line, field 91J, in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

subfield 1 of each line, field 96J, in MTs 300, 305, 306, 340, 341, 360, 361, 600, and 601

T79 Available.

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: This check applies to MTs 10x, 11x, 20x, 195, 199, 295 and 299.

T81 Format of field 72 Reject/Return is not allowed in this message.

This check applies to:

field 72, MTs 102 STP and 103 STP

T82 Euro-Related Information (ERI) format is not allowed in this field in this message.
This check applies to:

field 72, MT 102 STP and 103 STP

T83 Available.

182 Error Codes

 Chapter 3 Alphanumeric Codes

T84 Available.

T85 Code word error.

This check applies to :

field 23G, subfield 2, in MTs 307, 321, 370, 380, 381, 500-510, 513-515, 517-519, 524, 527,
530, 535-538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, , 586,
670, 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, 370, 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, 586, 670, 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

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.

25 July 2014 183

FIN

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: This check is applied only to 'common group messages'.

T95 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: This check is applied only to 'non-common group messages'.

T96 In field 22, subfield 2, or in field 22C, components 1 and 3 are not in alphabetical sequence.

T97 Code word error.

This check applies to:

subfield 2, field 28E, in MTs 506, 515, 527, 535, 536, 537, 538, 558, 564, 568, 569,
574W8BENO, 574IRSLST, 575, 576, and 586

T98 Available.

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 "{".

103 Service identifier

113 Banking priority

108 Message user reference

119 Validation flag

423 Balance checkpoint date and time

106 Message input reference

424 Related reference

115 Addressee information

184 Error Codes

 Chapter 3 Alphanumeric Codes

433 Sanctions screening information for the receiver

U01 Bad bank priority

U02 Bad message user reference

U03 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.

U07 User Header not authorised in system messages, except for MT 097 following MIRS
implementation

U08 Invalid syntax, format, code word in tag 119, or field tag 119 is missing

U09 Special validation is undefined for this message type.

User has used tag 119 in a message that is not a candidate for special processing.

U10 Invalid syntax, format, date, time in tag 423

U11 Invalid message input reference format in tag 106

3.17 V Codes - System Message Errors and Message Block

Format Errors
V01 Invalid text block

V02 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

V03 Minimum iterations of a field/component not satisfied

V04 Invalid date field

V05 Invalid time field

V06 Invalid message input reference/message output reference

V07 Generic error for failure of check against a character set, or line, subfield or component request
is empty

V08 Generic error for failure of range check on a field

25 July 2014 185

FIN

V09 Invalid report option

V10 End of block character '}' not found, or line, subfield or component greater than defined length

V11 Invalid logical terminal address, or invalid destination

V12 Invalid generation time option in MT 044

V13 Component content error, for example, invalid broadcast selection criteria, or invalid broadcast
heading code, or invalid broadcast heading text, or invalid country code, or invalid group code

V14 Selection MT 073 error, syntax, duplicate

V15 Future version not available on the system (Test and Training)

V20 Invalid application ID

V21 Session History Request for disabled application

V22 Empty report

V23 Invalid receiving pseudo logical terminal

V24 Logical Terminal History or Undelivered Change Request received in invalid application

V25 Empty report in a message sample request (Test and Training)

V26 Available

V30 Destination is not value date sensitive

V31 Specified value date does not refer to the past

V32 Specified cut-off time does not refer to the past 12 hours
Note: V50 - V68 are error codes issued for MT 047 errors.

V40 The start time is not within the allowed limit; or the end-time is earlier than the start time; or the
end-time is later than the current-time

V41 The range between the start and end time exceeds allowed limit

V42 The sending BIC in MT 024 Bulk Retrieval Request has not subscribed to the bulk retrieval
service

186 Error Codes

 Chapter 3 Alphanumeric Codes

V50 Incorrect delivery subset mnemonic (not unique, may not start with 'LTDIR')

V51 Message priority/category/type assigned to more than one delivery subset

V52 No message types assigned to this subset

V53 Message category/type not available for this destination

V54 Mismatch message category/type and priority

V55 Not all message category/types assigned

V56 Once a message category has been specified in a delivery subset, specific messages from that
category may not be specified in subsequent subsets

V57 Missing priority-assignment in the MT 047 command

V58 This MT 047 is replaced by a subsequent MT 047

V59 Same priority is defined within a subset more than once

V60 More than 30 delivery subsets specified

V61 Service code assigned to more than one delivery subset

V62 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

V63 Branch code with same priority assigned to more than one delivery subset

V64 Incorrect or invalid branch code specified in MT 047

V65 Invalid combination of branch code - priority

V66 Field tag with same priority assigned to more than one delivery subset

V67 Incorrect or invalid field tag specified in MT 047

V68 Invalid combination of field tag - priority

V69 Missing subset sharing field tag 348 or invalid value for field tag 348

V70 Only category/message type/VAS code and branch codes can be combined

25 July 2014 187

FIN

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

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

V73 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

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.18 X Codes - FINCopy Message Validation (01 - 27) and

Delayed NAK Error Codes (30 - 99)
X01 Message type not allowed for this service

X02 FINCopy service identifier is not valid

X03 Either sender or receiver, or both, is/are not subscriber(s) of this service (for example, a
FINCopy service)

X04 Available

188 Error Codes

 Chapter 3 Alphanumeric Codes

X05 Currency code is mandatory and not present

X06 Value date is mandatory and not present

X07 Currency code is different from service currency code

X08 Value date is not within the range specified for the service

X09 FINCopy service is closed

X20 Sender is not a FINCopy server destination for the service requested

X21 Message type is not allowed in this service mode

X26 FINCopy service is already open

X27 FINCopy service is already closed

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

X30 Attempt to authorise message input reference of another FINCopy service

X31 Mismatch between FINCopy destination and the service code

X32 Refusal code is out of allowed range for FINCopy server (70-89)

X35 Authorised or refused message input reference is not found in the system

X36 Message is already aborted by the FINCopy server

X37 Message is already authorised by the FINCopy server

X38 Message is already aborted by the system

X39 Message is already bypassed by the system

X40 Central institution signature is required in MT 097 Authorisation

X41 Central institution signature is not allowed in MT 097 Authorisation

X46 Date field is not valid (for example, future start date or start time later than cut-off time)

25 July 2014 189

FIN

X47 System cannot generate report because more than 39960 messages are pending authorisation
(999 sections of 40 messages each)

X48 System is unable to process the request at this time

X99 System error (software or data inconsistency)

3.19 Y Codes - UNK Error Codes

Y01 Checksum failure

3.20 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

Z01 Invalid trailer sequence (or Training trailer used as LIVE message)

Z04 Checksum trailer error

Z05 Possible Duplicate Emission trailer error

Z06 Training-trailer error

Z98 Trailer not compatible with message type

190 Error Codes

 Chapter 4 FIN Errors

Chapter 4 FIN Errors

4.1 Introduction
This chapter describes the FIN Abort codes and Abort Diagnostic codes returned within a FIN Abort PDU
(Protocol Data Unit).

The abort codes indicate an aborted session during processing with the FIN Bridge.

The diagnostic codes provide additional information for the abort codes.

4.2 Abort Codes

4.2.1 Introduction
An abort code is composed of five alphanumeric characters with the structure <origin><layer><reason>
where:

<origin> is a one-character code that indicates who aborts the session:

'U' for the USER side

'S' for the SYS side

<layer> is a one-character code that indicates which layer triggers the abort:

'T' for the Transport layer (that is, SWIFTNet)

'A' for the Application layer

'S' for the Session layer

<reason> is a three-digit value that provides the reason of the abort

An abort code is sometimes accompanied by an "abort diagnostic", which is a string that provides more details
on the error.

4.2.2 Abort Codes

The FIN protocol abort codes and abort diagnostics are listed in the following table. All abort codes are
delivered within the Abort PDU, except when stated explicitly (for example, UT100):

Abort Abort Abort Description Abort diagnostic Description

origin layer reason

U T 100 USER session layer <Status> XML status message as

aborts the SWIFTNet returned by SWIFTNet.
session following a
SWIFTNet transmission
error. No ABORT PDU
could be transmitted to
SYS as the connection
was broken. The error
is local to the USER.

25 July 2014 191

FIN

Abort Abort Abort Description Abort diagnostic Description

origin layer reason

U/S A 100 USER or SYS [Diagnostic code] In case of "SA100"

application aborts the abort, a 5-character
SWIFTNet session. alphanumeric
diagnostic code may be
returned by SYS to the
USER.
In case of "UA100", no
diagnostic needs to be
returned by the USER.

U/S S 001 USER or SYS session <SwiftRequestRef> SWIFT Reference of

layer aborts the the received PDU as
SWIFTNet session included in the
following receipt from RequestDescriptor.
the peer session layer
of an invalid PDU type.

U/S S 002 USER or SYS session <SwiftRequestRef>/ Concatenation of

layer aborts the <RequestType>/ field SWIFT Reference of
SWIFTNet session name the received PDU +
following receipt from PDU type (for example
the peer session layer "OPEN") + invalid or
of an invalid PDU field missing field name (for
or a missing PDU field. example "VendorCode")
delimited by "/"
character.

U/S S 003 USER or SYS session <SwiftRequestRef>/ Concatenation of

layer aborts the <RequestType>/ state SWIFT Reference of
SWIFTNet session name the received PDU +
following receipt from PDU type (for example
the peer session layer "DATA") + invalid or
of an invalid PDU type missing state name (for
for the state. example "OPENING")
delimited by "/"
character.

U/S S 004 USER or SYS session Missing sequence Missing sequence

layer aborts the number number as 6 numeric
SWIFTNet session digits (for example
following a Sequence 000651).
gap timeout.

U/S S 005 USER or SYS session <SwiftRequestRef>/ Concatenation of the

layer aborts the duplicate sequence SWIFT Reference of
SWIFTNet session number the received PDU, with
following the receipt of the duplicate sequence
a PDU with a duplicate number (6 numeric
sequence number, from digits) delimited by "/"
the peer session layer. character.

U S 006 USER session layer <RequestType> Expected Request type

aborts the SWIFTNet (for example "OPEN-
session following a CONF").
timeout while waiting for
a request from the peer
session layer.

192 Error Codes

 Chapter 4 FIN Errors

Abort Abort Abort Description Abort diagnostic Description

origin layer reason

U S 007 USER session layer Not applicable

aborts the SWIFTNet
session following a Life
Signal Timeout.

S S 008 SYS session layer <SwiftRequestRef>/ Concatenation of

aborts the SWIFTNet duplicate sequence SWIFT Request
session following number Reference of the
receipt from the USER received PDU +
session layer of a duplicate sequence
different PDU with a number as 6 numeric
duplicate sequence digits delimited by "/"
number. character.

U/S S 100 USER or SYS session [Diagnostic code] In case of "SS100"

layer aborts the abort, a 5-character
SWIFTNet session for alphanumeric
any other reason (for diagnostic code may be
example internal returned by SYS to the
software error). USER.
In case of "US100"
abort, no diagnostic
needs to be returned by
the USER.

4.3 Diagnostic Codes for SS100

4.3.1 Introduction
This section provides details about the FIN Bridge abort diagnostic codes for SS100. When abort codes occur
for SS100, the FIN Bridge generates an abort diagnostic code. The abort diagnostic code is composed of five
alphanumeric characters.

4.3.2 Abort Diagnostic Codes

The abort diagnostic codes for the FIN Bridge Session layer are described in the following table:

Abort Description Source of error

diagnostic
code

FS012 SYS sent a Life Signal to the USER, but the Life User triggered problem
Signal Response was not received within the allowed
timeout.

FS013 Software error FIN System error

FS016 Indicates that an out-of-window message was User triggered problem

received by SYS. There is an upper limit to the
maximum number of outstanding messages that may
be buffered for sequencing in the session layer at
SYS. This is NOT the FIN window size.

FS019 Software error FIN System error

25 July 2014 193

FIN

Abort Description Source of error

diagnostic
code

FS022 Out of resources (session layer) in SYS. FIN System error

FS023 SYS received an unsolicited Life Signal Response User triggered problem
from the USER.

FS024 Destination in the logical terminal identifier (BIC-8) is User triggered problem
not configured in the SYS.

FS025 Software error FIN System error

FS032 BatchingTImeout in OPEN PDU from USER is User triggered problem

missing or invalid.

FS033 MaxBatchCount in OPEN PDU from USER is missing User triggered problem
or invalid

FS034 RequestHeader.RequestRef or RequestPayload.Data User triggered problem

in USER DATA PDU is missing or invalid, for example
incorrect, invalid, or missing count or length
indicators.

FS037 MaxBatchSize in OPEN PDU from USER is invalid User triggered problem

FS038 Invalid retry - retry expired Unknown

FS039 Software error FIN System error

FS040 Software error FIN System error

FS041 Software error FIN internal error

FS042 RequestControl.NRIndicator in USER DATA PDU User triggered problem

containing a LOGIN or SELECT is set to FALSE
(must be TRUE).

FS043 DigestAlgorithm element received in User triggered problem

SignatureList.Signature.Mainfest.Reference of USER
DATA PDU (not allowed)

FS044 Crypto element received in USER DATA PDU (not User triggered problem
allowed).

FS045 Software error FIN System error

FS046 RequestControl.NRIndicator in USER DATA PDU not User triggered problem

containing a LOGIN or SELECT is set to TRUE (must
be FALSE).

FS047 More than one (1) SignatureList element received in User triggered problem
USER DATA PDU (maximum of one allowed).

FS048 SignatureList.Signature.Manifest.Reference. User triggered problem

DigestRef in USER DATA PDU is invalid.

FS049 Multiple DigestRef elements of the same type (that is, User triggered problem
M, 1, 2, or B) received in the same
SignatureList.Signature.Manifest of USER DATA PDU
(maximum of one of a given type allowed).

194 Error Codes

 Chapter 4 FIN Errors

Abort Description Source of error

diagnostic
code

FS050 Number of SignatureList.Signature elements received User triggered problem

in USER DATA PDU is greater than total count
specified by 'snnnnn' prefixes in RequestPayload.

FS051 Number of SignatureList.Signature elements received User triggered problem

in USER DATA PDU is less than total count specified
by 'snnnnn' prefixes in RequestPayload.

FS052 DigestRef 1 or B appears before DigestRef M in a User triggered problem

SignatureList.Signature.Manifest received in this
USER DATA PDU (DigestRef M must appear before
DigestRef 1 or B).

FS053 Count of Signature elements specified in 'snnnnn' User triggered problem

prefix in RequestPayload received in USER DATA
PDU is invalid (must be zero or one).

FS054 SignatureList.Signature.Object.RND element is User triggered problem

mandatory in this USER DATA PDU, but is not
present.

FS055 SignatureList.Signature.Object.RND element is User triggered problem

present in this USER DATA PDU, but is not allowed.

FS056 Too many Reference elements received in a User triggered problem

SignatureList.Signature.Manifest of this USER DATA
PDU (maximum of two allowed).

FS057 SignatureList.Signature.Manifest.Reference. User triggered problem

DigestRef in USER DATA PDU is invalid.

FS058 Number of SignatureList.Signature elements received User triggered problem

in USER DATA PDU is incorrect (must be exactly
one).

FS059 SignatureList.Signature element received in USER User triggered problem

DATA PDU is invalid.

FS060 SignatureList.Signature.Manifest.Reference.DigestRef User triggered problem

in USER DATA PDU is invalid (must be M).

4.4 Diagnostic Codes for SA100

4.4.1 Introduction
When abort codes occur for SA100, the FIN Bridge generates an abort diagnostic code. The abort diagnostic
code is composed of five alphanumeric characters.

The diagnostic codes for SA100 are described in the following sections.

4.4.2 Application Layer (FIN): Abort Diagnostic Codes

4.4.2.1 Introduction
This section details the abort diagnostic codes for the FIN Application layer.

25 July 2014 195

FIN

4.4.2.2 Abort Diagnostic Codes

The abort diagnostic codes for the FIN Application layer are listed and described in the following table:

Abort diagnostic Description Source of error

code

FA011 RequestHeader.RequestRef[1] field in the User triggered problem

USER Session Data PDU (FIN message)
does not match the contents of the Basic
Header in block 1 of the FIN message.

FA055 SYS received an AP message, which is not User triggered problem

a valid AP PDU Type.

FA060 SignatureList.Signature.KeyInfo.CertPolicyId User triggered problem

received in USER DATA PDU is invalid.

FA10x Signature verification failure on PKI digital Unknown error

signature on USER DATA request.

4.4.3 Application Layer - Application Control: Abort Diagnostic Codes

4.4.3.1 Introduction
This section details the abort diagnostic codes for the Application Control Application layer.

4.4.3.2 Abort Diagnostic Codes

The abort diagnostic codes for the Application Control Application layer are listed and described in the
following table:

Abort diagnostic Description Source of error

code

FP013 RequestHeader.RequestRef[1] field in the User triggered problem

USER Session Data PDU (Application
Control message) does not match the
contents of the Basic Header in block 1 of
the FIN message.

FP056 SYS received an Application Control User triggered problem

message, which is not a valid Application
Control PDU Type.

FP057 SYS received a SELECT with a logical User triggered problem

terminal identifier in Block 1, which does not
match the logical terminal identifier in the
Session OPEN request PDU.

FP058 SYS received a SELECT for an application User triggered problem

other than FIN ('F').

FP059 Field tag 501 is present in SELECT request User triggered problem
received in USER DATA PDU, but is not
allowed (beginning with protocol version 03,
field tag 501 is not allowed in SELECT).

196 Error Codes

 Chapter 4 FIN Errors

Abort diagnostic Description Source of error

code

FP060 SignatureList.Signature.Manifest.Reference. User triggered problem

DigestValue for SELECT request received in
USER DATA PDU is invalid.

FP061 SignatureList.Signature.KeyInfo.CertPolicyId User triggered problem

for SELECT request received in USER
DATA PDU is invalid.

FP062 AuthorisationContext DN does not match User triggered problem

Sign DN for USER DATA PDU containing
SELECT

FP10x Signature verification failure on PKI digital Unknown

signature on SELECT request received in
USER DATA PDU.

4.4.4 Application Layer - Logical Terminal Control: Abort Diagnostic

Codes
4.4.4.1 Introduction
This section details the abort diagnostic codes for the Logical Terminal Control Application layer.

4.4.4.2 Abort Diagnostic Codes

The abort diagnostic codes for the Logical Terminal Control Application layer are listed and described in the
following table:

Abort diagnostic Description Source of error

code

FT002 SYS received a LOGIN with a logical User triggered problem

terminal identifier in Block 1, which does not
match the logical terminal identifier in the
Session OPEN request PDU.

FT010 SYS received an ABORT logical terminal User triggered problem

message which is not a valid input Logical
Terminal Control PDU Type.

FT012 RequestHeader.RequestRef[1] field in the User triggered problem

User Session Data PDU (input Logical
Terminal Control message) does not match
the contents of the Basic Header in block 1
of the FIN message.

FT017 Software error FIN System error

FT018 SYS received an input message with a User triggered problem

message length greater than the maximum
size allowed.

FT019 Software error FIN System error

FT021 SYS received a message with Invalid FIN System error

Application in the Basic Header

25 July 2014 197

FIN

Abort diagnostic Description Source of error

code

FT052 AuthorisationContext DN does not match User triggered problem

Sign DN for USER DATA PDU containing
LOGIN request.

FT053 Field tag 501 is present in LOGIN request User triggered problem
received in USER DATA PDU, but is not
allowed (beginning with protocol version 03,
field tag 501 is not allowed in LOGIN).

FT054 SignatureList.Signature.Manifest.Reference. User triggered problem

DigestValue for LOGIN request received in
USER DATA PDU is invalid.

FT055 SignatureList.Signature.KeyInfo.CertPolicyId User triggered problem

for LOGIN request received in USER DATA
PDU is invalid.

FT099 Software error FIN System error

FT10x Verification failure on PKI digital signature Unknown error

on LOGIN request received in USER DATA
PDU.

4.4.5 Other Layers (Internal to FIN): Abort Diagnostic Codes

4.4.5.1 Introduction
This section lists and describes the abort diagnostic codes that occur in other layers that are internal to FIN.

4.4.5.2 Abort Diagnostic Codes

The following table lists and describes the abort diagnostic codes that occur in other layers that are internal to
FIN:

Abort diagnostic Diagnostic description Source of error

code

FInnn Software/Protocol error FIN system error

FUnnn Software/Protocol error FIN system error

RAxxx Software/Protocol error at FIN Application The 'xxx' gives further details of the error.
layer

RIxxx Software/Protocol error User triggered problem

RPxxx Software/Protocol error at FIN Application The 'xxx' gives further details of the error.
Control layer

RTxxx Software/Protocol error at FIN Logical The 'xxx' gives further details of the error.
Terminal Control layer

RUxxx Software/Protocol error FIN system error

198 Error Codes

 Legal Notices

Legal Notices
Copyright

SWIFT © 2014. All rights reserved.

Restricted Distribution

Do not distribute this publication outside your organisation unless your subscription or order expressly grants you that right,
in which case ensure you comply with any other applicable conditions.

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 and binding version.

Trademarks

SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: the SWIFT logo, SWIFT,
SWIFTNet, SWIFTReady, Accord, Sibos, 3SKey, Innotribe, the Standards Forum logo, MyStandards, and SWIFT Institute.
Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their
respective owners.

25 July 2014 199