MT543 Format Specifications

MT543 Network Validated Rules

• C1. The following amount fields cannot appear in more than one occurrence of subsequence E3 Amounts :

  Subsequence E3

  :19A::ACRU

  :19A::ANTO

  :19A::CHAR

  :19A::COUN

  :19A::DEAL

  :19A::EUTR

  :19A::EXEC

  :19A::ISDI

  :19A::LEVY

  :19A::LOCL

  :19A::LOCO

  :19A::MARG

  :19A::OTHR

  :19A::POST

  :19A::REGF

  :19A::SETT

  :19A::SHIP

  :19A::SPCN

  :19A::STAM

  :19A::STEX

  :19A::TRAN

  :19A::TRAX

  :19A::VATA

  :19A::WITH

  :19A::COAX

  :19A::ACCA

• C2. It is mandatory to specify a settlement amount: one occurrence of the subsequence E3 Amounts, must contain Amount field :19A::SETT .

• C3. If sequence C Financial Instrument/Account is present only once, the Settlement Amount (field :19A::SETT) must not be present in sequence C .

• C4. If sequence C is present two or more times, the Settlement Amount (field :19A::SETT) must be present in every occurrence of sequence C or in none .

  In the former case (when sequence C is present two or more times and the Settlement Amount (field :19A::SETT) is present in every occurrence of sequence C) then:

  • the sum of all occurrences of the Settlement Amount (field :19A::SETT) in sequence C must be equal to the Settlement Amount (field :19A::SETT) in subsequence E3 and

  • the currency code in the Settlement Amounts (fields 19A::SETT in (sub)sequences C and E3) must be the same for all occurrences of these fields in the message.

• C5. In sequence A, if the Total of Linked Settlement Instructions (field :99B::TOSE) is present, then the Current Settlement Instruction Number (field :99B::SETT) must be present .

  Sequence A if field :99B::TOSE is ...	Sequence A then field :99B::SETT is ...
  Present	Mandatory
  Not present	Optional

• C6. In subsequence E3, 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 E3 if field :92B::EXCH is ...	Subsequence E3 then field :19A::RESU is ...
  Present	Mandatory
  Not present	Not allowed

• C7. The following party fields cannot appear more than once in a message :

  Subsequence E1	Subsequence E2	Sequence F
  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::INVE
  :95a::PSET		:95a::VEND
  :95a::REAG		:95a::TRAG
  :95a::RECU
  :95a::REI1
  :95a::REI2
  :95a::SELL

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

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

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

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

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

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

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

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

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

  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)

• C10. 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 or PREA	Optional	Not Applicable

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

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

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

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

• C13. In sequence A, if field :99B::TORE or field :99B::TODE is present, then field :99B::TOSE is mandatory in the same sequence. .

  Sequence A if field :99B::4!c is ...	Sequence A then field :99B::TOSE is ...
  TORE or TODE	Mandatory
  Not (TORE or TODE)	Optional

• C14. If field :22F::DBNM is present in sequence E, then a buyer must be specified, i.e. one occurrence of subsequence E1 must contain field :95a::BUYR .

  Sequence E if field :22F::DBNM is ...	then in one occurrence of subsequence E1 ...
  Present	Field :95a::BUYR is Mandatory
  Not present	Not Applicable

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

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

• C16. If field :36B::PAIR is present in minimum one occurrence of sequence A1, then the type of settlement transaction must be a pair-off; ie, sequence E field :22F::SETR//PAIR must be present .

  In Seq. A1 if field :36B::PAIR is ...	then in Sequence E, field :22F::SETR must be ...
  Present	:22F::SETR//PAIR and DSS must not be present
  Not present	Not Applicable

• C17. In each occurrence of sequence C, 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 C 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

MT543 Usage Rules

• The message may also be used to:

  • re-send a message (be it an instruction, request for cancellation, or pre-advise) sent by the account owner to the account servicer (the sub-function of the message is DUPL)

  • provide a third party with a copy of a message (be it an the instruction, request for cancellation, or pre-advise) being sent by the account owner for information (the sub-function of the message is COPY)

  • re-send a third party a copy of a message (be it an instruction, request for cancellation, or pre-advise) being sent by the account owner for information (the sub-function of the message is CODU).

• When the message is used as a request to cancel, the linkage sequence must contain the reference of the original instruction.

• Field 11A Currency in Trade Details sequence B provides an instruction to the account servicer to execute a forex deal on behalf of the account owner. The purpose of the forex deal is to repatriate proceeds at the completion of a transaction. This field is not to be used when standing instructions have been established. The use of forex instruction implies the following:

  • the currency received as proceeds from the sale of securities, eg, the currency to be sold, is the currency of the settlement amount. The currency to be bought is indicated by the qualifier FXIB, 'currency to be bought'. If proceeds are repatriated, this is in the base currency of the portfolio.

  • the amount of currency to be sold is equal to the settlement amount of the transaction. This implies a bulk forex deal must be instructed by other means.

  • a forex deal to repatriate proceeds after the sale of securities should be executed for the soonest possible value date after settlement of the securities, as permitted by market convention.

  • a bilateral agreement regarding the use of this field has been established.