sese.004 Reversal Of Transfer Out Confirmation

What sese.004 is for

sese.004 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.

sese.004 message structure

The building blocks of sese.004.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]
  • RvslOfTrfOutConf ReversalOfTransferOutConfirmation [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.

    • RvslRefs Reversal References [1..*]TransferReference16

      Reference of the transfer confirmation to be reversed.

      • TrfRef Transfer Reference [1..1]Max35Text

        Unique and unambiguous identifier for the transfer instruction for which the confirmation reversal 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
      • TrfConfRef Transfer Confirmation Reference [0..1]Max35Text

        Unique and unambiguous identifier for the transfer execution for which the confirmation reversal is sent, as assigned by the confirming party.

      • 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 reversal as assigned by the confirming party.

      • RvslRsn Reversal Reason [0..1]Max35Text

        Reason for the reversal of confirmation.

    • 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.004 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

Related securities settlement messages

• sese.001Transfer Out Instruction
• sese.002Transfer Out Cancellation Request
• sese.003Transfer Out Confirmation
• sese.005Transfer In Instruction
• sese.006Transfer In Cancellation Request
• sese.007Transfer In Confirmation
• sese.008Reversal Of Transfer In Confirmation
• sese.009Request For Transfer Status Report
• sese.010Transfer Cancellation Status Report
• sese.011Transfer Instruction Status Report

sese.004 questions

What is the latest version of sese.004?

The latest version in the ISO 20022 e-Repository release of 24 April 2025 is sese.004.001.09.

What is the root element of sese.004?

The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:sese.004.001.09, and its message element is RvslOfTrfOutConf (ReversalOfTransferOutConfirmation).

Is there an MT equivalent of sese.004?

No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.