MT528 Format Specifications

MT528 Network Validated Rules

• C1. When the Type of Price (field :22F::PRIC) is present, the Deal Price (field :90a::DEAL) must also be present .

  Sequence B if field :22F::PRIC is ...	Sequence B then field :90a::DEAL is ...
  Present	Mandatory
  Not present	Optional

• C2. If an Exchange Rate (field :92B::EXCH) is present, the corresponding Resulting Amount (field :19A::RESU) must be present in the same subsequence. If the Exchange Rate is not present then the Resulting Amount is not allowed .

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

• C3. If the Settlement Amount (:19A::SETT) is specified in both sequence B and subsequence C3, it must contain the same value, ie, (Sign) (Currency) (Amount) must be identical .

• C4. If the message is a cancellation, ie, Function of the Message (field 23G) is CANC, 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	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

• C5. The following party fields for subsequences C1 and C2 cannot appear more than once in sequence C. The party fields for sequence D cannot appear more than once in a message .

  Subsequence C1	Subsequence C2	Sequence D
  :95a::BUYR	:95a::ACCW	:95a::EXCH
  :95a::DEAG	:95a::BENM	:95a::MEOR
  :95a::DECU	:95a::PAYE	:95a::MERE
  :95a::DEI1		:95a::TRRE
  :95a::DEI2		:95a::VEND
  :95a::PSET		:95a::TRAG
  :95a::REAG
  :95a::RECU
  :95a::REI1
  :95a::REI2
  :95a::SELL

• C6. If a qualifier from the list Deliverers is present in a subsequence C1, in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Deliverers (see below) must be present .

  In other words, in sequence C, the following scenarios must be validated:

  • If :95a::DEI2 is present in subseq C1, then :95a::DEI1 must be present in another subseq C1.

  • If :95a::DEI1 is present in subseq C1, then :95a::DECU must be present in another subseq C1.

  • If :95a::DECU is present in subseq C1, then :95a::SELL must be present in another subseq C1.

  If a qualifier from the list Receivers is present in a subsequence C1, in a field :95a::4!c, then all the remaining qualifiers following this qualifier in the list Receivers (see below) must be present.

  In other words, in sequence C, the following scenarios must be validated:

  • If :95a::REI2 is present in subseq C1, then :95a::REI1 must be present in another subseq C1.

  • If :95a::REI1 is present in subseq C1, then :95a::RECU must be present in another subseq C1.

  • If :95a::RECU is present in subseq C1, then :95a::BUYR must be present in another subseq C1.

  Deliverers		Receivers
  DEI2	Deliverer's Intermediary 2	REI2	Receiver's Intermediary 2
  DEI1	Deliverer's Intermediary 1	REI1	Receiver's Intermediary 1
  DECU	Deliverer's Custodian	RECU	Receiver's Custodian
  SELL	Seller (Deliverer)	BUYR	Buyer (Receiver)

• C7. If field :22F::DBNM is NOT present in sequence C, and the instruction is a delivery (:22H::REDE//DELI in sequence B), then it is mandatory to specify a receiving agent: one occurrence of subsequence C1 Settlement Parties must contain party field :95a::REAG .

  If field :22F::DBNM is NOT present in sequence C, and the instruction is a receipt (:22H::REDE//RECE in sequence B), then it is mandatory to specify a delivering agent: one occurrence of subsequence C1 Settlement Parties must contain party field :95a::DEAG .

  In sequence C if field :22F::DBNM is ...	and sequence B if field :22H::REDE is ...	then in one occurrence of subsequence C1
  Not Present	DELI	field :95a::REAG is Mandatory
  	RECE	field :95a::DEAG is Mandatory
  Present	Not Applicable	Not Applicable

• C8. In subsequence C1, if field :95a::PSET is present, then field :97a::SAFE is not allowed in the same subsequence. .

  Subsequence C1 if field :95a::PSET is ...	Subsequence C1 then field :97a::SAFE is ...
  Present	Not allowed within the same occurrence
  Not present	Optional

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

  Sequence C if field :22F::FXCX is if the Data Source Scheme is present in field :22F::FXCX// then the conditional rule does not apply.	In sequence A then field :23G:4!c is ...
  FXNO	CANC
  FXYE	CANC
  SINO	NEWM
  Not present	Not Applicable

• C10. If field :22F::DBNM is present in sequence C and the instruction is a delivery (i.e. :22H::REDE//DELI in sequence B), then it is mandatory to specify a buyer, i.e. one occurrence of subsequence C1 must contain field :95a::BUYR .

  If field :22F::DBNM is present in sequence C and the instruction is a receipt (i.e. :22H::REDE//RECE in sequence B), then it is mandatory to specify a seller, i.e. one occurrence of subsequence C1 must contain field :95a::SELL .

  Sequence C if field :22F::DBNM is ...	and Sequence B field :22H::REDE is ...	then in one occurrence of subsequence C1 ...
  Present	DELI	Field :95a::BUYR is Mandatory
  	RECE	Field :95a::SELL is Mandatory
  Not present	Not Applicable	Not Applicable

• C11. If field :22F::DBNM//VEND is present in sequence C, then a vendor must be specified; i.e. one occurrence of sequence D must contain field :95a::VEND .

  In Seq. C if field :22F::DBNM//VEND is ... if the Data Source Scheme is present in field :22F::DBNM//VEND then the conditional rule does not apply.	then Seq. D is ...	and in one occurrence of Seq. D field :95a::VEND is ...
  Present	Mandatory i.e. Seq. D must be present minimum once	Mandatory
  Not present	Optional	Optional

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

  In sequence C, if field :22F::DBNM is ...	then in one occurrence of subsequence C1 ...
  Not present	field :95a::PSET is Mandatory
  Present	Not Applicable

• C13. In sequence B, field :36B::SETT 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 :36B::SETT is ...	Then one occurrence of :36B::SETT must be ...	And the other occurrence of :36B::SETT must be ...
  Repeated	:36B::SETT//FAMT	:36B::SETT//AMOR
  Not Repeated	Not Applicable	Not Applicable

MT528 Usage Rules

• When an instruction is sent to a party other than the original Receiver, this original Receiver is identified in the other parties sequence as :95a::MERE (Recipient of the Message).

• When a broker is identified as a confirming party, the party capacity (:22F::TRCA) must be specified in subsequence B1.

• When an ETC service provider transfers a message from one institution to another, and when the originator of the message is not already identified in the confirmation parties sequence or the settlement parties sequence, the originating party is identified in the other parties sequence as :95a::MEOR (Originator of Message).

• This message may only be sent by an ETC service provider on behalf of an institution or executing broker in a client-side trade to a custodian or clearing agent.

• The Receiver of a request to cancel must advise the requesting party that the request has been accepted or denied in an MT 509 Trade Status Message.