ReversalOfTransferInConfirmationV08

sese.008.001.08

Scope The ReversalOfTransferInConfirmation message is sent by the executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent transfer in confirmation. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent transfer in confirmation. To request the reversal of a transfer in confirmation, the transfer reference of the transfer in instruction, as specified in the original TransferInInstruction message, is specified in the transfer reference element. The executing party’s reference for the execution of the transfer may also be specified in the TransferConfirmationReference element. The message identification of the original TransferInConfirmation message may also be quoted in PreviousReference but this is not recommended.

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
%% ReversalOfTransferInConfirmationV08 recursion level 0 with max 0
class ReversalOfTransferInConfirmationV08{
    MasterReference IsoMax35Text
    Function TransferInFunction2Code
}
ReversalOfTransferInConfirmationV08 *-- "1..1" MessageIdentification1 : MessageIdentification
ReversalOfTransferInConfirmationV08 *-- "0..1" AdditionalReference9 : PoolReference
ReversalOfTransferInConfirmationV08 *-- "0..1" AdditionalReference8 : PreviousReference
ReversalOfTransferInConfirmationV08 *-- "0..1" AdditionalReference8 : RelatedReference
ReversalOfTransferInConfirmationV08 *-- "1..1" TransferReference12 : Reference
ReversalOfTransferInConfirmationV08 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
ReversalOfTransferInConfirmationV08 *-- "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 the 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

PoolReference building block

Collective reference identifying a set of messages. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference9 recursion level 0 with max 1
class AdditionalReference9{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference9 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference9 members

PreviousReference building block

Reference to a linked message that was previously sent. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference8 recursion level 0 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference8 members

RelatedReference building block

Reference to a linked message that was previously received. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference8 recursion level 0 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference8 members

MasterReference building block

Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.

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.

Reference building block

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

classDiagram
   direction tb
%% TransferReference12 recursion level 0 with max 1
class TransferReference12{
    TransferReference IsoMax35Text
    TransferConfirmationReference IsoMax35Text
    CancellationReference IsoMax35Text
    ReversalReason IsoMax35Text
}
TransferReference12 *-- "0..1" AdditionalReference8 : ClientReference
TransferReference12 *-- "0..1" AdditionalReference8 : CounterpartyReference
%% AdditionalReference8 recursion level 1 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% AdditionalReference8 recursion level 1 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
  

TransferReference12 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 ReversalOfTransferInConfirmationV08 implementation follows a specific implementaiton pattern. First of all, ReversalOfTransferInConfirmationV08 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ReversalOfTransferInConfirmationV08Document implements IOuterDocument. Because ReversalOfTransferInConfirmationV08 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ReversalOfTransferInConfirmationV08.

classDiagram
    class IOuterRecord
    ReversalOfTransferInConfirmationV08 --|> IOuterRecord : Implements
    ReversalOfTransferInConfirmationV08Document --|> IOuterDocument~ReversalOfTransferInConfirmationV08~ : Implements
    class IOuterDocument~ReversalOfTransferInConfirmationV08~ {
        ReversalOfTransferInConfirmationV08 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ReversalOfTransferInConfirmationV08Document *-- ReversalOfTransferInConfirmationV08 : 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.08">
    <RvslOfTrfInConf>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <PoolRef>
            <!-- PoolReference inner content -->
        </PoolRef>
        <PrvsRef>
            <!-- PreviousReference inner content -->
        </PrvsRef>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <MstrRef>
            <!-- MasterReference inner content -->
        </MstrRef>
        <Fctn>
            <!-- Function inner content -->
        </Fctn>
        <Ref>
            <!-- Reference inner content -->
        </Ref>
        <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="_2G_jUYZLEeemXK0UETsSiA"
  nextVersions="_dPLusZDhEem7fvtoGpNpow"
  previousVersion="_BL8wcR8OEeWpZde3LQh6dg"
  name="ReversalOfTransferInConfirmationV08"
  definition="Scope&#xD;&#xA;The ReversalOfTransferInConfirmation message is sent by the executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent transfer in confirmation.&#xD;&#xA;Usage&#xD;&#xA;The ReversalOfTransferInConfirmation message is used to reverse a previously sent transfer in confirmation.&#xD;&#xA;To request the reversal of a transfer in confirmation, the transfer reference of the transfer in instruction, as specified in the original TransferInInstruction message, is specified in the transfer reference element. The executing party’s reference for the execution of the transfer may also be specified in the TransferConfirmationReference element.&#xD;&#xA;The message identification of the original TransferInConfirmation message may also be quoted in PreviousReference but this is not recommended."
  registrationStatus="Registered"
  messageSet="_wFQdsE2rEeG_I4xRYCA_7g"
  xmlTag="RvslOfTrfInConf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_2G_jVYZLEeemXK0UETsSiA"
    nextVersions="_dPLus5DhEem7fvtoGpNpow"
    previousVersion="_BL8wcx8OEeWpZde3LQh6dg"
    name="MessageIdentification"
    definition="Reference that uniquely identifies the message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_m_nYs4i1EeefvMoXmllHqg"
    nextVersions="_dPLutZDhEem7fvtoGpNpow"
    name="PoolReference"
    definition="Collective reference identifying a set of messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PoolRef"
    complexType="_N4g3EXETEea2e4bzJ8TyEw" />
  <messageBuildingBlock
    xmi:id="_m_nYtIi1EeefvMoXmllHqg"
    nextVersions="_dPLut5DhEem7fvtoGpNpow"
    name="PreviousReference"
    definition="Reference to a linked message that was previously sent."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrvsRef"
    complexType="_udnPoTbsEead9bDRE_1DAQ" />
  <messageBuildingBlock
    xmi:id="_m_n_wIi1EeefvMoXmllHqg"
    nextVersions="_dPLuuZDhEem7fvtoGpNpow"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_udnPoTbsEead9bDRE_1DAQ" />
  <messageBuildingBlock
    xmi:id="_yjJGQYi1EeefvMoXmllHqg"
    nextVersions="_dPLuu5DhEem7fvtoGpNpow"
    name="MasterReference"
    definition="Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MstrRef"
    simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
  <messageBuildingBlock
    xmi:id="_2G_jWYZLEeemXK0UETsSiA"
    nextVersions="_dPLuvZDhEem7fvtoGpNpow"
    previousVersion="_iHBxcSVQEeWI0orciOKunQ"
    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="_wTn6sYi1EeefvMoXmllHqg"
    nextVersions="_dPLuv5DhEem7fvtoGpNpow"
    name="Reference"
    definition="Reference of the transfer confirmation to be reversed."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Ref"
    complexType="_1LZXYYi0EeefvMoXmllHqg" />
  <messageBuildingBlock
    xmi:id="_2G_jXYZLEeemXK0UETsSiA"
    nextVersions="_dPLuwZDhEem7fvtoGpNpow"
    previousVersion="_BL8weR8OEeWpZde3LQh6dg"
    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="_2G_jX4ZLEeemXK0UETsSiA"
    nextVersions="_dPLuw5DhEem7fvtoGpNpow"
    previousVersion="_BL8wex8OEeWpZde3LQh6dg"
    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="08" />
</messageDefinition>

ISO Building Blocks

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