ZagTrader

reda: Reference Data

reda.022 Party Modification Request

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

reda.022 is the ISO 20022 PartyModificationRequest message in the Reference Data business area (reda). The latest version is reda.022.001.02, and 2 versions are in the repository.

Message
PartyModificationRequest
Latest version
reda.022.001.02
Submitting organisation
4CBs and Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What reda.022 is for

The PartyModificationRequest message is sent by the instructing party to the executing party to request for an update of the party reference data of a party defined in the executing system.

It aims at instructing the update of an existing party by amending its existing details or by providing additional details.

Processing and confirmation of the party modification request message are provided via a party status advice.

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

reda.022 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.022.001.02latestRegisteredLatest version set
reda.022.001.01RegisteredPrevious version set

reda.022 message structure

The building blocks of reda.022.001.02 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]
    • PtyModReq PartyModificationRequest [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.

      • SysPtyId System Party Identification [1..1]SystemPartyIdentification8

        Unique identification, as assigned by the executing system, to unambiguously identify the party to be modified.

        • Id Identification [1..1]PartyIdentification136

          Unique identification to unambiguously identify the party within the system.

          • Id Identification [1..1]PartyIdentification120Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
        • RspnsblPtyId Responsible Party Identification [0..1]PartyIdentification136

          Unique identification of the party responsible for the maintenance of the party reference data.

          • Id Identification [1..1]PartyIdentification120Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
      • Mod Modification [1..*]SystemPartyModification3

        Identifies the list of requested modifications to be executed by the system.

        • ScpIndctn Scope Indication [1..1]DataModification1Code

          Specifies the type of requested modification.

        • ReqdMod Requested Modification [1..1]SystemPartyModification3Choice (choice)

          Specifies the set of elements to be modified for the party reference data.

          • SysPtyDt System Party Date [1..1]SystemParty2
          • PtyId Party Identification [1..1]SystemPartyIdentification10
          • PtyNm Party Name [1..1]PartyName3
          • CtctDtls Contact Details [1..1]Contact14
          • TechAdr Technical Address [1..1]TechnicalIdentification2Choice (choice)
          • PtyAdr Party Address [1..1]PostalAddress28
          • ResTp Residence Type [1..1]ResidenceType1Code
          • LckSts Lock Status [1..1]PartyLockStatus1
          • SysRstrctn System Restriction [1..1]SystemRestriction1
          • MktSpcfcAttr Market Specific Attribute [1..1]MarketSpecificAttribute1
      • 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.022 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

reda.022 questions

What is the latest version of reda.022?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is reda.022.001.02.
What is the root element of reda.022?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:reda.022.001.02, and its message element is PtyModReq (PartyModificationRequest).
Is there an MT equivalent of reda.022?
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.