ZagTrader

sese: Securities Settlement

sese.009 Request For Transfer Status Report

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

sese.009 is the ISO 20022 RequestForTransferStatusReport message in the Securities Settlement business area (sese). The latest version is sese.009.001.08, and 8 versions are in the repository.

Message
RequestForTransferStatusReport
Latest version
sese.009.001.08
Submitting organisation
Not read from the catalogue
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What sese.009 is for

The RequestForTransferStatusReport is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent to request the status of a previously instructed transfer.

The RequestForTransferStatusReport may also be sent by any party in the transfer transaction to another party in the transfer transaction chain to request information relevant for the settlement of a transfer transaction.

The RequestForTransferStatusReport is used to request either:

- the status of one or several information requests or transfer instructions or,

- the status of one or several transfer cancellation instructions, or

- information relevant to one or more transfer instructions.

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

sese.009 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
sese.009.001.08latestRegisteredLatest version set
sese.009.001.07RegisteredPrevious version set
sese.009.001.06RegisteredArchive
sese.009.001.05RegisteredArchive
sese.009.001.04RegisteredArchive
sese.009.001.03RegisteredArchive
sese.009.001.02RegisteredArchive
sese.009.001.01RegisteredArchive

sese.009 message structure

The building blocks of sese.009.001.08 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]
    • ReqForTrfStsRpt RequestForTransferStatusReport [1..1]
      • MsgId Message Identification [1..1]MessageIdentification1

        Reference that uniquely identifies the message from a business application standpoint.

        • Id Identification [1..1]Max35Text

          Identification of the message.

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

          Date of creation of the message.

      • ReqDtls Request Details [1..*]MessageAndBusinessReference13

        Information to identify the transfer for which the status is requested.

        • Ref Reference [0..1]References68Choice (choice)

          Reference to the message or communication that was previously sent.

          • PrvsRef Previous Reference [1..1]AdditionalReference10
          • OthrRef Other Reference [1..1]AdditionalReference10
        • TpOfReq Type Of Request [0..1]TypeOfRequest1Choice (choice)

          Type of request required.

          • Cd Code [1..1]TypeOfRequest1Code
          • Prtry Proprietary [1..1]GenericIdentification36
        • MstrRef Master Reference [0..1]Max35Text

          Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party.

        • TrfRef Transfer Reference [1..1]Max35Text

          Unique and unambiguous identification of the transfer, as assigned by the instructing party.

        • ClntRef Client Reference [0..1]AdditionalReference10

          Unique and unambiguous investor's identification of the transfer.

          • Ref Reference [1..1]Max35Text
          • RefIssr Reference Issuer [0..1]PartyIdentification139
          • MsgNm Message Name [0..1]Max35Text
        • CxlRef Cancellation Reference [0..1]Max35Text

          Unique and unambiguous identifier for a transfer cancellation, as assigned by the instructing party.

        • Instrm Instrument [0..1]FinancialInstrument63Choice (choice)

          Identification of the asset.

          • Scty Security [1..1]FinancialInstrumentIdentification2
          • CshAsst Cash Asset [1..1]CashAsset3
          • OthrAsst Other Asset [1..1]OtherAsset2
        • InvstmtAcctDtls Investment Account Details [0..1]Account33

          Investment account information of the transfer for which the status or information is requested.

          • OwnrId Owner Identification [0..1]PartyIdentification132
          • AcctId Account Identification [0..1]Max35Text
          • AcctDsgnt Account Designation [0..1]Max35Text
          • AcctNm Account Name [0..1]Max35Text
          • Tp Type [0..1]GenericIdentification30
          • Svcr Servicer [0..1]PartyIdentification132
          • SubAcctDtls Sub Account Details [0..1]SubAccount5
        • IntrmyInf Intermediary Information [0..*]Intermediary48

          Identification of a related party or intermediary.

          • Id Identification [1..1]PartyIdentification132
          • Acct Account [0..1]Account34
          • Role Role [0..1]Role8Choice (choice)
          • CtctPrsn Contact Person [0..1]ContactIdentification2
        • QryInf Query Information [0..*]AdditionalInformation25

          Information about the query.

          • QryTp Query Type [0..1]GenericIdentification36
          • Qry Query [1..1]Max350Text
          • QryRsn Query Reason [0..1]Max350Text
          • RjctnRsn Rejection Reason [0..1]RejectedReason33Choice (choice)
        • ReqIssr Request Issuer [0..1]PartyIdentification139

          Party that issues the request message.

          • Pty Party [1..1]PartyIdentification125Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
        • ReqRcpt Request Recipient [0..1]PartyIdentification139

          Party that receives the request message.

          • Pty Party [1..1]PartyIdentification125Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
      • MktPrctcVrsn Market Practice Version [0..1]MarketPracticeVersion1

        Identifies the market practice to which the message conforms.

        • Nm Name [1..1]Max35Text

          Market practice, for example, “UKTRANSFERS”, “FINDELSLT”.

        • Dt Date [0..1]ISOYearMonth

          Year and month, for example, 2013-06.

        • Nb Number [0..1]Max35Text

          Version of the market practice.

      • Xtnsn Extension [0..*]Extension1

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

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

          Name qualifying the information provided in the Text field, and place where this information should be inserted.

        • Txt Text [1..1]Max350Text

          Text of the extension.

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

sese.009 questions

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