Text Validation Error Codes
If you receive a text validation error while you are programming in SWIFT, use the error code to obtain a description of how the validation is handled and enforced.
The following table contains the error codes for SWIFT text validation:
|SWIFT Error Code||Translator Report Error Number||Error Description|
|M50||901||Message length exceeded|
|M60||902||Non-SWIFT character encountered (a character not included in the <X>, <Y>, <Z> character sets. Also see error code T32.)|
|T01||904||Code word error. This check applies to:
|T02||905||Unable to determine the reason for NAK. Please contact your CSC immediately for advice.|
|T03||906||Code word error. This check applies to:
|T04||907||Code word error. This check applies to:
|T05||908||Code word error. This check applies to:
|T06||909||Code word error. This check applies to:
|T07||910||Code word error. This check applies to:
Subfield 3, field 33G.
Field :22H:INOU subfield 3 in MT503,505,527,558.
|T08||911||Code word error. This check applies to:
|T09||912||Code word error. This check applies to:
|T10||913||The repetitive sequence occurred more than the maximum number of times permitted.|
|T11||914||The repetitive sequence occurred less than the minimum number of times required.|
|T12||915||Field, line, subfield, or component content error. Or, the format Reject/Return is not allowed for field 72 in this MT. Or, when "ISIN" is used at the beginning of line one in field 35B it must never be composed of lower-case letters, nor a mix of upper and lower-case letters. Or, in the ISITC MT521 or MT523 in field 35B the second line is mandatory and must not begin with any of the code words defined for the third and subsequent lines.|
|T13||916||The field tag is not expected at this location in this MT.
Either a mandatory field is missing, the sequence of fields is not
correct, the specified field is not allowed at this point in the MT,
or the specified field is not a defined SWIFT field (for example,
the field tag is invalid), an end-of-text sequence (CRLF-) was encountered
when it was not expected, or more than one end-of-text sequence occurs
in this message.
Or in a common group message (i.e. n92,n95,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 following ISO15022 messages: MT502, 503, 504, 505, 506, 507, 508, 509, 513, 514, 515, 518, 524, 527, 528, 529, 530, 535, 536, 537, 538, 540, 541, 542, 543, 544, 545, 546, 547, 548, 549, 558, 564, 565, 566, 567, 568, 569, 575, 576, 578, 584, 586, 587, 588, 589, an optional sequence of fields was used, however a field or field qualifier which is required within that sequence is missing, or field 16R is present but its related code word is inappropriate.
Or in a qualifier table, for a particular generic field, 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.
|T14||917||Subfield[N] (negative indicator) must not be used when the
amount, number, or number count component is equal to zero. This check
|T15||918||Sign is not valid. <SIGN> must be either '+' or '-'.|
|T16||919||Time offset is not valid. <OFFSET> has the same format as time <HHMM>.|
|T17||920||Field, line, subfield, or component consists of blanks, <CRLF>, or it is missing a mandatory line, subfield, or component.|
|T18||921||Component is not in the format 3!n and/or it is not within
the range 100-999. This check applies to:
|T19||922||Code word error. This check applies to:
|T20||923||Code word error in subfield 1, component 3, of field 32K or 33K.|
|T22||925||A common reference mismatch exists between field 22, subfield
2, component 2 and one of the following:
Or, a common reference mismatch exists between field 22C, component 2, and one of the following:
|T23||926||Subfield 8 in field 61, subfield 5 in field 66A, or subfield 6 in field 26C is too long or contains only '//', or subfield 2 in fields 26A or 26B is too long or contains only '/'.|
|T24||927||Subfield 7 in field 61, subfield 4 in field 66A, subfield 5 in field 26C, subfield 1 in fields 26A or 26B is missing or is too long.|
|T25||928||Subfields 7 or 8 in field 61, subfield 4 or 5 in field 66A, subfield 5 or 6 in field 26C, subfield 1 or 2 in fields 26A or 26B has improper content.|
|T26||929||Subfield 7 or 8 in field 61, subfield 4 or 5 in field 66A,
subfield 5 or 6 in field 26C, subfield 1 or 2 in fields 26A or 26B
has improper content.
This check applies to:
|T27||930||BIC incorrectly formatted or invalid.|
|T28||931||SWIFT BIC is not a valid destination.|
|T29||932||SWIFT BIC contains an invalid branch code.|
|T30||933||Excessive lines, subfields, or components were found in this field.|
|T31||934||The line, subfield, or component separator or delimiter is missing or incorrect.|
|T32||935||An expected subfield, component, or component separator was not found.|
|T33||936||The length of the field, line, subfield, or component contents is too long, or, the component consists of one or more hidden characters, or, the component consists of one or more imbedded characters which are inconsistent with the defined field format, or the characters do not belong to the correct character set.|
|T34||937||The length of the field, line, subfield, or component contents is too short.|
|T35||938||Code word error in subfield 1, field 26C.|
|T36||939||Code word error. This check applies to:
|T37||940||Code word error. This check applies to:
|T38||941||Illogical time specified.|
|T39||942||Time of UTC Indicator (HH[MM]) is not in the valid range (00<=HH<=23,
00<=MM<=59). This check applies to:
|T40||943||Missing amount/number or incorrect amount/number first character.|
|T41||944||Code word error in subfield 3, field 66A.|
|T42||945||Code word error in subfield 3, field 35U.|
|T43||946||The decimal separator in the amount/number subfield or component is missing, is not a valid character, or more than one separator is present.|
|T44||947||The SWIFT BIC exists but it is not enabled for FIN, or the BIC is active but it is not published in the current BIC directory, or it is not cutover.|
|T45||948||Invalid non-SWIFT BIC.|
|T46||949||A Test-and-Training destination must not be used in a LIVE message.|
|T47||950||In an ERI field the data part of a code word /OCMT/, or /CHGS/
was being validated but the ending separator (such as, the third '/')
is missing. This error is also a code word error that applies to:
|T48||951||Code word error. This check applies to:
|T50||953||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
The valid range for <YY> is:
00-60 for the years 2000-2060
80-99 for the years 1980-1999
This check applies to:
|T51||954||Code word 'C','D','RC','RD','EC','ED' error.|
|T52||955||Invalid currency code or price code 'PCT','REN', or 'YLD'.|
|T53||956||Code word error in subfield 6, component 1 of field 61.|
|T54||957||The format of the first line of Field 50F (Party Identifier)
is invalid. This check applies to:
|T55||958||Code word error. This check applies to Subfield 1, component
|T56||959||Code word error. This check applies to Subfield 2, component
|T57||960||Code word error in subfield 2 of fields 31H, 31J, or 31X.|
|T58||961||Code word error. This check applies to:
|T60||963||Code word error. This check applies to:
|T61||964||Code word 'D' or 'M' error. This check applies to:
|T62||965||Either the first subfield <DATE2>[<HHMM>] or the
second subfield 7!a but not both must be present. If optional subfield
1 is used, component 1 <DATE2> of this subfield must be present.
This check applies to:
|T63||966||Error in component 2 of field 22C or subfield 2, component 2, of field 22. When the last character of this component is zero '0' and the preceding character is not one '1' then the entire component must consist of zeros.|
|T64||967||Code word error. This check applies to:
|T66||969||Code word error. This check applies to:
|T67||970||Code word error. This check applies to:
|T68||971||Code word error. This check applies to:
|T70||973||Either the Account number, the Place, or both must be present.|
|T71||974||Code word error. This check applies to:
|T72||975||Code word error. This check applies to:
Field 22J in MT306.
Field 23C, subfield 1, in MT405.
Field 23F, subfield 1, in MT405.
|T73||976||Invalid country code. Please refer to the BIC Directory General Information -Country Codes-.|
|T74||977||The currency code must be the same for each indicated subfield in the field.|
|T75||978||In MTs 405, n92, n95, n96:
Field 38B .
When subfields 1 and 2 contain "MONT/OTHR" then subfield 3 is mandatory, otherwise subfield 3 is not allowed.
|T76||979||The first character in the first line of this field must be a '/', and there must be at least another line, but not more than 5 lines. This check applies to field 50H.|
|T77||980||If the first character of the first line of this component
or sub-component is a '/', then there must be at least another line,
but not more than 5 lines. Otherwise, no more than 4 lines are allowed.
This check applies to:
Fields 42D,50K,(50-58)D,59,(82-88)D, and subfield 2 of field 87F.
|T78||981||Invalid or duplicated code word, or a mandatory code word is
This check applies to:
|T80||983||<Field 72 Reject/Return> or <Field 79 Reject Return> code word error, or mandatory code word missing, or code word not in proper sequence.|
|T81||984||Format of <Field 72 Reject/Return> is not allowed in
this message. This check applies to:
Field 72, MT102_STP,103_STP.
|T82||985||ERI format is not allowed in this message. This check applies to: Field 72, MT102_STP,103_STP.|
|T85||988||Code word error. This check applies to Field 23G, subfield 2, in MTs 307, 321, 380, 381, 500-510, 513-515, 517-519, 524, 527-529, 530, 535-538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586-589, or in any message appended in common groups n92, n95 or n96.|
|T86||989||Code word error. This check applies to:
Field 23G, subfield 1, in MTs 307, 321, 380, 381, 500-510, 513-515, 517-519, 524, 527-529, 530, 535-538, 540-549, 558, 564-569, 574IRSLST, 574W8BENO, 575, 576, 578, 584, 586-589, or in any message appended in common groups n92, n95 or n96.
|T87||990||In a generic field the colon ':' delimiter is not present at the expected position.|
|T88||991||Field 12 in MT570 may only consist of 571,572,573,577.
Field 12 in MT920 may only consist of 940,941,942,950.
Field 12 in MT973 may only consist of 971,972,998.
Field 13A in MT507 may only consist of 503,504,505.
Field 13A in MT549 may only consist of 509,535-538,548,567,575-577,584, 586,589.
|T89||992||In a generic field either the qualifier is invalid, the qualifier is duplicated, a mandatory qualifier is missing, or the qualifier format is not valid.|
|T90||993||In a generic field either the issuer code format is invalid, the mandatory issuer code is missing, or the generic field format is invalid.|
|T91||994||In a generic field the slash '/' delimiter is not present at the expected position.|
|T92||995||Code word error. This check applies to:
|T93||996||Code word error. This check applies to:
Field 22B in MT320,330,364,365.
|T94||997||In field 22, subfield 2, or in field 22C, the components 1 and 3, the values '0' and '1' are not permitted in <LC1> and <LC2>. However, the value '0' is allowed in the second (right-most) position if the sender or receiver is a test and training user.|
|T95||998||In field 22, subfield 2, or in field 22C, the components 1 and 3 do not contain the bank code and location code of the message sender, and/or the bank code and location code of the message receiver.|
|T96||999||In field 22, subfield 2, or in field 22C, the components 1 and 3 are not in alphabetical sequence.|
|T97||1000||Code word error. This check applies to:
Field 28E, subfield 2, in MT206,506,535-538,569,574WBENO,574IRSLST,575, 576,584,586.
|T99||1002||A special function has been declared in the validation syntax
that is not recognized.
Note: If you receive this error, it indicates that a special function was declared in a syntax that was not recognized by the translator.