ISO 15022 Data Field Dictionary

MT548 Scope

This message is sent by an account servicer (account servicing Institution) to an account owner or its designated agent. The account servicer may be a local agent (sub-custodian) acting on behalf of their global custodian customer, or a custodian acting on behalf of an investment management institution or a broker/dealer.

This message is used to advise the status of a settlement instruction previously sent by the account owner (the function of the message is INST).

The message may also be used to report on future settlement or forward transactions, for example, free receipts for which no instruction is required, which have become binding on the account owner.

The underlying instruction must be either a deliver or receive and be either free or against payment.

It is also used to reply to a cancellation request previously sent by the account owner (the function of the message is CAST).

MT548 Format Specifications

Status Tag Qualifier Generic Field Name Detailed Field Name Content/Options No.

Mandatory Sequence A General Information

M

16R

 

 

Start of Block

GENL

1

M

20C

SEME

Reference

Sender's Message Reference

:4!c//16x

2

M

23G

 

 

Function of the Message

4!c[/4!c]

3

O

98a

PREP

Date/Time

Preparation Date/Time

A, C, or E

4

-----> Mandatory Repetitive Subsequence A1 Linkages

M

16R

 

 

Start of Block

LINK

5

O

13a

LINK

Number Identification

Linked Message

A or B

6

M

20C

4!c

Reference

(see qualifier description)

:4!c//16x

7

M

16S

 

 

End of Block

LINK

8

-----| End of Subsequence A1 Linkages

-----> Mandatory Repetitive Subsequence A2 Status

M

16R

 

 

Start of Block

STAT

9

M

25D

4!c

Status Code

(see qualifier description)

:4!c/[8c]/4!c

10

-----> Optional Repetitive Subsequence A2a Reason

M

16R

 

 

Start of Block

REAS

11

M

24B

4!c

Reason Code

(see qualifier description)

:4!c/[8c]/4!c

12

O

70D

REAS

Narrative

Reason Narrative

:4!c//6*35x

13

M

16S

 

 

End of Block

REAS

14

-----| End of Subsequence A2a Reason

M

16S

 

 

End of Block

STAT

15

-----| End of Subsequence A2 Status

M

16S

 

 

End of Block

GENL

16

End of Sequence A General Information

Optional Sequence B Settlement Transaction Details

M

16R

 

 

Start of Block

SETTRAN

17

----->

O

94a

4!c

Place

(see qualifier description)

B, C, F, H, or L

18

-----|

M

35B

 

 

Identification of the Financial Instrument

[ISIN1!e12!c]
[4*35x]

19

----->

M

36B

SETT

Quantity of Financial Instrument

Quantity of Financial Instrument to be Settled

:4!c//4!c/15d

20

-----|

----->

O

19A

4!c

Amount

(see qualifier description)

:4!c//[N]3!a15d

21

-----|

----->

O

95a

4!c

Party

(see qualifier description)

L, P, or R

22

-----|

M

97a

SAFE

Account

Safekeeping Account

A or B

23

----->

M

22a

4!c

Indicator

(see qualifier description)

F or H

24

-----|

----->

M

98a

4!c

Date/Time

(see qualifier description)

A, B, C, or E

25

-----|

O

70E

SPRO

Narrative

Settlement Instruction Processing Narrative

:4!c//10*35x

26

-----> Optional Repetitive Subsequence B1 Settlement Parties

M

16R

 

 

Start of Block

SETPRTY

27

----->

M

95a

4!c

Party

(see qualifier description)

C, L, P, Q, or R

28

-----|

O

97a

SAFE

Account

Safekeeping Account

A or B

29

O

20C

PROC

Reference

Processing Reference

:4!c//16x

30

M

16S

 

 

End of Block

SETPRTY

31

-----| End of Subsequence B1 Settlement Parties

M

16S

 

 

End of Block

SETTRAN

32

End of Sequence B Settlement Transaction Details

-----> Optional Repetitive Sequence C Additional Information

M

16R

 

 

Start of Block

ADDINFO

33

----->

O

95a

4!c

Party

(see qualifier description)

C, L, P, Q, or R

34

-----|

M

16S

 

 

End of Block

ADDINFO

35

-----| End of Sequence C Additional Information

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::SAFE is not allowed in the same subsequence.

    Subsequence B1

    if field :95a::PSET is ...

    Subsequence B1

    then field :97a::SAFE 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 word (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

    (1) 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.

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

MT548 Usage Rules

  • When the message is used as an advice of status, the linkage sequence must contain the reference of the original instruction.

  • When the message is used as a cancellation reply, the linkage sequence must contain the reference of the cancellation request.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------