Iso20022

SecuritiesSettlementTransactionCounterpartyResponseV01

sese.040.001.01

Scope An account owner sends a SecuritiesSettlementTransactionCounterpartyResponse to advise the account servicer that:

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
%% SecuritiesSettlementTransactionCounterpartyResponseV01 recursion level 0 with max 0
SecuritiesSettlementTransactionCounterpartyResponseV01 *-- "1..1" TransactionIdentification2 : TransactionIdentification
SecuritiesSettlementTransactionCounterpartyResponseV01 *-- "1..1" IResponseStatus3Choice : ResponseStatus
SecuritiesSettlementTransactionCounterpartyResponseV01 *-- "0..1" TransactionDetails40 : TransactionDetails
SecuritiesSettlementTransactionCounterpartyResponseV01 *-- "0..1" SupplementaryData1 : SupplementaryData

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

TransactionIdentification building block

Provides unambiguous transaction identification information. Provides transaction type and identification information. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionIdentification2 recursion level 0 with max 1
class TransactionIdentification2{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
}

TransactionIdentification2 members

Member name Description Data Type / Multiplicity
AccountOwnerTransactionIdentification Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account). IsoMax35Text - Optional 0..1
AccountServicerTransactionIdentification Unambiguous identification of the transaction as known by the account servicer. IsoMax35Text - Optional 0..1
MarketInfrastructureTransactionIdentification Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities. IsoMax35Text - Optional 0..1
ProcessorTransactionIdentification Identification of the transaction assigned by the processor of the instruction other than the account owner the account servicer and the market infrastructure. IsoMax35Text - Optional 0..1

ResponseStatus building block

Provides the response status related to an allegement or a counterparty’s instruction. Choice of response status. For comparison, see the ISO20022 official specification

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

ResponseStatus3Choice members

Member name Description Data Type / Multiplicity

TransactionDetails building block

Identifies the details of the transaction. Identifies the details of the transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionDetails40 recursion level 0 with max 1
class TransactionDetails40{
    SecuritiesMovementType ReceiveDelivery1Code
    Payment DeliveryReceiptType2Code
}
TransactionDetails40 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
TransactionDetails40 *-- "1..1" IQuantity6Choice : SettlementQuantity
TransactionDetails40 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
TransactionDetails40 *-- "0..1" AmountAndDirection8 : SettlementAmount
TransactionDetails40 *-- "1..1" ISettlementDate2Choice : SettlementDate
TransactionDetails40 *-- "0..1" ITradeDate1Choice : TradeDate
TransactionDetails40 *-- "0..1" SettlementParties13 : DeliveringSettlementParties
TransactionDetails40 *-- "0..1" SettlementParties13 : ReceivingSettlementParties
TransactionDetails40 *-- "0..1" IPartyIdentification37Choice : Investor
%% SecurityIdentification14 recursion level 1 with max 1
class SecurityIdentification14{
    ISIN IsoISINIdentifier
    Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% IQuantity6Choice recursion level 1 with max 1
%% SecuritiesAccount13 recursion level 1 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% AmountAndDirection8 recursion level 1 with max 1
class AmountAndDirection8{
    Amount IsoActiveCurrencyAndAmount
    CreditDebitIndicator CreditDebitCode
    OriginalCurrencyAndOrderedAmount IsoActiveOrHistoricCurrencyAndAmount
}
%% ISettlementDate2Choice recursion level 1 with max 1
%% ITradeDate1Choice recursion level 1 with max 1
%% SettlementParties13 recursion level 1 with max 1
SettlementParties13 *-- "0..1" PartyIdentification46 : Depository
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party1
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party2
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party3
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party4
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party5
%% SettlementParties13 recursion level 1 with max 1
SettlementParties13 *-- "0..1" PartyIdentification46 : Depository
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party1
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party2
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party3
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party4
SettlementParties13 *-- "0..1" PartyIdentificationAndAccount44 : Party5
%% IPartyIdentification37Choice recursion level 1 with max 1

TransactionDetails40 members

Member name Description Data Type / Multiplicity
FinancialInstrumentIdentification Way(s) of identifying the security. SecurityIdentification14 - Required 1..1
SecuritiesMovementType Specifies if the movement on a securities account results from a deliver or a receive instruction. ReceiveDelivery1Code - Required 1..1
Payment Specifies how the transaction is to be settled, eg, against payment. DeliveryReceiptType2Code - Required 1..1
SettlementQuantity Total quantity of securities to be settled. IQuantity6Choice - Required 1..1
SafekeepingAccount Account to or from which a securities entry is made. SecuritiesAccount13 - Required 1..1
SettlementAmount Total amount of money to be paid or received in exchange for the securities. AmountAndDirection8 - Optional 0..1
SettlementDate Date and time at which the securities are to be delivered or received. ISettlementDate2Choice - Required 1..1
TradeDate Specifies the date/time on which the trade was executed. ITradeDate1Choice - Optional 0..1
DeliveringSettlementParties Identifies the chain of delivering settlement parties. SettlementParties13 - Optional 0..1
ReceivingSettlementParties Identifies the chain of receiving settlement parties. SettlementParties13 - Optional 0..1
Investor Party, either an individual or organisation, whose assets are being invested. IPartyIdentification37Choice - Optional 0..1

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 SecuritiesSettlementTransactionCounterpartyResponseV01 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionCounterpartyResponseV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionCounterpartyResponseV01Document implements IOuterDocument. Because SecuritiesSettlementTransactionCounterpartyResponseV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionCounterpartyResponseV01.

classDiagram
    class IOuterRecord
    SecuritiesSettlementTransactionCounterpartyResponseV01 --|> IOuterRecord : Implements
    SecuritiesSettlementTransactionCounterpartyResponseV01Document --|> IOuterDocument~SecuritiesSettlementTransactionCounterpartyResponseV01~ : Implements
    class IOuterDocument~SecuritiesSettlementTransactionCounterpartyResponseV01~ {
        SecuritiesSettlementTransactionCounterpartyResponseV01 Message
     }

Document wrapper for serialization

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

classDiagram
    SecuritiesSettlementTransactionCounterpartyResponseV01Document *-- SecuritiesSettlementTransactionCounterpartyResponseV01 : 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.040.001.01">
    <SctiesSttlmTxCtrPtyRspn>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <RspnSts>
            <!-- ResponseStatus inner content -->
        </RspnSts>
        <TxDtls>
            <!-- TransactionDetails inner content -->
        </TxDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesSttlmTxCtrPtyRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_0Z18hQlIEeGATtfOBToyew_-281695721"
  nextVersions="_XVkiVQCUEeW_3KiG8SEjHA"
  name="SecuritiesSettlementTransactionCounterpartyResponseV01"
  definition="Scope&#xA;An account owner sends a SecuritiesSettlementTransactionCounterpartyResponse to advise the account servicer that:&#xA;- the allegement received is either rejected (that is counterparty's transaction is unknown) or accepted (i.e. either the allegement was passed to the client or the transaction is know with or without mismatches)&#xA;- the modification or cancellation request sent by the counterparty for a matched transaction is affirmed or not. The account servicer will therefore proceed or not with the counterparty's request to modify or cancel the transaction.&#xA;The account servicer may be a central securities depository or another settlement market infrastructure acting on behalf of their participants&#xA;The account owner may be:&#xA;- a central securities depository participant which has an account with a central securities depository or a market infrastructure&#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 sent by the account owner to the account servicer,&#xA;- provide a third party with a copy of a message being sent by the account owner for information,&#xA;- re-send to a third party a copy of a message being sent by the account owner 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="SctiesSttlmTxCtrPtyRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_0Z18hglIEeGATtfOBToyew_709903212"
    nextVersions="_XVkiVwCUEeW_3KiG8SEjHA"
    name="TransactionIdentification"
    definition="Provides unambiguous transaction identification information."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_0fM9owlIEeGATtfOBToyew_486702993" />
  <messageBuildingBlock
    xmi:id="_0Z_GcAlIEeGATtfOBToyew_-2072906974"
    nextVersions="_XVkiWQCUEeW_3KiG8SEjHA"
    name="ResponseStatus"
    definition="Provides the response status related to an allegement or a counterparty's instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RspnSts"
    complexType="_0j-I4AlIEeGATtfOBToyew_1037532092" />
  <messageBuildingBlock
    xmi:id="_0Z_GcQlIEeGATtfOBToyew_667709329"
    nextVersions="_XVkiWwCUEeW_3KiG8SEjHA"
    name="TransactionDetails"
    definition="Identifies the details of the transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="TxDtls"
    complexType="_0cOiJAlIEeGATtfOBToyew_-2009352328" />
  <messageBuildingBlock
    xmi:id="_0Z_GcglIEeGATtfOBToyew_-2075725968"
    nextVersions="_XVkiXQCUEeW_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="040"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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