The Bank of England has published a policy statement setting out its response to consultation feedback and confirming final rule amendments to UK EMIR trade repository reporting requirements within its remit for central counterparties. The changes are intended to clarify requirements and reduce the need for reporting workarounds, and the implementation date has been moved to 26 January 2026. The final rules add “Execution agent” as a new reporting field (Field 30) in Table 3 of the annexes to the reporting technical standards and correct a cross-referencing error in Annex B relating to Unique Transaction Identifiers. Minor adjustments were also made to validation rules, including changes affecting fields 5 (Post-Trade Risk Reduction ID) and 45 (Early Termination Date), and amendments designed to avoid report rejections based on the status of the Execution Agent Legal Entity Identifier in Tables 1 and 3. Ten responses were received and all supported the substance of the changes, but trade repositories requested more time to implement and test updates, prompting the revised go-live date; final validation rules and XML reporting schemas (incoming and outgoing messages) have been published to support implementation. The amendments come into force on 26 January 2026. Requests for additional schema changes and clarification on validation rules for the UTI field were treated as outside the scope of the consultation, but the Bank indicated these may be considered in future.
Bank of England 2025-08-08
Bank of England finalises UK EMIR trade repository reporting changes and delays implementation to 26 January 2026
The Bank of England has issued a policy statement confirming final amendments to UK EMIR trade repository reporting requirements for central counterparties, effective 26 January 2026. Key changes include the addition of an "Execution agent" reporting field, correction of a cross-referencing error, and minor validation rule adjustments. The final validation rules and XML reporting schemas have been published to aid implementation.