sese.039.002.04
Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be:
- a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants
- an custodian acting as an accounting and/or settlement agent.
Usage The message may also be used to:
- re-send a message sent by the account owner to the account servicer,
- provide a third party with a copy of a message being sent by the account owner for information,
- re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.
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
%% SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 recursion level 0 with max 0
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "1..1" Identification16 : ModificationRequestReference
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "0..1" PartyIdentification109 : AccountOwner
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "1..1" SecuritiesAccount30 : SafekeepingAccount
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "0..1" TransactionIdentifications37 : TransactionIdentification
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "1..1" IModificationProcessingStatus8Choice : ModificationProcessingStatus
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "0..1" TransactionDetails84 : TransactionDetails
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
ModificationRequestReference building block
Reference to the unambiguous identification of the cancellation request as per the account owner. Unique identifier of a document, message or transaction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Identification16 recursion level 0 with max 1
class Identification16{
Identification IsoRestrictedFINXMax16Text
}
Identification16 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique identifier of a document, message or transaction. | IsoRestrictedFINXMax16Text - Required 1..1 |
AccountOwner building block
Party that legally owns the account. Identification of the party. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% PartyIdentification109 recursion level 0 with max 1
class PartyIdentification109{
LEI IsoLEIIdentifier
}
PartyIdentification109 *-- "1..1" IPartyIdentification114Choice : Identification
%% IPartyIdentification114Choice recursion level 1 with max 1
PartyIdentification109 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique identification of the party. | IPartyIdentification114Choice - Required 1..1 |
| LEI | Legal entity identification as an alternate identification for a party. | IsoLEIIdentifier - Optional 0..1 |
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
%% SecuritiesAccount30 recursion level 0 with max 1
class SecuritiesAccount30{
Identification IsoRestrictedFINXMax35Text
Name IsoMax70Text
}
SecuritiesAccount30 *-- "0..1" GenericIdentification47 : Type
%% GenericIdentification47 recursion level 1 with max 1
class GenericIdentification47{
Identification IsoExact4AlphaNumericText
Issuer IsoMax4AlphaNumericText
SchemeName IsoMax4AlphaNumericText
}
SecuritiesAccount30 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unambiguous identification for the account between the account owner and the account servicer. | IsoRestrictedFINXMax35Text - Required 1..1 |
| Type | Specifies the type of securities account. | GenericIdentification47 - Optional 0..1 |
| Name | Description of the account. | IsoMax70Text - Optional 0..1 |
TransactionIdentification building block
Provides unambiguous transaction identification information. Unique identifier of a document, message or transaction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% TransactionIdentifications37 recursion level 0 with max 1
class TransactionIdentifications37{
AccountOwnerTransactionIdentification IsoRestrictedFINXMax16Text
AccountServicerTransactionIdentification IsoRestrictedFINXMax16Text
MarketInfrastructureTransactionIdentification IsoRestrictedFINXMax16Text
ProcessorTransactionIdentification IsoRestrictedFINXMax16Text
OtherIdentification IsoRestrictedFINXMax16Text
}
TransactionIdentifications37 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). | IsoRestrictedFINXMax16Text - Required 1..1 |
| AccountServicerTransactionIdentification | Unambiguous identification of the transaction as known by the account servicer. | IsoRestrictedFINXMax16Text - Optional 0..1 |
| MarketInfrastructureTransactionIdentification | Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities. | IsoRestrictedFINXMax16Text - 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. | IsoRestrictedFINXMax16Text - Optional 0..1 |
| OtherIdentification | Reference to a transaction that cannot be identified using a standard reference element present in the message. | IsoRestrictedFINXMax16Text - Optional 0..1 |
ModificationProcessingStatus building block
Provides details on the processing status of the request. Choice of format for the processing status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IModificationProcessingStatus8Choice recursion level 0 with max 1
ModificationProcessingStatus8Choice 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
%% TransactionDetails84 recursion level 0 with max 1
class TransactionDetails84{
SecuritiesMovementType ReceiveDelivery1Code
Payment DeliveryReceiptType2Code
}
TransactionDetails84 *-- "1..1" SecurityIdentification20 : FinancialInstrumentIdentification
TransactionDetails84 *-- "1..1" IQuantity10Choice : SettlementQuantity
TransactionDetails84 *-- "0..1" AmountAndDirection67 : SettlementAmount
TransactionDetails84 *-- "1..1" ISettlementDate15Choice : SettlementDate
TransactionDetails84 *-- "0..1" ITradeDate6Choice : TradeDate
TransactionDetails84 *-- "0..1" SettlementParties49 : DeliveringSettlementParties
TransactionDetails84 *-- "0..1" SettlementParties49 : ReceivingSettlementParties
TransactionDetails84 *-- "0..1" PartyIdentification110 : Investor
%% SecurityIdentification20 recursion level 1 with max 1
class SecurityIdentification20{
ISIN IsoISINOct2015Identifier
Description IsoRestrictedFINXMax140Text
}
SecurityIdentification20 *-- "0..0" OtherIdentification2 : OtherIdentification
%% IQuantity10Choice recursion level 1 with max 1
%% AmountAndDirection67 recursion level 1 with max 1
class AmountAndDirection67{
Amount IsoRestrictedFINActiveCurrencyAndAmount
CreditDebitIndicator CreditDebitCode
OriginalCurrencyAndOrderedAmount IsoRestrictedFINActiveOrHistoricCurrencyAndAmount
}
%% ISettlementDate15Choice recursion level 1 with max 1
%% ITradeDate6Choice recursion level 1 with max 1
%% SettlementParties49 recursion level 1 with max 1
SettlementParties49 *-- "0..1" PartyIdentification108 : Depository
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party1
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party2
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party3
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party4
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party5
%% SettlementParties49 recursion level 1 with max 1
SettlementParties49 *-- "0..1" PartyIdentification108 : Depository
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party1
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party2
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party3
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party4
SettlementParties49 *-- "0..1" PartyIdentificationAndAccount146 : Party5
%% PartyIdentification110 recursion level 1 with max 1
class PartyIdentification110{
LEI IsoLEIIdentifier
}
PartyIdentification110 *-- "1..1" IPartyIdentification115Choice : Identification
TransactionDetails84 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| FinancialInstrumentIdentification | Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. | SecurityIdentification20 - 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. | IQuantity10Choice - Required 1..1 |
| SettlementAmount | Total amount of money to be paid or received in exchange for the securities. | AmountAndDirection67 - Optional 0..1 |
| SettlementDate | Date and time at which the securities are to be delivered or received. | ISettlementDate15Choice - Required 1..1 |
| TradeDate | Specifies the date/time on which the trade was executed. | ITradeDate6Choice - Optional 0..1 |
| DeliveringSettlementParties | Identifies the chain of delivering settlement parties. | SettlementParties49 - Optional 0..1 |
| ReceivingSettlementParties | Identifies the chain of receiving settlement parties. | SettlementParties49 - Optional 0..1 |
| Investor | Party, either an individual or organisation, whose assets are being invested. | PartyIdentification110 - 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 SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04Document implements IOuterDocument. Because SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04.
classDiagram
class IOuterRecord
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 --|> IOuterRecord : Implements
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04Document --|> IOuterDocument~SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04~ : Implements
class IOuterDocument~SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04~ {
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 Message
}
Document wrapper for serialization
The only real purpose SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.039.002.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04.ToDocument() method. The returned SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04Document *-- SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 : 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.039.002.04">
<SctiesSttlmTxModReqStsAdvc>
<ModReqRef>
<!-- ModificationRequestReference inner content -->
</ModReqRef>
<AcctOwnr>
<!-- AccountOwner inner content -->
</AcctOwnr>
<SfkpgAcct>
<!-- SafekeepingAccount inner content -->
</SfkpgAcct>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<ModPrcgSts>
<!-- ModificationProcessingStatus inner content -->
</ModPrcgSts>
<TxDtls>
<!-- TransactionDetails inner content -->
</TxDtls>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctiesSttlmTxModReqStsAdvc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_6zXzw5NLEeWGlc8L7oPDIg"
nextVersions="_Tf3IMyAdEeuyDZ-ukt4YRg"
name="SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04"
definition="Scope
An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner.
The account servicer may be:
- a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants
- an custodian acting as an accounting and/or settlement agent.

Usage
The message may also be used to:
- re-send a message sent by the account owner to the account servicer,
- provide a third party with a copy of a message being sent by the account owner for information,
- re-send to a third party a copy of a message being sent by the account owner for information
using the relevant elements in the Business Application Header."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="SctiesSttlmTxModReqStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_6zXzxZNLEeWGlc8L7oPDIg"
name="ModificationRequestReference"
definition="Reference to the unambiguous identification of the cancellation request as per the account owner."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="ModReqRef"
complexType="_5PaGvZNLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_6zXzx5NLEeWGlc8L7oPDIg"
name="AccountOwner"
definition="Party that legally owns the account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctOwnr"
complexType="_S1zDAZjTEeW1SPbGMCLIOQ" />
<messageBuildingBlock
xmi:id="_6zXzyZNLEeWGlc8L7oPDIg"
name="SafekeepingAccount"
definition="Account to or from which a securities entry is made."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SfkpgAcct"
complexType="_5SG1s5NLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_6zXzy5NLEeWGlc8L7oPDIg"
name="TransactionIdentification"
definition="Provides unambiguous transaction identification information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxId"
complexType="_6zX0JZNLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_6zXzzZNLEeWGlc8L7oPDIg"
name="ModificationProcessingStatus"
definition="Provides details on the processing status of the request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="ModPrcgSts"
complexType="_6QCdM5NLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_6zXzz5NLEeWGlc8L7oPDIg"
name="TransactionDetails"
definition="Identifies the details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxDtls"
complexType="_6zZCs5NLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_6zXz0ZNLEeWGlc8L7oPDIg"
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="039"
flavour="002"
version="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.