RequestForTransferStatusReportV08

sese.009.001.08

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. The RequestForTransferStatusReport may also be sent by any party in the transfer transaction to another party in the transfer transaction chain to request information relevant for the settlement of a transfer transaction. Usage The RequestForTransferStatusReport is used to request either:

• the status of one or several information requests or transfer instructions or,
• the status of one or several transfer cancellation instructions, or
• information relevant to one or more transfer 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
%% RequestForTransferStatusReportV08 recursion level 0 with max 0
RequestForTransferStatusReportV08 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForTransferStatusReportV08 *-- "1..1" MessageAndBusinessReference13 : RequestDetails
RequestForTransferStatusReportV08 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
RequestForTransferStatusReportV08 *-- "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
%% MessageAndBusinessReference13 recursion level 0 with max 1
class MessageAndBusinessReference13{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    CancellationReference IsoMax35Text
}
MessageAndBusinessReference13 *-- "0..1" IReferences68Choice : Reference
MessageAndBusinessReference13 *-- "0..1" ITypeOfRequest1Choice : TypeOfRequest
MessageAndBusinessReference13 *-- "0..1" AdditionalReference10 : ClientReference
MessageAndBusinessReference13 *-- "0..1" IFinancialInstrument63Choice : Instrument
MessageAndBusinessReference13 *-- "0..1" Account33 : InvestmentAccountDetails
MessageAndBusinessReference13 *-- "0..0" Intermediary48 : IntermediaryInformation
MessageAndBusinessReference13 *-- "0..0" AdditionalInformation25 : QueryInformation
MessageAndBusinessReference13 *-- "0..1" PartyIdentification139 : RequestIssuer
MessageAndBusinessReference13 *-- "0..1" PartyIdentification139 : RequestRecipient
%% IReferences68Choice recursion level 1 with max 1
%% ITypeOfRequest1Choice recursion level 1 with max 1
%% AdditionalReference10 recursion level 1 with max 1
class AdditionalReference10{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% IFinancialInstrument63Choice recursion level 1 with max 1
%% Account33 recursion level 1 with max 1
class Account33{
    AccountIdentification IsoMax35Text
    AccountDesignation IsoMax35Text
    AccountName IsoMax35Text
}
Account33 *-- "0..1" PartyIdentification132 : OwnerIdentification
Account33 *-- "0..1" GenericIdentification30 : Type
Account33 *-- "0..1" PartyIdentification132 : Servicer
Account33 *-- "0..1" SubAccount5 : SubAccountDetails
%% Intermediary48 recursion level 1 with max 1
Intermediary48 *-- "1..1" PartyIdentification132 : Identification
Intermediary48 *-- "0..1" Account34 : Account
Intermediary48 *-- "0..1" IRole8Choice : Role
Intermediary48 *-- "0..1" ContactIdentification2 : ContactPerson
%% AdditionalInformation25 recursion level 1 with max 1
class AdditionalInformation25{
    Query IsoMax350Text
    QueryReason IsoMax350Text
}
AdditionalInformation25 *-- "0..1" GenericIdentification36 : QueryType
AdditionalInformation25 *-- "0..1" IRejectedReason33Choice : RejectionReason
%% PartyIdentification139 recursion level 1 with max 1
class PartyIdentification139{
    LEI IsoLEIIdentifier
}
PartyIdentification139 *-- "1..1" IPartyIdentification125Choice : Party
%% PartyIdentification139 recursion level 1 with max 1
class PartyIdentification139{
    LEI IsoLEIIdentifier
}
PartyIdentification139 *-- "1..1" IPartyIdentification125Choice : Party
  

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

classDiagram
    class IOuterRecord
    RequestForTransferStatusReportV08 --|> IOuterRecord : Implements
    RequestForTransferStatusReportV08Document --|> IOuterDocument~RequestForTransferStatusReportV08~ : Implements
    class IOuterDocument~RequestForTransferStatusReportV08~ {
        RequestForTransferStatusReportV08 Message
     }
  

Document wrapper for serialization

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

classDiagram
    RequestForTransferStatusReportV08Document *-- RequestForTransferStatusReportV08 : 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.08">
    <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="_Ix6uEdvdEeqxGfKJubfhIw"
  previousVersion="_fnYVIZDhEem7fvtoGpNpow"
  name="RequestForTransferStatusReportV08"
  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;The RequestForTransferStatusReport may also be sent by any party in the transfer transaction to another party in the transfer transaction chain to request information relevant for the settlement of a transfer transaction.&#xD;&#xA;Usage&#xD;&#xA;The RequestForTransferStatusReport is used to request either:&#xD;&#xA;- the status of one or several information requests or transfer instructions or,&#xD;&#xA;- the status of one or several transfer cancellation instructions, or&#xD;&#xA;- information relevant to one or more transfer instructions."
  registrationStatus="Registered"
  messageSet="_hijK0WiLEeOuqdLlpUIWBw"
  xmlTag="ReqForTrfStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_Ix7VIdvdEeqxGfKJubfhIw"
    previousVersion="_fnYVI5DhEem7fvtoGpNpow"
    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="_Ix7VI9vdEeqxGfKJubfhIw"
    previousVersion="_fnYVJZDhEem7fvtoGpNpow"
    name="RequestDetails"
    definition="Information to identify the transfer for which the status is requested."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_STWoEdvdEeqxGfKJubfhIw" />
  <messageBuildingBlock
    xmi:id="_Ix7VJdvdEeqxGfKJubfhIw"
    previousVersion="_fnYVJ5DhEem7fvtoGpNpow"
    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="_Ix7VJ9vdEeqxGfKJubfhIw"
    previousVersion="_fnYVKZDhEem7fvtoGpNpow"
    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="08" />
</messageDefinition>

ISO Building Blocks

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