MT513 Format Specifications

MT513 Network Validated Rules

• C1. 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, the Resulting Amount is not allowed .

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

• C2. If Settlement Amount (:19A::SETT) is present in sequence C, it must not be present in any occurrence of subsequence D3 .

  Sequence C if field :19A::SETT is ...	Then for each occurrence of subsequence D3 field :19A::SETT IS ...
  Present	Not allowed
  Not present	Optional

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

• C4. The following party fields for subsequences D1 and D2 cannot appear more than once in sequence D. The party fields for sequence E cannot appear more than once in a message :

  Subsequence D1	Subsequence D2	Sequence E
  :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

• C5. If a qualifier from the list Deliverers is present in a subsequence D1, 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 D, the following scenarios must be validated:

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

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

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

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

  If a qualifier from the list Receivers is present in a subsequence D1, 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 D, the following scenarios must be validated:

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

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

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

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

  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)
  DEAG	Delivering Agent	REAG	Receiving Agent

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

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

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

  If Seq. D is ...	and in Seq. D 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. E is ...	and in one occurrence of Seq. E field :95a::VEND is ...
  Present	Present	Mandatory i.e. Seq. E must be present minimum once	Mandatory
  	Not present	Optional	Optional
  Not present	Not Applicable	Optional	Optional

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

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

• The MT 513 Advice of Execution may be sent either per partial execution or at the end of the execution day (along with an average price in the case of two or more partial fills executed during the day), but not both.

• In the case of partial executions, the message may include an optional repetitive partial fill sequence summarising previously executed partial trades related to the order to buy or sell to which the MT 513 Advice of Execution relates. An additional set of optional fields in the recap details sequence allows the executing party to indicate the total quantity ordered, the quantity previously executed and the remaining quantity on order.

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

• If a reference to the original order is available, the linkage sequence A1 must include this reference.