# ISO 20022 auth.030 XML Schema & 203 EMIR Fields (2026)

> Validate ISO 20022 auth.030.001.03 XML derivative trade messages across Counterparty, Contract, and Common data tables using ESMA/FCA XSD and conditional rules.

Canonical: https://regtechcodex.org/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields
Last updated: 2026-11-14T19:42:14.572Z

**Publication:** RegTech Codex
**Category:** Emir Refit Mifir Trade Reporting
**Published:** 2026-11-14T01:15: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 EU ITS 2022/1860 and UK EMIR technical standards, every derivative lifecycle submission must conform to the ISO 20022 auth.030.001.03 XML message definition and pass over 450 conditional cross-field validation rules.

## Key takeaways

- EMIR Refit’s 203 EU fields (204 in UK) partition cleanly across Table 1 Counterparty Data (Fields 1.1–1.20), Table 2 Common Trade/Lifecycle Data (Fields 2.1–2.154), and Table 3 Margin/Collateral Data (reported via auth.108).
- Passing pure XML Schema Definition (XSD) syntax validation guarantees structural tag types ONLY; Trade Repositories additionally enforce ESMA’s Validation Table of conditional M (Mandatory), C (Conditional), O (Optional), and N (Not Allowed) rules.
- Repeating XML sequence elements encode multi-installment notional schedules (Fields 2.50–2.52, 2.57–2.59), basket constituents, and multi-currency option strikes previously flattened awkwardly into pipe-delimited CSV cells.
- Strict UTF-8 character whitelists, ISO 8601 UTC microsecond timestamps (YYYY-MM-DDThh:mm:ssZ), and decimal precision bounds prevent silent truncation NACKs at DTCC, REGIS-TR, and LSEG.

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

Transitioning to `Commission Implementing Regulation (EU) 2022/1860` and synchronized [UK FCA](/regulators/financial-conduct-authority-uk-121) technical standards eliminated forgiving CSV parsers across European Trade Repositories (`DTCC GTR`, `REGIS-TR`, `LSEG`, and `KDPW_TR`). Under [EMIR Refit ISO 20022 Standards](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting), every derivative transaction, lifecycle modification, and end-of-day mark-to-market valuation submitted by institutions like [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), and [Exness](/licence-holders/exness) must serialize cleanly into `ISO 20022 auth.030.001.03` XML—passing both W3C XSD structural checks and ESMA's unforgiving **M/C/O/N (`Mandatory / Conditional / Optional / Not-Allowed`)** cross-field rule engine. Review 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).

## Structural Decomposition of the 203/204 EMIR Refit Data Elements

Rather than cramming trade economics and portfolio collateral into one bloated message, `ISO 20022` cleanly splits trade/valuation reporting (`auth.030`) from margin/collateral reporting (`auth.108`):

| EMIR Table & Message | Field Range | Core XML XPath Root (`Document/DerivsTradRpt/...`) | Key Mandatory / High-Failure Elements | Action Types Permitted |
| :--- | :--- | :--- | :--- | :--- |
| **Table 1: Counterparty** (`auth.030`) | `1.1 – 1.20` (`21` in UK) | `.../TradData/Rpt/.../CtrPtySpcfcData` | `RptgCtrPty` (`LEI`), `Ntr` (`F`/`N`), `CorpSctr`, `ClrThreshold`, `Drctn` (`BYER`/`SLLR` or Leg `MAKE`/`TAKE`), `ERR` (`1.3`) | All `auth.030` actions |
| **Table 2: IDs & Valuation** (`auth.030`) | `2.1 – 2.25` | `.../CmonTradData/TxData` & `CtrctData` | `UTI` (`2.1`), `PriorUTI` (`2.3`), `PTRR ID`, `UPI` (`2.8`), `ISIN`, `CFI`, `ValtnAmt` (`2.21`), `Delta` (`2.25`) | `VALU` restricts strictly to `2.1–2.2` & `2.21–2.25` |
| **Table 2: Economics & Schedules** (`auth.030`) | `2.26 – 2.154` | `.../CmonTradData/TxData/[Pric/NtnlAmt/IntrstRate/Ccy/Optn]` | `ClrOblgtn`, `Intragrp`, `NtnlAmt` + `<SchdlPrd>`, Fixed/Floating Day-Count (`A004`), `FX` Forward Rate | `NEWT`, `MODI`, `CORR`, `REVI`, `POSC` (`N` on `VALU`/`TERM`) |
| **Table 3: Margin & Collateral** (`auth.108`) | `3.1 – 3.29` | `Document/DerivsTradMrgnDataRpt/TradData` | `CollPrtflCd` (`VM` vs `IM` split), `InitlMrgnPstdPreHrcut`, `VarMrgnRcvdPostHrcut`, `ExcssColl` | `MARU` (Margin Update) & `CORR` |

![Four-stage local pre-repository ISO 20022 auth.030 XML serialization, XSD check, M/C/O/N validation, and auth.092 NACK ingestion pipeline](/api/figure?type=flow&title=Two-Tier%20Pre-Repository%20ISO%2020022%20Validation%20Engine&subtitle=Catching%20XSD%20type%20violations%20and%20Not-Allowed%20%28N%29%20tag%20leaks%20locally%20before%20SFTP%2FMQ%20dispatch%20to%20the%20TR&steps=1.%20Canonical%20CDM%20Map%3A%3ANormalize%20OMS%2FMurex%2FMT5%20trade%20object%20into%20ISDA%20CDM%20%2F%20Refit%20data%20dictionary%7C2.%20Action-Aware%20Prune%3A%3AStrip%20Not-Allowed%20%28N%29%20economics%20tags%20on%20VALU%2C%20TERM%20%26%20ERRO%20payloads%7C3.%20XSD%20%2B%20450%20Rule%20Gate%3A%3AValidate%20W3C%20auth.030.001.03%20XSD%20%2B%20ESMA%20asset-class%20C-rules%20%26%20LEI%20status%7C4.%20SFTP%2FAPI%20%26%20auth.092%3A%3ADispatch%20signed%20batch%3B%20parse%20TR%20auth.092%20ACK%2FNACK%20within%2015%20minutes&metrics=N-RULE%20REJECTIONS%3A%3A0.00%25%3A%3AEliminated%20via%20Action-Type%20Tag%20Pruner%7CDECIMAL%20PRECISION%3A%3A%3C%3D%2018%2C5%20%2F%2025%2C5%3A%3AStrict%20XSD%20Fractional-Digit%20Enforcement%7CUTC%20TIMESTAMP%20RULE%3A%3AISO%208601%20Z%3A%3ARejects%20Unqualified%20Local-Timezone%20Offsets%7CSCHEMA%20VERSION%20LOCK%3A%3Av1.1.0%20%2F%20v1.2%3A%3ATracks%20ESMA%20Annual%20XSD%20Maintenance%20Releases)

## Defeating the "Not-Allowed (`N`)" Tag Leak & Direction-Determination Traps

Two subtle schema traps account for over half of post-go-live `auth.092` rejections. First, middleware developers serialize full trade objects on daily `VALU` (`Valuation Update`) or `TERM` (`Early Termination`) messages—immediately triggering `NACK` errors because ESMA marks contract-economic fields (`2.33–2.151`) as **`N` (`Not Allowed`)** on `VALU` and `TERM`. Second, **Direction determination** splits into two mutually exclusive paradigms specified by ESMA `RTS 2022/1855 Article 4`: instruments with a natural buyer/seller (options, forwards, CFDs, credit default swaps) populate Field `1.17` (`BYER`/`SLLR`) and leave Fields `1.18–1.19` blank (`N`), whereas two-leg swaps (IRS, cross-currency swaps, FX swaps) leave `1.17` blank (`N`) and populate Leg 1 and Leg 2 payer/receiver tags (`MAKE`/`TAKE`) in `1.18–1.19`.

## Pre-Submission Schema Readiness & First-Pass Acceptance Formula

Reporting engineering teams gate production releases using a **Pre-Repository Validation Coverage & First-Pass `ACK` Score** ($V_{\text{xml}}$):

```formula
B_xsd_ok = I( W3C_XSD_Errors(msg) == 0 )
B_mcon_ok = prod_(f=1..203) I( State(msg, f) matches ESMA_Matrix[ActionType, AssetClass, ClearStatus, f] )
B_ref_ok = I( GLEIF_Status(LEI_1, LEI_2) in Valid_Set_For_Action ) * I( ANNA_UPI_CFI_Match(msg) == 1 )
Pass_PreTR = B_xsd_ok * B_mcon_ok * B_ref_ok

Operational Gate:
 Target First-Pass TR ACK Rate = ( sum Pass_TR_auth092 ) / Total_Dispatched >= 0.9985 (99.85%)

Worked Defect Catch (VALU Message Accidentally Carrying Notional Field 2.55):
 ESMA_Matrix[VALU, CURR, Uncleared, f=2.55] == "N" -> State(msg, 2.55) == Present -> B_mcon_ok = 0 (Quarantined & Stripped Locally!)
```

![Top field-level ISO 20022 auth.030 validation errors caught in pre-submission EMIR Refit gateways](/api/figure?type=bars&title=Most%20Frequent%20ISO%2020022%20auth.030%20Schema%20Validation%20Errors&subtitle=Distribution%20of%20conditional%20rule%20violations%20intercepted%20before%20Trade%20Repository%20submission&steps=Direction%201.17%20vs%201.18%2F19%3A%3A31.6%25%20mixed%20BYER%2FSLLR%20with%20Leg%201%2F2%20MAKE%2FTAKE%20swap%20tags%7CExtra%20Tags%20on%20VALU%20%2F%20TERM%3A%3A27.9%25%20violated%20Not-Allowed%20%28N%29%20economics%20exclusions%7CUPI%20vs%20CFI%20Attribute%20Clash%3A%3A22.4%25%20submitted%20Contract%20Type%2FAsset%20Class%20conflicting%20with%20DSB%20UPI%7CMissing%20Package%20%2F%20FX%20Rate%3A%3A18.1%25%20omitted%20Exchange%20Rate%20Basis%20or%20Complex%20Trade%20ID%20on%20swaps&metrics=CUSTOM%20BASKET%20ID%3A%3ALEI%20%2B%20Str52%3A%3AField%202.42%20Structuring%20When%20ISIN%20Absent%7CDELTA%20MANDATE%3A%3AField%202.25%3A%3ARequired%20Daily%20on%20Options%20%26%20Swaptions%20%28-1..%2B1%29%7CCRYPTO%20DERIVATIVES%3A%3AField%202.12%3A%3ADedicated%20Derivative-Based-on-Crypto%20Boolean%7CUK%20FIELD%201.21%3A%3AExecution%20Agt%3A%3AExtra%20UK-Specific%20Table%201%20Schema%20Element)

## Governing Annual ESMA / FCA XSD Maintenance Releases in CI/CD

ISO 20022 schemas are living specifications: ESMA and the [UK FCA](/regulators/financial-conduct-authority-uk-121) publish periodic `XML Schema v1.1 / v1.2` and Validation Table corrigenda tightening tolerances (such as Phase-2 reconciliation expansion and `Delta` validation on option valuations). Embedding official XSD + Schematron validation suites inside automated CI/CD regression pipelines ensures OMS upgrades never break production `auth.030` feeds.

## Connecting auth.030 Serialization to UPI, Lifecycle Matrices & UK Divergence

Pair XML schema engineering directly with [ANNA DSB ISO 4914 UPI and CFI cross-validation](/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation), [Action Type vs Event Type state-machine matrices](/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro), and [UK EMIR vs EU ESMA schema divergence handling](/briefings/uk-emir-fca-bank-of-england-vs-eu-esma-refit-schema-divergence).

## Frequently asked questions

### Which exact ISO 20022 message definitions govern EMIR Refit trade, margin, and feedback flows?

Counterparty-to-TR trade and valuation submissions use DerivativesTradeReportV03 (auth.030.001.03), margin and collateral portfolio updates use DerivativesTradeMarginDataReportV01 (auth.108.001.01), TR rejection/warning responses arrive in auth.092, and inter-TR pairing/matching reconciliation exceptions arrive daily in auth.091.

### Why does an XML message that passes official ISO 20022 XSD validation still get NACKed by DTCC or REGIS-TR?

The W3C .xsd file enforces XML element hierarchy, regex formats, and maximum string lengths, but most elements are marked optional (minOccurs="0") at the XSD layer because requirements vary by Action Type (NEWT vs TERM vs VALU) and Asset Class (INTR vs CURR). Cross-field conditional logic (e.g., "If Asset Class == CURR, Exchange Rate 2.113 is Mandatory") runs in the second-stage ESMA Validation Rules engine.

### How are notional schedules on amortizing interest-rate swaps represented in auth.030?

Fields 2.50–2.52 (Leg 1) and 2.57–2.59 (Leg 2) embed repeating <NtnlAmt><SchdlPrd> XML blocks specifying the unadjusted effective date, end date, and step-up/step-down notional amount known at execution—avoiding false daily MODI filings as pre-agreed amortization dates roll past.

### What does rule code "N" (Not Allowed) mean in the ESMA EMIR Refit Validation Table?

Unlike legacy EMIR where over-populating irrelevant optional fields was tolerated, EMIR Refit enforces explicit "N" (Not Allowed) constraints: for example, submitting contract-economics tags inside a pure VALU valuation update or populating Leg 2 currency on a single-leg equity option triggers an immediate TR NACK rejection.


## Source URLs

- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://eur-lex.europa.eu/eli/reg_impl/2022/1860/oj
- https://www.iso20022.org/catalogue-messages/iso-20022-messages-archive

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). ISO 20022 auth.030 XML Schema Validation: Engineering EMIR Refit’s 203 Data Fields. RegTech Codex. https://regtechcodex.org/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields
- Canonical article: [ISO 20022 auth.030 XML Schema Validation: Engineering EMIR Refit’s 203 Data Fields](https://regtechcodex.org/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
