ZagTrader

reda: Reference Data

reda.015 Party Query

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

reda.015 is the ISO 20022 PartyQuery message in the Reference Data business area (reda). The latest version is reda.015.001.01.

Message
PartyQuery
Latest version
reda.015.001.01
Submitting organisation
T2S
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What reda.015 is for

The PartyQuery message is sent by a central securities depository, a national central bank, a central securities depository participant, a central counter party, a payment bank, a trading party or a stock exchange to the executing party to query for the party reference data of a party defined in the system.

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

reda.015 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.015.001.01latestRegisteredLatest version set

reda.015 message structure

The building blocks of reda.015.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]
    • PtyQry PartyQuery [1..1]
      • MsgHdr Message Header [0..1]MessageHeader2

        Point to point reference elements, as assigned by the instructing party, to unambiguously identify the query 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.

        • ReqTp Request Type [0..1]RequestType2Choice (choice)

          Specific actions to be executed through the request.

          • PmtCtrl Payment Control [1..1]RequestType1Code
          • Enqry Enquiry [1..1]RequestType2Code
          • Prtry Proprietary [1..1]GenericIdentification1
      • SchCrit Search Criteria [1..1]PartyDataSearchCriteria2

        Defines the criteria to be used to query the party reference data by the executing system.

        • OpngDt Opening Date [0..1]DatePeriodSearch1Choice (choice)

          Specifies the opening date of the party.

          • FrDt From Date [1..1]ISODate
          • ToDt To Date [1..1]ISODate
          • FrToDt From To Date [1..1]DatePeriod2
          • EQDt Equal Date [1..1]ISODate
          • NEQDt Not Equal Date [1..1]ISODate
        • ClsgDt Closing Date [0..1]DatePeriodSearch1Choice (choice)

          Specifies the closing date of the party.

          • FrDt From Date [1..1]ISODate
          • ToDt To Date [1..1]ISODate
          • FrToDt From To Date [1..1]DatePeriod2
          • EQDt Equal Date [1..1]ISODate
          • NEQDt Not Equal Date [1..1]ISODate
        • Tp Type [0..1]SystemPartyType1Choice (choice)

          Specifies the type classification of the party.

          • Cd Code [1..1]ExternalSystemPartyType1Code
          • Prtry Proprietary [1..1]Max35Text
        • 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
        • PtyId Party Identification [0..1]PartyIdentification136

          Unique identification to unambiguously identify the party within the system.

          • Id Identification [1..1]PartyIdentification120Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
        • RstrctnId Restriction Identification [0..1]Max35Text

          Specifies the identification of a restriction.

        • RstrctnIsseDt Restriction Issue Date [0..1]DateAndDateTimeSearch4Choice (choice)

          Specifies the date when the restriction for the party has been issued.

          • DtTm Date Time [1..1]DateTimeSearch2Choice (choice)
          • Dt Date [1..1]DatePeriodSearch1Choice (choice)
        • ResTp Residence Type [0..1]ResidenceType1Code

          Specifies the type of residence where the party has its permanent home or principal establishment.

        • LckSts Lock Status [0..1]PartyLockStatus1

          Specifies whether the party is locked or not, and the reason for this status, when required.

          • VldFr Valid From [0..1]ISODate
          • Sts Status [1..1]LockStatus1Code
          • LckRsn Lock Reason [0..*]Max35Text
      • RtrCrit Return Criteria [0..1]PartyDataReturnCriteria2

        Defines the expected party reference data to be returned.

        • OpngDt Opening Date [0..1]RequestedIndicator

          Indicates whether the opening date of the party is requested.

        • ClsgDt Closing Date [0..1]RequestedIndicator

          Indicates whether the closing date of the party is requested.

        • Tp Type [0..1]RequestedIndicator

          Indicates whether the type is requested.

        • PtyId Party Identification [0..1]RequestedIndicator

          Indicates whether the unique identification to unambiguously identify the party within the system is requested.

        • RspnsblPtyId Responsible Party Identification [0..1]RequestedIndicator

          Indicates whether the responsible party who initially created the party reference data is requested.

        • RstrctnId Restriction Identification [0..1]RequestedIndicator

          Indicates whether the identification of the restriction is requested.

        • RstrctdOnDt Restricted On Date [0..1]RequestedIndicator

          Indicates whether the date at which a restriction for party has been issued is requested.

        • Nm Name [0..1]RequestedIndicator

          Indicates whether the name for the party is requested.

        • ShrtNm Short Name [0..1]RequestedIndicator

          Indicates whether the short name for the party is requested.

        • Adr Address [0..1]RequestedIndicator

          Indicates whether the address for the party is requested.

        • TechAdr Technical Address [0..1]RequestedIndicator

          Indicates whether the technical addresses for the party are requested.

        • CtctDtls Contact Details [0..1]RequestedIndicator

          Indicates whether the party contact details are requested.

        • ResTp Residence Type [0..1]RequestedIndicator

          Indicates whether the residence type is requested.

        • LckSts Lock Status [0..1]RequestedIndicator

          Indicates whether the lock status is requested.

        • MktSpcfcAttr Market Specific Attribute [0..1]RequestedIndicator

          Indicates whether the market specific attributes for the party are requested.

      • 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.015 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.015

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.015 questions

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