Rules 100-199

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

In sequence A, the presence of field 21 depends on the value of field 22A. (See the SWIFT User Handbook for more details.)

MT 350:

In sequence A, if field 22A contains ADVC then field 21 is optional, otherwise field 21 is mandatory.

In sequence A, if field 94A is ASET, then fields 17O is and 17N are not allowed. If field 94A is AFWD, the fields 17O and 17N are mandatory.

MT 535:

If field :94a:: is present in Sequence B, then fields :93B::AGGR and :94a::SAFE are not allowed in any occurrence of Subsequence B1b.

In sequence A, if field 17O is Y or not present, then field 17F is not allowed. If field 17O is N, then field 17F is mandatory.

MT 535:

In sub-sequence B1b, if field :93B::AGGR is present, then field :94a::SAFE is mandatory. If field :93B::AGGR is not present, the field :94a::SAFE is optional.

In each occurrence of Subsequence B1b, if field :93B::AVAI or/and :93B::NAVL is/are present, then :field :93B::AGGR must be present in the same occurrence of Subsequence B1b.

MT 700, 705, 707, 710, 720, 740, 747:

Either field 39A or field 39B, but not both, may be present.

If subfield 1 of field 77H contains \ISDA\, then (Date) and (Version) are mandatory.

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

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. (See the SWIFT User Handbook for more details.)

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.

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 occurrence 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 present in any occurrence of sequence B, that field must not be present in sequence A.

The presence and contents of fields in sequence B depend upon the presence of the country code of the sender's and receiver's BICs within D19_CC. (See the SWIFT User Handbook for more details.)

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.

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.

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.

If sequence A field 17O is Y or not present, then sequence D is not allowed. If sequence A field 17O is N, then sequence D is mandatory.

In sequence A, if field 12F contains VANI, then at least field 17A or field 17F must contain Y. Both fields may contain Y.

In sequence B, the presence of field 84a, depends on the value of fields 12F, 17A and 17F in sequence A. (See the SWIFT User Handbook for more details.)

In sequence A, the values allowed for field 12E depend on the value of field 12F. (See the SWIFT User Handbook for more details.)

In sequence A, the allowed values for subfield 1 of field 22K depend on fields 12F and 17A. (See the SWIFT User Handbook for more details.)

In sequence A, if subfield 1 of field 22K is CONF or CLST, then fields 30U and 29H are not allowed. If it is any other value, field 30U is mandatory and 29H is Optional.

The present of sequence E depends of field 17F and 17N. (See the SWIFT User Handbook for more details.)

MT 507:

The presence of sequence B depends on the value of field :25D::4!c//<Status> in sequence A and the value of field :13A::Link//<Number Id> in sub-sequence A2. See the SWIFT User Handbook for more details.

MT 567:

If the message is an instruction status or a cancellation request status (:23G:INST or CAST), and sequence B is present, and an instruction has been received (:25D::IPRC//NOIN is not present in the message), then sequence B should contain a CA option number and code (:13A::CAON and :22a::CAOP are mandatory). See the SWIFT User Handbook for more details.

If sequence A field 12F is VANI, then sequence D is mandatory and sequence G is not allowed. If field 12F is not VANI, then sequence D is not allowed and sequence G is mandatory.

If sequence D is present, that is if field 12F in sequence A contains VANI (see Error Code D30), then the presence of fields 30P and 30Q depends on the value of field 12E in sequence A. (See the SWIFT User Handbook for more details.)

The presence of sequence E depends on the values of field 12F and subfield 1 of field 22K in sequence A. (See the SWIFT User Handbook for more details.)

If sequence A field 12F is VANI and field 17F is Y, then sequence D field 26F must be NETCASH. If sequence A field 12F VANI and field 17F is N, the sequence D field 26F must be NETCASH or PRINCIPAL

In sequence E, if present, the presence of field 30H depends on the value of Type of Event (subfield 1 of field 22K) and on the Expiration Style (field 12E) in sequence A. (See the SWIFT User Handbook for more details.)

In sequence A, if field 14A contains OTHER, field 77D must be present.

In sequence A, if subfield 1 of field 77H is OTHER, then field 77D is mandatory. Otherwise, field 77D is optional.

MT 601:

If subfield 1 of field 77H contains OTHER, then field 77D must be present.

MT 340:

If sequence B field 14F is OTHER, then sequence E is mandatory and sequence E field 72 is mandatory. Otherwise, sequence E and sequence E field 72 are optional.

If sub-sequence B2 field 14D is OTHER, then sequence E is mandatory and sequence E field 72 is mandatory. Otherwise sequence E and sequence E field 72 are optional.

MT 360, 361:

In sequence B, C, E, and F, if field 14D consists of the code word \'OTHER\', field 37N must be present in the respective sequence.

In sequences C and F, if field 14F contains OTHER, field 37N must be present in the respective sequence.

In sequences C and F, if field 14J contains OTHER, field 37N must be present in the respective sequence.

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

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

If the second subcomponent of subfield 1 in sub-sequence B2 field 38G is O, then sequence E and sequence E field 72 are mandatory. Otherwise, they are optional.

If sequence A field 17A is Y then sequence F is mandatory. If field 17A is N then sequence F is not allowed.

In sequence F, if field 22G is SKIN or SKOT then field 37L is not allowed. If field 22G is DKIN or DKOT, then field 37L is mandatory.

If sub-sequence B1 is present, the presence of fields 32M, 17F, and 14D depends on field 37U in sequence B. (See the SWIFT User Handbook for more details.)

In sequence G, if field 22J is SITR then field 37P is not allowed. If field 22J is DBTR, then field 37P is mandatory.

If sequence A, field 17F is Y, then sequence H is mandatory. If field 17F is N, then sequence H is not allowed.

If in sequence L or M, field 57a if present, then in the same sequence, fields 53a and 56a are optional. If field 57a is not present, then fields 53a and 56a are not allowed.

If the country codes of both the Sender's and the Receiver's BIC belong to the D49_CC list, then field 33B is mandatory in each occurrence of sequence B, otherwise field 33B is optional. (See the SWIFT User Handbook for more details.)

MT 103_not_STP, 103_STP:

If the country codes of both the Sender's and the Receiver's BIC belong to the D49_CC list, then field 33B is mandatory, otherwise field 33B is optional. (See the SWIFT User Handbook for more details.)

MT 504:

Sequence D is not allowed when for all occurrences of sequence C, either sub-sequence C1 is not present or C1a is present in all occurrences of CI.

MT 505:

Sequence C is not allowed when for all occurrences of sequence B, either sub-sequence B1 is not present or B1a is present in all occurrences of B1.

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

MT 103_not_STP, 103_STP:

If field 71A contains SHA, then field(s) 71F is (are) optional and field 71G is not allowed.

MT 504:

Sequence E is not allowed when, for all occurrences of C, either sub-sequence 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 sub-sequence B2 is not present or sub-sequence B2a is present in all occurrences of B2.

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.

MT 103_not_STP, 103_STP:

If either field 71F (at least one occurrence) or field 71G is present, then field 33B is mandatory; otherwise field 33B is optional.

Field :13a::LINK must be present in one and only one occurrence of sub-sequence A2.

Field :20C::RELA must be present in the same occurrence of sub-sequence A2 where field :13a::LINK is present.

If field 36 is present, then field 21F must be present.

In sequences B, C, E and F, if field 14A contains OTHER, field 37N must be present in the respective sequence.

The presence of fields 32H and 30X in sequence B depends on the value of field 22B in sequence A. (See the SWIFT User Handbook for more details.)

MT 330:

The presence of fields 32B, 32H and 30X in sequence B depends on the value of field 22B in sequence A (See the SWIFT User Handbook for more details.)

MT 620:

The presence of fields 32H, 32R and 30X in sequence B depends on the value of field 22B in sequence A (See the SWIFT User Handbook for more details.)

In sequence C, in field 71G, Amount must not equal \'0\'.

MT 103_not_STP, 103_STP:

In field 71G, Amount must not equal \'0\'.

MT 320.

The values allowed for field 32H in sequence B depend on the values of fields 22B in sequence A and 17R in sequence B. (See the SWIFT User Handbook for more details.)

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. (See the SWIFT User Handbook for more details.)

MT 620:

In sequence B, the values allowed for field 32a (index 18, field32H, R) depend on the values of fields 22B in sequence A and 17R in sequence B.

Depending on the contents of subfield 1 of field 23A in sequence A, only certain combinations of optional sequences B, C, E, and F are allowed. (See the SWIFT User Handbook for more details.)

If sub-sequence E1 is present, the presence of fields 32M (in each occurrence of the internal loop), 17F and 14D, depends on field 37U in sequence E. (See the SWIFT User Handbook for more details.)

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.

MT 320, 330, 620:

In sequence B, if field 30F is present, then field 38J in sequence B is mandatory; otherwise field 38J is not allowed.

MT 341:

In sequence B, if field 30V is present then field 38D in sequence B is mandatory; otherwise field 38D is not allowed.

If there is only one debit account, the ordering customer must be identified in field 50a (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 (option F, G or H) of sequence B. Consequently, field 50a (option F, G or H) must be present in either sequence A or in each occurrence of sequence B, but must never be present in both sequences, nor be absent from both sequences.

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.

Field 51A is only valid in FileAct. This special error code is required to indicate to FileAct users that they have included a field in a FIN message that is reserved for FileAct.

Field 52a must not be present in both sequences A and B.

In each occurrence of sequence B, if field 56a is present then field 57a must be present.

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

MT 207:

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

In each occurrence of sequence B, when field 23E is used more than once, certain combinations are not allowed. (See the SWIFT User Handbook for more details.)

MT 103_STP:

When field 23E is used more than once, the following combination is not allowed: REPA with CORT.

MT 207:

Certain field combinations are not allowed. (See the SWIFT User Handbook for more details.)

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.

If field 22B in sequence A contains MATU, then field 30F in sequence B is not allowed; otherwise field 30F is 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.

MT 340:

If at least one occurrence of field 22B in sub-sequence B2 contains OTHR, then sequence E and field 72 in sequence E are mandatory; otherwise (that is no occurrence of field 22B contains OTHR), field 72 in sequence E is optional.

In sequence A, the presence of field 21 depends on the value of field 22A. (See the SWIFT User Handbook for more details.)

MT 320, 330,620:

In sequence A, the presence of field 21 depends on the values of fields 22B and 22A. (See the SWIFT User Handbook for more details.)

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

MT 513, 515:

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

MT 528, 529:

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

MT 540, 541, 542, 543:

If field :22F::DBNM//VEND is present in sequence E, then it is mandatory to specify a vendor: that is, one occurrence of sequence F Other Parties must contain a party field :95a::VEND:.

In sequence A, if field 94A is present and contains AGNT, then field 21N in sequence A is mandatory; otherwise it is optional.

MT 330, 350:

In sequence A, if field 94A is present and contains AGNT, then field 21N in sequence A is mandatory; otherwise it is optional.

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.

The presence of sequence C and fields 88a and 71F depends on field 94A. (See the SWIFT User Handbook for more details.)

MT 306:

The presence of sequence I and fields 88a and 71F in sequence I depends on the value of field 94A in sequence A. (See the SWIFT User Handbook for more details.)

MT 320, 620:

The presence of sequence H and fields 88a and 71F in sequence H depends on the value of field 94A in sequence A. (See the SWIFT User Handbook for more details.)

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. (See the SWIFT User Handbook for more details.)

MT 360, 361:

The presence of fields 88a and 71F in sequence N and, therefore, the presence of sequence N itself, depend on field 94A in sequence A. (See the SWIFT User Handbook for more details.)

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.

MT 104, 107:

In any occurrence of sequence B, if field 33B is present and the currency codes in fields 32B and 33B are different, then field 36 must be present. Otherwise, field 36 must not be present.

If sequence A field 17U is N or Not present, then sequence D is not allowed. If field 17U is Y, then sequence D is mandatory.

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.

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.

Field 23E must be present either in sequence A or in each occurrence of sequence B but not in both.

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

MT 104, 107:

If field 71F is present in one or more occurrences of sequence B, then it must also be present in sequence C, and vice-versa. If field 71G is present in one or more occurrences of sequence B, then it must also be present in sequence C, and vice-versa.

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.

MT 107:

If the amount in field 32B of sequence C is equal to the sum of amounts of the fields 32B of sequence B, then field 19 must not be present; otherwise field 19 must be present.

MT 256:

If the amount in field 32A of sequence C is equal to the sum of the amounts of the fields 32J of sequence B, then field 19 must not be present; otherwise (that is the amount in field 32A of sequence C is not equal to the sum of the amounts of fields 32J of sequence B), field 19 must be present.

Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of \'OTHR\'.

MT 306:

Subfield 2 of field 22K, that is \'/\'35x, is mandatory when subfield 1 of this field C consists of \'OTHR\'; otherwise subfield 2 is not allowed.

MT 405:

Subfield 2 of field 23C is allowed only when subfield 1 of this field consists of \'OTHR\'.

Subfield 2 of field 23E is allowed only when subfield 1 of this field consists of \'OTHR\'.

Subfield 2 of field 23F is allowed only when subfield 1 of this field consists of \'OTHR\'.

MT 700, 710, 720:

Subfield 2 of field 40E (that is, \'/\'35x) is only allowed when subfield 1 of this field consists of \'OTHR\'.

MT 760:

Subfield 2 of field 40C is only allowed when subfield 1 of this field consists of \'OTHR\'.

The first component in line 1 of field 72 must consist either /RETN/ or /REJT/.

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.

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

In sequence B, if field 30X is present, then field 34E is mandatory; otherwise field 34E is not allowed.

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.

MT 405:

Fields 23E and 50D must, independently of each other, be present either in sequence A or in each occurrence of sequence B, but not both.

When present in sequence A, fields 26T, 77B, 71A, 50L and 52a must, independently of each other, not be present in any occurrence of sequence B. Conversely, when not present in sequence A, fields 26T, 77B, 71A, 50L and 52a are, independently of each other, optional in any occurrence of sequence B.

Independently of each other, if fields 71F and 71G are present in one or more occurrence of sequence B, then they must also be present in sequence C. Conversely, if fields 71F and 71G are not present in any occurrence of sequence B, then they must not be present in sequence C.

If sequence C is present and the sum of the fields 32a in sequence B equals the amount indicated in field 32a in sequence C, then field 19 must not be present in sequence C. If sequence C is present and the sum of the fields 32a in sequence B does not equal the amount indicated in field 32a in sequence C, then field 19 must be present in sequence C and must equal the sum of all the fields 32a in sequences B.

The presence of sub-sequences A1 and B1 is dependent on the presence and the content of subfield 1 of field 23E in the same sequence A and B respectively. (See the SWIFT User Handbook for more details.)

If field 71A contains either SHA or BEN, field 17A must be used. If field 71A contains OUR, field 17A must not be used. If field 71A is not present, field 17A is optional.

In each occurrence of Sequence B, all Orders of field 20C are Optional, but at least one Order (any one) must be present.

MT 568:

All Orders of field 70a are Optional, but at least one Order (any one) must be present.

If field 23 contains CHQB, then subfield 1 must not be present in field 59a. In all other cases, it is mandatory.

MT 530:

In each occurrence of Sequence B, all Orders of field 22F are Optional, but at least one Order (any one) must be present.

The presence of fields 22D and 22E is dependent on the presence and the content of subfield 1 of field 23E. (See the SWIFT User Handbook for more details.)

In sequences A and B, depending on the content of field 23E, only certain code word combinations may be used in fields 22D and 22E.

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, 320, 340, 360, 361, 362:

Field 18A must equal the number of repetitions that immediately follows.

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.

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

If field 23E is repeated, the codes must appear in the following order: SDVA, INTC, REPA, CORT, HOLD, CHQB, PHOB, TELB, PHON, TELE, PHOI, TELI. Note: The first code does not need to be SDVA. There may be gaps.

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.

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

If field :70E::NAME is used in sequence C, then field :22F::CAEV//CHAN must be present in sequence A, and field :22F::CHAN//NAME must be present in sequence C.