ZagTrader

admi: Administration

admi.006 Resend Request

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

admi.006 is the ISO 20022 ResendRequest message in the Administration business area (admi). The latest version is admi.006.001.01.

Message
ResendRequest
Latest version
admi.006.001.01
Submitting organisation
T2S
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What admi.006 is for

A system member or any parties authorised by them send a ResendRequest message to the Central System (such as the T2S platform). The purpose of this request is, that the requesting party wants to receive the “original” message once again. This might be caused through technical problems on the receiving side (message could not be received or processed or is missing in the message sequencing) or for archiving purposes.

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

admi.006 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
admi.006.001.01latestRegisteredLatest version set

admi.006 message structure

The building blocks of admi.006.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]
    • RsndReq ResendRequest [1..1]
      • MsgHdr Message Header [1..1]MessageHeader7

        Set of elements to identify the resend 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]RequestType4Choice (choice)

          Specific actions to be executed through the request.

          • PmtCtrl Payment Control [1..1]ExternalPaymentControlRequestType1Code
          • Enqry Enquiry [1..1]ExternalEnquiryRequestType1Code
          • Prtry Proprietary [1..1]GenericIdentification1
        • OrgnlBizQry Original Business Query [0..1]OriginalBusinessQuery1

          Unique identification of the original query message.

          • MsgId Message Identification [1..1]Max35Text
          • MsgNmId Message Name Identification [0..1]Max35Text
          • CreDtTm Creation Date Time [0..1]ISODateTime
        • QryNm Query Name [0..1]Max35Text

          Recalls the criteria (search and return criteria) defined in a preceding query.

      • RsndSchCrit Resend Search Criteria [1..*]ResendSearchCriteria2

        Defines the criteria to unambiguously identify the information to be resent.

        • BizDt Business Date [0..1]ISODate

          Date of the business day of the requested messages the resend function is used for.

        • SeqNb Sequence Number [0..1]Max35Text

          Independent counter for message sequence, which is available once per party technical address.

        • SeqRg Sequence Range [0..1]SequenceRange1Choice (choice)

          Independent counter for a range of message sequences, which are available once per party technical address.

          • FrSeq From Sequence [1..1]Max35Text
          • ToSeq To Sequence [1..1]Max35Text
          • FrToSeq From To Sequence [1..*]SequenceRange1
          • EQSeq Equal Sequence [1..*]Max35Text
          • NEQSeq Not Equal Sequence [1..*]Max35Text
        • OrgnlMsgNmId Original Message Name Identification [0..1]Max35Text

          Unambiguously identifies the original bsiness message, which was delivered by the business sender.

        • FileRef File Reference [0..1]Max35Text

          String of characters that uniquely identifies the file, which was delivered by the sender.

        • Rcpt Recipient [1..1]PartyIdentification136

          Unique identification to unambiguously identify the recipient of the report message.

          • Id Identification [1..1]PartyIdentification120Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
      • 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 admi.006 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 admi.006

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

admi.006 questions

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