sese.039.002.05
Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementTransactionModificationRequest 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 %% SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 recursion level 0 with max 0 SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "1..1" Identification16 : ModificationRequestReference SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "0..1" PartyIdentification156 : AccountOwner SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "1..1" SecuritiesAccount30 : SafekeepingAccount SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "0..1" TransactionIdentifications37 : TransactionIdentification SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "1..1" IModificationProcessingStatus8Choice : ModificationProcessingStatus SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "0..1" TransactionDetails141 : TransactionDetails SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 *-- "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 a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% PartyIdentification156 recursion level 0 with max 1 class PartyIdentification156{ LEI IsoLEIIdentifier } PartyIdentification156 *-- "1..1" IPartyIdentification136Choice : Identification %% IPartyIdentification136Choice recursion level 1 with max 1
PartyIdentification156 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Unique identification of the party. | IPartyIdentification136Choice - 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 %% TransactionDetails141 recursion level 0 with max 1 class TransactionDetails141{ SecuritiesMovementType ReceiveDelivery1Code Payment DeliveryReceiptType2Code } TransactionDetails141 *-- "1..1" SecurityIdentification20 : FinancialInstrumentIdentification TransactionDetails141 *-- "1..1" IQuantity10Choice : SettlementQuantity TransactionDetails141 *-- "0..1" AmountAndDirection67 : SettlementAmount TransactionDetails141 *-- "1..1" ISettlementDate32Choice : SettlementDate TransactionDetails141 *-- "0..1" ITradeDate9Choice : TradeDate TransactionDetails141 *-- "0..1" SettlementParties90 : DeliveringSettlementParties TransactionDetails141 *-- "0..1" SettlementParties90 : ReceivingSettlementParties TransactionDetails141 *-- "0..1" PartyIdentification170 : 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 } %% ISettlementDate32Choice recursion level 1 with max 1 %% ITradeDate9Choice recursion level 1 with max 1 %% SettlementParties90 recursion level 1 with max 1 SettlementParties90 *-- "0..1" PartyIdentification191 : Depository SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party1 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party2 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party3 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party4 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party5 %% SettlementParties90 recursion level 1 with max 1 SettlementParties90 *-- "0..1" PartyIdentification191 : Depository SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party1 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party2 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party3 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party4 SettlementParties90 *-- "0..1" PartyIdentificationAndAccount190 : Party5 %% PartyIdentification170 recursion level 1 with max 1 class PartyIdentification170{ LEI IsoLEIIdentifier } PartyIdentification170 *-- "1..1" IPartyIdentification176Choice : Identification
TransactionDetails141 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. | ISettlementDate32Choice - Required 1..1 |
TradeDate | Specifies the date/time on which the trade was executed. | ITradeDate9Choice - Optional 0..1 |
DeliveringSettlementParties | Identifies the chain of delivering settlement parties. | SettlementParties90 - Optional 0..1 |
ReceivingSettlementParties | Identifies the chain of receiving settlement parties. | SettlementParties90 - Optional 0..1 |
Investor | Party, either an individual or organisation, whose assets are being invested. | PartyIdentification170 - 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 SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05Document implements IOuterDocument. Because SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05.
classDiagram class IOuterRecord SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 --|> IOuterRecord : Implements SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05Document --|> IOuterDocument~SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05~ : Implements class IOuterDocument~SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05~ { SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 Message }
Document wrapper for serialization
The only real purpose SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.039.002.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05.ToDocument() method. The returned SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05Document *-- SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05 : 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.05">
<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="_Tf3IMyAdEeuyDZ-ukt4YRg"
nextVersions="_eXqikzi8Eeydid5dcNPKvg"
previousVersion="_6zXzw5NLEeWGlc8L7oPDIg"
name="SecuritiesSettlementTransactionModificationRequestStatusAdvice002V05"
definition="Scope
An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementTransactionModificationRequest 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="_gMCB9OSnEeauk5I89sEP4g"
xmlTag="SctiesSttlmTxModReqStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_Tf3INSAdEeuyDZ-ukt4YRg"
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="_Tf3INyAdEeuyDZ-ukt4YRg"
name="AccountOwner"
definition="Party that legally owns the account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctOwnr"
complexType="_Z0x6o_fVEeiNZp_PtLohLw" />
<messageBuildingBlock
xmi:id="_Tf3IOSAdEeuyDZ-ukt4YRg"
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="_Tf3IOyAdEeuyDZ-ukt4YRg"
name="TransactionIdentification"
definition="Provides unambiguous transaction identification information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxId"
complexType="_6zX0JZNLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_Tf3IPSAdEeuyDZ-ukt4YRg"
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="_Tf3IPyAdEeuyDZ-ukt4YRg"
name="TransactionDetails"
definition="Identifies the details of the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="TxDtls"
complexType="_Tf4WiyAdEeuyDZ-ukt4YRg" />
<messageBuildingBlock
xmi:id="_Tf3IQSAdEeuyDZ-ukt4YRg"
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="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.