ReversalOfTransferInConfirmationV07

sese.008.001.07

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
%% ReversalOfTransferInConfirmationV07 recursion level 0 with max 0
class ReversalOfTransferInConfirmationV07{
    Function TransferInFunction2Code
}
ReversalOfTransferInConfirmationV07 *-- "1..1" MessageIdentification1 : MessageIdentification
ReversalOfTransferInConfirmationV07 *-- "0..1" References20 : References
ReversalOfTransferInConfirmationV07 *-- "1..1" IReversal7Choice : Reversal
ReversalOfTransferInConfirmationV07 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
ReversalOfTransferInConfirmationV07 *-- "0..1" CopyInformation4 : 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
%% References20 recursion level 0 with max 1
References20 *-- "0..1" AdditionalReference6 : PoolReference
References20 *-- "0..1" AdditionalReference6 : PreviousReference
References20 *-- "0..1" AdditionalReference6 : RelatedReference
%% AdditionalReference6 recursion level 1 with max 1
class AdditionalReference6{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference6 *-- "0..1" IPartyIdentification90Choice : ReferenceIssuer
%% AdditionalReference6 recursion level 1 with max 1
class AdditionalReference6{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference6 *-- "0..1" IPartyIdentification90Choice : ReferenceIssuer
%% AdditionalReference6 recursion level 1 with max 1
class AdditionalReference6{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference6 *-- "0..1" IPartyIdentification90Choice : ReferenceIssuer
  

References20 members

Function building block

Function of the transfer-in, that is, whether the message is used as a reversal of a previously sent confirmation or as a reversal of a previously sent advice. The absence of Function indicates the message is a reversal of a previously sent confirmation. Specifies the function of the transfer in confirmation. For comparison, see the ISO20022 official specification This message is declared as TransferInFunction2Code in the ISO specification. In our implementation, it is represented in source code as TransferInFunction2Code. Due to global using directives, it is treated as a System.String by the compiler and runtime.

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
%% IReversal7Choice recursion level 0 with max 1
  

Reversal7Choice 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
%% CopyInformation4 recursion level 0 with max 1
class CopyInformation4{
    CopyIndicator IsoYesNoIndicator
    OriginalReceiver IsoAnyBICIdentifier
}
  

CopyInformation4 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ReversalOfTransferInConfirmationV07 --|> IOuterRecord : Implements
    ReversalOfTransferInConfirmationV07Document --|> IOuterDocument~ReversalOfTransferInConfirmationV07~ : Implements
    class IOuterDocument~ReversalOfTransferInConfirmationV07~ {
        ReversalOfTransferInConfirmationV07 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ReversalOfTransferInConfirmationV07Document *-- ReversalOfTransferInConfirmationV07 : 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.07">
    <RvslOfTrfInConf>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <Fctn>
            <!-- Function inner content -->
        </Fctn>
        <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="_BL8wcR8OEeWpZde3LQh6dg"
  nextVersions="_2G_jUYZLEeemXK0UETsSiA"
  previousVersion="_EicmoT58EeSIqOPJHpnleA"
  name="ReversalOfTransferInConfirmationV07"
  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">
  <constraint
    xmi:id="_ZYRmsCVSEeWI0orciOKunQ"
    name="EffectiveTradeDateRule"
    definition="If Function is ADVI (Advice) or Function is not present, and Reversal/TransferInConfirmationDetails is present, then EffectiveTransferDate must be present."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_BL8wcx8OEeWpZde3LQh6dg"
    nextVersions="_2G_jVYZLEeemXK0UETsSiA"
    previousVersion="_Eicmoz58EeSIqOPJHpnleA"
    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="_BL8wdR8OEeWpZde3LQh6dg"
    previousVersion="_EicmpT58EeSIqOPJHpnleA"
    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="_Sh39oSP0EeWQjryFgN2ITg" />
  <messageBuildingBlock
    xmi:id="_iHBxcSVQEeWI0orciOKunQ"
    nextVersions="_2G_jWYZLEeemXK0UETsSiA"
    name="Function"
    definition="Function of the transfer-in, that is, whether the message is used as a reversal of a previously sent confirmation or as a reversal of a previously sent advice. The absence of Function indicates the message is a reversal of a previously sent confirmation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Fctn"
    simpleType="_p7s5kCVOEeWI0orciOKunQ" />
  <messageBuildingBlock
    xmi:id="_BL8wdx8OEeWpZde3LQh6dg"
    previousVersion="_Eicmpz58EeSIqOPJHpnleA"
    name="Reversal"
    definition="Choice between reversal by reference or by reversal details."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rvsl"
    complexType="_23jIcCPvEeWQjryFgN2ITg" />
  <messageBuildingBlock
    xmi:id="_BL8weR8OEeWpZde3LQh6dg"
    nextVersions="_2G_jXYZLEeemXK0UETsSiA"
    previousVersion="_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="_BL8wex8OEeWpZde3LQh6dg"
    nextVersions="_2G_jX4ZLEeemXK0UETsSiA"
    previousVersion="_Eicmqz58EeSIqOPJHpnleA"
    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="_7VUJ8degEeSA_uUacqhl1Q" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="008"
    flavour="001"
    version="07" />
</messageDefinition>

ISO Building Blocks

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