About a-team Marketing Services
The knowledge platform for the financial technology industry
The knowledge platform for the financial technology industry

A-Team Insight Blogs

FCA Cracks Down on OMS Reporting Errors: Regulated Firms Pay the Price

Subscribe to our newsletter

By Matt Smith, CEO, SteelEye.

Certain Order Management Systems (OMSs) have recently come under scrutiny from the FCA because of quality issues around MiFIR reporting. Firms that heavily rely on their OMS for daily regulatory reporting have been found to consistently over or under report their transactions.

The responsibility for accurate reporting rests solely with the regulated entity, and soon reporting errors from certain OMSs will no longer be tolerated.

Some OMSs are likened to black boxes when it comes to transaction reporting. There is very little transparency and visibility into what goes in the daily transaction reports downloaded by clients. As a result, regulated firms relying on this method have little to no way of knowing if the daily extract of transactions is in alignment with regulatory standards.

In fact, a couple of common issues with these systems is that they have slow or inaccurate MiFIR eligibility checks and struggle with security identification for anything more complex than listed products. To give an example, when a security is unknown to the system, certain fields are populated with default values. Take FX Forwards for example – through various consultations, we have seen multiple examples where these have been reported as Indices. Whilst this passes the validation checks (by defaulting the [Underlying Index Id] field value), it produces an inaccurate transaction report.

Because of these issues and the lack of visibility into the reporting process, many firms have unknowingly over, under or mis-reported.

The regulator’s intensified push on data accuracy is certainly being felt and several firms have already been approached – often given less than 3 months to remediate their reporting. The implications are grave, and fines are rife for reporting errors. In 2019, Goldman Sachs was fined £34.3 million for failing to provide accurate and timely reporting. The same year, UBS were fined £27.6 million for reporting issues. And that does include the reputational and commercial consequences of such bad press. Is now the time for firms to start taking their reporting more seriously?

Subscribe to our newsletter

Related content

WEBINAR

Recorded Webinar: Navigating a Complex World: Best Data Practices in Sanctions Screening

As rising geopolitical uncertainty prompts an intensification in the complexity and volume of global economic and financial sanctions, banks and financial institutions are faced with a daunting set of new compliance challenges. The risk of inadvertently engaging with sanctioned securities has never been higher and the penalties for doing so are harsh. Traditional sanctions screening...

BLOG

Why Do We Disagree? How AI Solves One of Post-Trade’s Most Persistent Challenges

By Carl Thornberg, head of optimisation and analytics technology, OSTTRA. In post-trade operations, most problems are not caused by outright errors, they are caused by ambiguity. Trades that look different but are not wrong. Valuations that diverge for valid reasons. Numbers that do not line up, even though nothing has actually gone awry. At scale,...

EVENT

RepRisk Sustainability Breakfast Roundtable London

The London sustainability breakfast is part of the global roundtable thought leadership event series hosted by RepRisk in key markets, including, New York, Toronto, London, Frankfurt, Oslo, Copenhagen, Stockholm, Hong Kong and Singapore in 2026.

GUIDE

Entity Data Management & the LEI

Just over a year since the Financial Stability Board handed over leadership and direction of the interim Global Legal Entity Identifier System – or GLEIS – to the Regulatory Oversight Committee (ROC) of the LEI the entity identifier is being used for reporting under European Market Infrastructure Regulation. This report discusses recent developments in the...