sese.021.001.01
Scope An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be:
- a global custodian which has an account with a local custodian, or
- an investment management institution which manage a fund account opened at a custodian, or
- a broker which has an account with a custodian, or
- a central securities depository participant which has an account with a central securities depository, or
- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or
- a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure. Usage The message may also be used to:
- re-send a message previously sent (the sub-function of the message is Duplicate),
- provide a third party with a copy of a message for information (the sub-function of the message is Copy),
- re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram direction LR %% SecuritiesTransactionStatusQueryV01 recursion level 0 with max 0 SecuritiesTransactionStatusQueryV01 *-- "1..1" DocumentIdentification11 : Identification SecuritiesTransactionStatusQueryV01 *-- "1..1" DocumentNumber2 : StatusAdviceRequested SecuritiesTransactionStatusQueryV01 *-- "0..1" IPartyIdentification13Choice : AccountOwner SecuritiesTransactionStatusQueryV01 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount SecuritiesTransactionStatusQueryV01 *-- "0..1" IPartyIdentification10Choice : MessageOriginator SecuritiesTransactionStatusQueryV01 *-- "0..1" IPartyIdentification10Choice : MessageRecipient SecuritiesTransactionStatusQueryV01 *-- "0..1" Extension2 : Extension
Now, we will zero-in one-by-one on each of these building blocks.
Identification building block
Information that unambiguously identifies a SecuritiesTransactionStatusQuery message as know by the account owner (or the instructing party acting on its behalf). Identification and creation date of a document. For comparison, see the ISO20022 official specification
classDiagram direction tb %% DocumentIdentification11 recursion level 0 with max 1 class DocumentIdentification11{ Identification IsoMax35Text CopyDuplicate CopyDuplicate1Code } DocumentIdentification11 *-- "0..1" IDateAndDateTimeChoice : CreationDateTime %% IDateAndDateTimeChoice recursion level 1 with max 1
DocumentIdentification11 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Unique identifier of the document (message) assigned by the sender of the document. | IsoMax35Text - Required 1..1 |
CreationDateTime | Date and time at which the document (message) was created by the sender. | IDateAndDateTimeChoice - Optional 0..1 |
CopyDuplicate | Specifies if this document is a copy, a duplicate, or a duplicate of a copy. | CopyDuplicate1Code - Optional 0..1 |
StatusAdviceRequested building block
Description of the status advise requested. Identification of the status being requested. For comparison, see the ISO20022 official specification
classDiagram direction tb %% DocumentNumber2 recursion level 0 with max 1 DocumentNumber2 *-- "1..1" IDocumentNumber1Choice : Number DocumentNumber2 *-- "1..0" Identification2 : References %% IDocumentNumber1Choice recursion level 1 with max 1 %% Identification2 recursion level 1 with max 1 class Identification2{ AccountOwnerTransactionIdentification IsoMax35Text AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text CommonIdentification IsoMax35Text TradeIdentification IsoMax35Text MasterIdentification IsoMax35Text BasketIdentification IsoMax35Text IndexIdentification IsoMax35Text ListIdentification IsoMax35Text ProgramIdentification IsoMax35Text PoolIdentification IsoMax35Text CorporateActionEventIdentification IsoMax35Text }
DocumentNumber2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Number | Number used to identify a message or document. | IDocumentNumber1Choice - Required 1..1 |
References | References of transaction for which the status is requested. | Identification2 - Unknown 1..0 |
AccountOwner building block
Party that legally owns the account. Choice of identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification13Choice recursion level 0 with max 1
PartyIdentification13Choice members
Member name | Description | Data Type / Multiplicity |
---|
SafekeepingAccount building block
Account to or from which a securities entry is made. Account to or from which a securities entry is made. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SecuritiesAccount13 recursion level 0 with max 1 class SecuritiesAccount13{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type %% GenericIdentification20 recursion level 1 with max 1 class GenericIdentification20{ Identification IsoExact4AlphaNumericText Issuer IsoMax35Text SchemeName IsoMax35Text }
SecuritiesAccount13 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Unambiguous identification for the account between the account owner and the account servicer.”. | IsoMax35Text - Required 1..1 |
Type | Specifies the type of securities account. | GenericIdentification20 - Optional 0..1 |
Name | Description of the account. | IsoMax70Text - Optional 0..1 |
MessageOriginator building block
Party that originated the message, if other than the sender. Choice of identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification10Choice recursion level 0 with max 1
PartyIdentification10Choice members
Member name | Description | Data Type / Multiplicity |
---|
MessageRecipient building block
Party that is the final destination of the message, if other than the receiver. Choice of identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification10Choice recursion level 0 with max 1
PartyIdentification10Choice members
Member name | Description | Data Type / Multiplicity |
---|
Extension building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Extension2 recursion level 0 with max 1 class Extension2{ PlaceAndName IsoMax350Text } Extension2 *-- "1..1" ExtensionEnvelope1 : ExtensionEnvelope %% ExtensionEnvelope1 recursion level 1 with max 1 ExtensionEnvelope1 *-- "1..1" ExtensionContents1 : ExtensionContents
Extension2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
PlaceAndName | Name qualifying the information provided in the Text field, and place where this information should be inserted. | IsoMax350Text - Optional 0..1 |
ExtensionEnvelope | Technical element wrapping the extension. | ExtensionEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the SecuritiesTransactionStatusQueryV01 implementation follows a specific implementaiton pattern. First of all, SecuritiesTransactionStatusQueryV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesTransactionStatusQueryV01Document implements IOuterDocument. Because SecuritiesTransactionStatusQueryV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesTransactionStatusQueryV01.
classDiagram class IOuterRecord SecuritiesTransactionStatusQueryV01 --|> IOuterRecord : Implements SecuritiesTransactionStatusQueryV01Document --|> IOuterDocument~SecuritiesTransactionStatusQueryV01~ : Implements class IOuterDocument~SecuritiesTransactionStatusQueryV01~ { SecuritiesTransactionStatusQueryV01 Message }
Document wrapper for serialization
The only real purpose SecuritiesTransactionStatusQueryV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.021.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesTransactionStatusQueryV01.ToDocument() method. The returned SecuritiesTransactionStatusQueryV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesTransactionStatusQueryV01Document *-- SecuritiesTransactionStatusQueryV01 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:sese.021.001.01">
<SctiesTxStsQry>
<Id>
<!-- Identification inner content -->
</Id>
<StsAdvcReqd>
<!-- StatusAdviceRequested inner content -->
</StsAdvcReqd>
<AcctOwnr>
<!-- AccountOwner inner content -->
</AcctOwnr>
<SfkpgAcct>
<!-- SafekeepingAccount inner content -->
</SfkpgAcct>
<MsgOrgtr>
<!-- MessageOriginator inner content -->
</MsgOrgtr>
<MsgRcpt>
<!-- MessageRecipient inner content -->
</MsgRcpt>
<Xtnsn>
<!-- Extension inner content -->
</Xtnsn>
</SctiesTxStsQry>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_GDGn6NE6Ed-BzquC8wXy7w_1892873307"
nextVersions="_hcSXMdtZEd-RF5yaMAVhAw"
name="SecuritiesTransactionStatusQueryV01"
definition="Scope
An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction.
The account owner/servicer relationship may be:
- a global custodian which has an account with a local custodian, or
- an investment management institution which manage a fund account opened at a custodian, or
- a broker which has an account with a custodian, or
- a central securities depository participant which has an account with a central securities depository, or
- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or
- a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure.
Usage
The message may also be used to:
- re-send a message previously sent (the sub-function of the message is Duplicate),
- provide a third party with a copy of a message for information (the sub-function of the message is Copy),
- re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate).
ISO 15022 - 20022 Coexistence
This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="SctiesTxStsQry"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<semanticMarkup
xmi:id="_f4TrdQ5lEeO42pgjaJ50lw"
type="Synonym">
<elements
xmi:id="_f4Trdg5lEeO42pgjaJ50lw"
name="context"
value="ISO 15022" />
<elements
xmi:id="_f4Trdw5lEeO42pgjaJ50lw"
name="value"
value="MT 549, Seq A :23G:NEWM, :13A::REQU//507, 509-10, 548, 558" />
</semanticMarkup>
<constraint
xmi:id="_GDQY4tE6Ed-BzquC8wXy7w_660068112"
name="CoexistenceCharacterSetXRule"
definition="During ISO 15022 – 20022 coexistence, characters used in all text fields must correspond to character set X, that is, a-z A-Z / - ? : ( ) . , ‘ + { } CR LF."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_GDQY5dE6Ed-BzquC8wXy7w_1075223897"
name="CoexistenceIdentificationRule"
definition="During ISO 15022 – 20022 coexistence, all transaction and document identifications or references must be 16 characters or less. The field must not start or end with a slash ‘/’ or contain two consecutive slashes ‘//’."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_GDGn6dE6Ed-BzquC8wXy7w_-1331732681"
name="Identification"
definition="Information that unambiguously identifies a SecuritiesTransactionStatusQuery message as know by the account owner (or the instructing party acting on its behalf)."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Id"
complexType="_RBcz8tp-Ed-ak6NoX_4Aeg_-746423515" />
<messageBuildingBlock
xmi:id="_GDGn6tE6Ed-BzquC8wXy7w_800677212"
name="StatusAdviceRequested"
definition="Description of the status advise requested."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="StsAdvcReqd"
complexType="_Tgvg89p-Ed-ak6NoX_4Aeg_171158783" />
<messageBuildingBlock
xmi:id="_GDGn69E6Ed-BzquC8wXy7w_-583681608"
name="AccountOwner"
definition="Party that legally owns the account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctOwnr"
complexType="_QQIEsNp-Ed-ak6NoX_4Aeg_-1062714307" />
<messageBuildingBlock
xmi:id="_GDGn7NE6Ed-BzquC8wXy7w_1201089256"
name="SafekeepingAccount"
definition="Account to or from which a securities entry is made."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SfkpgAcct"
complexType="_T_vKAdp-Ed-ak6NoX_4Aeg_-178975462" />
<messageBuildingBlock
xmi:id="_GDGn7dE6Ed-BzquC8wXy7w_843684538"
name="MessageOriginator"
definition="Party that originated the message, if other than the sender."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MsgOrgtr"
complexType="_QQR1tdp-Ed-ak6NoX_4Aeg_-1244141483" />
<messageBuildingBlock
xmi:id="_GDQY4NE6Ed-BzquC8wXy7w_882473953"
name="MessageRecipient"
definition="Party that is the final destination of the message, if other than the receiver."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MsgRcpt"
complexType="_QQR1tdp-Ed-ak6NoX_4Aeg_-1244141483" />
<messageBuildingBlock
xmi:id="_GDQY4dE6Ed-BzquC8wXy7w_2132989694"
name="Extension"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="Xtnsn"
complexType="_QzJSNdp-Ed-ak6NoX_4Aeg_251191216" />
<messageDefinitionIdentifier
businessArea="sese"
messageFunctionality="021"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.