Iso20022

RequestForTransferStatusReportV02

sese.009.001.02

Scope An instructing party, eg, an investment manager or its authorised representative, sends the RequestForTransferStatusReport to the executing party, eg, a transfer agent to request the status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either:

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
%% RequestForTransferStatusReportV02 recursion level 0 with max 0
RequestForTransferStatusReportV02 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForTransferStatusReportV02 *-- "1..1" MessageAndBusinessReference6 : RequestDetails
RequestForTransferStatusReportV02 *-- "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

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

RequestDetails building block

Information to identify the transfer for which the status is requested. . Information about the message reference of the message for which the status is requested and the business reference of the transfer instruction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageAndBusinessReference6 recursion level 0 with max 1
class MessageAndBusinessReference6{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    ClientReference IsoMax35Text
    CancellationReference IsoMax35Text
}
MessageAndBusinessReference6 *-- "0..1" AdditionalReference3 : PreviousReference
MessageAndBusinessReference6 *-- "0..1" AdditionalReference3 : OtherReference
MessageAndBusinessReference6 *-- "0..1" InvestmentAccount22 : InvestmentAccountDetails
%% AdditionalReference3 recursion level 1 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% AdditionalReference3 recursion level 1 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% InvestmentAccount22 recursion level 1 with max 1
class InvestmentAccount22{
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
    SecuritiesForm FormOfSecurity1Code
    DematerialisedIndicator IsoYesNoIndicator
    IncomePreference IncomePreference1Code
    BeneficiaryCertificationCompletion BeneficiaryCertificationCompletion1Code
}
InvestmentAccount22 *-- "0..0" IPartyIdentification2Choice : OwnerIdentification
InvestmentAccount22 *-- "1..1" AccountIdentification1 : AccountIdentification
InvestmentAccount22 *-- "0..0" Intermediary11 : IntermediaryInformation
InvestmentAccount22 *-- "0..1" IPartyIdentification2Choice : SafekeepingPlace
InvestmentAccount22 *-- "0..1" IPartyIdentification2Choice : AccountServicer

MessageAndBusinessReference6 members

Member name Description Data Type / Multiplicity
PreviousReference Reference to a linked message that was previously sent. AdditionalReference3 - Optional 0..1
OtherReference Reference to a linked message sent in a proprietary way or the reference of a system. AdditionalReference3 - Optional 0..1
MasterReference Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together. IsoMax35Text - Optional 0..1
TransferReference Unique and unambiguous identification of a transfer, as assigned by the instructing party. IsoMax35Text - Required 1..1
ClientReference Unique and unambiguous investor’s identification of a transfer. This reference can typically be used in a hub scenario to give the reference of the transfer as assigned by the underlying client. IsoMax35Text - Optional 0..1
CancellationReference Unique and unambiguous identifier for a transfer cancellation, as assigned by the instructing party. IsoMax35Text - Optional 0..1
InvestmentAccountDetails Investment account information of the transfer message for which the status is requested. InvestmentAccount22 - Optional 0..1

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

Member name Description Data Type / Multiplicity
PlaceAndName Name qualifying the information provided in the Text field, and place where this information should be inserted. IsoMax350Text - Required 1..1
Text Text of the extension. IsoMax350Text - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RequestForTransferStatusReportV02 --|> IOuterRecord : Implements
    RequestForTransferStatusReportV02Document --|> IOuterDocument~RequestForTransferStatusReportV02~ : Implements
    class IOuterDocument~RequestForTransferStatusReportV02~ {
        RequestForTransferStatusReportV02 Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForTransferStatusReportV02Document *-- RequestForTransferStatusReportV02 : 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.009.001.02">
    <ReqForTrfStsRptV02>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </ReqForTrfStsRptV02>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_oGN9ZdE5Ed-BzquC8wXy7w_2033838549"
  nextVersions="__iaEofpbEeCPwaG9zjUPNQ"
  previousVersion="_nnEjSNE5Ed-BzquC8wXy7w_-788060154"
  name="RequestForTransferStatusReportV02"
  definition="Scope&#xD;&#xA;An instructing party, eg, an investment manager or its authorised representative, sends the RequestForTransferStatusReport to the executing party, eg, a transfer agent to request the status of a previously instructed transfer.&#xD;&#xA;Usage&#xD;&#xA;The RequestForTransferStatusReport is used to request either:&#xD;&#xA;- the status of one or several transfer instructions or,&#xD;&#xA;- the status of one or several transfer cancellation instructions."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="ReqForTrfStsRptV02"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_oGN9ZtE5Ed-BzquC8wXy7w_1731455646"
    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="_oGN9Z9E5Ed-BzquC8wXy7w_2033838559"
    name="RequestDetails"
    definition="Information to identify the transfer for which the status is requested.&#xA;."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_Sww1ctp-Ed-ak6NoX_4Aeg_2114109590" />
  <messageBuildingBlock
    xmi:id="_oGN9aNE5Ed-BzquC8wXy7w_240300067"
    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="009"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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