A-Team Insight Blogs

EMIR and MiFID Transaction Reporting Challenges Continue to Trouble Firms and Regulators

Share article

Data quality is proving to be an enduring albatross around the necks of financial institutions that must comply with EU reporting rules under MiFID II and EMIR. A recent disclosure by the European Securities and Markets Authority (ESMA) shows that matching rates remain poor for derivatives transactions reported under the European Markets and Infrastructure Regulation (EMIR), suggesting that basic trade details are reported inconsistently. Meanwhile, analysis conducted by a regulatory compliance consulting firm reveals specific data quality issues financial services organisations are encountering that could undermine compliance with Markets in Financial Instruments Directive II (MiFID II).

EMIR’s data quality issues

A Freedom of Information request of ESMA has revealed that the reconciliation

statistics for February 2019 show average pairing rates of 86%, and matching rates of 40%. Trades are paired by using the Unique Transaction Identifier (UTI) to bring together two trade reports, which are submitted by the counterparties to the trade. Pairing should, in theory, be simple – and it’s even easier if one of the counterparties has delegated reporting to the other counterparty, which is possible under certain circumstances. Even so, more than one in 10 trades is currently failing to pair.

Matching demands that key data fields in the transaction contain the same data – ESMA specifies 47 critical fields. Some data may not match exactly – such as execution time – but this is acceptable if the data is within a certain range. The current data from ESMA shows that only four in 10 trades are matched at present – and it’s possible that this level could be even lower. For example, it’s unclear whether ESMA’s matching rate includes delegated reports, which in theory should be a perfect match since one party is submitting both reports. Removing delegated reports from the equation could lower the matching rate further.

MiFID II’s data quality issues

Analysis completed by ACA Compliance Group suggests that financial services firms are also struggling with the quality of their trade transaction reporting data under the Markets in Financial Instruments Regulation (MiFIR), part of the overall MiFID II project. The UK consultancy asked a number of financial services organisations to submit sample transaction reporting data, which was then analysed in the context of the firms’ permissions and activities. The results show that the industry has work to do; for example, 48% had incorrectly reported one of the fields, the transmission of order indicator. This data point reflects how an order has been executed, either by transmitting to a third party or directly on a venue.

“We’ve found this to be a problematic field in the course of our assurance and consulting work,” says Bobby Johal, managing director at ACA Compliance Group in London. “However, the accuracy of data in other fields needs improving too. In our sample, we found quality issues with venue data, trading time, quantity and price. Firms need to eliminate these kinds of errors by putting in place monitoring and reconciliation processes that are both regular and meaningful.”

Regulators issue more fines

UK regulators are very much focused on transaction reporting compliance under the preceding regulation, MiFID I, which has been in place for about a decade. In March, the Financial Conduct Authority (FCA) fined Goldman Sachs over £34 million because of more than 220 million transaction reporting errors over nine and a half years under MiFID 1. Also, in March, UBS was fine over £27 million for making more than 135 million transaction reporting errors over the same period of time under MiFID I.

More recently, regulatory attention has been on the trade repositories to whom firms must submit their EMIR reports, with Regis-TR, the second largest EU trade repository, being fined €56,000. According to the regulator, the trade repository ‘failed to put in place systems capable of providing to regulators direct and immediate access to derivatives data from the start of the EMIR reporting obligation in February 2014 to October 2016. These access failures related to:

  • 85.5% (3.7 billion) of Regis-TR’s data on trade terminations and 1.6% (15 million) of data on trade modifications; and
  • 100% (2.9 billion) of Regis-TR’s data on trade valuations and 100% (22 million) of data on collateral updates.’

This follows on from ESMA’s fining the trade repository DTCC €64,000 ‘for negligently failing to put in place systems capable of providing regulators with direct and immediate access to derivatives trading data’ in March 2016.

Indeed, the regulators have been banging the data quality drum for some time. According to ACA Compliance Group, the UK’s FCA and predecessor organisation, the Financial Services Authority (FSA), have fined the financial services firms they regulate a total of £95 million for MiFID I transaction reporting issues – a total of 14 fines since 2009 – and a total of £34.5 million for EMIR reporting issues. Says Johal, “At the moment, regulators are focused on understanding the nature and scale of errors and how they are being addressed. However, considering how regulators engaged around MiFID I, it’s likely that enforcement activity will increase at both UK and EU levels over the coming 12 months. Firms should prepare for an increased level of scrutiny on their transaction reporting processes.”

Leave a comment

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

*

Related content

WEBINAR

Recorded Webinar: FRTB: The time to get your data in order is now

Fundamental Review of the Trading Book (FRTB) regulation requires firms within its scope to source significant amounts of data, some of which has not previously been required and is difficult to pin down. The data management challenges of the regulation’s Internal Model Approach (IMA) to market risk capital calculations include ongoing P&L attribution, back testing...

BLOG

Saxo Bank Japan Migrates from Legacy Ledger to Torstone Cloud Solution

Saxo Bank Japan is replacing its legal ledger legacy system with Torstone Technology’s Inferno cloud-based solution and has gone live with the first phase of migration. The bank is making the replacement to support regulatory reporting on the cloud for existing and new equity business. Using Inferno, Saxo Bank Japan is able to reduce operational...

GUIDE

Regulatory Data Handbook 2019/2020 – Seventh Edition

Welcome to A-Team Group’s best read handbook, the Regulatory Data Handbook, which is now in its seventh edition and continues to grow in terms of the number of regulations covered, the detail of each regulation and the impact that all the rules and regulations will have on data and data management at your institution. This...