ReversalOfTransferInConfirmationV05

sese.008.001.05

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.

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
%% ReversalOfTransferInConfirmationV05 recursion level 0 with max 0
ReversalOfTransferInConfirmationV05 *-- "1..1" MessageIdentification1 : MessageIdentification
ReversalOfTransferInConfirmationV05 *-- "0..1" References15 : References
ReversalOfTransferInConfirmationV05 *-- "1..1" IReversal4Choice : Reversal
ReversalOfTransferInConfirmationV05 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
ReversalOfTransferInConfirmationV05 *-- "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

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
%% References15 recursion level 0 with max 1
References15 *-- "0..1" AdditionalReference2 : PoolReference
References15 *-- "0..1" AdditionalReference2 : PreviousReference
References15 *-- "0..1" AdditionalReference2 : RelatedReference
%% 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
  

References15 members

Reversal building block

Choice between reversal by reference or by reversal details. Choice between reversal by reference or by reversal details. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IReversal4Choice recursion level 0 with max 1
  

Reversal4Choice members

MarketPracticeVersion building block

Identifies the market practice to which the message conforms. Identifies the implementation and version. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MarketPracticeVersion1 recursion level 0 with max 1
class MarketPracticeVersion1{
    Name IsoMax35Text
    Date IsoISOYearMonth
    Number IsoMax35Text
}
  

MarketPracticeVersion1 members

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ReversalOfTransferInConfirmationV05 --|> IOuterRecord : Implements
    ReversalOfTransferInConfirmationV05Document --|> IOuterDocument~ReversalOfTransferInConfirmationV05~ : Implements
    class IOuterDocument~ReversalOfTransferInConfirmationV05~ {
        ReversalOfTransferInConfirmationV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ReversalOfTransferInConfirmationV05Document *-- ReversalOfTransferInConfirmationV05 : 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.05">
    <RvslOfTrfInConf>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <Rvsl>
            <!-- Reversal inner content -->
        </Rvsl>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
        <CpyDtls>
            <!-- CopyDetails inner content -->
        </CpyDtls>
    </RvslOfTrfInConf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="__b7YQRXfEeOocOqSQt5Jbw"
  nextVersions="_EicmoT58EeSIqOPJHpnleA"
  previousVersion="_kT5aARgCEeKqWJINzXcn5g"
  name="ReversalOfTransferInConfirmationV05"
  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;"
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="RvslOfTrfInConf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="__b7YQxXfEeOocOqSQt5Jbw"
    nextVersions="_Eicmoz58EeSIqOPJHpnleA"
    previousVersion="_kT5aCxgCEeKqWJINzXcn5g"
    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="__b7YRRXfEeOocOqSQt5Jbw"
    nextVersions="_EicmpT58EeSIqOPJHpnleA"
    previousVersion="_kT5aDxgCEeKqWJINzXcn5g"
    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="0"
    xmlTag="Refs"
    complexType="_LJFy4RX0EeOBE-jZfcm4KQ" />
  <messageBuildingBlock
    xmi:id="__b7YRxXfEeOocOqSQt5Jbw"
    nextVersions="_Eicmpz58EeSIqOPJHpnleA"
    previousVersion="_sM_NpRg4EeK-_89we2b-bA"
    name="Reversal"
    definition="Choice between reversal by reference or by reversal details."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rvsl"
    complexType="_PslE0RX3EeOBE-jZfcm4KQ" />
  <messageBuildingBlock
    xmi:id="_eDNL0Rw8EeOIveEnnb_1-A"
    nextVersions="_EicmqT58EeSIqOPJHpnleA"
    name="MarketPracticeVersion"
    definition="Identifies the market practice to which the message conforms."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MktPrctcVrsn"
    complexType="_FaNY0RUVEeOIaq8KyCdIDQ" />
  <messageBuildingBlock
    xmi:id="__b7YSRXfEeOocOqSQt5Jbw"
    nextVersions="_Eicmqz58EeSIqOPJHpnleA"
    previousVersion="_kT5aGxgCEeKqWJINzXcn5g"
    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="05" />
</messageDefinition>

ISO Building Blocks

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