ReversalOfTransferInConfirmationV03

sese.008.001.03

Scope An executing party, for example, a transfer agent, sends the ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either:

the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or,
all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. It is also possible to request a reversal of a TransferInConfirmation by quoting its message reference (MessageIdentification) in PreviousReference.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% ReversalOfTransferInConfirmationV03 recursion level 0 with max 0
ReversalOfTransferInConfirmationV03 *-- "1..1" MessageIdentification1 : MessageIdentification
ReversalOfTransferInConfirmationV03 *-- "1..1" References11 : References
ReversalOfTransferInConfirmationV03 *-- "0..1" TransferReference2 : ReversalByReference
ReversalOfTransferInConfirmationV03 *-- "0..1" TransferIn6 : ReversalByTransferInConfirmationDetails
ReversalOfTransferInConfirmationV03 *-- "0..1" CopyInformation2 : CopyDetails

Now, we will zero-in one-by-one on each of these building blocks.

MessageIdentification building block

Reference that uniquely identifies a message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}

MessageIdentification1 members

Member name	Description	Data Type / Multiplicity
Identification	Identification of the message.	IsoMax35Text - Required 1..1
CreationDateTime	Date of creation of the message.	IsoISODateTime - Required 1..1

References building block

Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together. Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% References11 recursion level 0 with max 1
References11 *-- "0..1" AdditionalReference2 : PoolReference
References11 *-- "0..1" AdditionalReference2 : PreviousReference
References11 *-- "0..1" AdditionalReference2 : RelatedReference
References11 *-- "0..1" AdditionalReference2 : CounterpartyReference
%% AdditionalReference2 recursion level 1 with max 1
class AdditionalReference2{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference2 *-- "0..1" IPartyIdentification1Choice : ReferenceIssuer
%% AdditionalReference2 recursion level 1 with max 1
class AdditionalReference2{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference2 *-- "0..1" IPartyIdentification1Choice : ReferenceIssuer
%% AdditionalReference2 recursion level 1 with max 1
class AdditionalReference2{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference2 *-- "0..1" IPartyIdentification1Choice : ReferenceIssuer
%% AdditionalReference2 recursion level 1 with max 1
class AdditionalReference2{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference2 *-- "0..1" IPartyIdentification1Choice : ReferenceIssuer

References11 members

Member name	Description	Data Type / Multiplicity
PoolReference	Collective reference identifying a set of messages.	AdditionalReference2 - Optional 0..1
PreviousReference	Reference of the linked message that was previously sent.	AdditionalReference2 - Optional 0..1
RelatedReference	Reference to a linked message that was previously received.	AdditionalReference2 - Optional 0..1
CounterpartyReference	Unambiguous identification of the transfer allocated by the counterparty.	AdditionalReference2 - Optional 0..1

ReversalByReference building block

Reference of the transfer in confirmation to be reversed. Reference of a transfer and of a transfer confirmation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransferReference2 recursion level 0 with max 1
class TransferReference2{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    ClientReference IsoMax35Text
    TransferConfirmationReference IsoMax35Text
}

TransferReference2 members

Member name	Description	Data Type / Multiplicity
MasterReference	Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.	IsoMax35Text - Optional 0..1
TransferReference	Unique and unambiguous identifier for a transfer instruction, as assigned by the instructing party.	IsoMax35Text - Optional 0..1
ClientReference	Unique and unambiguous investor’s identification of a transfer. This reference can typically be used in a hub scenario to give the reference of the transfer as assigned by the underlying client.	IsoMax35Text - Optional 0..1
TransferConfirmationReference	Unique and unambiguous identifier for a transfer execution, as assigned by a confirming party.	IsoMax35Text - Optional 0..1

ReversalByTransferInConfirmationDetails building block

Copy of the transfer in confirmation to reverse. Information about the confirmation of a transfer in transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransferIn6 recursion level 0 with max 1
TransferIn6 *-- "1..0" Transfer17 : TransferDetails
TransferIn6 *-- "1..1" InvestmentAccount22 : AccountDetails
TransferIn6 *-- "1..1" DeliverInformation7 : SettlementDetails
TransferIn6 *-- "0..0" Extension1 : Extension
%% Transfer17 recursion level 1 with max 1
class Transfer17{
    HoldingsPlanType HoldingsPlanType1Code
    AveragePrice IsoActiveOrHistoricCurrencyAnd13DecimalAmount
    OwnAccountTransferIndicator IsoYesNoIndicator
    NonStandardSettlementInformation IsoMax350Text
}
Transfer17 *-- "1..1" IDateAndDateTimeChoice : EffectiveTransferDate
Transfer17 *-- "0..1" IDateAndDateTimeChoice : TradeDate
Transfer17 *-- "1..1" FinancialInstrument13 : FinancialInstrumentDetails
Transfer17 *-- "1..1" FinancialInstrumentQuantity1 : TotalUnitsNumber
Transfer17 *-- "0..0" Unit3 : UnitsDetails
%% InvestmentAccount22 recursion level 1 with max 1
class InvestmentAccount22{
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
    SecuritiesForm FormOfSecurity1Code
    DematerialisedIndicator IsoYesNoIndicator
    IncomePreference IncomePreference1Code
    BeneficiaryCertificationCompletion BeneficiaryCertificationCompletion1Code
}
InvestmentAccount22 *-- "0..0" IPartyIdentification2Choice : OwnerIdentification
InvestmentAccount22 *-- "1..1" AccountIdentification1 : AccountIdentification
InvestmentAccount22 *-- "0..0" Intermediary11 : IntermediaryInformation
InvestmentAccount22 *-- "0..1" IPartyIdentification2Choice : SafekeepingPlace
InvestmentAccount22 *-- "0..1" IPartyIdentification2Choice : AccountServicer
%% DeliverInformation7 recursion level 1 with max 1
class DeliverInformation7{
    SettlementAmount IsoActiveCurrencyAndAmount
    StampDuty StampDutyType2Code
    NetAmount IsoActiveCurrencyAndAmount
    PhysicalTransfer PhysicalTransferType1Code
}
DeliverInformation7 *-- "0..1" IDateAndDateTimeChoice : EffectiveSettlementDate
DeliverInformation7 *-- "0..0" Charge20 : ChargeDetails
DeliverInformation7 *-- "0..0" Commission12 : CommissionDetails
DeliverInformation7 *-- "0..0" Tax15 : TaxDetails
DeliverInformation7 *-- "1..1" DeliveringPartiesAndAccount8 : SettlementPartiesDetails
DeliverInformation7 *-- "0..1" DeliveryParameters4 : PhysicalTransferDetails
%% Extension1 recursion level 1 with max 1
class Extension1{
    PlaceAndName IsoMax350Text
    Text IsoMax350Text
}

TransferIn6 members

Member name	Description	Data Type / Multiplicity
TransferDetails	General information related to the transfer of a financial instrument.	Transfer17 - Unknown 1..0
AccountDetails	Information related to the account into which the financial instrument was received.	InvestmentAccount22 - Required 1..1
SettlementDetails	Information related to the delivering side of the transfer.	DeliverInformation7 - Required 1..1
Extension	Additional information that can not be captured in the structured fields and/or any other specific block.	Extension1 - Unknown 0..0

CopyDetails building block

Information provided when the message is a copy of a previous message. Information provided when the message is a copy of a previous message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CopyInformation2 recursion level 0 with max 1
class CopyInformation2{
    CopyIndicator IsoYesNoIndicator
}
CopyInformation2 *-- "0..1" BICIdentification1 : OriginalReceiver
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}

CopyInformation2 members

Member name	Description	Data Type / Multiplicity
CopyIndicator	Indicates whether the message is a copy.	IsoYesNoIndicator - Required 1..1
OriginalReceiver	Original receiver of the message, if this message is a copy.	BICIdentification1 - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the ReversalOfTransferInConfirmationV03 implementation follows a specific implementaiton pattern. First of all, ReversalOfTransferInConfirmationV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ReversalOfTransferInConfirmationV03Document implements IOuterDocument. Because ReversalOfTransferInConfirmationV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ReversalOfTransferInConfirmationV03.

classDiagram
    class IOuterRecord
    ReversalOfTransferInConfirmationV03 --|> IOuterRecord : Implements
    ReversalOfTransferInConfirmationV03Document --|> IOuterDocument~ReversalOfTransferInConfirmationV03~ : Implements
    class IOuterDocument~ReversalOfTransferInConfirmationV03~ {
        ReversalOfTransferInConfirmationV03 Message
     }

Document wrapper for serialization

The only real purpose ReversalOfTransferInConfirmationV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.008.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ReversalOfTransferInConfirmationV03.ToDocument() method. The returned ReversalOfTransferInConfirmationV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    ReversalOfTransferInConfirmationV03Document *-- ReversalOfTransferInConfirmationV03 : Document

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:sese.008.001.03">
    <RvslOfTrfInConf>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <RvslByRef>
            <!-- ReversalByReference inner content -->
        </RvslByRef>
        <RvslByTrfInConfDtls>
            <!-- ReversalByTransferInConfirmationDetails inner content -->
        </RvslByTrfInConfDtls>
        <CpyDtls>
            <!-- CopyDetails inner content -->
        </CpyDtls>
    </RvslOfTrfInConf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9cSssfpbEeCPwaG9zjUPNQ"
  nextVersions="_kT5aARgCEeKqWJINzXcn5g"
  previousVersion="_pHChMNE5Ed-BzquC8wXy7w_-604499550"
  name="ReversalOfTransferInConfirmationV03"
  definition="Scope&#xD;&#xA;An executing party, for example, a transfer agent, sends the ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message.&#xD;&#xA;Usage&#xD;&#xA;The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation.&#xD;&#xA;There are two ways to specify the reversal of the transfer in confirmation. Either:&#xD;&#xA;- the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or,&#xD;&#xA;- all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended.&#xD;&#xA;The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference.&#xD;&#xA;The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.&#xD;&#xA;It is also possible to request a reversal of a TransferInConfirmation by quoting its message reference (MessageIdentification) in PreviousReference."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="RvslOfTrfInConf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <xors
    xmi:id="_9cSstfpbEeCPwaG9zjUPNQ"
    name="Operation1"
    registrationStatus="Provisionally Registered"
    impactedMessageBuildingBlocks="_9cSszfpbEeCPwaG9zjUPNQ _9cSs0fpbEeCPwaG9zjUPNQ" />
  <messageBuildingBlock
    xmi:id="_9cSsvfpbEeCPwaG9zjUPNQ"
    name="MessageIdentification"
    definition="Reference that uniquely identifies a message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_tbZjH_r3EeCJc7cZxzE2fg"
    name="References"
    definition="Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="Refs"
    complexType="_Vv7Tofr0EeCJc7cZxzE2fg" />
  <messageBuildingBlock
    xmi:id="_9cSszfpbEeCPwaG9zjUPNQ"
    name="ReversalByReference"
    definition="Reference of the transfer in confirmation to be reversed."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RvslByRef"
    complexType="_SwKYhdp-Ed-ak6NoX_4Aeg_-1697995766" />
  <messageBuildingBlock
    xmi:id="_9cSs0fpbEeCPwaG9zjUPNQ"
    name="ReversalByTransferInConfirmationDetails"
    definition="Copy of the transfer in confirmation to reverse."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RvslByTrfInConfDtls"
    complexType="_j9WUd_r3EeCJc7cZxzE2fg" />
  <messageBuildingBlock
    xmi:id="_9cSs1fpbEeCPwaG9zjUPNQ"
    name="CopyDetails"
    definition="Information provided when the message is a copy of a previous message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CpyDtls"
    complexType="_Q7Vk4tp-Ed-ak6NoX_4Aeg_-1918092012" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="008"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.