PortfolioTransferCancellationRequestV09

sese.014.001.09

Scope The PortfolioTransferCancellationRequest message is sent by, 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 PortfolioTransferInstruction message. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of a portfolio transfer instruction. There is no amendment, but a cancellation and re-instruct policy. To request the cancellation of a portfolio transfer instruction, the transfer reference of the portfolio transfer, as specified in the original PortfolioTransferInstruction message, is specified in the transfer reference element. The message identification of the original PortfolioTransferInstruction 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 PortfolioTransferCancellationRequest is made using an 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
%% PortfolioTransferCancellationRequestV09 recursion level 0 with max 0
class PortfolioTransferCancellationRequestV09{
    MasterReference IsoMax35Text
}
PortfolioTransferCancellationRequestV09 *-- "1..1" MessageIdentification1 : MessageReference
PortfolioTransferCancellationRequestV09 *-- "0..1" AdditionalReference11 : PoolReference
PortfolioTransferCancellationRequestV09 *-- "0..1" AdditionalReference10 : PreviousReference
PortfolioTransferCancellationRequestV09 *-- "0..1" AdditionalReference10 : RelatedReference
PortfolioTransferCancellationRequestV09 *-- "1..1" TransferReference14 : TransferReferences
PortfolioTransferCancellationRequestV09 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
  

Now, we will zero-in one-by-one on each of these building blocks.

MessageReference 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
%% 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

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

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

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 portfolio transfer instruction to be cancelled. Reference of a transfer and of a transfer cancellation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransferReference14 recursion level 0 with max 1
class TransferReference14{
    TransferReference IsoMax35Text
    TransferConfirmationReference IsoMax35Text
    CancellationReference IsoMax35Text
    CancellationReason IsoMax35Text
}
TransferReference14 *-- "0..1" AdditionalReference10 : ClientReference
TransferReference14 *-- "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
  

TransferReference14 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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    PortfolioTransferCancellationRequestV09 --|> IOuterRecord : Implements
    PortfolioTransferCancellationRequestV09Document --|> IOuterDocument~PortfolioTransferCancellationRequestV09~ : Implements
    class IOuterDocument~PortfolioTransferCancellationRequestV09~ {
        PortfolioTransferCancellationRequestV09 Message
     }
  

Document wrapper for serialization

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

classDiagram
    PortfolioTransferCancellationRequestV09Document *-- PortfolioTransferCancellationRequestV09 : 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.014.001.09">
    <PrtflTrfCxlReq>
        <MsgRef>
            <!-- MessageReference inner content -->
        </MsgRef>
        <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>
    </PrtflTrfCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_OSc-8XhFEeij0vbhRaNJcw"
  previousVersion="_gblKUYZMEeemXK0UETsSiA"
  name="PortfolioTransferCancellationRequestV09"
  definition="Scope&#xD;&#xA;The PortfolioTransferCancellationRequest message is sent by, 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 PortfolioTransferInstruction message.&#xD;&#xA;Usage&#xD;&#xA;The PortfolioTransferCancellationRequest message is used to request the cancellation of a portfolio transfer instruction.&#xD;&#xA;There is no amendment, but a cancellation and re-instruct policy.&#xD;&#xA;To request the cancellation of a portfolio transfer instruction, the transfer reference of the portfolio transfer, as specified in the original PortfolioTransferInstruction message, is specified in the transfer reference element.&#xD;&#xA;The message identification of the original PortfolioTransferInstruction 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 PortfolioTransferCancellationRequest is made using an TransferCancellationStatusReport message."
  registrationStatus="Registered"
  messageSet="_hijK0WiLEeOuqdLlpUIWBw _qCumkAFwEeu2__1EbNXzuA"
  xmlTag="PrtflTrfCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_OSc-83hFEeij0vbhRaNJcw"
    previousVersion="_gblKU4ZMEeemXK0UETsSiA"
    name="MessageReference"
    definition="Reference that uniquely identifies the message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_OSc-9XhFEeij0vbhRaNJcw"
    previousVersion="_gblKVYZMEeemXK0UETsSiA"
    name="PoolReference"
    definition="Collective reference identifying a set of messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PoolRef"
    complexType="_daTFkWpUEeipaMTLlhaKMQ" />
  <messageBuildingBlock
    xmi:id="_OSc-93hFEeij0vbhRaNJcw"
    previousVersion="_gblKV4ZMEeemXK0UETsSiA"
    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="_OSc--XhFEeij0vbhRaNJcw"
    previousVersion="_gblKWYZMEeemXK0UETsSiA"
    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="_OSc--3hFEeij0vbhRaNJcw"
    previousVersion="_Oh4CAYi2EeefvMoXmllHqg"
    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="_OSc-_XhFEeij0vbhRaNJcw"
    previousVersion="_ru7yEYi2EeefvMoXmllHqg"
    name="TransferReferences"
    definition="Reference of the portfolio transfer instruction to be cancelled."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TrfRefs"
    complexType="_YPWs8XhFEeij0vbhRaNJcw" />
  <messageBuildingBlock
    xmi:id="_OSc-_3hFEeij0vbhRaNJcw"
    previousVersion="_gblKXYZMEeemXK0UETsSiA"
    name="MarketPracticeVersion"
    definition="Identifies the market practice to which the message conforms."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MktPrctcVrsn"
    complexType="_FaNY0RUVEeOIaq8KyCdIDQ" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="014"
    flavour="001"
    version="09" />
</messageDefinition>

ISO Building Blocks

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