auth.044.001.01
The FinancialInstrumentReportingEquityTradingActivityResult message is sent by a national competent authority to report on computed results data of equity specific trading activity.
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 %% FinancialInstrumentReportingEquityTradingActivityResultV01 recursion level 0 with max 0 FinancialInstrumentReportingEquityTradingActivityResultV01 *-- "1..1" SecuritiesMarketReportHeader1 : ReportHeader FinancialInstrumentReportingEquityTradingActivityResultV01 *-- "1..1" TransparencyDataReport12 : EquityTransparencyData FinancialInstrumentReportingEquityTradingActivityResultV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
ReportHeader building block
Header to provide details on when and from whom the message originates. 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 transparency data reported by a trading venue. Provides for reporting calculation results of equity instruments as part of transparency. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransparencyDataReport12 recursion level 0 with max 1 class TransparencyDataReport12{ TechnicalRecordIdentification IsoMax35Text Identification IsoISINOct2015Identifier FullName IsoMax350Text TradingVenue IsoMICIdentifier Liquidity IsoTrueFalseIndicator Methodology TransparencyMethodology2Code } TransparencyDataReport12 *-- "0..1" IPeriod4Choice : ReportingPeriod TransparencyDataReport12 *-- "0..1" StatisticsTransparency3 : Statistics TransparencyDataReport12 *-- "0..1" MarketDetail2 : RelevantMarket %% IPeriod4Choice recursion level 1 with max 1 %% StatisticsTransparency3 recursion level 1 with max 1 class StatisticsTransparency3{ AverageDailyTurnover IsoActiveCurrencyAndAmount AverageTransactionValue IsoActiveCurrencyAndAmount LargeInScale IsoDecimalNumber StandardMarketSize IsoDecimalNumber AverageDailyNumberOfTransactions IsoDecimalNumber TotalNumberOfTransactionsExecuted IsoDecimalNumber TotalVolumeOfTransactionsExecuted IsoDecimalNumber TotalNumberOfTradingDays IsoNumber } %% MarketDetail2 recursion level 1 with max 1 class MarketDetail2{ Identification IsoMICIdentifier AverageDailyNumberOfTransactions IsoDecimalNumber }
TransparencyDataReport12 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 of the reporting entity. | IsoMax350Text - Optional 0..1 |
TradingVenue | Segment MIC for the trading venue where applicable, otherwise the operational MIC. | IsoMICIdentifier - Optional 0..1 |
ReportingPeriod | Period to which the quantitative data fields relate. | IPeriod4Choice - Optional 0..1 |
Liquidity | Flag to say if this ISIN is liquid or not post calculations. Usage: When not present, this field should be treated as not applicable. | IsoTrueFalseIndicator - Optional 0..1 |
Methodology | Methodology that has been used to calculate the result. | TransparencyMethodology2Code - Optional 0..1 |
Statistics | Statistics for a financial instrument generated as part of transparency calculations. | StatisticsTransparency3 - Optional 0..1 |
RelevantMarket | Specific market details related to the most relevant market in terms of liquidity. | MarketDetail2 - 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 FinancialInstrumentReportingEquityTradingActivityResultV01 implementation follows a specific implementaiton pattern. First of all, FinancialInstrumentReportingEquityTradingActivityResultV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialInstrumentReportingEquityTradingActivityResultV01Document implements IOuterDocument. Because FinancialInstrumentReportingEquityTradingActivityResultV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialInstrumentReportingEquityTradingActivityResultV01.
classDiagram class IOuterRecord FinancialInstrumentReportingEquityTradingActivityResultV01 --|> IOuterRecord : Implements FinancialInstrumentReportingEquityTradingActivityResultV01Document --|> IOuterDocument~FinancialInstrumentReportingEquityTradingActivityResultV01~ : Implements class IOuterDocument~FinancialInstrumentReportingEquityTradingActivityResultV01~ { FinancialInstrumentReportingEquityTradingActivityResultV01 Message }
Document wrapper for serialization
The only real purpose FinancialInstrumentReportingEquityTradingActivityResultV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.044.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FinancialInstrumentReportingEquityTradingActivityResultV01.ToDocument() method. The returned FinancialInstrumentReportingEquityTradingActivityResultV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram FinancialInstrumentReportingEquityTradingActivityResultV01Document *-- FinancialInstrumentReportingEquityTradingActivityResultV01 : 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.044.001.01">
<FinInstrmRptgEqtyTradgActvtyRslt>
<RptHdr>
<!-- ReportHeader inner content -->
</RptHdr>
<EqtyTrnsprncyData>
<!-- EquityTransparencyData inner content -->
</EqtyTrnsprncyData>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</FinInstrmRptgEqtyTradgActvtyRslt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_4LK8RURNEee7JdgA9zPESA"
nextVersions="_ZoWOQSe2Eei12pGEsJIAeQ"
name="FinancialInstrumentReportingEquityTradingActivityResultV01"
definition="The FinancialInstrumentReportingEquityTradingActivityResult message is sent by a national competent authority to report on computed results data of equity specific trading activity."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ _Smpa0G47Eeiuqc7swom0-A"
xmlTag="FinInstrmRptgEqtyTradgActvtyRslt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_4LK8R0RNEee7JdgA9zPESA"
nextVersions="_ZoWOQye2Eei12pGEsJIAeQ"
name="ReportHeader"
definition="Header to provide details on when and from whom the message originates."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RptHdr"
complexType="_Xt9fc8v5EeSxLrW9hropkQ" />
<messageBuildingBlock
xmi:id="_4LK8SURNEee7JdgA9zPESA"
nextVersions="_ZoWORSe2Eei12pGEsJIAeQ"
name="EquityTransparencyData"
definition="Details the transparency data reported by a trading venue."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="EqtyTrnsprncyData"
complexType="_1xRg0Wk8EeaLAKoEUNsD9g" />
<messageBuildingBlock
xmi:id="_4LK8S0RNEee7JdgA9zPESA"
nextVersions="_ZoWORye2Eei12pGEsJIAeQ"
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="044"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.