FinancialInstrumentReportingReferenceDataIndexReportV01

auth.043.001.01

This FinancialInstrumentReportingReferenceDataIndexReport message is sent by National Competent Authorities to express an interest in receiving data on European indices.

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
%% FinancialInstrumentReportingReferenceDataIndexReportV01 recursion level 0 with max 0
FinancialInstrumentReportingReferenceDataIndexReportV01 *-- "1..1" SecuritiesMarketReportHeader1 : ReportHeader
FinancialInstrumentReportingReferenceDataIndexReportV01 *-- "1..1" SecuritiesIndexReport1 : IndexData
FinancialInstrumentReportingReferenceDataIndexReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

ReportHeader building block

Header information related to the global report, common to all reference data. Provides the securities market transaction report related header details. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesMarketReportHeader1 recursion level 0 with max 1
class SecuritiesMarketReportHeader1{
    SubmissionDateTime IsoISODateTime
}
SecuritiesMarketReportHeader1 *-- "1..1" ITradingVenueIdentification1Choice : ReportingEntity
SecuritiesMarketReportHeader1 *-- "1..1" IPeriod4Choice : ReportingPeriod
%% ITradingVenueIdentification1Choice recursion level 1 with max 1
%% IPeriod4Choice recursion level 1 with max 1
  

SecuritiesMarketReportHeader1 members

Member name Description Data Type / Multiplicity
ReportingEntity Identification of the venue which generates the report. ITradingVenueIdentification1Choice - Required 1..1
ReportingPeriod Date or date range the report relates to. IPeriod4Choice - Required 1..1
SubmissionDateTime Date and time of the report originally submitted by the reporting entity when the file is generated for submission to their reporting authority. IsoISODateTime - Optional 0..1

IndexData building block

Details of specific financial instruments a National Competent Authority wishes to express an interest in receiving transaction reports on. Provides details on the securities index request operations for national competent authorities. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesIndexReport1 recursion level 0 with max 1
class SecuritiesIndexReport1{
    TechnicalRecordIdentification IsoMax35Text
    RequestingEntity CountryCode
}
SecuritiesIndexReport1 *-- "1..1" IFinancialInstrument46Choice : Index
SecuritiesIndexReport1 *-- "0..1" IPeriod4Choice : ValidityPeriod
%% IFinancialInstrument46Choice recursion level 1 with max 1
%% IPeriod4Choice recursion level 1 with max 1
  

SecuritiesIndexReport1 members

Member name Description Data Type / Multiplicity
TechnicalRecordIdentification Unique identifier of a record in a message used as part of error management and feedback messages. Usage: This identification will be used in the status advice sent back. IsoMax35Text - Optional 0..1
RequestingEntity Country code of the entity that wishes to express an interest in receiving transaction reports for the requested indexes. CountryCode - Optional 0..1
Index Details the index that is being requested. IFinancialInstrument46Choice - Required 1..1
ValidityPeriod Date when the national competent authority last expressed its interest in this index. IPeriod4Choice - Optional 0..1

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

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    FinancialInstrumentReportingReferenceDataIndexReportV01 --|> IOuterRecord : Implements
    FinancialInstrumentReportingReferenceDataIndexReportV01Document --|> IOuterDocument~FinancialInstrumentReportingReferenceDataIndexReportV01~ : Implements
    class IOuterDocument~FinancialInstrumentReportingReferenceDataIndexReportV01~ {
        FinancialInstrumentReportingReferenceDataIndexReportV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    FinancialInstrumentReportingReferenceDataIndexReportV01Document *-- FinancialInstrumentReportingReferenceDataIndexReportV01 : 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.043.001.01">
    <FinInstrmRptgRefDataIndxRpt>
        <RptHdr>
            <!-- ReportHeader inner content -->
        </RptHdr>
        <IndxData>
            <!-- IndexData inner content -->
        </IndxData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FinInstrmRptgRefDataIndxRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_4LUGMURNEee7JdgA9zPESA"
  name="FinancialInstrumentReportingReferenceDataIndexReportV01"
  definition="This FinancialInstrumentReportingReferenceDataIndexReport message is sent by National Competent Authorities to express an interest in receiving data on European indices."
  registrationStatus="Registered"
  messageSet="_m18yAApTEeeand7dul6qJQ"
  xmlTag="FinInstrmRptgRefDataIndxRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_4LUGM0RNEee7JdgA9zPESA"
    name="ReportHeader"
    definition="Header information related to the global report, common to all reference data."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptHdr"
    complexType="_Xt9fc8v5EeSxLrW9hropkQ" />
  <messageBuildingBlock
    xmi:id="_4LUGNURNEee7JdgA9zPESA"
    name="IndexData"
    definition="Details of specific financial instruments a National Competent Authority wishes to express an interest in receiving transaction reports on."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="IndxData"
    complexType="_00E_kL3kEeWvRsMSLyTf-A" />
  <messageBuildingBlock
    xmi:id="_4LUGN0RNEee7JdgA9zPESA"
    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="043"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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