FX Compliance Reporting Under EMIR: Obligations for Non-Financial Counterparties

EMIR — the European Market Infrastructure Regulation (Regulation (EU) No 648/2012) — was introduced in the aftermath of the 2008 financial crisis to bring transparency and risk management requirements to the over-the-counter derivatives market. FX forwards and options used by corporate treasury teams for hedging fall within EMIR's scope as OTC derivatives, meaning businesses that execute FX hedging transactions have ongoing EMIR compliance obligations that many finance teams have not fully mapped. The introduction of EMIR Refit (Regulation (EU) 2019/834) and the UK's parallel UK EMIR regime post-Brexit added further complexity. This article provides a practical guide to EMIR's FX reporting obligations for non-financial counterparties.

Are You Subject to EMIR Reporting?

EMIR applies to counterparties established in the EU (for EU EMIR) and in the UK (for UK EMIR). Non-financial counterparties (NFCs) are entities that are not financial counterparties — broadly, corporates that are not banks, investment firms, or insurance companies. NFCs are categorised into two tiers based on their OTC derivative position sizes relative to clearing thresholds:

• NFC-: Non-financial counterparties whose OTC derivative positions across all asset classes (including FX) are below all clearing thresholds. These entities have reporting obligations but are exempt from the mandatory clearing and bilateral margin requirements that apply to financial counterparties.
• NFC+: Non-financial counterparties whose positions exceed one or more clearing thresholds. NFC+ entities are subject to clearing obligations and bilateral margining requirements similar to financial counterparties.

The clearing thresholds for FX derivatives under EMIR Refit are EUR 3 billion gross notional for FX derivatives. Most corporate treasury hedging programmes — including those run by mid-size iGaming operators, crypto businesses, and offshore holding structures — remain well below EUR 3 billion in FX derivative notional and are therefore NFC- entities with reporting obligations but no clearing obligation. NFC- status must be recalculated at least annually and notified to ESMA (for EU EMIR) or the FCA (for UK EMIR) if thresholds are breached.

The Trade Reporting Obligation

The EMIR trade reporting obligation requires both counterparties to an OTC derivative transaction to report details of that transaction to an authorised trade repository no later than the business day following execution (T+1). The report must include a comprehensive set of data fields covering: counterparty identifiers (LEI — Legal Entity Identifier), transaction identifiers (UTI — Unique Transaction Identifier), trade date and time, contract type, asset class, underlying currency pair, notional amount, maturity date, price, and — for modifications — modification or termination event type.

Under EMIR Refit, the reporting obligation was significantly expanded. The number of reportable data fields increased from 85 to 203 fields. The requirement to report using ISO 20022 XML format was introduced (phased in from April 2024 for EU EMIR and September 2024 for UK EMIR). The UTI generation and sharing process was clarified: for OTC derivatives executed with a financial counterparty, the financial counterparty generates the UTI and communicates it to the NFC before the reporting deadline. This is the delegation model that most corporate treasury teams rely upon.

Delegation of Reporting

An NFC may delegate the actual submission of its EMIR trade reports to its financial counterparty. Delegation is available under both EU EMIR (Article 9(1a)) and UK EMIR, and it is the standard arrangement for corporate clients executing FX derivatives with regulated dealers. Under delegation: the financial counterparty (e.g., CCYFX as a regulated FCA-authorised EMI acting as the transaction counterparty) submits the trade report to the trade repository on behalf of the NFC, using data fields provided and agreed with the NFC. Critically, delegation does not transfer liability — if the report is incorrect or late, the NFC remains legally responsible. The NFC must therefore maintain oversight of its delegated reporting arrangements, including periodic reconciliation of reported trades against its own records.

The practical implication is that businesses using CCYFX for FX forwards and options should: (a) ensure they have an LEI number (obtainable from the Global LEI System at relatively low annual cost); (b) confirm the delegation arrangement with CCYFX at account inception; (c) maintain their own trade blotter to reconcile against reported trades; and (d) confirm annually that their NFC- status has been recalculated and remains below clearing thresholds.

FX Spot Transactions: Exempt from EMIR

One important carve-out from EMIR scope is FX spot transactions. Under EMIR, FX spot contracts with settlement within T+2 business days (for major pairs) or T+7 for "exotic" pairs are explicitly excluded from the definition of derivative financial instruments for EMIR purposes. This means that SEPA payments, same-day currency conversions, and standard spot FX transactions converting one currency balance to another at spot are not reportable under EMIR. Only FX forwards (settlement beyond T+2), FX swaps, FX options, and currency swaps fall within EMIR scope.

This distinction has practical implications for businesses that use FX primarily for payment execution (converting currency immediately at spot to fund a payment) rather than for hedging future flows. If all FX activity is spot, EMIR reporting obligations do not arise. The obligation is triggered once the first forward or option is executed.

UK EMIR Post-Brexit Divergence

Following Brexit, the UK retained EMIR requirements in domestic law as UK EMIR, initially as retained EU law under the European Union (Withdrawal) Act 2018. The FCA and HM Treasury have progressively diverged UK EMIR from EU EMIR through the UK EMIR Refit (which came into effect September 2024) and subsequent technical standards. Key UK-specific differences include: UK-based trade repositories (DTCC, ICE TR, and others operating under FCA authorisation rather than ESMA recognition), the requirement to use the FCA's version of the ISO 20022 reporting format (which differs in some fields from ESMA's version), and the FCA's LEI validation process. Businesses with both EU and UK entity locations hedging through both EU-established and UK-established counterparties need to track obligations under both regimes separately.

Common Compliance Failures and How to Avoid Them

The most common EMIR compliance failures for NFC corporate clients that GP encounters in practice are:

• No LEI registered: Reports cannot be submitted without an LEI. LEIs must be renewed annually; an expired LEI renders the entity non-reportable.
• No delegation agreement in place: Executing FX forwards without confirming the delegation arrangement means neither party may be reporting — creating a bilateral reporting failure.
• Failure to track NFC status annually: A business whose FX hedging programme grows may cross the NFC+ threshold without realising it, triggering clearing obligations it is not set up to meet.
• No reconciliation process: Delegating reporting without reconciling means errors in counterparty-reported data go undetected. FCA supervisory reviews of NFC reporting practices have identified this as a material gap.

At CCYFX, our MLRO and compliance team (led by GP) works with clients to ensure EMIR delegation arrangements are properly documented and that clients have the tools to maintain compliance oversight. We provide clients with trade confirmation data in a format suitable for reconciliation against trade repository reports. Speak to our compliance team if you are uncertain about your EMIR obligations.