Iso20022

SecuritiesStatusOrStatementQueryStatusAdviceV03

sese.022.001.03

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be:

Usage The message may also be used to:

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
%% SecuritiesStatusOrStatementQueryStatusAdviceV03 recursion level 0 with max 0
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "1..1" DocumentIdentification24 : QueryDetails
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "0..1" IPartyIdentification36Choice : AccountOwner
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "0..1" IStatusOrStatement5Choice : StatusOrStatementRequested
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "1..1" IProcessingStatus22Choice : ProcessingStatus
SecuritiesStatusOrStatementQueryStatusAdviceV03 *-- "0..1" SupplementaryData1 : SupplementaryData

Now, we will zero-in one-by-one on each of these building blocks.

QueryDetails building block

Unambiguous identification of the query as per the account owner. Identification of the message number and the query identification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification24 recursion level 0 with max 1
DocumentIdentification24 *-- "0..1" IDocumentNumber1Choice : MessageNumber
DocumentIdentification24 *-- "1..1" Identification1 : Reference
%% IDocumentNumber1Choice recursion level 1 with max 1
%% Identification1 recursion level 1 with max 1
class Identification1{
    Identification IsoMax35Text
}

DocumentIdentification24 members

Member name Description Data Type / Multiplicity
MessageNumber Message type number/message identifier of the message referenced in the linkage sequence. IDocumentNumber1Choice - Optional 0..1
Reference Reference to the query identification. Identification1 - Required 1..1

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
%% IPartyIdentification36Choice recursion level 0 with max 1

PartyIdentification36Choice 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

StatusOrStatementRequested building block

Details of the request. Choice between the identification of a status or statement query. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IStatusOrStatement5Choice recursion level 0 with max 1

StatusOrStatement5Choice members

Member name Description Data Type / Multiplicity

ProcessingStatus building block

Provides details on the processing status of the request. Choice of format for the processing status. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IProcessingStatus22Choice recursion level 0 with max 1

ProcessingStatus22Choice members

Member name Description Data Type / Multiplicity

SupplementaryData 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
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1

SupplementaryData1 members

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the SecuritiesStatusOrStatementQueryStatusAdviceV03 implementation follows a specific implementaiton pattern. First of all, SecuritiesStatusOrStatementQueryStatusAdviceV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesStatusOrStatementQueryStatusAdviceV03Document implements IOuterDocument. Because SecuritiesStatusOrStatementQueryStatusAdviceV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesStatusOrStatementQueryStatusAdviceV03.

classDiagram
    class IOuterRecord
    SecuritiesStatusOrStatementQueryStatusAdviceV03 --|> IOuterRecord : Implements
    SecuritiesStatusOrStatementQueryStatusAdviceV03Document --|> IOuterDocument~SecuritiesStatusOrStatementQueryStatusAdviceV03~ : Implements
    class IOuterDocument~SecuritiesStatusOrStatementQueryStatusAdviceV03~ {
        SecuritiesStatusOrStatementQueryStatusAdviceV03 Message
     }

Document wrapper for serialization

The only real purpose SecuritiesStatusOrStatementQueryStatusAdviceV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.022.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesStatusOrStatementQueryStatusAdviceV03.ToDocument() method. The returned SecuritiesStatusOrStatementQueryStatusAdviceV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    SecuritiesStatusOrStatementQueryStatusAdviceV03Document *-- SecuritiesStatusOrStatementQueryStatusAdviceV03 : 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.022.001.03">
    <SctiesStsOrStmtQryStsAdvc>
        <QryDtls>
            <!-- QueryDetails inner content -->
        </QryDtls>
        <AcctOwnr>
            <!-- AccountOwner inner content -->
        </AcctOwnr>
        <SfkpgAcct>
            <!-- SafekeepingAccount inner content -->
        </SfkpgAcct>
        <StsOrStmtReqd>
            <!-- StatusOrStatementRequested inner content -->
        </StsOrStmtReqd>
        <PrcgSts>
            <!-- ProcessingStatus inner content -->
        </PrcgSts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesStsOrStmtQryStsAdvc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_I7iwYfvfEeCBQp5TnX1XKQ"
  nextVersions="_XVkjZQCUEeW_3KiG8SEjHA"
  previousVersion="_qlTxMdtZEd-RF5yaMAVhAw"
  name="SecuritiesStatusOrStatementQueryStatusAdviceV03"
  definition="Scope&#xA;An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner.&#xA;The account servicer/owner relationship may be:&#xA;- a central securities depository or another settlement market infrastructure acting on behalf of their participants&#xA;- an agent (sub-custodian) acting on behalf of their global custodian customer, or&#xA;- a custodian acting on behalf of an investment management institution or a broker/dealer.&#xA;&#xA;Usage&#xA;The message may also be used to:&#xA;- re-send a message previously sent,&#xA;- provide a third party with a copy of a message for information,&#xA;- re-send to a third party a copy of a message for information&#xA;using the relevant elements in the Business Application Header.&#xA;&#xA;ISO 15022 - 20022 Coexistence&#xA;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="SctiesStsOrStmtQryStsAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_I7iwZfvfEeCBQp5TnX1XKQ"
    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="_I7iwafvfEeCBQp5TnX1XKQ"
    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="_I7iwbfvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjawCUEeW_3KiG8SEjHA"
    name="QueryDetails"
    definition="Unambiguous identification of the query as per the account owner."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="QryDtls"
    complexType="_QBS1o_5REeCtrO5qCU90cA" />
  <messageBuildingBlock
    xmi:id="_I7iwcfvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjbQCUEeW_3KiG8SEjHA"
    name="AccountOwner"
    definition="Party that legally owns the account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AcctOwnr"
    complexType="_qU9DBeaPEd-q8fx_Zl_34A" />
  <messageBuildingBlock
    xmi:id="_I7iwdfvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjbwCUEeW_3KiG8SEjHA"
    name="SafekeepingAccount"
    definition="Account to or from which a securities entry is made."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SfkpgAcct"
    complexType="_T_vKAdp-Ed-ak6NoX_4Aeg_-178975462" />
  <messageBuildingBlock
    xmi:id="_I7iwefvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjcQCUEeW_3KiG8SEjHA"
    name="StatusOrStatementRequested"
    definition="Details of the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="StsOrStmtReqd"
    complexType="_BTEbgf7yEeCvPoRGOxRobQ" />
  <messageBuildingBlock
    xmi:id="_I7iwffvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjcwCUEeW_3KiG8SEjHA"
    name="ProcessingStatus"
    definition="Provides details on the processing status of the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="PrcgSts"
    complexType="_2zEPMf7rEeCvPoRGOxRobQ" />
  <messageBuildingBlock
    xmi:id="_I7iwgfvfEeCBQp5TnX1XKQ"
    nextVersions="_XVkjdQCUEeW_3KiG8SEjHA"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="022"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.