FinancialInstrumentReportingTransactionReportV03

auth.016.001.03

The FinancialInstrumentReportingTransactionReport message is sent by the reporting agent to the competent authority to report on the securities transactions or by the competent authority to another competent authority when the transaction needs to be exchanged between the competent authorities.

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
%% FinancialInstrumentReportingTransactionReportV03 recursion level 0 with max 0
FinancialInstrumentReportingTransactionReportV03 *-- "1..1" IReportingTransactionType3Choice : Transaction
FinancialInstrumentReportingTransactionReportV03 *-- "0..1" SupplementaryData1 : SupplementaryData
  

Now, we will zero-in one-by-one on each of these building blocks.

Transaction building block

Provides the details of the reported securities transactions. Choice between a new or a cancellation transaction. For comparison, see the ISO20022 official specification

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

ReportingTransactionType3Choice members

SupplementaryData building block

Additional information that can not be captured in the structured fields 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
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    FinancialInstrumentReportingTransactionReportV03 --|> IOuterRecord : Implements
    FinancialInstrumentReportingTransactionReportV03Document --|> IOuterDocument~FinancialInstrumentReportingTransactionReportV03~ : Implements
    class IOuterDocument~FinancialInstrumentReportingTransactionReportV03~ {
        FinancialInstrumentReportingTransactionReportV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    FinancialInstrumentReportingTransactionReportV03Document *-- FinancialInstrumentReportingTransactionReportV03 : 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:auth.016.001.03">
    <FinInstrmRptgTxRpt>
        <Tx>
            <!-- Transaction inner content -->
        </Tx>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FinInstrmRptgTxRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_YfqlMQxPEe6IZ4NJLf_INA"
  name="FinancialInstrumentReportingTransactionReportV03"
  definition="The FinancialInstrumentReportingTransactionReport message is sent by the reporting agent to the competent authority to report on the securities transactions or by the competent authority to another competent authority when the transaction needs to be exchanged between the competent authorities."
  registrationStatus="Registered"
  messageSet="_m18yAApTEeeand7dul6qJQ"
  xmlTag="FinInstrmRptgTxRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_YfqlNQxPEe6IZ4NJLf_INA"
    name="Transaction"
    definition="Provides the details of the reported securities transactions."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="Tx"
    complexType="_6c12MZicEe2f7NHvXATP5g" />
  <messageBuildingBlock
    xmi:id="_YfrMQQxPEe6IZ4NJLf_INA"
    name="SupplementaryData"
    definition="Additional information that can not be captured in the structured fields and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="auth"
    messageFunctionality="016"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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