MT536 Format Specifications

MT536 Network Validated Rules

• C1. If the Activity Flag (field :17B:ACTI) in sequence A General Information is N, then sequence B must not be present. Otherwise, sequence B is mandatory .

  Sequence A if field :17B::ACTI is ...	Sequence B is ...
  N	Not allowed
  Y	Mandatory

• C2. If the instruction is against payment (:22H::PAYM//APMT) then it is mandatory to specify a Posting Amount (field :19A::PSTA). This rule applies to subsequence B1a2 .

  Subsequence B1a2 if field :22H::PAYM is ...	Subsequence B1a2 then field :19A::PSTA is ...
  APMT	Mandatory
  Not equals APMT	Optional

• C3. In each occurrence of subsequence B1a, in subsequence B1a2, the following Party Fields cannot appear more than once :

  Subsequence B1a2a

  :95a::BUYR

  :95a::DEAG

  :95a::DECU

  :95a::DEI1

  :95a::DEI2

  :95a::PSET

  :95a::REAG

  :95a::RECU

  :95a::REI1

  :95a::REI2

  :95a::SELL

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

  In other words, in subsequence B1a2, the following scenarios must be validated:

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

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

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

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

  In other words, in subsequence B1a2, the following scenarios must be validated:

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

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

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

  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)

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

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

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

• C7. If in sequence A field :17B::CONS=Y, then in every occurrence of sequence B Sub-safekeeping Account, field :97a::SAFE and field :17B::ACTI are mandatory .

  This check only applies when sequence B Sub-safekeeping Account is present as per rule C1, ie, in sequence A, field :17B::ACTI=Y.

  Sequence A if field :17B::ACTI is ...	then sequence B is ...	and sequence A if field :17B::CONS is ...	then in every occurrence of Sequence B field :97a::SAFE and field :17B::ACTI are ...
  Y	Mandatory i.e. minimum one occurrence	Y	Mandatory
  		N	Not allowed
  N	Not allowed	Not Applicable	Not Applicable

• C8. If the Activity Flag (field :17B::ACTI) in sequence B Sub-safekeeping Account indicates no information to be reported, ie, N, then subsequence B1 Financial Instrument must not be present. Subsequence B1 Financial Instrument is otherwise mandatory .

  This check only applies when sequence B Sub-safekeeping Account is present per rule C1, ie, in sequence A, field :17B::ACTI=Y.

  Sequence A if field :17B::ACTI is ...	then sequence B is ...	in every occurrence of sequence B if field :17B::ACTI is ...	in the same occurrence of sequence B then subsequence B1 is ...
  Y	Mandatory i.e. minimum one occurrence	Y	Mandatory i.e. minimum one occurrence
  		N	Not allowed
  		Not present	Mandatory i.e. minimum one occurrence
  N	Not allowed	Not Applicable	Not Applicable

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

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

• C10. A reference to the previously received message must be specified for each transaction reported, i.e. in each occurrence of subsequence B1a Transaction, field :20C::RELA must be present in one and only one occurrence of subsequence B1a1 Linkages; field :20C::RELA is not allowed in all other occurrences of subsequence B1a1 .

MT536 Usage Rules

• This statement is used by the account servicer to report on increases and decreases of holdings which are held for the account owner.

• The frequency of the statement must be bilaterally agreed between the account servicer and the account owner.

• The optional balance fields are available to provide opening and closing balances per security within the holding.

• Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.