MT548 Network Validated Rules

• C1 If the instruction is against payment (:22H::PAYM//APMT) then it is mandatory to specify a settlement amount (field :19A::SETT). This rule applies to sequence B.

  Sequence B if field :22H::PAYM is ...	Sequence B then field :19A::SETT is ...
  APMT	Mandatory
  Not equal to APMT	Optional

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

  Subsequence B1
  :95a::BUYR
  :95a::DEAG
  :95a::DECU
  :95a::DEI1
  :95a::DEI2
  :95a::PSET
  :95a::REAG
  :95a::RECU
  :95a::REI1
  :95a::REI2
  :95a::SELL

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

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

  Sequence B if field :22H::REDE is ...	And if subsequence B1 is ...	Then in one occurrence of subsequence B1 field :95a::REAG
  DELI	Present	Must be present

  Sequence B if field :22H::REDE is ...	And if subsequence B1 is ...	Then in one occurrence of subsequence B1 field :95a::DEAG
  RECE	Present	Must be present

• C4 If a qualifier from the list Deliverers is present in a subsequence B1, 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 B, the following scenarios must be validated:

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

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

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

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

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

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

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

  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 In subsequence B1, if field :95a::PSET is present, then field :97a:: is not allowed in the same subsequence.

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

• C6 Within each occurrence of subsequence A2a, the qualifier in field 24B must be the same as the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence A2.

  In each occurrence of sequence A2 Status
  In each occurrence of subsequence A2a Reason (if present) if field :24B:: is ...	Then in sequence A2 Status, field :25D:: must be ... (1)
  :24B::CAND	:25D::IPRC//CAND or :25D::CPRC//CAND
  :24B::CANP	:25D::IPRC//CANP or :25D::CPRC//CANP
  :24B::CGEN	:25D::IPRC//CGEN
  :24B::DEND	:25D::CPRC//DEND or :25D::CALL//DEND or :25D::TPRC//DEND
  :24B::NMAT	:25D::MTCH//NMAT or :25D::INMH//NMAT
  :24B::PACK	:25D::IPRC//PACK or :25D::CPRC//PACK or :25D::TPRC//PACK
  :24B::PEND	:25D::SETT//PEND
  :24B::PENF	:25D::SETT//PENF
  :24B::REPR	:25D::IPRC//REPR
  :24B::REJT	:25D::IPRC//REJT or :25D::CPRC//REJT or :25D::SPRC//REJT or :25D::TPRC//REJT
  :24B::CACK	:25D::CALL//CACK
  :24B::PPRC	:25D::IPRC//PPRC
  :24B::MOPN	:25D::TPRC//MOPN

  ⁽¹⁾ if the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

  Within each occurrence of subsequence C1a1B1a1 (Reason), the qualifier in field 24B must be the same as or linked to the code (Status Code) used with the appropriate qualifier in field 25D of its surrounding subsequence C1a1B1a (Status).

  In each occurrence of subsequence C1a1B1a Status
  In each occurrence of subsequence C1a1B1a1 Reason (if present) if field :24B:: is ...	Then in subsequence C1a1B1a Status field :25D:: must be ... (1)
  :24B::NMAT	:25D::MTCH//NMAT
  :24B::PENF	:25D::SETT//PEND :25D::SETT//PENF

  ⁽¹⁾ if the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.

• C7 A reference to the previously received message must be specified, that is field 20C::RELA must be present in one and only one occurrence of subsequence A1 Linkages; field 20C::RELA is not allowed in all other occurrences of subsequence A1.

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

• C9 In sequence B, if field :95L::ALTE is present, then field :95a::ACOW must be present.

  In sequence C, if field :95L::ALTE is present, then field :95P::ASDP must be present.

  In subsequence C1a, if field :95L::ALTE is present, then field :95a::ASDP must be present.

  In subsequence C1a, if field :95L::ALRP is present, then field :95a::REPA must be present.

• C10 In sequence B, field :94a::CLEA must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::CLEA).

  In sequence B, field :94a::SAFE must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::SAFE).

  In sequence B, field :94a::TRAD must not be present more than twice. When repeated, one and only one occurrence must be with format option L (:94L::TRAD).

• C11 In each occurrence of sequence D, if field :95a::ALTE is present with format option L, then field :95a::MEOR and field :95a::MERE must not be present in the same occurrence of the sequence.

• C12 If the message is a penalty, that is, Function of the Message (field 23G) is PENA, then sequence B (Settlement Transaction Details) is not allowed and sequence C (Penalties) must be present.

  Sequence A if field :23G: is ...	Then sequence B is ...	And sequence C is ...
  CAST	Optional	Not Allowed
  INST	Optional	Not Allowed
  PENA	Not Allowed	Mandatory

• C13 In subsequence C1a1B1 (Transaction Details), if field 95a is present, all qualifiers of field 95a are optional, but either ACOW or CACO (not both) must be present.

• C14 In subsequence C1a (Penalties per Counterparty) all qualifiers of field 95a are optional, but either ASDP or REPA must be present.

• C15 In subsequence C1a1 (Penalty Details), if field 24B is present, or field 70D, then field 25D must be present.

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

  Subsequence C1a1B1 if field :22H::PAYM is ...	Subsequence C1a1B1 then field :19A::PSTA is ...
  APMT	Mandatory
  Not equal to APMT	Optional