ZagTrader

reda: Reference Data

reda.050 Account Link Maintenance Request

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

reda.050 is the ISO 20022 AccountLinkMaintenanceRequest message in the Reference Data business area (reda). The latest version is reda.050.001.01.

Message
AccountLinkMaintenanceRequest
Latest version
reda.050.001.01
Submitting organisation
4CBs and Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What reda.050 is for

The AccountLinkMaintenanceRequest message is sent by the instructing party to the executing/servicing party to request for the maintenance of an account link in their system.

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

- Central Securities Depositories (CSD) who would like to publish account link 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 account link coverage of the executing/servicing party. The instructing party needs this account link to be maintained 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.050 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.050.001.01latestRegisteredLatest version set

reda.050 message structure

The building blocks of reda.050.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]
    • AcctLkMntncReq AccountLinkMaintenanceRequest [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.

      • AcctLkId Account Link Identification [1..1]AccountLink8

        Provides a unique and unambiguous identification for the account link.

        • SctiesAcct Securities Account [0..1]SecuritiesAccount19

          Account to or from which a securities entry is made.

          • Id Identification [1..1]Max35Text
          • Tp Type [0..1]GenericIdentification30
          • Nm Name [0..1]Max70Text
        • BlckChainAdrOrWllt Block Chain Address Or Wallet [0..1]BlockChainAddressWallet3

          Blockchain address or wallet where digital assets are maintained.

          • Id Identification [1..1]Max140Text
          • Tp Type [0..1]GenericIdentification30
          • Nm Name [0..1]Max70Text
        • CshAcct Cash Account [1..1]CashAccount38

          Account to or from which a cash entry is made.

          • Id Identification [1..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • VldFr Valid From [1..1]DateAndDateTime2Choice (choice)

          Defines the date since when the securities account is linked to the cash account.

          • Dt Date [1..1]ISODate
          • DtTm Date Time [1..1]ISODateTime
      • Upd Update [1..1]AccountLinkUpdate2

        Provides data that needs to be maintained.

        • VldTo Valid To [1..1]DateAndDateTime2Choice (choice)

          Defines the date until when the securities account is linked to the cash account.

          • Dt Date [1..1]ISODate
          • DtTm Date Time [1..1]ISODateTime
      • 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.050 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.050

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

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