Iso20022

RequestForTransferStatusReportV05

sese.009.001.05

Scope An instructing party, for example, an investment manager or its authorised representative, sends the RequestForTransferStatusReport to the executing party, for example, 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
%% RequestForTransferStatusReportV05 recursion level 0 with max 0
RequestForTransferStatusReportV05 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForTransferStatusReportV05 *-- "1..1" MessageAndBusinessReference8 : RequestDetails
RequestForTransferStatusReportV05 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
RequestForTransferStatusReportV05 *-- "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
%% MessageAndBusinessReference8 recursion level 0 with max 1
class MessageAndBusinessReference8{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    CancellationReference IsoMax35Text
}
MessageAndBusinessReference8 *-- "0..1" IReferences48Choice : Reference
MessageAndBusinessReference8 *-- "0..1" AdditionalReference7 : ClientReference
MessageAndBusinessReference8 *-- "0..1" InvestmentAccount57 : InvestmentAccountDetails
%% IReferences48Choice recursion level 1 with max 1
%% AdditionalReference7 recursion level 1 with max 1
class AdditionalReference7{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference7 *-- "0..1" IPartyIdentification97Choice : ReferenceIssuer
%% InvestmentAccount57 recursion level 1 with max 1
class InvestmentAccount57{
    AccountIdentification IsoMax35Text
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
    SecuritiesForm FormOfSecurity1Code
    DematerialisedIndicator IsoYesNoIndicator
    IncomePreference IncomePreference2Code
    BeneficiaryCertificationCompletion BeneficiaryCertificationCompletion1Code
}
InvestmentAccount57 *-- "0..0" IPartyIdentification70Choice : OwnerIdentification
InvestmentAccount57 *-- "0..0" Intermediary35 : IntermediaryInformation
InvestmentAccount57 *-- "0..1" ISafekeepingPlaceFormat8Choice : SafekeepingPlace
InvestmentAccount57 *-- "0..1" IPartyIdentification70Choice : AccountServicer
InvestmentAccount57 *-- "0..1" SubAccount5 : SubAccountDetails

MessageAndBusinessReference8 members

Member name Description Data Type / Multiplicity
Reference Reference to the message or communication that was previously sent. IReferences48Choice - 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. AdditionalReference7 - 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. InvestmentAccount57 - 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

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

classDiagram
    class IOuterRecord
    RequestForTransferStatusReportV05 --|> IOuterRecord : Implements
    RequestForTransferStatusReportV05Document --|> IOuterDocument~RequestForTransferStatusReportV05~ : Implements
    class IOuterDocument~RequestForTransferStatusReportV05~ {
        RequestForTransferStatusReportV05 Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForTransferStatusReportV05Document *-- RequestForTransferStatusReportV05 : 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.05">
    <ReqForTrfStsRpt>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </ReqForTrfStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_H02-IR8OEeWpZde3LQh6dg"
  nextVersions="_UWPwMYZMEeemXK0UETsSiA"
  previousVersion="_uTTqcRXfEeOocOqSQt5Jbw"
  name="RequestForTransferStatusReportV05"
  definition="Scope&#xD;&#xA;An instructing party, for example, an investment manager or its authorised representative, sends the RequestForTransferStatusReport to the executing party, for example, 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="ReqForTrfStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_H02-Ix8OEeWpZde3LQh6dg"
    nextVersions="_UWPwM4ZMEeemXK0UETsSiA"
    previousVersion="_uTTqcxXfEeOocOqSQt5Jbw"
    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="_H02-JR8OEeWpZde3LQh6dg"
    nextVersions="_UWPwNYZMEeemXK0UETsSiA"
    previousVersion="_uTTqdRXfEeOocOqSQt5Jbw"
    name="RequestDetails"
    definition="Information to identify the transfer for which the status is requested.&#xA;."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_mE8WeyR9EeWWV-wpfEW00A" />
  <messageBuildingBlock
    xmi:id="_H02-Jx8OEeWpZde3LQh6dg"
    nextVersions="_UWPwN4ZMEeemXK0UETsSiA"
    previousVersion="_6usDYRw9EeOIveEnnb_1-A"
    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="_H02-KR8OEeWpZde3LQh6dg"
    nextVersions="_UWPwOYZMEeemXK0UETsSiA"
    previousVersion="_uTTqdxXfEeOocOqSQt5Jbw"
    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="05" />
</messageDefinition>

ISO Building Blocks

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