Only 13 Of The 23 Existing Fields Remain Unchanged.
140 and 250 which relate to field 45 (notional currency 2); The transaction reporting solution utilises two principal data sources: Esma guidelines specify the construction of transaction reports field by field for the various trading scenarios.
Each Of The Scenarios Is Accompanied With An Example Of The Xml Text To Be Used To Represent The Specific Reportable Values.
• trading venue data (order data, member portal, instrument reference data) • additional information provided by members to unavista after the trade has taken place Within erep the reports will be known as: Fields reported include counterparty, who initiated the trade and behalf of whom the trade is for.
A C Sv Report On Products Covered Under The Mifir Requirements.
Any financial instrument which has traded or has been admitted to trading on a trading venue (not just regulated markets as dictated by mifid i). In the mifid ii world, a transaction report can contain up to 65 fields. 166 which relates to field 53 (option exercise style).
Similar To Emir Reporting, Mifid Ii’s Transaction Reporting Greatly Increases The Data Fields Required When Compared To Trade Reporting.
Reports are required for all asset classes and comprise of up to 65 xml fields. 154 and 264 which relate to field 48 (underlying index name); The report also summarizes, for each currency held by the accounts, total debits and credits and the beginning and ending balance.
Data Field (16) And (18) The Quantity Required By The Trum Description To Calculate Both The Values For Fields “Total Notional Contract Quantity” And “Estimated Notional Amount” Is.
How the fields should be filled in) is described in annex 1, table 2. The information that must be filed in transaction reports (i.e. Reports of transactions in financial instruments in accordance with mifid ii/mifir are filed in accordance with the technical specifications from the european securities and markets authority (esma).