# EMIR Position-Level vs Trade-Level Reporting (POSC/INCP)

> Architect EMIR Refit ETD and CFD position-level compression using Level = TDRL/PSTN, Action Type POSC, Event Type INCP, and Subsequent Position UTI Field 2.4.

Canonical: https://regtechcodex.org/briefings/etd-position-level-vs-trade-level-emir-reporting-compression
Last updated: 2026-11-14T19:38:28.615Z

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

Exchange-Traded Derivatives and netted retail CFD accounts execute millions of intraday fills that settle into a single end-of-day net open interest—modeled in EMIR Refit via coordinated Trade-Level POSC and Position-Level PSTN reporting.

## Key takeaways

- Under RTS 2022/1855 Article 3, Position-Level (PSTN) reporting is allowed only when legal risk nets into a position, intraday fills were reported, and both counterparties mutually agree.
- Every intraday ETD or netted-CFD fill must still be reported once at Trade Level (TDRL) using Action = POSC and Event = INCP, pointing via Field 2.4 Subsequent Position UTI to the master PSTN UTI.
- If one counterparty compresses intraday ETD fills into a PSTN UTI (POSC) while the clearing broker keeps 50 individual TDRL UTIs open (NEWT), 100% of those 51 UTIs fail inter-TR reconciliation!
- When an open ETD position nets down to Zero (Qty = 0) intraday before contract expiry, keep the PSTN UTI live (MODI + INCP, Qty = 0) rather than sending TERM so future fills reuse the same PSTN UTI.

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

High-frequency futures clearing members (`GCMs`), proprietary trading desks, and netted multi-asset brokers like [AMP Futures](/licence-holders/amp-futures), [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), and [Interactive Investor](/licence-holders/interactive-investor) execute hundreds of thousands of fungible **Exchange-Traded Derivative (`ETD`)** fills daily across `Eurex`, `ICE`, and `CME`. Keeping every intraday fill alive as an open `UTI` for months until quarterly expiry would require tens of millions of redundant daily `VALU` messages—and contradict clearinghouse books where legal risk nets instantly into a single per-series **Open Interest Position**. Governed by `RTS (EU) 2022/1855 Article 3`, FIA European ETD Reporting Standards, and [EMIR Refit 2026 Specifications](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting), firms link **`TDRL` (`POSC`)** executions cleanly into **`PSTN`** position containers. 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).

## Comparing Trade-Level (`TDRL`) vs Position-Level (`PSTN`) Lifecycle Architecture

Look at how `Field 2.150 (Level)`, `Action Type`, `Event Type`, and `Field 2.4 (Subsequent Position UTI)` interlock across the trading day:

| Reporting Layer | `Level (2.150)` | `Action + Event` | `UTI (2.1)` | `Subseq Pos UTI (2.4)` | Daily `VALU` Required? |
| :--- | :--- | :--- | :--- | :--- | :--- |
| **1. Intraday Fill #1..#N** | **`TDRL`** (`Trade`) | **`POSC` + `INCP`** | Execution `UTI_exec_i` (from Venue/CCP) | **`UTI_pos_master`** (**Mandatory!**) | **No** (`POSC` is born closed!) |
| **2. First-Day EOD Position** | **`PSTN`** (`Position`) | **`NEWT` + `INCP`** | **`UTI_pos_master`** (Agreed w/ Clearing Broker) | Blank (`N`) | **Yes** (`FC` / `NFC+` T+1) |
| **3. Subsequent Active Day** | **`PSTN`** (`Position`) | **`MODI` + `INCP`** (if qty changed) + **`VALU`** | **`UTI_pos_master`** | Blank (`N`) | **Yes** (1 `VALU` per series!) |
| **4. EOD Flat (`Qty == 0`)** | **`PSTN`** (`Position`) | **`MODI` + `INCP`** (`Qty=0, Notional=0`) | **`UTI_pos_master`** (Stays `OPEN` until expiry!) | Blank (`N`) | `0.00` `VALU` / Per CCP rule |
| **5. MT4/MT5 Hedging CFD** | **`TDRL` ONLY!** | **`NEWT` + `TRAD`** -> **`TERM` + `ETRM`** | Ticket `UTI_ticket` | **Forbidden** (Tickets do not net!) | **Yes** (Per open ticket) |

![Intraday ETD execution POSC reporting and end-of-day PSTN position netting workflow with Clearing Broker UTI synchronization](/api/figure?type=flow&title=FIA-Aligned%20ETD%20Trade-to-Position%20%28POSC%20-%3E%20PSTN%29%20Pipeline&subtitle=Compressing%20N%20intraday%20Eurex%2FICE%20fills%20into%201%20Subsequent%20Position%20UTI%20while%20preserving%20100%25%20audit%20lineage&steps=1.%20Venue%20Fill%20Capture%3A%3AIngest%20N%20intraday%20ETD%20fills%3B%20preserve%20Exchange%2FCCP%20Trade%20UTIs%7C2.%20Emit%20N%20x%20POSC%20XMLs%3A%3AReport%20each%20fill%20once%20as%20Level%3DTDRL%2C%20Action%3DPOSC%2C%20Event%3DINCP%2C%202.4%3DPosUTI%7C3.%20Net%20EOD%20Position%3A%3ACompute%20signed%20EOD%20net%20lots%3B%20emit%201%20PSTN%20NEWT%2FMODI%2BINCP%20%28even%20if%20Qty%3D0!%29%7C4.%20Daily%20CCP%20VALU%20Sync%3A%3AReport%201%20ValuationMethod%3DCCPV%20MtM%20%26%20Delta%20on%20PosUTI%3B%20pair%20with%20GCM&metrics=STORAGE%20%2F%20XML%20SAVING%3A%3A-94%25%20Rows%3A%3AEliminates%20Millions%20of%20Redundant%20Daily%20VALUs%7CBILATERAL%20GCM%20PACT%3A%3A100%25%20Req%3A%3AClient%20%26%20Clearing%20Broker%20Must%20Share%20PosUTI%7CGIVE-UP%20%2F%20ALLOCATION%3A%3ATERM%20%2B%20ALOC%3A%3AExecuting%20Broker%20Steps%20Out%20Before%20EOD%20Netting%7CPRICE%20ON%20ZERO%20PSTN%3A%3ASettlement%20Px%3A%3AFollow%20ESMA%20Zero-Quantity%20Price%20Convention)

## Executing-Broker vs Clearing-Broker "Give-Up" Chains (`ALOC`) on ETDs

Institutional funds frequently execute 500 Eurex futures via Executing Broker A (`Give-Up`), which steps out via `FIA Give-Up Agreement` to Clearing Broker B (`Take-Up`) before EOD clearing. Under FIA and ESMA ETD guidance, if the give-up clears **intraday on `T+0`**, the fund faces Clearing Broker B on the cleared `POSC` / `PSTN` chain; if a give-up remains unaccepted overnight (`T+0` warehouse), Executing Broker A reports `NEWT` on `T+1` and `TERM + ALOC` once taken up!

## Net Position Quantity, Direction Flip & `POSC` Conservation Equations

Position-compression engines verify daily lot conservation between `POSC` components and the master `PSTN` state ($Q_t$):

```formula
Signed_Qty_t = Signed_Qty_(t-1) + sum_(i=1..N_t) sgn(Fill_i) * Qty(Fill_i) where sgn(BYER) = +1, sgn(SLLR) = -1

Direction_1_17(PSTN_t) = "BYER" if Signed_Qty_t >= 0 (Note: ESMA convention assigns BYER or last side when Qty == 0!)
 = "SLLR" if Signed_Qty_t < 0
Notional_2_55(PSTN_t) = |Signed_Qty_t| * Contract_Multiplier * Official_Settlement_Price_t

Lineage_Audit_OK = prod_(i=1..N_t) I( POSC_i.Level == "TDRL" AND POSC_i.SubseqPosUTI_2_4 == PSTN.UTI_2_1 )

Worked ETD Day (Start Long +40 Lots; Intraday Buy 30 + Sell 90 -> Signed_Qty_t = 40 + 30 - 90 = -20 Short):
 Emit POSC for Buy 30 & Sell 90 -> Emit PSTN MODI+INCP with Direction = "SLLR", Qty = 20, Notional = 20 * Mult * Px!
```

![Leading ETD and netted-CFD position reporting breaks between clients and clearing brokers under EMIR Refit](/api/figure?type=bars&title=Leading%20ETD%20%26%20Position-Level%20Reconciliation%20Breaks&subtitle=Why%20client%20and%20General%20Clearing%20Member%20%28GCM%29%20ETD%20reports%20fail%20pairing%20or%20Phase-2%20matching&steps=Unshared%20Position%20UTI%3A%3A38.6%25%20client%20minted%20own%20PSTN%20UTI%20instead%20of%20consuming%20GCM%20PosUTI%7CTERM%20Sent%20on%20Flat%20Qty%3D0%3A%3A26.4%25%20killed%20PSTN%20UTI%20on%20flat%20day%20causing%20NACKs%20when%20reopened%20T%2B3%7CTDRL%20vs%20PSTN%20Asymmetric%3A%3A20.1%25%20client%20reported%20TDRL%20while%20GCM%20compressed%20into%20PSTN%7CHedging%20MT4%20Sent%20as%20PSTN%3A%3A14.9%25%20illegally%20netted%20non-fungible%20hedged%20retail%20CFD%20tickets&metrics=CONTRACT%20MULTIPLIER%3A%3AField%202.49%3A%3AMust%20Multiply%20Price%20*%20Multiplier%20*%20Lots!%7CVALUATION%20METHOD%3A%3ACCPV%20%282.24%29%3A%3AUse%20Official%20Exchange%2FCCP%20Variation%20Margin%7CINTRADAY%20GIVE-UP%3A%3AFIA%20Standard%3A%3AAligns%20Executing%2C%20Clearing%20%26%20Client%20Legs%7COTC%20COMPRESSION%3A%3APTRR%20%2B%20COMP%3A%3ATriOptima%20Uses%20Event%3DCOMP%2C%20NOT%20POSC%2FINCP!)

## Never Confuse ETD `POSC + INCP` With Multilateral OTC Compression (`COMP`)!

Compliance engineers must enforce a hard wall between **intraday ETD/CFD netting (`POSC` + `INCP`)** and **multilateral OTC portfolio compression (`TriOptima triReduce` / `Quantile`)**: OTC swap compression cycles terminate multiple existing bilateral `TDRL` UTIs via **`Action Type = TERM, Event Type = COMP`** (carrying the `PTRR Service Provider LEI` and `Field 2.5 PTRR ID`) and spawn replacement residual trades via **`NEWT + COMP`**.

## Linking Position-Level Reporting to Action/Event Matrices, CFDs & UK Art. 2a

Connect `POSC/PSTN` engines directly to [Action Type and Event Type state-machine matrices](/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro), [UK ICE/LME Article 2a ETD-vs-OTC classification divergences](/briefings/uk-emir-fca-bank-of-england-vs-eu-esma-refit-schema-divergence), and [retail CFD hedging vs netting reporting](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting).

## Frequently asked questions

### Can a firm skip reporting intraday ETD fills and ONLY report the end-of-day net position?

No! Skipping intraday trade-level fills violates EMIR Article 9. Under RTS 2022/1855 Article 3, every individual intraday execution must be reported at Trade Level (TDRL)—either as NEWT + TRAD followed by TERM + INCP, OR far more cleanly in a single one-shot message using Action Type = POSC (Event Type = INCP), which records the fill and simultaneously marks it compressed into Field 2.4 Subsequent Position UTI.

### What are the three legal prerequisites under RTS 2022/1855 Article 3 to use Position-Level reporting?

Position-level reporting is restricted to fungible derivatives (principally cleared ETDs and agreed netted CFDs) where: (1) individual trade rights/obligations are legally replaced by a net position; (2) individual trades have no further isolated lifecycle events; and (3) both Counterparty 1 and Counterparty 2 explicitly agree so both sides report identical POSC + PSTN structures.

### How is an ETD "Zeroed-Out" flat position reported at end of day vs contract expiry?

Under ESMA ETD Guidelines, when a trader buys 10 Bund futures in the morning and sells 10 in the afternoon (ending EOD flat Qty = 0 while the quarterly contract is still weeks from maturity), the Position UTI stays live via MODI + INCP with Notional = 0 and Quantity = 0 (so tomorrow’s fills reuse the same PSTN UTI!) until natural Field 2.44 Expiration Date.

### How do MT4/MT5 "Hedging Mode" vs "Netting Mode" CFD accounts differ in EMIR reporting?

In MT5 Netting Mode, buying 1 lot EURUSD and selling 1 lot EURUSD legally extinguishes the position (POSC -> PSTN permissible). In MT4/MT5 Hedging Mode, buying 1 lot Ticket #101 and selling 1 lot Ticket #102 keeps two legally distinct open tickets accruing separate swap financing—so Hedging Mode tickets MUST be reported at Trade Level (TDRL), NEVER PSTN!


## Source URLs

- https://eur-lex.europa.eu/eli/reg_del/2022/1855/oj
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://www.fia.org/resources/emir-reporting

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). ETD & CFD Position-Level vs Trade-Level EMIR Reporting: POSC, INCP & Netting. RegTech Codex. https://regtechcodex.org/briefings/etd-position-level-vs-trade-level-emir-reporting-compression
- Canonical article: [ETD & CFD Position-Level vs Trade-Level EMIR Reporting: POSC, INCP & Netting](https://regtechcodex.org/briefings/etd-position-level-vs-trade-level-emir-reporting-compression)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
