sese.020.001.01
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 (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 %% SecuritiesTransactionCancellationRequestV01 recursion level 0 with max 0 SecuritiesTransactionCancellationRequestV01 *-- "1..1" DocumentIdentification11 : Identification SecuritiesTransactionCancellationRequestV01 *-- "1..1" TransactionDetails11 : Details SecuritiesTransactionCancellationRequestV01 *-- "0..1" IPartyIdentification10Choice : MessageOriginator SecuritiesTransactionCancellationRequestV01 *-- "0..1" IPartyIdentification10Choice : MessageRecipient SecuritiesTransactionCancellationRequestV01 *-- "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 SecuritiesTransactionCancellationRequest 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 |
Details building block
Details of the transaction. Identifies the details of the transaction. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransactionDetails11 recursion level 0 with max 1 class TransactionDetails11{ AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text } TransactionDetails11 *-- "1..1" IReferences2Choice : AccountOwnerTransactionIdentification TransactionDetails11 *-- "0..1" IPartyIdentification13Choice : AccountOwner TransactionDetails11 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount TransactionDetails11 *-- "0..1" TransactionDetails10 : TransactionDetails TransactionDetails11 *-- "0..1" IFXCancellation1Choice : FXCancellation %% IReferences2Choice recursion level 1 with max 1 %% IPartyIdentification13Choice recursion level 1 with max 1 %% SecuritiesAccount13 recursion level 1 with max 1 class SecuritiesAccount13{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type %% TransactionDetails10 recursion level 1 with max 1 TransactionDetails10 *-- "1..1" SecurityIdentification11 : FinancialInstrumentIdentification TransactionDetails10 *-- "0..1" ITradeDate1Choice : TradeDate TransactionDetails10 *-- "1..1" ISettlementDate1Choice : SettlementDate TransactionDetails10 *-- "1..1" IQuantity6Choice : SettlementQuantity TransactionDetails10 *-- "0..1" AmountAndDirection8 : SettlementAmount TransactionDetails10 *-- "0..1" SettlementParties2 : DeliveringSettlementParties TransactionDetails10 *-- "0..1" SettlementParties2 : ReceivingSettlementParties TransactionDetails10 *-- "0..1" IPartyIdentification14Choice : Investor %% IFXCancellation1Choice recursion level 1 with max 1
TransactionDetails11 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). | IReferences2Choice - Required 1..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 |
AccountOwner | Party that legally owns the account. | IPartyIdentification13Choice - Optional 0..1 |
SafekeepingAccount | Account to or from which a securities entry is made. | SecuritiesAccount13 - Required 1..1 |
TransactionDetails | Identifies the details of the transaction. | TransactionDetails10 - Optional 0..1 |
FXCancellation | Specifies whether an associated FX should be cancelled. | IFXCancellation1Choice - 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 SecuritiesTransactionCancellationRequestV01 implementation follows a specific implementaiton pattern. First of all, SecuritiesTransactionCancellationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesTransactionCancellationRequestV01Document implements IOuterDocument. Because SecuritiesTransactionCancellationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesTransactionCancellationRequestV01.
classDiagram class IOuterRecord SecuritiesTransactionCancellationRequestV01 --|> IOuterRecord : Implements SecuritiesTransactionCancellationRequestV01Document --|> IOuterDocument~SecuritiesTransactionCancellationRequestV01~ : Implements class IOuterDocument~SecuritiesTransactionCancellationRequestV01~ { SecuritiesTransactionCancellationRequestV01 Message }
Document wrapper for serialization
The only real purpose SecuritiesTransactionCancellationRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.020.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesTransactionCancellationRequestV01.ToDocument() method. The returned SecuritiesTransactionCancellationRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesTransactionCancellationRequestV01Document *-- SecuritiesTransactionCancellationRequestV01 : 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.01">
<SctiesTxCxlReq>
<Id>
<!-- Identification inner content -->
</Id>
<Dtls>
<!-- Details inner content -->
</Dtls>
<MsgOrgtr>
<!-- MessageOriginator inner content -->
</MsgOrgtr>
<MsgRcpt>
<!-- MessageRecipient inner content -->
</MsgRcpt>
<Xtnsn>
<!-- Extension inner content -->
</Xtnsn>
</SctiesTxCxlReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_EdCB-NE6Ed-BzquC8wXy7w_-363861038"
nextVersions="_aj0DgdtZEd-RF5yaMAVhAw"
name="SecuritiesTransactionCancellationRequestV01"
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 (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="SctiesTxCxlReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<semanticMarkup
xmi:id="_f4J6bw5lEeO42pgjaJ50lw"
type="Synonym">
<elements
xmi:id="_f4J6cA5lEeO42pgjaJ50lw"
name="context"
value="ISO 15022" />
<elements
xmi:id="_f4J6cQ5lEeO42pgjaJ50lw"
name="value"
value="MT 524, 540-3, 549, Seq A :23G:CANC" />
</semanticMarkup>
<constraint
xmi:id="_EdLy8tE6Ed-BzquC8wXy7w_-1163209713"
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="_EdLy9dE6Ed-BzquC8wXy7w_1361446353"
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="_EdCB-dE6Ed-BzquC8wXy7w_1971127414"
name="Identification"
definition="Information that unambiguously identifies a SecuritiesTransactionCancellationRequest 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="_EdCB-tE6Ed-BzquC8wXy7w_-1926064672"
name="Details"
definition="Details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Dtls"
complexType="_UcNDk9p-Ed-ak6NoX_4Aeg_1219473022" />
<messageBuildingBlock
xmi:id="_EdCB-9E6Ed-BzquC8wXy7w_-505950582"
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="_EdLy8NE6Ed-BzquC8wXy7w_-473628723"
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="_EdLy8dE6Ed-BzquC8wXy7w_2033219671"
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="020"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.