As first published in Traders Magazine

Two years after the launch of the EU’s flagship financial markets legislation, the European Commission is considering a revamp of a number of aspects of the regulatory framework by issuing a consultation for the review of MiFID II. The aim of the consultation is to gather views from stakeholders regarding their experience under the MiFID II regime and on certain technical aspects, as well as providing a chance to comment on any further issues.

What has transpired is that European fund and asset managers have now insisted upon the need to implement a consolidated tape as part of their response to the review of MiFID II. This article examines the hurdles that would need to be overcome in order for a consolidated tape to be established.

Problems past

While the MiFID II regulation did outline requirements for voluntarily consolidated tape providers, the establishment of a consolidated tape was not mandated for, meaning firms are not currently obligated to submit their transaction data as they are in the US. In the end, a European consolidated tape did not transpire, even though some feel there is still a need for one.

As things currently stand, it is extremely difficult for firms to create a reliable aggregation solution based on current methods of obtaining data. Research conducted by Etrading Software, which will be published in the coming weeks, has shown that while some aggregation of non-equity post-trade information made available free of charge 15 minutes after its publication is possible with sufficiently large effort, in fact aggregation is quite difficult to achieve. This is down to either a lack of machine access to the data (for example, the files are machine-readable but automated machine access to the files is often blocked), a lack of comprehensive post-trade data specification regarding the ordering of the fields or file format, or the fact that many APAs do not follow the stipulations as laid out in the Technical Specifications (RTS2).

Ultimately, the problems surrounding the creation of a consolidated tape still stand, primarily because there is no viable business case in the operation of such a utility under the current provisions. It should also be noted that some trading venues and APAs are also data vendors in their own right and therefore may have a conflict of interest due to the potential impact of a CT on their proprietary commercial data offerings. A second problem exists in that both existing APAs and trading venues are publishing their free post-trade data in incompatible formats. Our research strongly supports the need for detailed specifications for the content, format and terminology of the post-trade data. Specifically, our findings show that these vary sufficiently widely amongst TVs and APAs to cause data quality issues for aggregation.

Detailed solutions

At Etrading Software, we firmly believe the aforementioned problems can be mitigated if the following were implemented as part of an initiative:

Mandatory contributions: One option to address the issue of conflicting business cases is to mandate contribution to the Consolidated Tape Provider (CTP). Another option is to ensure any CTP is wholly independent of any Trading Venue (TV) or Approved Publication Arrangement (APA) to remove the incentive for the CTP to tilt its service in favour of the commercial offerings of TVs/APAs.

Standardised formats: A critical success factor is the unambiguous specification of every data element of the mandated dataset. Ideally, such specification would be based on an ISO standard, but where these are missing, other industry standards should be considered. For example, the FIX Market Model Typology provides a good example of a non-ISO standard by a neutral, independent organisation that can assist with the definition of the post trade flags required by the CTP.

API-led Connectivity: The only reliable way for data aggregation is for trading venues and APAs to connect to a single CTP using a single, unambiguous specification. The alternative of the CTP connecting to each individual Trading Venue or APA, using the TV/APAs own data format and API will very likely impact data quality significantly due to differing interpretations that our research has uncovered in existing APA/TV post trade data.

Further, this single API should be mandated for use by contributing organisations (TVs/APAs etc). A single API minimises the risk of differing, incompatible implementations. Achieving a single API implementation requires the mandating of TVs/APAs to connect to the CTPs using the CTPs API and not the other way round (i.e. not for the CTP to connect to the APA/TV APIs using their individual APIs).

A cost-recovery model: There is currently a lack of research regarding a model where market data contributors provide the raw post-trade data for free to a single CTP, and where the CTP is only mandated to recover its own costs. Such a model allows the possibility of the lowest overall cost to data consumers, as revenues need only cover the cost of operation of the CT. We note such a model already exists in the reference data space and it may be sensible to investigate its applicability to market data as well. An alternative model of sharing revenues with TVs/APAs would require higher overall fees to be charged in order both to cover the operational cost of the CT and also to compensate TVs/APAs.

Perfect timing

For many years now there have been murmurs from industry practitioners with regards to high market data costs. This consultation represents a perfect opportunity for the industry to engage with regulators to help simplify the market data infrastructure within Europe. Such a streamlined infrastructure in the form of mandating a high-quality consolidated tape provider should then have a knock-on impact in terms of lowered costs. With responses due in to ESMA by the extended deadline of 14 June 2020, we look forward to ESMAs output and strongly encourage industry participants to engage with the regulators.

Categories: ETS News Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

shares