reda.057.001.01
Scope An instructing party sends the StandingSettlementInstructionDeletion message to the receiver to delete a previously sent StandingSettlementInstruction message. The message can also be used to notify a counterparty of the deletion of a standing settlement information.
Usage The instructing party (initiator) is: • An account servicer, for example, a global custodian or prime broker • A counterparty in a transaction, for example: - an investment manager (executing broker), - a global custodian (executing broker, prime broker) • A vendor’s application communicating on behalf of an account servicer or counterparty The receiver is: • An account owner, for example, an investment manager, hedge fund administrator or a party to which SSI operations have been outsourced • A counterparty, for example: - an investment manager (executing broker) - a global custodian (executing broker, prime broker) • A vendor’s application communicating on behalf of the account owner or counterparty.
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
%% StandingSettlementInstructionDeletionV01 recursion level 0 with max 0
class StandingSettlementInstructionDeletionV01{
MessageReferenceIdentification IsoMax35Text
}
StandingSettlementInstructionDeletionV01 *-- "0..1" EffectiveDate1 : EffectiveDateDetails
StandingSettlementInstructionDeletionV01 *-- "1..1" AccountIdentification26 : AccountIdentification
StandingSettlementInstructionDeletionV01 *-- "1..1" IMarketIdentificationOrCashPurpose1Choice : MarketIdentification
StandingSettlementInstructionDeletionV01 *-- "1..1" IPartyOrCurrency1Choice : SettlementDetails
StandingSettlementInstructionDeletionV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MessageReferenceIdentification building block
Reference of this message. 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.
EffectiveDateDetails building block
Date on which the SSI is effective. Date and date parameters. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% EffectiveDate1 recursion level 0 with max 1
class EffectiveDate1{
EffectiveDate IsoISODate
EffectiveDateParameter ExternalEffectiveDateParameter1Code
}
EffectiveDate1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| EffectiveDate | Date on which the SSI is effective. If the SSI is effective on a future date, then the date must be provided. | IsoISODate - Required 1..1 |
| EffectiveDateParameter | Specifies how the SSI update effective date is to be applied. | ExternalEffectiveDateParameter1Code - Optional 0..1 |
AccountIdentification building block
Unique and unambiguous master identification known to the sender (or its authorised agent) and receiver (or its authorised agent), below which the SSI will be lodged. This may be an account number or reference to a fund. If no account or reference is available then “NONREF” must be specified. Unique identifier of an account, as assigned by the account servicer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AccountIdentification26 recursion level 0 with max 1
AccountIdentification26 *-- "1..1" SimpleIdentificationInformation4 : Proprietary
%% SimpleIdentificationInformation4 recursion level 1 with max 1
class SimpleIdentificationInformation4{
Identification IsoMax35Text
}
AccountIdentification26 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Proprietary | Unique identifier for an account. It is assigned by the account servicer using a proprietary identification scheme. | SimpleIdentificationInformation4 - Required 1..1 |
MarketIdentification building block
Identifies the market for the standing settlement instruction. Choice of cash purpose or a securities market identifier. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IMarketIdentificationOrCashPurpose1Choice recursion level 0 with max 1
MarketIdentificationOrCashPurpose1Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
SettlementDetails building block
Settlement information that helps to identify the standing settlement instruction for which the deletion is sent. Choice of a depostory or settlement currency. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyOrCurrency1Choice recursion level 0 with max 1
PartyOrCurrency1Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
SupplementaryData building block
Additional information that can not be captured in the structured fields 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 StandingSettlementInstructionDeletionV01 implementation follows a specific implementaiton pattern. First of all, StandingSettlementInstructionDeletionV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StandingSettlementInstructionDeletionV01Document implements IOuterDocument. Because StandingSettlementInstructionDeletionV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StandingSettlementInstructionDeletionV01.
classDiagram
class IOuterRecord
StandingSettlementInstructionDeletionV01 --|> IOuterRecord : Implements
StandingSettlementInstructionDeletionV01Document --|> IOuterDocument~StandingSettlementInstructionDeletionV01~ : Implements
class IOuterDocument~StandingSettlementInstructionDeletionV01~ {
StandingSettlementInstructionDeletionV01 Message
}
Document wrapper for serialization
The only real purpose StandingSettlementInstructionDeletionV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.057.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using StandingSettlementInstructionDeletionV01.ToDocument() method. The returned StandingSettlementInstructionDeletionV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
StandingSettlementInstructionDeletionV01Document *-- StandingSettlementInstructionDeletionV01 : 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:reda.057.001.01">
<StgSttlmInstrDeltn>
<MsgRefId>
<!-- MessageReferenceIdentification inner content -->
</MsgRefId>
<FctvDtDtls>
<!-- EffectiveDateDetails inner content -->
</FctvDtDtls>
<AcctId>
<!-- AccountIdentification inner content -->
</AcctId>
<MktId>
<!-- MarketIdentification inner content -->
</MktId>
<SttlmDtls>
<!-- SettlementDetails inner content -->
</SttlmDtls>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</StgSttlmInstrDeltn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_n9oL6tQiEeKvJeoOII0e7w"
name="StandingSettlementInstructionDeletionV01"
definition="Scope
An instructing party sends the StandingSettlementInstructionDeletion message to the receiver to delete a previously sent StandingSettlementInstruction message. The message can also be used to notify a counterparty of the deletion of a standing settlement information.

Usage
The instructing party (initiator) is:
• An account servicer, for example, a global custodian or prime broker
• A counterparty in a transaction, for example:
	- an investment manager (executing broker),
	- a global custodian (executing broker, prime broker)
• A vendor's application communicating on behalf of an account servicer or counterparty
The receiver is:
• An account owner, for example, an investment manager, hedge fund administrator or a party to which SSI operations have been outsourced
• A counterparty, for example:
	- an investment manager (executing broker)
	- a global custodian (executing broker, prime broker)
• A vendor's application communicating on behalf of the account owner or counterparty."
registrationStatus="Registered"
messageSet="_N7G_0dQPEeKSSosHwGnjNw"
xmlTag="StgSttlmInstrDeltn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_n9oL69QiEeKvJeoOII0e7w"
type="purpose" />
<messageBuildingBlock
xmi:id="_MwZHMewmEeWkJ9nstgT-Yw"
name="MessageReferenceIdentification"
definition="Reference of this message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgRefId"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_n9oL89QiEeKvJeoOII0e7w"
name="EffectiveDateDetails"
definition="Date on which the SSI is effective."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="FctvDtDtls"
complexType="_oxDxcDceEeOA3chqL9a4Rw" />
<messageBuildingBlock
xmi:id="_n9oL7dQiEeKvJeoOII0e7w"
name="AccountIdentification"
definition="Unique and unambiguous master identification known to the sender (or its authorised agent) and receiver (or its authorised agent), below which the SSI will be lodged. This may be an account number or reference to a fund.
If no account or reference is available then “NONREF” must be specified."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="AcctId"
complexType="_ku_soSxxEeKgiYs1KJCQUg" />
<messageBuildingBlock
xmi:id="_hviQYVKyEeOsJr32EK1NAQ"
name="MarketIdentification"
definition="Identifies the market for the standing settlement instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MktId"
complexType="_Lc9dQEiNEeOdL6nMHefDgg" />
<messageBuildingBlock
xmi:id="_EMun4VK0EeOsJr32EK1NAQ"
name="SettlementDetails"
definition="Settlement information that helps to identify the standing settlement instruction for which the deletion is sent."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SttlmDtls"
complexType="_eY4Ls1K0EeOsJr32EK1NAQ" />
<messageBuildingBlock
xmi:id="_1CltkdT_EeKnWItMEK8CZg"
name="SupplementaryData"
definition="Additional information that can not be captured in the structured fields and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="reda"
messageFunctionality="057"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.