Iso20022

TransferInstructionStatusReportV06

sese.011.001.06

Scope The TransferInstructionStatusReport is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction.

Usage The TransferInstructionStatusReport message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction. The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported:

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
%% TransferInstructionStatusReportV06 recursion level 0 with max 0
TransferInstructionStatusReportV06 *-- "1..1" MessageIdentification1 : MessageIdentification
TransferInstructionStatusReportV06 *-- "0..1" AdditionalReference7 : CounterpartyReference
TransferInstructionStatusReportV06 *-- "0..1" IReferences61Choice : Reference
TransferInstructionStatusReportV06 *-- "1..1" TransferStatusAndReason5 : StatusReport
TransferInstructionStatusReportV06 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
TransferInstructionStatusReportV06 *-- "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

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

CounterpartyReference building block

Unambiguous identification of the transfer allocated by the counterparty. Reference to a related message or transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference7 recursion level 0 with max 1
class AdditionalReference7{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference7 *-- "0..1" IPartyIdentification97Choice : ReferenceIssuer
%% IPartyIdentification97Choice recursion level 1 with max 1

AdditionalReference7 members

Member name Description Data Type / Multiplicity
Reference Reference issued by a party to identify an instruction, transaction or a message. IsoMax35Text - Required 1..1
ReferenceIssuer Party that issued the reference. IPartyIdentification97Choice - Optional 0..1
MessageName Name of the message. IsoMax35Text - Optional 0..1

Reference building block

Reference to the message or communication that was previously received. Choice of references used to reference a previous transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IReferences61Choice recursion level 0 with max 1

References61Choice members

Member name Description Data Type / Multiplicity

StatusReport building block

Status of the transfer instruction. Information about the status of a transfer instruction and its reason. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransferStatusAndReason5 recursion level 0 with max 1
class TransferStatusAndReason5{
    MasterReference IsoMax35Text
    TransferReference IsoMax35Text
    CancellationReference IsoMax35Text
    TradeDate IsoISODate
    SendOutDate IsoISODate
    TotalUnitsNumber IsoDecimalNumber
    AveragePrice IsoActiveOrHistoricCurrencyAnd13DecimalAmount
}
TransferStatusAndReason5 *-- "0..1" AdditionalReference7 : ClientReference
TransferStatusAndReason5 *-- "1..1" ITransferStatus2Choice : TransferStatus
TransferStatusAndReason5 *-- "0..0" Unit8 : UnitsDetails
TransferStatusAndReason5 *-- "0..1" PartyIdentification113 : StatusInitiator
%% AdditionalReference7 recursion level 1 with max 1
class AdditionalReference7{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference7 *-- "0..1" IPartyIdentification97Choice : ReferenceIssuer
%% ITransferStatus2Choice recursion level 1 with max 1
%% Unit8 recursion level 1 with max 1
class Unit8{
    UnitsNumber IsoDecimalNumber
    OrderDate IsoISODate
    AcquisitionDate IsoISODate
    CertificateNumber IsoMax35Text
    Group1Or2Units UKTaxGroupUnit1Code
    Reference IsoMax35Text
}
Unit8 *-- "0..1" UnitPrice23 : PriceDetails
Unit8 *-- "0..1" TotalFeesAndTaxes40 : TransactionOverhead
Unit8 *-- "0..0" OtherAmount1 : OtherAmount
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party

TransferStatusAndReason5 members

Member name Description Data Type / Multiplicity
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 the transfer, as assigned by the instructing party. IsoMax35Text - Required 1..1
ClientReference Unique and unambiguous investor’s identification of the 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
TransferStatus Status of the transfer instruction. ITransferStatus2Choice - Required 1..1
TradeDate Date and time at which the transfer was executed. IsoISODate - Optional 0..1
SendOutDate Date on which the document, for example, the application form, was sent. IsoISODate - Optional 0..1
TotalUnitsNumber Number of units to be transferred. IsoDecimalNumber - Optional 0..1
AveragePrice Weighted average price of the units in the account. The AveragePrice may also be known as the average acquisition price. IsoActiveOrHistoricCurrencyAnd13DecimalAmount - Optional 0..1
UnitsDetails Breakdown of units to be transferred. Unit8 - Unknown 0..0
StatusInitiator Party that initiates the status. PartyIdentification113 - 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 TransferInstructionStatusReportV06 implementation follows a specific implementaiton pattern. First of all, TransferInstructionStatusReportV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, TransferInstructionStatusReportV06Document implements IOuterDocument. Because TransferInstructionStatusReportV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type TransferInstructionStatusReportV06.

classDiagram
    class IOuterRecord
    TransferInstructionStatusReportV06 --|> IOuterRecord : Implements
    TransferInstructionStatusReportV06Document --|> IOuterDocument~TransferInstructionStatusReportV06~ : Implements
    class IOuterDocument~TransferInstructionStatusReportV06~ {
        TransferInstructionStatusReportV06 Message
     }

Document wrapper for serialization

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

classDiagram
    TransferInstructionStatusReportV06Document *-- TransferInstructionStatusReportV06 : 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.011.001.06">
    <TrfInstrStsRpt>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <CtrPtyRef>
            <!-- CounterpartyReference inner content -->
        </CtrPtyRef>
        <Ref>
            <!-- Reference inner content -->
        </Ref>
        <StsRpt>
            <!-- StatusReport inner content -->
        </StsRpt>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </TrfInstrStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_ZUnusYZMEeemXK0UETsSiA"
  nextVersions="_EObOgVNUEeijdq8ilaxyOA"
  previousVersion="_Pm-PkR8OEeWpZde3LQh6dg"
  name="TransferInstructionStatusReportV06"
  definition="Scope&#xD;&#xA;The TransferInstructionStatusReport is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction.&#xD;&#xA;&#xD;&#xA;Usage&#xD;&#xA;The TransferInstructionStatusReport message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction.&#xD;&#xA;The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.&#xD;&#xA;One of the following statuses can be reported:&#xD;&#xA;- an accepted status, or,&#xD;&#xA;- an already executed status, or,&#xD;&#xA;- a sent to next party status, or,&#xD;&#xA;- a matched status, or,&#xD;&#xA;- a settled status, or,&#xD;&#xA;- a pending settlement status and the reason for the status, or,&#xD;&#xA;- an unmatched status and the reason for the status, or,&#xD;&#xA;- an in-repair status and the reason for the status, or,&#xD;&#xA;- a rejected status and the reason for the status, or,&#xD;&#xA;- a failed settlement status and the reason for the status, or,&#xD;&#xA;- a cancelled status and the reason for the status, or,&#xD;&#xA;- a cancelled status and the reason for the status, or,&#xD;&#xA;- a cancellation pending status and the reason for the status."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="TrfInstrStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_ZUnus4ZMEeemXK0UETsSiA"
    nextVersions="_EObOg1NUEeijdq8ilaxyOA"
    previousVersion="_Pm-Pkx8OEeWpZde3LQh6dg"
    name="OtherReferenceRule"
    definition="Reference/OtherReference should be used to reference a transfer instruction or a transfer cancellation request 'message' sent in a proprietary way or used for a system reference. If Reference/OtherReference is present, Reference/OtherReference/MessageName must contain 'fax' or 'phone' or 'email', etc."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_ZUnutYZMEeemXK0UETsSiA"
    nextVersions="_EObOhVNUEeijdq8ilaxyOA"
    previousVersion="_Pm-PlR8OEeWpZde3LQh6dg"
    name="RelatedReferenceRule"
    definition="If Reference/RelatedReference/MessageName is present, it must start with sese.001, sese.002, sese.005, sese.006, sese.009, sese.012 or sese.014."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_ZUnut4ZMEeemXK0UETsSiA"
    nextVersions="_EObOh1NUEeijdq8ilaxyOA"
    previousVersion="_Pm-Plx8OEeWpZde3LQh6dg"
    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="_ZUnuuYZMEeemXK0UETsSiA"
    nextVersions="_EObOiVNUEeijdq8ilaxyOA"
    previousVersion="_Pm-PmR8OEeWpZde3LQh6dg"
    name="CounterpartyReference"
    definition="Unambiguous identification of the transfer allocated by the counterparty."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CtrPtyRef"
    complexType="_CxGKASVIEeWI0orciOKunQ" />
  <messageBuildingBlock
    xmi:id="_ZUnuu4ZMEeemXK0UETsSiA"
    nextVersions="_EObOi1NUEeijdq8ilaxyOA"
    previousVersion="_Pm-Pmx8OEeWpZde3LQh6dg"
    name="Reference"
    definition="Reference to the message or communication that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Ref"
    complexType="_kTej8UHOEeazV4RAqPV71g" />
  <messageBuildingBlock
    xmi:id="_ZUnuvYZMEeemXK0UETsSiA"
    nextVersions="_EObOjVNUEeijdq8ilaxyOA"
    previousVersion="_Pm-PnR8OEeWpZde3LQh6dg"
    name="StatusReport"
    definition="Status of the transfer instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StsRpt"
    complexType="_FjDpwYfuEeevKP8c-ilVhA" />
  <messageBuildingBlock
    xmi:id="_ZUnuv4ZMEeemXK0UETsSiA"
    nextVersions="_EObOj1NUEeijdq8ilaxyOA"
    previousVersion="_Pm-Pnx8OEeWpZde3LQh6dg"
    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="_ZUnuwYZMEeemXK0UETsSiA"
    nextVersions="_EObOkVNUEeijdq8ilaxyOA"
    previousVersion="_Pm-PoR8OEeWpZde3LQh6dg"
    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="011"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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