ZagTrader

sese: Securities Settlement

sese.002 Transfer Out Cancellation Request

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

sese.002 is the ISO 20022 TransferOutCancellationRequest message in the Securities Settlement business area (sese). The latest version is sese.002.001.09, and 9 versions are in the repository.

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

In use: published in the current ISO 20022 catalogue.

What sese.002 is for

The TransferOutCancellationRequest message 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 cancellation of a previously sent transfer out instruction.

The TransferOutCancellationRequest message is used to request the cancellation of one or more transfer out instructions.

There is no amendment, but a cancellation and re-instruct policy.

To request the cancellation of one or more transfer out instructions, the transfer reference of the transfer, as specified in the original TransferOutInstruction message, is specified in the transfer reference element.

The message identification of the original TransferOutInstruction message may also be quoted in PreviousReference but this is not recommended.

The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation.

The rejection or acceptance of a TransferOutCancellationRequest is made using a TransferCancellationStatusReport message.

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

sese.002 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.002.001.09latestRegisteredLatest version set
sese.002.001.08RegisteredPrevious version set
sese.002.001.07RegisteredArchive
sese.002.001.06RegisteredArchive
sese.002.001.05RegisteredArchive
sese.002.001.04RegisteredArchive
sese.002.001.03RegisteredArchive
sese.002.001.02RegisteredArchive
sese.002.001.01RegisteredArchive

sese.002 message structure

The building blocks of sese.002.001.09 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]
    • TrfOutCxlReq TransferOutCancellationRequest [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.

      • PoolRef Pool Reference [0..1]AdditionalReference11

        Collective reference identifying a set of messages.

        • Ref Reference [1..1]Max35Text

          Reference identifying a set of messages.

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

      • PrvsRef Previous Reference [0..1]AdditionalReference10

        Reference to a linked message that was previously sent.

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

      • RltdRef Related Reference [0..1]AdditionalReference10

        Reference to a linked message that was previously received.

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

      • MstrRef Master Reference [0..1]Max35Text

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

      • TrfRefs Transfer References [1..*]TransferReference15

        Reference of the transfer to be cancelled.

        • TrfRef Transfer Reference [1..1]Max35Text

          Unique and unambiguous identifier for the transfer instruction for which the cancellation request is sent, 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
        • CtrPtyRef Counterparty Reference [0..1]AdditionalReference10

          Unambiguous identification of the transfer allocated by the counterparty.

          • 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 the transfer cancellation, as assigned by the instructing party.

        • CxlRsn Cancellation Reason [0..1]Max35Text

          Reason for the cancellation.

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

      • CpyDtls Copy Details [0..1]CopyInformation5

        Information provided when the message is a copy of a previous message.

        • CpyInd Copy Indicator [1..1]YesNoIndicator

          Indicates whether the message is a copy.

        • OrgnlRcvr Original Receiver [0..1]AnyBICDec2014Identifier

          Original receiver of the message, if this message is a copy.

Have a sese.002 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.002 questions

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