TransferCancellationStatusReportV02

sese.010.001.02

Scope An executing party, eg, a transfer agent, sends the TransferCancellationStatusReport message to the instructing party, eg, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction. Usage The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request. The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported:

• the transfer cancellation is accepted, or,
• the transfer cancellation has been sent to the next party, or,
• the transfer cancellation is complete and the reason for the status,
• the transfer cancellation pending and the reason for the status,
• the transfer cancellation is rejected and the reason for the status.

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
%% TransferCancellationStatusReportV02 recursion level 0 with max 0
TransferCancellationStatusReportV02 *-- "1..1" MessageIdentification1 : MessageIdentification
TransferCancellationStatusReportV02 *-- "0..2" AdditionalReference3 : RelatedReference
TransferCancellationStatusReportV02 *-- "0..2" AdditionalReference3 : OtherReference
TransferCancellationStatusReportV02 *-- "1..1" CancellationStatusAndReason2 : StatusReport
TransferCancellationStatusReportV02 *-- "0..1" Extension1 : Extension
  

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

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
%% AdditionalReference3 recursion level 0 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% IPartyIdentification2Choice recursion level 1 with max 1
  

AdditionalReference3 members

OtherReference building block

Reference to the linked message sent in a proprietary way or the reference of a system. 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
%% AdditionalReference3 recursion level 0 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% IPartyIdentification2Choice recursion level 1 with max 1
  

AdditionalReference3 members

StatusReport building block

Status of the transfer cancellation instruction. Status of a transfer cancellation instruction and the reason for the status. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CancellationStatusAndReason2 recursion level 0 with max 1
class CancellationStatusAndReason2{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    ClientReference IsoMax35Text
    CancellationReference IsoMax35Text
}
CancellationStatusAndReason2 *-- "1..1" TransferCancellationStatus2 : Status
CancellationStatusAndReason2 *-- "1..1" TransferCancellationRejectedStatus1 : Rejected
CancellationStatusAndReason2 *-- "1..1" TransferCancellationCompleteStatusAndReason1 : Complete
CancellationStatusAndReason2 *-- "1..1" TransferCancellationPendingStatus1 : Pending
CancellationStatusAndReason2 *-- "0..1" IPartyIdentification2Choice : StatusInitiator
%% TransferCancellationStatus2 recursion level 1 with max 1
class TransferCancellationStatus2{
    Status CancellationStatus2Code
    Reason IsoMax350Text
}
%% TransferCancellationRejectedStatus1 recursion level 1 with max 1
class TransferCancellationRejectedStatus1{
    Reason CancellationRejectedReason1Code
    ExtendedReason IsoExtended350Code
}
TransferCancellationRejectedStatus1 *-- "1..10" GenericIdentification1 : DataSourceScheme
%% TransferCancellationCompleteStatusAndReason1 recursion level 1 with max 1
class TransferCancellationCompleteStatusAndReason1{
    Reason CancelledStatusReason1Code
    ExtendedReason IsoExtended350Code
}
TransferCancellationCompleteStatusAndReason1 *-- "1..1" GenericIdentification1 : DataSourceScheme
%% TransferCancellationPendingStatus1 recursion level 1 with max 1
class TransferCancellationPendingStatus1{
    Reason IsoMax350Text
}
%% IPartyIdentification2Choice recursion level 1 with max 1
  

CancellationStatusAndReason2 members

Extension building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Extension1 recursion level 0 with max 1
class Extension1{
    PlaceAndName IsoMax350Text
    Text IsoMax350Text
}
  

Extension1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    TransferCancellationStatusReportV02 --|> IOuterRecord : Implements
    TransferCancellationStatusReportV02Document --|> IOuterDocument~TransferCancellationStatusReportV02~ : Implements
    class IOuterDocument~TransferCancellationStatusReportV02~ {
        TransferCancellationStatusReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    TransferCancellationStatusReportV02Document *-- TransferCancellationStatusReportV02 : 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.010.001.02">
    <TrfCxlStsRptV02>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <OthrRef>
            <!-- OtherReference inner content -->
        </OthrRef>
        <StsRpt>
            <!-- StatusReport inner content -->
        </StsRpt>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </TrfCxlStsRptV02>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_HnZFINE6Ed-BzquC8wXy7w_1645958483"
  nextVersions="_By8j4fpcEeCPwaG9zjUPNQ"
  previousVersion="_HFtUYNE6Ed-BzquC8wXy7w_1729523466"
  name="TransferCancellationStatusReportV02"
  definition="Scope&#xD;&#xA;An executing party, eg, a transfer agent, sends the TransferCancellationStatusReport message to the instructing party, eg, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction.&#xD;&#xA;Usage&#xD;&#xA;The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request.&#xD;&#xA;The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference.&#xD;&#xA;The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference.&#xD;&#xA;One of the following statuses can be reported:&#xD;&#xA;- the transfer cancellation is accepted, or,&#xD;&#xA;- the transfer cancellation has been sent to the next party, or,&#xD;&#xA;- the transfer cancellation is complete and the reason for the status,&#xD;&#xA;- the transfer cancellation pending and the reason for the status,&#xD;&#xA;- the transfer cancellation is rejected and the reason for the status."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="TrfCxlStsRptV02"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_HnZFKdE6Ed-BzquC8wXy7w_-1635533964"
    name="OtherReferenceRule"
    definition="OtherReference should be used to reference a transfer cancellation request 'message' sent in a proprietary way or used for a system reference. If OtherReference is present, OtherReference/MessageName must contain 'fax' or 'phone' or 'email', etc."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_HniPEtE6Ed-BzquC8wXy7w_-1635533328"
    name="RelatedReferenceRule"
    definition="If RelatedReference/MessageName is present, it must contain 540 or 542 or must start with sese.002, sese.006 or sese.009 and the RelatedReference/Reference must contain the reference of a message in this list."
    registrationStatus="Provisionally Registered" />
  <xors
    xmi:id="_HnZFJtE6Ed-BzquC8wXy7w_1645958812"
    name="RelatedReferenceOrOtherReferenceRule"
    definition="Occurrences of either RelatedReference or OtherReference may be present, but not occurrences of both."
    registrationStatus="Provisionally Registered"
    impactedMessageBuildingBlocks="_HnZFItE6Ed-BzquC8wXy7w_1645958501 _HnZFI9E6Ed-BzquC8wXy7w_1645958519" />
  <messageBuildingBlock
    xmi:id="_HnZFIdE6Ed-BzquC8wXy7w_-2063886787"
    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="_HnZFItE6Ed-BzquC8wXy7w_1645958501"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_HnZFI9E6Ed-BzquC8wXy7w_1645958519"
    name="OtherReference"
    definition="Reference to the linked message sent in a proprietary way or the reference of a system."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="0"
    xmlTag="OthrRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_HnZFJNE6Ed-BzquC8wXy7w_-665648289"
    name="StatusReport"
    definition="Status of the transfer cancellation instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StsRpt"
    complexType="_SxzXTNp-Ed-ak6NoX_4Aeg_195934515" />
  <messageBuildingBlock
    xmi:id="_HnZFJdE6Ed-BzquC8wXy7w_97152090"
    name="Extension"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Xtnsn"
    complexType="_Q6vvCNp-Ed-ak6NoX_4Aeg_1503007069" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="010"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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