RequestForTransferStatusReportV07

sese.009.001.07

Scope The RequestForTransferStatusReport 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 status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either:

• the status of one or several transfer instructions or,
• the status of one or several transfer cancellation instructions.

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
%% RequestForTransferStatusReportV07 recursion level 0 with max 0
RequestForTransferStatusReportV07 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForTransferStatusReportV07 *-- "1..1" MessageAndBusinessReference12 : RequestDetails
RequestForTransferStatusReportV07 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
RequestForTransferStatusReportV07 *-- "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 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

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
%% MessageAndBusinessReference12 recursion level 0 with max 1
class MessageAndBusinessReference12{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    CancellationReference IsoMax35Text
}
MessageAndBusinessReference12 *-- "0..1" IReferences68Choice : Reference
MessageAndBusinessReference12 *-- "0..1" AdditionalReference10 : ClientReference
MessageAndBusinessReference12 *-- "0..1" InvestmentAccount72 : InvestmentAccountDetails
%% IReferences68Choice recursion level 1 with max 1
%% AdditionalReference10 recursion level 1 with max 1
class AdditionalReference10{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% InvestmentAccount72 recursion level 1 with max 1
class InvestmentAccount72{
    AccountIdentification IsoMax35Text
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
    SecuritiesForm FormOfSecurity1Code
    DematerialisedIndicator IsoYesNoIndicator
    IncomePreference IncomePreference2Code
    BeneficiaryCertificationCompletion BeneficiaryCertificationCompletion1Code
}
InvestmentAccount72 *-- "0..0" PartyIdentification139 : OwnerIdentification
InvestmentAccount72 *-- "0..0" Intermediary43 : IntermediaryInformation
InvestmentAccount72 *-- "0..1" ISafekeepingPlaceFormat28Choice : SafekeepingPlace
InvestmentAccount72 *-- "0..1" PartyIdentification139 : AccountServicer
InvestmentAccount72 *-- "0..1" SubAccount5 : SubAccountDetails
  

MessageAndBusinessReference12 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

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

classDiagram
    class IOuterRecord
    RequestForTransferStatusReportV07 --|> IOuterRecord : Implements
    RequestForTransferStatusReportV07Document --|> IOuterDocument~RequestForTransferStatusReportV07~ : Implements
    class IOuterDocument~RequestForTransferStatusReportV07~ {
        RequestForTransferStatusReportV07 Message
     }
  

Document wrapper for serialization

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

classDiagram
    RequestForTransferStatusReportV07Document *-- RequestForTransferStatusReportV07 : 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.07">
    <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="_fnYVIZDhEem7fvtoGpNpow"
  nextVersions="_Ix6uEdvdEeqxGfKJubfhIw"
  previousVersion="_UWPwMYZMEeemXK0UETsSiA"
  name="RequestForTransferStatusReportV07"
  definition="Scope&#xD;&#xA;The RequestForTransferStatusReport 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 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="_wFQdsE2rEeG_I4xRYCA_7g _qCumkAFwEeu2__1EbNXzuA"
  xmlTag="ReqForTrfStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_fnYVI5DhEem7fvtoGpNpow"
    nextVersions="_Ix7VIdvdEeqxGfKJubfhIw"
    previousVersion="_UWPwM4ZMEeemXK0UETsSiA"
    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="_fnYVJZDhEem7fvtoGpNpow"
    nextVersions="_Ix7VI9vdEeqxGfKJubfhIw"
    previousVersion="_UWPwNYZMEeemXK0UETsSiA"
    name="RequestDetails"
    definition="Information to identify the transfer for which the status is requested."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_43AM8ZGqEem-9Y6mq5ZH3Q" />
  <messageBuildingBlock
    xmi:id="_fnYVJ5DhEem7fvtoGpNpow"
    nextVersions="_Ix7VJdvdEeqxGfKJubfhIw"
    previousVersion="_UWPwN4ZMEeemXK0UETsSiA"
    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="_fnYVKZDhEem7fvtoGpNpow"
    nextVersions="_Ix7VJ9vdEeqxGfKJubfhIw"
    previousVersion="_UWPwOYZMEeemXK0UETsSiA"
    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="07" />
</messageDefinition>

ISO Building Blocks

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