RD e-book Blog 2 website.png

Regulatory compliance: Trying to hit a moving target with one hand tied behind your back

This blog highlights a discussion point from our comprehensive eBook: “Reference Data: The Essential Guide”.

It is a truth universally acknowledged that faulty reference data is, today, one of the key contributors to regulatory reporting failures. More trading venues transacting more and more instruments, more regulatory obligations to manage and data to report, and more demanding customers, make the challenge of regulatory reporting especially difficult for sell-side firms in their roles as consumers, generators and distributors of financial markets data.

MiFID & EMIR reporting obligations

A senior banker once described MiFID I regulation as “peeling back the layers of an onion to reveal….a carrot”. Throw into the regulatory compliance mix MiFID II, EMIR, EMIR Refit and a host of other market transparency and anti-abuse regulatory reporting compliance obligations and the challenge of managing reference data might be likened to trying to hit a constantly moving target with one hand tied behind your back.

The EMIR refit set to go live in Europe in April 2024 (September in UK) requires ALL derivative trades to be reported to trade repositories in a standardised format, adding a lot more (74) reportable fields to EMIR-eligible transaction messages. It also imposes an ISO20022 global messaging standard on EMIR reporting, requiring it to be reported in a standardised XML structure, not the typical csv format used today.

No sign of data standardisation

It might be reasonable to assume that there is consensus and harmonisation of data standards with respect to how instruments are labelled but this is simply not (yet) the case. Different symbols can be used to identify the same instrument; identifiers can also be subject to frequent change.

A number of industry initiatives are looking at more standardised instrument classifications and identifiers including the Financial Stability Board (FSB) (its feasibility study in 2014 concluded that “it is critical for any data aggregation option that the work on standardisation and harmonisation of important data elements be completed, in particular through the global introduction of the Legal Entity Identifier (LEI), and the creation of a UTI and UPI”. SWIFT, ISDA and other industry bodies are also engaged in developing data and messaging standards to support industry standardisation and consistency.

Meeting regulatory reporting obligations

From working closely with our customers, it is clear that meeting regulatory reporting obligations - getting the right data in the right boxes at the right time - is their most pressing challenge. Fortunately, helping businesses to navigate smoothly through ever-changing regulatory reporting seas is our entire focus.

To find out more about reference data trends and challenges, download our comprehensive eBook “Reference Data: The Essential Guide”.

Share

Reference Data: The Essential Guide

As the number of financial markets, assets, issuers, products and participants continues to grow, our latest guide explores the increasing impact of reference data on financial markets.

Related Insights

  1. Article
    In the continuing absence of single, global identification and transaction messaging standards, the challenges of managing reference data are many and varied, since every data point may be subject to multiple interpretations - and indeed uses - in different contexts.
  2. Article
    Reference data plays an increasingly critical role in the smooth running of global financial markets, touching on every part of the transaction lifecycle.
  3. Article
    The use of reference data is not always an ‘after the event’ activity for reporting purposes. Futures and options reference data in particular is not only instrumental but also mission critical in price discovery for forward-priced transactions. As such, any problem with this data, whether at source , in its delivery to an end user application, or because of a ‘glitch in the matrix’ on the end user side , can cause major headaches.