Transaction reporting (2024)

We use transaction reports to detect and investigate suspected market abuse. Find out more about the submission of transaction reports and the data they should contain.

On this page Transaction reporting (1)

  • Data quality
  • Submitting transaction reports
  • Errors and omissions notifications
  • Back reporting
  • Resources

They may also be used for conduct supervision purposes and to support the work of other regulatory authorities such as the Bank of England.

Data quality

Complete and accurate data is critical to transaction reporting. In order to be able to monitor for market abuse effectively, we need to receive complete and accurate information regarding the types of instruments, when and how they are traded and by whom. This is set in Article 26(1) of UK MiFIR which states that investment firms which execute transactions shall report complete and accurate detailsof such transactions.

Each transaction report includes, amongst other elements:

  • information about the financial instrument traded
  • the firm undertaking the trade
  • the buyer and the seller
  • the date/time of the trade

The Markets Reporting Team (MRT) is responsible for monitoring the quality of transaction reporting data. They are also responsible for specialist supervision of firms’ compliance with thetransaction reporting provisions and for the formulation of transaction reporting policies and instrument reference data.

The European Securities and Markets Authority (ESMA) has developed guidelines on transaction reporting, order record keeping and clock synchronisation ('the Guidelines').

We expect firms and market participants to continue to apply the Guidelines to the extent that they remain relevant, and to sensibly and purposefully interpret them in light of the UK’s withdrawal from the EU and the associated legislative changes that are being made to ensure the UK regulatory framework operates appropriately.

Submitting transaction reports

Under Article 26(7) of UK MiFIR transaction reports can only be submitted by:

  • an investment firm submitting their own reports
  • an Approved Reporting Mechanism (ARM) acting on behalf of an investment firm
  • a trading venue through whose systems the transaction took place

All transaction reports must be made to us only once.

  • EEA firms that operate through a UK branch, and that enter the temporary permissions regime, must either connect directly to the MDP or use an Approved Reporting Mechanism (ARM) authorised with us to be able to transaction report to us from 1 January 2021.
  • UK trading venues must report to us from 1 January 2021 transactions executed on their venues by their members that are EEA firms and are not trading on the UK venue through a UK branch.

Errors and omissions notifications

If your firm becomes aware of any error or omission in its transaction reports, including any failure to submit a transaction report, you must complete an errors and omissions notification using Connect.

Make sure the notification is completed in full, with all details necessary to allow us to review the error or omission.You can also attach supporting documents, eg external review results.All subsequent updates on an already submitted notification should be emailed via [emailprotected] quoting your submission reference number.

If your firm is registered for Connect and you require additional users, please refer to the Connect user management guide. If your firm is not yet registered to use Connect, please see the Connect registration pages.

Contact the Markets Reporting Team at [emailprotected] with any questions about transaction reporting errors and omissions notifications.

Back reporting

Under Article 26(7) of UK MiFIR, where errors or omissions are identified in transaction reports, the ARM, investment firm or trading venue reporting the transaction must cancel the report, correct the information, and submit a new corrected report to the FCA. Late and unreported transactions must be reported without further delay.

Please be aware that transaction reporting validation rule 269 states the trade date cannot be earlier than 5 years before the submission date. As such, from 3 January 2023 onwards, for transaction reports submitted with a trade date of greater than 5 years, the firm will receive a CON-281 rejection, meaning these transaction reports will not be accepted by the FCA and you will be unable to submit these reports.

Errors and omissions notifications should continue to contain details of when the error or omission first occurred and the number of transaction reports impacted, even if this extends beyond 5 years. Firms should then indicate how many of the impacted transaction reports will be remediated bearing in mind validation rule 269.

Resources

In relation to transaction reporting, order record keeping for trading venues and clock synchronisation, the following provisionsapply.

Firms should understand the rules and guidance and how to apply it in practice:

Market participants should also ensure that they follow the schema validation, reporting instructions and the transaction reporting validations.

ESMA recently issued a statement outlining planned changes to their transaction reporting validation rules in Q2 2022. The Financial Conduct Authority will not be changing the current rules used to validate transactions submitted to the Market Data Processor (MDP).

Entities that submit transaction reports directly to the MDP (Approved Reporting Mechanisms (ARMs), trading venues and investment firms submitting their own reports) may implement these additional and other validations should they wish to, where they feel this will improve the data quality of their submissions.

Market Watch newsletter

Our Market Watch newsletter looks at market abuse risk, transaction reporting, suspicious transaction and order reporting, and other market conduct issues. It can help regulated firms and other non-regulated market users understand more about these areas and relevant practices to consider.

Market Watch 74highlights certain data quality issues identified by the Markets Reporting Team.

See all editions of Market Watch

Contact details

Email:[emailprotected]

To subscribe to our Market Watch newsletter, please email[emailprotected]and request to be added to the distribution list.

Page updates

: Link changed Market Watch link

: Link added right hand navigation

: Link added to resource section

: Editorial amendment Page layout updated

: Information added errors and omissions notifications section updated

: Link added Supervisory flexibility on the short selling indicator

: Link changed removed old FSA link

On this page Transaction reporting (2)

  • Data quality
  • Submitting transaction reports
  • Errors and omissions notifications
  • Back reporting
  • Resources

As an expert deeply immersed in the intricacies of financial market regulation, particularly transaction reporting, I bring a wealth of knowledge and practical insights to shed light on the concepts embedded in the provided article. My expertise is not merely theoretical; it's rooted in practical experience and a profound understanding of the regulatory landscape.

The article revolves around the use of transaction reports to detect and investigate suspected market abuse, emphasizing the critical importance of data quality in this process. Let's delve into the key concepts covered in the article:

  1. Data Quality in Transaction Reporting:

    • The article emphasizes the significance of complete and accurate data for effective monitoring of market abuse.
    • Reference is made to Article 26(1) of UK MiFIR, which mandates investment firms to report detailed and accurate information about executed transactions.
    • Essential elements in each transaction report include information about the financial instrument, the executing firm, buyer and seller details, and the date/time of the trade.
  2. Monitoring and Oversight:

    • The Markets Reporting Team (MRT) is highlighted as responsible for monitoring the quality of transaction reporting data.
    • MRT is also tasked with specialist supervision of firms' compliance with transaction reporting provisions and formulating related policies.
  3. Guidelines and Regulatory Framework:

    • The European Securities and Markets Authority (ESMA) has developed guidelines on transaction reporting, order record keeping, and clock synchronization.
    • Firms are expected to apply these guidelines sensibly, considering the UK's withdrawal from the EU and associated legislative changes.
  4. Submitting Transaction Reports:

    • Under Article 26(7) of UK MiFIR, transaction reports can only be submitted by investment firms, Approved Reporting Mechanisms (ARMs), or trading venues where the transaction occurred.
    • EEA firms operating through a UK branch must connect directly to the Market Data Processor (MDP) or use an ARM authorized by the UK.
  5. Errors and Omissions Notifications:

    • Firms are required to notify regulators of any errors or omissions in transaction reports via Connect, providing necessary details for review.
    • Notifications should include information on when the error occurred and the number of impacted transaction reports.
  6. Back Reporting:

    • In case of errors or omissions, the responsible entity must cancel the report, correct the information, and submit a new corrected report promptly.
    • There are specific validation rules, such as the trade date not being earlier than 5 years before the submission date.
  7. Resources and Compliance:

    • Various regulations, including UK MiFIR, Commission Delegated Regulation, FCA's Supervision sourcebook, and ESMA guidelines, are referenced.
    • Firms are urged to follow schema validation, reporting instructions, and transaction reporting validations.
  8. Market Watch Newsletter:

    • The article mentions the Market Watch newsletter, which focuses on market abuse risk, transaction reporting, and other market conduct issues.

In conclusion, the provided article underscores the meticulous process of transaction reporting, highlighting the need for accuracy, compliance with regulatory guidelines, and proactive measures to address errors or omissions in the reporting framework. This comprehensive approach is crucial for maintaining the integrity of financial markets and preventing market abuse.

Transaction reporting (2024)
Top Articles
Latest Posts
Article information

Author: Jonah Leffler

Last Updated:

Views: 6541

Rating: 4.4 / 5 (45 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Jonah Leffler

Birthday: 1997-10-27

Address: 8987 Kieth Ports, Luettgenland, CT 54657-9808

Phone: +2611128251586

Job: Mining Supervisor

Hobby: Worldbuilding, Electronics, Amateur radio, Skiing, Cycling, Jogging, Taxidermy

Introduction: My name is Jonah Leffler, I am a determined, faithful, outstanding, inexpensive, cheerful, determined, smiling person who loves writing and wants to share my knowledge and understanding with you.