sese.030.002.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
%% SecuritiesSettlementConditionsModificationRequest002V07 recursion level 0 with max 0
SecuritiesSettlementConditionsModificationRequest002V07 *-- "0..1" PartyIdentification119 : AccountOwner
SecuritiesSettlementConditionsModificationRequest002V07 *-- "1..1" SecuritiesAccount30 : SafekeepingAccount
SecuritiesSettlementConditionsModificationRequest002V07 *-- "1..1" RequestDetails16 : RequestDetails
SecuritiesSettlementConditionsModificationRequest002V07 *-- "0..1" AdditionalInformation14 : AdditionalInformation
SecuritiesSettlementConditionsModificationRequest002V07 *-- "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
%% PartyIdentification119 recursion level 0 with max 1
class PartyIdentification119{
LEI IsoLEIIdentifier
}
PartyIdentification119 *-- "1..1" IPartyIdentification103Choice : Identification
%% IPartyIdentification103Choice recursion level 1 with max 1
PartyIdentification119 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique identification of the party. | IPartyIdentification103Choice - 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 |
RequestDetails building block
Details of the request. Details of the settlement condition modification request. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% RequestDetails16 recursion level 0 with max 1
class RequestDetails16{
RetainIndicator IsoYesNoIndicator
PartialSettlementIndicator SettlementTransactionCondition5Code
}
RequestDetails16 *-- "1..1" References21 : Reference
RequestDetails16 *-- "0..1" IAutomaticBorrowing11Choice : AutomaticBorrowing
RequestDetails16 *-- "0..1" ILinkageType4Choice : Linkage
RequestDetails16 *-- "0..1" IPriorityNumeric5Choice : Priority
RequestDetails16 *-- "0..0" GenericIdentification47 : OtherProcessing
RequestDetails16 *-- "0..1" ISecuritiesRTGS5Choice : SecuritiesRTGS
RequestDetails16 *-- "0..1" HoldIndicator7 : HoldIndicator
RequestDetails16 *-- "0..1" IMatchingDenied4Choice : MatchingDenial
RequestDetails16 *-- "0..1" IUnilateralSplit4Choice : UnilateralSplit
RequestDetails16 *-- "0..0" Linkages44 : Linkages
%% References21 recursion level 1 with max 1
class References21{
AccountOwnerTransactionIdentification IsoRestrictedFINXMax16Text
AccountServicerTransactionIdentification IsoRestrictedFINXMax16Text
MarketInfrastructureTransactionIdentification IsoRestrictedFINXMax16Text
ProcessorTransactionIdentification IsoRestrictedFINXMax16Text
PoolIdentification IsoRestrictedFINXMax16Text
CommonIdentification IsoRestrictedFINXMax16Text
TradeIdentification IsoRestrictedFINXMax16Text
}
%% IAutomaticBorrowing11Choice recursion level 1 with max 1
%% ILinkageType4Choice recursion level 1 with max 1
%% IPriorityNumeric5Choice recursion level 1 with max 1
%% GenericIdentification47 recursion level 1 with max 1
class GenericIdentification47{
Identification IsoExact4AlphaNumericText
Issuer IsoMax4AlphaNumericText
SchemeName IsoMax4AlphaNumericText
}
%% ISecuritiesRTGS5Choice recursion level 1 with max 1
%% HoldIndicator7 recursion level 1 with max 1
class HoldIndicator7{
Indicator IsoYesNoIndicator
}
HoldIndicator7 *-- "0..0" RegistrationReason6 : Reason
%% IMatchingDenied4Choice recursion level 1 with max 1
%% IUnilateralSplit4Choice recursion level 1 with max 1
%% Linkages44 recursion level 1 with max 1
Linkages44 *-- "0..1" IProcessingPosition18Choice : ProcessingPosition
Linkages44 *-- "0..1" IDocumentNumber16Choice : MessageNumber
Linkages44 *-- "1..1" IReferences54Choice : Reference
Linkages44 *-- "0..1" IPartyIdentification103Choice : ReferenceOwner
RequestDetails16 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Reference | References of the transaction for which the securities settlement condition modification is requested. | References21 - Required 1..1 |
| AutomaticBorrowing | Condition for automatic borrowing. | IAutomaticBorrowing11Choice - 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. | ILinkageType4Choice - Optional 0..1 |
| Priority | Specifies whether the transaction is to be executed with a high priority. | IPriorityNumeric5Choice - Optional 0..1 |
| OtherProcessing | Specifies another type of processing change request. | GenericIdentification47 - 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. | ISecuritiesRTGS5Choice - Optional 0..1 |
| HoldIndicator | Specifies whether the transaction is on hold/blocked/frozen. | HoldIndicator7 - Optional 0..1 |
| MatchingDenial | Specifies the matching processing change requested. | IMatchingDenied4Choice - Optional 0..1 |
| UnilateralSplit | Specifies that the transaction is requested to be unilaterally split. | IUnilateralSplit4Choice - Optional 0..1 |
| Linkages | Information regarding the linkage requested. | Linkages44 - 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
%% AdditionalInformation14 recursion level 0 with max 1
class AdditionalInformation14{
AccountOwnerTransactionIdentification IsoRestrictedFINXMax16Text
}
AdditionalInformation14 *-- "0..1" IClassificationType33Choice : ClassificationType
AdditionalInformation14 *-- "0..1" SecuritiesAccount30 : SafekeepingAccount
AdditionalInformation14 *-- "0..1" SecurityIdentification20 : FinancialInstrumentIdentification
AdditionalInformation14 *-- "0..1" IFinancialInstrumentQuantity15Choice : Quantity
AdditionalInformation14 *-- "0..1" IDateAndDateTimeChoice : EffectiveDate
AdditionalInformation14 *-- "0..1" IDateAndDateTimeChoice : ExpiryDate
AdditionalInformation14 *-- "0..1" IDateAndDateTimeChoice : CutOffDate
AdditionalInformation14 *-- "0..1" PartyIdentification111 : Investor
AdditionalInformation14 *-- "0..1" PartyIdentificationAndAccount146 : DeliveringParty1
AdditionalInformation14 *-- "0..1" PartyIdentificationAndAccount146 : ReceivingParty1
%% IClassificationType33Choice recursion level 1 with max 1
%% SecuritiesAccount30 recursion level 1 with max 1
class SecuritiesAccount30{
Identification IsoRestrictedFINXMax35Text
Name IsoMax70Text
}
SecuritiesAccount30 *-- "0..1" GenericIdentification47 : Type
%% SecurityIdentification20 recursion level 1 with max 1
class SecurityIdentification20{
ISIN IsoISINOct2015Identifier
Description IsoRestrictedFINXMax140Text
}
SecurityIdentification20 *-- "0..0" OtherIdentification2 : OtherIdentification
%% IFinancialInstrumentQuantity15Choice 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
%% PartyIdentification111 recursion level 1 with max 1
class PartyIdentification111{
LEI IsoLEIIdentifier
}
PartyIdentification111 *-- "1..1" IPartyIdentification104Choice : Identification
%% PartyIdentificationAndAccount146 recursion level 1 with max 1
class PartyIdentificationAndAccount146{
LEI IsoLEIIdentifier
ProcessingIdentification IsoRestrictedFINXMax16Text
}
PartyIdentificationAndAccount146 *-- "1..1" IPartyIdentification104Choice : Identification
PartyIdentificationAndAccount146 *-- "0..1" SecuritiesAccount30 : SafekeepingAccount
%% PartyIdentificationAndAccount146 recursion level 1 with max 1
class PartyIdentificationAndAccount146{
LEI IsoLEIIdentifier
ProcessingIdentification IsoRestrictedFINXMax16Text
}
PartyIdentificationAndAccount146 *-- "1..1" IPartyIdentification104Choice : Identification
PartyIdentificationAndAccount146 *-- "0..1" SecuritiesAccount30 : SafekeepingAccount
AdditionalInformation14 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. | IsoRestrictedFINXMax16Text - Optional 0..1 |
| ClassificationType | Type of instrument involved in the transactions on which the modification request should apply. | IClassificationType33Choice - Optional 0..1 |
| SafekeepingAccount | Account to or from which a securities entry is made. | SecuritiesAccount30 - Optional 0..1 |
| FinancialInstrumentIdentification | Identification of the financial instrument involved in the transactions on which the modification request should apply. | SecurityIdentification20 - Optional 0..1 |
| Quantity | Quantity of financial instrument concerned by the settlement condition modification request. | IFinancialInstrumentQuantity15Choice - 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. | PartyIdentification111 - Optional 0..1 |
| DeliveringParty1 | Party that, in a settlement chain interacts with the depository. | PartyIdentificationAndAccount146 - Optional 0..1 |
| ReceivingParty1 | Party that, in a settlement chain interacts with the depository. | PartyIdentificationAndAccount146 - 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 SecuritiesSettlementConditionsModificationRequest002V07 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementConditionsModificationRequest002V07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementConditionsModificationRequest002V07Document implements IOuterDocument. Because SecuritiesSettlementConditionsModificationRequest002V07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementConditionsModificationRequest002V07.
classDiagram
class IOuterRecord
SecuritiesSettlementConditionsModificationRequest002V07 --|> IOuterRecord : Implements
SecuritiesSettlementConditionsModificationRequest002V07Document --|> IOuterDocument~SecuritiesSettlementConditionsModificationRequest002V07~ : Implements
class IOuterDocument~SecuritiesSettlementConditionsModificationRequest002V07~ {
SecuritiesSettlementConditionsModificationRequest002V07 Message
}
Document wrapper for serialization
The only real purpose SecuritiesSettlementConditionsModificationRequest002V07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.030.002.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementConditionsModificationRequest002V07.ToDocument() method. The returned SecuritiesSettlementConditionsModificationRequest002V07Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SecuritiesSettlementConditionsModificationRequest002V07Document *-- SecuritiesSettlementConditionsModificationRequest002V07 : 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.002.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="_BZe3O5w0EeazcsnODTksnQ"
nextVersions="_OMbE8_fXEeiNZp_PtLohLw"
previousVersion="_6HTX8ZNLEeWGlc8L7oPDIg"
name="SecuritiesSettlementConditionsModificationRequest002V07"
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="_BZe3PZw0EeazcsnODTksnQ"
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="_BZe3P5w0EeazcsnODTksnQ"
name="AccountOwner"
definition="Party that legally owns the account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AcctOwnr"
complexType="_Vy5oUaWYEea1rLcUp8Fsgw" />
<messageBuildingBlock
xmi:id="_BZe3QZw0EeazcsnODTksnQ"
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="_BZe3Q5w0EeazcsnODTksnQ"
name="RequestDetails"
definition="Details of the request."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="ReqDtls"
complexType="_6GVu8ZNLEeWGlc8L7oPDIg" />
<messageBuildingBlock
xmi:id="_BZe3RZw0EeazcsnODTksnQ"
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="_BZe52Zw0EeazcsnODTksnQ" />
<messageBuildingBlock
xmi:id="_BZe3R5w0EeazcsnODTksnQ"
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="002"
version="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.