MT564 Format Specifications

MT564 Network Validated Rules

• C1. If 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 E2.

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

• C2. If the safekeeping accounts are not provided, ie, if field :97C::SAFE//GENR is present in any occurrence of subsequence B2, then:

  • subsequence B2 Account Information must not be repeated in the message

  • the Balance of Securities, ie, field 93a, must not be present in subsequence B2 Account Information .

  In subsequence B2 if field :97C::SAFE//GENR is ...	then subsequence B2 is Mandatory and ...	and in subsequence B2 field 93a is ...
  Present	Not Repetitive min-Max = 1-1	Not allowed
  Not present	Repetitive min-Max = 1-n	Optional

• C3. In sequence A, if field :23G:REPE is present, then

  when sequence C is present, field :36a::QINT is mandatory .

  In Seq. A if field :23G:REPE is ...	and Seq. C is ...	then in Seq. C field :36a::QINT is ...
  Present	Present	Mandatory
  	Not Present	Not Applicable
  Not present	Optional	Optional

• C4. In sequence A, if field :22F::CAEV//OTHR is present, then minimum one of the Sequences D or F must be present, and minimum one occurrence of field :70E::ADTX must be present in the message (i.e. in seq. D, or F, or both) .

  Sequence A, if field:22F::CAEV//OTHR is ... if the Data Source Scheme is present in field :22F::CAEV//OTHR then the conditional rule does not apply.	And Seq. D is ...	And in Sequence D field :70E::ADTXis ...	Then Sequence F is ...	And in Sequence F field :70E::ADTX is ...
  Present	Present	Present	Optional	Optional
  		Not present	Mandatory	Mandatory
  	Not present	Not Applicable	Mandatory	Mandatory
  Not present	Not Applicable	Not Applicable	Not Applicable	Not Applicable

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

  In each occurrence of Sequence E if field :22F::CAOP//OTHR is ... if the Data Source Scheme is present in field :22F::CAOP//OTHR then the conditional rule does not apply.	In the same occurrence of Sequence E then field :70E::ADTX is ...
  Present	Mandatory
  Not present	Optional

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

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

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

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

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

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

• C10. If the message is a cancellation, a replacement, an eligible balance notification, a withdrawal or a reminder, ie, Function of the Message (field 23G) is CANC, , REPL, REPE, WITH or RMDR, 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 ...
  CANC, REPL, REPE, WITH or RMDR	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

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

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

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

  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.	And if Seq. D is ...	then Seq E and field :22F::RHDI are ...
  Present	present and :22F::RHDI is present	Seq. E is Optional, and field :22F::RHDI is not allowed in all occurrences of Seq. E
  	present and :22F::RHDI is not present	Seq. E is Mandatory (minimum one occurrence), and field :22F::RHDI is Mandatory in at least one occurrence of Seq. E
  	not present	Seq. E is Mandatory (minimum one occurrence), and field :22F::RHDI is Mandatory in at least one occurrence of Seq. E
  Not Present	Not Applicable	Not Applicable

• C13. In each occurrence of subsequence B2, 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 .

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

• C14. In each occurrence of subsequence E1, field :36B::ENTL 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 E1 if field :36B::ENTL is ...	Then one occurrence of :36B::ENTL must be ...	And the other occurrence of :36B::ENTL must be ...
  Repeated	:36B::ENTL//FAMT	:36B::ENTL//AMOR
  Not Repeated	Not Applicable	Not Applicable

MT564 Usage Rules

• The same details must not be repeated in both the Corporate Action Details sequence and the Corporate Action Options sequence. The Corporate Action Details sequence should convey details that are common to the corporate action event while details appearing in the Corporate Action Option sequence should be specific only to the specific option.

• If the account owner has a choice of multiple currencies, the Corporate Action Option sequence should be repeated once for each currency offered using the OPTN qualifier in field 11A.

• The Financial Instrument Attribute (FIA) sequence is intended to provide additional information regarding the terms and conditions of a securities issue. The objective of the FIA sequence is to ensure unambiguous identification of the security by the Receiver. It is recommended that the FIA sequence 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.

• The MT 564 can be used to announce the basic details of a proxy voting event. For the complete agenda an MT 568 Corporate Action Narrative, using the same corporate action reference in the linkages sequence, should be used.