sese.020.001.02
Scope An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of 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 ot another settlement market infrastructure. Usage The transaction may be:
- a securities settlement transaction
- an intra-position movement
- a securities financing transaction The instruction cannot be:
- a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested).
- a securities financing modification. The message may also be used to:
- re-send a message previously sent,
- provide a third party with a copy of a message for information,
- re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. 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 %% SecuritiesTransactionCancellationRequestV02 recursion level 0 with max 0 class SecuritiesTransactionCancellationRequestV02{ AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text ProcessorTransactionIdentification IsoMax35Text } SecuritiesTransactionCancellationRequestV02 *-- "1..1" IReferences2Choice : AccountOwnerTransactionIdentification SecuritiesTransactionCancellationRequestV02 *-- "0..1" IPartyIdentification36Choice : AccountOwner SecuritiesTransactionCancellationRequestV02 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount SecuritiesTransactionCancellationRequestV02 *-- "0..1" TransactionDetails29 : TransactionDetails SecuritiesTransactionCancellationRequestV02 *-- "0..1" IFXCancellation1Choice : FXCancellation SecuritiesTransactionCancellationRequestV02 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
AccountOwnerTransactionIdentification building block
Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account). Choice of reference. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IReferences2Choice recursion level 0 with max 1
References2Choice members
Member name | Description | Data Type / Multiplicity |
---|
AccountServicerTransactionIdentification building block
Unambiguous identification of the transaction as known by the account servicer. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
MarketInfrastructureTransactionIdentification building block
Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
ProcessorTransactionIdentification building block
Message Reference identifying the Processor of the transaction. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
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 |
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 %% TransactionDetails29 recursion level 0 with max 1 TransactionDetails29 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification TransactionDetails29 *-- "0..1" ITradeDate1Choice : TradeDate TransactionDetails29 *-- "1..1" ISettlementDate1Choice : SettlementDate TransactionDetails29 *-- "1..1" IQuantity6Choice : SettlementQuantity TransactionDetails29 *-- "0..1" AmountAndDirection8 : SettlementAmount TransactionDetails29 *-- "0..1" SettlementParties13 : DeliveringSettlementParties TransactionDetails29 *-- "0..1" SettlementParties13 : ReceivingSettlementParties TransactionDetails29 *-- "0..1" IPartyIdentification37Choice : Investor %% SecurityIdentification14 recursion level 1 with max 1 class SecurityIdentification14{ ISIN IsoISINIdentifier Description IsoMax140Text } SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification %% ITradeDate1Choice recursion level 1 with max 1 %% ISettlementDate1Choice recursion level 1 with max 1 %% IQuantity6Choice recursion level 1 with max 1 %% AmountAndDirection8 recursion level 1 with max 1 class AmountAndDirection8{ Amount IsoActiveCurrencyAndAmount CreditDebitIndicator CreditDebitCode OriginalCurrencyAndOrderedAmount IsoActiveOrHistoricCurrencyAndAmount } %% 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
TransactionDetails29 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
FinancialInstrumentIdentification | Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. | SecurityIdentification14 - Required 1..1 |
TradeDate | Specifies the date/time on which the trade was executed. | ITradeDate1Choice - Optional 0..1 |
SettlementDate | Date and time at which the securities are to be delivered or received. | ISettlementDate1Choice - Required 1..1 |
SettlementQuantity | Total quantity of securities to be settled. | IQuantity6Choice - Required 1..1 |
SettlementAmount | Total amount of money to be paid or received in exchange for the securities. | AmountAndDirection8 - 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 |
FXCancellation building block
Specifies whether an associated FX should be cancelled. Choice of format for the FX cancellation information. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IFXCancellation1Choice recursion level 0 with max 1
FXCancellation1Choice 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 SecuritiesTransactionCancellationRequestV02 implementation follows a specific implementaiton pattern. First of all, SecuritiesTransactionCancellationRequestV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesTransactionCancellationRequestV02Document implements IOuterDocument. Because SecuritiesTransactionCancellationRequestV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesTransactionCancellationRequestV02.
classDiagram class IOuterRecord SecuritiesTransactionCancellationRequestV02 --|> IOuterRecord : Implements SecuritiesTransactionCancellationRequestV02Document --|> IOuterDocument~SecuritiesTransactionCancellationRequestV02~ : Implements class IOuterDocument~SecuritiesTransactionCancellationRequestV02~ { SecuritiesTransactionCancellationRequestV02 Message }
Document wrapper for serialization
The only real purpose SecuritiesTransactionCancellationRequestV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.020.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesTransactionCancellationRequestV02.ToDocument() method. The returned SecuritiesTransactionCancellationRequestV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesTransactionCancellationRequestV02Document *-- SecuritiesTransactionCancellationRequestV02 : 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.020.001.02">
<SctiesTxCxlReq>
<AcctOwnrTxId>
<!-- AccountOwnerTransactionIdentification inner content -->
</AcctOwnrTxId>
<AcctSvcrTxId>
<!-- AccountServicerTransactionIdentification inner content -->
</AcctSvcrTxId>
<MktInfrstrctrTxId>
<!-- MarketInfrastructureTransactionIdentification inner content -->
</MktInfrstrctrTxId>
<PrcrTxId>
<!-- ProcessorTransactionIdentification inner content -->
</PrcrTxId>
<AcctOwnr>
<!-- AccountOwner inner content -->
</AcctOwnr>
<SfkpgAcct>
<!-- SafekeepingAccount inner content -->
</SfkpgAcct>
<TxDtls>
<!-- TransactionDetails inner content -->
</TxDtls>
<FxCxl>
<!-- FXCancellation inner content -->
</FxCxl>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctiesTxCxlReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_aj0DgdtZEd-RF5yaMAVhAw"
nextVersions="_oUrBUfvdEeCBQp5TnX1XKQ"
previousVersion="_EdCB-NE6Ed-BzquC8wXy7w_-363861038"
name="SecuritiesTransactionCancellationRequestV02"
definition="Scope
An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of 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 ot another settlement market infrastructure.
Usage
The transaction may be:
- a securities settlement transaction
- an intra-position movement
- a securities financing transaction
The instruction cannot be:
- a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested).
- a securities financing modification.
The message may also be used to:
- re-send a message previously sent,
- provide a third party with a copy of a message for information,
- re-send to a third party a copy of a message for information.
using the relevant elements in the Business Application Header.
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="SctiesTxCxlReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_aj0DjdtZEd-RF5yaMAVhAw"
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="_aj0Dj9tZEd-RF5yaMAVhAw"
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="_8aii0fikEd-3eNJ4QJmSyg"
name="AccountOwnerTransactionIdentification"
definition="Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account)."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AcctOwnrTxId"
complexType="_US9oCdp-Ed-ak6NoX_4Aeg_1980096839" />
<messageBuildingBlock
xmi:id="_9M5z4fikEd-3eNJ4QJmSyg"
name="AccountServicerTransactionIdentification"
definition="Unambiguous identification of the transaction as known by the account servicer."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctSvcrTxId"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_-D5GQfikEd-3eNJ4QJmSyg"
name="MarketInfrastructureTransactionIdentification"
definition="Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MktInfrstrctrTxId"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_BdccAfilEd-3eNJ4QJmSyg"
name="ProcessorTransactionIdentification"
definition="Message Reference identifying the Processor of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrcrTxId"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_-ugwkfikEd-3eNJ4QJmSyg"
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="__efcAfikEd-3eNJ4QJmSyg"
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="_AKveAfilEd-3eNJ4QJmSyg"
name="TransactionDetails"
definition="Identifies the details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxDtls"
complexType="_idcJq-aOEd-q8fx_Zl_34A" />
<messageBuildingBlock
xmi:id="_A4pF0filEd-3eNJ4QJmSyg"
name="FXCancellation"
definition="Specifies whether an associated FX should be cancelled."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="FxCxl"
complexType="_QtVlIdp-Ed-ak6NoX_4Aeg_615585032" />
<messageBuildingBlock
xmi:id="_aj0Di9tZEd-RF5yaMAVhAw"
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="020"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.