# MiFIR Article 26 & RTS 22 ARM Reporting Guide (2026)

> Audit EU/UK MiFIR Article 26 (RTS 22) ISO 20022 auth.016 transaction reports: Annex II natural-person CONCAT priorities, INTC accounts, TOTV, and Algo IDs.

Canonical: https://regtechcodex.org/briefings/mifir-rts-22-article-26-arm-transaction-reporting-national-id
Last updated: 2026-11-14T19:40:14.701Z

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

While EMIR monitors open derivative positions, MiFIR Article 26 (RTS 22) polices market abuse—requiring T+1 submission of 65-field ISO 20022 auth.016 reports via an Approved Reporting Mechanism with strict Annex II natural-person identifiers and INTC aggregation.

## Key takeaways

- MiFIR Article 26 (RTS 22) mandates T+1 ARM reporting (auth.016) on instruments Traded on a Trading Venue (TOTV) or OTC derivatives whose underlying security or index constituent is TOTV.
- MiFIR RTS 22 Annex II mandates statutory National Client IDs for natural persons (e.g., UK NINO, Spanish DNI, Italian CF, or 20-char CONCAT = ISO2 + YYYYMMDD + First5# + Surname5#).
- Correct population of the INTC (Aggregate Client Account) convention prevents broken buyer/seller chains when a broker fills one market block order and allocates across multiple underlying retail or institutional clients.
- Fields 57–59 require deterministic 50-byte identifiers for the specific Investment Decision Within Firm and Execution Within Firm—whether a natural-person trader (National ID) or registered Algorithm (Algo ID).

## 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.
- **MiFID II Annex II Elective Professional vs. Retail Client Categorization** (MIFID2-CLIENT-CAT) — license: MiFID II Annex II Elective Professional vs. Retail Client Categorization (MIFID2-CLIENT-CAT) refers to an institutional financial benchmark and regulatory standard monitored by ESMA Directive 2014/65/EU (EU), currently calibrated at EUR 500,000 (Portfolio Size Criterion (2 of 3)) as of October 2026.
- **UK FCA Consumer Duty (PRIN 2A) & Section 21 Financial Promotions Gateway** (FCA-CONSUMER-DUTY) — license: UK FCA Consumer Duty (PRIN 2A) & Section 21 Financial Promotions Gateway (FCA-CONSUMER-DUTY) refers to an institutional financial benchmark and regulatory standard monitored by UK Financial Conduct Authority (UK), currently calibrated at 2 Years (Max s21 Statutory Penalty) as of October 2026.

## Analysis

Over **GBP 90 million in cumulative transaction-reporting fines** imposed by the [UK Financial Conduct Authority](/regulators/financial-conduct-authority-uk-121)—alongside ongoing thematic sweeps by [AMF France](/regulators/amf), [AFM Netherlands](/regulators/afm), BaFin, and ESMA under the 2024–2026 **MiFIR Review (`Regulation (EU) 2024/791`)**—demonstrate that `MiFIR Article 26` (`RTS 22`) tolerates zero clerical sloppiness. Across multi-asset retail and institutional investment firms governed by [MiFID II Client Categorization](/definitions/mifid2-client-cat-mifid-ii-annex-ii-elective-professional-vs-retail-client-categorization)—such as [Interactive Investor](/licence-holders/interactive-investor), [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), and [London Capital Group](/licence-holders/london-capital-group-ltd-2687)—compliance engineering teams submit daily `ISO 20022 auth.016.001.01` files via Approved Reporting Mechanisms (`ARMs`) and reconcile against NCA **`MDP` / `FIRDS` Golden Source extracts**. 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).

## Critical RTS 22 Field & Annex II Natural-Person Identifier Rules

Unlike `EMIR` (where retail clients use internal firm IDs), `MiFIR RTS 22` tracks insider trading down to the exact human passport, national insurance number, or normalized `CONCAT` string across borders:

| Client Nationality (`ISO-2`) | Annex II **Priority 1** Identifier | Annex II **Priority 2 / 3** Fallback | Exact Formatting & Validation Rule |
| :--- | :--- | :--- | :--- |
| **United Kingdom (`GB`)** | UK National Insurance Number (`NINO`) | `GB` + **`CONCAT`** (`Priority 2`) | `GB` + `2 letters + 6 digits + A/B/C/D` (Never passport!) |
| **DE, FR, IE, AT, NL, LU** | **`CONCAT`** (`Priority 1` ONLY!) | None (`CONCAT` always derivable!) | `CC + YYYYMMDD + First5(#-pad) + Surname5(#-pad)` (`20 chars`) |
| **IT, ES, PL, EE, SE, DK** | Statutory Tax/Personal Code (`CF`, `DNI`, `PESEL`, `Isikukood`, `CPR`) | Passport / **`CONCAT`** (per Annex II row) | Validate official check-digit (`Codice Fiscale` / `PESEL` mod-10) |
| **All Non-EEA (`US`, `SG`, `AU`)** | National Passport Number (`CC` + Passport) | **`CONCAT`** (`Priority 2`) | Strip spaces/hyphens; capture **all** dual nationalities at KYC! |

![MiFIR Article 26 RTS 22 transaction reporting pipeline from ESMA/FCA FIRDS TOTV check to CONCAT generation, INTC balancing, and NCA MDP reconciliation](/api/figure?type=flow&title=MiFIR%20Article%2026%20%28RTS%2022%29%20ARM%20Validation%20%26%20MDP%20Recon%20Pipeline&subtitle=Enforcing%20FIRDS%20TOTV%2Funderlier%20checks%2C%20dual-nationality%20Annex%20II%20sorting%2C%20and%20zero-net%20INTC%20warehousing&steps=1.%20FIRDS%20TOTV%20%26%20Underlier%3A%3AQuery%20ESMA%2FFCA%20FIRDS%20for%20direct%20ISIN%20TOTV%20or%20OTC%20underlier%2Findex%20TOTV%7C2.%20Annex%20II%20%26%20CONCAT%3A%3ASort%20dual%20nationalities%20alphabetically%3B%20build%20validated%20NINO%2FPESEL%2FCONCAT%7C3.%20Capacity%20%26%20INTC%20Check%3A%3AMap%20DEAL%2FMTCH%2FAOTC%20capacity%3B%20assert%20sum%28Market%20INTC%29%20%3D%3D%20sum%28Client%20INTC%29%7C4.%20ARM%20-%3E%20NCA%20Sample%3A%3ATransmit%20auth.016%20XML%3B%20pull%20regular%20FCA%20MDP%20%2F%20NCA%20XML%20sample%20for%203-way%20recon&metrics=CONCAT%20EXACT%20LENGTH%3A%3A20%20Chars%3A%3ACC%282%29%2BYYYYMMDD%288%29%2BFirst%285%29%2BLast%285%29%7CTRADING%20CAPACITY%3A%3ADEAL%2FMTCH%2FAOTC%3A%3APrincipal%20vs%20Matched%20Principal%20vs%20Agent%7CSHORT-SELLING%20FLAG%3A%3AField%2062%3A%3AUpdated%20Under%20MiFIR%20Review%20RTS%2022%20Reform%7CNCA%20SAMPLE%20AUDIT%3A%3AFCA%20Art.%2015%283%29%3A%3ADirect%20NCA%20Data%20Request%20Mandate)

## Mastering RTS 22 `CONCAT` String Normalization & Transliteration

Even a single stray apostrophe (`O'CONNOR`), accented character (`MÜLLER`), prefix (`VAN DER BERG`), or unstripped title (`DR.`) corrupts `CONCAT` matching across European NCAs! Under `RTS 22 Annex II`, firms must: **(1)** strip honorifics (`MR`, `DR`, `SIR`, `PROF`) and nobility/surname prefixes specified in ESMA's table (`VON`, `VAN`, `DE LA`); **(2)** transliterate diacritics to plain uppercase ASCII (`Ü -> U`, `ß -> SS`, `Ø -> O`, `Ł -> L`); **(3)** strip hyphens, spaces, and apostrophes (`O'CONNOR -> OCONNOR`); and **(4)** take the first 5 letters of the first forename and surname, right-padding shorter names (`LI` -> `LI###`) to exactly 5 characters.

## Deterministic Dual-Nationality `CONCAT` & `INTC` Zero-Balance Equations

Pre-ARM validation engines verify both `RTS 22 Article 6` dual-nationality priority selection and `INTC` warehouse conservation:

```formula
Primary_Country(Client) = Min_Alphabetical_ISO2( Client.All_Verified_Nationalities )
CONCAT(cc, dob, fn, sn) = cc + YYYYMMDD(dob) + PadRight5(CleanASCII(fn), "#") + PadRight5(CleanASCII(sn), "#")

INTC_Balanced(ISIN_i, Day_d) = I( sum_(m in Market_Legs(i,d)) Qty(m) == sum_(c in Client_Allocs(i,d)) Qty(c) )

Worked Dual-Nationality Case (Jane Li, Born 1988-05-14, Dual German "DE" & UK "GB" Citizen):
 Min_Alphabetical("DE", "GB") = "DE" -> Annex II Row DE Priority 1 = CONCAT
 -> Client_ID = "DE" + "19880514" + "JANE#" + "LI###" = "DE19880514JANE#LI###" (20 chars exact!)
```

![Leading MiFIR Article 26 transaction reporting errors cited in FCA Market Watch and ESMA supervisory reviews](/api/figure?type=bars&title=Top%20MiFIR%20RTS%2022%20Errors%20Flagged%20in%20FCA%20Market%20Watch&subtitle=Share%20of%20remediated%20back-reporting%20populations%20across%20UK%20and%20EEA%20investment%20firms&steps=National%20ID%20%2F%20CONCAT%20Bugs%3A%3A34.1%25%20used%20Passport%20instead%20of%20Priority%201%20ID%20or%20botched%20CONCAT%20padding%7CUnbalanced%20INTC%20%2F%20Capacity%3A%3A26.7%25%20left%20dangling%20INTC%20fills%20or%20confused%20DEAL%20vs%20AOTC%2FMTCH%7CMissed%20OTC%20Underlier%20TOTV%3A%3A21.9%25%20missed%20index%2Fbasket%20CFDs%20containing%20%3E%3D1%20EEA%2FUK%20TOTV%20stock%7CDecision%20%2F%20Algo%20ID%20Errors%3A%3A17.3%25%20populated%20firm%20LEI%20or%20stale%20employee%20ID%20in%20Fields%2057-59&metrics=TRANSMISSION%20ART.%204%3A%3AAll-or-Nothing%3A%3AInvalid%20RTS%2022%20Art.%204%20Transfer%20Forces%20Full%20Report%7CUK%20VS%20EU%20TOTV%20SPLIT%3A%3AFCA%20vs%20ESMA%3A%3ASeparate%20FCA%20FIRDS%20vs%20ESMA%20FIRDS%20Post-Brexit!%7CMIFIR%20REVIEW%202024%2F791%3A%3AOTC%20Scope%20Rev%3A%3AReforms%20OTC%20Derivative%20Ref-Data%20Alignment%7CBACK-REPORT%20WINDOW%3A%3AUp%20to%205%20Years%3A%3AFull%20Historical%20Replay%20on%20Systematic%20Bugs)

## Post-Brexit Divergence: Separate `FCA FIRDS` vs `ESMA FIRDS` `TOTV` Checks!

Dual-regulated London/EU brokers must never query ESMA's `FIRDS` database alone to decide UK MiFIR reportability: post-Brexit, the [UK FCA](/regulators/financial-conduct-authority-uk-121) operates its own independent **FCA `FIRDS`** (`Financial Instruments Reference Data System`)! A US equity traded solely on a London MTF (`Turquoise UK`) is `TOTV` in **UK `FCA FIRDS`** (reportable to the FCA) even if absent from **EU `ESMA FIRDS`**, and vice versa.

## Linking MiFIR RTS 22 to Retail CFDs, GLEIF LEIs & Three-Way Recon

Pair `MiFIR auth.016` validation directly with [retail CFD & rolling-spot FX dual EMIR/MiFIR reporting](/briefings/cfd-rolling-spot-fx-retail-broker-emir-mifir-dual-reporting), [GLEIF LEI pre-trade "No LEI, No Trade" gates](/briefings/gleif-lei-lapsed-status-renewal-rejections-emir-mifir-reporting), and [automated T+1 three-way ARM/MDP reconciliation](/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine).

## Frequently asked questions

### Why are OTC single-stock and equity-index CFDs reportable under BOTH EMIR and MiFIR Article 26?

Under MiFIR Article 26(2)(b)-(c), an off-venue OTC derivative (MIC = XXXX) is still MiFIR-reportable if its underlying is a financial instrument traded on an EEA/UK Trading Venue (e.g., an OTC CFD on Vodafone or Apple shares traded on XETRA/LSE) or an index/basket composed of venue-traded instruments (e.g., FTSE 100 or DAX 40 CFD)—triggering both EMIR auth.030 (to a TR) and MiFIR auth.016 (to an ARM)!

### How is a MiFIR RTS 22 "CONCAT" natural-person identifier constructed when Priority 1 National ID does not use a tax/passport number?

RTS 22 Annex II sets per-country priority rules across EEA, UK, and ROW. Where CONCAT is Priority 1 (e.g., DE, FR, IE, AT, NL), it is an exact 20-character string: CC (2-letter ISO nationality) + YYYYMMDD (DOB) + first 5 uppercase ASCII letters of first name (#-padded, titles stripped) + first 5 uppercase ASCII letters of surname (#-padded).

### How do dual-nationality retail clients get identified under MiFIR RTS 22 Article 6?

Under RTS 22 Article 6(2), if a natural person holds nationalities of more than one country, the firm MUST sort the client’s two-letter ISO 3166-1 alpha-2 country codes alphabetically (e.g., dual French FR and British GB citizen -> FR comes before GB!) and apply the Annex II Priority 1 identifier of that alphabetically first country (FR -> CONCAT, NOT UK NI Number!).

### How does FCA Market Watch penalize misuse of the "INTC" (Aggregate Client Account) code?

FCA Market Watch newsletters repeatedly flag firms leaving unbalanced INTC legs! INTC is a temporary warehouse virtual counterparty used ONLY to link multiple market fills (M legs) to multiple client allocations (C legs) executed at an average price on the same day—the sum of quantities into INTC MUST equal 100.00% of quantities allocated out of INTC at end of day!


## Source URLs

- https://eur-lex.europa.eu/eli/reg_del/2017/590/oj
- https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mifir/article-26
- https://www.fca.org.uk/markets/uk-mifir/transaction-reporting

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). MiFIR Article 26 & RTS 22 Transaction Reporting: ARM auth.016, TOTV & CONCAT IDs. RegTech Codex. https://regtechcodex.org/briefings/mifir-rts-22-article-26-arm-transaction-reporting-national-id
- Canonical article: [MiFIR Article 26 & RTS 22 Transaction Reporting: ARM auth.016, TOTV & CONCAT IDs](https://regtechcodex.org/briefings/mifir-rts-22-article-26-arm-transaction-reporting-national-id)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
