SecuritiesAccountModificationRequestV01

reda.023.001.01

The SecuritiesAccountModificationRequest message is sent by an instructing party to the executing party to instruct the update of an existing securities account by amending its existing attributes or by providing additional attibutes details.

Usage: Processing and confirmation of the securities account creation request message are provided via a SecuritiesAccountStatusAdvice message.

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
%% SecuritiesAccountModificationRequestV01 recursion level 0 with max 0
SecuritiesAccountModificationRequestV01 *-- "0..1" MessageHeader1 : MessageHeader
SecuritiesAccountModificationRequestV01 *-- "1..1" SecuritiesAccount19 : AccountIdentification
SecuritiesAccountModificationRequestV01 *-- "1..1" SecuritiesAccountModification2 : Modification
SecuritiesAccountModificationRequestV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

Now, we will zero-in one-by-one on each of these building blocks.

MessageHeader building block

Common business identification for the message. Set of characteristics, such as the identification or the creation date and time, specific to the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageHeader1 recursion level 0 with max 1
class MessageHeader1{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageHeader1 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the sender, to unambiguously identify the message. Usage: The sender has to make sure that MessageIdentification is unique for a pre-agreed period. IsoMax35Text - Required 1..1
CreationDateTime Date and time at which the message was created. IsoISODateTime - Optional 0..1

AccountIdentification building block

Identification of the securities account to be updated in the executing party system. 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

Modification building block

Further details about the requested modification. Specifies the details of the modification to be applied on the securities account reference data. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesAccountModification2 recursion level 0 with max 1
class SecuritiesAccountModification2{
    ScopeIndication DataModification1Code
}
SecuritiesAccountModification2 *-- "1..1" ISecuritiesAccountModification2Choice : RequestedModification
%% ISecuritiesAccountModification2Choice recursion level 1 with max 1
  

SecuritiesAccountModification2 members

Member name Description Data Type / Multiplicity
ScopeIndication Specifies the type of requested modification. DataModification1Code - Required 1..1
RequestedModification Specifies which elements to be modified for the securities account reference data. ISecuritiesAccountModification2Choice - Required 1..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 SecuritiesAccountModificationRequestV01 implementation follows a specific implementaiton pattern. First of all, SecuritiesAccountModificationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesAccountModificationRequestV01Document implements IOuterDocument. Because SecuritiesAccountModificationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesAccountModificationRequestV01.

classDiagram
    class IOuterRecord
    SecuritiesAccountModificationRequestV01 --|> IOuterRecord : Implements
    SecuritiesAccountModificationRequestV01Document --|> IOuterDocument~SecuritiesAccountModificationRequestV01~ : Implements
    class IOuterDocument~SecuritiesAccountModificationRequestV01~ {
        SecuritiesAccountModificationRequestV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesAccountModificationRequestV01Document *-- SecuritiesAccountModificationRequestV01 : 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:reda.023.001.01">
    <SctiesAcctModReq>
        <MsgHdr>
            <!-- MessageHeader inner content -->
        </MsgHdr>
        <AcctId>
            <!-- AccountIdentification inner content -->
        </AcctId>
        <Mod>
            <!-- Modification inner content -->
        </Mod>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesAcctModReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_KAu-rZ2fEem_Be8NuxvF7Q"
  name="SecuritiesAccountModificationRequestV01"
  definition="The SecuritiesAccountModificationRequest message is sent by an instructing party to the executing party to instruct the update of an existing securities account by amending its existing attributes or by providing additional attibutes details.&#xD;&#xA;&#xD;&#xA;Usage:&#xD;&#xA;Processing and confirmation of the securities account creation request message are provided via a SecuritiesAccountStatusAdvice message."
  registrationStatus="Registered"
  messageSet="_Fl3iMBHREeqzEaNIFJIN-g"
  xmlTag="SctiesAcctModReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_Za_90J5HEemQg7pJhFUUYg"
    name="MessageHeader"
    definition="Common business identification for the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MsgHdr"
    complexType="_75DzkaMgEeCJ6YNENx4h-w_-613853819" />
  <messageBuildingBlock
    xmi:id="_KAu-u52fEem_Be8NuxvF7Q"
    name="AccountIdentification"
    definition="Identification of the securities account to be updated in the executing party system."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AcctId"
    complexType="_T_JUKtp-Ed-ak6NoX_4Aeg_1976638301" />
  <messageBuildingBlock
    xmi:id="_KAu-vZ2fEem_Be8NuxvF7Q"
    name="Modification"
    definition="Further details about the requested modification."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="Mod"
    complexType="_70DO0Tp0Eemk2e6qGBk8IQ" />
  <messageBuildingBlock
    xmi:id="_KAu-v52fEem_Be8NuxvF7Q"
    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="reda"
    messageFunctionality="023"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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