# FX Swaps, Forwards & NDFs EMIR Refit XML Mapping (2026)

> Map FX Swaps (2 UTIs linked by Package ID vs 1 UTI), Deliverable FX Forwards, Non-Deliverable Forwards (NDFs), and commercial spot-FX exemptions into auth.030.

Canonical: https://regtechcodex.org/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mapping
Last updated: 2026-11-14T19:40:13.810Z

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

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.

## Key takeaways

- Under ESMA EMIR Refit Guidelines, an FX Swap (Near Leg + Far Leg) MUST be reported as two separate auth.030 reports (2 UTIs) linked via Field 2.6 Package Identifier—including a <=T+2 Near Leg!
- T+2 Spot FX and <=T+5 securities-settlement FX conversions (Reg 2017/565 Art. 10) are statutorily exempt non-derivatives—submitting them to a Trade Repository causes unlawful over-reporting.
- Deliverable FX Forwards (PHYS) and Non-Deliverable Forwards (NDFs, CASH settled against fixing rates like PTAX or CNY SAEC) require distinct ANNA DSB UPIs, CFIs, and Forward Exchange Rate fields.
- Enforcing ISO 4217 Alphabetical Currency Ordering (EUR = Leg 1, USD = Leg 2; JPY = Leg 1, USD = Leg 2!) prevents 100% of Leg 1 / Leg 2 inversion breaks in Phase-1/Phase-2 reconciliation!

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

## Analysis

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](/licence-holders/icap), [CMC Markets](/licence-holders/cmcmarkets), [Equiti](/licence-holders/equiti), [Axi](/licence-holders/axi), and [Exness](/licence-holders/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](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting) and GFMA Global FX Division guidelines, ESMA locked down a single canonical XML mapping. See 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).

## 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 |

![FX product classification, MiFID Org Reg Article 10 spot filtering, ISO 4217 alphabetical leg sorting, and two-UTI FX Swap package serialization](/api/figure?type=flow&title=FX%20Derivative%20Filter%2C%20Alphabetical%20Leg%20Sorter%20%26%20Swap%20Packager&subtitle=Suppressing%20exempt%20T%2B2%2FT%2B5%20spot%20FX%20while%20splitting%20FX%20Swaps%20into%20dual%20Package-linked%20ISO%2020022%20reports&steps=1.%20Art.%2010%20Spot%20Filter%3A%3AExclude%20pure%20%3C%3DT%2B2%20spot%2C%20%3C%3DT%2B5%20security-settle%20FX%20%26%20verified%20payment%20fwds%7C2.%20FX%20Swap%20Leg%20Split%3A%3AUnbundle%20FX%20Swap%20into%20Near-Leg%20UTI_1%20%2B%20Far-Leg%20UTI_2%20sharing%20Package%20ID%202.6%7C3.%20Alpha%20ISO%20Leg%20Sort%3A%3AOrder%20Leg%201%20%3D%20Min_Alpha%28CCY_A%2C%20CCY_B%29%3B%20set%201.18%2F1.19%20MAKE%2FTAKE%20payer%20roles%7C4.%20Rate%20%26%20Basis%20Align%3A%3AOrient%20Exchange%20Rate%20%282.113%2F114%29%20strictly%20to%20match%20Exchange%20Rate%20Basis%20%282.115%29&metrics=LEG-FLIP%20BREAKS%3A%3A0.00%25%3A%3AVia%20Strict%20ISO%204217%20Alphabetical%20Leg%201%20Rule%7CRATE%20ORIENTATION%3A%3AUnit%20%2F%20Quoted%3A%3ARate%20Must%20Equal%20Units%20of%20CCY2%20per%201%20CCY1%20in%202.115%7CFX%20ROLL%20%2F%20TOM-NEXT%3A%3A2-Leg%20Swap%3A%3AHistorical%20Roll%20Swaps%20Follow%20Package%20Pattern%7CUS%20CFTC%20DIVERGENCE%3A%3APart%2045%20Only%3A%3ADeliverable%20FX%20Fwds%2FSwaps%20Exempt%20From%20CFTC%20Pt%2043)

## 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 = MAKE` if paying JPY, `TAKE` if receiving JPY);
- **Leg 2 (`2.64 / 2.65`)** = `USD 10,000,000` (`Field 1.19 = TAKE` if receiving USD, `MAKE` if paying USD);
- **Exchange Rate Basis (`2.115`) & Forward Rate (`2.114`)**: If `2.115` is populated as `USD/JPY` (`1 USD = 152.50 JPY`), `2.114` MUST be `152.50` (never `0.006557` while claiming `USD/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`:

```formula
(CCY_1, CCY_2) = ( min_alpha(C_pay, C_rcv), max_alpha(C_pay, C_rcv) )
(Dir_Leg1_1_18, Dir_Leg2_1_19) = ("MAKE", "TAKE") if C_pay == CCY_1 else ("TAKE", "MAKE")

Implied_Cross_Rate = Notional_CCY_Quote / Notional_CCY_Base for Exchange_Rate_Basis = "CCY_Base/CCY_Quote"
Rate_Parity_OK = I( | Forward_Rate_2_114 - Implied_Cross_Rate | / Implied_Cross_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!
```

![Breakdown of FX derivative reporting errors across EMIR Refit Trade Repositories](/api/figure?type=bars&title=Most%20Frequent%20FX%20Derivative%20Errors%20in%20EMIR%20Refit&subtitle=Distribution%20of%20NACKs%20and%20inter-TR%20matching%20breaks%20on%20FX%20Swaps%2C%20Outright%20Forwards%2C%20and%20NDFs&steps=USD%2FJPY%20%26%20GBP%2FUSD%20Leg%20Flip%3A%3A35.8%25%20used%20market-quote%20order%20instead%20of%20alphabetical%20ISO%204217%7C1-UTI%20vs%202-UTI%20FX%20Swap%3A%3A27.4%25%20omitted%20Near%20Leg%20or%20forgot%20shared%20Field%202.6%20Package%20ID%7CInverted%20Rate%20vs%20Basis%3A%3A21.2%25%20reported%200.8800%20rate%20alongside%20inverted%20CHF%2FUSD%20basis%20tag%7COver-Reported%20T%2B2%20Spot%20FX%3A%3A15.6%25%20mistakenly%20reported%20exempt%20T%2B2%20spot%20or%20T%2B3%20equity-settle%20FX&metrics=GFMA%20FX%20BEST%20PRACTICE%3A%3AIndustry%20Std%3A%3AHarmonizes%20Inter-Dealer%20FX%20Swap%20UTIs%7CNDF%20FIXING%20SOURCE%3A%3AEMTA%20Template%3A%3ABRL%20PTAX%2C%20KRW%20KFTC18%2C%20INR%20FBIL%2C%20TWD%20TAIFX1%7CFX%20OPTION%20DELTA%3A%3AField%202.25%3A%3AMandatory%20Daily%20Phase-2%20Reconciled%20Element%7CROLLING%20SPOT%20FX%3A%3ANOT%20Exempt!%3A%3APerpetual%20Auto-Roll%20Retail%20FX%20Is%20a%20Derivative!)

## 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](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting), [ANNA DSB ISO 4914 `PHYS` vs `CASH` UPI selection](/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation), and [bilateral Swift MT300 Tag 22L UTI exchange](/briefings/bilateral-uti-generation-waterfall-emir-refit-article-7-tiebreak).

## 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!


## Source URLs

- https://www.esma.europa.eu/sites/default/files/library/esma74-362-2281_final_report_guidelines_emir_refit.pdf
- https://eur-lex.europa.eu/eli/reg_del/2017/565/oj
- https://www.gfma.org/policies-resources/fx/

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). 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-mapping
- Canonical article: [FX Swaps, Deliverable Forwards & NDFs: Two-Leg EMIR Refit ISO 20022 XML Mapping](https://regtechcodex.org/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mapping)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
