auth.032.001.01
The FinancialInstrumentReportingEquityTransparencyDataReport message is sent by the trading venues to the national competent authority to report on the transparency data for equity financial instruments.
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 %% FinancialInstrumentReportingEquityTransparencyDataReportV01 recursion level 0 with max 0 FinancialInstrumentReportingEquityTransparencyDataReportV01 *-- "1..1" SecuritiesMarketReportHeader1 : ReportHeader FinancialInstrumentReportingEquityTransparencyDataReportV01 *-- "1..1" TransparencyDataReport11 : EquityTransparencyData FinancialInstrumentReportingEquityTransparencyDataReportV01 *-- "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 |
EquityTransparencyData building block
Details the equity transparency qualitative data reported by a trading venue. Provides for reporting qualitative details of equity instruments as part of Transparency calculations. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransparencyDataReport11 recursion level 0 with max 1 class TransparencyDataReport11{ TechnicalRecordIdentification IsoMax35Text Identification IsoISINOct2015Identifier FullName IsoMax350Text TradingVenue IsoMICIdentifier ReportingDate IsoISODate FinancialInstrumentClassification EquityInstrumentReportingClassification1Code NumberOutstandingInstruments IsoDecimalNumberFraction5 HoldingsExceedingTotalVotingRightThreshold IsoDecimalNumberFraction5 IssuanceSize IsoActiveCurrencyAndAmount InstrumentPrice IsoActiveCurrencyAnd13DecimalAmount }
TransparencyDataReport11 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
TechnicalRecordIdentification | Unique identifier of a record in a message used as part of error management and status advice messages. Usage: This identification will be used in the status advice report sent back. | IsoMax35Text - Optional 0..1 |
Identification | Identifies the financial instrument using an ISIN. | IsoISINOct2015Identifier - Required 1..1 |
FullName | Full name or description of the financial instrument. | IsoMax350Text - Optional 0..1 |
TradingVenue | Segment MIC for the trading venue where applicable, otherwise the operational MIC. | IsoMICIdentifier - Optional 0..1 |
ReportingDate | Date for which the data is provided. | IsoISODate - Optional 0..1 |
FinancialInstrumentClassification | Specifies the classification of the equity instrument. | EquityInstrumentReportingClassification1Code - Required 1..1 |
NumberOutstandingInstruments | For shares and depositary receipts, the total number of outstanding instruments. For ETFs, the number of units issued for trading. | IsoDecimalNumberFraction5 - Optional 0..1 |
HoldingsExceedingTotalVotingRightThreshold | The total number of shares corresponding to holdings exceeding 5% of total voting rights of the issuer unless such a holding is held by a collective investment undertaking or a pension fund. This field is to be populated only when actual information is known. | IsoDecimalNumberFraction5 - Optional 0..1 |
IssuanceSize | Issuance size of the certificate expressed in Euros. | IsoActiveCurrencyAndAmount - Optional 0..1 |
InstrumentPrice | Before the first admission to trading of the instrument, the price of the instrument as it will stand at the start of the first day of trading. After the first admission to trading of the instrument, the price of the instrument at the last trading day of the previous year, or at the end of the day on which a corporate action is effective. The price should be expressed in Euros. To be reported for shares and depositary receipts. | IsoActiveCurrencyAnd13DecimalAmount - 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 FinancialInstrumentReportingEquityTransparencyDataReportV01 implementation follows a specific implementaiton pattern. First of all, FinancialInstrumentReportingEquityTransparencyDataReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialInstrumentReportingEquityTransparencyDataReportV01Document implements IOuterDocument. Because FinancialInstrumentReportingEquityTransparencyDataReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialInstrumentReportingEquityTransparencyDataReportV01.
classDiagram class IOuterRecord FinancialInstrumentReportingEquityTransparencyDataReportV01 --|> IOuterRecord : Implements FinancialInstrumentReportingEquityTransparencyDataReportV01Document --|> IOuterDocument~FinancialInstrumentReportingEquityTransparencyDataReportV01~ : Implements class IOuterDocument~FinancialInstrumentReportingEquityTransparencyDataReportV01~ { FinancialInstrumentReportingEquityTransparencyDataReportV01 Message }
Document wrapper for serialization
The only real purpose FinancialInstrumentReportingEquityTransparencyDataReportV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.032.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FinancialInstrumentReportingEquityTransparencyDataReportV01.ToDocument() method. The returned FinancialInstrumentReportingEquityTransparencyDataReportV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram FinancialInstrumentReportingEquityTransparencyDataReportV01Document *-- FinancialInstrumentReportingEquityTransparencyDataReportV01 : 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.032.001.01">
<FinInstrmRptgEqtyTrnsprncyDataRpt>
<RptHdr>
<!-- ReportHeader inner content -->
</RptHdr>
<EqtyTrnsprncyData>
<!-- EquityTransparencyData inner content -->
</EqtyTrnsprncyData>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</FinInstrmRptgEqtyTrnsprncyDataRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_4LK8TURNEee7JdgA9zPESA"
name="FinancialInstrumentReportingEquityTransparencyDataReportV01"
definition="The FinancialInstrumentReportingEquityTransparencyDataReport message is sent by the trading venues to the national competent authority to report on the transparency data for equity financial instruments."
registrationStatus="Registered"
messageSet="_m18yAApTEeeand7dul6qJQ"
xmlTag="FinInstrmRptgEqtyTrnsprncyDataRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_4LK8T0RNEee7JdgA9zPESA"
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="_4LK8UURNEee7JdgA9zPESA"
name="EquityTransparencyData"
definition="Details the equity transparency qualitative data reported by a trading venue."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="EqtyTrnsprncyData"
complexType="_pVzQ4Wk3EeaLAKoEUNsD9g" />
<messageBuildingBlock
xmi:id="_4LK8U0RNEee7JdgA9zPESA"
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="032"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.