Swift Errors Code
Swift Errors Code
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.
20 July 2023
Table of Contents
Preface......................................................................................................................................................4
Introduction..............................................................................................................................................6
Numeric Codes........................................................................................................................................ 7
General....................................................................................................................................................7
Logout/Quit Acknowledgement Errors..................................................................................................... 7
Re-Login Request Errors.........................................................................................................................8
Retrieval Errors........................................................................................................................................9
Message Status.....................................................................................................................................13
Abort Reasons.......................................................................................................................................15
FIN and General Purpose Application Session Termination..................................................................17
Report Errors......................................................................................................................................... 19
Bulk Retrieval Errors Codes.................................................................................................................. 20
Alphanumeric Codes.............................................................................................................................22
General..................................................................................................................................................22
A Codes - Re-Select Error Codes..........................................................................................................22
B Codes - Copy Service Errors..............................................................................................................22
C, D, and E Codes - Conditional Semantic Error Codes....................................................................... 23
G Codes - Service-Specific Validation................................................................................................. 206
H Codes - Basic Header and Application Header Validation............................................................... 209
K Codes - Codes Validation in Generic Fields.....................................................................................212
L Codes - LOGIN Errors...................................................................................................................... 212
M Codes - Message Errors..................................................................................................................213
N Codes - Market Infrastructure Resiliency Service (MIRS) Errors.....................................................215
P Codes - Protocol Errors....................................................................................................................219
R Codes - Re-Login/Re-Select Errors................................................................................................. 221
S Codes - System-Initiated Abort Errors..............................................................................................221
S Codes - Select Errors....................................................................................................................... 223
T Codes - Text Validation.....................................................................................................................225
U Codes - User Header Validation.......................................................................................................247
V Codes - System Message Errors and Message Block Format Errors..............................................249
X Codes - FINCopy Message Validation (01 - 27) and Delayed NAK Error Codes (30 - 99).............. 255
20 July 2023 2
FIN Table of Contents
Error Codes
20 July 2023 3
FIN Preface
Error Codes
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.
Reading conventions
The following abbreviations are used in this document:
Abbreviation Term
Significant changes
The following table lists significant changes to the content of FIN Error Codes since the 22 July 2022
edition. This table does not include editorial changes that Swift makes to improve the usability and
comprehension of the document.
20 July 2023 4
FIN Preface
Error Codes
Update text of error codes C03, C05, C17, C19, C20, C Error Codes on page 23
C21, C71, C72, D16, D26, D27, D30, D32, D34, D43,
D Error Codes on page 62
D44, D46, D48, D49, D50, D51, E20, E55, E58, E67,
E68, E70, E76, E77, E78, E83, E94, T14, T22, T36, T47, E Error Codes on page 113
and T73
T Codes - Text Validation on page 225
20 July 2023 5
FIN Introduction
Error Codes
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. Numeric Codes on page 7,
contains all the errors that are represented by two- or three-digit codes. Error codes in Alphanumeric
Codes on page 22, 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.
20 July 2023 6
FIN Numeric Codes
Error Codes
Numeric Codes
General
Numeric codes are used for:
• Logout/Quit acknowledgement errors (field 401)
• Re-login request errors (fields 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)
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.
20 July 2023 7
FIN Numeric Codes
Error Codes
010
Re-login request received while logical terminal is active on the Logical Terminal Control association.
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.
20 July 2023 8
FIN Numeric Codes
Error Codes
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.
025
Re-login request, a new login request is sent to login a logical terminal while same logical terminal has
active login session.
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.
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.
20 July 2023 9
FIN Numeric Codes
Error Codes
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 identifier 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).
20 July 2023 10
FIN Numeric Codes
Error Codes
016
Branch identifier is not "XXX".
018
Invalid destination for report (field 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).
035
Text read error from archival (system).
20 July 2023 11
FIN Numeric Codes
Error Codes
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 field
252 (message input reference range) or field 254 (message output reference range).
044
Illogical use of field 152 (first input sequence number) or field 153 (first output sequence number). 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.
20 July 2023 12
FIN Numeric Codes
Error Codes
049
Retrieval period specified exceeds 10 days.
099
Retrieval report problem. Contact your Customer Support Centre.
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.
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.
20 July 2023 13
FIN Numeric Codes
Error Codes
29
Message held for approval prior to bypass mode and aborted.
31
Authorised by the copy service or the subscriber to a Swift service and delivered.
32
Not authorised by the copy service or the subscriber to a Swift service and aborted by the system.
33
Copy message is aborted and not delivered to the copy service.
34
Authorised by the copy service or the subscriber to a Swift service but aborted by the system.
35
Not yet authorised/refused by the copy service or the subscriber to a Swift service.
37
Authorised by the copy service or the subscriber to a Swift service but no delivery attempted.
38
Authorised by the copy service or the subscriber to a Swift service 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.
20 July 2023 14
FIN Numeric Codes
Error Codes
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.
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.
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.
20 July 2023 15
FIN Numeric Codes
Error Codes
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.
29
Message held for approval prior to bypass mode and aborted.
20 July 2023 16
FIN Numeric Codes
Error Codes
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.
Transaction Manager (VAS code TMR) uses codes in this range to indicate error reasons resulting from
Transaction Manager processing. See the Transaction Manager Operations Guide for a description of the
error codes (this document will be available at a later stage).
Swift screening services can use the following codes:
• Code S1 indicates that the message has been aborted on request of the subscribing user.
• Code S2 indicates that the message has been automatically aborted by the screening service as per
the configuration created by the user.
• Code S3 indicates that the message has been automatically aborted by the screening service
because of a business time-out.
• Code S4 indicates that the message has been aborted by more than one service.
Please consult the service specific documentation to confirm the full list that applies to each individual
screening service.
Note All undefined numeric codes are reserved for use by FIN.
000
Normal termination.
001
Application Control or Logical Terminal Control has aborted.
20 July 2023 17
FIN Numeric Codes
Error Codes
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.
016
Too many messages output in a session. Maximum is 500000.
20 July 2023 18
FIN Numeric Codes
Error Codes
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.
055
• FIN session has aborted because RMA validation is not available.
• FIN is unable to access the authorisation record, the FIN session has aborted.
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.
20 July 2023 19
FIN Numeric Codes
Error Codes
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 identifier is not "XXX".
099
System internal problems, contact your Customer Support Centre.
03
Retrieval only partially complete.
20 July 2023 20
FIN Numeric Codes
Error Codes
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 due to system recovery.
17
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 primary BIC).
20 July 2023 21
FIN Alphanumeric Codes
Error Codes
Alphanumeric Codes
General
This chapter contains the codes for the following error types:
Note Similar error codes are used by other Swift services, such as 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.
A56
Re-select NAK error code (in field 503) to indicate that the logical terminal is not in a recoverable state.
The FIN interface should execute a fresh select procedure.
B01
Message contains value-added service server id but sender or receiver, or both, are not members of the
service.
20 July 2023 22
FIN Alphanumeric Codes
Error Codes
B02
Available.
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
A system error has occurred. Contact your local Customer Support Centre for further information.
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.
C02
The currency code must be the same for all occurrences of indicated fields in the entire message. See
the Standards MT Message Reference Guides for the indicated fields in each message.
Examples:
20 July 2023 23
FIN Alphanumeric Codes
Error Codes
The following list (not exhaustive) explains how error code C02 is applied in specific message types:
• MT 321. The currency code in the amount fields (fields 19A in sequence B) must be the same for all
occurrences of this field in the message.
• MTs 320 and 330. The currency code in the amount fields, except for fields 33B and 33E in sequence
G, must be the same for all occurrences of these fields in the message.
• MT 350. The currency code in the amount fields 32B and 34B in sequence B must be the same.
Special Cases:
The following MTs (not an exhaustive list) 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 that contain both the amount and the
currency code components.
Examples:
• field 32A in MTs 103, 103 REMIT, and 103 STP
• field 32B in MTs 104 and 107 (sequences B and C), 760, 765, 767, and 786
This check also applies, among others, to:
• field 19 in MTs 102, 102 STP, 104, 107, 201, 203, and 204 where the corresponding currency is the
one used in field 32B or 34A
• field 32H and 33E in MT 300 sequence F
• field 33B in MTs 103, 103 REMIT, 103 STP, MTs 104 and 107 (sequence B), and 767
• field 33Z in MT 306 where the corresponding currency is the one used in field 34B in subsequence B1.
This check only applies if field 34B in subsequence B1 is present.
• 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
20 July 2023 24
FIN Alphanumeric Codes
Error Codes
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
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 connected BICs, non-connected BICs, primary BICs, Synonyms, Live
destinations and Test & Training destinations.
57A B
103 52A
53A
54A The same validation applies to the MT 103,
55A MT 103 REMIT, and the MT 103 STP
56A
57A
104 52A A, B
Note For sequence C, see also
53A C
error code C96.
57A B
107 52A A, B
53A C
57A B
110 52A
53A
54A
20 July 2023 25
FIN Alphanumeric Codes
Error Codes
20 July 2023 26
FIN Alphanumeric Codes
Error Codes
20 July 2023 27
FIN Alphanumeric Codes
Error Codes
20 July 2023 28
FIN Alphanumeric Codes
Error Codes
20 July 2023 29
FIN Alphanumeric Codes
Error Codes
20 July 2023 30
FIN Alphanumeric Codes
Error Codes
C06
MT 210
Either field 50a or field 52a, but not both, must be present in a repetitive sequence.
MT 910
Either field 50a or field 52a must be present.
C07
MT 516
Either field 35A or 35N must be present.
20 July 2023 31
FIN Alphanumeric Codes
Error Codes
C08
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.
MT Field Sequence(s)
101 32B B
102 32B B
32A C
102 STP 32B B
32A C
103 32A
103 REMIT 32A
103 STP 32A
200 32A
201 32B
202 32A
202 COV 32A A
203 32B
205 32A
205 COV 32A A
210 32B
300 32E A
32B B1
33B B2
71F C
32B D
32H F
33E F
304 32E A
32B B1
33B B2
32G D
34B D
32G E
305 32B A
32E A
33B A
34a A
306 34B B1
20 July 2023 32
FIN Alphanumeric Codes
Error Codes
MT Field Sequence(s)
32B D
33B D
33E E
32Q G
32E H
71F K
32H L
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
MT 707
Either field 32B or field 33B may be present, but not both.
MT 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.
MT 767
In sequence B, either field 32B or field 33B, but not both, may be present.
In sequence C, either field 32B or field 33B, but not both, may be present.
20 July 2023 33
FIN Alphanumeric Codes
Error Codes
C13
MT 750
If any of fields 33B, 71D, or 73A is present, field 34B must be present.
MT 765
If field 49A is INCP, then field 77 must be present, otherwise field 77 is not allowed.
C14
MT 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, 39C, 72Z, or 77 must be present.
C16
MT 760
In sequence B, if field 23F is absent, then fields 78, 26E, and 31S are not allowed.
In sequence C, if field 23F is absent, then fields 78, 26E, and 31S are not allowed.
C17
MT 734
If field 73A is present, field 33a must be present.
MT 760
In sequence A, if field 22A is ISSU then, in sequence B, field 50 must be present.
20 July 2023 34
FIN Alphanumeric Codes
Error Codes
MT 765
If field 22G is PAYM, then fields 31E and 31R are not allowed.
If field 22G is ... Then fields 31E and 31R are ...
PAYM Not allowed
Any other value Optional
C18
MT 752
If fields 32B and 71D are present, field 33a must be present.
MT 760
If in sequence A field 22A is ISSU and in sequence B field 22D is STBY, then field 49 must be present in
sequence B.
In sequence A And if sequence B, field 22D is ... Then in sequence B, field 49 is ...
if field 22A is ...
ISSU STBY Mandatory
Any other value Not applicable Optional
Sequence B
If field 22D is ... Then field 49 is ...
DGAR Not allowed
Any other value Optional
C19
MT 754
Either field 72Z or field 77, but not both, may be present.
MT 760
In sequence A, if field 22A is ISCO or ICCO then, in sequence B, fields 48D, 24E, and 24G are not
allowed.
In sequence A, if field 22A is ISCO or ICCO, then sequence C must be present, otherwise sequence C is
not allowed.
20 July 2023 35
FIN Alphanumeric Codes
Error Codes
In sequence A, if field 22A is ISCA or ICCA, then in sequence B fields 24E and 24G are not allowed.
C20
MT 304
In sequence D, field 30F may only be present if field 34B is present.
MT 601
Field 53a may be present only if field 34P is present.
MT 760
In sequence B, if field 49 is CONFIRM or field 49 is MAY ADD, then field 58a must be present, otherwise
field 58a is not allowed.
Sequence B
If field 49 is ... Then field 58a is ...
CONFIRM or MAY ADD Mandatory
Any other value Not allowed
MT 767
In sequence A, if field 22A is ACNA or ADVA, then field 23 may be present, otherwise field 23 is not
allowed.
Sequence A
If field 22A is ... Then field 23 is ...
ACNA or ADVA Optional
Any other value Not allowed
20 July 2023 36
FIN Alphanumeric Codes
Error Codes
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.
MT 760
In sequence B, if field 22D is DGAR, then field 41a is not allowed.
Sequence B
If field 22D is ... Then field 41a is ...
DGAR Not allowed
Any other value Optional
In sequence C, if field 22D is DGAR or DEPU, then field 41a is not allowed.
Sequence C
If field 22D is ... Then field 41a is ...
DGAR or DEPU Not allowed
Any other value 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.
20 July 2023 37
FIN Alphanumeric Codes
Error Codes
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.
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 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.
20 July 2023 38
FIN Alphanumeric Codes
Error Codes
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 also error code E87.
• MTs 545 and 547, see also error code E92.
MT 586
A value date must only be provided for cash/securities split settlement. That is, in any occurrence of
subsequence B6b, if value date field :98a::VALU is present, then in subsequence B6 field :22F::STCO//
SPST must be present, and settlement amount field :19A::SETT must be present in the same
subsequence B6b.
C29
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift Go), and MT 199 (Universal
Confirmations)
In field 79, if line 5 is present, then the currency code in line 5, subfield 3 and the currency code in field
79, line 4 must be the same.
MT 586
In field 23G, if subfield 1 is RMDR, then subfield 2 must be PORT.
C30
MT 707
At least one of the fields 23S, 31D, 32B, 33B, 39A, 39C, 40A, 40E, 41A, 41D, 42A, 42C, 42D, 42M, 42P,
43P, 43T, 44A, 44B, 44C, 44D, 44E, 44F, 45B, 46B, 47B, 48, 49, 49M, 49N, 50, 53A, 53D, 57A, 57B, 57D,
58A, 58D, 59, 71D, 71N, 72Z, or 78 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.
20 July 2023 39
FIN Alphanumeric Codes
Error Codes
Note Swift does not validate the relationship between the copied fields and the original message;
hence any valid fields are accepted.
C32
MTs 300, 304, 305, 306, 320, 330, 340, 341, 350, 360, 361, 362, 364, 365, 600, 601, and 620
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
MT 760
In sequence C, if field 22Y is present, then field 22K must be present.
Sequence C
If field 22Y is ... Then field 22K is ...
Present Mandatory
Not present Optional
C34
MT 769
Either field 33B or 39C, but not both, must be present.
C35
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift Go), and MT 299 (Swift gpi -
gCOV)
The presence of line 3 subfield 4 (Clearing System) depends on line 2 subfield 1 (Status Code) and line 2
subfield 2 (Reason Code) and line 3 subfield 3 (Settlement Method) as follows:
In field 79
If line 2 subfield 1 is ... If line 2 subfield 2 is ... And line 3 subfield 3 is ... Then line 3 subfield 4
is ...
ACSP G000 CLRG Optional
ACSP G001 CLRG Optional
ACSP G000 Any other value Not allowed
ACSP G001 Any other value Not allowed
RETN Not applicable CLRG Optional
RETN Not applicable Any other value Not allowed
20 July 2023 40
FIN Alphanumeric Codes
Error Codes
In field 79
If line 2 subfield 1 is ... If line 2 subfield 2 is ... And line 3 subfield 3 is ... Then line 3 subfield 4
is ...
Any other value Not applicable Not applicable Not allowed
In field 79
If line 2 subfield 1 is ... If line 2 subfield 2 is ... And line 3 subfield 3 is ... Then line 3 subfield 4
is ...
ACSP G001 CLRG Optional
ACSP Any other value Any other value Not allowed
Any other value Not applicable Not applicable Not allowed
In field 79
If line 2 subfield 1 is ... And line 2 subfield 2 is ... And line 3 subfield 3 is ... Then line 3 subfield 4
is ...
ACSP G000 CLRG Optional
ACSP G001 CLRG Optional
ACSP G000 Any other value Not allowed
ACSP G001 Any other value Not allowed
ACSP Any other value Not allowed Not allowed
C36
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), and MT 199 (Swift Go)
If line 4 subfield 2 (Details of Charges) is OUR, then line 6 is not allowed.
If line 4 subfield 2 (Details of Charges) equals BEN, then at least one occurrence of line 6 must be
present.
In field 79
If line 4 subfield 2 is ... Then line 6 is ...
OUR Not allowed
BEN Mandatory
Any other value Optional
20 July 2023 41
FIN Alphanumeric Codes
Error Codes
In field 79
If line 4 subfield 2 is ... Then line 6 is ...
OUR Not allowed
Any other value Optional
C37
MT 199 (Universal Confirmations)
If line 2 subfields 1 and 2 (Status Code/Reason Code) are ACSP/G001, then line 4 subfield 2 (Charge
Code) may be present, otherwise line 4 subfield 2 is not allowed.
In field 79
If line 2 subfield 1 is ... And line 2 subfield 2 is ... Then line 4 subfield 2 must be ...
ACSP G001 Optional
ACSP Any other value Not allowed
Any other value Any other value Not allowed
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), and MT 199 (Swift Go). This validation only
applies to user-to-Tracker (U2T).
If line 2 subfields 1 and 2 (Status Code/Reason Code) are ACSP/G000 or ACSP/G001, then line 4
subfield 2 (Charge Code) is mandatory, otherwise line 4 subfield 2 is not allowed.
In field 79
If line 2 subfield 1 is ... And line 2 subfield 2 is ... Then line 4 subfield 2 must be ...
ACSP G000, G001 Mandatory
ACSP Any other value Not allowed
Any other value Any other value Not allowed
C38
MT 306
In sequence I, if field 12G contains the code BERM, then field 30T and field 22Y must be present.
C39
MT 306
In sequence I, if field 12G contains the code AMER, then field 30Y must be present.
20 July 2023 42
FIN Alphanumeric Codes
Error Codes
C40
MT 920
The currency code must be the same for each occurrence of field 34F within each repetitive sequence.
C41
MT 306
The presence of sequence J, subsequence J1, subsequence J2, and field 14B in sequence J depends on
the value of field 12F in sequence A, as follows:
C42
Available.
C43
MT 103 (Swift Go)
In field 32A the currency code amount must not exceed the following limits.
In field 32A the currency code amount must not exceed the following limits
Currency code Currency code limit
EUR 10,000
GBP 10,000
USD 10,000
C44
Available.
20 July 2023 43
FIN Alphanumeric Codes
Error Codes
C45
MT 199 (Swift gpi - g4CIT (007))
Subfield 1 (Remittance Information) of lines 16 (REM1), 17 (REM2), 18 (REM3), and 19 (REM4) must be
in numerical order if present.
Note The line numbers are based on a count of all fields. Optional fields are not excluded in the
numbering.
C46
Available.
C47
Available.
C48
Available.
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
Available.
20 July 2023 44
FIN Alphanumeric Codes
Error Codes
C52
MT 361
In sequence A, the presence of field 32B depends on field 23A, as follows:
Sequence A
If field 23A is ... Then field 32B is ...
CORRBUYER Not allowed
CORRSELLER Not allowed
VOLABUYER Not allowed
VOLASELLER Not allowed
Any other value Mandatory
C53
Available.
C54
Available.
C55
Available.
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
Sequence B
If field 17Z is ... Then field 22Q is ...
Y Mandatory
N Optional
20 July 2023 45
FIN Alphanumeric Codes
Error Codes
Sequence B
If field 17Z is ... Then field 22Q is ...
Not present Optional
MT 306
In sequence M, the presence of field 22Q depends on field 17Z as follows:
Sequence M
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
N Optional
Not present Optional
Sequence D
If field 17Z is ... Then field 22Q is ...
Y Mandatory
N Optional
Not present Optional
MT 360
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
20 July 2023 46
FIN Alphanumeric Codes
Error Codes
MT 361
In sequence P, the presence of field 22Q depends on field 17Z, as follows:
Sequence P
If field 17Z is ... Then field 22Q is ...
Y Mandatory
N Optional
Not present Optional
C57
Available.
C58
Available.
C59
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 :
Then field : And field : And field : And field : And field :
22H::TLDE is ...
98A::INTR is ... 19A::SETT is ... 19A::RODI is ... 19A::CINT is ... 19A::NINT 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
C60
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
20 July 2023 47
FIN Alphanumeric Codes
Error Codes
C61
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
C62
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 321
In sequence A, if field 99B is present, then all qualifiers must be present.
C64
Available.
C65
MT 567
If the message is a cancellation request status (:23G:CAST), then, in every occurrence of subsequence
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 subsequence 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
subsequence A2 Status, an event status (:25D::EPRC...) must be reported.
20 July 2023 48
FIN Alphanumeric Codes
Error Codes
C66
Available.
C67
MT 516
In sequence A, either field 83C or 87a but not both, may be present.
C68
MTs 202 COV and 205 COV
In sequence B, if field 56a is present, then field 57a must also be present.
C69
MT 507
In each occurrence of sequence B, if present, if subsequence B1 is present, the presence of
subsequences B1a and B1b depends on the value of field :22H::COLL in sequence B as follows:
Note Error code C70 takes precedence over error code C69.
20 July 2023 49
FIN Alphanumeric Codes
Error Codes
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:
(1) See also 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.
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.
20 July 2023 50
FIN Alphanumeric Codes
Error Codes
MT 537
In each occurrence of subsequence B2b, field :36B::PSTA cannot appear more than twice (maximum 2
occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other
occurrence must have Quantity Type Code AMOR.
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.
20 July 2023 51
FIN Alphanumeric Codes
Error Codes
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.
Note When used with format option F, field 93a qualifier ELIG cannot be repeated.
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.
Note When used with format option F, field 93a qualifier ELIG cannot be repeated.
MT 566
In sequence B, field :93B::ELIG cannot appear more than twice (maximum 2 occurrences). When
repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have
Quantity Type Code AMOR.
Note When used with format option F, field 93a qualifier ELIG cannot be repeated.
MT 567
In sequence B, field :36a::STAQ 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.
20 July 2023 52
FIN Alphanumeric Codes
Error Codes
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.
Note When used with format option F, field 93a qualifier ELIG cannot be repeated.
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.
MT 564
In each occurrence of subsequence E1, field :36a::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.
MT 565
In sequence D, field :36a::QINS 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.
20 July 2023 53
FIN Alphanumeric Codes
Error Codes
MT 566
In each occurrence of subsequence D1, field :36a::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.
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.
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.
20 July 2023 54
FIN Alphanumeric Codes
Error Codes
• 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
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.
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.
20 July 2023 55
FIN Alphanumeric Codes
Error Codes
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.
MT 760
In sequence B, if field 57() is present, then field 56() must be present.
Sequence B
If field 57() is ... Then field 56() is ...
Present Mandatory
Not present Optional
MT 785
If field 57() is present, then field 56() must 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
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
Available.
C85
Available.
20 July 2023 56
FIN Alphanumeric Codes
Error Codes
C86
Available.
C87
MT 300
In sequence A, if field 17F is present and contains "Y", then field 17O must also be present, otherwise
field 17O is not allowed.
Sequence A
If field 17F is ... Then field 17O is ...
Y Mandatory
N Not allowed
Not present Not allowed
In sequence A, if field 17O is present and contains "Y", then fields 32E, 30U, and at least one occurrence
of 14S must also be present, field 26K is optional, and field 21A is not allowed. If 17O is present and
contains "N", then field 21A must be present and fields 32E, 30U, 14S, and 26K are not allowed.
If field 17O is not present, then fields 32E, 30U, 14S, 26K, and 21A are not allowed.
Sequence A
If field 17O is ... Then fields 32E, 30U, and And field 21A is ... And field 26K is ...
14S are ...
Y Mandatory Not allowed Optional
N Not allowed Mandatory Not allowed
Not present Not allowed Not allowed Not allowed
In sequence B, field 35C may only be present if field 17F in sequence A is present and contains "Y" and
the currency in either field 32B in subsequence B1 or field 33B in subsequence B2 contains "XXX".
20 July 2023 57
FIN Alphanumeric Codes
Error Codes
MT 304
In sequence A, if field 94A contains ANDF, then fields 32E, 14S, 26K, and 21A are optional and field 30U
is mandatory, otherwise fields 32E, 14S, 26K, 21A, and 30U are not allowed.
Sequence A
If field 94A is ... Then fields 32E, 14S, 26K, and 21A And field 30U is...
are ...
ANDF Optional Mandatory
AFWD, ASET Not allowed Not allowed
In sequence B, field 35C may only be present if field 94A in sequence A contains "ANDF" and the
currency in either field 32B in subsequence B1 or field 33B in subsequence B2 contains "XXX".
MT 305
In sequence A, if field 17F is present and contains "Y", then field 32E and at least one occurrence of field
14S is mandatory, and field 26K is optional, otherwise fields 32E and 26K are not allowed and field 14S is
optional.
Sequence A
If field 17F is ... Then field 32E is... And field 14S is... And field 26K is...
Y Mandatory Mandatory Optional
N Not allowed Optional Not allowed
Not present Not allowed Optional Not allowed
In sequence A, field 35C may only be present if field 17F in sequence A is present and contains "Y" and
the currency in either field 32B or field 33B in sequence A contains "XXX".
Sequence A
If field 17F is ... And if subfield 1 of field And if subfield 1 of field Then field 35C is ...
32B is ... 33B is ...
Not present Any value Any value Not allowed
N Any value Any value Not allowed
Y Not XXX Not XXX Not allowed
Y XXX Any value Optional
Y Any value XXX Optional
20 July 2023 58
FIN Alphanumeric Codes
Error Codes
MT 306
In sequence H field 35C may only be present if sequence D is present and if the currency in either field
32B or field 33B in sequence D contains "XXX".
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, and 608
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.
MT 620
A maximum of 6 decimal digits is permitted in the subfields Amount of sequence B: field 32F, index 18,
field 32R, index 19, field 34J, index 21, and of sequence G: field 33J, index 52, and field 33J, index 54.
C90
MTs 700, 710, 720, and 740
If field 42a is used, the only combinations that are allowed are field 42M (on its own) or field 42P (on its
own) or both fields 42C and 42 (A or D).
C91
MT 608
Subfield 4 of field 61 must not be present.
C92
Available.
20 July 2023 59
FIN Alphanumeric Codes
Error Codes
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.
Note This error code takes precedence over error codes C75 and C96.
C95
Available.
C96
MT 104
If field 23E is present in sequence A and contains RFDD, then:
• field 21R in sequence A is optional
• fields 21E, 50a (option A or K), 52a, 71F and 71G must not be present in sequence B
• sequence C must not be present
Otherwise, that is in sequence A, field 23E does not contain RFDD or field 23E is not present:
• in sequence A, field 21R must not be present
• and in sequence B, the fields 21E, 50a (option A or K), 52a, 71F and 71G are optional
• and sequence C must be present
20 July 2023 60
FIN Alphanumeric Codes
Error Codes
Sequence A Sequence B
and fields 21E, 50a
If field 23E is ... Then field 21R is ... And sequence C is ...
(option A or K), 52a, 71F,
and 71G are ...
Present and = RFDD Optional Not allowed Not allowed
Present and not = RFDD Not allowed Optional Mandatory
Not present Not allowed Optional Mandatory
C97
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.
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.
C98
MTs 300, 304, 305, 306, 320, 330, 340, 341, 360, 361, 600, 601, 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:
20 July 2023 61
FIN Alphanumeric Codes
Error Codes
C99
MT 504
Sequence E is mandatory when in any occurrence of sequence C, subsequence C2 is present and
subsequence C2a is not present.
MT 505
Sequence D is mandatory when in any occurrence of sequence B, subsequence B2 is present and
subsequence B2a is not present.
D Error Codes
D00
Not used.
D01
Available.
20 July 2023 62
FIN Alphanumeric Codes
Error Codes
D02
MT 304
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, CAMN Mandatory
CANC, CCAN Mandatory
CNEW, NEWT Optional
DUPL Optional
Sequence A
If field 22A is ... Then field 21 is ...
AMND Mandatory
CANC Mandatory
DUPL Optional
NEWT Optional
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
20 July 2023 63
FIN Alphanumeric Codes
Error Codes
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 ...
AFWD Mandatory Mandatory
ANDF Mandatory Not allowed
ASET Not allowed Not allowed
MT 535
If field :94a:: is present in sequence B, then fields :93a::AGGR and :94a::SAFE are not allowed in any
occurrence of subsequence B1b.
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
20 July 2023 64
FIN Alphanumeric Codes
Error Codes
MT 535
If field :93a::AGGR is present in subsequence B1b, then field :94a::SAFE must be present in the same
subsequence B1b.
D05
MT 535
In each occurrence of subsequence B1b, if field :93a::AVAI or/and :93a::NAVL is/are present, then field :
93a::AGGR must be present in the same occurrence of subsequence B1b.
D06
MTs 700, 705, 707, 710, and 720
Either field 44C or 44D but not both, may be present.
MT 707
In field 45B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 46B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 47B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 49M, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 49N, if code REPALL is used it must be used only once in the field, and no other code must be
used.
MT 708
In field 45B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 46B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 47B, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 49M, if code REPALL is used it must be used only once in the field, and no other code must be
used.
In field 49N, if code REPALL is used it must be used only once in the field, and no other code must be
used.
20 July 2023 65
FIN Alphanumeric Codes
Error Codes
D07
MT 600
The use of FOZ, GOZ, and TOZ in subfield Unit in sequences B and C, field 32F depends on the
commodity in subfield 4 (Type) in sequence A, field 26C, as follows:
MT 601
The use of FOZ, GOZ, and TOZ in subfield Unit in sequence A, field 32F depends on the commodity in
subfield 4 (Type) in sequence A, field 26C, as follows:
Sequence A
If subfield 4 (Type) in field 26C is ... Then Unit in field 32F must be ...
GOLD Neither GOZ nor TOZ
PALL Neither FOZ nor TOZ
PLAT Neither FOZ nor TOZ
SILV Neither FOZ nor TOZ
If subfield 4 (Type) in field 26C is ... Then Unit in field 32F must be ...
GOLD Neither GOZ nor TOZ
PALL Neither FOZ nor TOZ
PLAT Neither FOZ nor TOZ
SILV Neither FOZ nor TOZ
MT 608
The use of FOZ, GOZ, and TOZ in subfield Unit in fields 60a, 62a, 64, and 65 depends on the commodity
in subfield 4 (Type) in field 26C, as follows:
If subfield 4 (Type) in field 26C is ... Then Unit in field 60a, 62a, 64 (if present), 65 (if
present) must be ...
GOLD Neither GOZ nor TOZ
PALL Neither FOZ nor TOZ
PLAT Neither FOZ nor TOZ
20 July 2023 66
FIN Alphanumeric Codes
Error Codes
If subfield 4 (Type) in field 26C is ... Then Unit in field 60a, 62a, 64 (if present), 65 (if
present) must be ...
SILV Neither FOZ nor TOZ
Note See also error code C80 for additional checks. Error code D07 takes precedence over error
code C80.
MT 620
The use of FOZ, GOZ, and TOZ in subfield Unit in sequence B, fields 32F, 32R, and 34J and in
subsequences G1 and G2, field 33J depends on the commodity in subfield 4 (Type) in sequence A, field
26C, as follows:
D08
MT 670
In subsequence A2, either field :95P::SSIR or field :94C::SSIR or field :22H::SSIR must be present.
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 identifier of the Sender's BIC is XXX, then the branch identifier is not required in field :95P::SUBM.
If the branch identifier of the Sender's BIC is not XXX, then the branch identifier in field :95P::SUBM must
be the same. If the branch identifier of :95P::SUBM is present, then the branch identifier of the Sender's
BIC must be the same.
Note If the Sender's BIC is a Test and Training BIC then its owning primary's registered BIC, and
only its owning primary's registered BIC, with or without a branch identifier, is also allowed in
field :95P::SUBM Submitting Party.
20 July 2023 67
FIN Alphanumeric Codes
Error Codes
D10
MT 199 and MT 299 (SRP)
In field 79, line 1, presence of subfield 2 (Reason Code) and its value depends on subfield 1 (Status) as
follows:
If line 1, subfield 1 is ... And line 1, subfield 2 is ... Then line 2 is ...
CNCL Not allowed Mandatory
RJCR Not applicable Mandatory
PDCR S000 Not allowed
S001 Not allowed
S002 Not allowed
S003 Mandatory
S004 Optional
INDM, PTNA, RQDA Mandatory
Not present Mandatory
AGNT, AM09, COVR, CURR, CUST, Not applicable Not allowed
CUTA, DUPL, FRAD, TECH, UPAY
20 July 2023 68
FIN Alphanumeric Codes
Error Codes
In field 79, if line 3 is present, then line 4 is optional, otherwise line 4 is not allowed.
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.
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.
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.
20 July 2023 69
FIN Alphanumeric Codes
Error Codes
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.
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:
20 July 2023 70
FIN Alphanumeric Codes
Error Codes
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.
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.
20 July 2023 71
FIN Alphanumeric Codes
Error 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
country code list (see note), then in each occurrence of sequence B the following apply:
• If field 57A is not present, then an IBAN (ISO 13616) is mandatory in subfield 1 Account of field 59a in
this occurrence of sequence B. The IBAN format is validated.
• If field 57A is present and the country code of the BIC in 57A is present in the country code list (see
note), then an IBAN is mandatory in subfield 1 Account of field 59a in this occurrence of sequence B.
The IBAN format is validated.
In all other cases, the presence of an IBAN is optional and its format is not validated in subfield 1 Account
of field 59a.
Note Country codes list: AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI,
GP, GR, HR, 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
Note This validation rule applies to all types of BICs that are referenced in field 57A: connected
BIC, non-connected BIC, primary BIC, Synonym, LIVE destination, Test and Training
destination.
20 July 2023 72
FIN Alphanumeric Codes
Error Codes
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 country code list (see note), then in each occurrence of sequence B the following apply:
• If field 57A is not present, then an IBAN (ISO 13616) is mandatory in subfield 1 Account of field 59a.
The IBAN format is validated.
• If field 57A is present and the country code of the BIC in 57A is present in the country code list (see
note), then an IBAN is mandatory in subfield 1 Account of field 59a. The IBAN format is validated.
In all other cases, the presence of an IBAN is optional and its format is not validated in subfield 1 Account
of field 59a.
Note Country codes: AD, AT, BE, BG, BV, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP,
GR, HR, 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 code of and field 57A and country code then in field 59a an
of Sender's BIC Receiver's BIC present of field 57A IBAN
present in present in is present in in subfield 1
country code list country code list country code list 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: connected
BIC, non-connected BIC, primary BIC, 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.
20 July 2023 73
FIN Alphanumeric Codes
Error 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 allowed in any
sequence B field 33B must be occurrence of sequence B
present, and currency codes in fields
32B and 33B must be different.
D23
MT 304
The presence of sequence D and fields 21P, 17G, and 32G in sequence D depends on fields 94A and
17O as follows:
20 July 2023 74
FIN Alphanumeric Codes
Error Codes
D24
MT 306
In sequence A, if field 12F contains the code VANI, then at least one of the following is required: field 17A
with code Y or field 17F with code Y or sequence I is present.
D25
MT 199 and MT 299 (SRP)
In field 79, presence of line 2 subfield 2 (Forwarded-to) depends on line 1, subfield 2 (Reason Code) as
follows:
In field 79
If line 1, subfield 2 is ... And line 1, subfield 2 is ... And line 2 is ... Then line 2, subfield 2
is ...
Present PTNA Present Optional
S003, S004 Present Mandatory
AC04, AGNT, AM04, Present Not allowed
ARDT, CUST, INDM, LEGL,
NOAS, NOOR, RQDA,
FRNA
Not present Not applicable Present Not allowed
D26
MT 300
In sequence A, the values allowed for the field 83J depend on the value of subfield 1.
The allowed values for subfield 2 are as follows:
If subfield 1 of 83J is ... Then the allowed values for subfield 2 are ...
SVBY PTYA, PTYB
In subsequence B1 and B2, the values allowed for the field 57J depend on the value of subfield 1.
If subfield 1 of 57J is ... Then the allowed values for subfield 2 are ...
NOSI CLRD, NDFS, NETS, NONE, SSIS, UKWN
MT 304
In subsequence B1, the values allowed for the field 53J depend on the value of subfield 1.
The allowed values for subfield 2 are as follows:
If subfield 1 of 53J is ... Then the allowed values for subfield 2 are ...
NOSI CLRD, NDFS, NETS, NONE, SSIS, UKWN
20 July 2023 75
FIN Alphanumeric Codes
Error Codes
In subsequence B2, the values allowed for the field 57J depend on the value of subfield 1.
The allowed values for subfield 2 are as follows:
If subfield 1 of 57J is ... Then the allowed values for subfield 2 are ...
NOSI CLRD, NDFS, NETS, NONE, SSIS, UKWN
MT 305
If code NOSI is present in field 57 option J, it must be followed by one of these codes:
If the code NOSI in field 57J The following subfield must be ...
NOSI CLRD, NETS, NONE, SSIS, UKWN
If code SVBY is present in field 83 option J, it must be followed by one of these party codes:
If the code SVBY in field 83J The following subfield must be ...
SVBY PTYA, PTYB
MT 306
In sequence A, the presence of field 12E depends on the value of field 12F as follows:
Sequence A
If field 12F is ... Then the allowed values for field 12E are ...
BINA Not allowed
Any other value Mandatory
If code NOSI is present in field 57 option J, it must be followed by one of these party codes:
If the code NOSI in field 57J The following subfield must be ...
NOSI CLRD, NETS, NONE, SSIS, UKWN
If code SVBY is present in field 83 option J, it must be followed by one of these party codes:
If the code SVBY in field 83J The following subfield must be ...
SVBY PTYA, PTYB
MT 600
If code NOSI is present in field 57 option J, it must be followed by one of these party codes:
If the code NOSI in field 57J The following subfield must be ...
NOSI CLRD, NETS, NONE, SSIS, UKWN
If code SVBY is present in field 83 option J, it must be followed by one of these party codes:
If the code SVBY in field 83J The following subfield must be ...
SVBY PTYA, PTYB
20 July 2023 76
FIN Alphanumeric Codes
Error Codes
MT 601
If code NOSI is present in field 57 option J, it must be followed by one of these party codes:
If the code NOSI in field 57J The following subfield must be ...
NOSI CLRD, NETS, NONE, SSIS, UKWN
If code SVBY is present in field 83 option J, it must be followed by one of these party codes:
If the code SVBY in field 83J The following subfield must be ...
SVBY PTYA, PTYB
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 ...
AVRF, AVRO, AVSF, AVSO, DAVF, N CONF, CLST, OTHR
DAVO, VANI
AVRF, AVRO, AVSF, AVSO, DAVF, Y CONF, CLST, KNIN, KNOT, OTHR
DAVO, VANI
BINA Not applicable CONF, CLST, KNIN, KNOT, 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
20 July 2023 77
FIN Alphanumeric Codes
Error Codes
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
Y Not present Optional
N Y or N Not allowed
N Not present Not allowed
Not present Y or N Not allowed
Not present Not present Not allowed
Sequence A Subsequence A2
and field :
If field:25D::4!c/ And field: And field : Then sequence B
13A::LINK//3!c is ...
[8c]/4!c 25D::REST/[8c]/4!c 25D::REST/[8c]/4!c is ...
Qualifier is ... Data Source is ...
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
20 July 2023 78
FIN Alphanumeric Codes
Error Codes
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).
D30
MT 306
The presence of sequence D depends on the value of field 12F in sequence A as follows:
D31
MT 306
If sequence D is present, 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 12E is ...
Then field 30P is ... And field 30Q is ...
AMER Mandatory Not allowed
BERM Not allowed Mandatory (that is, at least one
occurrence must be present)
20 July 2023 79
FIN Alphanumeric Codes
Error Codes
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
Then sequence E is ...
If field 12F is ... And subfield 1 of field 22K is ...
BINA Any value Mandatory
Any other value Any value Not allowed
D33
MT 306
In sequence D, if present, (see also error code D30), the allowed values for field 26F depend on the value
of field 17F in sequence A as follows:
Sequence A Sequence D
and field 17F is ... then the allowed values for field 26F are ...
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 as follows:
D35
MTs 360 and 361
In sequence A, if field 14A contains OTHER, field 77D must be present.
20 July 2023 80
FIN Alphanumeric Codes
Error Codes
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:
MT 600
The presence of field 77D depends on the value of Type of Agreement (subfield 1 of field 77H) as follows:
Sequence A
If subfield 1 of field 77H is ... 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:
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:
20 July 2023 81
FIN Alphanumeric Codes
Error Codes
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.
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:
20 July 2023 82
FIN Alphanumeric Codes
Error Codes
D43
MT 306
The presence of sequence F depends on the value of field 17A in sequence A as follows:
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 ...
DIKI Not allowed
DKIN Mandatory
DKOT Mandatory
DOKO Not allowed
DUKI Mandatory
DUKO Mandatory
UIKI Not allowed
UOKO Not allowed
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 37M in sequence B as follows:
20 July 2023 83
FIN Alphanumeric Codes
Error Codes
D46
MT 306
In sequence A, the presence of field 17A depends on the value of field 12F as follows:
Sequence A
If field 12F is ... Then field 17A is ...
BINA Not allowed
Any other value Mandatory
D47
MT 306
The presence of sequence H depends on the value of field 17F in sequence A as follows:
D48
MT 306
In sequence F, if field 14M contains the code DISC, then field 29J or 14O must be present, both cannot
be present:
Sequence F
If field 14M is ... And field 29J is ... Then field 14O is ...
DISC Present Not allowed
DISC Not present Mandatory
20 July 2023 84
FIN Alphanumeric Codes
Error Codes
MT 360
In sequences L and M, for all occurrences of fields 53a, 56a and 57a the following rules apply:
MT 361
In sequences M and N, for all occurrences of the fields 53a, 56a, and 57a, the following rules apply:
D49
MTs 102 and 102 STP
If the country codes of both the Sender's and the Receiver's BIC belong to the country code list, then field
33B is mandatory in each occurrence of sequence B, otherwise field 33B is optional.
Country codes list: 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 Sender's BIC country code And Receiver's BIC country code In each occurrence of sequence B,
present in country code list present in country code list then field 33B is ...
Yes Yes Mandatory
Yes No Optional
No Yes Optional
No No Optional
If Sender's BIC country code And Receiver's BIC country Then field 33B is ...
present in country code list code present in country code list
Yes Yes Mandatory
Yes No Optional
No Yes Optional
No No Optional
20 July 2023 85
FIN Alphanumeric Codes
Error Codes
MT 306
In sequence F, the presence of field 30a depends on the presence of field 33Z as follows:
Sequence F
If field 33Z is ... Then field 30a is ...
Present Optional
Not present Not allowed
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.
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.
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.
20 July 2023 86
FIN Alphanumeric Codes
Error Codes
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.
Note See also error codes D20, E13, and E15. Error code D20 takes precedence over error codes
D50, E13, and E15.
If field 71A is ... Then field 71F is ... And field 71G is ...
SHA Optional Not allowed
MT 306
In sequence F, if field 14M contains the code CONT, then field 29O or 14N may be present, both cannot
be present.
Sequence F
If field 14M is ... Then field 29O is ... And field 14N is ...
CONT Present Not allowed
CONT Not allowed Present
CONT Not present Optional
CONT Optional Not present
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.
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.
20 July 2023 87
FIN Alphanumeric Codes
Error Codes
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.
(1) The presence of both fields 71F and 71G is not allowed: see also error codes D50, E13, and E15.
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 also error codes D50, E13, and E15.
MT 306
The presence of sequence G depends on the value of field 12F in sequence A as follows:
D52
MT 507
Field :13a::LINK must be present in one and only one occurrence of subsequence A2.
Note See also error code D53.
20 July 2023 88
FIN Alphanumeric Codes
Error Codes
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:
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
20 July 2023 89
FIN Alphanumeric Codes
Error Codes
Sequence A Sequence B
if field 22B is ...
Then field 32B is ... And field 32H is ... And field 30X is ...
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, field 32H, And field 30X is ...
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".
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
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
20 July 2023 90
FIN Alphanumeric Codes
Error 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 also 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.
Sequence B
If second subfield of field 22H is ... Then field 19A, 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
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:
20 July 2023 91
FIN Alphanumeric Codes
Error Codes
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 37M in sequence E as follows:
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
If field 30F is ... Then field 38J is ...
Present Mandatory
Not present Not allowed
20 July 2023 92
FIN Alphanumeric Codes
Error Codes
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
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.
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.)
20 July 2023 93
FIN Alphanumeric Codes
Error Codes
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
MT 101
In each occurrence of sequence B, if field 56a is present then field 57a must be present.
D66
MT 101
Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of CMTO, PHON, OTHR, or
REPA.
D67
MT 101
In each occurrence of sequence B, when field 23E is used more than once, the following combinations
are not allowed:
20 July 2023 94
FIN Alphanumeric Codes
Error Codes
Example:
Valid Invalid
:23E:URGP :23E:CHQB
:23E:CORT :23E:URGP
:23E:NETS
:23E:RTGS
MT 103 STP
When field 23E is used more than once, the following combination is not allowed:
20 July 2023 95
FIN Alphanumeric Codes
Error Codes
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,
: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.
20 July 2023 96
FIN Alphanumeric Codes
Error Codes
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
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 is ... And in one occurrence of
field:22F::DBNM//VEND sequence D
is ... (1) 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 also error code E84.
20 July 2023 97
FIN Alphanumeric Codes
Error Codes
If sequence D is ... And in sequence D Then sequence E is ... And in one occurrence of
field:22F::DBNM//VEND sequence E
is ... (1) 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 also error code E84.
(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 also 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
20 July 2023 98
FIN Alphanumeric Codes
Error Codes
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
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
20 July 2023 99
FIN Alphanumeric Codes
Error Codes
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:
MT 306
The presence of sequence K and fields 88a and 71F in sequence K depends on the value of field 94A in
sequence A as follows:
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:
MT 360
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:
MT 361
The presence of fields 88a and 71F in sequence O and, therefore, the presence of sequence O itself,
depends on field 94A in sequence A, as follows:
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.
Sequence B
If field 33B is ... Then field 36 is ...
Not present Not allowed
Present, and currency code in field 32B is not equal to Mandatory
currency code in field 33B
Present, and currency code in field 32B is equal to Not allowed
currency code in field 33B
D76
MT 300
The presence of sequence D depends on field 17U in sequence A as follows:
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 also error code D76)
Sequence B
If field 21E is ... Then field 50a (option A or K) is ...
Present Mandatory
Not present Optional (see also 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.
Sequence A
If field 21E is ... Then field 50a (option A or K) is ...
Present Mandatory
Not present Optional (see also error code D86)
Sequence B
If field 21E is ... Then field 50a (option A or K) is ...
Present Mandatory
Not present Optional (see also 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.
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
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.
D81
MTs 104, 107, and 416
Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of OTHR.
MT 306
Subfield 2 of field 22K, that is "/"35x, is mandatory when subfield 1 of this field C consists of OTHR;
otherwise subfield 2 is not allowed.
MT 760
If subfield 1 of field 40C is OTHR, then subfield 2 of field 40C may be present, otherwise subfield 2 of field
40C is not allowed.
If subfield 1 of field 23F is DAYS or OTHR, then subfield 2 of field 23F is mandatory, if subfield 1 of field
23F is ONEY then subfield 2 is not allowed.
D82
MTs 104 and 107
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.
D84
MT 740
Either field 58a or 59, but not both, may be present.
D85
MT 330
In sequence B, if field 30X is present, then field 34E is mandatory; otherwise field 34E is not allowed.
Sequence B
If field 30X is ... 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.
D87
MT 759
The value in field 22D depends on the value of field 23H as follows:
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
MT 298/093
If field 21H is present in a subsequence B1, then:
• Field 21H must be present in all other subsequences B1 of the same parent sequence B.
• Field 21H in the parent sequence B must not be present.
• Fields 51, 54, and 12G are mandatory in the parent sequence B.
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 20a are optional, but at least one qualifier (any
one) must be present.
MT 537
In subsequence D1a1B1 (Transaction Details), if field 95a is present, all qualifiers of field 95a are
optional, but either ACOW or CACO (not both) must be present.
In subsequence D1a (Penalties per Counterparty), all qualifiers of field 95a are optional, but either ASDP
or REPA must be present.
MT 548
In subsequence C1a1B1 (Transaction Details), if field 95a is present, all qualifiers of field 95a are
optional, but either ACOW or CACO (not both) must be present.
In subsequence C1a (Penalties per Counterparty), all qualifiers of field 95a are optional, but either ASDP
or REPA must be present.
MT 568
All qualifiers of field 70a 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
MT 196 and MT 296 (SRP)
In field 76, line 1, presence of subfield 2 (Reason Code) and its value depends on subfield 1 (Status) as
follows:
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), and MT 199 (Swift Go)
In field 79, line 2, presence of subfield 2 (Reason Code) depends on subfield 1 (Status) as follows:
D95
MT 196 and MT 296 (SRP)
In field 76, presence of line 2 subfield 2 (Forwarded-to) depends on line 1, subfield 2 (Reason Code) as
follows:
In field 76
If line 1, subfield 2 is ... And line 1, subfield 2 is ... Then line 2, subfield 2 is ...
Present PTNA Optional
AC04, AGNT, AM04, ARDT, CUST, Not allowed
INDM, LEGL, NOAS, NOOR, RQDA
Not present Not applicable Not allowed
MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift Go), and MT 299 (Swift gpi -
gCOV)
In field 79, presence of line 3 subfield 2 (Forwarded-to) and line 3 subfield 3 (Settlement Method)
depends on line 2, subfield 2 (Reason Code) as follows:
In field 79
If line 2, subfield 1 is ... And line 2, subfield 2 is ... And line 3, subfield 2 is ... And line 3, subfield 3 is ...
ACSP G000 Mandatory Mandatory
G001 Optional Mandatory
Any other value Not allowed Not allowed
RETN Not allowed Optional Optional
RJCT Not applicable Not allowed Not allowed
Any other value Not applicable Not allowed Not allowed
In field 79
If line 2, subfield 1 is ... And line 2, subfield 2 is ... And line 3, subfield 2 is ... Then line 3, subfield 3
is ...
ACSP G001 Optional Optional
Any other value Not allowed Not allowed
Any other value Not applicable Not allowed Not allowed
In field 79
If line 2, subfield 1 is ... And line 2, subfield 2 is ... Then line 3, subfield 2 Then line 3, subfield 3
is ... is ...
ACSP G000 Mandatory Mandatory
G001 Optional Mandatory
Any other value Not allowed Not allowed
Any other value Any other value Not allowed Not allowed
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).
MT 306
If subsequence J1 is present, field 18B must be equal to the number of occurrences of the field 30M.
MT 306
If subsequence J2 is present, field 18C must be equal to the number of occurrences of the field 30N.
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.
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.
MT 565
In sequence D, if field :22F::CAOP//BOBD is present, then in sequence A field :22F::CAEV//WTRC must
be present in the message.
MT 567
In sequence B, if field :22F::CAOP//BOBD is present, then in sequence A field :22F::CAEV//WTRC must
be present in the message.
E Error Codes
E00
Not used.
E01
MTs 103 and 103 REMIT
If field 23B contains SPRI, field 23E can contain only SDVA, TELB, PHOB, or INTC.
MT 103 STP
If field 23B contains SPRI, field 23E can contain only SDVA and INTC.
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.
(1) If the Data Source Scheme is present in field :22F::CAEV then the conditional rule does not apply.
MT 760
In sequence B, if field 23B is FIXD, then field 31E must be present, if field 23B is COND, then field 31E
may be present, otherwise field 31E is not allowed.
Sequence B
If field 23B is ... Then field 31E is ...
FIXD Mandatory
COND Optional
Other Not allowed
In sequence C, if field 23B is FIXD, then field 31E must be present, if field 23B is COND, then field 31E
may be present, otherwise field 31E is not allowed.
Sequence C
If field 23B is ... Then field 31E is ...
FIXD Mandatory
COND Optional
Other Not allowed
E02
MTs 103, 103 REMIT, and 103 STP
If field 23B contains SSTD or SPAY, field 23E must not be used.
MT 564
In sequence A, if field :23G:REPE is present, then when sequence C is present, field :36a::QINT is
mandatory.
MT 760
In sequence B, if field 23B is COND, then field 35G must be present otherwise field 35G is not allowed.
Sequence B
If field 23B is ... Then field 35G is ...
COND Mandatory
Other Not allowed
In sequence C, if field 23B is COND, then field 35G must be present otherwise field 35G is not allowed.
Sequence C
If field 23B is ... Then field 35G is ...
COND Mandatory
Other Not allowed
MT 767
In sequence B, if field 23B is COND, then field 35G must be present in sequence B, otherwise field 35G
is not allowed.
Sequence B
If field 23B is ... Then field 35G is ...
COND Mandatory
Other Not allowed
In sequence C, if field 23B is COND, then field 35G must be present in sequence C, otherwise field 35G
is not allowed.
Sequence C
If field 23B is ... Then field 35G is ...
COND Mandatory
Other Not allowed
E03
MTs 103 and 103 REMIT
If field 23B contains SPRI, SSTD or SPAY, field 53a must not be used with option D.
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.
(1) If the Data Source Scheme is present in field :22F::CAEV//OTHR, then the conditional rule does not apply.
MT 760
In sequence B, if field 23B is OPEN then field 23F is not allowed.
Sequence B
If field 23B is ... Then field 23F is ...
OPEN Not allowed
Other Optional
Sequence C
If field 23B is ... Then field 23F is ...
OPEN Not allowed
Other Optional
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 ([/1!a]['/'34x] 'CrLf') must be present in field 53B.
MT 103 STP
If field 53a is present with option B, subfield 1, Party Identifier ([/1!a]['/'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.
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.
(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.
(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.
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).
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).
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.
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.
field :20C::PREV must be present; consequently, in all other occurrences of A2, field :20C::PREV is not
allowed.
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.
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.
MT 527
If subfield 1 of field 23G contains REPL in sequence A, then sequence B is not allowed; otherwise
sequence B is mandatory.
MT 548
If the message is a penalty, that is, if field :23G::PENA is present, then sequence B is not allowed and
sequence C is mandatory.
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
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.
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.
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, (['/'1!a]['/'34x] 'CrLf') must be present.
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.
E10
MTs 103 and 103 REMIT
If field 23B contains SPRI, SSTD, or SPAY, subfield 1, Account, in field 59a is mandatory.
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 CLAI (Claim or Compensation), TAXR (Tax Refund), or REVR (Notification
or Reversal).
Note Error code E11 must be applied even if the DSS is present in field :22F::ADDB.
E12
MT 586
In sequence A, if field :23G:CANC/PORT is present or field 23G:NEWM/PORT is present or field
23G:RMDR/PORT is present, then field 95Q is optional, otherwise field 95Q is not allowed.
Sequence A
If field 23G is ... Then field 95Q is ...
CANC/PORT Optional
NEWM/PORT Optional
RMDR/PORT Optional
Any other value Not allowed
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.
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.
If field 71A is ... Then field 71F is ... And field 71G is ...
OUR Not allowed Optional
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.
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.
Note See also error codes D20, D50 and E13. Error code D20 takes precedence over error codes
D50, E13, and E15.
If field 71A is ... Then field 71F is ... And field 71G is ...
BEN Mandatory (at least one occurrence) Not allowed
E16
MTs 103, 103 REMIT, and 103 STP
If field 23B contains SPRI, field 56a must not be used.
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.
E18
MTs 103 and 103 REMIT
If any field 23E contains CHQB, subfield 1, Account, in field 59a is not allowed.
E19
MT 564
In each occurrence of sequence E, if :22F::OPTF//QCAS is not present, then in the same occurrence of
sequence E fields :90a::MACI, :90a::MICI and :90a::MMCI are not allowed.
E20
MT 564
In each occurrence of sequence E, if field :92a::WITL is present, then field :92a::TAXR must be present in
the same occurrence of sequence E.
In each occurrence of subsequence E1, if field :92a::WITL is present, then field :92a::TAXR must be
present in the same occurrence of subsequence E1.
In each occurrence of subsequence E2, if field :92a::WITL is present, then field :92a::TAXR must be
present in the same occurrence of subsequence E2.
MT 566
In sequence D, if field :92a::WITL is present, then field :92a::TAXR must be present.
In each occurrence of subsequence D1, if field :92a::WITL is present, then field :92a::TAXR must be
present in the same occurrence of subsequence D1.
In each occurrence of subsequence D2, if field :92a::WITL is present, then field :92a::TAXR must be
present in the same occurrence of subsequence D2.
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.
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.
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.
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 message) And (in the message) Then in sequence D,
subsequence E1 is ... subsequence E2 is ... field :98a::PAYD 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 564
In each occurrence of sequence E:
• Field :98A::BORD must not be present more than once.
• Field :98B::BORD must not be present more than once.
• Field :98C::BORD must not be present more than once.
• Field :98E::BORD must not be present more than once.
• Only one of the fields :98A::BORD or :98B::BORD or :98C::BORD or :98E::BORD may be present.
Note Error code E25 must be applied even if the DSS is present in field :98B::.
Note See also E26.
E26
MT 564
In each occurrence of sequence E:
• If field :98J::BORD is present more than once, then for each occurrence of field :98J::BORD, the
Identifier Code must be different.
• If field :98K::BORD is present more than once, then for each occurrence of field :98K::BORD, the
Proprietary Code must be different.
Note Error code E26 must be applied even if the DSS is present in field :98K::.
Note See also E25.
E27
MT 564
If field :90a::MINP is present in any occurrence of sequence E, then :90a::MINP must not be present in
sequence D.
If field :90a::MAXP is present in any occurrence of sequence E, then :90a::MAXP must not be present in
sequence D.
If field :90a::FBIP is present in any occurrence of sequence E, then :90a::FBIP must not be present in
sequence D.
If field :90a::LBIP is present in any occurrence of sequence E, then :90a::LBIP must not be present in
sequence D.
E28
MT 564
If field :92a::BIDI is present in any occurrence of sequence E, then :92a::BIDI must not be present in
sequence D.
E29
MT 564
In sequence D, if field :22F::ADDB//INCP is present, then in sequence A field :22F::CAEV//CONS must
be present.
(1) If DSS is present in field :22F::ADDB, then conditional rule does not apply.
Sequence D
If field :22F::OFFE//DISS is (1) ... Then field :22F::OFFE//NDIS is ...
Present Not allowed
Not present Optional
(1) If DSS is present in field :22F::OFFE, then conditional rule does not apply.
In each occurrence of sequence E, if field :22F::OFFE//DISS is present, then in the same occurrence of
sequence E field :22F::OFFE//NDIS is not allowed.
(1) If DSS is present in field :22F::OFFE, then conditional rule does not apply.
(1) If DSS is present in field :22F::OFFE, then conditional rule does not apply.
In each occurrence of subsequences E1 or E2, if field :22F::OTYP is present, then in the same
occurrence of subsequences E1 or E2 field :22F::ITYP must be present.
In sequence D or in any occurrence of sequence E, if field :90a::FBIP or field :90a::LBIP is present, then
in sequence A, either field :22F::CAEV//BIDS or field :22F::CAEV//DTCH or :22F::CAEV//TEND must be
present.
In sequence D or in any occurrence of sequence E, if field :90a::FBIP or field :90a::LBIP is present, then
in sequence D, field :22F::ADDB//INCP is not allowed.
MT 566
In sequence C, if field :22F::ADDB//INCP is present, then in sequence A field :22F::CAEV//CONS must
be present.
(1) If DSS is present in field :22F::ADDB, then conditional rule does not apply.
In each occurrence of subsequences D1 or D2, if field :22F::OTYP is present, then in the same
occurrence of subsequences D1 or D2 field :22F::ITYP must be present.
E30
Available.
E31
Available.
E32
MT 537
In subsequence D1a1 (Penalty Details), if field 24B is present, or field 70D, then field 25D must be
present.
MT 548
In subsequence C1a1 (Penalty Details), if field 24B is present, or field 70D then field 25D must be
present.
E33
MT 364
The presence of sequences B and E depends on subfield 1 of field 23A in sequence A as follows:
Note See also 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:
Note See also 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 37G
depends on field 22B in sequence A as follows:
MT 365
In sequence A, the presence of fields 32G, 33E and 22D and, in sequences B and E, the presence of
field 37G, depend on field 22B in sequence A as follows:
E35
MT 306
In sequences C (if present) and E, (if present - see also error code D32), and L (if present), if field 56a is
not present, then field 86a in the same sequence C, E or L 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 L
If field 56a is ... Then field 86a is ...
Not present Not allowed
Present 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
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
Sequence C
If field 56a is ... Then field 86a is ...
Not present Not allowed
Present Optional
If, in a sequence, or an internal loop, Then, in the same sequence, or the same internal
field 56a is ... 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
(Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2.
(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 (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence C1.
(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
(Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence B.
(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
(Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence C3 Status.
(1) If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.
Within each occurrence of subsequence D1a1B1a1 Reason, the qualifier in field 24B must be the same
as or linked to the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding
subsequence D1a1B1a Status.
(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
(Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2.
(1) If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.
Within each occurrence of subsequence C1a1B1a1 Reason, the qualifier in field 24B must be the same
as or linked to the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding
subsequence C1a1B1a Status.
(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 (Status
Code) used with the appropriate qualifier in field 25D of the same occurrence of sequence B.
(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
(Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2 Status.
(1) If the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.
E38
MT 362
The currency code of the fields 33F and 32H in sequence B must be the same. The currency codes of the
fields 33F and 32H in sequence D must be the same.
E39
MT 362
In sequences B and D, the presence of fields 37V and 37G depends on subfield 1 of field 23A in
sequence A as follows:
Note In sequence B, 37G refers to the field at index 23. In sequence D, 37G refers to the field at
index 44.
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 37V or 37G 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, 37V 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, 37G must be
present in sequence D.)
1. If sequences B and D are present:
Sequence A Sequence D
if subfield 1 of field 23A is ...
Then field 37V must be ... And field 37G must be ...
FIXEDFIXED Not allowed Not allowed
FLOATFLOAT Optional Optional
Sequence A Sequence D
if subfield 1 of field 23A is ...
Then field 37V must be ... And field 37G must be ...
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
CORRBUYER Not allowed Not allowed
CORRSELLER Optional Optional
VARBUYER Not allowed Not allowed
VARSELLER Optional Optional
VOLABUYER Not allowed Not allowed
VOLASELLER Optional Optional
COLLARBYER either 37V or 37G or both is/are mandatory
COLLARSLLR either 37V or 37G or both is/are mandatory
Sequence A Sequence B
if subfield 1 of field 23A is ...
Then field 37V must be ... And field 37G 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
CORRBUYER Optional Optional
CORRSELLER Not allowed Not allowed
VARBUYER Optional Optional
VARSELLER Not allowed Not allowed
VOLABUYER Optional Optional
VOLASELLER Not allowed Not allowed
COLLARBYER Either 37V or 37G or both is/are mandatory
COLLARSLLR Either 37V or 37G 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
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.
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:
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 also error codes D45, D59, and E40 for additional subsequence(s) and field(s)
conditional checks.
2. For each valid sequence combination, a table (below) indicates the checks to apply.
3. For the combination CF, both tables 1 and 2 must be applied.
1. If sequence C is present:
2. If sequence F is present:
E42
MT 360
In sequences C and F, the presence of fields 37V and 37G 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 37V or 37G 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, 37V 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, 37G must be
present in sequence F.)
1. If sequences C and F are present:
Sequence A Sequence F
if subfield 1 of field 23A is ...
Then field 37V must be ... And field 37G 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 error code D58
COLLARSLLR Not applicable per error code D58
Sequence A Sequence C
if subfield 1 of field 23A is ...
Then field 37V must be ... And field 37G must be ...
FIXEDFIXED Not applicable Not applicable
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 error code D58
COLLARSLLR Not applicable per error code D58
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, F, and H are allowed:
Sequence A Then sequence And sequence C And sequence E And sequence F And sequence H
if subfield 1 of B is ... is ... is ... is ... is ...
field 23A is ...
CORRBUYER Not allowed Mandatory Mandatory Not allowed Mandatory
CORRSELLER Mandatory Not allowed Not allowed Mandatory Mandatory
FIXEDFIXED Mandatory Not allowed Mandatory Not allowed Not allowed
Sequence A Then sequence And sequence C And sequence E And sequence F And sequence H
if subfield 1 of B is ... is ... is ... is ... is ...
field 23A is ...
FLOATFLOAT Not allowed Mandatory Not allowed Mandatory Not allowed
FLOATFIXED Mandatory Not allowed Not allowed Mandatory Not allowed
FIXEDFLOAT Not allowed Mandatory Mandatory Not allowed Not allowed
VARBUYER Not allowed Mandatory Mandatory Not allowed Mandatory
VARSELLER Mandatory Not allowed Not allowed Mandatory Mandatory
VOLABUYER Not allowed Mandatory Mandatory Not allowed Mandatory
VOLASELLER Mandatory Not allowed Not allowed Mandatory Mandatory
Note See also 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.
E45
MTs 103 and 103 REMIT
If field 57a is not present, no field 23E may contain TELE or PHON.
E46
MT 101
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.
E47
MT 350
If sequence D is present, at least one of the subsequences D1 or D2 must be present.
MT 362
At least one of the sequences B or D must be present.
E48
MT 362
At least one of the sequences C or E must be present.
MT 504
In each occurrence of subsequence C1a, the presence of subsequence C1a1 depends on the presence
of field :22F::STCO//NSSP as follows:
(1) This error code does not apply if the Data Source Scheme is present.
(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:
(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:
(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:
(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 also error code E48).
Note See also error code D96.
MT 504
In sequence D, the presence of subsequence D1 depends on the presence of field :22F::STCO//NSSP as
follows:
(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:
(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 also
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:
(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:
(1) This error code does not apply if the Data Source Scheme is present.
E52
MTs 502, 514, and 518
In subsequence C1, if field :95a::PSET is present, then field 97a is not allowed in the same subsequence.
Subsequence C1
If field :95a::PSET is ... Then field 97a is ...
Present Not allowed within the same occurrence
Not present Optional
Subsequence D1
If field :95a::PSET is ... Then field 97a 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 is not allowed in the same
subsequence.
Subsequence B1a2a
If field :95a::PSET is ... Then field 97a 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 is not allowed in the same
subsequence.
Subsequence B2b1
If field :95a::PSET is ... Then field 97a is ...
Present Not allowed within the same occurrence
Not present Optional
In subsequence C2a, if field :95a::PSET is present, then field 97a is not allowed in the same sequence.
Subsequence C2a
If field :95a::PSET is ... Then field 97a 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 is not allowed in the same subsequence.
Subsequence E1
If field :95a::PSET is ... Then field 97a 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 is not allowed in the same subsequence.
Subsequence B1
If field :95a::PSET is ... Then field 97a 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 is not allowed in the same
subsequence.
Subsequence B1a4
If field :95a::PSET is ... Then field 97a is ...
Present Not allowed within the same occurrence
Not present Optional
MT 586
In subsequence B6a, if field :95a::PSET is present, then field 97a is not allowed in the same
subsequence.
Subsequence B6a
If field :95a::PSET is ... Then field 97a 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 one Mandatory, that is, must be present
occurrence of A1 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.
MT 575
In subsequence C2a, if field :95a::PSET is present, then field 97a is not allowed in the same
subsequence.
Subsequence C2a
If field :95a::PSET is ... Then field 97a 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:
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
Not present Optional
E56
MTs 535 and 536
If in sequence A, field :17B::CONS contains Y, then in every occurrence of sequence B, field 97a 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.
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, connected
BIC, non-connected BIC, primary BIC, 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 :36a::ORDR or field :19A::ORDR must be present, but not both.
Sequence B
If field :36a::ORDR is ... Then field :19A::ORDR is ...
Present Not allowed
Not present Mandatory
MT 509
In sequence B, either a quantity (field :36a::) or an amount (field :19A::) must be present, but not both.
Sequence B
If field :36a:: 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 present then field 19A
must not be present, and vice versa if field 19A is present then field 36B must not be present.
E59
MT 517
If field 23G does not contain CANC, then field 13A must be present and contain 515 in minimum one
occurrence of subsequence A1.
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:
MT 569
In each occurrence of subsequence C1a1A, the presence of field :70C::RATS depends on the presence
of field :94B::RATS as follows:
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
MT 527
When in sequence B field :22F::OFRF is present, then in sequence B field :99B::FFRD must not be
present.
Sequence B
If field :22F::OFRF is ... Then field :99B::FFRD is ...
Present Not allowed
Not present Optional
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
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.
Subsequence E2
If field :19B::RESU is ... Then field :92B::EXCH is ...
Present Mandatory
Not present Optional
MT 565
In sequence D, if field :36a::QINS is present, then field :19B::QCAS is not allowed and if field :36a::QINS
is not present, then field :19B::QCAS is mandatory.
Sequence D
If field :36a::QINS is ... Then field :19B::QCAS is ...
Present Not allowed
Not present Mandatory
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
Not present Not allowed
MT 567
In sequence B, if field :36a::STAQ is present, then field :19B::STAC is not allowed and if field :36a::STAQ
is not present, then field :19B::STAC is optional.
Sequence B
If field :36a::STAQ is ... Then field :19B::STAC is ...
Present Not allowed
Sequence B
If field :36a::STAQ is ... Then field :19B::STAC is ...
Not present Optional
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 B6b.
Subsequence B6b
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.
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.
E64
MT 502
If the Function of the Message (field :23G:) is CANC and the Ordered Quantity (field :36B::ORDR) is
present, then the Quantity to Cancel (field :36B::CANC) must be present in the order details sequence.
If the Function of the Message (field :23G:) is CANC and the Ordered Amount (field:19A::ORDR) is
present, then the Amount to Cancel (field :19A::CANC) must be present in the order details sequence.
If the Function of the Message is not CANC, the Quantity to Cancel and the Amount to Cancel are not
allowed.
Sequence A 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 also 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.
MT 558
If sequence A field :22a::COLA// is other than SLEB, then in sequence B field :19A::TRAA must be
present.
E66
MTs 535, 536, 538, and 586
If field :17B::ACTI in sequence A contains N, then sequence B must not be present; otherwise, sequence
B is mandatory.
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, sequence C Transactions, and sequence D Penalties 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 and sequence D Penalties are 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 and sequence D Penalties are not allowed and sequence C Transactions
is mandatory.
If the Activity Flag (field :17B::ACTI) in sequence A indicates that there is information to be reported, that
is, Y and field :22H::STST//PENA is present, then sequence B and sequence C are not allowed and
sequence D is 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:
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.
MT 576
If field :17B::ACTI in sequence A contains N, then sequence B must not be present.
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.
MT 537
In sequence A, if field 22H::STST//PENA is present and if field 22F::SFRE//MNTH is present and if field
17B::ACTI//Y is present, then field 69a::STAT in sequence D (PENA) must be present.
Sequence A And if field 22F::SFRE// And if field 17B::ACTI// Then in sequence D field
if field :22H::STST//PENA MNTH is ... is ... 69a::STAT is ...
is ...
Present Present Y Mandatory (1)
MT 576
Field 97a must be present in sequence A, or in all occurrences of subsequence B2c, but not both.
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
Present Optional
MT 537
In sequence A, if field 22H::STST//PENA is present and if field 22F::SFRE//MNTH is present and if field
17B::ACTI//Y is present, then field 98a::PAYD in sequence D1 (PENACUR) must be present.
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.
Note Error codes E66 and E56 take precedence over error code E69.
E70
MT 537
In sequence A, if field 23G::PENA is present, then field 22H::STST//PENA must be present.
Sequence A
If field :23G::PENA is ... Then field :22H::STST//PENA is ...
Present Mandatory
Not present Optional
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.
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.
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.
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.
MT 569
In each occurrence of subsequence C1a1, the presence of field :98a::SETT depends on the value of
field :17B:COLL as follows:
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.
E74
MT 502
In sequence B, field :22F::TOOR and/or field :90a::LIMI must be present.
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
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 once Not present or present only once May contain any indicator 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.
(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.
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.
If the value date is after 31 December 2014, then the currency code LTL (Lithuania) must not be used as
the currency of settlement.
If the value date is after 15 January 2023, then the currency code HRK (Croatia) must not be used as the
currency of settlement.
E77
MT 564
In each occurrence of sequence E and subsequence E2:
• Field :92F::GRSS must not be present more than once.
• Field :92H::GRSS must not be present more than once.
• Field :92K::GRSS must not be present more than once.
• Only one of the fields :92F::GRSS or :92H::GRSS or :92K::GRSS may be present.
• Field :92F::NETT must not be present more than once.
• Field :92H::NETT must not be present more than once.
• Field :92K::NETT must not be present more than once.
• Only one of the fields :92F::NETT or :92H::NETT or :92K::NETT may be present.
In each occurrence of sequence E, and subsequences E1 and E2:
• Field :92A::TAXR must not be present more than once.
• Field :92F::TAXR must not be present more than once.
• Field :92K::TAXR must not be present more than once.
• Only one of the fields :92A::TAXR or :92F::TAXR or :92K::TAXR may be present.
• Field :92A::WITL must not be present more than once.
• Field :92F::WITL must not be present more than once.
• Field :92K::WITL must not be present more than once.
• Only one of the fields :92A::WITL or :92F::WITL or :92K::WITL may be present.
In each occurrence of subsequence E2:
• Field :92A::DEEM must not be present more than once.
• Field :92F::DEEM must not be present more than once.
MT 566
In sequence D and in each occurrence of subsequence D2:
• Field :92F::GRSS must not be present more than once.
• Field :92H::GRSS must not be present more than once.
• Only one of the fields :92F::GRSS or :92H::GRSS may be present.
• Field :92F::NETT must not be present more than once.
• Field :92H::NETT must not be present more than once.
• Only one of the fields :92F::NETT or :92H::NETT may be present.
In each occurrence of sequence D and subsequences D1 and D2:
• Field :92A::TAXR must not be present more than once.
• Field :92F::TAXR must not be present more than once.
• Only one of the fields :92A::TAXR or :92F::TAXR may be present.
• Field :92A::WITL must not be present more than once.
• Field :92F::WITL must not be present more than once.
• Only one of the fields :92A::WITL or :92F::WITL may be present.
In each occurrence of subsequence D2:
• Field :92A::DEEM must not be present more than once.
• Field :92F::DEEM must not be present more than once.
• Only one of the fields :92A::DEEM or :92F::DEEM may be present.
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:: 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 sequence E and subsequences E1 and E2:
• If field :92R::TAXR is present more than once, then for each occurrence of field :92R::TAXR, the Rate
Type Code must be different.
• If field :92R::WITL is present more than once, then for each occurrence of field :92R::WITL, the Rate
Type Code must be different.
In each occurrence of subsequence E2:
• If field :92J:: DEEM is present more than once, then for each occurrence of field :92J:: DEEM, the
Rate Type Code must be different.
• If field:92R::DEEM is present more than once, then for each occurrence of field :92R::DEEM, the Rate
Type Code must be different.
Note Error code E78 must be applied even if the DSS is present in field:92J:: or field :92R::.
Note See also 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::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 sequence D and subsequences D1 and D2:
• If field :92R::TAXR is present more than once, then for each occurrence of field :92R::TAXR, the Rate
Type Code must be different.
• If field :92R::WITL is present more than once, then for each occurrence of field :92R::WITL, the Rate
Type Code must be different.
In each occurrence of subsequence D2:
• If field :92J:: DEEM is present more than once, then for each occurrence of field :92J:: DEEM, the
Rate Type Code must be different.
• If field :92R::DEEM is present more than once, then for each occurrence of field :92R::DEEM, the
Rate Type Code must be different.
Note Error code E78 must be applied even if the DSS is present in field:92J:: or field 93R.
Note See also 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.
(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.
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 also error code E67),
that is, if field :22F::STTY//ACCT is present.
In every occurrence Then, in the same And the same And in every And in every
of subsequence B1 occurrence of occurrence of occurrence of occurrence of
if subsequence B1b subsequence B1 subsequence B1 subsequence B1b subsequence B1b
is ... field :90a: is ... field :19A::HOLD field :90a: is ... field :19A::HOLD
is ... is ...
Not present Mandatory Mandatory Not applicable Not applicable
Present once or more Optional Optional Mandatory Mandatory
E83
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:
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:
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:
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 subsequences B2b, C2, and D1a1B1, 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
Not = APMT Optional
Subsequence C2
If field :22H::PAYM is ... Then field :19A::PSTA is ...
APMT Mandatory
Not = APMT Optional
Subsequence D1a1B1
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
In subsequence C1a1B1, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be specified.
Subsequence C1a1B1
If field :22H::PAYM is ... Then field :19A::PSTA 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.
MT 586
In sequence B, if field :22H::PAYM//APMT is used, then field :19A::SETT must be specified.
E84
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
MT 504
In each occurrence of sequence C, for subsequences C1a1 and C2a1, the following party fields cannot
appear more than once:
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:
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:
MT 536
In each occurrence of subsequence B1a, in subsequence B1a2, the following party fields cannot appear
more than once:
Subsequence B1a2a
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
MT 537
The following party fields cannot appear more than once in the same occurrence of subsequence B2b:
Subsequence B2b1
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
The following party fields cannot appear more than once in the same occurrence of subsequence C2:
Sequence C2a
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
MT 548
The following party fields cannot appear more than once in the same occurrence of sequence B:
Subsequence B1
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
MT 575
The following party fields cannot appear more than once in the same occurrence of subsequence B1a:
Subsequence B1a4
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
MT 575
The following party fields cannot appear more than once in the same occurrence of subsequence C2:
Subsequence C2a
:95a::BUYR
:95a::DEAG
:95a::DECU
:95a::DEI1
:95a::DEI2
:95a::PSET
:95a::REAG
:95a::RECU
:95a::REI1
:95a::REI2
:95a::SELL
MT 578
The following party fields cannot appear more than once in a message:
Subsequence E1 Subsequence E2
:95a::BUYR :95a::ACCW
:95a::DEAG :95a::BENM
:95a::DECU :95a::PAYE
:95a::DEI1 :95a::DEBT
:95a::DEI2 :95a::INTM
Subsequence E1 Subsequence E2
: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 B6a
: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:
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:
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:
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.
If the instruction is a delivery (:22H::REDE//DELI in subsequence C2) and the Settlement Parties
subsequence C2a is used, then it is mandatory to specify a Receiving Agent: one occurrence of the
settlement parties subsequence C2a must contain party field :95a::REAG.
If the instruction is a receipt (:22H::REDE//RECE in subsequence C2) and the Settlement Parties
subsequence C2a is used, then it is mandatory to specify a Delivering Agent: one occurrence of the
settlement parties subsequence C2a must contain party field :95a::DEAG.
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.
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.
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 B6a.
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 B6a.
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 occurrence In each occurrence For all occurrences Fields :95a:: all
of sequence of subsequence of subsequence(s) qualifiers must
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, 543, E Not applicable E1 :95a::qualifier(s)
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)
578 E Not applicable E1 :95a::qualifier(s)
586 B (R) Not applicable B6a :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:
(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.
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
Subsequence E3
:19A::DEAL
:19A::EXEC
:19A::ISDI
:19A::LADT
:19A::LEVY
:19A::LOCL
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
:19A::SETT
:19A::SHIP
:19A::SPCN
:19A::STAM
:19A::STEX
:19A::TRAN
:19A::TRAX
:19A::VATA
:19A::WITH
MT 541
The following amount fields cannot appear in more than one occurrence of the Amounts subsequence
E3:
Subsequence E3
:19A::ACCA
:19A::ACRU
:19A::ANTO
:19A::CHAR
:19A::COAX
:19A::COUN
:19A::DEAL
:19A::EXEC
:19A::ISDI
:19A::LADT
:19A::LEVY
:19A::LOCL
Subsequence E3
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
:19A::SETT
:19A::SHIP
:19A::SPCN
:19A::STAM
:19A::STEX
:19A::TRAN
:19A::TRAX
:19A::VATA
:19A::WITH
MT 542
The following amount fields cannot appear in more than one occurrence of the Amounts subsequence
E3:
Subsequence E3
:19A::ACCA
:19A::ACRU
:19A::ANTO
:19A::BOOK
:19A::CHAR
:19A::COAX
:19A::COUN
:19A::DEAL
:19A::EXEC
:19A::ISDI
:19A::LADT
:19A::LEVY
:19A::LOCL
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
Subsequence E3
:19A::SETT
:19A::SHIP
:19A::SPCN
:19A::STAM
:19A::STEX
:19A::TRAN
:19A::TRAX
:19A::VATA
:19A::WITH
MT 543
The following amount fields cannot appear in more than one occurrence of the Amounts subsequence
E3:
Subsequence E3
:19A::ACCA
:19A::ACRU
:19A::ANTO
:19A::CHAR
:19A::COAX
:19A::COUN
:19A::DEAL
:19A::EXEC
:19A::ISDI
:19A::LADT
:19A::LEVY
:19A::LOCL
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
:19A::SETT
:19A::SHIP
:19A::SPCN
:19A::STAM
:19A::STEX
:19A::TRAN
Subsequence E3
:19A::TRAX
:19A::VATA
:19A::WITH
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
:19A::LADT
:19A::LEVY
:19A::LOCL
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
:19A::SHIP
:19A::SPCN
:19A::STAM
:19A::STEX
:19A::TRAN
:19A::TRAX
:19A::VATA
:19A::WITH
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
:19A::LOCO
:19A::MARG
:19A::OTHR
:19A::REGF
:19A::RSCH
: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
Subsequence E3
: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
B6b:
Subsequence B6b
:19A::ACRU
:19A::CHAR
:19A::COAX
:19A::DEAL
:19A::EXEC
:19A::LOCL
:19A::LOCO
:19A::OTHR
:19A::SETT
:19A::STAM
:19A::TRAX
:19A::WITH
E88
MTs 502, 514, and 518
In each occurrence of sequence D, if field :95a::ALTE is present with letter option L, then field :
95a::MEOR and field :95a::MERE must not be present in the same occurrence of the sequence D.
MT 527
In each occurrence of sequence E, if field :95a::ALTE is present, then field :95a:: must be present with
only one other qualifier (ISSU or INVE only) in the same occurrence of the sequence.
MTs 540-47 and 578
In each occurrence of sequence F, if field :95a::ALTE is present with letter option L, then field :
95a::MEOR and field :95a::MERE must not be present in the same occurrence of the sequence F.
MT 548
In each occurrence of sequence D, if field :95a::ALTE is present with letter option L, then field :
95a::MEOR and field :95a::MERE must not be present in the same occurrence of the sequence D.
MT 586
In each occurrence of sequence C, if field :95a::ALTE is present with letter option L, then field :
95a::MEOR and field :95a::MERE must not be present in the same occurrence of the sequence C.
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 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.
MT 524
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
Sequence A
If field :99a::TOSE is ... Then field :99a::SETT is ...
Present Mandatory
Sequence A
If field :99a::TOSE is ... Then field :99a::SETT is ...
Not present Optional
MT 565
If the field :36a::RDUQ is present in sequence D, then field 36a::QINS is mandatory in the same
sequence.
Sequence D
if field :36a::RDUQ is ... Then field :36a::QINS is ...
Present Mandatory
Not present Optional
E91
MT 321
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:
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.
E92
MT 321
In a message, the following sequence C fields cannot appear more than once:
Sequence C
:22H::PRIT//APFM
:22H::PRIT//APCP
:22H::PRIT//IPFM
:22H::PRIT//IPCP
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.
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 36a, must not be present in subsequence E1
Securities Movement
• the Amount, that is, field 19B, must not be present in subsequence E1 Securities Movement and E2
Cash Movement
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.
E96
MT 575
Within subsequence B1a, subsequence B1a2 and subsequence B1a3 are mutually exclusive.
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
MT 509
In sequence B, if field :95L::ALTE is present, then field :95a::ACOW must be present.
MT 527
In each occurrence of subsequence A1, if field :95L::ALTA is present, then field :95a::ACOW must be
present.
MT 537
In sequence A, if field :95L::ALTE is present, then field :95a::ACOW must be present.
In each occurrence of sequence D, if field :95L::ALTE is present, then field :95P::ASDP must be present
in the same occurrence of the sequence D.
In each occurrence of subsequence D1a, if field :95L::ALTE is present, then field :95a::ASDP must be
present in the same occurrence of the subsequence D1a.
In each occurrence of subsequence D1a, if field :95L::ALRP is present, then field :95a::REPA must be
present in the same occurrence of the subsequence D1a.
MT 548
In sequence B, if field :95L::ALTE is present, then field :95a::ACOW must be present.
In sequence C, if field :95L::ALTE is present, then field :95P::ASDP must be present.
In subsequence C1a, if field :95L::ALTE is present, then field :95a::ASDP must be present.
In subsequence C1a, if field :95L::ALRP is present, then field :95a::REPA must be present.
MT 558
In each occurrence of subsequence A1, if field :95L::ALTA is present, then field :95a::ACOW must be
present.
MT 569
In each occurrence of subsequence C1a1A, if field :95L::ALTE is present, then field :95a::ACOW must be
present in the same occurrence of the subsequence C1a1A.
MT 575
In sequence A, if field :95L::ALTE is present, then field :95a::ACOW must be present.
In each occurrence of sequence B, if field :95L::ALTE is present, then field :95a::ACOW must be present
in the same occurrence of the sequence B.
In subsequence C2, if field :95L::ALTE is present, then field :95a::ACOW must be present.
E99
MT 502
In sequence B, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
In sequence B, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence B2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence C1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence C2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence D, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 509
In each occurrence of subsequence B1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 513
In each occurrence of subsequence B1, field :94a::TRAD must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence C2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence D1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence D2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence E, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence C2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence D, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 515
In each occurrence of sequence B, field :94a::TRAD must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence C1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence D1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence D2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence E, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 535
In each occurrence of sequence B, field :94a::SAFE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence B1b, field :94a::PLED must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::PLED).
In each occurrence of subsequence B1b, field :94a::SAFE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::SAFE).
MT 536
In each occurrence of sequence B, field :94a::SAFE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::SAFE).
In subsequence B1a2, field :94a::CLEA must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::CLEA).
In subsequence B1a2, field :94a::SAFE must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::SAFE).
In subsequence B1a2, field :94a::TRAD must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::TRAD).
MT 537
In subsequence B2b, field :94a::CLEA must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::CLEA).
In subsequence B2b, field :94a::SAFE must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::SAFE).
In subsequence B2b, field :94a::TRAD must not be present more than twice. When repeated, one and
only one occurrence must be with letter option L (:94L::TRAD).
In subsequence C2, field :94a::CLEA must not be present more than twice. When repeated, one and only
one occurrence must be with letter option L (:94L::CLEA).
In subsequence C2, field :94a::SAFE must not be present more than twice. When repeated, one and only
one occurrence must be with letter option L (:94L::SAFE).
In subsequence C2, field :94a::TRAD must not be present more than twice. When repeated, one and only
one occurrence must be with letter option L (:94L::TRAD).
MTs 540-47
In sequence B, field :94a::CLEA must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::CLEA).
In sequence B, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence E1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence E2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence F, field :95a::ALTE must not be present more than twice. When repeated,
one and only one occurrence must be with letter option L (:95L::ALTE).
MT 548
In sequence B, field :94a::CLEA must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::CLEA).
In sequence B, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In sequence B, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
MT 576
In each occurrence of subsequence B2c, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 578
In sequence B, field :94a::CLEA must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::CLEA).
In sequence B, field :94a::TRAD must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::TRAD).
In sequence C, field :94a::SAFE must not be present more than twice. When repeated, one and only one
occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence E1, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of subsequence E2, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
MT 586
In each occurrence of sequence B, field :94a::CLEA must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::CLEA).
In each occurrence of sequence B, field :94a::TRAD must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:94L::TRAD).
In subsequence B4, field :94a::SAFE must not be present more than twice. When repeated, one and only
one occurrence must be with letter option L (:94L::SAFE).
In each occurrence of subsequence B6a, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
In each occurrence of sequence C, field :95a::ALTE must not be present more than twice. When
repeated, one and only one occurrence must be with letter option L (:95L::ALTE).
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.
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.
G05
If 2 LVTS members (that is sender and receiver are LVTS subscribers and the first six characters of their
destination id, that is connected 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.
G06
Available.
G26
MT 502
The following qualifiers and codes must only be used in messages where both the sender and the
receiver are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of
the Funds CUG and that send the MT 502 with any of these listed qualifiers and codes will receive a
NAK:
• Sequence B, ORDRDET, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM, SUBS,
SWIF, SWIT)
• Sequence B, ORDRDET, field 22H, qualifier CAOP
• Sequence B, ORDRDET, field 98a, qualifier NAVD
• Sequence B, ORDRDET, field 92A, qualifier SWRT
• Sequence C, SETDET, field 22F, qualifier SETR, funds code (REDM, SUBS)
MT 509
The following qualifiers and codes must only be used in messages where both the sender and the
receiver are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of
the Funds CUG and that send the MT 509 with any of these listed qualifiers and codes will receive a
NAK:
• Sequence B, TRADE, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM, SUBS,
SWIF, SWIT)
MT 515
The following qualifiers and codes must only be used in messages where both the sender and the
receiver are members of the FIN Funds Closed User Group (CUG). Institutions that are not members of
the Funds CUG and that send the MT 515 with any of these listed qualifiers and codes will receive a
NAK:
• Sequence C, CONFDET, field 98a, qualifier NAVD
• Sequence C, CONFDET, field 92A, qualifier (BAKL, ENTF, NAVR)
• Sequence C, CONFDET, field 22H, qualifier BUSE, funds code (CROF, CROT, DIVR, REDM, SUBS,
SWIF, SWIT)
G27
Use of field 111 is restricted to specific gpi Closed User Groups. Use of field 121 is also restricted to
messages used in the context of Swift services with the exception of MT 103, MT 103 REMIT, MT 103
STP, MT 202, MT 202 COV, MT 205, MT 205 COV, MT 190, MT 191, MT 192, MT 195, MT 196, MT 199,
MT 292, MT 295, MT 296, MT 299, MT 992, MT 995, MT 996, and MT 999.
G28
A request for cancellation was received for this message. See KB article 5023053 for more information.
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.
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.
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 sender 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 sender is CLS or CLT member and
receiver is not, and field 34R is present, then field 57A must contain CLSB****; when sender 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.
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 - H09
Available.
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 identifier.
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.
H40
This priority does not exist for this message category.
H50
Destination address error:
• Destination not known to the system (includes branch identifier)
• 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 and
Training user in full function mode sending MT 073
• Sender or Receiver BIC is reserved for use in a FINCopy service
• FIN restricts the use of certain message types to Message User Group (MUG) members
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 KB article 5018412.
H52
MT 072, selection of Test and Training mode/version, MT 077 Additional Selection Criteria for FIN are not
allowed while a FIN session is open.
H53
The authorisation to send is revoked by receiver.
H54
The authorisation to send does not exist, it has been rejected or it has expired.
H55
The user is not allowed to send user-to-user messages.
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).
Knn
Code error in a generic field.
The 2 digits "nn" indicate the field id.
The invalid code is located either:
• right after the Data Source Scheme, that is, after the ending "/", for example:
- K17 MT 500 subsequence B1 :17B::CALL//A (reject A)
- K22 MT 500 sequence A :22F::INST//DERA (reject DERA)
- K90 MT 500 subsequence B1 :90B::INDC//ACTA/USD123, (reject ACTA)
- K93 MT 564 subsequence B2 :93C::BLOK//FAMA/ELIG/123, (reject FAMA)
• or further into the field, for example:
- K93 MT 564 subsequence B2 :93C::BLOK//FAMT/ELIA/123, (reject ELIA)
This check applies to:
• MTs 321, 370, 380, 381, 500-510, 513-515, 517-519, 524, 527, 530, 535-538, 540-549, 558, 564-569,
575, 576, 578, and 586.
Note K17 applies also to field :17B:: in MTs n92, n95, and n96.
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.
L06
Login request received when system maintenance is in progress.
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 primary destination does not belong to Sign Distinguished Name (DN)
organisation.
L55
Login NAK error code (field 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.
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 primary 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.
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.
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}.
N15
Multiple currencies not allowed in balance checkpoint. Found {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}.
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.
N48
Participant {0} owns template(s) and cannot be deleted.
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.
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 primary destination does not belong to Sign Distinguished Name (DN)
organisation.
PRI
Timeout expired on a response to a primitive sent to the user.
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.
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 primary BIC 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 identifier.
S71
Signature syntax error.
S72
Signature semantic error.
S76
Session aborted because subsets sharing mode change was requested using MT 077.
S07
Select request received when system maintenance is in progress.
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.
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 and 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 primary 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.
S66
Select ACKs contain invalid field tag.
S68
Invalid association identification.
T00
Not used.
T01
Code error.
This check applies to:
• field 39B in any message appended in common group MTs n92, n95, n96
T02
Unable to ascertain reason for NAK.
Contact your Customer Support Centre immediately for advice.
T03
Code error.
This check applies to:
• subfield 3, field 26C in MTs 600, 601, 604, 605, 606, 607, 608, and 620
• field 48B in MT 760, or in any message appended in common group MTs n92, n95, or n96
T04
Code error.
This check applies to:
• subfield 4, field 26C in MTs 600, 601, 604, 605, 606, 607, 608, and 620
• field 48D in MT 760, or in any message appended in common group MTs n92, n95, or n96
T05
Code error.
This check applies to:
• subfield 4, field 68B in common group MTs n92, n95, and n96
T06
Code error.
This check applies to:
• subfield 1 field 32F in MTs 600, 601, 604, 605, 606, 607, and 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 and 65 in MT 608
• or any of the above fields in common group MTs n92, n95, or n96
• or subfield 5, fields 68B and 68C in common group MTs n92, n95, and n96
T07
Code error.
This check applies to:
• subfield 3, field 33G in MT 600
T08
Code error.
This check applies to:
• field 23 in MT 102 STP
• field 23F in MT 760, or in any message appended in common group MTs n92, n95; or n96
• field 71A in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 104, 107, 740, or in any message
appended in common group MTs n92, n95, or n96
T09
Code error.
This check applies to:
• subfield 3, field 23 in MT 305
• subfields 1, 2, 3, and 4 in MT 601
• subfield 3, field 68C in common group MTs n92, n95, and 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.
This check applies to field 71F, subfield 2 in MT 103.
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 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, index points, number,
number count component, price, or UTC indicator is equal to zero.
This check applies to:
• field 19A in MTs 321, 370, 502, 506, 508, 509, 513, 514, 515, 518, 527, 530, 535, 536, 537, 538, 540,
541, 542, 543, 544, 545, 546, 547, 548, 558, 569, 575, 578, and 586
• field 19C in MT 306
• field 32H in MTs 300, 306, 320, 330, 340, 362, and 620
• field 32R in MT 620
• field 34C in MT 300, 304, 305, 306, 320, 330, 340, 341, 360, 361, 600, and 601
• field 34E in MTs 320, 330, 341, and 620
• field 34J in MT 620
• field 35H in MT 581
• field 36E in MT 564
• field 37G in MTs 320, 330, 360-362, 364, 365, and 620
• field 37H in MT 935
• field 37M in MTs 340, 341, 350, 360-362, 364, and 365
• field 37R in MTs 341, 360, 361, and 362
• field 37V in MTs 360-362
• field 90A in MTs 500-502, 506, 508, 509, 513-515, 518, 519, 524,530, 535, 536, 537, 538, 540-547,
548, 564-566, 569, 576, 578, and 586
• field 90L in MTs 564-566
• field 92A in MTs 321, 500, 501, 502, 506, 508, 513, 514, 515, 518, 519, 524, 527, 535, 537, 538, 540,
541, 542, 543, 544, 545, 546, 547, 548, 558, 564, 565, 566, 568, 569, 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 93E in MTs 535, 564, 565, 566, and 568
• field 93F in MTs 501, 535, 564, 565, 566, 567, and 568
• field 98D in MTs 300, 304, 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,
565, 566, 567, 568, 569, 575, 576, 578, and 586
• field 98G in MTs 300 and 304
• field 98H in MTs 300 and 304
• field 99A in MTs 370, 506, 513, 514, 515, 518, 535, 536, 537, 540, 541, 542, 543, 544, 545, 546, 547,
548, 564, 566, 569, 575, 578, and 586
• any of the above fields in common group MTs n92, n95, and n96
T15
Subfield Sign must be either + or -.
T16
Time offset is not valid. Offset and time have the same format of HHMM, where 00<=HH<=13 and
00<=MM<=59.
T17
Field, line, subfield, or component consists of blanks, ("CrLf") or missing mandatory line, subfield or
component.
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 also error
code 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 error.
This check applies to:
• subfield 1, component 3, field 32K in MTs 400, 410, 416, 420, 422, and 430 or 33K in MT 430
T21
Code 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 D, or field 37J, sequence F, in MT 306
• field 37G, sequence B, in MTs 320 and 330
• field 37M, sequence B, in MTs 340, 341, and 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, 26B, or 35C 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, 26B, or 35C 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, 26B, or 35C 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, 20D, and 20U
• fields 21, 21A, 21F, 21G, 21H, 21P, and 21R
• field 22W
• field 94B
• fields 95Q, 95R, 95S, 95T, 95U, and 95V
• field 98K
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
BIC is not a valid FIN destination.
T29
Connected BIC contains an invalid branch identifier.
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:
In this case, ";" is not part of the X-character set; "^" is not part of the X-character set.
T33
Field, line or subfield error.
• Length of field, line, subfield, or component contents is too long.
Example:
Where:
- "e" = blank (space) character
- "1" = numeric character
- ":" = special character (not an alphabetic character)
- ";" = Not in the X-character set
T34
Length of field, line, subfield, or component contents is too short, or a character does not belong to the
right character set.
T35
Code error.
This check applies to:
• subfield 1, field 26C in MTs 600, 601, 604, 605, 606, 607, 608, and 620
T36
Code error.
This check applies to:
• field 14A in MTs 360 and 361
• field 14D in MTs 320, 330, 340, 350, 360, 361, and 620, or in any message appended in common
group MTs n92, n95, or n96
• field 14H in MT 306
T37
Code error.
This check applies to:
• subfield 2, field 35H contains an invalid code or currency code, when used with MT 581, and with any
message appended in common group MTs n92, n95, or n96
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, 304, 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, 575, 576, 578, and 586
• field 98G in MTs 300 and 304
• field 98H in MTs 300 and 304
T40
Missing amount/number or incorrect amount/number first character.
T41
Code error.
This check applies to:
• field 14B in MT 306 or in any message appended in common group MTs n92, n95, or n96
T42
Available.
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 connected BIC exists but it is not enabled for FIN, or the BIC is active but is not published in the
current BIC Plus directory, or it is not cutover. Except for gpi messages with the non-cutover connected
BIC in block 4 that are sent to and from gpi Tracker BICs that is, user-to-Tracker (U2T) and Tracker-to-
user (T2U) messages. This exception is extended to gpi user-to-user messages, when the service code
in field 111 is "003" and "007" (that is, g4CPT and g4CIT).
T45
Invalid non-connected BIC.
T46
A Test and Training destination must not be used in a live message.
T47
The data part of a code /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 error. This check applies to:
• subfield 1, field 14G in MTs 360, 361, and in common group MTs n92, n95, and n96
• field 14N in MT 306
• subfield 1, field 22 in MT 305
• subfield 1, field 23A in MTs 360, 361, 362, 364, 365, or in any message appended in common group
MTs n92, n95, or n96
• subfield 1, field 23E in MTs 101, 103, 103 REMIT, 104, 107, 416, and in common group MTs n92, n95,
and n96
• subfield 9, field 61, duplicated codes: /OCMT/ or /CHGS/
• field 72 (narrative), duplicated codes: /OCMT/ or /CHGS/
• field 72 (structured), duplicated codes: /OCMT/ or /CHGS/or /INS/
• field 77A, duplicated codes: /OCMT/ or /CHGS/
• subfield 1, field 77H in MTs 300, 304, 305, 306, 340, 360, 361, 600, 601, and in common group MTs
n92, n95, and n96
• field 79, duplicated codes: /OCMT/ or /CHGS/
• field 86, duplicated codes: /OCMT/ or /CHGS/
• subfield 1, field 39P in common group MTs n92, n95, and n96
T48
Code error.
This check applies to:
• subfield 2, field 14G in MTs 360 and 361
• subfield 1, field 22K in MTs 306 and 760 or in any message appended in common group
• field 22Y in MT 760
• subfield 2, field 23A in MTs 360, 361, 362, 364, 365, or in any message appended in common group
MTs n92, n95, or n96
• field 23C in MT 306 or in any message appended in common groupMTs n92, n95, or n96
• field 23D in MTs 340 and 341
• subfield 1, field 23E in MT 103 STP
• field 23H in MT 759 or in any message appended in common group MTs n92, n95, or n96
• field 23R in MT 787 or in any message appended in common group MTs n92, n95, or n96
• 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
• subfield 1, field 73R in MT 744 or in any message appended in common group MTs n92, n95, or n96
T49
Any line in field 72 must not start with code /PUSI/, /PUTI/, /USI/, or /UTI/.
This check applies to:
• MTs 300, 304, 305, 306, 340, 341, 360, 361, 600, and 601
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:
• 01-60 for the years 2001-2060
This list is not exhaustive this check applies to:
• field 30 in MTs: 101, 104, 107, 110, 111, 112, 201, 203, 204, 210, 760, and 786
• field 32A in MTs: 102, 102 STP, 103, 103 REMIT, 103 STP, 110, 111, 112, 200, 202, 202 COV, 205,
205 COV, and 910
In addition, the following also apply:
• The value 0000 is invalid in the year format YYYY.
• Date in field 50F must not be later than the date, local to the Sender, on which the message is
successfully sent.
• Date in MT 670, field 98A must not be earlier than the date, local to the Sender, on which the message
is successfully sent.
T51
Code "C", "D", "RC", "RD", "EC", or "ED" error.
T52
Invalid currency code or price code PCT, REN, or YLD.
T53
Code error.
This check applies to:
• component 1, subfield 6 of field 61 in MTs 608, 940, 942, 950, 970, and 972.
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, 110, 202 COV, 205 COV, 210, and 910
This check applies to all MTs that contain field 50F, when appended to common group MTs n92, n95, and
n96.
T55
Code error.
This check applies to subfield 1, component 1:
• field 50F in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 110, 202 COV, 205 COV, 210, and 910
This check applies to all MTs that contain field 50F, when appended to common group MTs n92, n95, and
n96.
T56
Code 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, 110, 202 COV, 205 COV, 210, and 910
This check applies to all MTs that contain field 50F, when appended to common group MTs n92, n95, and
n96.
Syntax error or format error.
This check applies to subfield 2, lines 1-4:
• field 59F in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 110, 202 COV, and 205 COV
This check applies to all MTs that contain field 59F, when appended to common group MTs n92, n95, and
n96.
Syntax error or format error.
This check applies to subfield 1 and subfield 3, lines 5-35:
• field 79 in MT 199 (Swift gpi - g4CPT)
Syntax error or format error.
T57
Code error.
This check applies to:
• subfield 1 of field 31X in MT 516
T58
Code error.
This check applies to:
• subfield 1 field 35A in MTs 516, 526, and 559, 35N in MT 516, or 35S in MT 516
T59
Code error.
This check applies to:
• field 24E in MT 760 and in sequences B and C of MT 767
• subfield 1 field 40E in MTs 700, 707, 710, and 720
• field 40F in MT 740
• or any of the above fields in common group MTs n92, n95, or n96
T60
Code error.
This check applies to:
• field 24G in MT 760 and in sequences B and C of MT 767
• field 26F in MTs 305, 306, and 601
• field 40A in MTs 700,705, and 707
• field 40B in MT 710
• subfield 1 field 40C in MT 760
• subfield 1 field 73S in MT 744
• or any of the above fields in common group MTs n92, n95, or n96
• subfield 1 field 77B in MT 734
T61
Code "D" or "M" error.
T62
Either the first subfield ([YYMMDD[HHMM]]) or the second subfield (7!a), but not both, must be present. If
optional subfield 1 is used, component 1 YYMMDD of this subfield must be present. This check applies to
field 31X in MT 516.
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 that contain field 22 or field 22C, when appended to common group MTs n92, n95, and n96
T64
Code error.
This check applies to:
• field 12F in MT 306
• line 1, field 40B in MT 720
• field 43P, in MT 700, 707, 710, and 720
• or any of the above fields in common group MTs n92, n95, or n96
T65
Code error. This check applies to:
• field 12D in MT 306
• field 43T, in MT 700, 707, 710, and 720
• or any of the above fields in common group MTs n92, n95, or n96
T66
Code error.
T67
Code error.
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 45B, subfield 1, in any line that starts with a slash, in MT 707 or MT 708
• field 47B, subfield 1, in any line that starts with a slash, in MT 707 or MT 708
• field 49 in MTs 700, 707, 710, 720, and 760
• field 49A in MT 765
• field 71N, subfield 1, in MT 707
• or any of the above fields in common group MTs n92, n95, or n96
• field 49N, subfield 1 in any line that starts with a slash, in MT 707 or MT 708
T68
Code 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, 707, 710, 720, and 740
• subfield 2, field 41D in MTs 700, 705, 707, 710, 720, and 740
• or any of the above fields in common group MTs n92, n95, or n96
T69
Sign [N] (negative indicator) may only be present if subfield 2, Percentage Type Code is YIEL.
T70
MT 300
In sequence A, if field 77D is present then /FIX/, /SETC/, /SRCE/ or /VALD/ must not be present at the
start of any line.
In sequence C, if field 72 is present then /FIX/, /SETC/, /SRCE/ or /VALD/ must not be present at the start
of any line.
MT 304
In sequence C, if field 72 is present then /FIX/, /SETC/, /SRCE/ or /VALD/ must not be present at the start
of any line.
MT 305
In sequence A, if field 72 is present then /SETC/ or /VALD/ must not be present at the start of any line.
T71
Code error.
This check applies to:
• field 22D in MTs 360, 361, 364, 365, 759, and 760
• field 22G in MTs 306 and 765
• or any of the above fields in common group MTs n92, n95, or n96
T72
Code error.
This check applies to:
• field 22J in MT 306
T73
Invalid country code. The list of country codes is available in the BIC Plus directory, which is available on
www.swiftrefdata.com.
This check applies to:
• field 39M in MT 300, 304, 305, 306, 320, 330, 340, 341, 360, and 361
• field 44J in MT 760
• field 50F in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 110, 202 COV, 205 COV, 210, and 910
• field 59F in MTs 101, 102, 102 STP, 103, 103 REMIT, 103 STP, 110, 202 COV, and 205 COV
• field 59, 59A, and 59F subfield IBAN in MTs 102 STP and 103 STP
• field 94C, 2!a (Country Code) in MTs 321, 380, 381, 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, 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, and 535
• 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
Available.
T75
Invalid value
• field 27, subfield 1 must be "1"; subfield 2 must be within the range 1-8 in MTs 700, 707, 710, 720,
760, and 767
• field 27, subfield 1 and subfield 2 both must be within the range 2-8; subfield 1 must be less than or
equal to subfield 2 in MTs 701, 708, 711, 721, 761, and 775
• field 27, subfield 1 and subfield 2 both must be within the range 1-8; subfield 1 must be less than or
equal to subfield 2 in MT 759
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:
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.
T78
Invalid or duplicated code, or a mandatory code is missing.
This check applies to:
• subfield 1 of each line, field 53J in MTs 300, 304, 305, 306, 320, 330, 340, 341, 350, 600, 601, and
620
• subfield 1 of each line, field 56J in MTs 300, 304, 305, 306, 320, 330, 340, 341, 350, 600, 601, and
620
• subfield 1 of each line, field 57J in MTs 300, 304, 305, 306, 320, 330, 340, 341, 350, 600, 601, and
620
• subfield 1 of each line, field 58J in MTs 300, 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, 304, 305, 306, 320, 330, 350, 600, 601, and 620
• subfield 1 of each line, field 83J in MTs 300, 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, 306, 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, 304, 305, 306, 320, 330, 350, 600, 601, and 620
• subfield 1 of each line, field 88J in MTs 300, 306, 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
Subfield or code missing
• field 73S, subfield 2 is mandatory if subfield 1 is HOLD, in MT 744
• field 53J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
• field 56J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
• field 57J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
• field 58J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, and 306
• field 82J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
• field 83J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
• field 86J, at least one other code is mandatory if subfield 1 is ABIC in MT 306
• field 87J, at least one other code is mandatory if subfield 1 is ABIC, in MTs 300, 304, 305, 306, 600,
and 601
T80
Field 72 or field 79 is used with Reject/Return information and one or more of the following conditions has
occurred:
• code error, or
• mandatory code is missing, or
• code not in the proper sequence.
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 in 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 in MTs 102 STP and 103 STP
T83
Code error.
Field 76, line 1, subfield 1 in MT 196 (SRP) and MT 296 (SRP).
Field 79, line 1, subfield 1 in MT 192 (SRP), MT 199 (SRP), MT 199 (CASE), MT 292 (SRP), MT 299
(SRP), and MT 299 (CASE).
Field 79, line 1, subfield 3 in MT 199 (CASE) and MT 299 (CASE).
Field 79, line 2, subfield 1 in MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift
Go), MT 199 (Universal Confirmations), MT 199 (Swift gpi - g4CPT), MT 199 (Swift gpi - g4CIT), MT 199
(Swift gpi - g4CF), MT 299 (Swift gpi - gCOV), and MT 299 (Swift gpi - gFIT).
Field 79, line 3, subfield 3, in MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift
Go), MT 199 (Universal Confirmations), MT 299 (Swift gpi - gCOV), and MT 299 (Swift gpi - gFIT).
Field 79, line 4, subfield 2, in MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift
Go), and MT 199 (Universal Confirmations).
Field 23B, MT 103 (Swift Go).
Field 71A, MT 103 (Swift Go).
T84
Code error.
Field 76, line 1, subfield 2 in MT 196 (SRP) and MT 296 (SRP).
Field 79, line 1, subfield 2 in MT 192 (SRP), MT 199 (SRP), MT 292 (SRP), and MT 299 (SRP).
Field 79, line 2, subfield 2 in MT 199 (Swift gpi - gCCT), MT 199 (Swift gpi - gCCT Inst), MT 199 (Swift
Go), MT 199 (Universal Confirmations), MT 199 (Swift gpi - g4CPT), MT 199 (Swift gpi - g4CIT), MT 299
(Swift gpi - gCOV), and MT 299 (Swift gpi - gFIT).
Field 79, line 3, subfield 1 in MT 199 and MT 299 (CASE).
T85
Code error.
This check applies to :
• field 23G, subfield 2, in MTs 321, 370, 380, 381, 500-510, 513-515, 517-519, 524, 527, 530, 535-538,
540-549, 558, 564-569, 575, 576, 578, 586, 670, or in any message appended in common group MTs
n92, n95, or n96
T86
Code error.
This check applies to:
• subfield 1, field 23G in MTs 321, 370, 380, 381, 500-510, 513, 514, 515, 517-519, 524, 527, 530, 535,
536, 537, 538, 540-549, 558, 564-569, 575, 576, 578, 586, 670, or in any message appended in
common group MTs 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 error.
This check applies to:
• field 16R in ISO 15022 MTs
• field 16S in ISO 15022 MTs
T93
Code error.
This check applies to
• field 22B in MTs 320, 330, 364, 365, and 620
• field 23S in MTs 707 and 767
• field 23X in MTs 759, 760, 765, 767, 768, 769, 785, 786, and 787
• field 30J, subfield 1, in MT 306,
• field 46B, subfield 1, in any line that starts with a slash, in MTs 707 and 708
• or any of the above fields in common group MTs n92, n95, or n96
• field 49M, subfield 1, in any line that starts with a slash, in MTs 707 and 708
T94
In field 22, subfield 2, or in field 22C, components 1 and 3, the digit "0" is allowed in the rightmost position
of the party suffixes but only if the sender is a Test and Training user.
This check is applied only to common group messages.
T95
In field 22 or in field 22C, the first six characters do not consist of the party prefix and party suffix of the
Sender's or Receiver's BICs and/or the last six characters do not consist of the party prefix and party
suffix of the Sender's or Receiver's BICs.
This check is applied only to non-common group messages.
T96
In field 22 or in field 22C, the code in the first six characters and the code in the last six characters are not
in alphabetic order.
T97
Code error.
This check applies to:
• subfield 2, field 28E in MTs 506, 515, 527, 535, 536, 537, 538, 558, 564, 568, 569, 575, 576, and 586
T98
Available.
T99
Available.
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
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 in field 119, or field 119 is missing.
U09
Special validation is undefined for this message type.
User has used field 119 in a message that is not a candidate for special processing.
Sender or receiver is not part of the MT 103 REMIT Message User Group.
U10
Invalid syntax, format, date, time in field 423.
U11
Invalid message input reference format in field 106.
U12
Incorrect order of fields 111 and 121; or field 111 is present without field 121; or both fields 111 and 121
are required; or field 121 is present without filed 111 in a message specific to the Swift gpi service; or field
111 is not allowed.
U13
Mandatory field 121 is missing from header block 3 of the message; or invalid syntax or format of field
121, field 121 must be formatted as xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx where x is any hexadecimal
character (lower case only) and y is one of 8, 9, a, or b.
U14
Field 111 contains an invalid service identifier or is wrongly formatted.
For MT 103 if field 111 is present, then it must be either "001", "005", or "009".
For MT 103 STP and MT 103 REMIT if field 111 is present, then it must be either "001" or "005".
For MT 202 COV and MT 205 COV if field 111 is present, then it must be "001".
For MT 202 and MT 205 if field 111 is present, then it must be "004".
For MT 199 if field 111 is present, then it must be either "001", "002", "003", "005", "006", "007", "008", or
"009".
Note Only MT 199 can have "009" when sent from Swift Go user to the Tracker. Only MT 103 can
have "009" when sent between Swift Go participants.
For MT 192 and MT 196 if field 111 is present, then it must be "002".
For MT 299 if field 111 is present, then it must be either "001", "002", "004", or "006".
For MT 292 and MT 296, if field 111 is present, then it must be "002".
U15
The content of field 121 has already been used for a different transaction.
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.
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.
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 103 are allowed in MT 047.
V63
Branch identifier with same priority assigned to more than one delivery subset.
V64
Incorrect or invalid branch identifier specified in MT 047.
V65
Invalid combination of branch identifier - 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 348 or invalid value for field 348.
V70
Only category/message type/VAS code and branch identifiers can be combined.
This error code will be returned if both the following conditions are true for a specific subset:
1. The subset contains field 349 with value 1 AND
2. The subset contains field 347
V71
Incomplete combined criteria.
This error code will be returned if a subset has field 349 with value 1 AND any of the following conditions
is true:
1. The subset does not contain field 346 (branch identifier) 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 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.
V99
System undergoing major recovery or system not completely synchronised yet, or the destination, or
some message types are being intercepted.
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.
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 copy server destination for the service requested or mismatch between contents of fields
103 and 165.
X21
Message type is not allowed in this service mode.
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 or it was not possible to create
the copy message as none of the fields were found in the original message.
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).
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).
Y01
Checksum failure.
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.
FIN Errors
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.
Abort Codes
Introduction
An abort code is composed of five alphanumeric characters with the structure
<origin><layer><reason> where:
An abort code is sometimes accompanied by an "abort diagnostic", which is a string that provides more
details on the error.
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):
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.
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.
Introduction
This section details the abort diagnostic codes for the FIN application layer.
Introduction
This section details the abort diagnostic codes for the Application Control application layer.
Introduction
This section details the abort diagnostic codes for the Logical Terminal Control application layer.
Introduction
This section lists and describes the abort diagnostic codes that occur in other layers that are internal to
FIN.
Legal Notices
Copyright
SWIFT © 2023. All rights reserved.
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. SC. The following are registered trademarks of SWIFT: 3SKey,
Innotribe, MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the Standards Forum logo, the
SWIFT logo, SWIFT gpi with logo, the SWIFT gpi logo, and UETR. Other product, service, or company
names in this publication are trade names, trademarks, or registered trademarks of their respective
owners.