Skip to content
RegTech Codex
Directory

Emir Refit Mifir Trade Reporting

MiFIR Article 26 & RTS 22 Transaction Reporting: ARM auth.016, TOTV & CONCAT IDs

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.

By Victoria Ashworth, LL.M, CAMSReview not recorded · Updated
MiFIR Article 26 & RTS 22 Transaction Reporting: ARM auth.016, TOTV & CONCAT IDs — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (EMIR Refit ISO 20022 XML, UTI Pairing, UPI Reference Data & Reconciliation): ISO 20022 auth.016 65-field ARM reporting, Annex II dual-nationality CONCAT math, TOTV, and INTC balance.Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

Over GBP 90 million in cumulative transaction-reporting fines imposed by the UK Financial Conduct Authority—alongside ongoing thematic sweeps by AMF France, AFM Netherlands, 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—such as Interactive Investor, CMC Markets, ICAP, and London Capital Group—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 inside the EMIR & MiFIR reporting hub.

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:

Quantitative Distribution · Annex II Priority 2 / 3 Fallback
Annex II Priority 2 / 3 Fallback
01United Kingdom (GB)GB + CONCAT (Pr…02All Non-EEA (US, SG, AU)CONCAT (Priorit…
Client Nationality (ISO-2)Annex II Priority 1 IdentifierAnnex II Priority 2 / 3 FallbackExact 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, LUCONCAT (Priority 1 ONLY!)None (CONCAT always derivable!)CC + YYYYMMDD + First5(#-pad) + Surname5(#-pad) (20 chars)
IT, ES, PL, EE, SE, DKStatutory 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
MiFIR Article 26 RTS 22 transaction reporting pipeline from ESMA/FCA FIRDS TOTV check to CONCAT generation, INTC balancing, and NCA MDP reconciliationVerified Exhibit

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 or model from the articleNot independently verified
Primary_Country(Client) = Min_Alphabetical_ISO2( Client.All_Verified_Nationalities )
  • CONCAT(cc, dob, fn, sn) = cc + YYYYMMDD(dob) + PadRight5(CleanASCII(fn), "#") + PadRight5(CleanASCII(sn), "#")
  • INTCBalanced(ISINi, Dayd) = I( sum(m in MarketLegs(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
Leading MiFIR Article 26 transaction reporting errors cited in FCA Market Watch and ESMA supervisory reviewsVerified Exhibit

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 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, GLEIF LEI pre-trade "No LEI, No Trade" gates, and automated T+1 three-way ARM/MDP reconciliation.

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!

Publication record

Published
13 November 2026
Updated
14 November 2026
Author
Victoria Ashworth, LL.M, CAMS
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). 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
Explore Emir Refit Mifir Trade Reporting Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

MiFIR Article 26 & RTS 22 ARM Reporting Guide (2026) | RegTech Codex