The European Market Infrastructure Regulation (EMIR) introduced mandatory trade reporting for OTC derivatives as one of the G20's post-crisis reform commitments, following the 2008 financial crisis's demonstration that regulators had almost no visibility into the scale and interconnectedness of the OTC derivatives market. Under EMIR, both counterparties to a derivatives trade are required to report to a registered trade repository — a single-sided report would not give regulators the bilateral view they needed. The result is a reporting regime that is simultaneously broader in scope and more complex to operate than MiFID II transaction reporting.

Who Must Report

EMIR's reporting obligation falls on any financial counterparty (FC) or non-financial counterparty (NFC) that enters into a derivative contract. Financial counterparties include banks, investment firms, insurance companies, UCITS funds, pension funds, and alternative investment funds. Non-financial counterparties are corporate entities that use derivatives — for example, an airline hedging jet fuel costs with oil futures, or a manufacturer hedging FX exposure.

The distinction between FC and NFC matters beyond reporting. NFCs that exceed certain clearing thresholds (based on the gross notional of their derivative positions) become NFC+, which triggers the clearing obligation for standardised derivatives and margin requirements for uncleared derivatives. Those below the threshold are NFC-, with lighter obligations.

Post-Brexit, the UK adopted its own version of EMIR (UK EMIR), administered by the FCA. UK firms report to trade repositories registered with the FCA, while EU counterparties continue to report under EU EMIR to ESMA-registered repositories. Cross-border trades between UK and EU counterparties create a dual-reporting scenario: both counterparties must report to their respective regime.

What Must Be Reported

EMIR requires reporting of all OTC derivatives — interest rate, credit, equity, FX, and commodity — as well as exchange-traded derivatives (ETDs). Every new trade must be reported by T+1. Modifications to existing trades (amendments, partial terminations) must be reported promptly. Full terminations and expirations must also be reported. The obligation to report is ongoing: the life of every contract in the trade repository must be kept current.

The data fields required under EMIR are extensive, covering counterparty information, contract details, clearing information, and risk mitigation fields. Key fields include:

  • UTI (Unique Trade Identifier): a code that uniquely identifies the trade across both counterparty reports
  • LEI: identifying both the reporting counterparty and the other counterparty
  • UPI (Unique Product Identifier): identifying the derivative product type
  • Notional amount and currency
  • Maturity date and trade date
  • Clearing status: whether the trade is centrally cleared and, if so, through which CCP
  • Collateral and margin: type of collateral arrangement (bilateral, CCP), margin posted and received
  • Valuation: current mark-to-market value and the date of valuation

Trade Repositories

Reports must be submitted to a trade repository (TR) registered with the relevant authority. In the EU, ESMA maintains the register of authorised TRs; in the UK, the FCA does the same. The major TRs in the market include DTCC Data Repository, REGIS-TR (operated by Clearstream), and ICE Trade Vault. Each TR provides connectivity, data validation, and access to the regulatory data it holds — ESMA and NCAs can query TR data to monitor systemic risk and detect anomalies.

Unlike MiFID II, where the reporting obligation falls on one party and the ARM relays to the NCA, EMIR requires both counterparties to report independently. Each counterparty chooses its own TR, which creates the possibility that counterparty A reports to DTCC and counterparty B reports to REGIS-TR. Regulators address this through a TR reconciliation process — TRs are required to reconcile their data with each other and flag paired and mismatched trades.

The UTI Pairing and Matching Problem

The Unique Trade Identifier is central to EMIR's bilateral architecture. For regulators to aggregate the two sides of a trade into a single view, both counterparties must report the same UTI. If counterparty A and counterparty B each generate their own UTI independently, regulators cannot match the two sides. The UTI must therefore be agreed between the counterparties before reporting.

The UTI generation hierarchy is: the CCP generates the UTI for centrally cleared trades; for uncleared trades, the parties follow the CPMI-IOSCO guidance that establishes a waterfall — the reporting counterparty (or the party that made the trade available on an electronic platform) generates the UTI and communicates it to the other party. In practice, implementation of this hierarchy has been inconsistent, and a significant proportion of EMIR reports historically showed mismatches — the same trade reported by two counterparties with different UTIs, or with matching UTIs but mismatching economic terms.

The matching rate for EMIR reports has been a persistent regulatory concern. ESMA has published data showing that a large fraction of EU derivatives trades cannot be matched across the two legs. The causes range from UTI generation failures to field-level discrepancies (different notional conventions, different maturity date formats) to entirely missing counterparty reports.

EMIR Refit

EMIR Refit (effective in the EU from April 2024 and in the UK from September 2024) was the most significant overhaul of EMIR trade reporting since the original 2014 go-live. The key changes introduced by Refit include:

  • Expanded field set: The number of reportable fields increased substantially (to over 200 in the EU), capturing more granular information about derivative products, collateral, and margin.
  • ISO 20022 XML format: Refit mandated a move to the ISO 20022 message standard, replacing the legacy CSV format. This required significant technology investment by both firms and trade repositories.
  • Mandatory delegation for FCs: Financial counterparties became responsible for reporting on behalf of NFC- counterparties, removing the reporting burden from smaller corporate end-users who had historically struggled with it.
  • UPI requirement: Trades must now be identified using the ANNA-DSB issued Unique Product Identifier, adding a new reference data dependency.
  • Reconciliation improvements: The Refit framework strengthened the bilateral reconciliation process between TRs and introduced tighter tolerances for field mismatches.

Refit implementation was one of the largest change programmes in capital markets operations in 2023 and 2024, requiring firms to upgrade their trade reporting infrastructure, update reference data feeds, renegotiate delegation agreements with NFC- counterparties, and test connectivity with trade repositories under the new format.

Valuation and Collateral Reporting

EMIR's ongoing reporting obligations go beyond trade inception. Firms must report the current mark-to-market valuation of each outstanding derivative on a daily basis. For centrally cleared trades, the CCP-generated valuation is typically used. For uncleared bilateral trades, firms use their own front-office valuations. Valuation reporting is technically demanding — it requires a feed from the firm's risk systems to the reporting infrastructure that updates daily for every outstanding contract.

Collateral reporting is equally demanding. Firms must report the value and type of collateral posted and received under each collateral arrangement. For trades subject to the EMIR margin rules, this includes initial margin and variation margin. The collateral data must be reported daily and must reconcile with the actual collateral management records held in the firm's operations systems.

In practice, valuation and collateral reporting are among the most error-prone aspects of EMIR compliance. Discrepancies between the valuation in the TR and the firm's own systems, or between collateral reported and collateral actually posted, are common findings in regulatory reviews and internal audits of EMIR compliance programmes.