# EMIR FC vs NFC-/NFC+ Thresholds & Delegated Liability (2026)

> Calculate EMIR Refit & EMIR 3.0 NFC+/SFC clearing thresholds (EUR 1B–4B), hedging exemptions, and Article 9(1a) FC mandatory reporting liability.

Canonical: https://regtechcodex.org/briefings/fc-nfc-clearing-threshold-delegated-emir-reporting-liability
Last updated: 2026-11-16T16:24:57.017Z

**Publication:** RegTech Codex
**Category:** Emir Refit Mifir Trade Reporting
**Published:** 2026-11-13T21:55:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Under EMIR Article 9(1a), Financial Counterparties bear statutory legal responsibility for reporting both sides of OTC derivatives traded with NFC- corporates—unless strict onboarding attestations, hedging-exemption math, and AIFM/UCITS rules are tracked.

## Key takeaways

- EMIR classifies counterparties into four buckets: standard Financial Counterparties (FC+), Small Financial Counterparties (FC-), Non-Financials above any threshold (NFC+), and below all thresholds (NFC-).
- Current asset-class Clearing Thresholds (CTs) stand at EUR 1 billion (Credit, Equity), EUR 3 billion (Interest Rate, FX), and EUR 4 billion (Commodity and Emission Allowance derivatives, raised from EUR 3B!).
- Under EMIR Article 9(1a), when an FC trades OTC derivatives with an NFC-, the FC is solely responsible AND legally liable (Field 1.3 ERR = FC LEI) for reporting BOTH counterparties’ legs—unless the NFC- formally opts out to self-report.
- NFC 12-month position calculations exclude objectively risk-reducing commercial treasury hedges, whereas FC- (SFC) calculations must include 100% of both hedging and speculative OTC positions.

## Related financial entities

- **EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting** (EMIR-REFIT-2026) — license: EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting (EMIR-REFIT-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / Bank of England (EU), currently calibrated at T+1 (Trade Repository Reporting SLA) as of October 2026.
- **MiFID II Annex II Elective Professional vs. Retail Client Categorization** (MIFID2-CLIENT-CAT) — license: MiFID II Annex II Elective Professional vs. Retail Client Categorization (MIFID2-CLIENT-CAT) refers to an institutional financial benchmark and regulatory standard monitored by ESMA Directive 2014/65/EU (EU), currently calibrated at EUR 500,000 (Portfolio Size Criterion (2 of 3)) as of October 2026.

## Analysis

Misclassifying a corporate hedging client's **`FC` / `NFC+` / `NFC-`** status during onboarding creates immediate dual-reporting or zero-reporting violations under `EMIR Refit Regulation (EU) 2019/834`, **EMIR 3.0** (`Regulation (EU) 2024/2987`), and [UK FCA EMIR Rules](/regulators/financial-conduct-authority-uk-121). Under **Article 9(1a)**, whenever an EU or UK Financial Counterparty—such as [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [Equiti](/licence-holders/equiti), or a commercial hedging bank—executes an **OTC derivative** with an EEA/UK **`NFC-`**, statutory legal liability (`Field 1.3 Entity Responsible for Reporting`) shifts by operation of law onto the `FC` for **both** sides of the trade! Note carefully how `EMIR FC/NFC` status is completely independent of [MiFID II Elective Professional vs Retail Categorization](/definitions/mifid2-client-cat-mifid-ii-annex-ii-elective-professional-vs-retail-client-categorization). Consult our [EMIR Refit Master Guide 2026](/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026) inside the [EMIR & MiFIR reporting hub](/topics/emir-refit-mifir-trade-reporting).

## Statutory Entity Responsible for Reporting (`ERR`, Field 1.3) Assignment Matrix

Distinguishing **Statutory Liability Transfer** (`Art. 9(1a)–(1d)`) from **Voluntary Contractual Delegation** (`Art. 9(1f)`) determines which `LEI` populates `Field 1.3 (ERR)` versus `Field 1.2 (Report Submitting Entity)`:

| Counterparty Pairing / Vehicle | Scope | `Field 1.3 ERR` (Legally Liable) | `Field 1.2 Submitting Entity` | Who Bears NCA Fine on Failure? |
| :--- | :--- | :--- | :--- | :--- |
| **EU `FC` vs EU `NFC-`** (No opt-out) | **OTC only** (Not ETD!) | **`FC` `LEI` on BOTH reports!** | `FC` `LEI` (or vendor hub `LEI`) | **100% `FC`** (unless caused by false `NFC-` info) |
| **EU `FC` vs EU `NFC-`** (ETD Futures) | **ETD** (`RM`) | Each party is its own `ERR`! | Each party / clearing broker | **Art. 9(1a) covers OTC ONLY!** `NFC-` stays liable on ETD! |
| **3rd-Country `FC` vs EU `NFC-`** | OTC (Conditional) | `EU NFC-` **unless** 3rd-country regime declared equivalent & reports to EU TR | `EU NFC-` (or delegated LP) | **Critical Trap**: UK/US broker != EU `FC` -> `EU NFC-` still owes EU TR! |
| **`UCITS` / `AIF` Fund** | OTC & ETD | **Authorized `ManCo` / `AIFM` `LEI`** | `ManCo` / Admin / Prime Broker | **`ManCo` / `AIFM`** (`Art. 9(1b)-(1c)`) |
| **Voluntary Delegated** (`FC` vs `FC` / Retail) | OTC & ETD | **Client's Own `LEI`** (`1.3 == 1.4`) | Delegated Broker / Vendor `LEI` (`1.2`) | **Client remains 100% legally liable!** |

![Annual EMIR clearing threshold calculation, NFC- vs NFC+ classification, and Article 9(1a) ERR assignment workflow](/api/figure?type=flow&title=Annual%20Clearing%20Threshold%20%26%20Article%209%281a%29%20Liability%20Engine&subtitle=Calculating%2012-month%20month-end%20gross%20notional%20averages%20and%20routing%20mandatory%20NFC-%20dual-leg%20reporting&steps=1.%20Annual%20June%20Calc%3A%3ACompute%2012-month%20avg%20month-end%20notional%20%28exclude%20hedges%20for%20NFC%3B%20keep%20all%20for%20FC%29%7C2.%20Status%20Attestation%3A%3ACollect%20ISDA%2FEMIR%20NFC-%20vs%20NFC%2B%20%26%20Field%201.15%20Hedging%20flags%20%2B%20active%20LEI%7C3.%20OTC%20vs%20ETD%20Split%3A%3AApply%20Art.%209%281a%29%20FC-mandatory%20reporting%20strictly%20to%20EEA%2FUK%20OTC%20trades%7C4.%20Twin-Report%20Mirror%3A%3AGenerate%20FC%20Leg%20%2B%20Mirrored%20NFC-%20Leg%20%28same%20UTI%2C%20inverted%20BYER%2FSLLR%20%26%20MtM%29&metrics=CREDIT%20%26%20EQUITY%20CT%3A%3AEUR%201.0B%3A%3AGross%20Notional%2012-Month%20Average%7CRATES%20%26%20FX%20CT%3A%3AEUR%203.0B%3A%3AGross%20Notional%2012-Month%20Average%7CCOMMODITY%20%26%20EMISSION%3A%3AEUR%204.0B%3A%3ARaised%20Under%20Reg%20%28EU%29%202022%2F2311%7CCALCULATION%20CADENCE%3A%3AEvery%2012%20Mos%3A%3AImmediate%20NCA%20%2B%20ESMA%20Notice%20If%20Breached)

## Two Classic Legal Traps: ETD Carve-Out & Third-Country UK/US Brokers!

Corporate treasurers at European `NFC-` manufacturers fall into two recurring compliance traps: first, `EMIR Article 9(1a)` transfers mandatory reporting to the `FC` **exclusively for OTC derivatives**—if that same `NFC-` trades listed commodity or FX futures (`ETD`) on Eurex, the `NFC-` remains legally responsible for reporting its own `ETD` leg unless it signs a separate contractual delegation addendum! Second, post-Brexit, a **UK-only or US-only broker** is a *third-country entity*, NOT an EU `FC`—meaning an EU `NFC-` hedging FX with a London-booked bank **still owes its own EU EMIR report** to an ESMA Trade Repository!

## 12-Month Aggregate Month-End Clearing Threshold Formula (`FC` vs `NFC`)

Group treasury engines compute annual asset-class clearing-threshold positions ($P_a$, including EMIR 3.0 enhancements focusing uncleared OTC aggregation for NFCs) across $M = 12$ month-end snapshots:

```formula
P_NFC(a) = (1 / 12) * sum_(m=1..12) sum_(e in Group_Uncleared_OTC(a, m)) Notional_EUR(e) * (1 - I_risk_reducing_hedge(e))
P_FC(a) = (1 / 12) * sum_(m=1..12) sum_(e in Group_All_OTC(a, m)) Notional_EUR(e) (Zero Hedging Deduction for FCs!)

Thresholds_EUR = { Credit: 1e9, Equity: 1e9, Rates: 3e9, FX: 3e9, Commodity_Emissions: 4e9 }
Is_NFC_Plus = max_(a) I( P_NFC(a) > Thresholds_EUR[a] ) (Clears breached class a; Self-reports ALL classes!)
Is_FC_Plus = max_(a) I( P_FC(a) > Thresholds_EUR[a] ) (Clears ALL clearable classes!)

Worked Corporate Treasury (EUR 6.2B Gross FX Forwards, 85% Documented IFRS 9 Commercial Export Hedges):
 Non-Hedge Speculative Avg = 6.2B * 0.15 = EUR 0.93B (<= EUR 3.0B FX Threshold) -> Remains NFC- (EU Bank Reports OTC Both Legs!)
```

![Distribution of EMIR Article 9(1a) and delegated reporting operational failures across corporate and fund counterparties](/api/figure?type=bars&title=Operational%20Failures%20in%20Article%209%281a%29%20%26%20Fund%20Reporting&subtitle=Root%20causes%20of%20misreporting%20across%20FC-to-NFC-%20corporate%20books%20and%20AIFM%2FUCITS%20structures&steps=Lapsed%20NFC-%20Client%20LEI%3A%3A38.4%25%20hit%20TR%20NACKs%20on%20NEWT%2FMODI%20because%20corporate%20let%20LEI%20lapse%7CUK%2FNon-EEA%20Broker%20Trap%3A%3A27.1%25%20EU%20NFC-%20assumed%20UK%20bank%20satisfied%20EU%20TR%20obligation%7CETD%20Assumed%20Covered%3A%3A20.6%25%20forgot%20Art.%209%281a%29%20applies%20strictly%20to%20OTC%20%28not%20ETDs%29%7CWrong%20ERR%20on%20Sub-Funds%3A%3A13.9%25%20populated%20Fund%20LEI%20instead%20of%20AIFM%2FManCo%20LEI%20in%20Field%201.3&metrics=LEI%20UPFRONT%20RULE%3A%3AArt.%209%281a%29%20Duty%3A%3ANFC-%20Must%20Maintain%20Renewed%20LEI%20for%20FC%7CFIELD%201.15%20HEDGE%20TAG%3A%3ATrue%20%2F%20False%3A%3ARequired%20on%20Every%20NFC%20Trade%20Leg%7CNON-REPORTING%20NOTICE%3A%3AAnnual%20June%3A%3ANotify%20ESMA%20%2B%20NCA%20Only%20If%20Threshold%20Crossed%7CNATURAL%20PERSON%20SCOPE%3A%3ARetail%20%3D%20Outside%3A%3APrivate%20Retail%20Traders%20Are%20Not%20EMIR%20%22Undertakings%22)

## Retail Natural Persons vs Sole-Trader "Undertakings"

Under ESMA Q&As, **private retail individuals** trading CFDs for personal accounts are *not* "undertakings" (`NFCs`)—so the retail CFD broker reports a **single-sided** report (`Field 1.9 Counterparty 2 ID Type = False`, populated with `LEI of Broker + Internal Client Code`, max `72` chars) and **never** submits a second mirrored client leg! By contrast, a small incorporated family-office LLC or commercial sole-proprietor hedging business FX **is** an `NFC-` undertaking requiring a `GLEIF LEI` and **two** mirrored `Art. 9(1a)` legs.

## Linking Clearing Thresholds to LEI Renewals, Retail CFDs & Breach Rules

Connect `FC/NFC` classification directly to [GLEIF LEI lapsed-status rejection guards](/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting), [retail CFD and rolling-spot FX single-vs-dual reporting](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting), and [Entity Responsible for Reporting NCA breach notifications](/briefings/emir-significant-reporting-issues-nca-entity-responsible-breach).

## Frequently asked questions

### What are the five current EMIR Clearing Thresholds in euros?

Based on aggregate 12-month average month-end gross notional value: EUR 1 billion for Credit derivatives, EUR 1 billion for Equity derivatives, EUR 3 billion for Interest Rate derivatives, EUR 3 billion for Foreign Exchange derivatives, and EUR 4 billion for Commodity and Emission Allowance derivatives (raised from EUR 3 billion under Commission Delegated Regulation (EU) 2022/2311).

### What happens if an NFC exceeds the threshold in only ONE asset class (vs EMIR 3.0)?

For NFCs, breaching a clearing threshold in one asset class triggers clearing obligations only in that breached asset class (unlike FCs, where breaching ANY single asset class makes the FC an FC+ subject to clearing across ALL clearable asset classes!). Furthermore, once an NFC breaches ANY single class, it becomes an NFC+, ending the FC’s mandatory Article 9(1a) bilateral reporting duty across all OTC classes!

### Who is the legally liable Entity Responsible for Reporting (ERR) for UCITS and AIFs?

Under EMIR Refit Articles 9(1b)–(1d), the UCITS Management Company is statutorily responsible and legally liable for reporting OTC derivatives of the UCITS fund, and the Alternative Investment Fund Manager (AIFM) is statutorily responsible and liable for reporting OTC derivatives of the AIF (Field 1.3 ERR = ManCo/AIFM LEI, Field 1.4 Counterparty 1 = Fund Sub-LEI).

### What obligations fall on the NFC- corporate when the FC reports on its behalf under Article 9(1a)?

Under EMIR Article 9(1a) subparagraph 2 and ITS 2022/1860, the NFC- remains legally obligated to provide the FC with the data details the FC cannot reasonably know on its own (specifically: an active renewed GLEIF LEI, its NFC- status confirmation, corporate sector, and whether the trade is directly linked to commercial or treasury financing activity in Field 1.15!).


## Source URLs

- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/clearing-thresholds
- https://eur-lex.europa.eu/eli/reg/2019/834/oj
- https://eur-lex.europa.eu/eli/reg/2024/2987/oj

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). FC, SFC & NFC-/NFC+ Clearing Thresholds: EMIR Article 9(1a) Delegated Liability. RegTech Codex. https://regtechcodex.org/briefings/fc-nfc-clearing-threshold-delegated-emir-reporting-liability
- Canonical article: [FC, SFC & NFC-/NFC+ Clearing Thresholds: EMIR Article 9(1a) Delegated Liability](https://regtechcodex.org/briefings/fc-nfc-clearing-threshold-delegated-emir-reporting-liability)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
