# EMIR Refit, MiFIR & ISO 20022 Trade Reporting Guide (2026)

> Master EMIR Refit 203-field ISO 20022 auth.030 XML schemas, ANNA DSB UPI lookups, bilateral UTI pairing waterfalls, MiFIR RTS 22, and T+1 reconciliation.

Canonical: https://regtechcodex.org/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026
Last updated: 2026-11-14T19:41:33.405Z

**Publication:** RegTech Codex
**Category:** Emir Refit Mifir Trade Reporting
**Published:** 2026-11-14T19:20: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

Regulatory derivatives and transaction reporting across EU EMIR Refit, UK EMIR, MiFIR Article 26, CFTC Rewrite, and APAC ISO 20022 mandates now demands deterministic XML schema validation, bilateral UTI/UPI synchronization, and automated T+1 reconciliation.

## Key takeaways

- EU EMIR Refit (effective April 29, 2024) and UK EMIR Refit (effective September 30, 2024) retired legacy CSV/FpML pipes in favor of strict end-to-end ISO 20022 auth.030 XML schemas spanning 203-204 fields.
- Trade Repositories (DTCC GTR, REGIS-TR, UnaVista/LSEG, KDPW) enforce two-stage automated Pairing (on UTI + Counterparty LEIs) and Matching across up to 148 reconcilable economics, valuation, and collateral fields.
- Mandatory ANNA DSB ISO 4914 Unique Product Identifiers (UPIs) and active GLEIF ISO 17442 LEIs block unenriched OTC derivative submissions at the pre-repository XSD/business-rule gateway.
- Under ESMA Guidelines and FCA Market Watch expectations, the Entity Responsible for Reporting (ERR) must notify its National Competent Authority whenever misreporting breaches quantitative materiality thresholds.

## 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.
- **EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting — 2026 Standard** (EMIR-REFIT-2026-STD) — license: EMIR-REFIT-2026 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / Bank of England governing EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting across EU capital markets (T+1 Trade Repository Reporting SLA, October 2026).
- **SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping** (SEC-RULE-17A4-2042) — license: SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping (SEC-RULE-17A4-2042) refers to an institutional financial benchmark and regulatory standard monitored by U.S. Securities and Exchange Commission (US), currently calibrated at $2.3B (Cumulative SEC Fines (95 Actions)) as of October 2026.
- **U.S. CFTC & NFA Compliance Rule 2-9 Swap Dealer & FCM Supervision** (CFTC-NFA-RULE2-9) — license: U.S. CFTC & NFA Compliance Rule 2-9 Swap Dealer & FCM Supervision (CFTC-NFA-RULE2-9) refers to an institutional financial benchmark and regulatory standard monitored by Commodity Futures Trading Commission (US), currently calibrated at $20M (Minimum Adjusted Net Capital) as of October 2026.

## Analysis

Between 2022 and 2026, global derivatives and transaction reporting underwent a synchronized technological convergence: the [US CFTC](https://www.cftc.gov/Data/SwapReports/index.htm) Swap Data Rewrite, [US SEC](/regulators/u-s-securities-and-exchange-commission-141) `Regulation SBSR`, **EU EMIR Refit** (`Regulation (EU) 2019/834` + `RTS 2022/1855` / `ITS 2022/1860`), **[UK FCA](/regulators/financial-conduct-authority-uk-121) / Bank of England UK EMIR Refit**, and synchronized `ISO 20022` rewrites across ASIC, MAS, HKMA ([Hong Kong Monetary Authority](/regulators/hong-kong-monetary-authority-153)), and JFSA replaced fragmented legacy spreadsheets with machine-enforceable XML schemas. Multi-jurisdictional liquidity providers, CFDs/FX brokers, and swap dealers—including [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [Exness](/licence-holders/exness), [ATFX](/licence-holders/atfx), and [AMP Futures](/licence-holders/amp-futures)—now run unified pre-submission validation gateways anchored to [EU & UK EMIR Refit 2026 Standards](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting). Explore every implementation module in the [EMIR Refit & MiFIR reporting hub](/topics/emir-refit-mifir-trade-reporting).

## Global Cross-Regime Derivative & Transaction Reporting Matrix (2026)

Reconciling technical schemas, unique identifiers, and delegation liabilities across the major G20 supervisory perimeters prevents silent cross-border schema collisions:

| Regime & Supervisor | Primary Technical Schema | Field Count | Product & Entity IDs | Inter-TR Pairing & Recon? | Delegation Legal Liability |
| :--- | :--- | :--- | :--- | :--- | :--- |
| **EU EMIR Refit** (ESMA / [AMF](/regulators/amf) / [AFM](/regulators/afm) / [KNF](/regulators/polish-financial-supervision-authority-knf-394)) | `ISO 20022 auth.030.001.03` | **203** (`3` tables) | `ANNA DSB UPI` + `ISIN` + `GLEIF LEI` | **Dual-Sided**: `87` Phase-1 -> `148` Phase-2 fields | `FC` statutorily liable for `NFC-` OTC (`Art. 9(1a)`) |
| **UK EMIR Refit** ([FCA](/regulators/financial-conduct-authority-uk-121) / [PRA](/regulators/prudential-regulation-authority-uk-173) / BoE) | `ISO 20022 auth.030.001.03` (UK XSD) | **204** (+ UK execution agt) | `UPI` + `ISIN` + `LEI` | **Dual-Sided**: UK-TR + inter-TR reconciliation | `FC` liable for `NFC-` OTC; operational delegation retains duty |
| **EU/UK MiFIR Art. 26** (`RTS 22` via `ARM`) | `ISO 20022 auth.016.001.01` | **65** (`T+1` tx) | `ISIN` + `LEI` + Natural Person `CONCAT`/Passport | Single-sided venue/investment-firm cross-check | Investment firm strictly liable (`No ARM shield`) |
| **US CFTC Part 43/45** & [CFTC Rule 2-9](/definitions/cftc-nfa-rule2-9-u-s-cftc-nfa-compliance-rule-2-9-swap-dealer-fcm-supervision) | `ISO 20022 auth.030` (`CDE`) | **128** (`T+1` / `ASAP`) | `UPI` (Rates/Credit/FX/Eq/Commod) + `LEI` | **Single-Sided** (`SD` -> `MSP` -> `FC` reporting hierarchy) | Reporting Counterparty (`RCP`) bears 100% SDR recon duty |
| **APAC Rewrite** (ASIC / MAS / [HKMA](/regulators/hong-kong-monetary-authority-153)) | `ISO 20022` (`ASIC/MAS` 2024–2025) | **104–134** (`CDE`) | `UTI` + `UPI` + `LEI` | Single-sided / Nexus + Delegated `UTI` | Licensed bank/AFSL/CMS firm retains primary supervisory duty |

![End-to-end EMIR Refit and global ISO 20022 trade reporting architecture from OMS execution to T+1 three-way Trade Repository reconciliation](/api/figure?type=flow&title=Unified%20Multi-Regime%20ISO%2020022%20Trade%20Reporting%20Pipeline&subtitle=Enforcing%20pre-submission%20XSD%2Fbusiness-rule%20validation%2C%20ANNA%20DSB%20UPI%2FLEI%20enrichment%2C%20and%20T%2B1%20TR%20reconciliation&steps=1.%20Execution%20%26%20ID%20Sync%3A%3AIngest%20FIX%2FOMS%20trade%3B%20resolve%20Article%207%20UTI%20waterfall%20%26%20ANNA%20DSB%20UPI%7C2.%20ISO%2020022%20Transform%3A%3AMap%20203%2F204%20fields%20into%20auth.030.001.03%20%26%20margin%20auth.108%20XML%7C3.%20Pre-TR%20Rules%20Engine%3A%3ARun%20ESMA%2FFCA%20XSD%20%2B%20450%2B%20conditional%20Action%2FEvent%20%26%20LEI%20status%20checks%7C4.%20T%2B1%20Pairing%20%26%20Recon%3A%3AConsume%20TR%20auth.091%20feedback%3B%20auto-remediate%20Unpaired%20%26%20Unmatched%20breaks&metrics=FIRST-PASS%20NACK%20RATE%3A%3A%3C%200.15%25%3A%3AVia%20Local%20Pre-TR%20XSD%20%26%20Validation%20Table%7CPAIRING%20SLA%20%28T%2B1%29%3A%3A%3E%3D%2099.2%25%3A%3ABilateral%20UTI%20Synchronization%20Rate%7CMATCHING%20TOLERANCE%3A%3A5dp%20%2F%200.005%25%3A%3AESMA%20Phase-2%20Valuation%20%26%20Price%20Bands%7CAUDIT%20WORM%20ARCHIVE%3A%3A5-7%20Years%3A%3AImmutable%20Payload%20%2B%20TR%20ACK%20Lineage)

## Core Architectural Pillars Across Our 19 Silo 3 Technical Briefings

A single broken reference-data join—such as an unrenewed counterparty `LEI`, an Asymmetric `UTI` generated independently by both sides, or a mis-mapped `MODI` vs `CORR` lifecycle combination—cascades into thousands of Trade Repository `NACK` rejections. Our engineering curriculum dissects each failure mode:

- **Schema, Identifiers & Pairing**: Master [203-field ISO 20022 auth.030 XML schema validation](/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields), [Article 7 bilateral UTI generation waterfalls](/briefings/bilateral-uti-generation-waterfall-emir-refit-article-7-tiebreak), [ANNA DSB ISO 4914 UPI & CFI product validation](/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation), [inter-TR pairing and Phase-2 valuation matching tolerances](/briefings/emir-refit-inter-tr-pairing-matching-valuation-tolerance-bands), and [GLEIF LEI lapsed-status rejection handling](/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting).
- **Lifecycle, Collateral & Asset-Class Mapping**: Implement [Action Type vs Event Type lifecycle state machines](/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro), [daily auth.108 collateral and ISDA SIMM margin reporting](/briefings/daily-collateral-margin-valuation-auth-108-isda-simm-reporting), [ETD trade-level vs position-level compression reporting](/briefings/etd-position-level-vs-trade-level-emir-reporting-compression), [two-leg FX swap and NDF package mapping](/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mapping), and [retail CFD / rolling-spot FX dual EMIR + MiFIR reporting](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting).
- **Cross-Border Divergences & Supervisory Governance**: Reconcile [UK EMIR FCA/BoE vs EU ESMA schema divergences](/briefings/uk-emir-fca-bank-of-england-vs-eu-esma-refit-schema-divergence), [CFTC Part 43/45 CDE and SEC SBSR swap rules](/briefings/cftc-part-43-part-45-cde-swap-data-reporting-sec-sbsr-audit), [ASIC, MAS & HKMA APAC ISO 20022 rewrites](/briefings/asic-mas-hkma-jfsc-apac-otc-derivatives-rewrite-iso-20022-sync), [MiFIR RTS 22 natural-person CONCAT transaction reporting](/briefings/mifir-rts-22-article-26-arm-transaction-reporting-national-id), [SFTR ISO 20022 repo & securities lending reporting](/briefings/sftr-iso-20022-repo-securities-lending-uti-collateral-reuse), [FC/NFC- clearing thresholds & delegated liability](/briefings/fc-nfc-clearing-threshold-delegated-emir-reporting-liability), [NCA Significant Reporting Issue breach notifications](/briefings/emir-significant-reporting-issues-nca-entity-responsible-breach), [SEC 17a-4 & CFTC 1.31 WORM trade reconstruction](/briefings/sec-rule-17a-4-cftc-1-31-worm-audit-trail-trade-reconstruction), and [automated T+1 three-way completeness reconciliation](/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine).

## Quantitative Reporting Health &NCA Material-Breach Threshold Formula

Under ESMA Final Report Guidelines (`Section 9.3`) and [EMIR Refit 2026 Benchmark Thresholds](/definitions/emir-refit-2026-2026-benchmark-standard), an Entity Responsible for Reporting (`ERR`) evaluates monthly misreporting volumes across three buckets ($A$: timely/action reporting, $B$: valuation/margin, $C$: reconciliation breaks) to detect mandatory **NCA Significant Issue Notifications**:

```formula
Avg_Monthly_Submissions = (1 / 12) * sum_(m=1..12) N_submitted_bucket(m)
Breach_Ratio_Bucket = N_affected_reports / max(1, Avg_Monthly_Submissions)
Notify_NCA_Trigger = I( (N_affected_reports > Num_Floor AND Breach_Ratio_Bucket > 0.15) OR N_affected_reports > Hard_Cap )

ESMA Quantitative Reference Calibration (Illustrative Supervisory Guidance):
 Bucket A/B/C: If affected reports exceed BOTH the absolute count floor AND 15% of 12-month monthly average,
 ERR must promptly file structured Significant Issue Notification with home NCA (and FCA under UK EMIR Market Watch).

Worked Firm Self-Audit (CFD Broker Averaging 400,000 Monthly Reports Discovers Bug Corrupting 78,000 Valuation XMLs):
 Breach_Ratio = 78,000 / 400,000 = 19.5% (> 15.0% materiality threshold) -> Mandatory Prompt NCA Breach Notification + Back-Reporting Plan
```

![Root causes of Trade Repository NACK rejections and inter-TR reconciliation breaks following EMIR Refit go-live](/api/figure?type=bars&title=Post-Refit%20Trade%20Repository%20NACK%20%26%20Recon%20Break%20Drivers&subtitle=Empirical%20share%20of%20T%2B1%20reporting%20exceptions%20across%20European%20and%20UK%20derivative%20counterparties&steps=UTI%20Non-Pairing%20%2F%20Late%20Share%3A%3A34.8%25%20failed%20T%2B1%20pairing%20due%20to%20broken%20bilateral%20UTI%20exchange%7CAction%2FEvent%20Matrix%20Violation%3A%3A26.1%25%20sent%20invalid%20MODI%2FTERM%2FPOSC%20combinations%20or%20prior%20dead%20UTI%7CMissing%20%2F%20Wrong%20ANNA%20UPI%3A%3A21.7%25%20failed%20CFI-to-ISO%204914%20UPI%20attribute%20cross-validation%7CValuation%20%26%20Margin%20Mismatch%3A%3A17.4%25%20breached%20auth.108%20collateral%20or%20MtM%20currency%20tolerances&metrics=AUTH.091%20FEEDBACK%3A%3ADaily%20XML%3A%3AMandatory%20TR%20Rejection%20%26%20Recon%20Ingestion%7CLEGACY%20BACKLOG%3A%3AZero%20Open%3A%3AAll%20Live%20Trades%20Must%20Be%20ISO%2020022%20Native%7CRECORD%20ARCHIVE%3A%3A%3E%3D%205%20Years%3A%3AEMIR%20Art.%209%282%29%20Post-Termination%20Retention%7CFCA%20MARKET%20WATCH%3A%3AActive%20Audit%3A%3APenalizes%20Ignored%20TR%20Exception%20Queues)

## Pre-Submission Reference Data Synchronization (`GLEIF`, `ANNA DSB`, `FIRDS`)

High-maturity RegTech stacks ingest three external Golden Copies every 8 to 24 hours—the **GLEIF Concatenated File** (`ISO 17442 LEIs`), the **ANNA DSB Golden Copy** (`ISO 4914 UPIs` and `OTC ISINs`), and **ESMA / FCA `FIRDS`** (`TOTV` admission scope)—blocking invalid identifiers locally before any XML reaches a Trade Repository or ARM.

## Eliminating "Fire-and-Forget" Delegated Reporting Blindspots

Both ESMA and the [UK Financial Conduct Authority](/regulators/financial-conduct-authority-uk-121) (`Market Watch 74–81`) repeatedly warn buy-side funds, corporate treasuries (`NFC+`), and retail brokers using delegated vendor hubs that **outsourcing submission never outsources oversight**: firms that never log into their Trade Repository portal (`DTCC GTR`, `REGIS-TR`, `LSEG UnaVista`, or [Polish KNF-supervised KDPW_TR](/regulators/polish-financial-supervision-authority-knf-394)) to review daily `auth.091` rejection and reconciliation files receive aggravated supervisory penalties when multi-year under-reporting surfaces.

## Frequently asked questions

### What changed fundamentally when EU and UK EMIR Refit transitioned to ISO 20022 XML?

Prior to 2024, firms submitted heterogeneous CSV or proprietary templates to Trade Repositories, which converted them only for regulator consumption. Under Commission Implementing Regulation (EU) 2022/1860 and FCA/Bank of England UK EMIR rules, reporting counterparties must transmit native ISO 20022 (auth.030.001.03) XML directly into the TR, expanding data elements from 129 to 203 (EU) and 204 (UK).

### How do EMIR Refit derivative reports differ from MiFIR Article 26 transaction reports?

EMIR Article 9 targets systemic counterparty and clearing risk across all OTC and exchange-traded derivatives (reported T+1 to a Trade Repository with daily lifecycle valuation/margin updates). MiFIR Article 26 (RTS 22) targets insider dealing and market manipulation on financial instruments traded on/referenced to a trading venue (reported T+1 via an Approved Reporting Mechanism to the NCA with natural-person trader/decision-maker IDs).

### When did the final 6-month transition period for legacy open derivatives expire?

For EU EMIR Refit, counterparties had 180 calendar days from April 29, 2024—expiring October 26, 2024—to uplift all outstanding live derivative positions to the new 203-field ISO 20022 standard using Action Type UPDT. For UK EMIR Refit, the 6-month transition window ran from September 30, 2024 through March 31, 2025.

### Can a Financial Counterparty delegate its legal liability when delegating operational reporting?

Under EMIR Article 9(1a), when a Financial Counterparty (FC) trades OTC derivatives with a Non-Financial Counterparty below the clearing threshold (NFC-), the FC becomes statutorily responsible AND legally liable for reporting both sides. By contrast, voluntary contractual delegation to a broker or vendor transfers operational execution ONLY—regulatory liability remains squarely on the statutory counterparty.


## Source URLs

- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://www.fca.org.uk/markets/uk-emir
- https://www.cftc.gov/LawRegulation/DoddFrankAct/Rulemakings/DF_17_Recordkeeping/index.htm
- https://www.iosco.org/publications/?subsection=public_reports

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). EMIR Refit, MiFIR & Global ISO 20022 Trade Reporting Master Guide (2026). RegTech Codex. https://regtechcodex.org/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026
- Canonical article: [EMIR Refit, MiFIR & Global ISO 20022 Trade Reporting Master Guide (2026)](https://regtechcodex.org/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
