ZagTrader

reda: Reference Data

reda.007 Security Maintenance Request

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

reda.007 is the ISO 20022 SecurityMaintenanceRequest message in the Reference Data business area (reda). The latest version is reda.007.001.01.

Message
SecurityMaintenanceRequest
Latest version
reda.007.001.01
Submitting organisation
T2S
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What reda.007 is for

An instructing party sends a SecurityMaintenanceRequest message to an executing/servicing party to request the maintenance of financial instrument details in their system.

The instructing party - executing/servicing party relationship may be:

- Central Securities Depositories (CSD) who would like to publish security static data, or

- a Corporate, or

- a Bank, or

- a Market Infrastructure, or

- a Market Data Provider.

The request is sent when the instructing party identified a gap in the security data within the executing/servicing party system. The instructing party needs this security to be updated at the executing /servicing party to perform its activities.

Initiator: instructing party.

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

reda.007 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

VersionRegistration statusPublished in
reda.007.001.01latestRegisteredLatest version set

reda.007 message structure

The building blocks of reda.007.001.01 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

  • Document [1..1]
    • SctyMntncReq SecurityMaintenanceRequest [1..1]
      • MsgHdr Message Header [0..1]MessageHeader1

        Common business identification for the message.

        • MsgId Message Identification [1..1]Max35Text

          Point to point reference, as assigned by the sender, to unambiguously identify the message.

        • CreDtTm Creation Date Time [0..1]ISODateTime

          Date and time at which the message was created.

      • UpdTp Update Type [1..1]UpdateType36Choice (choice)

        Request to maintain data's of a security.

        • UpdTp Update Type [1..3]UpdateType35Choice (choice)

          Request to add, modify or delete data's of a security.

          • Add Add [1..1]SecurityAttributes12
          • Del Delete [1..1]SecurityAttributes12
          • Modfy Modify [1..1]SecurityAttributes12
        • Rplc Replace [1..1]SecurityAttributes12

          Request to replace all present data of a security.

          • FinInstrmTp Financial Instrument Type [0..*]FinancialInstrument97
          • FinInstrmAttrbts Financial Instrument Attributes [0..*]CommonFinancialInstrumentAttributes12
          • SplmtryData Supplementary Data [0..*]SupplementaryData1
      • UpdRsn Update Reason [0..1]SecuritiesUpdateReason1Choice (choice)

        Reason for the update of a security.

        • Cd Code [1..1]ExternalSecuritiesUpdateReason1Code

          Update reason, as published in an external code set.

        • Prtry Proprietary [1..1]GenericIdentification30

          Update reason, in a proprietary form.

          • Id Identification [1..1]Exact4AlphaNumericText
          • Issr Issuer [1..1]Max35Text
          • SchmeNm Scheme Name [0..1]Max35Text
      • FinInstrmId Financial Instrument Identification [1..1]SecurityIdentification39

        Identification of the financial instrument.

        • ISIN ISIN [0..1]ISIN2021Identifier

          International Securities Identification Number (ISIN).

        • OthrId Other Identification [0..*]OtherIdentification1

          Identification of a security by proprietary or domestic identification scheme.

          • Id Identification [1..1]Max35Text
          • Sfx Suffix [0..1]Max16Text
          • Tp Type [1..1]IdentificationSource3Choice (choice)
        • Desc Description [0..1]Max140Text

          Textual description of a security instrument.

      • SplmtryData Supplementary Data [0..*]SupplementaryData1

        Additional information that cannot be captured in the structured elements and/or any other specific block.

        • PlcAndNm Place And Name [0..1]Max350Text

          Unambiguous reference to the location where the supplementary data must be inserted in the message instance.

        • Envlp Envelope [1..1]SupplementaryDataEnvelope1

          Technical element wrapping the supplementary data.

Have a reda.007 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

External code sets used in reda.007

These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.

reda.007 questions

What is the latest version of reda.007?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is reda.007.001.01.
What is the root element of reda.007?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:reda.007.001.01, and its message element is SctyMntncReq (SecurityMaintenanceRequest).
Is there an MT equivalent of reda.007?
No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.