Emir Refit Mifir Trade Reporting
FX Swaps, Deliverable Forwards & NDFs: Two-Leg EMIR Refit ISO 20022 XML Mapping
Foreign exchange derivatives generate massive inter-TR pairing and leg-ordering breaks under EMIR Refit—requiring exact ESMA mapping of FX Swap Near/Far legs, Package Identifiers, Exchange Rate Basis, and MiFID II Article 10 spot/commercial exemptions.

Foreign exchange derivatives—spanning corporate FX Forwards, institutional Near/Far FX Swaps, emerging-market Non-Deliverable Forwards (NDFs), and FX Vanilla/Barrier Options—account for over 40% of bilateral OTC Trade Repository volume across Europe, the UK, and APAC. Yet FX desks at wholesale brokers and liquidity providers like ICAP, CMC Markets, Equiti, Axi, and Exness historically suffered chronic pairing breaks because legacy EMIR allowed firms to choose between 1-report and 2-report FX Swaps! Under EMIR Refit 2026 ISO 20022 Standards and GFMA Global FX Division guidelines, ESMA locked down a single canonical XML mapping. See our EMIR Refit Master Guide 2026 inside the EMIR & MiFIR reporting hub.
Canonical EMIR Refit Mapping Across FX Spot, Forwards, FX Swaps & NDFs#
Before generating auth.030, your FX classifier must separate exempt MiFID Org Reg Article 10 spot/settlement conversions from reportable OTC FX derivatives:
| FX Contract Type | EMIR Reportable? | UTI & Package Count | Contract (2.10) & Delivery (2.154) | Critical auth.030 FX Fields (2.113–2.115) |
|---|---|---|---|---|
Standard Spot FX (<= T+2) | NO (Exempt!) | 0 (Never report!) | Exempt Reg 2017/565 Art. 10 | Suppress in pre-TR filter (unless rolling spot!) |
Security-Settlement FX (<= T+5) | NO (Exempt!) | 0 (Linked to equity/bond settle) | Ancillary conversion exemption | Retain linked security TradeID in audit log |
| Deliverable FX Outright Forward | YES (OTC) | 1 UTI (No Package ID) | FORW + PHYS (+ Deliverable UPI) | 2.114 Fwd Rate, 2.115 Exch Rate Basis (CCY1/CCY2), Alpha ISO Leg 1/2 |
FX Swap (Near + Far Legs) | YES (Both Legs!) | 2 UTIs + Shared 2.6 Package ID! | FORW/SWAP + PHYS on each leg | Near Leg reported even if <= T+2! Link via Field 2.6 |
Non-Deliverable Forward (NDF) | YES (OTC) | 1 UTI | FORW + CASH (+ NDF UPI) | Populate Settlement Currency 1 (2.19) (e.g., USD) + Fixing Date |
Eliminating the Inverse Exchange-Rate & MAKE / TAKE Direction Bug!#
Look at what happens on a $10,000,000 USD/JPY forward agreed at 152.50: Market convention quotes USD first (1 USD = 152.50 JPY), yet alphabetically JPY (J) comes BEFORE USD (U)! Under ESMA's rule:
- Leg 1 (
2.55 / 2.56) =JPY 1,525,000,000(Field 1.18 = MAKEif paying JPY,TAKEif receiving JPY); - Leg 2 (
2.64 / 2.65) =USD 10,000,000(Field 1.19 = TAKEif receiving USD,MAKEif paying USD); - Exchange Rate Basis (
2.115) & Forward Rate (2.114): If2.115is populated asUSD/JPY(1 USD = 152.50 JPY),2.114MUST be152.50(never0.006557while claimingUSD/JPY!).
Deterministic FX Leg-Sorting & Rate-Orientation Consistency Formula#
FX serialization engines guarantee mathematical cross-consistency across Leg 1, Leg 2, MAKE/TAKE, and Forward Exchange Rate:
- (DirLeg1118, DirLeg2119) = ("MAKE", "TAKE") if Cpay == CCY1 else ("TAKE", "MAKE")
- ImpliedCrossRate = NotionalCCYQuote / NotionalCCYBase for ExchangeRateBasis = "CCYBase/CCYQuote"
- RateParityOK = I( | ForwardRate2114 - ImpliedCrossRate | / ImpliedCross_Rate <= 0.0001 )
- Worked USD/CHF Forward (Bank Pays USD 5,000,000, Receives CHF 4,400,000 at USD/CHF = 0.8800):
- min_alpha("CHF","USD") = "CHF" -> Leg 1 = CHF 4.4M (Dir 1.18 = TAKE), Leg 2 = USD 5.0M (Dir 1.19 = MAKE); Basis="USD/CHF", Rate=0.8800!
Crucial Distinction: Exempt Institutional T+2 Spot vs Reportable "Rolling Spot FX"!#
Never confuse genuine deliverable T+2 Spot FX with Retail/Margin "Rolling Spot FX"! Under MiFID II Annex I Section C(4) and FCA/ESMA guidance, an undated FX margin contract (EUR/USD on MT4/MT5/cTrader) that automatically rolls Tom-Next every evening at 17:00 EST without intended physical currency delivery is a Financial Contract for Differences / Rolling Spot Derivative—100% reportable under EMIR (and under MiFIR when referencing a venue-traded currency derivative/TOTV scope where applicable)!
Linking FX Reporting to Retail CFDs, ANNA DSB UPIs & UTI Waterfalls#
Connect FX XML serializers directly to retail CFD and rolling-spot FX dual EMIR/MiFIR reporting, ANNA DSB ISO 4914 `PHYS` vs `CASH` UPI selection, and bilateral Swift MT300 Tag 22L UTI exchange.
Frequently asked questions
Are FX Swaps reported as ONE UTI or TWO UTIs linked by Package ID under EMIR Refit?
This was one of the biggest shifts in EMIR Refit! Under ESMA’s Final Report Guidelines (Section 6.5), an FX Swap composed of a Near Leg and a Far Leg is reported as TWO separate derivative reports (2 UTIs) linked by a shared Field 2.6 Package Identifier (Complex Trade ID)—and yes, the Near Leg IS reported as part of the FX Swap package even when the Near Leg settles within T+2!
When is a spot FX or T+3/T+5 securities-settlement FX trade EXEMPT from EMIR reporting?
Under MiFID II Delegated Regulation (EU) 2017/565 Article 10 (incorporated by reference into EMIR), a FX contract is an exempt spot contract (NOT a derivative) if it settles within 2 trading days (T+2) for major/minor pairs, OR within the market-standard settlement period (up to 5 trading days) when entered into solely to pay for an identifiable purchase/sale of a transferable security!
Are "Means-of-Payment" commercial FX forwards exempt under EU EMIR vs UK EMIR?
Watch the subtlety! Under MiFID II Org Reg Article 10(1)(b), physically settled FX forwards (not traded on a venue) entered into by non-financial clients as a *means of payment* for identifiable goods/services are excluded from the MiFID financial-instrument definition (and thus outside EMIR!). However, investment firms must document objective client commercial-goods nexus before treating a T+90 FX forward as an Article 10 means-of-payment exclusion.
How do Leg 1 and Leg 2 currencies get ordered on a USD/JPY or GBP/USD FX Forward in auth.030?
Ignore market quoting conventions (GBP/USD or USD/JPY) when ordering XML legs! Under ESMA Guidelines (Paragraph 231), counterparties MUST order Notional Currency 1 (Field 2.56) and Notional Currency 2 (Field 2.65) in strict alphabetical order of their 3-letter ISO 4217 codes (GBP = Leg 1, USD = Leg 2; JPY = Leg 1, USD = Leg 2!) and assign MAKE/TAKE payer/receiver directions in 1.18–1.19 accordingly!
Publication record
- Published
- 13 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
- 3 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
Standard academic & institutional research paper citation format.
Victoria Ashworth, LL.M, CAMS. (2026, November 14). FX Swaps, Deliverable Forwards & NDFs: Two-Leg EMIR Refit ISO 20022 XML Mapping. RegTech Codex. https://regtechcodex.org/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mappingRelated Emir Refit Mifir Trade Reporting & Institutional Briefings
Explore Emir Refit Mifir Trade Reporting Hub (20) →Emir Refit Mifir Trade Reporting
EMIR Refit, MiFIR & Global ISO 20022 Trade Reporting Master Guide (2026)Emir Refit Mifir Trade Reporting
Retail CFD & Rolling-Spot FX Brokers: Dual EMIR Refit & MiFIR Reporting ArchitectureEmir Refit Mifir Trade Reporting
SFTR ISO 20022 Reporting: Repo, Securities Lending, Margin Lending & Collateral ReuseEmir Refit Mifir Trade Reporting
SEC Rule 17a-4, CFTC Rule 1.31 & MiFID II Art. 16(7): WORM Audit-Trail & Trade ReconstructionEmir Refit Mifir Trade Reporting
Automated T+1 Three-Way Reconciliation: Front-Office OMS vs Middleware vs Trade RepositoryEmir Refit Mifir Trade Reporting
ISO 20022 auth.030 XML Schema Validation: Engineering EMIR Refit’s 203 Data FieldsEmir Refit Mifir Trade Reporting
Bilateral UTI Generation Waterfall: EMIR Refit ITS Article 7 Tie-Breakers & Pairing SLAsEmir Refit Mifir Trade Reporting
ANNA DSB UPI (ISO 4914) & ISO 10962 CFI Validation for OTC Derivatives ReportingClient Asset Segregation Breaches
Singapore MAS SFA Reg 16–37 & Hong Kong SFC Cap. 571O: APAC Client Money DeadlinesClient Asset Segregation Breaches
Prime Broker Rehypothecation: SEC Rule 15c3-3 140% Cap vs UK/EU Unlimited Reuse & CASS 9Client Asset Segregation Breaches
Unallocated Client Receipts & PSP Settlement Floats: CASS 7.13, PSR Safeguarding & CASS 15Client Asset Segregation Breaches
External CASS Assurance Audits: FRC Client Asset Standard, Breach Logs & Adverse Opinions
RegTech Codex Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
