# EMIR Refit Action Type & Event Type Matrix Guide (2026)

> Implement the deterministic EMIR Refit ITS 2022/1860 Action Type (NEWT, MODI, CORR, TERM, ERRO, REVI, VALU, POSC) and Event Type state-machine matrix.

Canonical: https://regtechcodex.org/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro
Last updated: 2026-11-16T19:07:41.581Z

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

Replacing legacy single-dimensional action codes, EMIR Refit pairs eight Action Types with twelve business Event Types inside a strict finite-state machine—where sending ERRO instead of TERM or MODI after maturity triggers instant NACKs.

## Key takeaways

- EMIR Refit separates technical database actions (Field 2.151 Action Type: NEWT, MODI, CORR, TERM, ERRO, REVI, VALU, POSC) from business causes (Field 2.152 Event Type: TRAD, NOVA, COMP, ETRM, INCP, etc.).
- Not every (Action Type, Event Type) pair is legal! ESMA’s ITS 2022/1860 matrix permits only ~33 valid combinations out of 96 theoretical pairs (for example, VALU and ERRO MUST leave Event Type completely blank!).
- Introduced specifically in Refit, REVI (Revive) resurrects a trade previously cancelled in error (ERRO) or terminated prematurely (TERM)—or re-opens a trade whose Expiration Date was mistakenly allowed to pass before fixing.
- Scheduled natural maturity requires zero TERM message: Trade Repositories automatically expire open trades at Field 2.44 Expiration Date; sending TERM is strictly reserved for *early* unscheduled terminations (ETRM, COMP, CLRG, NOVA, EXER)!

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

Over **26.1% of post-Refit Trade Repository `NACK` rejections** occur not because economic numbers are malformed, but because reporting engines emit an illegal **`(Action Type, Event Type)`** pair or attempt to update a derivative whose `UTI` has already transitioned into a terminal state inside the Trade Repository's state machine. Standardized across [EU & UK EMIR Refit 2026 Specifications](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting), CFTC CDE, and ASIC/MAS rewrites, firms like [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [AMP Futures](/licence-holders/amp-futures), and [ATFX](/licence-holders/atfx) maintain local **UTI Lifecycle Shadow State Machines** synchronized to `DTCC`, `REGIS-TR`, and `LSEG`. 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).

## Allowed EMIR Refit `(Action Type × Event Type)` Compatibility Matrix

Before serializing `Field 2.151 (Action Type)` and `Field 2.152 (Event Type)`, middleware must enforce ESMA `ITS 2022/1860 Annex` permissible pairings alongside required **Prior UTI (`2.3`)** or **Subsequent Position UTI (`2.4`)** pointers:

| Action Type (`2.151`) | Required Prior State | Resulting TR State | **ONLY Permitted Event Types (`2.152`)** | Mandatory Linkage Pointer |
| :--- | :--- | :--- | :--- | :--- |
| **`NEWT`** (New) | Non-Existent | `OPEN (Live)` | `TRAD`, `NOVA`, `COMP`, `CLRG`, `EXER`, `ALOC`, `INCP`, `CORP` | `Prior UTI (2.3)` on `NOVA`/`CLRG`/`EXER`/`ALOC` |
| **`MODI`** (Modify) | `OPEN (Live)` | `OPEN (Live)` | `TRAD`, `NOVA`, `COMP`, `ETRM` (partial!), `ALOC`, `INCP`, `CREV`, `CORP`, `UPDT` | `PTRR ID (2.5)` if `COMP` compression |
| **`CORR`** (Correct) | `OPEN` or `TERM` | Unchanged | **Blank (`N`)** — *Event Type strictly forbidden!* | Historical `Event Date (2.153)` |
| **`VALU`** (Valuation) | `OPEN (Live)` | `OPEN (Live)` | **Blank (`N`)** — *Only Fields `2.1–2.2` & `2.21–2.25`!* | None |
| **`TERM`** (Terminate) | `OPEN (Live)` | `TERMINATED` | `ETRM`, `NOVA` (full), `COMP` (full), `CLRG`, `EXER`, `ALOC`, `INCP`, `CORP`, `CREV` | Never send on natural maturity! |
| **`ERRO`** (Cancel Error) | `OPEN` or `TERM` | `ERRORED (Dead)` | **Blank (`N`)** — *Cannot send `CORR`/`MODI` after `ERRO`!* | Requires `REVI` to undo |
| **`REVI`** (Revive) | `TERM`, `ERRO`, `EXPIRED` | `OPEN` (or active) | **Blank (`N`)** — *Includes full current economics!* | Restores mistaken `ERRO`/`TERM` |
| **`POSC`** (Pos Component) | Non-Existent (`TDRL`) | `INCLUDED_CLOSED` | **`INCP` ONLY** (*Inclusion in Position*) | **`Subsequent Position UTI (2.4)`** Req! |

![Finite-state machine of an EMIR Refit UTI moving between Unborn, Live Open, Position-Compressed, Terminated, Expired, Errored, and Revived states](/api/figure?type=flow&title=Trade%20Repository%20UTI%20Finite-State%20Machine%20%26%20Ordering%20Sequencer&subtitle=Sequencing%20intraday%20batches%20so%20NEWT%20precedes%20VALU%2FTERM%20and%20REVI%20precedes%20overdue%20Expiration%20extensions&steps=1.%20Shadow%20State%20Check%3A%3AQuery%20local%20TR-mirror%20DB%20for%20current%20UTI%20state%20%28Unborn%2FOpen%2FDead%2FExpired%29%7C2.%20Auto-Inject%20REVI%3A%3AIf%20amending%20an%20expired%20or%20mistakenly%20errored%20UTI%2C%20prepend%20REVI%20before%20MODI%7C3.%20Sequence%20Order%20Sort%3A%3ASort%20EOD%20XML%20batch%20strictly%3A%20NEWT%2FREVI%20-%3E%20MODI%2FCORR%20-%3E%20VALU%20-%3E%20TERM%2FERRO%7C4.%20Bilateral%20Sync%3A%3AConfirm%20counterparty%20agrees%20on%20MODI%20%28partial%29%20vs%20TERM%2BNEWT%20%28novation%29&metrics=OUT-OF-ORDER%20NACKS%3A%3A0.00%25%3A%3AVia%20Deterministic%20Intra-Batch%20Topological%20Sort%7CPARTIAL%20UNWIND%3A%3AMODI%20%2B%20ETRM%3A%3AReduces%20Notional%20Without%20Killing%20Open%20UTI%7CFULL%20NOVATION%3A%3ATERM%20%2B%20NEWT%3A%3AOld%20UTI%20Gets%20TERM%2BNOVA%3B%20New%20Gets%20NEWT%2BNOVA%7CCREDIT%20EVENT%20CDS%3A%3AMODI%2FTERM%2BCREV%3A%3ADedicated%20Restructuring%20%2F%20Auction%20Code)

## Solving Intra-Batch Message-Ordering Races (`NEWT` + Same-Day `TERM` or `VALU`)

When a client opens and closes a derivative on the same trading day (`Day-Trade`), or when an EOD batch dispatches `NEWT` alongside `VALU` across multi-threaded Kafka workers, sending `TERM` or `VALU` **120 milliseconds ahead of `NEWT`** causes the Trade Repository to `NACK` the `TERM` (*"UTI unknown"*) and leave a permanent "zombie open trade" from the later `NEWT`! Deterministic batch sequencers enforce strict per-UTI topological ordering (`NEWT` -> `MODI` -> `CORR` -> `VALU` -> `TERM`/`ERRO`) inside a single ordered XML envelope.

## Finite-State Transition Validity & Batch Topological Sequencing Formula

Given Trade Repository shadow state $S_t(u) \in \{\emptyset, \text{OPEN}, \text{TERM}, \text{EXP}, \text{ERR}\}$ for `UTI` $u$, transition validity ($\delta$) requires both state legality and matrix compatibility:

```formula
Valid_Step(S_t, Act, Evt) =
 I( S_t == Empty AND Act in {NEWT, POSC} ) * Matrix_OK(Act, Evt)
 + I( S_t == OPEN AND Act in {MODI, CORR, VALU, TERM, ERRO} ) * Matrix_OK(Act, Evt)
 + I( S_t == TERM AND Act in {CORR, ERRO, REVI} ) * Matrix_OK(Act, Evt)
 + I( S_t in {EXP,ERR} AND Act == REVI ) * I( Evt == Blank )

Sort_Key(msg) = ( UTI(msg), Event_Timestamp(msg), Action_Rank[msg.Act] )
 where Action_Rank = { NEWT: 1, POSC: 1, REVI: 2, MODI: 3, CORR: 4, VALU: 5, TERM: 6, ERRO: 7 }

Worked Auto-Repair (Rolling Forward Missed Rollover; S_t == EXP, Desk Wants New Expiry):
 Direct MODI fails (S_t == EXP != OPEN) -> Sequencer emits [ Msg_1: REVI (New Expiry), Msg_2: VALU ] -> 100% TR ACK!
```

![Frequency of EMIR Refit lifecycle state-machine and Action/Event matrix errors before state-shadowing deployment](/api/figure?type=bars&title=Most%20Common%20Lifecycle%20State-Machine%20NACKs%20in%20Production&subtitle=Breakdown%20of%20sequence%20and%20Action%2FEvent%20violations%20across%20multi-asset%20reporting%20desks&steps=VALU%20%2F%20MODI%20on%20Expired%20UTI%3A%3A34.9%25%20sent%20updates%20after%20Field%202.44%20Expiration%20Date%20passed%7CTERM%20Sent%20on%20Scheduled%20End%3A%3A25.8%25%20mistakenly%20sent%20TERM%2BETRM%20on%20natural%20contract%20maturity%7CEvent%20Type%20Populated%20on%20CORR%3A%3A21.1%25%20attached%20TRAD%2FUPDT%20to%20CORR%20or%20ERRO%20%28must%20be%20blank%29%7CSame-Day%20TERM%20Before%20NEWT%3A%3A18.2%25%20suffered%20async%20race%20conditions%20on%20intraday%20round-trips&metrics=ALPHA%20CLEARING%3A%3ATERM%20%2B%20CLRG%3A%3ACloses%20Bilateral%20Alpha%20Trade%20Upon%20CCP%20Acceptance%7CPTRR%20COMPRESSION%3A%3AField%202.5%20ID%3A%3ALinks%20TriOptima%2FQuantile%20Multilateral%20Cycles%7CROLLING%20OPEN-ENDED%3A%3ABlank%202.44%3A%3ALeave%20Expiry%20Blank%20on%20Undated%20Rolling%20CFDs%7CUPDT%20TRANSITION%3A%3AHistorical%3A%3AUsed%20Strictly%20for%20180-Day%20Refit%20Uplift)

## Undated Rolling Contracts: Never Fake a "Tomorrow" Expiration Date!

A classic anti-pattern among retail CFD and rolling-spot FX brokers is populating `Field 2.44 (Expiration Date)` with `T+1` on open-ended undated CFDs—forcing the Trade Repository to auto-expire every open client position overnight and `NACK` tomorrow's `VALU` updates! For genuine open-ended rolling contracts without a contractual maturity date, leave `Field 2.44` **blank** until closed via `TERM + ETRM` (or compressed via `POSC + INCP`).

## Connecting Lifecycle State Machines to ETD Positions, CFDs & Completeness

Link `Action/Event` state machines directly to [ETD and CFD position-level `POSC` compression reporting](/briefings/etd-position-level-vs-trade-level-emir-reporting-compression), [203-field ISO 20022 auth.030 tag pruning](/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields), and [automated T+1 open-state completeness reconciliation](/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine).

## Frequently asked questions

### What is the operational difference between TERM (Early Termination) and ERRO (Error)?

TERM means a real, legally binding derivative existed and was closed *prior to its scheduled maturity date* (due to mutual unwind ETRM, novation NOVA, compression COMP, clearing CLRG, or option exercise EXER). ERRO means the report should NEVER have existed in that Trade Repository at all (fat-finger booking, duplicate UTI, or out-of-scope non-derivative).

### When must a firm use the new EMIR Refit Action Type "REVI" (Revive)?

Once a UTI enters a "Dead" state in the Trade Repository—because someone sent ERRO, sent premature TERM, or let Field 2.44 Expiration Date pass without extending a rolling contract—the TR rejects any MODI, CORR, or VALU on that UTI! Sending Action Type = REVI restores the UTI to active "Live" status so lifecycle updates can resume.

### What distinguishes MODI (Modify) from CORR (Correct) in EMIR Refit?

MODI records a genuine commercial contract amendment agreed between counterparties on Event Date T (such as partial notional step-down, maturity extension, or corporate action CORP). CORR fixes a historical reporting mistake (such as wrong strike price or counterparty LEI submitted earlier) without any underlying legal change to the contract.

### How does POSC (Position Component) work for Exchange-Traded Derivatives and CFDs?

When two counterparties agree to net intraday ETD or retail CFD executions into a single end-of-day Position-Level UTI (Level = PSTN), each individual intraday execution is reported once at trade level with Action Type = POSC (Event Type = INCP Inclusion in Position)—which immediately closes that trade-level UTI while rolling its economics into the open Position UTI (NEWT/MODI with INCP).


## Source URLs

- https://eur-lex.europa.eu/eli/reg_impl/2022/1860/oj
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://www.fca.org.uk/markets/uk-emir

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). EMIR Refit Action Type & Event Type Lifecycle Matrix: NEWT, MODI, TERM, ERRO & REVI. RegTech Codex. https://regtechcodex.org/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro
- Canonical article: [EMIR Refit Action Type & Event Type Lifecycle Matrix: NEWT, MODI, TERM, ERRO & REVI](https://regtechcodex.org/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
