ISO 15022 Data Field Dictionary

MT549 Scope

This message is sent by an account owner to an account servicer (account servicing institution). The account owner may be a global custodian which has an account with its local agent (sub custodian) or an investment management institution or a broker/dealer which has an account with their custodian.

It is used to request one of the following statements:

  • Collateral and Exposure Statement (MT 506)

  • Statement of Holdings (MT 535)

  • Statement of Transactions (MT 536)

  • Statement of Pending Transactions (MT 537)

  • Triparty Collateral and Exposure Statement (MT 569)

  • Statement of Intra-Position Advices (MT 538)

  • Report of Combined Activity (MT 575)

  • Statement of Open Orders (MT 576)

  • Statement of Settlement Allegements (MT 586)

It is also used to request one of the following status messages:

  • Collateral Status and Processing Advice (MT 507)

  • Trade Status (MT 509)

  • Settlement Status and Processing Advice (MT 548)

  • Corporate Actions Status and Processing Advice (MT 567)

  • Registration Status and Processing Advice (MT 510)

  • Triparty Collateral Status and Processing Advice (MT 558)

MT549 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

STAT

Date/Time

Statement Date/Time

A or C

4

O

69a

STAT

Period

Statement Period

A or B

5

M

13A

REQU

Number Identification

Requested Message Type

:4!c//3!c

6

----->

O

95a

4!c

Party

(see qualifier description)

L, P, or R

7

-----|

M

97a

SAFE

Account

Safekeeping Account

A or B

8

----->

O

22F

4!c

Indicator

(see qualifier description)

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

9

-----|

-----> Optional Repetitive Subsequence A1 Linkages

M

16R

 

 

Start of Block

LINK

10

O

13a

LINK

Number Identification

Linked Message

A or B

11

M

20C

4!c

Reference

(see qualifier description)

:4!c//16x

12

M

16S

 

 

End of Block

LINK

13

-----| End of Subsequence A1 Linkages

M

16S

 

 

End of Block

GENL

14

End of Sequence A General Information

-----> Optional Repetitive Sequence B Statement by Status/Reason and/or by Financial Instrument

M

16R

 

 

Start of Block

BYSTAREA

15

O

25D

4!c

Status Code

(see qualifier description)

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

16

----->

O

24B

4!c

Reason Code

(see qualifier description)

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

17

-----|

----->

O

35B

 

 

Identification of the Financial Instrument

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

18

-----|

M

16S

 

 

End of Block

BYSTAREA

19

-----| End of Sequence B Statement by Status/Reason and/or by Financial Instrument

-----> Optional Repetitive Sequence C By Instruction Reference

M

16R

 

 

Start of Block

REF

20

----->

M

20C

4!c

Reference

(see qualifier description)

:4!c//16x

21

-----|

M

16S

 

 

End of Block

REF

22

-----| End of Sequence C By Instruction Reference

Optional Sequence D Additional Information

M

16R

 

 

Start of Block

ADDINFO

23

----->

O

95a

4!c

Party

(see qualifier description)

P, Q, or R

24

-----|

M

16S

 

 

End of Block

ADDINFO

25

End of Sequence D Additional Information

MT549 Network Validated Rules

  • C1 Statement Date/Time (field :98a::STAT) and Statement Period (field :69a:: STAT) are mutually exclusive. This rule applies to sequence A.

    Sequence A

    if field :98a::STAT is ...

    Sequence A

    then field :69a::STAT is ...

    Present

    Not allowed

    Not present

    Optional

  • C2 Sequence B Statement by Status/Reason and/or by Financial Instrument and sequence C Statement by Instruction Reference are mutually exclusive.

    If sequence B is ...

    Then sequence C is ...

    Present

    Not allowed

    Not present

    Optional

  • C3 Within each occurrence of sequence B, the qualifier field 24B must be the same as the code word (Status Code) used with the appropriate qualifier in field 25D of the same occurrence of sequence B.

    In each occurrence of sequence B Statement by Status/Reason and/or by Financial Instrument:

    If field :24B:: is present and is ...

    Then field :25D:: is mandatory and must be ... (1)

    :24B::NMAT

    :25D::MTCH//NMAT

    :25D::INMH//NMAT

    :24B::PEND

    :25D::EPRC//PEND or

    :25D::SETT//PEND or

    :25D::RPRC//PEND

    :24B::PENF

    :25D::SETT//PENF

    :24B::REJT

    :25D::IPRC//REJT or

    :25D::CPRC//REJT or

    :25D::RPRC//REJT or

    :25D::RERC//REJT or

    :25D::REST//REJT or

    :25D::TPRC//REJT

    :24B::DEND

    :25D::CPRC//DEND or

    :25D::RPRC//DEND or

    :25D::CALL//DEND or

    :25D::TPRC//DEND

    :24B::CAND

    :25D::IPRC//CAND or

    :25D::CPRC//CAND

    :24B::CANP

    :25D::IPRC//CANP or

    :25D::CPRC//CANP

    :24B::CGEN

    :25D::IPRC//CGEN

    :24B::NAFI

    :25D::AFFM//NAFI

    :24B::PACK

    :25D::IPRC//PACK or

    :25D::CPRC//PACK or

    :25D::RPRC//PACK or

    :25D::RERC//PACK or

    :25D::TPRC//PACK

    :24B::CACK

    :25D::CALL//CACK

    :24B::REPR

    :25D::CPRC//REPR or

    :25D::IPRC//REPR or

    :25D::RPRC//REPR

    :24B::PPRC

    :25D::IPRC//PPRC

    :24B::MOPN

    :25D::TPRC//MOPN

    field ::24B:: is not present

    Rule does not apply

    (1) if the Data Source Scheme is present in field :25D:: then the conditional rule does not apply.
  • C4 If the message is a cancellation, that is, 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 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 subsequence A1, and not allowed in all other occurrences of subsequence A1

    NEWM

    Optional

    Not applicable

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

MT549 Usage Rules

  • Where the message is used to request a statement of pending transactions, the Sender may specify all or selected statuses and/or reasons why the transaction is pending, and for all or selected securities.

  • Where the message is used to request the status of one or more specific instructions, the By Instruction Reference sequence should be used to specify the references of this/these instruction(s).

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