ZagTrader

sese: Securities Settlement

sese.010 Transfer Cancellation Status Report

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

sese.010 is the ISO 20022 TransferCancellationStatusReport message in the Securities Settlement business area (sese). The latest version is sese.010.001.07, and 7 versions are in the repository.

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

In use: published in the current ISO 20022 catalogue.

What sese.010 is for

The TransferCancellationStatusReport message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction.

The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request.

The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

One of the following statuses can be reported:

- the transfer cancellation is accepted, or,

- the transfer cancellation has been sent to the next party, or,

- the transfer cancellation is complete and the reason for the status,

- the transfer cancellation pending and the reason for the status,

- the transfer cancellation is rejected and the reason for the status.

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

sese.010 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.010.001.07latestRegisteredLatest version set
sese.010.001.06RegisteredPrevious version set
sese.010.001.05RegisteredArchive
sese.010.001.04RegisteredArchive
sese.010.001.03RegisteredArchive
sese.010.001.02RegisteredArchive
sese.010.001.01RegisteredArchive

sese.010 message structure

The building blocks of sese.010.001.07 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]
    • TrfCxlStsRpt TransferCancellationStatusReport [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.

      • CtrPtyRef Counterparty Reference [0..1]AdditionalReference10

        Unambiguous identification of the transfer allocated by the counterparty.

        • Ref Reference [1..1]Max35Text

          Reference issued by a party to identify an instruction, transaction or a message.

        • RefIssr Reference Issuer [0..1]PartyIdentification139

          Issuer of the reference.

          • Pty Party [1..1]PartyIdentification125Choice (choice)
          • LEI LEI [0..1]LEIIdentifier
        • MsgNm Message Name [0..1]Max35Text

          Name of the message.

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

        Reference to the message or communication that was previously received.

        • RltdRef Related Reference [1..2]AdditionalReference10

          Reference to a linked message that was previously received.

          • Ref Reference [1..1]Max35Text
          • RefIssr Reference Issuer [0..1]PartyIdentification139
          • MsgNm Message Name [0..1]Max35Text
        • OthrRef Other Reference [1..2]AdditionalReference10

          Reference to a linked proprietary message or reference of a system that was previously received.

          • Ref Reference [1..1]Max35Text
          • RefIssr Reference Issuer [0..1]PartyIdentification139
          • MsgNm Message Name [0..1]Max35Text
      • StsRpt Status Report [1..1]CancellationStatusAndReason5

        Status of the transfer cancellation instruction.

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

        • Sts Status [1..1]Status31Choice (choice)

          Status of the transfer cancellation.

          • Sts Status [1..1]TransferCancellationStatus3
          • Rjctd Rejected [1..1]RejectionReason33
          • Cmplt Complete [1..1]CancelledCompleteReason1
          • Pdg Pending [1..1]TransferCancellationPendingStatus1
        • StsInitr Status Initiator [0..1]PartyIdentification139

          Party that initiates the status.

          • 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.010 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.010 questions

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