# EMIR Refit Article 7 UTI Generation Waterfall Guide (2026)

> Implement the deterministic EMIR Refit Article 7 UTI generation waterfall, reverse-ASCII LEI tie-breakers, and 10:00 UTC T+1 exchange SLAs.

Canonical: https://regtechcodex.org/briefings/bilateral-uti-generation-waterfall-emir-refit-article-7-tiebreak
Last updated: 2026-11-14T19:38:28.116Z

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

Unpaired Trade Repository submissions almost always trace back to bilateral counterparties independently minting two different Unique Transaction Identifiers—cured by coding the exact ITS 2022/1860 Article 7 waterfall.

## Key takeaways

- Under ISO 23897 and Commission Implementing Regulation (EU) 2022/1860 Article 7, every ISO 20022 UTI consists of up to 52 uppercase alphanumeric characters ([A-Z0-9]{1,52}), prefixed by the 20-character LEI of the generating entity.
- Unlike legacy EMIR where counterparties negotiated ad-hoc bilateral agreements first, EMIR Refit places venue/CCP/confirmation-platform infrastructure BEFORE bilateral agreement in the statutory waterfall.
- When two same-status counterparties trade OTC off-venue without a bilateral UTI pact, the final tie-breaker assigns UTI generation to the Seller (1.17) or first LEI in reversed ASCII order.
- Per Article 7(4), the UTI-generating entity must transmit the UTI to its counterparty no later than 10:00 UTC on T+1 so both legs pair cleanly by EOD T+1.

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

Across European and UK Trade Repositories, **Unpaired `UTI` exceptions** represent the single largest operational bottleneck in post-Refit reporting—accounting for **34.8% of all open `auth.091` reconciliation breaks**. Whenever two bilateral OTC counterparties independently mint different `Unique Transaction Identifiers` (`Field 2.1`), `DTCC GTR`, `REGIS-TR`, and `LSEG` cannot link the two halves of the contract to begin Phase-1/Phase-2 economic matching. Harmonized across CPMI-IOSCO Technical Guidance, [EU & UK EMIR Refit Standards](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting), and [US CFTC Swap Reporting Rules](/definitions/cftc-nfa-rule2-9-u-s-cftc-nfa-compliance-rule-2-9-swap-dealer-fcm-supervision), global dealers and prime brokers like [ICAP](/licence-holders/icap), [CMC Markets](/licence-holders/cmcmarkets), and [Equiti](/licence-holders/equiti) execute a deterministic **Article 7 UTI Waterfall**. Consult 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).

## Step-by-Step ITS (EU) 2022/1860 Article 7 UTI Generation Waterfall

Unlike 2014 EMIR, counterparties **cannot** override market infrastructure via private bilateral agreements when a trading venue or CCP sits in the execution chain. Evaluate these ordered steps from top (`Priority 1`) to bottom (`Priority 8`):

| Waterfall Step | Execution / Counterparty Context | Statutory UTI Generator | Delivery Channel & Format | Common Implementation Pitfall |
| :--- | :--- | :--- | :--- | :--- |
| **1. Cleared Trade (`CCP`)** | Cleared derivative (post-novation `beta`/`gamma` legs) | **Central Counterparty (`CCP`)** (`LCH`, `Eurex`, `CME`) | CCP clearing confirmation message (`LEI_CCP + ID`) | Re-using pre-clearing `alpha` trade UTI on cleared legs |
| **2. Venue Trade (`TV`)** | Executed on `RM`, `MTF`, `OTF`, or equivalent `SEF` | **Trading Venue** (e.g., [ICAP](/licence-holders/icap) MTF / Bloomberg MTF) | Real-time FIX ExecutionReport Tag `1903` / `ExecID` | Broker overwriting MTF-assigned UTI with internal trade ID |
| **3. Cross-Border Sooner SLA** | Bilingual trade where 3rd country has faster deadline (e.g., US `CFTC` `T+0`/`ASAP`) | **Counterparty under sooner-deadline regime** | `FIX` / `MarkitWire` / `FpML` confirm | EU bank ignoring US Swap Dealer's `CFTC` UTI |
| **4. Confirmation Platform** | Electronically confirmed off-venue (`MarkitWire`, `FXAll`, `Traiana`) | **Confirmation Platform** (if mutually enabled) | Electronic confirmation payload | One side disabling platform-UTI ingestion |
| **5. Bilateral Agreement** | Off-venue bilateral OTC with documented UTI pact | **Contractually agreed party** (e.g., Liquidity Provider) | Master Reporting / ISDA UTI Annex | Unsigned or ambiguous email agreement |
| **6. Cross-Border Single-EU** | Only 1 party subject to EU EMIR (other non-EEA, non-sooner) | **EU Counterparty** (or `FC` over `NFC-` under Art. 9(1a)) | API / Portal / Swift `MT300` (`22L`) | Non-EEA prime failing to echo EU client's UTI |
| **7. Regulatory Hierarchy** | `FC` vs `NFC+` (off-venue, no agreement) | **Financial Counterparty (`FC`)** | Electronic confirm (`<= 10:00 UTC T+1`) | Misclassifying counterparty `FC` vs `NFC+` status |
| **8. Final Tie-Breaker** | Same status (`FC` vs `FC`) off-venue, no pact | **Seller** (if `1.17` applies); else **LEI sort tie-break** | Automated pre-10:00 UTC T+1 feed | Reversing EU vs CFTC ASCII tie-breaker order! |

![Deterministic EMIR Refit Article 7 UTI generation waterfall from CCP and Trading Venue down to Seller and LEI sort tie-breakers](/api/figure?type=flow&title=Deterministic%20Article%207%20UTI%20Resolution%20%26%2010%3A00%20UTC%20Exchange&subtitle=Ensuring%20both%20bilateral%20counterparties%20converge%20on%20a%20single%20ISO%2023897%2052-char%20identifier%20before%20T%2B1%20submission&steps=1.%20Infrastructure%20Check%3A%3AConsume%20CCP%20or%20MTF%2FOTF%2FSEF%20UTI%20verbatim%20if%20cleared%20or%20venue-traded%7C2.%20Cross-Border%20%26%20Platform%3A%3ADefer%20to%20sooner-SLA%20regime%20%28US%20SD%29%20or%20electronic%20confirm%20platform%7C3.%20Bilateral%20%2F%20FC%20Rank%3A%3AApply%20signed%20UTI%20pact%20-%3E%20FC%20over%20NFC%2B%20-%3E%20Seller%20on%201.17%20contracts%7C4.%2010%2000%20UTC%20T%2B1%20Sync%3A%3ATransmit%20LEI%2820%29%2BAlphanum%28%3C%3D32%29%20via%20FIX%2FSwift%2FAPI%20%26%20monitor%20pairing&metrics=MAX%20UTI%20LENGTH%3A%3A52%20Chars%3A%3A20-Char%20Generating%20LEI%20%2B%20%3C%3D32%20Unique%20ID%7CHYPHENS%20%2F%20SYMBOLS%3A%3AForbidden%3A%3AISO%2023897%20Strict%20%5BA-Z0-9%5D%20Regex%7CALPHA%20-%3E%20BETA%2FGAMMA%3A%3APrior%20UTI%3A%3ALink%20Cleared%20Legs%20via%20Field%202.3%20Prior%20UTI%7CFALLBACK%20REMEDIATION%3A%3AERRO%20%2B%20NEWT%3A%3ARequired%20If%20Temporary%20UTI%20Replaced%20Later)

## Beware the EU vs CFTC/ASIC ASCII Tie-Breaker Trap!

Compliance architects operating trans-Atlantic swap engines must guard against a notorious specification quirk at **Step 8** when two `FC` swap dealers trade a two-leg interest-rate or FX swap off-venue without a confirmation platform or bilateral pact: under **EU ITS 2022/1860 Article 7(2)(k)(ii)** and **UK EMIR**, the counterparty whose `LEI` comes first in **reversed** ASCII sort order (`Z` before `A`, `9` before `0`) generates the UTI—the exact **opposite** of standard ASCII order used in CPMI-IOSCO / ASIC baselines! Executing a two-page **ISDA/GFMA Bilateral UTI Generation Annex** at **Step 5** cleanly bypasses Step 8 altogether.

## ISO 23897 Format & Deterministic Generator Assignment Formula

Order-management engines validate `ISO 23897` syntax and compute deterministic generator ownership ($G_{\text{uti}} \in \{\text{Infra}, A, B\}$) immediately at trade capture:

```formula
Valid_ISO23897(u) = I( 21 <= len(u) <= 52 ) * I( Regex_Match(u, "^[A-Z0-9]{20}[A-Z0-9]{1,32}$") ) * I( Valid_GLEIF_Checksum(u[0:20]) )

G_uti(Trade) = CCP if Is_Cleared_Leg == 1
 = Venue else if Traded_On_TV_SEF == 1
 = Sooner_Regime_Pty else if Has_T0_ThirdCountry_Duty == 1
 = Confirm_Platform else if Confirmed_With_Platform_UTI == 1
 = Agreed_Generator else if Has_Bilateral_UTI_Pact == 1
 = FC_Party else if Status(A) != Status(B)
 = Seller_Party else if Uses_Field_1_17_BuyerSeller == 1
 = ArgMax_ASCII(LEI_A, LEI_B) (EU/UK Reversed-ASCII Final Tie-Breaker)

Worked Check: LEI_A = "549300ABC..." vs LEI_B = "213800XYZ..." -> "5" > "2" in ASCII -> Party A generates UTI under EU Step 8!
```

![Share of bilateral UTI pairing breaks by operational failure point across OTC FX, rates, and equity derivatives](/api/figure?type=bars&title=Root%20Causes%20of%20T%2B1%20Unpaired%20UTI%20Exceptions%20at%20TRs&subtitle=Breakdown%20of%20unlinked%20derivative%20reports%20across%20DTCC%20GTR%2C%20REGIS-TR%2C%20and%20LSEG%20UnaVista&steps=Late%20T%2B1%20Generator%20Feed%3A%3A39.2%25%20delivered%20UTI%20after%2010%3A00%20UTC%20forcing%20temporary%20fallback%20UTIs%7CFX%20Swap%20Far%2FNear%20Leg%20Split%3A%3A24.6%25%20generated%202%20UTIs%20while%20counterparty%20reported%201%20single%20UTI%7CLegacy%20Prefix%20%2F%20Hyphens%3A%3A19.8%25%20prepended%20%22E01%22%20or%20%22-%22%20breaking%20ISO%2023897%20exact%20string%20match%7CVenue%20vs%20Broker%20Overwrite%3A%3A16.4%25%20ignored%20MTF%20Tag%201903%20UTI%20and%20minted%20proprietary%20trade%20IDs&metrics=SWIFT%20MT300%20FIELD%3A%3ATag%2022L%20%2F%2022M%3A%3ACarries%20ISO%2023897%20UTI%20in%20FX%20Confirms%7CFIX%20PROTOCOL%20TAG%3A%3ATag%201903%2F2828%3A%3ARegulatoryTradeID%20Standard%20Transport%7CUTI%20IMMUTABILITY%3A%3ALifetime%3A%3ACannot%20Modify%20UTI%20via%20MODI%2FCORR%20%28Use%20ERRO%2BNEWT%29%7CPRIOR%20UTI%20CHAIN%3A%3AField%202.3%3A%3APreserves%20Novation%2C%20Clearing%20%26%20Compression%20Lineage)

## Why You Can Never "Correct" a Wrong UTI Using `CORR` or `MODI`

Because Trade Repositories index every derivative record by the composite primary key `(Reporting Counterparty LEI, Other Counterparty LEI, UTI)`, `Field 2.1 (UTI)` is strictly immutable! If a broker submits a temporary fallback `UTI_TEMP` on `T+1` and receives the counterparty's authoritative `UTI_TRUE` on `T+2`, sending `CORR` will simply create or fail on the key—instead, the firm must send **`Action Type = ERRO`** on `UTI_TEMP` followed immediately by **`Action Type = NEWT`** on `UTI_TRUE`.

## Linking UTI Generation to Inter-TR Pairing, FX Swaps & Lifecycle Matrices

Connect deterministic UTI waterfalls directly to [inter-TR pairing and Phase-2 matching engines](/briefings/emir-refit-inter-tr-pairing-matching-valuation-tolerance-bands), [two-leg FX swap single-vs-dual UTI conventions](/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mapping), and [ERRO/REVI/NEWT lifecycle state machines](/briefings/emir-action-type-event-type-lifecycle-matrix-newt-modi-term-erro).

## Frequently asked questions

### What is the exact format and character-set constraint for an ISO 23897 UTI under EMIR Refit?

Under ISO 23897 and EMIR Refit Field 2.1, a new UTI must contain a maximum of 52 characters composed strictly of uppercase Latin letters A–Z and digits 0–9 (zero hyphens, underscores, colons, or spaces!), starting with the valid 20-character GLEIF LEI of the UTI-generating entity followed by up to 32 unique alphanumeric characters.

### How does the "LEI Reverse ASCII Sort" tie-breaker work in ITS 2022/1860 Article 7?

When two same-status counterparties trade a two-leg swap off-venue without a bilateral agreement, EU ITS 2022/1860 Art. 7(2)(k)(ii) and UK EMIR compare their 20-character LEIs in reversed ASCII order (Z before A, 9 before 0)—the exact opposite of standard ASCII used in ASIC/CPMI-IOSCO! Signing an ISDA Bilateral UTI Annex at Step 5 avoids tie-breaker collisions.

### What happens if the UTI-generating counterparty fails to send the UTI before 10:00 UTC on T+1?

If the counterparty responsible for generating the UTI fails to deliver it in time to meet the T+1 reporting deadline, ESMA Q&As advise the non-generating party NOT to refrain from reporting; instead, it submits a temporary fallback UTI on T+1 to meet timeliness duties and subsequently submits ERRO + NEWT (or agreed remediation) once the true bilateral UTI arrives.

### How does UK EMIR’s UTI waterfall handle cross-border UK-to-EU OTC trades?

Both EU ITS 2022/1860 Article 7 and the FCA/BoE UK EMIR Technical Standards include cross-jurisdictional recognition steps: if a trade is subject to a third-country jurisdiction with a sooner reporting deadline (such as US CFTC real-time/ASAP reporting), that third-country ruleset’s UTI generator takes priority globally so a single ISO 23897 UTI spans all SDRs and TRs.


## Source URLs

- https://eur-lex.europa.eu/eli/reg_impl/2022/1860/oj
- https://www.bis.org/cpmi/publ/d158.htm
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). Bilateral UTI Generation Waterfall: EMIR Refit ITS Article 7 Tie-Breakers & Pairing SLAs. RegTech Codex. https://regtechcodex.org/briefings/bilateral-uti-generation-waterfall-emir-refit-article-7-tiebreak
- Canonical article: [Bilateral UTI Generation Waterfall: EMIR Refit ITS Article 7 Tie-Breakers & Pairing SLAs](https://regtechcodex.org/briefings/bilateral-uti-generation-waterfall-emir-refit-article-7-tiebreak)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
