25.02 ims15022 participant messages/media/files/downloads/settlement... · 25.02 ims15022...

Depository Trust Company

25.02 IMS15022 Participant Messages

Version 2.6 Date updated: June 26, 2003


Copyright © 2003 by The Depository Trust Company (“DTC”). All rights reserved. This work is proprietary and is intended for the exclusive use of DTC’s Participants and other users of DTC’s services. No part of this work may be reproduced or distributed (including by transmission) in any form or by any means, or stored in any information storage and retrieval system, without DTC’s prior written permission. All requests for additional copies of this work or inquiries about this work should be directed to DTC Participant Interface Planning, The Depository Trust Company, 55 Water Street, New York, NY 10041, USA.

25.02 IMS 15022 Participant Messages Page ii Copyright © 2003 by The Depository Trust Company 6/26/2003


Revision History

Date By Version Description

May 22, 2003 Robert Brenner 2.6 Document created

25.02 IMS 15022 Participant Messages Page iii Copyright © 2003 by The Depository Trust Company 6/26/2003


Table of Contents 1 PROPOSED ISO 15022 MESSAGES .......................................................................................................1

1.1 Introduction .......................................................................................................................................1 1.1.1 A Short Primer On ISO 15022 .....................................................................................................1

1.1.1.1 Message Type Format Specifications .................................................................................................... 1 1.1.1.2 Field Formatting Rules ........................................................................................................................... 3 1.1.1.3 Field Structure........................................................................................................................................ 3

1.1.2 Suppressed Elements..................................................................................................................5 1.1.3 Source Codes ..............................................................................................................................5 1.1.4 Party Types ..................................................................................................................................9 1.1.5 Reference Qualifiers ..................................................................................................................10

1.2 Participant Messages .....................................................................................................................11 1.2.1 Command Message...................................................................................................................11

1.2.1.1 Overview .............................................................................................................................................. 11 1.2.1.2 Field Descriptions................................................................................................................................. 11

1.2.2 Transaction Notification Message..............................................................................................19 1.2.2.1 Long Version ........................................................................................................................................ 19

1.2.2.1.1 Overview ....................................................................................................................................... 19 1.2.2.1.2 Field Descriptions.......................................................................................................................... 19

1.2.2.2 Short Version ....................................................................................................................................... 31 1.2.2.2.1 Overview ....................................................................................................................................... 31 1.2.2.2.2 Field Descriptions.......................................................................................................................... 31

1.2.3 Command Notification Message................................................................................................35 1.2.3.1 Overview .............................................................................................................................................. 35 1.2.3.2 Field Descriptions................................................................................................................................. 35

1.2.4 Transaction Warning Message ..................................................................................................42 1.2.4.1 Overview .............................................................................................................................................. 42 1.2.4.2 Field Descriptions................................................................................................................................. 42

25.02 IMS 15022 Participant Messages Page iv Copyright © 2003 by The Depository Trust Company 6/26/2003


1 Proposed ISO 15022 Messages 1.1 Introduction The purpose of this document is to describe the format of messages sent to and received from IMS in compliance with ISO 15022. Participants will use these messages to send commands to IMS and receive real-time state change notification messages from IMS.

This document is divided into two major sections. Section 1.1 provides a general introduction to ISO 15022. Section 1.2 describes messages specific to Participants.

1.1.1 A Short Primer On ISO 15022 The following is a short primer on the ISO 15022 message specification. It is not a substitute for familiarizing yourself with the actual specification. This material is adapted from the SWIFT User Handbook. The relevant publications are:

• Standards - General Information describes general info about SWIFT. Section 1.2 - Formatting Explanation, Chapter 4 - Message Structure & Message Types, and Chapter 5 - Field Structure are particularly informative.

• Standards - Category 5 - Securities Markets describes message types specific to the securities industry. The message types defined in this document are based on MT 548 - Settlement Status and Processing Advice.

1.1.1.1 Message Type Format Specifications The format specifications are the rules for the layout of the message type. This information is provided in table form with the following information:

MT nnn (Message Type Name)

Status Tag Field Name Content/Options IMS

M 20 Transaction Reference Number 16x

M 21 Related Reference 16x

Mandatory Sequence A (Sequence Name)

M 25 Account Identification 35x

M 32a Value Date, Currency Code, Amount C or D

----> Optional Repetitive Sequence B (Sequence Name)

O 52a Ordering Institution A or D

M 71B Details of Charges 6*35x

O 72 Sender to Receiver Information 6*35x

25.02 IMS 15022 Participant Messages Page 1 Copyright © 2003 by The Depository Trust Company 6/26/2003


----|

M = Mandatory O = Optional

MT nnn (Message Type Name) provides the message type number and name.

• Status indicates if the field is:

• M - Mandatory

• O - Optional

The status M for fields in optional (sub)sequences means that the field must be present if the (sub)sequence is present, and is otherwise not allowed.

• Tag is the field identification

• Field Name is the detailed name of the field tag, for this message type

• Content/Options provides permitted field length and characteristics.

• IMS specifies exactly how the field will be used by IMS. Only fields, and field tag options which are shown in the message format, may be used in that message type. Some message formats are separated into sequences of fields, as shown below. An arrow indicates that a sequence of fields may be repeated.

First Sequence

Second Sequence The arrow indicates that this sequence may be repeated ------->

-------|

Third Sequence



1.1.1.2 Field Formatting Rules The following general rules apply to all fields:

1. the field length and type of character(s), e.g., letters, numbers, are specified in the Standards General Field Definitions plus, and in the field specifications for individual message types

2. unless otherwise stated in the Standards General Field Definitions plus, or message field specifications, all specified subfields must be present:

• in the order (i.e., sequence) specified

• with no separator symbols (except a slash ‘/’ or double slash ‘//’, when specified)

3. brackets, [ ], around the format of a particular subfield (in a field containing more than one subfield), indicate that the subfield is optional within that field

For example, if the format for a field is ‘16x[/4x]’, up to 16 characters must be present (when the field is used). The following 4 characters, preceded by a slash ‘/’, are optional, and therefore may not be present in the field.

4. a field format may be shown on two or more lines: 3!n 6!n

When this is the case, the information must be formatted with the CrLf character separating each line.

1.1.1.3 Field Structure There are several rules which must be followed when structuring fields.

1. Each field is identified by a tag which consists of two digits, or two digits followed by a letter option

2. Field structure consists of a colon ‘:’, followed by a tag, followed by a colon ‘:’ and the field content

3. The following character restrictions are applied to field content:

• it must not start with a Carriage Return, Line Feed (CrLf)

• it must not be entirely composed of blank characters

• within field content, apart from the first character of the field, a colon ‘:’ or hyphen ‘-‘ must never be used as the first character of a line

• except for fields 15a and 77E, a field must consist of at least one meaningful character (See Standards General Field Definitions plus for formatting requirements.)

4. Fields are separated by a ‘Field Separator within Text’ (CrLf:).

5. The first field in a message is preceded by a ‘Start of Text’ (CrLf:) and the last field in a message is followed by an ‘End of Text’ (CrLf-).

6. The Carriage Return, Line Feed character must always appear as a sequence. This sequence shall



only be used to indicate start of text, as a field separation within text, to indicate a new line, and to indicate the end of text.

7. Field content may be composed of one or several subfields.

When subfields appear on separate lines, the Carriage Return, Line Feed (CrLf), which is not included in the number of characters for the length of the subfield, serves as the subfield separator.

• subfields may themselves be of fixed or variable length

• the order of subfields is fixed

• when necessary, subfields are separated by special symbols, e.g., ‘/’ or ‘//’

• subfields must not be entirely composed of blank characters

• subfields and/or components must consist of at least one meaningful character

8. Whenever a field content contains mandatory and optional subfields, at least all of the mandatory subfields must appear when that field is used

9. The specification of field or subfield content may consist of:

• restrictions on the length of field or subfield content, using the descriptions listed below:

Restrictions on Length Types of Characters Allowed

nn

nn-nn

Maximum length

Minimum and maximum length

n

a

c

h

Digits only

Alphabetic letters, upper case only

Alphabetic letters (upper case) and digits only

Hexadecimal letters A through F (upper case) and digits only

nn! Fixed length x Any character of the permitted character set upper and lower case

y Any character of the EDIFACT level A character set as defined in ISO 9735 upper case only

z Any character as defined by the Information Service

nn*nn Maximum number of lines times maximum line length

e Blank space

d



Examples

2n = up to 2 digits

3!a = always 3 letters

4*35x = up to 4 lines of up to 35 characters each

16-64h

= at least 16 and up to 64 hexadecimal digits

• special formats, e.g., for numbers and dates

• codes, e.g., currency codes (see International Bank Identifier Code Directory [green pages])

10. In some messages, the field specifications may indicate specific characters, or sets of characters, for inclusion in the text of the field. These take the following forms:

• codes, e.g., AMEND, TRF or 08

• slash ‘/’ or double slash ‘//’

• slash or double slash followed by a code, e.g., //CH or /FIXED

• slash followed by a code and another slash, e.g., /REC/ Note: All codes must be in upper-case alphabetic characters. When codes contain a mix of alpha and numeric characters, the alpha character must also be in uppercase.

1.1.2 Suppressed Elements Sequences, subsequences, and fields marked as “suppress” are optional elements of the ISO 15022 specification that are not supported by IMS. They should not be included in messages sent or received by IMS. If they are included in messages received by IMS, IMS will ignore them in terms of processing the message; however, IMS will store them in the Raw Text Table for auditing purposes.

1.1.3 Source Codes Many fields take a one-to-eight character (8c) source code. This source code allows implementers to define their own values for these fields. Wherever possible, we have included the source code DTCYcccc in fields in order to use DTCC-specific values instead of the generic values defined by ISO 15022, where cccc indicates the purpose of the source code. Table 1 describes these source codes: Table 1: Source Codes

Source Code Description

DTCYACTV/<activity> DTC activity code.

DTCYERCD/<error> DTCC error code. Reason why transaction was canceled, dropped, or rejected, or is pending.

DTCYID/<fins> FINS number. Used to identify financial institution.




DTCYIFMT/<input format> Format transaction was input to IMS, where <input format> is one of the following:

• ISO1 – ISO 15022 message format

• ANEX – ANE proprietary message format

• GUIX – PBS web page

• 3270 – PTS 3270 screen

DTCYISRC/<internal source code>

Identifier of DTC application that input transaction to IMS.

DTCYPART/<partnum> DTC participant number.

DTCYPROC/<processing> IMS normal or express processing, where <processing> is one of the following:

• NORM – normal processing

• XPRS - express processing

DTCYRCVD/yyyymmdd Date transaction was input to IMS.

DTCYREAS/<reason> DTC reason code.

DTCYSCGP/<security group> Participant classification of security.




DTCYSTAT/<state> IMS transaction state, where <state> is one of the following:

• AUTH - authorized

• CANC - canceled

• PDRP - dropped permanent

• RDPR - dropped reintroduce

• GREN - green

• MAKD – made

• PMPN - Part made, part pending

• MPPD - Part made, part pending, part permanently dropped

• PMPD - Part made, part permanently dropped

• PPPD - Part pending, part permanently dropped

• RAUT - RAD authorized

• REDD - red

• RGRN - recycling green

• RJCT - rejected

• RLSD - released

• RRED - recycling red

• RSUB - submitted to RAD

• XPER - recycling express

• RYLW - recycling yellow

• SUBA - submitted to ATP

• UNPR – unprocessed

• WARN – transaction has encountered a warning condition.

• XMPT - exempted

• XPRS - expressed

• YELL - yellow

DTCYSUBA/<subactivity> DTC subactivity code.




DTCYTXNT/<txntype> IMS transaction type, where <txntype> is one of the following:

• ALLT – all transaction types

• MITS – matched institutional trades

• NDOS – night delivery orders

• ACATS – ACATS transactions

• CNSS – CNS transactions. Not valid with XMPT command.

• RDRP – reintroduced drops

DTCYUSER/<userid> DTC user id.



1.1.4 Party Types Table 2 lists the party types support by this message protocol. Table 2: Party Types

Party Sequence Qualifier - MT 543 Deliver Against Payment

MT 541 Receive Against Payment

Institution E1: Settlement Parties

SELL BUYR

Clearing Agent E1: Settlement Parties

DECU RECU

Clearing Agent Sub-Custodian

E1: Settlement Parties

DEAG REAG

Executing Broker E1: Settlement Parties

BUYR SELL

Clearing Broker E1: Settlement Parties

RECU DECU

Clearing Broker Sub-Custodian

E1: Settlement Parties

REAG DEAG

Matching Utility F: Other Parties MTUT

MU Agent F: Other Parties MTAG



1.1.5 Reference Qualifiers Table 3 lists the reference qualifiers supported by this message protocol: Table 3: Reference Qualifiers

Qualifier Description

COMM Reference assigned by MU to transaction.

TRRF Reference assigned by delivering participant to transaction.

RELA Reference assigned by IMS to transaction.

PREV Reference assigned by ATP to transaction.



1.2 Participant Messages

1.2.1 Command Message

1.2.1.1 Overview For phase 1, this message will be used by delivering participants to authorize, exempt, unexempt, or cancel transactions, or to change authorization modes. In later phases, other commands will be added to this message type.

This message can impact transactions globally, by asset class-transaction type pairs, or by lists of transactions. The transaction list can be as short as a single transaction, i.e., the command can impact an individual transaction.

This message is not based on any existing Message Type (MT) in the ISO 15022 message specification. We are currently in the process of applying to ISO to formally add this MT to their specification. This message has been assigned MT530.

Note that selecting ALLA (all asset classes) and ALLT (all transactions types) is the equivalent of entering a selecting a scope of GLBL (global).

For phase 1, IMS will only support DTC-defined asset classes. In later phases, IMS will also support “security groups,” i.e., participant-defined asset classes.

1.2.1.2 Field Descriptions

MT 530 IMS Commands

Status Tag Qualifier Generic Field Name

Detailed Field Name

Content/Options IMS

Mandatory Sequence A General Information

M 16R Start of Block

GENL 16R:GENL

M 20C SEME Reference Sender’s Reference

:4!c//16x 20C:SEME//16x

M 23G Function of the Message

4!c[/4!c] 23G:NEWM

M 16S End of Block

GENL 16S:GENL

End Mandatory Sequence A General Information Mandatory Sequence B Command Parties



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS


CMDPRTY 16R:CMDPRTY

M 95a 4!c Party (see qualifier description)

Option R

:4!c/8c/34x

or

Option P

:4!c//4!a2!a2!c[3!c]

95R:SELL/DTCYPART/<partnum>

or

95P:SELL//<bic>

where <partnum> is the participant number of the deliverer. Or BIC.


Option R

:4!c/8c/34x 95R:SELL/DTCYUSER/<userid>

where <userid> is the ID of the “user” (probably an application, since this is an electronic message).

M 16S End of Block

CMDPRTY 16S: CMDPRTY

End Mandatory Sequence B Command Parties Mandatory Sequence C Command/Scope


CMDSCOP 16R:CMDSCOP



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

M 22F 4!c Indicator (see qualifier description)

:4!c/[8c]/4!c 22F:SETR/ /<command>, where <command> is one of the following for phase 1:

• AUTH – authorization

• XMPT – exemption.

• UXMP – unexemption

• KILL – kill transaction. Invalid with CNSS transaction type. Invalid with GLBL command scope.

• MODE – change mode. Invalid with LIST scope.

Additional commands for phase 2 and 3 may include:

• RELS – release

• CCLR – change color

• CPRI - change priority

• PATH – partially authorize

• BSTK – borrow stock

• RSTK – return stock

• LINK – link transactions

• ULNK – unlink transactions

• BFOR – move before

• AFTR – move after



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

M 22F 4!c Indicator (see qualifier description)

:4!c/[8c]/4!c 22F:PROC/ /<scope>

where <scope> is one of the following:

• GLBL – global. Invalid with KILL command. Invalid with the CNSS transaction type.

• ASTN – by asset class/transaction type

• LIST – list of transactions. Invalid with MODE command.

M 98a 4!c Date/Time (see qualifier description)

Option A

:4!c//8!n 98A:SETT//yyyymmdd

where yyyymmdd is the original intended settlement date of the transaction(s).

-----> Repetitive Optional Subsequence C1 Asset Classes/Transaction Types . -----> Repeat for one or more asset class/transaction type pairs, where <scope> = ASTN. Otherwise, suppress.


ASST 16R:ASTN



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

O 12a 4!c Type of Financial Instrument

(see qualifier description)

Option A

:4!c/[8c]/30x 12A:CLAS/ /<asset class>

or

12A:CLAS/DTCYSCGP/<security group>

where <asset class> is a DTC-defined asset class:

• ALLA – all asset classes

• MMIS – money market instruments

• EQTS - equities

• CRBD – corporate bonds

• MUNI – municipal bonds

And <security group> is a participant-defined asset class (phase II).



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

O 22F 4!c Indicator (see qualifier description)

:4!c/[8c]/4!c 22F:PROC/DTCYTXNT/<txntype>

where <txntype> is one of the following:

• ALLT – all transaction types

• MITS – matched institutional trades

• NDOS – night delivery orders

• ACATS – ACATS transactions

• CNSS – CNS transactions. Not valid with KILL command.

• RDRP – reintroduced drops

Used to specify the transaction types where <scope> is ASTN. Otherwise, suppress.

M 16S End of Block

ASTN 16S:ASTN

-----| End of Subsequence C1 Asset Classes/Transaction Types

-----> Repetitive Optional Subsequence C2 Linkages Repeat for one or more transactions, where <scope> = LIST. Otherwise, suppress.


LINK 16R:LINK



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

M 20C 4!c Reference (see qualifier description)

:4!c//16x 20C:COMM//<mutid>

20C:TRRF//<dlvtid>

20C:RELA//<imstid>

20C:PREV//<atptid>

where <mutid> is the TID assigned to the transaction by the matching utility, <dlvtid> is the TID assigned to the transaction by the deliverer, <imstid> is the TID IMS assigned to the transaction, and <atptid> is the TID ATP assigned to the transaction.

Note that for phase 1 using <atptid> only makes sense if you are canceling a transaction that is recycling in ATP. For all other commands and transaction states, the transaction will not have been submitted yet to ATP for execution; therefore, the transaction will not have been assigned an ATP TID yet.

M 16S End of Block

LINK 16S:LINK

-----| End of Subsequence C2 Linkages

-----> Optional Subsequence C3 Mode ----->Mandatory if <command> = MODE; suppress otherwise.


MODE 16R:MODE



MT 530 IMS Commands


Detailed Field Name

Content/Options IMS

M 22F

4!c Indicator (see qualifier description)

:4!c/[8c]/4!c 22F:PROC/ /<mode>

where <mode> is one of the following:

• ACTV – active authorization

• PASS – passive authorization

M 16S End of Block

MODE 16S:MODE

-----| End of Subsequence C3 Mode

M 16S End of Block

CMDSCOP 16S: CMDSCOP

End of Sequence C Command Scope




1.2.2 Transaction Notification Message A notification message is sent when a transaction’s state changes. There are two versions of the notification message: long and short. These are described in the following subsections. Which version is sent is determined by the interested party’s Notification Profile. We anticipate most interested parties will elect to receive the long version for the initial (UNPROCESSED) state, and the short version for all subsequent states.

1.2.2.1 Long Version 1.2.2.1.1 Overview The long version of the notification message resembles a record from the Transaction Table. That is, it contains basically all the information IMS has about a transaction. 1.2.2.1.2 Field Descriptions

MT 548 Settlement Status and Processing Advice


Detailed Field Name

Content/ Options

IMS


M 16R Start of Block GENL 16R:GENL

M 20C SEME Reference

Sender’s Reference

:4!c//16x 20C:SEME//16x


4!c[/4!c] 23G:INST

Mandatory for our purposes

98a PREP Date/Time

Preparation Date/Time

Option C

:4!c//8!n6!n 98C:PREP//yyyymmddhhmmss

where yyyymmddhhmmss is Transaction Update Date/Time field from State table.

-----> Repetitive Mandatory Subsequence A1 Linkages. Repeat this subsequence for as many TIDs as are available: MU TID, Deliverer TID, IMS TID, ATP TID.

M 16R Start of Block LINK 16R:LINK





Detailed Field Name

Content/ Options

IMS

O 13A LINK Number Identification

Linked Transaction

:4!c//3!c 13A:LINK//543

for sell-side (delivery) transactions, or

13A:LINK//541

for buy-side (receive) transactions.



20C:TRRF//<dlvtid>

20C:RELA//<imstid>

20C:PREV//<atptid>


M 16S End of Block LINK 16S:LINK

-----| End of Subsequence A1 Linkages -----> Repetitive Mandatory Subsequence A2 Status

M 16R Start of Block STAT 16R:STAT

M 25D 4!c Status (see qualifier description)

:4!c/[8c]/4!c 25D:IPRC/DTCYSTAT/<state>, where <state> is one of the following:

• AUTH – AUTHORIZED





Detailed Field Name

Content/ Options

IMS

• CANC - CANCELED

• PDRP - DROPPED PERMANENT

• RDPR - DROPPED REINTRODUCE

• GREN - GREEN

• MAKD - MADE

• PMPN - PART MADE, PART PENDING

• MPPD - PART MADE, PART PENDING, PART PERMANENTLY DROPPED

• PMPD - PART MADE, PART PERMANENTLY DROPPED

• PPPD - PART PENDING, PART PERMANENTLY DROPPED

• RAUT - RECEIVER AUTHORIZED

• REDD - RED

• RGRN - RECYCLING GREEN

• RJCT - REJECTED

• RLSD - RELEASED

• RRED - RECYCLING RED





Detailed Field Name

Content/ Options

IMS

• RSUB - SUBMITTED TO RAD

• XPER - RECYCLING EXPRESS

• RYLW - RECYCLING YELLOW

• SUBA - SUBMITTED TO ATP

• UNPR - UNPROCESSED

• XMPT - EXEMPTED

• XPRS - EXPRESSED

• YELL - YELLOW

-----> Repetitive Optional Subsequence A2a Reason

M 16R Start of Block REAS 16R:REAS





Detailed Field Name

Content/ Options

IMS

M 24B 4!c Reason (see qualifier description)

:4!c/[8c]/4!c 24B:<qualifier>/DTCYERCD/<error>

Where <qualifier> is one of the following:

• CAND – cancellation

• PEND – pending (recycling)

• REJT – reject. Transaction could not be processed for syntax reasons.

• DROP – dropped. Transaction could not be processed for business reasons.

And <error> is Reason field from Transaction State Table.

The qualifier used is determined by the current state of the transaction, e.g., a transaction in the CANCELED state would use the CAND qualifier.

Note the DROP is not part of the ISO 15022 standard and would have to be added.

O 70D REAS Narrative Reason Narrative :4!c//6*35x 70D:REAS//<narrative>

where <narrative> is Narrative field in Transaction Table.

M 16S End of Block REAS 16S:REAS

-----| End of Subsequence A2a Reason





Detailed Field Name

Content/ Options

IMS

M 16S End of Block STAT 16S:STAT

-----| End of Subsequence A2 Status

M 16S End of Block GENL 16S:GENL

End of Sequence A General Information Optional Sequence B Settlement Transaction Details


SETTRAN

16R:SETTRAN

M 35B Identification of the Financial Instrument

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

35B:ISIN <country><cusip><check>

where <country> is stored in Country Code field, <cusip> is stored in Cusip field, and <check> is stored in Check Digit field of the Transaction Table.

----->





Detailed Field Name

Content/ Options

IMS

M 36B SETT Quantity of Financial Instrument

Quantity of Financial Instrument to be Settled

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

36B:SETT//UNIT/<quantity>

where <quantity> is Quantity field from Transaction Table.

The following qualifiers are only valid for transactions of type CNSS:

36B:AUTH//UNIT/<quantity>

where <quantity> is number of shares authorized by the deliverer to be settled.

36B:MADE//UNIT/<quantity>

where <quantity> is the number of shares actually delivered.

36B:DROP//UNIT/<quantity>

where <quantity> is the number of shares that could not be delivered.

36B:RSTT//UNIT/<quantity>

where <quantity> is the number of shares recycling.

-----|

----->

O 19A 4!c Amount (see qualifier description)

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

19A:SETT//<currency><amount>

where <currency> is Currency field from Transaction Table and <amount> is Amount field for transaction table.

-----|





Detailed Field Name

Content/ Options

IMS

M 97a SAFE Account Safekeeping Account

Option A

:4!c//35x 97A:SAFE//<account>

where <account> is:

• The Deliverer’s Account if this message is linked to a 543.

• The Receiver’s Account if this message is linked to a 541.

----->Repeat following field for each field in Transaction Table that isn’t null.





Detailed Field Name

Content/ Options

IMS

M 22a 4!c Indicator (see qualifier description)

Option F

:4!c/[8c]/4!c 22F:SETR/DTCYIFMT/<input format>

where <input format> indicates how the transaction was input into IMS.

22F:SETR/DTCYPROC/<processing>

where <processing> indicates whether the transaction is being processed normally or going express.

22F:SETR/DTCYTXNT/<imstxntype>

where <imstxntype> indicates the IMS transaction type assigned to the transaction.

22F:SETR/DTCYISRC/<internal source code>

where <internal source code> is the DTC application that sent the transaction to IMS.

22F:SETR/DTCYACTV/<activity code>

22F:SETR/DTCYSUBA/<subactivity code>

22F:SETR/DTCYREAS/<reason code>

-----| ----->Repeat following field for each date available.





Detailed Field Name

Content/ Options

IMS

M 98a 4!c Date/Time (see qualifier description)

Option A

:4!c//8!n

Option B

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

98A:EXSE//yyyymmdd

where <yyyymmdd> is Settlement Date field from Transaction Table. This is the date the transaction is intended to settle.

98A:SETT//yyyymmdd

where <yyyymmdd> is Business Date from State Table. This is the date the transaction actually settles.

98A:TRAD//yyyymmdd

where yyyymmdd is Trade Date from Transaction Table.

98B:SETT/DTCYRCVD/yyyymmdd

where <yyyymmdd> is date IMS received transaction

-----|

O 70E SPRO Narrative Settlement Instruction Processing Narrative

:4!c//10*35x Suppress

-----> Repetitive Optional Subsequence B1 Settlement Parties. Repeat subsequence once for each of the following parties to the trade: Institution, Clearing Agent, Clearing Agent Sub-Custodian, Executing Broker, Clearing Broker, Clearing Broker Sub-Custodian.

M 16R Start of Block SETPRTY 16R:SETPRTY





Detailed Field Name

Content/ Options

IMS


Option P

:4!c//4!a2!a2!c[3!c]

Option R

:4!c/8c/34x

95P:<type>//<bic>

or

95R:<type>/DTCYPART/<participant number>

or

95R:<type>/DTCYID/<fins number>

where <type> is Party Type, <bic> is the BIC or BEI of the party, <participant number> is the DTC participant number of the party, and<fins number> is the FINS number associated with an institution. If party is identified by both BIC/BEI and participant number, use participant number format. If institution, use the FINS number.

O 97a SAFE Account

Safekeeping Account

Option A

:4!c//35x 97A:SAFE//<account>

where <account> is account associated with party.

For agents, this will be the AIA number. For brokers, this will be the BIA number.

M 16S End of Block SETPRTY 16S:SETPRTY

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

M 16S End of Block SETTRAN 16S:SETTRAN





Detailed Field Name

Content/ Options

IMS

End of Sequence B Settlement Transaction Details Optional Sequence C Additional Information Repeat for each of the following parties: Matching Utility and Matching Utility Agent

M 16R Start of Block ADDINFO 16R: ADDINFO

----->

O 95a 4!c Party (see qualifier description)

Option R

:4!c/8c/34x

or

Option P

:4!c//4!a2!a2!c[3!c]

or

Option Q

:4!c//4*35x

95R:<party>/DTCYPART/<partnum>

or

95P:<party>//<bic>

or

95Q:<party>//<name>

where <party> is either MTUT (matching utility) or MTAG (matching utility agent), <partnum> is a DTCC participant number, <bic> is a BIC/BEI code, and <name> is the name of the party.

-----|

M 16S End of Block ADDINFO 16S:ADDINFO

End of Sequence C Additional Information




1.2.2.2 Short Version 1.2.2.2.1 Overview The short version of the notification message resembles a record from the Transaction State Table. That is, it contains just enough information to inform interested parties that a transaction’s state has changed. This message format is based upon an MT 548 Settlement Status and Processing Advice, with most of the optional fields suppressed. 1.2.2.2.2 Field Descriptions



Detailed Field Name

Content/ Options

IMS



GENL 16R:GENL


:4!c//16x 20C:SEME//16x


4!c[/4!c] 23G:INST

Man-datory for our purposes

98a PREP Date/Time Preparation Date/Time

Option C


where yyyymmddhhmmss is Transaction Update Date/Time from State table.



LINK 16R:LINK





Detailed Field Name

Content/ Options

IMS

O 13A LINK Number Identific-ation

Linked Transac-tion

:4!c//3!c 13A:LINK//543


13A:LINK//541


M 20C 4!c Reference (see qualifier descrip-tion)


20C:TRRF//<dlvtid>

20C:RELA//<imstid>

20C:PREV//<atptid>

where <mutid> is the TID assigned to the transaction by the matching utility, <dlvtid> is the TID assigned to the transaction by the deliverer, <imstid> is the TID IMS assigned to the transaction, and <atptid> is the TID IMS assigned to the transaction.

M 16S End of Block

LINK 16S:LINK



STAT 16R:STAT


:4!c/[8c]/4!c 25D:IPRC/DTCYSTAT/<state>, where <state> is Transaction State.






Detailed Field Name

Content/ Options

IMS


REAS 16R:REAS

M 24B 4!c Reason (see qualifier descrip-tion)

:4!c/[8c]/4!c 24B:<qualifier>/DTCYERCD/<reason>

Where <qualifier> is one of the following:

• CAND – cancellation

• PEND – pending (recycling)

• REJT – reject. Transaction could not be processed for syntax reasons.

• DROP – dropped. Transaction could not be processed for business reasons.

• PART – partially made, partially pending, partially dropped.

And <reason> is Reason field from Transaction State Table.

The qualifier used is determined by the current state of the transaction, e.g., a transaction in the CANCELED state would use the CAND qualifier.

Note the DROP is not part of the ISO 15022 standard and would have to be added.

O 70D REAS Narrative Reason Narrative

:4!c//6*35x 70D:REAS//<narrative>

where <narrative> is Narrative field in Transaction Table.





Detailed Field Name

Content/ Options

IMS

M 16S End of Block

REAS 16S:REAS


M 16S End of Block

STAT 16S:STAT


M 16S End of Block

GENL 16S:GENL

End of Sequence A General Information

----->




1.2.3 Command Notification Message

1.2.3.1 Overview If IMS cannot execute a command message (section 1.2.10) for some reason, then IMS will send a command notification message to the sender of the command message (i.e., the delivering participant) explaining why the command message could not be executed.

If IMS successfully executes a command message, then IMS will not send a command notification message acknowledging execution of the command. However, IMS will send a transaction notification message (section 1.2.2) for each transaction that changes its state as a result of the command being executed. This assumes the delivering participant has configured its Notification Profile to generate notifications for the new transaction state.




Detailed Field Name

Content/ Options

IMS


M 16R Start of Block GENL 16R:GENL


:4!c//16x 20C:SEME//16x


4!c[/4!c] 23G:INST

mandatory for our

purposes

98a PREP Date/Time Preparation Date/Time

Option C


where yyyymmddhhmmss is the date and time IMS received the command.

-----> Repetitive Mandatory Subsequence A1 Linkages. If SCOPE = LIST, then this subsequence will be repeated for each transaction in the list. If SCOPE <> LIST, then this subsequence will be included only once.

M 16R Start of Block LINK 16R:LINK

O 13A LINK Number Identif-ication

Linked Transaction

:4!c//3!c 13A:LINK//530





Detailed Field Name

Content/ Options

IMS


:4!c//16x If SCOPE = LIST:

20C:COMM//<mutid>

20C:TRRF//<dlvtid>

20C:RELA//<imstid>

20C:PREV//<atptid>


If SCOPE <> LIST:

20C:COMM//<cmnd>

where <cmnd> is the sender’s ID from the command.

M 16S End of Block LINK 16S:LINK




:4!c/[8c]/4!c 25D:IPRC//REJT


M 16R Start of Block REAS 16R:REAS





Detailed Field Name

Content/ Options

IMS


:4!c/[8c]/4!c 24B:REJT/DTCYERCD/<error>

where <error> is one of the following:

• IPAR – invalid participant

• IUSR – invalid user

• ICMD – invalid command

• ISCP – invalid scope

• ICLS – invalid asset class or security group

• ITID – invalid transaction identifier

• IMOD – invalid mode

• ISTA – invalid state. E.g., user tried to cancel transaction in MADE state.

• CNSC – user attempted to kill CNS transaction.

• GLBC – user attempted global kill of transactions.

or

24B:REJT//<error>

where <error> is one of the following:

• DDAT – invalid settlement date





Detailed Field Name

Content/ Options

IMS

• SETR – invalid settlement transaction type

• NRGN – not found. I.e., no transactions matched command.

O 70D REAS Narrative Reason Narrative :4!c//6*35x Reason for error text.

M 16S End of Block REAS 16S:REAS


M 16S End of Block STAT 16S:STAT


M 16S End of Block GENL 16S:GENL

End of Sequence A General Information Optional Sequence B Settlement Transaction Details Suppress entire sequence.


SETTRAN

Suppress

M 35B Identification of the Financial Instrument

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

Suppress

----->





Detailed Field Name

Content/ Options

IMS

M 36B SETT Quantity of Financial Instrument

Quantity of Financial Instrument to be Settled

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

Suppress

-----|

----->

O 19A 4!c Amount (see qualifier descrip-tion)

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

Suppress

-----|

M 97a SAFE Account Safekeep-ing Account

Option A

:4!c//35x • Suppress

----->Repeat following field for each field in Transaction Table that isn’t null.

M 22a 4!c Indicator (see qualifier descrip-tion)

Option F

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

-----| ----->Repeat following field for each date available.

M 98a

4!c Date/ Time

(see qualifier description)

Option A

:4!c//8!n

Option B

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

Suppress

-----|





Detailed Field Name

Content/ Options

IMS

O 70E

SPRO Narrative

Settlement Instruction Processing Narrative

:4!c//10*35x Suppress

-----> Repetitive Optional Subsequence B1 Settlement Parties. Repeat subsequence once for each of the following parties to the trade: Institution, Clearing Agent, Clearing Agent Sub-Custodian, Executing Broker, Clearing Broker, Clearing Broker Sub-Custodian. Suppress entire sequence

M 16R

Start of Block SETPRTY Suppress

M 95a

4!c Party (see qualifier description)

Option P

:4!c//4!a2!a2!c[3!c]

Option R

:4!c/8c/34x

Suppress

O 97a

SAFE Account

Safekeeping Account

Option A

:4!c//35x Suppress

M 16S

End of Block SETPRTY Suppress

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

M 16S End of Block SETTRAN Suppress

End of Sequence B Settlement Transaction Details Optional Sequence C Additional Information Repeat for each of the following parties: Matching Utility and Matching Utility Agent Suppress entire sequence

M 16R Start of Block ADDINFO Suppress

----->





Detailed Field Name

Content/ Options

IMS

O 95a 4!c Party (see qualifier description)

Option R

:4!c/8c/34x

or

Option P

:4!c//4!a2!a2!c[3!c]

or

Option Q

:4!c//4*35x

Suppress

-----|

M 16S End of Block ADDINFO Suppress

End of Sequence C Additional Information




1.2.4 Transaction Warning Message

1.2.4.1 Overview This message is generated when a transaction encounters a warning condition. For example, the transaction is authorized after cutoff time for that transaction type.




Detailed Field Name

Content/ Options

IMS


M 16R

Start of Block

GENL 16R:GENL

M 20C

SEME Reference Sender’s Reference

:4!c//16x 20C:SEME//16x

M 23G

Function of the Message

4!c[/4!c] 23G:INST

Mandat-ory for

our purposes

98a

PREP Date/Time Preparation Date/Time

Option C


where yyyymmddhhmmss is date/time warning condition was encountered.



LINK 16R:LINK





Detailed Field Name

Content/ Options

IMS

O 13A LINK Number Identification

Linked Transaction

:4!c//3!c 13A:LINK//543


13A:LINK//541




20C:TRRF//<dlvtid>

20C:RELA//<imstid>

20C:PREV//<atptid>

where <mutid> is the TID assigned to the transaction by the matching utility, <dlvtid> is the TID assigned to the transaction by the deliverer, <imstid> is the TID IMS assigned to the transaction, and <atptid> is the TID IMS assigned to the transaction.

M 16S End of Block

LINK 16S:LINK




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

25D:IPRC/DTCYSTAT/WARN







Detailed Field Name

Content/ Options

IMS


REAS 16R:REAS


:4!c/[8c]/4!c 24B:PEND/DTCYERCD/<error code>

O 70D REAS

Narrative Reason Narrative

:4!c//6*35x 70D:REAS//<narrative>

where <narrative> optional text explaining warning.

M 16S End of Block

REAS 16S:REAS


M 16S

End of Block

STAT 16S:STAT


M 16S

End of Block

GENL 16S:GENL

End of Sequence A General Information

----->


25.02 ims15022 participant messages/media/files/downloads/settlement... · 25.02 ims15022...

Documents