Iso20022

SecuritiesSettlementConditionsModificationRequestV02

sese.030.001.02

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:

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
%% SecuritiesSettlementConditionsModificationRequestV02 recursion level 0 with max 0
SecuritiesSettlementConditionsModificationRequestV02 *-- "0..1" IPartyIdentification36Choice : AccountOwner
SecuritiesSettlementConditionsModificationRequestV02 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
SecuritiesSettlementConditionsModificationRequestV02 *-- "1..1" RequestDetails6 : RequestDetails
SecuritiesSettlementConditionsModificationRequestV02 *-- "0..1" AdditionalInformation7 : AdditionalInformation
SecuritiesSettlementConditionsModificationRequestV02 *-- "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. Choice of identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification36Choice recursion level 0 with max 1

PartyIdentification36Choice members

Member name Description Data Type / Multiplicity

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
%% SecuritiesAccount13 recursion level 0 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% GenericIdentification20 recursion level 1 with max 1
class GenericIdentification20{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}

SecuritiesAccount13 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. GenericIdentification20 - 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
%% RequestDetails6 recursion level 0 with max 1
class RequestDetails6{
    RetainIndicator IsoYesNoIndicator
    PartialSettlementIndicator SettlementTransactionCondition5Code
}
RequestDetails6 *-- "1..1" References7 : Reference
RequestDetails6 *-- "0..1" IAutomaticBorrowing2Choice : AutomaticBorrowing
RequestDetails6 *-- "0..1" ILinkageType1Choice : Linkage
RequestDetails6 *-- "0..1" IPriorityNumeric1Choice : Priority
RequestDetails6 *-- "0..0" GenericIdentification20 : OtherProcessing
RequestDetails6 *-- "0..1" ISecuritiesRTGS1Choice : SecuritiesRTGS
RequestDetails6 *-- "0..1" HoldIndicator2 : HoldIndicator
RequestDetails6 *-- "0..1" IMatchingDenied1Choice : MatchingDenial
RequestDetails6 *-- "0..1" IUnilateralSplit1Choice : UnilateralSplit
RequestDetails6 *-- "0..0" Linkages10 : Linkages
%% References7 recursion level 1 with max 1
class References7{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CommonIdentification IsoMax35Text
    TradeIdentification IsoMax35Text
}
%% IAutomaticBorrowing2Choice recursion level 1 with max 1
%% ILinkageType1Choice recursion level 1 with max 1
%% IPriorityNumeric1Choice recursion level 1 with max 1
%% GenericIdentification20 recursion level 1 with max 1
class GenericIdentification20{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}
%% ISecuritiesRTGS1Choice recursion level 1 with max 1
%% HoldIndicator2 recursion level 1 with max 1
class HoldIndicator2{
    Indicator IsoYesNoIndicator
}
HoldIndicator2 *-- "0..0" RegistrationReason1 : Reason
%% IMatchingDenied1Choice recursion level 1 with max 1
%% IUnilateralSplit1Choice recursion level 1 with max 1
%% Linkages10 recursion level 1 with max 1
Linkages10 *-- "0..1" IProcessingPosition2Choice : ProcessingPosition
Linkages10 *-- "0..1" IDocumentNumber1Choice : MessageNumber
Linkages10 *-- "1..1" IReferences13Choice : Reference
Linkages10 *-- "0..1" IPartyIdentification36Choice : ReferenceOwner

RequestDetails6 members

Member name Description Data Type / Multiplicity
Reference References of the transaction for which the securities settlement condition modification is requested. References7 - Required 1..1
AutomaticBorrowing Condition for automatic borrowing. IAutomaticBorrowing2Choice - 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. ILinkageType1Choice - Optional 0..1
Priority Specifies whether the transaction is to be executed with a high priority. IPriorityNumeric1Choice - Optional 0..1
OtherProcessing Specifies another type of processing change request. GenericIdentification20 - 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. ISecuritiesRTGS1Choice - Optional 0..1
HoldIndicator Specifies whether the transaction is on hold/blocked/frozen. HoldIndicator2 - Optional 0..1
MatchingDenial Specifies the matching processing change requested. IMatchingDenied1Choice - Optional 0..1
UnilateralSplit Specifies that the transaction is requested to be unilaterally split. IUnilateralSplit1Choice - Optional 0..1
Linkages Information regarding the linkage requested. Linkages10 - 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
%% AdditionalInformation7 recursion level 0 with max 1
class AdditionalInformation7{
    AccountOwnerTransactionIdentification IsoMax35Text
}
AdditionalInformation7 *-- "0..1" IClassificationType1Choice : ClassificationType
AdditionalInformation7 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount
AdditionalInformation7 *-- "0..1" SecurityIdentification14 : FinancialInstrumentIdentification
AdditionalInformation7 *-- "0..1" IFinancialInstrumentQuantity1Choice : Quantity
AdditionalInformation7 *-- "0..1" IDateAndDateTimeChoice : EffectiveDate
AdditionalInformation7 *-- "0..1" IDateAndDateTimeChoice : ExpiryDate
AdditionalInformation7 *-- "0..1" IDateAndDateTimeChoice : CutOffDate
AdditionalInformation7 *-- "0..1" IPartyIdentification43Choice : Investor
AdditionalInformation7 *-- "0..1" PartyIdentificationAndAccount43 : DeliveringParty1
AdditionalInformation7 *-- "0..1" PartyIdentificationAndAccount43 : ReceivingParty1
%% IClassificationType1Choice recursion level 1 with max 1
%% SecuritiesAccount13 recursion level 1 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% SecurityIdentification14 recursion level 1 with max 1
class SecurityIdentification14{
    ISIN IsoISINIdentifier
    Description IsoMax140Text
}
SecurityIdentification14 *-- "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
%% IPartyIdentification43Choice recursion level 1 with max 1
%% PartyIdentificationAndAccount43 recursion level 1 with max 1
class PartyIdentificationAndAccount43{
    ProcessingIdentification IsoMax35Text
}
PartyIdentificationAndAccount43 *-- "1..1" IPartyIdentification43Choice : Identification
PartyIdentificationAndAccount43 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount
%% PartyIdentificationAndAccount43 recursion level 1 with max 1
class PartyIdentificationAndAccount43{
    ProcessingIdentification IsoMax35Text
}
PartyIdentificationAndAccount43 *-- "1..1" IPartyIdentification43Choice : Identification
PartyIdentificationAndAccount43 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount

AdditionalInformation7 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. IClassificationType1Choice - Optional 0..1
SafekeepingAccount Account to or from which a securities entry is made. SecuritiesAccount13 - Optional 0..1
FinancialInstrumentIdentification Identification of the financial instrument involved in the transactions on which the modification request should apply. SecurityIdentification14 - 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. IPartyIdentification43Choice - Optional 0..1
DeliveringParty1 Party that, in a settlement chain interacts with the depository. PartyIdentificationAndAccount43 - Optional 0..1
ReceivingParty1 Party that, in a settlement chain interacts with the depository. PartyIdentificationAndAccount43 - 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 SecuritiesSettlementConditionsModificationRequestV02 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementConditionsModificationRequestV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementConditionsModificationRequestV02Document implements IOuterDocument. Because SecuritiesSettlementConditionsModificationRequestV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementConditionsModificationRequestV02.

classDiagram
    class IOuterRecord
    SecuritiesSettlementConditionsModificationRequestV02 --|> IOuterRecord : Implements
    SecuritiesSettlementConditionsModificationRequestV02Document --|> IOuterDocument~SecuritiesSettlementConditionsModificationRequestV02~ : Implements
    class IOuterDocument~SecuritiesSettlementConditionsModificationRequestV02~ {
        SecuritiesSettlementConditionsModificationRequestV02 Message
     }

Document wrapper for serialization

The only real purpose SecuritiesSettlementConditionsModificationRequestV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.030.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementConditionsModificationRequestV02.ToDocument() method. The returned SecuritiesSettlementConditionsModificationRequestV02Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    SecuritiesSettlementConditionsModificationRequestV02Document *-- SecuritiesSettlementConditionsModificationRequestV02 : 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.02">
    <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="_YAYA8dtaEd-RF5yaMAVhAw"
  nextVersions="_wcljofvdEeCBQp5TnX1XKQ"
  previousVersion="_0LJH2NE5Ed-BzquC8wXy7w_2056028498"
  name="SecuritiesSettlementConditionsModificationRequestV02"
  definition="Scope&#xD;&#xA;An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.&#xD;&#xA;The account owner/servicer relationship may be:&#xD;&#xA;- a central securities depository participant which has an account with a central securities depository.&#xD;&#xA;It could also be, if agreed in a service level agreement:&#xD;&#xA;- a global custodian which has an account with its local agent (sub-custodian), or&#xD;&#xA;- an investment management institution which manage a fund account opened at a custodian, or&#xD;&#xA;- a broker which has an account with a custodian, or&#xD;&#xA;- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.&#xD;&#xA;Usage&#xA;The message may also be used to:&#xA;- re-send a message previously sent,&#xA;- provide a third party with a copy of a message for information,&#xA;- re-send to a third party a copy of a message for information.&#xA;using the relevant elements in the Business Application Header.&#xD;&#xA;This message cannot be used to request the modification of trade or event details.&#xD;&#xA;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.&#xA;ISO 15022 - 20022 Coexistence&#xA;This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="SctiesSttlmCondsModReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_YAYBA9taEd-RF5yaMAVhAw"
    name="CoexistenceCharacterSetXRule"
    definition="During ISO 15022 – 20022 coexistence, characters used in all text fields must correspond to character set X, that is, a-z A-Z / - ? : ( ) . , ‘ + { } CR LF."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_YAYBBdtaEd-RF5yaMAVhAw"
    name="CoexistenceIdentificationRule"
    definition="During ISO 15022 – 20022 coexistence, all transaction and document identifications or references must be 16 characters or less. The field must not start or end with a slash ‘/’ or contain two consecutive slashes ‘//’."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_YAYBB9taEd-RF5yaMAVhAw"
    name="SecuritiesMarketPracticeGroupGuideline"
    definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.&#xD;&#xA;These market practices are available on www.smpg.info."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_YAYA9dtaEd-RF5yaMAVhAw"
    name="AccountOwner"
    definition="Party that legally owns the account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AcctOwnr"
    complexType="_qU9DBeaPEd-q8fx_Zl_34A" />
  <messageBuildingBlock
    xmi:id="_YAYA99taEd-RF5yaMAVhAw"
    name="SafekeepingAccount"
    definition="Account to or from which a securities entry is made."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SfkpgAcct"
    complexType="_T_vKAdp-Ed-ak6NoX_4Aeg_-178975462" />
  <messageBuildingBlock
    xmi:id="_YAYA-dtaEd-RF5yaMAVhAw"
    name="RequestDetails"
    definition="Details of the request."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_5VWQEeDVEd-udr336SN7mQ" />
  <messageBuildingBlock
    xmi:id="_YAYA-9taEd-RF5yaMAVhAw"
    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="_eaw-ReaOEd-q8fx_Zl_34A" />
  <messageBuildingBlock
    xmi:id="_YAYBAdtaEd-RF5yaMAVhAw"
    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="02" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.