MT566 Format Specifications

MT566 Network Validated Rules

• C1. If an Exchange Rate is present (field :92B::EXCH), the corresponding Resulting Amount (field :19B::RESU) must be present in the same (sub)sequence. If the exchange rate is not present, the resulting amount is not allowed .

  This check applies to subsequence D2.

  Subsequence D2 if field :92B::EXCH is ...	Subsequence D2 then field :19B::RESU is ...
  Present	Mandatory
  Not present	Not allowed

• C2. If the message is a reversal, ie, 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 .

  Sequence A if field :23G: is ...	then subsequence A1 is ...	and field :20C::PREV is ...
  REVR	Mandatory (minimum one occurrence of A1 must be present)	Mandatory in one occurrence of subseq. A1, and not allowed in all other occurrences of subseq. A1
  NEWM	Optional	Not Applicable

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

• C4. 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 :92J:: TAXE is present more than once, then for each occurrence of field :92J:: TAXE, the Rate Type Code must be different .

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

  In Seq. C if field :70E::NAME is ...	then Seq. A field :22F::CAEV//CHAN is ...	and Seq. C field :22F::CHAN//NAME is ...
  Present	Mandatory (DSS must not be present)	Mandatory (DSS must not be present)
  Not present	Not Applicable	Not Applicable

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

  In Seq. A if field :22F::CAEV//RHDI is ... if the Data Source Scheme is present in field :22F::CAEV then the conditional rule does not apply.	then Seq. C is ...	and in Seq. C field :22F::RHDI is ...
  Present	Mandatory	Mandatory
  Not present	Optional	Optional

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

• C8. In sequence B, field :93B::ELIG cannot appear more than twice (maximum two occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR .

  Sequence B if field :93B::ELIG is ...	Then one occurrence of :93B::ELIG must be ...	And the other occurrence of :93B::ELIG must be ...
  Repeated	:93B::ELIG//FAMT and DSS must not be present	:93B::ELIG//AMOR and DSS must not be present
  Not Repeated	Not Applicable	Not Applicable

• C9. In each occurrence of subsequence D1, field :36B::PSTA cannot appear more than twice (maximum two occurrences). When repeated, one occurrence must have Quantity Type Code FAMT and the other occurrence must have Quantity Type Code AMOR .

  Subsequence D1 if field :36B::PSTA is ...	Then one occurrence of :36B::PSTA must be ...	And the other occurrence of :36B::PSTA must be ...
  Repeated	:36B::PSTA//FAMT	:36B::PSTA//AMOR
  Not Repeated	Not Applicable	Not Applicable

MT566 Usage Rules

• Unless an MT 564 Corporate Action Notification was not previously sent or unless pursuant to a bilateral agreement, general details of corporate action event should not be reiterated in the MT 566. If details are included, the same event details should not be repeated in both the sequence Corporate Action Details and the sequence Corporate Actions Confirmation. The sequence Corporate Actions Details should convey details that are common to the corporate action event while details appearing in the sequence Corporate Action Confirmation should be specific only to the specific posting.

• The quantity of securities reported in the sequence Underlying Securities represents the balance before the posting was effected.

• The sequence Financial Instrument Attribute (FIA) is intended to provide additional information regarding the terms and conditions of a securities issue. The objective of the sequence FIA is to ensure unambiguous identification of the security by the Receiver. It is recommended that the sequence FIA not be used unless required by a specific corporate action event, pursuant to a bilateral agreement, or when a valid ISIN or security identifier is not available.

• In case of blocking of shares, depending on your internal processing method, you can use either an MT 566 Corporate Action Confirmation or an MT 508 Intra-Position Advice. The MT 566 is to be used when the securities safekeeping account is debited and another securities safekeeping account is credited. The MT 508 is to be used when the securities remain in the same securities safekeeping account but are given a blocked status.