Checking if Instrument is Reportable

Resolving the CON-412 Rejection Code

MiFID Transaction Reporting | Troubleshooting
12 May 2021

According the FCA, nearly 60pct of rejected transactions are due to the instrument not being found in their database.

MiFID firms submitting transaction reports will be familiar with the CON-412 rejection code – the error code assigned by ESMA, the originators of the MiFID body of regulations. The CON-412 error states: “Instrument is not valid in reference data on transaction date” and is well-known amongst regulatory operational specialists monitoring transaction reports.

Even though firms have had three years to bed-in processes, the CON-412 rejection code continues to plague operations and compliance departments. In 2018, at the start of MiFID, over 37pct of rejections were due to this error. In 2019, this skyrocketed to nearly 70pct of rejected transactions being assigned this error only to drop back down to over 57pct in 2020.

How do firms avoid or resolve this issue? The first port of call would be to conduct due diligence in ensuring the transaction is reportable and residing in the FCA or ESMA databases.

A free tool by Qomply can help. The cloud-based tool retrieves instrument data across all UK and EU exchanges and trading venues and instantly shows if an instrument is reportable on a specific date. If the instrument is not reportable, and there are no underlying instruments, then the transaction should not be submitted to the regulator as it would be considered “over reporting”.

Step 1 Getting Started

Step 1 Search Instrument in FCA and EU FIRDS

Access the Tool

Enter ISIN to Check Across UK and EU Databases

In our test, we use ISIN GB00BDFGHW41

Click View Results

The Trading Venues on which this instrument was tradable for today’s date are shown.

Determine Reportability

To determine if a particular instrument was considered reportable on a trade date, enter the ISIN and the Trade Date in Step 2 on the screen. If a date is not entered, the system will retrieve data for today.

The results show whether the instrument is Reportable in the UK and/or Reportable in the EU along side the Trading Venue on which it was active. If you are reporting to a UK regulator then you are only interested in whether the instrument was reportable in the UK. Therefore, if TRUE appears in the “Reportable in UK” column, the instrument is reportable.

Additional details such as the Trading Venue, to which the instrument was admitted, also appears. For firms who traded the instrument on a trading venue this is useful. If you traded the instrument on a trading venue and it is not listed in the results, then contact the trading venue to ensure they submitted the reference data to FIRDS – an obligation they have under the RTS23 regulation.

If an instrument is traded XOFF, then the instrument should be reportable on at least one trading venue in the region.

If an instrument is traded XXXX, then the instrument should not have been admitted to trading in the region. That is, using the example above, in column “ Reportable in the UK” we should not see TRUE in any of the rows.

Steps to lookup instrument

Step 2 Advanced Tips and Tricks

Step 2 Advanced Tips and Tricks

Get Results for a Specific Trade Date

This feature is especially useful when troubleshooting historic transaction reports.

To go back in time to a specific trade date to determine reportability on that date, enter the ISIN, enter a trade date, and click VIEW RESULTS.

Get Results for Multiple ISINs

To conduct efficient searches across multiple ISINS for the same trade date, simply enter a series of ISINS separated by a comma. Enter the trade date and click VIEW RESULTS.

Get Results for Multiple ISINs in a CSV file

From page, select the CSV file from your local machine, enter a trade date and click VIEW RESULTS.

Download Results

Instead of viewing the results on the screen, it may be more helpful to download the results to a CSV file. This is especially true when entering more than one ISIN. Run the search as normal however instead of clicking VIEW RESULTS, click DOWNLOAD RESULTS.

Quality Assurance at the Touch of a Button

MiFID II regulations requires firms to have arrangements in place to ensure transaction reports are complete and accurate.

Perform Quality Assurance on your transaction reporting through Qomply's cloud-based ReportAssure Suite. Qomply performs accuracy, timeliness, and completeness checks providing assurance that transaction reporting systems are working correctly.

Checks can be done before or after sending to the regulatory or ARM. Qomply's platform is built to respond to increasing levels of complexity of regulation, rules, and data analytics. Qomply's tools offer straight-forward interfaces and streamlined APIs enabling market participants to either use as a stand-alone products or integrate within their existing technical infrastructure.

If you are looking to conduct your own periodic quality assurance, accuracy, completeness, and timeliness checks, then the ReportAssure Suite puts One Thousand Checks at a Click.

Click here for more information.

Quality Assurance in a Click

Request a Demo

About Qomply

Qomply empowers financial firms of all sizes to meet their regulatory transaction reporting requirements (MiFID, EMIR, SFTR, and ASIC) with best-in-class cloud-based technology solutions that are easy to use at affordable price points.

Our award-winning ReportAssure platform, powered by our proprietary assurance engine, delivers one of the most comprehensive arsenals of accuracy checks in the industry, ensuring our customers’ transaction reports are as complete and accurate as possible.

By offering affordable, modular subscriptions, we enable financial firms of all sizes to benefit from high-quality, regulatory reporting technology, choosing from a menu to suit all appetites.

For more information, please contact Qomply, on +44 (0) 20 8242 4789 or

Follow Qomply on social media on Twitter ( and LinkedIn (

Let's Get In Touch!

Want to know more or just want to phone us up for a chat?

+44(0)20 8242 4789