SWIFT MT Library Own Error Messages

Code Error Message
SV00 Swift Validator Error
SV01 Field length exceeded
SV02 Code word must be placed between slashes '/'
SV03 Code word length exceeded
SV04 Field not valid
SV05 Amount must have a comma
SV06 Amount must have only one comma
SV07 Party Identifier format not valid
SV08 Party Identifier must start with a slash '/'
SV09 Does not contain a valid code word
SV10 - Field must start with a double slash '//' or a '/'code word'/'.
- Field must start with a double slash '//'
SV11 Maximum lines for this option are 2
SV12 BIC is mandatory
SV13 - At least one line must be present.
- Minimum lines for this option are: <available options>
SV14 Maximum lines for this option are 5
SV15 Option must be
SV16 Mandatory Tag is missing
SV17 Field must start with a '/'code word'/'
SV18 Field must start with a double slash '//'
SV19 Narrative text must not start with a slash
SV20 Account line must start with a slash '/'
SV21 Maximum lines for this option
SV22 - Use a '/' to separate Message Index and Total fields.
- Use a '/' to separate Statement number and Sequence number
SV23 - Message Index field must not be more than 5 digits.
- Statement number must not be more than 5 digits or less than 1 digit
SV24 Total field length must be 4 digits
SV25 - Message Index field must be numeric.
- Statement number must be numeric
SV26 - Total field must be numeric. - Sequence number must be numeric.
- Number of days field is invalid or empty.
- Invalid function code word
SV27 Use a '/' to separate Type and Market fields
SV28 Use a '/' to separate Market and Data fields
SV29 Repetitive sequence must not be present in message type
SV30 At least one Repetitive sequence must be present
SV31 Narrative text must start with a slash '/'
SV32 Narrative text must be present
SV33 Rate must have a comma
SV34 Rate must have only one comma
SV35 Rate must not start with a comma
SV36 Field length must be : <permitted length>
SV37 Both the account number and BEI line must be present
SV38 The second character must be a slash '/'
SV39 Invalid Session Number or ISN
SV40 Message Type Number and Date fields must be present
SV41 Country field is missing or invalid
SV42 Account is mandatory
SV43 Index field must not be more than 1 digit
SV44 Partial Code Line must not be more than 33 digits
SV45 Check the format option for field 50a (Instruction Party or Creditor)
SV46 Tag 50a must not be present more than 2 times
SV47 Second line must be present
SV48 Tag 52 must not be present more than 2 times
SV49 Check the format option for field 50a (Instruction Party or Ordering Customer)
SV50 - Total field length must not be more than 5 digits.
- Sequence number must not be more than 5 digits or less than 1 digit.
- Sequence number must not be more than 2 digits or less than 1 digit
SV51 Additional Information must start with a slash '/'
SV52 BEI is mandatory
SV53 Application Identifier is missing (Basic Header Block)
SV54 Application Identifier is invalid (Basic Header Block)
SV55 Service Identifier is missing (Basic Header Block)
SV56 Service Identifier is invalid (Basic Header Block)
SV57 LT Identifier is missing (Basic Header Block)
SV58 LT Identifier is invalid (Basic Header Block)
SV59 Session Number is invalid (Basic Header Block)
SV60 Sequence Number is invalid (Basic Header Block)
SV61 Input/Output Identifier must be 'I' or 'O' (Application Header Block)
SV62 Message Type is missing (Application Header Block)
SV63 Message Type is invalid (Application Header Block)
SV64 Receiver Address is missing (Application Header Block)
SV65 Receiver Address is invalid (Application Header Block)
SV66 Message Priority is missing (Application Header Block)
SV67 Message Priority is invalid (Application Header Block)
SV68 Delivery Monitoring must be '1' or '3' (Application Header Block)
SV69 Delivery Monitoring must be '2' or blank (Application Header Block)
SV70 Delivery Monitoring must not be used (Application Header Block)
SV71 Obsolescence period must not be used (Application Header Block)
SV72 Obsolescence period must be '003' (Application Header Block)
SV73 Obsolescence period must be '020' (Application Header Block)
SV74 Obsolescence period is missing (Application Header Block).
SV75 Swift Validator cannot handle this Type of Message
SV76 Message Type is missing from the message
SV77 At least one line of the subfield Name & Address is required
SV78 Invalid format. Format is :
SV78 Invalid format. Field must be empty
SV79 Mandatory Subfield is missing or invalid
SV79 Subfield is invalid
SV80 Field length invalid
SV81 Field must start with symbol ' : '
SV82 Field after qualifier , must contain double slash '//'
SV83 Use a '/' to separate Function and Subfunction fields
SV84 Use a '/' to separate Qualifier , Data Source Scheme and Proprietary Code fields
SV85 Use a '/' to separate Function and Name & Address fields
SV86 Subfield must start with a slash '/'.
SV87 Frequency/Timing in Period subfields are missing or invalid
SV88 Use a '/' to separate Frequency and Timing in Period subfields
SV89 Use a '/' to separate Timing in Period and Day subfields
SV90 When subfield Day is present, it must consist of 2 numbers
SV93 - Use a '/' to separate Qualifier , Data Source Scheme, Account Type Code and Account Number.
- Use a '/' to separate Code and Function
SV94 Qualifier of Tag is Mandatory
SV95 Invalid length of Qualifier
SV96 Codes must start and end with a slash '/'.
SV97 When an ISIN identifier is not used it is strongly recommended that one of the following codes be used at the first four characters of the description of security : The ISO two digit country code or /TS/ or /XX/.
SV98 The decimal comma occurs more than one time(s)
SV99 In field 72, if the code /INS/ is used at the beginning of a line, it must be followed by a valid financial institution BIC and be the only information on that line
SV100 Missing Mandatory Sequence(s)
SV101 Number of Days specifies the number of days notice (for example, 07). It must only be used when Function is NOTICE
SV102 In field 72, when first line starts with one of the codes /RETN/ or /REJT/, the third line must start with the code /MREF/ and follow the format : 16x
SV103 In field 72, when first line starts with one of the codes /RETN/ or /REJT/, code words must not be duplicated
SV104 In field 72, when first line starts with one of the codes /RETN/ or /REJT/, code words on the lines 2-6 must be in proper sequence : reason code (format 2!c2!n), MREF, TREF (optional), CHGS (optional), TEXT (optional)
SV105 In field 72, when first line starts with one of the codes /RETN/ or /REJT/, the information component following all code words, except for reason code (for example, /AC01/) is mandatory. This component must not be empty, nor consist entirely of blanks
SV106 In field 72, information following the code /RETN/ or /REJT/ must consist of the field causing the reject or return, and possibly other message elements (for example, letter option and sequence identification), which may be helpful to the sender in isolating the specific error; format : 2!n[1!a][/2c].
SV107 In field 72, when first line starts with one of the codes /RETN/ or /REJT/, each line must begin with the format : /'code word'/.
SV108 One of the following codes must be used:
SV109 Slash absent or in wrong position
SV110 Left part not present
SV111 Field must contain the following codes : <list of codes>
SV112 <field name> must contain the following codes : <list of codes>
SV113 Narrative text must not start with a slash and, if used, must begin on a new line and be the last information in the field
SV115 At least one of the following codes should be used, placed between slashes \ /\ : <list of codes>
SV116 For field <field name> in sequence <sequence name> the following values must not be repeated : <list of values>
SV117 At least one of fields 95P, 95Q, 95R must be present in sequence <sequence name>