UK EMIR Trade Repository Data
Under Article 9 of UK EMIR the Bank of England and the Financial Conduct Authority (FCA) share responsibilities for the derivatives reporting obligation.
The Bank is responsible for the framework for derivatives reporting as they apply to central counterparties (CCPs). The FCA is responsible for the reporting framework for all other counterparties. Our objective is to keep the reporting framework identical for all UK reporting counterparties.
On a daily basis relevant UK firms report details of any derivatives transactions they have entered into. These cover five asset classes:
- interest rates
- foreign exchange
- commodities
- credit default swaps
- equities
These can be transacted bilaterally or through futures exchanges.
Information for reporting counterparties:
UK EMIR Breach notification form
CCPs can use the UK EMIR breach notification form to notify us about any errors or omissions in their reports under Article 9 of UK EMIR.
Any enquiries relating to UK EMIR should be sent to emirreporting@bankofengland.co.uk.
Reporting Regime
The formal reporting requirements are set out in The Bank’s Standards Instrument.
To support CCPs meeting the requirements, we have guidance in the form of questions and answers (Q&As) and technical specification documents to support implementation:
XML schemas under UK EMIR
The following documents have been amended to support implementation following the publication of a Policy Statement and final rules on the proposed changes to the UK EMIR Trade Repository reporting requirements (see 'Latest news').
The technical specification documents:
XML schemas under UK EMIR, together “the XML Schemas”
Latest news
October 2025 – UK EMIR reporting requirements: Finalisation of new Q&As
On 31 October 2025, together with the FCA, we published new Q&As (4.14 and 11.7) and a summary of the feedback to our consultation.
August 2025 – UK EMIR reporting requirements: Publication of a Policy Statement and final rules and launch of additional draft Q&As for consultation
On 8 August 2025, together with the FCA, we published a Policy Statement and final rules on the proposed changes to the UK EMIR Trade Repository reporting requirements. These will come into force on 26 January 2026. To support industry implementation, we published the final Validation Rules (applicable from 26 January 2026) and XML reporting schemas: Incoming messages to TRs and Outgoing messages from TRs (applicable from 26 January 2026).
Also today, we and the FCA are separately launching a consultation on additional guidance (in the form of questions and answers), addressing issues identified by industry. The consultation will remain open until 12 September 2025.
June 2025 – Consultation on proposed amendments to the UK EMIR Trade Repository reporting requirements
On 6 June 2025, together with the FCA, we launched a consultation on proposed amendments to the UK EMIR reporting requirements to make it work more efficiently, following feedback from industry.
The consultation outlines joint proposals to amend our respective Standards Instruments (“the Technical Standards”). To ensure consistency, the proposed amendments also require corresponding changes to the draft UK EMIR Validation Rules (applicable from 1 December 2025) and draft XML reporting schemas: Incoming messages to TRs and Outgoing messages from TRs (applicable from 1 December 2025) for which we are also seeking feedback. The consultation will remain open until Monday 30 June.
September 2024 – New UK EMIR reporting regime comes into force
On 30 September 2024 the revised derivate reporting regime came into force. These changes align the UK derivatives reporting framework with CPMI-IOSCO Technical Guidance on the Harmonisation of critical OTC derivatives data elements, where appropriate, to ensure a more globally consistent dataset. For more information see the joint Bank/FCA Policy Statement.
July 2024 – UK EMIR reporting Q&As: Finalisation of second consultation and publication of finalised guidance
On 26 July 2024, alongside the FCA, we published an update to the UK EMIR Validation Rules (applicable from 30 September 2024) to ensure consistency with the finalised guidance on UK EMIR Reporting, which was published on 12 July 2024. We do not intend to make any further changes to the validation rules (or schemas) ahead of 30 September 2024. Today, we also published an additional finalised Q&A under topic 10 (Q&A 10.9) of the finalised guidance, following a joint consultation with the FCA.
On 12 July 2024, alongside the FCA, we published finalised guidance and a summary of feedback from the second consultation on guidance to support implementation of the amended UK EMIR reporting requirements that will go-live on 30 September 2024. The guidance is in the form of Questions and Answers (Q&As), grouped into relevant topics. Today we also published updated Schemas and finalised changes to the UK EMIR Validation Rules (applicable from 30 September 2024).
May 2024 – UK EMIR reporting Q&As: Finalisation of first consultation and publication of second consultation
On 2 May 2024, alongside the FCA, we published finalised guidance and a summary of feedback from the first consultation on guidance to support implementation of the amended UK EMIR reporting requirements that will go-live on 30 September 2024. The guidance is in the form of Questions and Answers (Q&As), grouped into relevant topics. Today we also published a second consultation on the remaining topics. In certain circumstances, the draft Q&As also require a corresponding change to the UK EMIR Validation Rules (applicable from 30 September 2024), which we are also seeking feedback on.
We are consulting jointly with the FCA on guidance to support implementation of the amended UK EMIR reporting requirements that will go-live on 30 September 2024. The draft guidance is in the form of Questions and Answers (Q&As), grouped into relevant topics. In certain circumstances, the draft Q&As also require a corresponding change to the UK EMIR Validation Rules (applicable from 30 September 2024), which we are also seeking feedback on.