sese.030.001.07
Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.
The account owner/servicer relationship may be:
- a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement:
- a global custodian which has an account with its local agent (sub-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 which has an account with a custodian, another central securities depository or another settlement market infrastructure.
Usage The message may also be used to:
- re-send a message previously sent,
- provide a third party with a copy of a message for information,
- re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.
In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.
This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.
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 %% SecuritiesSettlementConditionsModificationRequestV07 recursion level 0 with max 0 SecuritiesSettlementConditionsModificationRequestV07 *-- "0..1" PartyIdentification98 : AccountOwner SecuritiesSettlementConditionsModificationRequestV07 *-- "1..1" SecuritiesAccount19 : SafekeepingAccount SecuritiesSettlementConditionsModificationRequestV07 *-- "1..1" RequestDetails15 : RequestDetails SecuritiesSettlementConditionsModificationRequestV07 *-- "0..1" AdditionalInformation13 : AdditionalInformation SecuritiesSettlementConditionsModificationRequestV07 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
AccountOwner building block
Party that legally owns the account. Identification of the party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% PartyIdentification98 recursion level 0 with max 1 class PartyIdentification98{ LEI IsoLEIIdentifier } PartyIdentification98 *-- "1..1" IPartyIdentification92Choice : Identification %% IPartyIdentification92Choice recursion level 1 with max 1
PartyIdentification98 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Unique identification of the party. | IPartyIdentification92Choice - 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 %% SecuritiesAccount19 recursion level 0 with max 1 class SecuritiesAccount19{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount19 *-- "0..1" GenericIdentification30 : Type %% GenericIdentification30 recursion level 1 with max 1 class GenericIdentification30{ Identification IsoExact4AlphaNumericText Issuer IsoMax35Text SchemeName IsoMax35Text }
SecuritiesAccount19 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Unambiguous identification for the account between the account owner and the account servicer. | IsoMax35Text - Required 1..1 |
Type | Specifies the type of securities account. | GenericIdentification30 - Optional 0..1 |
Name | Description of the account. | IsoMax70Text - Optional 0..1 |
RequestDetails building block
Details of the request. Details of the settlement condition modification request. For comparison, see the ISO20022 official specification
classDiagram direction tb %% RequestDetails15 recursion level 0 with max 1 class RequestDetails15{ RetainIndicator IsoYesNoIndicator PartialSettlementIndicator SettlementTransactionCondition5Code } RequestDetails15 *-- "1..1" References18 : Reference RequestDetails15 *-- "0..1" IAutomaticBorrowing7Choice : AutomaticBorrowing RequestDetails15 *-- "0..1" ILinkageType3Choice : Linkage RequestDetails15 *-- "0..1" IPriorityNumeric4Choice : Priority RequestDetails15 *-- "0..0" GenericIdentification30 : OtherProcessing RequestDetails15 *-- "0..1" ISecuritiesRTGS4Choice : SecuritiesRTGS RequestDetails15 *-- "0..1" HoldIndicator6 : HoldIndicator RequestDetails15 *-- "0..1" IMatchingDenied3Choice : MatchingDenial RequestDetails15 *-- "0..1" IUnilateralSplit3Choice : UnilateralSplit RequestDetails15 *-- "0..0" Linkages39 : Linkages %% References18 recursion level 1 with max 1 class References18{ AccountOwnerTransactionIdentification IsoMax35Text AccountServicerTransactionIdentification IsoMax35Text MarketInfrastructureTransactionIdentification IsoMax35Text ProcessorTransactionIdentification IsoMax35Text PoolIdentification IsoMax35Text CommonIdentification IsoMax35Text TradeIdentification IsoMax35Text } %% IAutomaticBorrowing7Choice recursion level 1 with max 1 %% ILinkageType3Choice recursion level 1 with max 1 %% IPriorityNumeric4Choice recursion level 1 with max 1 %% GenericIdentification30 recursion level 1 with max 1 class GenericIdentification30{ Identification IsoExact4AlphaNumericText Issuer IsoMax35Text SchemeName IsoMax35Text } %% ISecuritiesRTGS4Choice recursion level 1 with max 1 %% HoldIndicator6 recursion level 1 with max 1 class HoldIndicator6{ Indicator IsoYesNoIndicator } HoldIndicator6 *-- "0..0" RegistrationReason5 : Reason %% IMatchingDenied3Choice recursion level 1 with max 1 %% IUnilateralSplit3Choice recursion level 1 with max 1 %% Linkages39 recursion level 1 with max 1 Linkages39 *-- "0..1" IProcessingPosition8Choice : ProcessingPosition Linkages39 *-- "0..1" IDocumentNumber5Choice : MessageNumber Linkages39 *-- "1..1" IReferences46Choice : Reference Linkages39 *-- "0..1" IPartyIdentification92Choice : ReferenceOwner
RequestDetails15 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Reference | References of the transaction for which the securities settlement condition modification is requested. | References18 - Required 1..1 |
AutomaticBorrowing | Condition for automatic borrowing. | IAutomaticBorrowing7Choice - Optional 0..1 |
RetainIndicator | Specifies whether the instruction due to expire is confirmed for settlement. | IsoYesNoIndicator - Optional 0..1 |
Linkage | Specifies the type of linkage requested. | ILinkageType3Choice - Optional 0..1 |
Priority | Specifies whether the transaction is to be executed with a high priority. | IPriorityNumeric4Choice - Optional 0..1 |
OtherProcessing | Specifies another type of processing change request. | GenericIdentification30 - Unknown 0..0 |
PartialSettlementIndicator | Specifies whether partial settlement is allowed. | SettlementTransactionCondition5Code - Optional 0..1 |
SecuritiesRTGS | Specifies whether the settlement transaction is to be settled through an RTGS or a non RTGS system. | ISecuritiesRTGS4Choice - Optional 0..1 |
HoldIndicator | Specifies whether the transaction is on hold/blocked/frozen. | HoldIndicator6 - Optional 0..1 |
MatchingDenial | Specifies the matching processing change requested. | IMatchingDenied3Choice - Optional 0..1 |
UnilateralSplit | Specifies that the transaction is requested to be unilaterally split. | IUnilateralSplit3Choice - Optional 0..1 |
Linkages | Information regarding the linkage requested. | Linkages39 - Unknown 0..0 |
AdditionalInformation building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional specific modification criteria. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AdditionalInformation13 recursion level 0 with max 1 class AdditionalInformation13{ AccountOwnerTransactionIdentification IsoMax35Text } AdditionalInformation13 *-- "0..1" IClassificationType32Choice : ClassificationType AdditionalInformation13 *-- "0..1" SecuritiesAccount19 : SafekeepingAccount AdditionalInformation13 *-- "0..1" SecurityIdentification19 : FinancialInstrumentIdentification AdditionalInformation13 *-- "0..1" IFinancialInstrumentQuantity1Choice : Quantity AdditionalInformation13 *-- "0..1" IDateAndDateTimeChoice : EffectiveDate AdditionalInformation13 *-- "0..1" IDateAndDateTimeChoice : ExpiryDate AdditionalInformation13 *-- "0..1" IDateAndDateTimeChoice : CutOffDate AdditionalInformation13 *-- "0..1" PartyIdentification100 : Investor AdditionalInformation13 *-- "0..1" PartyIdentificationAndAccount117 : DeliveringParty1 AdditionalInformation13 *-- "0..1" PartyIdentificationAndAccount117 : ReceivingParty1 %% IClassificationType32Choice recursion level 1 with max 1 %% SecuritiesAccount19 recursion level 1 with max 1 class SecuritiesAccount19{ Identification IsoMax35Text Name IsoMax70Text } SecuritiesAccount19 *-- "0..1" GenericIdentification30 : Type %% SecurityIdentification19 recursion level 1 with max 1 class SecurityIdentification19{ ISIN IsoISINOct2015Identifier Description IsoMax140Text } SecurityIdentification19 *-- "0..0" OtherIdentification1 : OtherIdentification %% IFinancialInstrumentQuantity1Choice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% PartyIdentification100 recursion level 1 with max 1 class PartyIdentification100{ LEI IsoLEIIdentifier } PartyIdentification100 *-- "1..1" IPartyIdentification71Choice : Identification %% PartyIdentificationAndAccount117 recursion level 1 with max 1 class PartyIdentificationAndAccount117{ LEI IsoLEIIdentifier ProcessingIdentification IsoMax35Text } PartyIdentificationAndAccount117 *-- "1..1" IPartyIdentification71Choice : Identification PartyIdentificationAndAccount117 *-- "0..1" SecuritiesAccount19 : SafekeepingAccount %% PartyIdentificationAndAccount117 recursion level 1 with max 1 class PartyIdentificationAndAccount117{ LEI IsoLEIIdentifier ProcessingIdentification IsoMax35Text } PartyIdentificationAndAccount117 *-- "1..1" IPartyIdentification71Choice : Identification PartyIdentificationAndAccount117 *-- "0..1" SecuritiesAccount19 : SafekeepingAccount
AdditionalInformation13 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
AccountOwnerTransactionIdentification | Identification of the transaction as known by the account owner. Will be used in a unilateral split to provide the executing party with the account owner identification of each split transaction. | IsoMax35Text - Optional 0..1 |
ClassificationType | Type of instrument involved in the transactions on which the modification request should apply. | IClassificationType32Choice - Optional 0..1 |
SafekeepingAccount | Account to or from which a securities entry is made. | SecuritiesAccount19 - Optional 0..1 |
FinancialInstrumentIdentification | Identification of the financial instrument involved in the transactions on which the modification request should apply. | SecurityIdentification19 - Optional 0..1 |
Quantity | Quantity of financial instrument concerned by the settlement condition modification request. | IFinancialInstrumentQuantity1Choice - Optional 0..1 |
EffectiveDate | Date/time when the request should take effect. | IDateAndDateTimeChoice - Optional 0..1 |
ExpiryDate | Date/time when the request should cease to be in effect. | IDateAndDateTimeChoice - Optional 0..1 |
CutOffDate | Date/time of the release. | IDateAndDateTimeChoice - Optional 0..1 |
Investor | Party, either an individual or organisation, whose assets are being invested. | PartyIdentification100 - Optional 0..1 |
DeliveringParty1 | Party that, in a settlement chain interacts with the depository. | PartyIdentificationAndAccount117 - Optional 0..1 |
ReceivingParty1 | Party that, in a settlement chain interacts with the depository. | PartyIdentificationAndAccount117 - 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 SecuritiesSettlementConditionsModificationRequestV07 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementConditionsModificationRequestV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementConditionsModificationRequestV07Document implements IOuterDocument. Because SecuritiesSettlementConditionsModificationRequestV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementConditionsModificationRequestV07.
classDiagram class IOuterRecord SecuritiesSettlementConditionsModificationRequestV07 --|> IOuterRecord : Implements SecuritiesSettlementConditionsModificationRequestV07Document --|> IOuterDocument~SecuritiesSettlementConditionsModificationRequestV07~ : Implements class IOuterDocument~SecuritiesSettlementConditionsModificationRequestV07~ { SecuritiesSettlementConditionsModificationRequestV07 Message }
Document wrapper for serialization
The only real purpose SecuritiesSettlementConditionsModificationRequestV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.030.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementConditionsModificationRequestV07.ToDocument() method. The returned SecuritiesSettlementConditionsModificationRequestV07Document value will serialize correctly according to ISO 20022 standards.
classDiagram SecuritiesSettlementConditionsModificationRequestV07Document *-- SecuritiesSettlementConditionsModificationRequestV07 : 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.030.001.07">
<SctiesSttlmCondsModReq>
<AcctOwnr>
<!-- AccountOwner inner content -->
</AcctOwnr>
<SfkpgAcct>
<!-- SafekeepingAccount inner content -->
</SfkpgAcct>
<ReqDtls>
<!-- RequestDetails inner content -->
</ReqDtls>
<AddtlInf>
<!-- AdditionalInformation inner content -->
</AddtlInf>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctiesSttlmCondsModReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_fjVckW6uEeat2-NFbXd1Pw"
nextVersions="_vYSqsdBmEeihG9bKfarOOA"
previousVersion="_YSMXPwCTEeW_3KiG8SEjHA"
name="SecuritiesSettlementConditionsModificationRequestV07"
definition="Scope
An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be:
- a central securities depository participant which has an account with a central securities depository.
It could also be, if agreed in a service level agreement:
- a global custodian which has an account with its local agent (sub-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 which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage
The message may also be used to:
- re-send a message previously sent,
- provide a third party with a copy of a message for information,
- re-send to a third party a copy of a message for information
using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details.
The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="SctiesSttlmCondsModReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_fjVck26uEeat2-NFbXd1Pw"
nextVersions="_vYSqs9BmEeihG9bKfarOOA"
previousVersion="_YSMXRQCTEeW_3KiG8SEjHA"
name="SecuritiesMarketPracticeGroupGuideline"
definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.
These market practices are available on www.smpg.info."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_fjVclW6uEeat2-NFbXd1Pw"
nextVersions="_vYSqtdBmEeihG9bKfarOOA"
previousVersion="_YSMXRwCTEeW_3KiG8SEjHA"
name="AccountOwner"
definition="Party that legally owns the account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctOwnr"
complexType="_lwSA1GwBEeWLq_lbZ2Mhyw" />
<messageBuildingBlock
xmi:id="_fjVcl26uEeat2-NFbXd1Pw"
nextVersions="_vYSqt9BmEeihG9bKfarOOA"
previousVersion="_YSMXSQCTEeW_3KiG8SEjHA"
name="SafekeepingAccount"
definition="Account to or from which a securities entry is made."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SfkpgAcct"
complexType="_T_JUKtp-Ed-ak6NoX_4Aeg_1976638301" />
<messageBuildingBlock
xmi:id="_fjVcmW6uEeat2-NFbXd1Pw"
nextVersions="_vYSqudBmEeihG9bKfarOOA"
previousVersion="_YSMXSwCTEeW_3KiG8SEjHA"
name="RequestDetails"
definition="Details of the request."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="ReqDtls"
complexType="_-zrY2zqEEeWVrPy0StzzSg" />
<messageBuildingBlock
xmi:id="_fjVcm26uEeat2-NFbXd1Pw"
nextVersions="_vYSqu9BmEeihG9bKfarOOA"
previousVersion="_YSMXTQCTEeW_3KiG8SEjHA"
name="AdditionalInformation"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="AddtlInf"
complexType="_ZmIZgY7HEeaa5_S8lsRKCQ" />
<messageBuildingBlock
xmi:id="_fjVcnW6uEeat2-NFbXd1Pw"
nextVersions="_vYSqvdBmEeihG9bKfarOOA"
previousVersion="_YSMXTwCTEeW_3KiG8SEjHA"
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="030"
flavour="001"
version="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.