reda.058.001.01
Scope The receiver of a StandingSettlementInstruction message sends the StandingSettlementInstructionStatusAdvice message to the instructing party (sender of the StandingSettlementInstruction message) to provide the status of a previously received StandingSettlementInstruction, StandingSettlementInstructionCancellation or StandingSettlementInstructionDeletion message.
Usage The StandingSettlementInstructionStatusAdvice message is used to report one of the following statuses:
- a received status, or,
- an accepted status, or,
- a rejected status, or,
- a pending processing status, or,
- a proprietary status.
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
%% StandingSettlementInstructionStatusAdviceV01 recursion level 0 with max 0
class StandingSettlementInstructionStatusAdviceV01{
RelatedMessageReference IsoMax35Text
}
StandingSettlementInstructionStatusAdviceV01 *-- "0..1" EffectiveDate1 : EffectiveDateDetails
StandingSettlementInstructionStatusAdviceV01 *-- "1..1" AccountIdentification26 : AccountIdentification
StandingSettlementInstructionStatusAdviceV01 *-- "1..1" IMarketIdentificationOrCashPurpose1Choice : MarketIdentification
StandingSettlementInstructionStatusAdviceV01 *-- "1..1" IPartyOrCurrency1Choice : SettlementDetails
StandingSettlementInstructionStatusAdviceV01 *-- "1..1" IProcessingStatus43Choice : ProcessingStatus
StandingSettlementInstructionStatusAdviceV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
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, cancellation or deletion for which the status 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 |
|---|
RelatedMessageReference building block
Reference to a linked message that was previously received. 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.
ProcessingStatus building block
Status of the standing settlement instruction, deletion or cancellation. Choice of formats for the specification of a status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IProcessingStatus43Choice recursion level 0 with max 1
ProcessingStatus43Choice 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 StandingSettlementInstructionStatusAdviceV01 implementation follows a specific implementaiton pattern. First of all, StandingSettlementInstructionStatusAdviceV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StandingSettlementInstructionStatusAdviceV01Document implements IOuterDocument. Because StandingSettlementInstructionStatusAdviceV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StandingSettlementInstructionStatusAdviceV01.
classDiagram
class IOuterRecord
StandingSettlementInstructionStatusAdviceV01 --|> IOuterRecord : Implements
StandingSettlementInstructionStatusAdviceV01Document --|> IOuterDocument~StandingSettlementInstructionStatusAdviceV01~ : Implements
class IOuterDocument~StandingSettlementInstructionStatusAdviceV01~ {
StandingSettlementInstructionStatusAdviceV01 Message
}
Document wrapper for serialization
The only real purpose StandingSettlementInstructionStatusAdviceV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.058.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using StandingSettlementInstructionStatusAdviceV01.ToDocument() method. The returned StandingSettlementInstructionStatusAdviceV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
StandingSettlementInstructionStatusAdviceV01Document *-- StandingSettlementInstructionStatusAdviceV01 : 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.058.001.01">
<StgSttlmInstrStsAdvc>
<FctvDtDtls>
<!-- EffectiveDateDetails inner content -->
</FctvDtDtls>
<AcctId>
<!-- AccountIdentification inner content -->
</AcctId>
<MktId>
<!-- MarketIdentification inner content -->
</MktId>
<SttlmDtls>
<!-- SettlementDetails inner content -->
</SttlmDtls>
<RltdMsgRef>
<!-- RelatedMessageReference inner content -->
</RltdMsgRef>
<PrcgSts>
<!-- ProcessingStatus inner content -->
</PrcgSts>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</StgSttlmInstrStsAdvc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_5gmxoPRnEeK8G5J12Bcx2g"
name="StandingSettlementInstructionStatusAdviceV01"
definition="Scope
The receiver of a StandingSettlementInstruction message sends the StandingSettlementInstructionStatusAdvice message to the instructing party (sender of the StandingSettlementInstruction message) to provide the status of a previously received StandingSettlementInstruction, StandingSettlementInstructionCancellation or StandingSettlementInstructionDeletion message.

Usage
The StandingSettlementInstructionStatusAdvice message is used to report one of the following statuses:
-	a received status, or, 
-	an accepted status, or,
-	a rejected status, or,
-	a pending processing status, or,
-	a proprietary status."
registrationStatus="Registered"
messageSet="_N7G_0dQPEeKSSosHwGnjNw"
xmlTag="StgSttlmInstrStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<doclet
xmi:id="_5lq30PRnEeK8G5J12Bcx2g"
type="purpose" />
<messageBuildingBlock
xmi:id="_QP7bYPXrEeKpFY1yaoww4A"
name="EffectiveDateDetails"
definition="Date on which the SSI is effective."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="FctvDtDtls"
complexType="_oxDxcDceEeOA3chqL9a4Rw" />
<messageBuildingBlock
xmi:id="_QP7bYfXrEeKpFY1yaoww4A"
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="_Va68wVK1EeOsJr32EK1NAQ"
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="_jd-AwVK1EeOsJr32EK1NAQ"
name="SettlementDetails"
definition="Settlement information that helps to identify the standing settlement instruction, cancellation or deletion for which the status is sent."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SttlmDtls"
complexType="_eY4Ls1K0EeOsJr32EK1NAQ" />
<messageBuildingBlock
xmi:id="_z8NGwPm-EeKDvJTxb9tKVw"
name="RelatedMessageReference"
definition="Reference to a linked message that was previously received."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RltdMsgRef"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="__JwQcFhJEeOMYfRGLS0NbA"
name="ProcessingStatus"
definition="Status of the standing settlement instruction, deletion or cancellation."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="PrcgSts"
complexType="_ezCkoVhFEeOMYfRGLS0NbA" />
<messageBuildingBlock
xmi:id="_1jvlQfXtEeKpFY1yaoww4A"
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="058"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.