# ANNA DSB UPI (ISO 4914) & CFI Validation Guide (2026)

> Integrate the ANNA Derivatives Service Bureau (DSB) ISO 4914 Unique Product Identifier (UPI) API, ISIN vs UPI decision trees, and CFI cross-field checks.

Canonical: https://regtechcodex.org/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation
Last updated: 2026-11-14T19:38:36.142Z

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

Global ISO 20022 rewrites across EU/UK EMIR Refit, US CFTC, ASIC, MAS, and HKMA mandate the 12-character ISO 4914 Unique Product Identifier from ANNA DSB for OTC derivatives lacking a venue ISIN.

## Key takeaways

- Designated by the FSB and overseen by the Regulatory Oversight Committee (ROC), the ANNA Derivatives Service Bureau (DSB) serves as sole global issuer of 12-character ISO 4914 Unique Product Identifiers (QZ prefix + 9 alphanumerics + check character).
- Under EU/UK EMIR Refit (Fields 2.7 and 2.8), instruments traded on a Trading Venue (TOTV / SI) report an ISIN, whereas pure off-venue OTC derivatives MUST populate Field 2.8 ISO 4914 UPI.
- Trade Repositories cross-validate the submitted UPI against ANNA DSB reference JSON files—rejecting any auth.030 report whose Asset Class (2.11), Contract Type (2.10), CFI (2.9), or Delivery Type contradicts the DSB product record!
- Local read-through UPI caching indexed by canonical product-attribute hashes eliminates per-trade REST API latency and prevents duplicate DSB creation requests.

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

Prior to global `ISO 4914` adoption, regulators supervised by [IOSCO](https://www.iosco.org/), the [US CFTC](https://www.cftc.gov/), ESMA, and the [UK FCA](/regulators/financial-conduct-authority-uk-121) could not aggregate systemic OTC derivative exposures across Trade Repositories because one dealer labeled a 5-year EURIBOR swap `IRS-EUR-6M` while its counterparty labeled it `SWAP_FIXED_FLOAT`. Overseen by the **Regulatory Oversight Committee (`ROC`)**, the **ANNA Derivatives Service Bureau (`DSB`)** now issues deterministic 12-character **`Unique Product Identifiers` (`UPIs`, `QZ...`)** mandatory across [EMIR Refit 2026 Reporting](/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting), US CFTC Part 43/45, ASIC, MAS, and [HKMA](/regulators/hong-kong-monetary-authority-153). Multi-asset dealers and CFD/FX brokers such as [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [Axi](/licence-holders/axi), and [IC Markets](/licence-holders/ic-markets) maintain local synchronized ANNA DSB product caches. 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).

## ANNA DSB Product Identifier Hierarchy: Venue ISIN vs OTC ISIN vs ISO 4914 UPI

Selecting the right identifier between `Field 2.7 (ISIN)` and `Field 2.8 (UPI)` depends strictly on venue admission (`TOTV` / `SI`) while preserving parent-child taxonomy consistency:

| Instrument Scope | Venue Status | Field `2.7` (`ISIN`) | Field `2.8` (`UPI`) | Underlying Product Attributes Hashed in DSB |
| :--- | :--- | :--- | :--- | :--- |
| Exchange-Traded (`ETD` Futures/Options) | Traded on `RM` (`Eurex`, `CME`, `ICE`) | **Mandatory** Exchange `ISIN` | Optional / Derived | Exchange product code, expiry, strike, `ISO 10962 CFI` |
| Venue / `OTF` / `MTF` OTC Derivative | `TOTV` or `SI` (`RTS 23` scope) | **Mandatory** `ANNA DSB OTC ISIN` (`EZ...`) | Embedded parent `UPI` in DSB JSON | Asset class + Underlier + **Expiry Date / Tenor** (`Granular`) |
| Pure Bilateral OTC Swap (`IRS`/`NDF`) | Off-Venue (`XXXX` MIC) | Blank (`O` / Not Applicable) | **Mandatory** `ISO 4914 UPI` (`QZ...`) | Asset class (`INTR`/`CURR`), Ref Rate/Ccy Pair, Delivery (`CASH`/`PHYS`) — **No Expiry!** |
| Retail OTC `CFD` (Equity/Index/FX/Gold) | Off-Venue (`XXXX` MIC) | Blank (unless `SI` OTC ISIN) | **Mandatory** `ISO 4914 UPI` (`QZ...`) | Asset class (`EQUI`/`COMM`/`CURR`), Contract=`CFDS`, Underlier ISIN/Index |

![High-throughput ANNA DSB UPI resolution, daily delta caching, and ISO 10962 CFI cross-validation pipeline for OTC derivatives](/api/figure?type=flow&title=Local%20ANNA%20DSB%20UPI%20Cache%20%26%20CFI%20Parity%20Engine&subtitle=Achieving%20sub-millisecond%20UPI%20enrichment%20and%20zero%20Trade%20Repository%20attribute-mismatch%20rejections&steps=1.%20Daily%20DSB%20File%20Sync%3A%3AIngest%20nightly%20ANNA%20DSB%20UPI%20Golden%20Copy%20%26%20intraday%20delta%20JSON%20streams%7C2.%20Attribute%20Hash%20Key%3A%3ACanonicalize%20Asset%20Class%20%2B%20Instrument%20Type%20%2B%20Underlier%20%2B%20Settlement%7C3.%20Cache-First%20Lookup%3A%3AHit%20local%20Redis%2FPostgreSQL%20%28%3E99.4%25%29%3B%20call%20DSB%20Create%2FSearch%20REST%20on%20miss%7C4.%20Derive%20CFI%20%26%202.10%2F11%3A%3AHydrate%20auth.030%20CFI%20%282.9%29%2C%20Contract%20%282.10%29%20%26%20Delivery%20%282.154%29%20FROM%20DSB%20JSON!&metrics=UPI%20vs%20OTC%20ISIN%20DIFF%3A%3ATenor-Free%3A%3AOne%20UPI%20Covers%20All%20Maturity%20Dates%20of%20Same%20Swap%7CCFI%20LENGTH%20%28ISO%2010962%29%3A%3A6%20Letters%3A%3Ae.g.%20JFTXFC%20%28FX%20Forward%29%20%2F%20SRCCSP%20%28IRS%29%7CREST%20FALLBACK%20SLA%3A%3A%3C%20350%20ms%3A%3AOnly%20Triggered%20on%20Novel%20Exotic%20Underliers%7CBILATERAL%20UPI%20MATCH%3A%3APhase%201%3A%3AField%202.8%20Must%20Match%20Counterparty%20Report)

## The Golden Engineering Rule: Hydrate `auth.030` Taxonomy Fields *From* the DSB Record!

Why do firms suffer `22%+` UPI-related `NACK` rejections during initial UAT? Because front-office booking systems map `Field 2.9 (CFI)`, `Field 2.10 (Contract Type)`, and `Field 2.154 (Delivery Type)` from legacy internal product tables while looking up `Field 2.8 (UPI)` separately! Because Trade Repositories validate your `auth.030` submission against ANNA DSB's authoritative JSON schema for that `QZ...` code, **hydrating `CFI` and taxonomy tags directly from the matched DSB JSON record** guarantees `100.00%` cross-attribute consistency.

## Canonical UPI Attribute Hash & TR Cross-Field Consistency Equation

Reference-data microservices enforce canonical attribute equivalence ($H_{\text{dsb}}$) and bi-directional `CFI` validation before releasing any OTC report:

```formula
Key_UPI = Canonical_JSON( AssetClass, InstrumentType, Sorted_Underlier_Tuple, ReturnOrPayoutTrigger, DeliveryType )
UPI_code = Local_DSB_Cache[ SHA256(Key_UPI) ] ?? ANNA_DSB_REST_SearchOrCreate(Key_UPI)

Consistency_Gate(msg, DSB[UPI_code]) =
 I( msg.AssetClass_2_11 == DSB.AssetClass ) * I( msg.ContractType_2_10 == DSB.InstrumentMap )
 * I( msg.CFI_2_9[0:2] == DSB.ISO10962_CFI[0:2] ) * I( msg.Delivery_2_154 in DSB.AllowedDelivery )

Worked CFD Check (Single-Stock CFD on Apple US0378331005, Cash-Settled):
 DSB Record QZ... -> Asset=Equity, Type=Swap/CFD, CFI="JE..." / ContractType="CFDS", Delivery="CASH" -> Consistency_Gate = 1
```

![Distribution of ANNA DSB UPI lookup and cross-validation exceptions across OTC asset classes](/api/figure?type=bars&title=UPI%20%26%20CFI%20Reference-Data%20Breakpoints%20by%20Asset%20Class&subtitle=Where%20OTC%20derivative%20attributes%20most%20frequently%20diverge%20between%20front-office%20OMS%20and%20ANNA%20DSB&steps=Custom%20Equity%20%2F%20FX%20Baskets%3A%3A35.4%25%20mis-mapped%20multi-underlier%20custom%20basket%20identifiers%7CNDF%20vs%20Deliverable%20FX%20Fwd%3A%3A27.8%25%20confused%20CASH%20%28NDF%29%20vs%20PHYS%20%28Deliverable%20Forward%29%20UPIs%7CCFD%20Index%20vs%20Future%20Underlier%3A%3A21.3%25%20mixed%20cash-index%20UPIs%20with%20rolling%20front-month%20future%20UPIs%7CDeprecated%20IBOR%20Ref%20Rates%3A%3A15.5%25%20referenced%20ceased%20USD%20LIBOR%20enums%20instead%20of%20SOFR%2FESTR&metrics=DSB%20FEE%20TIER%20MODEL%3A%3AProgrammatic%3A%3AAnnual%20ANNA%20DSB%20API%20Subscription%20Licensing%7CNON-STANDARD%20UNDERLIER%3A%3AOther%20%2F%20Basket%3A%3AStandardized%20Fallback%20DSB%20Templates%7CCHECK-DIGIT%20GUARD%3A%3AISO%204914%20Mod%3A%3ACatches%20Manual%20Copy-Paste%20Typos%20Instantly%7CGLOBAL%20REUSE%3A%3AEU%2FUK%2FUS%2FAPAC%3A%3AIdentical%2012-Char%20UPI%20Across%20All%206%20Regimes)

## Handling Bespoke Baskets & Crypto-Underlying OTC Derivatives

For custom client equity baskets lacking an `ISIN`, ANNA DSB provides generic *Non-Standard / Basket* `UPI` templates while `EMIR Field 2.42` carries the structurer's `20-char LEI + <=52-char Basket Code` plus repeating constituent `<BsktCnsttnts>` nodes. For OTC crypto CFDs and options, firms must simultaneously populate the DSB crypto-underlier `UPI` **and** set `EMIR Field 2.12 (Derivative based on crypto-assets) = true`.

## Linking UPI Reference Data to auth.030 Validation, FX Swaps & CFDs

Pair ANNA DSB UPI pipelines directly with [203-field ISO 20022 auth.030 XML validation](/briefings/iso-20022-auth-030-xml-schema-validation-emir-refit-203-fields), [FX forward and NDF package mapping](/briefings/fx-swaps-forwards-ndf-two-leg-package-emir-refit-xml-mapping), and [retail CFD / rolling-spot FX reporting](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting).

## Frequently asked questions

### When must an EMIR Refit report populate ISIN (Field 2.7) versus UPI (Field 2.8)?

Under ESMA ITS 2022/1860 Validation Rules, Field 2.7 (ISIN) is mandatory if the derivative is admitted to trading or traded on a Trading Venue (RM, MTF, OTF) or Systematic Internaliser. For all other pure bilateral OTC derivatives (such as bespoke FX forwards, OTC CFDs without venue ISINs, or off-venue swaps), Field 2.8 (ISO 4914 UPI) is strictly mandatory.

### What is the exact structure of an ISO 4914 Unique Product Identifier?

Every ISO 4914 UPI is a fixed 12-character code starting with the reserved pseudo-country prefix QZ, followed by 9 uppercase alphanumeric characters (0-9, B-Z excluding vowels A, E, I, O, U to prevent accidental words) and 1 Luhn-mod-N check character (for example, QZ4R9K2M7P8X).

### Which asset classes require ANNA DSB UPIs under US CFTC Part 43/45 Swap Reporting?

The CFTC mandated ANNA DSB UPIs effective January 29, 2024 for four OTC swap asset classes—Interest Rates, Credit, Foreign Exchange, and Equities—and subsequently extended UPI adoption timelines toward Other Commodity swaps to align globally with CPMI-IOSCO harmonized guidance.

### Why do Trade Repositories NACK valid-looking UPI codes on bespoke OTC options or CFDs?

Every night, DTCC, REGIS-TR, and LSEG ingest the full ANNA DSB UPI Golden Copy. If a broker looks up a Cash-Settled FX Forward UPI (Delivery = CASH) but populates Field 2.154 Delivery Type = PHYS (or mismatches the ISO 10962 6-letter CFI code) inside auth.030, the TR’s reference-data cross-check fires an immediate NACK.


## Source URLs

- https://www.anna-dsb.com/upi/
- https://www.leiroc.org/publications/gls/roc_20230929.pdf
- https://www.cftc.gov/PressRoom/PressReleases/8659-23
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). ANNA DSB UPI (ISO 4914) & ISO 10962 CFI Validation for OTC Derivatives Reporting. RegTech Codex. https://regtechcodex.org/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation
- Canonical article: [ANNA DSB UPI (ISO 4914) & ISO 10962 CFI Validation for OTC Derivatives Reporting](https://regtechcodex.org/briefings/anna-dsb-upi-iso-4914-otc-derivatives-taxonomy-cfi-validation)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
