TransferOutCancellationRequestV09

sese.002.001.09

Scope The TransferOutCancellationRequest message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to request the cancellation of a previously sent transfer out instruction. Usage The TransferOutCancellationRequest message is used to request the cancellation of one or more transfer out instructions. There is no amendment, but a cancellation and re-instruct policy. To request the cancellation of one or more transfer out instructions, the transfer reference of the transfer, as specified in the original TransferOutInstruction message, is specified in the transfer reference element. The message identification of the original TransferOutInstruction message may also be quoted in PreviousReference but this is not recommended. The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation. The rejection or acceptance of a TransferOutCancellationRequest is made using a TransferCancellationStatusReport message.

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
%% TransferOutCancellationRequestV09 recursion level 0 with max 0
class TransferOutCancellationRequestV09{
    MasterReference IsoMax35Text
}
TransferOutCancellationRequestV09 *-- "1..1" MessageIdentification1 : MessageIdentification
TransferOutCancellationRequestV09 *-- "0..1" AdditionalReference11 : PoolReference
TransferOutCancellationRequestV09 *-- "0..1" AdditionalReference10 : PreviousReference
TransferOutCancellationRequestV09 *-- "0..1" AdditionalReference10 : RelatedReference
TransferOutCancellationRequestV09 *-- "1..1" TransferReference15 : TransferReferences
TransferOutCancellationRequestV09 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
TransferOutCancellationRequestV09 *-- "0..1" CopyInformation5 : 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

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

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
%% AdditionalReference11 recursion level 0 with max 1
class AdditionalReference11{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference11 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% PartyIdentification139 recursion level 1 with max 1
class PartyIdentification139{
    LEI IsoLEIIdentifier
}
PartyIdentification139 *-- "1..1" IPartyIdentification125Choice : Party
  

AdditionalReference11 members

Member name Description Data Type / Multiplicity
Reference Reference identifying a set of messages. IsoMax35Text - Required 1..1
ReferenceIssuer Issuer of the reference. PartyIdentification139 - Optional 0..1
MessageName Name of the message. IsoMax35Text - Optional 0..1

PreviousReference building block

Reference to a linked message that was previously sent. Reference and reference issuer. For comparison, see the ISO20022 official specification

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

AdditionalReference10 members

Member name Description Data Type / Multiplicity
Reference Reference issued by a party to identify an instruction, transaction or a message. IsoMax35Text - Required 1..1
ReferenceIssuer Issuer of the reference. PartyIdentification139 - Optional 0..1
MessageName Name of the message. IsoMax35Text - Optional 0..1

RelatedReference building block

Reference to a linked message that was previously received. Reference and reference issuer. For comparison, see the ISO20022 official specification

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

AdditionalReference10 members

Member name Description Data Type / Multiplicity
Reference Reference issued by a party to identify an instruction, transaction or a message. IsoMax35Text - Required 1..1
ReferenceIssuer Issuer of the reference. PartyIdentification139 - Optional 0..1
MessageName Name of the message. IsoMax35Text - Optional 0..1

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.

TransferReferences building block

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

classDiagram
   direction tb
%% TransferReference15 recursion level 0 with max 1
class TransferReference15{
    TransferReference IsoMax35Text
    CancellationReference IsoMax35Text
    CancellationReason IsoMax35Text
}
TransferReference15 *-- "0..1" AdditionalReference10 : ClientReference
TransferReference15 *-- "0..1" AdditionalReference10 : CounterpartyReference
%% AdditionalReference10 recursion level 1 with max 1
class AdditionalReference10{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% AdditionalReference10 recursion level 1 with max 1
class AdditionalReference10{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
  

TransferReference15 members

Member name Description Data Type / Multiplicity
TransferReference Unique and unambiguous identifier for the transfer instruction for which the cancellation request is sent, as assigned by the instructing party. IsoMax35Text - Required 1..1
ClientReference Unique and unambiguous investor’s identification of the transfer. This reference can typically be used in a hub scenario to give the reference of the transfer as assigned by the underlying client. AdditionalReference10 - Optional 0..1
CounterpartyReference Unambiguous identification of the transfer allocated by the counterparty. AdditionalReference10 - Optional 0..1
CancellationReference Unique and unambiguous identifier for the transfer cancellation, as assigned by the instructing party. IsoMax35Text - Optional 0..1
CancellationReason Reason for the cancellation. IsoMax35Text - Optional 0..1

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

Member name Description Data Type / Multiplicity
Name Market practice, for example, “UKTRANSFERS”, “FINDELSLT”. IsoMax35Text - Required 1..1
Date Year and month, for example, 2013-06. IsoISOYearMonth - Optional 0..1
Number Version of the market practice. IsoMax35Text - Optional 0..1

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

CopyInformation5 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. IsoAnyBICDec2014Identifier - Optional 0..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    TransferOutCancellationRequestV09 --|> IOuterRecord : Implements
    TransferOutCancellationRequestV09Document --|> IOuterDocument~TransferOutCancellationRequestV09~ : Implements
    class IOuterDocument~TransferOutCancellationRequestV09~ {
        TransferOutCancellationRequestV09 Message
     }
  

Document wrapper for serialization

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

classDiagram
    TransferOutCancellationRequestV09Document *-- TransferOutCancellationRequestV09 : 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.002.001.09">
    <TrfOutCxlReq>
        <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>
        <TrfRefs>
            <!-- TransferReferences inner content -->
        </TrfRefs>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
        <CpyDtls>
            <!-- CopyDetails inner content -->
        </CpyDtls>
    </TrfOutCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_LctLkZDhEem7fvtoGpNpow"
  previousVersion="_k4R0kYZLEeemXK0UETsSiA"
  name="TransferOutCancellationRequestV09"
  definition="Scope&#xD;&#xA;The TransferOutCancellationRequest message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to request the cancellation of a previously sent transfer out instruction.&#xD;&#xA;Usage&#xD;&#xA;The TransferOutCancellationRequest message is used to request the cancellation of one or more transfer out instructions.&#xD;&#xA;There is no amendment, but a cancellation and re-instruct policy.&#xD;&#xA;To request the cancellation of one or more transfer out instructions, the transfer reference of the transfer, as specified in the original TransferOutInstruction message, is specified in the transfer reference element.&#xD;&#xA;The message identification of the original TransferOutInstruction message may also be quoted in PreviousReference but this is not recommended.&#xD;&#xA;The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation.&#xD;&#xA;The rejection or acceptance of a TransferOutCancellationRequest is made using a TransferCancellationStatusReport message."
  registrationStatus="Registered"
  messageSet="_hijK0WiLEeOuqdLlpUIWBw _qCumkAFwEeu2__1EbNXzuA"
  xmlTag="TrfOutCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_LctLk5DhEem7fvtoGpNpow"
    previousVersion="_k4R0k4ZLEeemXK0UETsSiA"
    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="_LctLlZDhEem7fvtoGpNpow"
    previousVersion="_vWzNcYiyEeefvMoXmllHqg"
    name="PoolReference"
    definition="Collective reference identifying a set of messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PoolRef"
    complexType="_daTFkWpUEeipaMTLlhaKMQ" />
  <messageBuildingBlock
    xmi:id="_LctLl5DhEem7fvtoGpNpow"
    previousVersion="_zjWGYYiyEeefvMoXmllHqg"
    name="PreviousReference"
    definition="Reference to a linked message that was previously sent."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrvsRef"
    complexType="_ZBypsWpTEeipaMTLlhaKMQ" />
  <messageBuildingBlock
    xmi:id="_LctLmZDhEem7fvtoGpNpow"
    previousVersion="_4sH-EYiyEeefvMoXmllHqg"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_ZBypsWpTEeipaMTLlhaKMQ" />
  <messageBuildingBlock
    xmi:id="_LctLm5DhEem7fvtoGpNpow"
    previousVersion="_FzFNQYizEeefvMoXmllHqg"
    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="_LctLnZDhEem7fvtoGpNpow"
    previousVersion="_jg5WcYiyEeefvMoXmllHqg"
    name="TransferReferences"
    definition="Reference of the transfer to be cancelled."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="TrfRefs"
    complexType="_6hDwcZGpEem-9Y6mq5ZH3Q" />
  <messageBuildingBlock
    xmi:id="_LctLn5DhEem7fvtoGpNpow"
    previousVersion="_k4R0mYZLEeemXK0UETsSiA"
    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="_LctLoZDhEem7fvtoGpNpow"
    previousVersion="_k4R0m4ZLEeemXK0UETsSiA"
    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="_y6HYAZELEem-9Y6mq5ZH3Q" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="002"
    flavour="001"
    version="09" />
</messageDefinition>

ISO Building Blocks

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