Skip to content
RegTech Codex
Directory

Emir Refit Mifir Trade Reporting

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

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.

By Victoria Ashworth, LL.M, CAMSReview not recorded
EMIR Refit, MiFIR & Global ISO 20022 Trade Reporting Master Guide (2026) — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (EMIR Refit ISO 20022 XML, UTI Pairing, UPI Reference Data & Reconciliation): Architectural blueprint for EMIR Refit ISO 20022 XML, UTI/UPI reference data, MiFIR RTS 22, and CFTC/APAC rewrites.Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

Between 2022 and 2026, global derivatives and transaction reporting underwent a synchronized technological convergence: the US CFTC Swap Data Rewrite, US SEC Regulation SBSR, EU EMIR Refit (Regulation (EU) 2019/834 + RTS 2022/1855 / ITS 2022/1860), UK FCA / Bank of England UK EMIR Refit, and synchronized ISO 20022 rewrites across ASIC, MAS, HKMA (Hong Kong Monetary Authority), and JFSA replaced fragmented legacy spreadsheets with machine-enforceable XML schemas. Multi-jurisdictional liquidity providers, CFDs/FX brokers, and swap dealers—including CMC Markets, ICAP, Exness, ATFX, and AMP Futures—now run unified pre-submission validation gateways anchored to EU & UK EMIR Refit 2026 Standards. Explore every implementation module in the EMIR Refit & MiFIR reporting hub.

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:

Quantitative Distribution · Primary Technical Schema
Primary Technical SchemaField Count
01EU EMIR Refit (ESMA / AMF /…ISO 20022 auth.…02UK EMIR Refit (FCA / PRA / …ISO 20022 auth.…03EU/UK MiFIR Art. 26 (RTS 22…ISO 20022 auth.…04US CFTC Part 43/45 & CFTC R…ISO 20022 auth.…05APAC Rewrite (ASIC / MAS / …ISO 20022 (ASIC…
Regime & SupervisorPrimary Technical SchemaField CountProduct & Entity IDsInter-TR Pairing & Recon?Delegation Legal Liability
EU EMIR Refit (ESMA / AMF / AFM / KNF)ISO 20022 auth.030.001.03203 (3 tables)ANNA DSB UPI + ISIN + GLEIF LEIDual-Sided: 87 Phase-1 -> 148 Phase-2 fieldsFC statutorily liable for NFC- OTC (Art. 9(1a))
UK EMIR Refit (FCA / PRA / BoE)ISO 20022 auth.030.001.03 (UK XSD)204 (+ UK execution agt)UPI + ISIN + LEIDual-Sided: UK-TR + inter-TR reconciliationFC liable for NFC- OTC; operational delegation retains duty
EU/UK MiFIR Art. 26 (RTS 22 via ARM)ISO 20022 auth.016.001.0165 (T+1 tx)ISIN + LEI + Natural Person CONCAT/PassportSingle-sided venue/investment-firm cross-checkInvestment firm strictly liable (No ARM shield)
US CFTC Part 43/45 & CFTC Rule 2-9ISO 20022 auth.030 (CDE)128 (T+1 / ASAP)UPI (Rates/Credit/FX/Eq/Commod) + LEISingle-Sided (SD -> MSP -> FC reporting hierarchy)Reporting Counterparty (RCP) bears 100% SDR recon duty
APAC Rewrite (ASIC / MAS / HKMA)ISO 20022 (ASIC/MAS 2024–2025)104–134 (CDE)UTI + UPI + LEISingle-sided / Nexus + Delegated UTILicensed 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
End-to-end EMIR Refit and global ISO 20022 trade reporting architecture from OMS execution to T+1 three-way Trade Repository reconciliationVerified Exhibit

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:

Quantitative Reporting Health &NCA Material-Breach Threshold Formula#

Under ESMA Final Report Guidelines (Section 9.3) and EMIR Refit 2026 Benchmark Thresholds, 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 or model from the articleNot independently verified
Avg_Monthly_Submissions = (1 / 12) * sum_(m=1..12) N_submitted_bucket(m)
  • BreachRatioBucket = Naffectedreports / max(1, AvgMonthlySubmissions)
  • NotifyNCATrigger = I( (Naffectedreports > NumFloor AND BreachRatioBucket > 0.15) OR Naffectedreports > HardCap )
  • 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
Root causes of Trade Repository NACK rejections and inter-TR reconciliation breaks following EMIR Refit go-liveVerified Exhibit

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 (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) 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.

Publication record

Published
14 November 2026
Updated
14 November 2026
Author
Victoria Ashworth, LL.M, CAMS
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
4 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). 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
Explore Emir Refit Mifir Trade Reporting Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

EMIR Refit, MiFIR & ISO 20022 Trade Reporting Guide (2026) | RegTech Codex