Rules 200-299

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.

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.

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 a minimum of one occurrence of sequence D or F must be present, and a minimum of one occurrence of field :70E::ADTX must be present in the message (that is, in sequence D, F, or both).

If field 23B contains SPRI, SSTD or SPAY and field 53a is present with option B, subfield 1, Party Identifier ([\'/\'<DC>][\'/\'34x] \'CRLF\') must be present in field 53B.

MT 103_STP:

If field 53a is present with option B, subfield 1, Party Identifier ([\'/\'<DC>][\'/\'34x] \'CRLF\') must be present in field 53B.

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

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

MT 103_STP:

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

MT 564:

If field :22F::CAEV//RHDI is present in sequence A, then field :22F::RHDI must be present in sequence D or in at least one occurrence of sequence E, but not in both D and E.

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.

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

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then sub-sequence 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 at least once in that message).

MT 500, 513, 514, 518, 519, 528, 529, 535, 536, 537, 538, 549, 565, 575, 576, 584, 586, 587:

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then sub-sequence A1 Linkages must be present at least once, 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 502:

If the message is a cancellation or replacement (that is, the Function of the Message, field 23G, is CANC or REPL), then sub-sequence A1 Linkages must be present at least once in the message, and in only one occurrence of A1, field :20C::PREV must be present. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

MT 503, 504, 505, 506, 569:

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then sub-sequence A2 Linkages must be present at least once in the message, and in only one occurrence of A2, field :20C::PREV must be present. Consequently, in all other occurrences of A2, field :20C::PREV is not allowed.

MT 508, 524:

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then sub-sequence A1 Linkages must be present in the message, and field :20C::PREV must be present in A1.

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then field :20C::PREV must be present in 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 540, 541, 542, 543:

If the message is a cancellation (that is, the Function of the Message, field 23G, is CANC), then sub-sequence A1 Linkages must be present at least once in the message, and in only one occurrence of A1, field :20C::PREV must be present. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

MT 544, 545, 546, 547:

If the message is a cancellation or a reversal (that is, the Function of the Message, field 23G, is CANC or RVSL), then field :20C::PREV must be present in only once occurrence of sub-sequence A1. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

MT 558:

In sequence A, the presence of subsequence A2 depends on the value of subfield 1 of field 23G. (See the SWIFT User Handbook for more details.)

MT 564, 568:

If the message is a cancellation, a replacement, an eligible balance notification, a withdrawal, or a reminder (that is, the Function of the Message, field 23G, is CANC, REPL, REPE, WITH, or RMDR), then sub-sequence A1 Linkages must be present at least once in the message, and in only one occurrence of A1, field :20C::PREV must be present. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

MT 566 and 588:

If the message is a reversal (that is, the Function of the Message, field 23G, is REVR), then sub-sequence A1 Linkages must be present at least once in the message, and in only one occurrence of A1, field :20C::PREV must be present. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

If the message is a cancellation or a removal (that is, the Function of the Message, field 23G, is CANC or REMO), then sub-sequence A1 Linkages must be present at least once in the message, and in only one occurrence of A1, field :20C::PREV must be present. Consequently, in all other occurrences of A1, field :20C::PREV is not allowed.

If field 23B contains SPRI, SSTD or SPAY, field 57a can be used with option A, option C or option D. In addition, in option D, subfield 1, Party Identifier, ([\'/\'<DC>][\'/\'34x] \'CRLF\') must be present.

MT 564:

If the field 23G::01 contains REPL or REPE, then the code word ENTL is not allowed in the field 25D::PROC.

If field 23B contains SPRI, SSTD or SPAY, subfield 1, Account, in field 59a is mandatory.

MT 102_STP, 103_STP, 104, 107:

Subfield 1, Account, of field 59a is mandatory.

If the message is an additional business process (:23G::ADDB) then sequence D Corporate Action Details is mandatory, and in sequence D, field :22F::ADDB is Mandatory, only one occurrence is allowed, and it must contain the code word CLAI (Claim or Compensation), TAXR (Tax Refund) or REVR (Notification or Reversal).

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

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.

MT 103_not_STP, 103_STP:

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

If field :22F::FXCX//FXNO or FXYE is present in sequence C, 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 C, then the message must be new, that is, Function of the Message in sequence A (field 23G) is NEWM.

MT 540, 541, 542, 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

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.

MT 103_not_STP, 103_STP:

If field 71A contains BEN, then at least one occurrence of field 71F is mandatory and field 71G is not allowed.

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

If field 23B contains SSTD or SPAY, field 56a can be used with either option A or option C. If option C is used, it must contain a clearing code.

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

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

If field 71L is present in sequence C, then the amount specified in field 71L must be equal to the sum of all occurrences of field 71F in sequence B.

If field 71J is present in sequence C, then the amount specified in field 71J must be equal to the sum of all occurrences of field 71G in sequence B.

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

If field 71F is present in any occurrence of sequence B, then field 71L must be present in sequence C, and vice versa if field 71F is absent from all occurrences of sequence B, then field 71L is not allowed in sequence C.

If field 71G is present in any occurrence of sequence B, then field 71J must be present in sequence C, and vice versa if field 71G is absent from all occurrences of sequence B, then field 71J is not allowed in sequence C.

If field 71H is present in any occurrence of sequence B, then field 71K must be present in sequence C, and vice versa if field 71H is absent from all occurrences of sequence B, then field 71K is not allowed in sequence C.

If field 71K is present in sequence C, then the amount specified in field 71K must be equal to the sum of all occurrences of field 71H in sequence B.

The presence of sequences B and E depends on subfield 1 of field 23A in sequence A. (See the SWIFT User Handbook for more details.)

MT 365:

The presence of sequences B and E depends on subfield 1 of field 23A in sequence A. (See the SWIFT User Handbook for more details.)

In sequence A, the presence of fields 32G and 22D and, in sequences B and E, the presence of field 37P depend on field 22B in sequence A. (See the SWIFT User Handbook for more details.)

MT 365:

In sequence A, the presence of fields 32G, 33E and 22D and, in sequences B and E, the presence of field 37P, depend on field 22B in sequence A. (See the SWIFT User Handbook for more details.)

In sequences C, E and J, if field 56a is not present, then field 86a in the same sequence C, E or J is not allowed; otherwise field 86a is optional.

MT 320:

In sequences C, D, E, F and I, if field 56a is not present, then field 86a in the same sequence is not allowed; otherwise field 86a is optional.

MT 330, 620:

In sequences C, D, E and F, if field 56a is not present, then field 86a in the same sequence is not allowed; otherwise field 86a is 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.

MT 341, 350:

In sequence C, if field 56a is not present, then field 86a is not allowed; otherwise field 86a is optional.

MT 360, 361, 362, 364, 365:

Within a specific sequence, or within an internal loop, the presence of field 86a depends on field 56a. (See the SWIFT User Handbook for more details.)

In sequence A, if field 22D contains OTHR, field 37N must be present.

Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2. (See the SWIFT User Handbook for more details.)

MT 537:

Within each occurrence of subsequence B1, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence B. (See the SWIFT User Handbook for more details.) Within each occurrence of subsequence C3a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding sequence C3 Status. (See the SWIFT User Handbook for more details.)

MT 548:

Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2. (See the SWIFT User Handbook for more details.)

MT 549:

Within each occurrence of sequence B, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of the same occurrence of sequence B. (See the SWIFT User Handbook for more details.)

MT 567:

Within each occurrence of sub-sequence A2a, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of its surrounding sub-sequence A2 Status.

MT 584:

Within each occurrence of subsequence B2, the qualifier in field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of the same occurrence of subsequence B2. (See the SWIFT User Handbook for more details.)

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.

In sequences B and D, the presence of fields 37J and 37L depends on subfield 1 of field 23A in sequence A. (See the SWIFT User Handbook for more details.)

In sequence A, the presence of field 14C depends on the value of subfield 1 of field 77H. (See the SWIFT User Handbook for more details.)

MT 361:

The content of field 77H, in sequence A, determines the presence of fields 14G and 37R in the sub-sequences C1 and F1, and sub-sequences C2 and F2. (See the SWIFT User Handbook for more details.)

In sequence B, the presence of sub-sequence B1 depends on the value of subfield 1 of field 77H in sequence A. (See the SWIFT User Handbook for more details.)

MT 360, 361:

The presence of field 37U in sequences B and E and the presence of sub-sequences B1, C1, C2, C3, E1, F1, F2 and F3 depend on the content of subfield 1of field 77H and on the content of field 14F. (See the SWIFT User Handbook for more details.)

In sequences C and F, the presence of fields 37J and 37L depends on subfield 1 of field 23A in sequence A. (See the SWIFT User Handbook for more details.)

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

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

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

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.

MT 103_not_STP, 103_STP:

If field 23E is repeated, it must not contain the same code more than once.

If sequence D is present, at least one of the sub-sequences D1 or D2 must be present.

MT 362:

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

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

MT 504:

In each occurrence of sub-sequence C1a, the presence of sub-sequence C1a1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

MT 505, 507:

In each occurrence of sub-sequence B1a, the presence of sub-sequence B1a1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

When subfield 2 of field 23A contains NET, either sequence C or E must be present, but not both.

MT 504:

In each occurrence of sub-sequence C2a, the presence of sub-sequence C2a1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

MT 505:

In each occurrence of sub-sequence B2a, the presence of sub-sequence B2a1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

MT 507:

In each occurrence of sub-sequence B1b, the presence of sub-sequence B1b1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

When subfield 2 of field 23A contains NET, fields 30F to 57a in sequence C or E must occur only once.

MT 504:

In sequence D, the presence of sub-sequence D1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

MT 505:

In sequence C, the presence of sub-sequence C1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

When subfield 2 of field 23A contains GROSS, fields 30F to 57a in sequence C and E cannot occur more than three times.

MT 504:

In sequence E, the presence of sub-sequence E1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

MT 505:

In sequence D, the presence of sub-sequence D1 depends on the presence of field :22F::STCO//NSSP. (See the SWIFT User Handbook for more details.)

In sub-sequence C1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 513, 515:

In sub-sequence D1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 536:

In sub-sequence B1a2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 537:

In sub-sequence B2b1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence. In subsequence C2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sequence.

MT 540, 541, 542, 543, 544, 545, 546, 547, 578:

In sub-sequence E1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 548:

In sub-sequence B1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 575:

In sub-sequence B1a4, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

MT 586:

In sub-sequence B5a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

In sequence B, if field :22H::BUSE//SWIT is present, then sub-sequence A1 is mandatory, and field :20C::PREV must be present in a minimum of one occurrence of sub-sequence A1.

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 sub-sequence A1.

MT 575:

In sub-sequence C2a, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same sub-sequence.

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

If in Sequence A, field :12E:: contains Euro, then field 30F of sequence B is mandatory and if 12E is not Euro, then field 30F of sequence B is optional.

If in sequence A, field :17B::CONS contains Y, then in every occurrence of sequence B, field :97a::SAFE and field :17B::ACTI are mandatory. This error code applies only when sequence B is present as per Error Code E66, that is, in sequence A, field :17B::ACTI contains Y.

The BIC must be a BEI, that is, it must be of sub-type BEID, TRCO, MCCO or SMDP.

In sequence B, either field :36B::ORDR or field :19A::ORDR must be present, but not both.

MT 509:

In Sequence B, either a quantity (field 36B::) or an amount (field 19A::) must be present, but not both.

MT 535:

In each occurrence of Sequence B1, if field :93C::PEND is present in one of the occurrences of subsequence B1b, then fields :93C::PDUM and :93C::PDMT are not allowed in the other occurrences of subsequence B1b.

If field 23G does not contain CANC, then field 13A must be present and contain 515 in minimum one occurrence of sub-sequence A1.

MT 535:

In each occurrence of Sequence B1, if field :93C::PENR is present in one of the occurrences of subsequence B1b, then fields :93C::PRUM and :93C::PRMT are not allowed in the other occurrences of subsequence B1b.

In each occurrence of sub-sequence D1, the presence of field :70C::RATS depends on the presence of field :94B::RATS. (See the SWIFT User Handbook for more details.)

MT 569:

In each occurrence of sub-sequence C1a1A, the presence of field :70C::RATS depends on the presence of field :94B::RATS. (See the SWIFT User Handbook for more details.)

MT 576:

In each occurrence of sub-sequence B2, either an ordered quantity (field :36B::ORDR), or an ordered amount (field :19A::ORDER) must be present, but not both. In addition, if field 36B is present then field 19A must not be present, and vice-versa.

When field :22F::PRIC is present, field :90a::DEAL must also be present.

In each sub-sequence 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.

MT 513, 515:

In sub-sequence D3, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed.

MT 540, 541, 542, 543, 544, 545, 546, 547, 578:

In sub-sequence E3, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed.

MT 564:

In sub-sequence E2, if field :92B::EXCH is present, the corresponding field :19B::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19B::RESU is not allowed.

MT 566:

In sub-sequence D2, if field :92B::EXCH is present, the corresponding field :19B::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19B::RESU is not allowed.

MT 584:

In sub-sequences B2b2 and C1c2, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed.

MT 586:

In sub-sequence B5c, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed.

MT 588:

In (sub)-sequences C2 and E, if field :92B::EXCH is present, the corresponding field :19A::RESU must be present in the same sub-sequence. If field :92B::EXCH is not present, then field :19A::RESU is not allowed.

In Sequence B, it is mandatory to provide an Issue Date/Time (:98a::ISSU) OR a Release Date/Time (:98a::RELD). Both dates may be provided.

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.

MT 527:

In sequence A, if field :20C::CLCI is not present, then field :20C::TRCI is mandatory; otherwise field :20C::TRCI is optional.

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.

MT 584.:

Sequences B and C are mutually exclusive and must not both be present in the same message.

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 and Sequence C Transactions must not be present.

If the Activity Flag (field :17B::ACTI) indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per status (field :22H::STST//STAT), then sequence B Status is mandatory and sequence C Transactions is not allowed. If the Activity Flag (field :17B::ACTI) in sequence A General Information indicates that there is information to be reported, that is, Y and Statement Structure Type Indicator is per transaction (field :22H::STST//TRAN), then sequence B Status is not allowed and sequence C Transactions is mandatory.

MT 569:

In each occurrence of sub-sequence C1a1, the presence of sub-sequence C1a1A depends on the value of field :17B::SECU. (See the SWIFT User Handbook for more details.)

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.

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

Field :97a::SAFE must be present in sequence A, or in all occurrences of sub-sequence B2c, but not both.

MT 584:

Field :97a::SAFE must be present in sequence A, or in all occurrences of sub-sequence B2b1 in sequence B, or in all occurrences of sub-sequence C1c1 in sequence C.

In sequence A, if field :20C::SCTR is not present, then field :20C::RCTR is mandatory; otherwise field :20C::RCTR is optional.

MT 558:

In sequence A, if field :20C::CLTR is not present, then field :20C::TCTR is mandatory; otherwise field :20C::TCTR is optional.

MT 584:

Sub-sequence B2a in sequence B must be present when field :20C::MAST is not present in sub-sequence B2.

If field :17B::ACTI in sequence B contains N, then sub-sequence B1 must not be present. In all other cases, sub-sequence 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.

MT 584:

If field :17B::ACTI in sequence A contains N, then sequences B and C must not be present.

If field :22F::DBNM is present in sequence C and field :22H::REDE//DELI is present in sequence B, then one occurrence of subsequence C1 must contain :95a::BUYR. If field :22F::DBNM is present in sequence C and field :22H::REDE//RECE is present in sequence B, one occurrence of subsequence C1 must contain field :95a::SELL.

MT 540, 541:

If field :22F::DBNM is present in sequence E, then one occurrence of subsequence E1 must contain :95a::SELL.

MT 542, 543:

If field :22F::DBNM is present in sequence E, then one occurrence of subsequence E1 must contain :95a::BUYR.

In each occurrence of sub-sequence A1, if field :22F::AGRE is not present, then field :70C::AGRE is mandatory; otherwise field :70C::AGRE is optional.

In each occurrence of sub-sequence 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 sub-sequence 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 sub-sequence 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 sub-sequence C1a1, the presence of field :98a::SETT depends on the value of field :17B:COLL. (See the SWIFT User Handbook for more details.)

If field :19A::SETT is present in sequence C, it must not be present in any occurrence of sub-sequence D3.

MT 514, 518:

If field :19A::SETT is present in sequence B, it must not be present in any occurrence of sub-sequence C3.

MT 584:

Within each occurrence of sub-sequence B2b, if field :19A::SETT is present, it must not be present in any occurrence of sub-sequence B2b2. Within each occurrence of sub-sequence C1c, if field :19A::SETT is present, it must not be present in any occurrence of sub-sequence C1c2.

In sequence B, field :22F::TOOR and/or field :90a::LIMI must be present.

If field 19A::SETT is specified in both sequences B and C3, it must contain the same value, that is Sign, Currency and Amount must be identical.

In sequence D, field :92a::, the qualifier TAXC may only be repeated with letter option/s E or/and J; and the qualifiers GRSS and NETT may only be repeated with letter option J.

In each occurrence of sequence E, field :92a::, the qualifier TAXC may only be repeated with letter option/s E or/and J; and the qualifiers GRSS and NETT may only be repeated with letter option J.

MT 566:

In sequence C, field :92a::, the qualifier TAXC may only be repeated with letter option/s E or/and J; and the qualifiers GRSS and NETT may only be repeated with letter option J.

In sequence D, field :92a::, the qualifier TAXC may only be repeated with letter option/s E or/and J; and the qualifiers GRSS and NETT may only be repeated with letter option J.

In sequence D:

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 :92E::TAXC or/and :92J::TAXC is/are present more than once, then for each occurrence of field :92a::TAXC, 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.

if field :92J:: TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.

In each occurrence of sequence E:

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 :92E::TAXC or/and :92J::TAXC is/are present more than once, then for each occurrence of field :92a::TAXC, 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.

if field :92E::TAXE or/and :92J::TAXE is/are present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.

In sequence C:

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 :92E::TAXC or/and :92J::TAXC is/are present more than once, then for each occurrence of field :92a::TAXC, 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.

if field :92J:: TAXE is present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.

In sequence D:

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 :92E::TAXC or/and :92J::TAXC is/are present more than once, then for each occurrence of field :92a::TAXC, 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.

if field :92E::TAXE or/and :92J::TAXE is/are present more than once, then for each occurrence of field :92J::TAXE, the Rate Type Code must be different.

In sequence A, field :98a::STAT and field :69a::STAT are mutually exclusive.

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.

MT 565:

In sequence D, if field :22F::CAOP//SPLI is present, then field :70E::INST is mandatory in the same sequence.

If field :22F::DBNM is NOT present in sequence C, then it is mandatory to specify a place of settlement: one occurrence of subsequence C1 Settlement Parties must contain party field :95a::PSET.

MT 549:

Sequence B Statement by Status/Reason and/or by Financial Instrument and sequence C Statement by Instruction Reference are mutually exclusive.

MT 564:

In sequence D, if field :92J::TAXE is present, then field:92F::GRSS must be present.

In each occurrence of sequence E, if field :92J::TAXE is present, then field :92F::GRSS must be present in the same sequence occurrence.

MT 566:

In sequence C, if field :92J::TAXE is present, then field:92F::GRSS must be present.

In sequence D, if field :92J::TAXE is present, then field :92F::GRSS must be present.

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 sub-sequence B2, the third component of field :93A::FROM must be different from the third component in all occurrences of field :93A::TOBA in sub-sequence B2a.

MT 564:

In each occurrence of sequence D, E, and E1, if field :92J::TAXE is present, then field :92F::GRSS must be present in the same sequence occurrence.

MT 566:

In each occurrence of sequence C, D, and D1, if field :92J::TAXE is present, then field :92F::GRSS must be present in the same sequence occurrence.

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

Certain fields cannot appear more than once in the message. (See the SWIFT User Handbook for more details.)

MT 503, 504:

In each occurrence of sequence C, the presence of sub-sequences C1, C2 and C3 depends on the value of field :22H::COLL<Indicator>. (See the SWIFT User Handbook for more details.)

MT 505:

In each occurrence of sequence B, the presence of sub-sequences B1, B2 and B3 depends on the value of field :22H::COLL. (See the SWIFT User Handbook for more details.)

MT 506:

In each occurrence of sequence D, the presence of sub-sequences D1, D2 and D3 depends on the value of field :22H::COLL. (See the SWIFT User Handbook for more details.)

MT 536:

In sub-sequence B1a2, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be specified.

MT 537:

In sub-sequence B2b and C2, if field :22H::PAYM//APMT is used, then field :19A::PSTA must be specified.

MT 548:

In sequence B, if field :22H::PAYM//APMT is used, then field :19A::SETT must be specified.

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.

In each occurrence of Seq. B3, the following party fields cannot appear more than once: :95a::CDEA, :95a::INTE, :95a::ACCW, :95a::BENM.

MT 308:

In each occurrence of Seq. B4, the following party fields cannot appear more than once: :95a::CDEA, :95a::INTE, :95a::ACCW, :95a::BENM.

MT 321:

In each occurrence of sequence C, the following party fields for sequence C1 cannot appear more than once: :95a::CDEA, :95a::INT2, :95a::INTE, :95a::ACCW, :95a::BENM.

MT 502, 504, 505, 507, 513, 514, 515, 518, 528, 529, 536, 537, 540, 541, 542, 543, 544, 545, 546, 547, 548, 575, 578, 586:

Certain party fields cannot appear more than once. (See the SWIFT User Handbook for more details.)

In each occurrence of sub-sequence C2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator>. (See the SWIFT User Handbook for more details.)

MT 505:

In each occurrence of sub-sequence B2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator>. (See the SWIFT User Handbook for more details.)

MT 506:

In each occurrence of sub-sequence D2, the presence of field :98A::TERM depends on the value of field :22H::DEPO//<Indicator>. (See the SWIFT User Handbook for more details.)

MT 528, 529:

If field :22F::DBNM is NOT present in sequence C, and if field :22H::REDE is DELI in sequence B, then one occurrence of field :95a::REAG must be present in sub-sequence C1. If field :22F::DBNM is NOT present in sequence C, and if field :22H::REDE is RECE in sequence B, then one occurrence of field :95a::DEAG must be present in sub-sequence C1.

MT 537:

If field :22H::REDE//DELI is present in sub-sequence B2b and sub-sequence B2b1 is used, then it is mandatory to specify field :95a::REAG in one occurrence of sub-sequence B2b1. If field :22H::REDE//RECE is present in sub-sequence B2b and sub-sequence B2b1 is used, then it is mandatory to specify field :95a::DEAG in one occurrence of sub-sequence B2b1. If the instruction is a delivery (:22H::REDE//DELI in sequence C2) and the Settlement Parties sequence C2a is used, then it is mandatory to specify a Receiving Agent: one occurrence of the settlement parties sequence C2a must contain party field :95a::REAG. If the instruction is a receipt (:22H::REDE//RECE in sequence C2) and the Settlement Parties sequence C2a is used, then it is mandatory to specify a Delivering Agent: one occurrence of the settlement parties sequence C2a must contain party field :95a::DEAG.

If field :22H::REDE//DELI is present in sequence B and sub-sequence B1 is used, then it is mandatory to specify field :95a::REAG in one occurrence of sub-sequence B1. If field :22H::REDE//RECE is present in sequence B and sub-sequence B1 is used, then it is mandatory to specify field :95a::DEAG in one occurrence of sub-sequence 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 sub-sequence E1. If field :22H::REDE//RECE is present in sequence B, then it is mandatory to specify field :95a::REAG in one occurrence of sub-sequence 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 sub-sequence B5a. Within each occurrence of sequence B, if field :22H::REDE//RECE is present in sequence B, then it is mandatory to specify field :95a::REAG in one occurrence of sub-sequence B5a.

If sequence C is present once, field :19A::SETT must not be present in sequence C.

MT 544, 545, 546, 547:

If sequence C is present once, field :19A::ESTT must not be present in sequence C.

Repetitive subsequence B3 must be present exactly twice in the message.

MT 321:

One occurrence of sequence C must have the value :22H::PRIT//APFM and one must have the value :22H::PRIT//APCP.

MT 540, 541, 542, 543:

In sequence A, if field :99B::TOSE is present, then field :99B::SETT must be present.

In each occurrence of Seq. B3, the presence of the repetitive subsequence B3a depends on the content of :22H::NEGR. (See the SWIFT User Handbook for more details.)

MT 321:

Taking into account rules 284 and 290, in each occurrence of Seq. 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 Seq. C. (See the SWIFT User Handbook for more details.)

MT 504:

It is mandatory to specify a Delivery Agent for sub-sequences C1a1 and D1. In each occurrence of sequence C, if sub-sequence C1a1 is present, then field :95a::DEAG must be present in one and only one occurrence of sub-sequence C1a1 within the same occurrence of sequence C. In sequence D, if present, if sub-sequence D1 is present, then field :95a::DEAG must be present in one and only occurrence of sub-sequence D1.

MT 540, 541, 544, 545:

If field :22F::DBNM is NOT present in sequence E, then it is mandatory to specify a Delivering Agent and a place of settlement: one occurrence of Subsequence E1 Settlement Parties must contain party field :95a::DEAG and another one must contain party field :95a::PSET.

Taking into account rule 291: in each occurrence of Sequence B3, the presence of field 95a in Sequence B3a depends on the content of field 19B in sequence B3. (See the SWIFT User Handbook for more details.)

MT 321:

In a message, the following sequence C fields cannot appear more than once: :22H::PRIT//APFM, :22H::PRIT//APCP, :22H::PRIT//IPFM, :22H::PRIT//IPCP.

MT 541, 543:

It is mandatory to specify one occurrence of sub-sequence E3 with field :19A::SETT.

MT 545, 547:

It is mandatory to specify one occurrence of sub-sequence E3 with field :19A::ESTT.

It is mandatory to specify a Receiving Agent for sub-sequence B1a1. In each occurrence of sequence B if present, if sub-sequence B1a1 is present, then field :95a::REAG must be present in one and only one occurrence of sub-sequence B1a1 within the same occurrence of sequence B.

MT 542, 543, 546, 547:

If field :22F::DBNM is NOT present in sequence E, then it is mandatory to specify a Receiving Agent and a place of settlement: one occurrence of the settlement parties Subsequence E1 must contain party field :95a::REAG and another one must contain party field :95a::PSET.

If field :97C::SAFE//GENR is present in any occurrence of sub-sequence B2, then sub-sequence B2 must not be repeated in the message, field 93a must not be present in sub-sequence B2, field 36B must not be present in subsequence E1, and field 19B must not be present in subsequence E2.

Within each occurrence of sequence B1, if field :17B::ACTI contains N, then sub-sequence B1a within that sub-sequence B1 is not allowed. If field 17B::ACTI contains Y, then sub-sequence B1a is mandatory.

Within sub-sequence B1a, sub-sequence B1a2 and sub-sequence B1a3 are mutually exclusive.

In sequence B, the presence of field :95a::EXPP depends on the value of field :22H::COAL//<Indicator>. (See the SWIFT User Handbook for more details.)

MT 587, 588, 589:

In sequence A, if field :22H::DERE contains CONV, then field :22F::CNVT and field :22F::CNVF must be specified and field 12a must not be present. If field 22H::DERE does not contain CONV, then field 12a must be present.

If field :17B::PRER contains Y, sequence C must also be present. If field :17B::PRER contains N, sequence C must not be present.

In sequence A, if field :99B::TORE or :99B::TODE is present, field :99B::TOSE must also be present.