# MiFIR Article 26 & RTS 22 EEA Branch Transaction Reporting

> Configure MiFIR Article 26 and RTS 22 T+1 transaction reporting for EEA passported branches: Home NCA hub routing, Field 16/37 country flags, and CONCAT IDs.

Canonical: https://eurofirmledger.com/bulletins/mifir-article-26-arm-passport-branch-transaction-reporting-t1
Last updated: 2026-11-14T20:01:37.970Z

**Publication:** Euro Firm Ledger
**Category:** Mifid2 Article34 35 Eea Passporting
**Published:** 2026-11-14T10:50:25.915Z
**Author:** Lukas Lindqvist, CEFA (Certified European Financial Analyst (EFFAS/CEFA, Frankfurt & Zurich))
**Reviewer:** Not recorded

## Answer-first summary

Under MiFIR Article 26 and Delegated Regulation (EU) 2017/590 Article 14, EEA branches submit all 65-field T+1 transaction reports to their Home NCA, which routes records onward via ESMA TREM.

## Key takeaways

- Under RTS 22 Article 14(1), EEA investment firms submit 100% of T+1 transaction reports—including all trades executed by foreign Article 35 branches—solely to their Home NCA.
- ESMA’s TREM system automatically routes branch transaction copies to the relevant Host Branch NCA and Most Relevant Market NCA based on ISO country codes in Fields 16, 37, 46, and 58.
- Cross-border retail onboarding systems must enforce RTS 22 Annex II country-by-country identifier priorities (e.g., Spanish NIF, Italian Codice Fiscale, Polish PESEL) rather than defaulting to CONCAT.
- For dual-national clients, RTS 22 Article 6(2) mandates sorting ISO alpha-2 country codes alphabetically (e.g., DE before ES) and reporting the first code’s Priority 1 identifier.

## Related financial entities

- **European Securities and Markets Authority (ESMA)** (ESMA) — license: Independent European Union authority contributing to safeguarding the stability of the EU financial system by enhancing investor protection and promoting stable markets.
- **Global Legal Entity Identifier Foundation (GLEIF) Standard** (GLEIF-LEI) — product: Global standard for the 20-character alphanumeric Legal Entity Identifier (LEI) uniquely identifying legally distinct entities engaging in financial transactions.
- **MiFID II Cross-Border Passporting Framework** (MIFID2-PASS) — license: Harmonized European framework allowing authorized investment firms to provide investment services across all EU member states and EEA countries.

## Analysis

One of the sharpest operational traps in cross-border MiFID II compliance sits at the intersection of **MiFID II Article 35(8)** and **Commission Delegated Regulation (EU) 2017/590 (RTS 22) Article 14**: although Article 35(8) gives the host regulator supervisory authority over branch compliance with MiFIR Article 26, **RTS 22 Article 14(1) mandates that an EEA investment firm submit 100% of its T+1 transaction reports—including every trade executed by its foreign EEA branches—exclusively to the Home National Competent Authority**, never directly to the host regulator's portal!

Within our [MiFID II EEA passporting cornerstone guide](/bulletins/mifid-ii-article-34-35-eea-passporting-host-nca-guide-2026) and the [EEA passporting hub](/topics/mifid2-article34-35-eea-passporting), misrouting branch XML files directly to a host supervisor or mispopulating RTS 22 branch-country ISO tags causes immediate Approved Reporting Mechanism (ARM) schema rejections and multi-hundred-thousand-euro back-reporting remediation orders from [BaFin](/competent-authorities/bafin), [AFM](/competent-authorities/afm), and [CSSF](/competent-authorities/cssf).

## Hub-and-Spoke TREM Routing Under RTS 22 Article 14 and MiFIR Review Updates

Prior to 2018, under MiFID I, EEA branches often submitted local equity reports directly to host authorities while sending derivatives elsewhere, producing massive duplicate and orphaned records. RTS 22 solved this by centralizing ingestion through the **Home NCA + ESMA Transaction Reporting Exchange Mechanism (TREM)**:
- **Single Submission Endpoint**: An Austrian or Dutch dealer such as [UniCredit Bank Austria](/firms/bank-austria) or [Algemene Bank Nederland](/firms/algemene-bank-nederland) transmits a single consolidated ISO 20022 auth.016 XML feed via its licensed ARM (e.g., MarketAxess Trax, UnaVista/LSEG, or Deutsche Borse REGIS-TR) to its home authority no later than the close of the following working day (T+1).
- **Automated TREM Fan-Out**: Using the two-letter ISO 3166-1 alpha-2 country codes populated in RTS 22 **Fields 8, 16, 37, 46, and 58**, the home NCA automatically forwards copies via ESMA TREM to (a) the NCA of the most relevant market in terms of liquidity (MRM), (b) the host NCA of any branch involved in client membership, supervision, or execution, and (c) the NCA supervising the executing trader.

![MiFIR Article 26 and RTS 22 Article 14 T+1 transaction reporting routing from EEA branch via ARM to Home NCA and ESMA TREM](/api/figure?type=flow&title=RTS%2022%20Article%2014%20Branch%20Transaction%20Reporting%20Pipeline&subtitle=65-field%20ISO%2020022%20auth.016%20T%2B1%20ingestion%20through%20Home%20NCA%20and%20ESMA%20TREM%20fan-out&steps=1.%20Trade%20%26%20ID%20Gate%3A%3ANo%20LEI%2C%20No%20Trade%20%28corp%29%20%2B%20Annex%20II%20NatID%2FCONCAT%7C2.%20Branch%20ISO%20Tags%3A%3APopulate%20Fields%2016%2C%2037%2C%2046%20%26%2058%20country%20codes%7C3.%20T%2B1%20ARM%20Feed%3A%3ASubmit%20100%25%20of%20branch%20%2B%20HQ%20trades%20to%20Home%20NCA%7C4.%20ESMA%20TREM%20Relay%3A%3AAuto-fanout%20to%20Host%20Branch%20NCA%20%26%20MRM%20Liquidity%20NCA&metrics=REPORTING%20DEADLINE%3A%3AT%2B1%20Close%3A%3AMiFIR%20Art.%2026%281%29%20hard%20cutoff%7CRTS%2022%20DATA%20FIELDS%3A%3A65%20Fields%3A%3AISO%2020022%20auth.016%20XML%20schema%7CNATIONAL%20ID%20RULES%3A%3A30%20Priorities%3A%3ARTS%2022%20Annex%20II%20country%20table%7CLEI%20VALIDATION%3A%3AMandatory%3A%3ARTS%2022%20Art.%2013%20pre-trade%20check)

## Critical RTS 22 Branch Country Fields & Annex II Natural-Person Identifier Priority

Passported firms onboarding retail savers across 25+ nationalities frequently suffer systemic rejections on two technical fronts: **Branch Country Flagging** and **RTS 22 Annex II Natural-Person National Identifiers** (where Spanish DNI/NIF, Italian Codice Fiscale, Polish PESEL, Estonian personal codes, and German CONCAT strings follow totally different priority hierarchies!).

| RTS 22 Field # | XML Field Name | Exact Rule for Cross-Border / Art. 35 Branch Trades | Top ESMA Validation Rejection Error |
| :--- | :--- | :--- | :--- |
| **Field 7 / 16** | Buyer / Seller ID (LEI vs NatID / CONCAT) | Legal entities: 20-char [GLEIF LEI](/passports/gleif-lei-standard); Natural persons: strictly follow nationality's 1st/2nd/3rd priority in RTS 22 Annex II | Using CONCAT (CC + YYYYMMDD + First5 + Last5) for an Italian or Spanish citizen whose 1st priority is Codice Fiscale / NIF! |
| **Field 16 / 25** | Country of Branch for the Buyer / Seller | Populate ISO code of branch whose client membership agreement governs the relationship | Leaving blank or entering client residence ISO instead of branch establishment ISO |
| **Field 37** | Country of Branch Membership | ISO country code of the branch that received the order from the client or made the client investment decision |Mismatching remote [Article 34](/bulletins/mifid-ii-article-34-freedom-provide-services-notification-sla) orders (must use Home country ISO, never client country!) |
| **Field 46 / 58** | Country of Branch Supervising Trader / Decision Maker | ISO country where the trader/algorithm (Field 59) is organizationally supervised—even if travelling temporarily | Omitting country tag when a Paris branch trader executes on head-office Xetra membership |

## Modeling Back-Reporting Remediation Cost Under MiFIR Article 26 Audits

When an NCA data-quality audit (such as BaFin's § 9 WpHG / Art. 26 special inspection or CySEC's TRS data sweep) discovers a systematic CONCAT or Branch-Country bug spanning 24 months of cross-border CFD or equity flow at firms like [CAPEX.com](/firms/capex) or [B2Prime](/firms/b2prime), the firm cannot simply patch forward; it must cancel (CANC) and replay (NEWT) every defective historical XML record.

```formula
Total_MiFIR_Back_Reporting_Remediation_Cost (C_remed_EUR) =
 (N_months_affected * V_monthly_tx * R_error_pct) * Fee_arm_cancel_newt
 + C_forensic_etl_engineering
 + Fine_NCA_data_quality

Where:
 N_months_affected = Historical months containing systematic RTS 22 Annex II / Field 37 error
 V_monthly_tx = Monthly reportable executions across C1-C11 instruments & OTC derivatives
 R_error_pct = Share of cross-border records failing Annex II NatID or branch-flag audit
 Fee_arm_cancel_newt = ARM per-record surcharge for historical CANC + NEWT pair (EUR)
 C_forensic_etl_engineering = External RegTech reconciliation & XML replay engineering cost (EUR)
 Fine_NCA_data_quality = Administrative penalty under MiFID II Art. 70 for Art. 26 reporting failures (EUR)

Worked 24-Month Cross-Border Natural-Person Identifier Replay Audit:
 N_months_affected = 24, V_monthly_tx = 450,000 trades, R_error_pct = 0.22 (2,376,000 bad records)
 Fee_arm_cancel_newt = EUR 0.045 / pair (EUR 106,920 ARM replay bill)
 C_forensic_etl_engineering = EUR 165,000, Fine_NCA_data_quality = EUR 280,000
 C_remed_EUR = 106,920 + 165,000 + 280,000 = EUR 551,920 total back-reporting & sanction cost
```

![RTS 22 Annex II natural-person identifier error rates and MiFIR Article 26 T+1 ARM replay cost drivers](/api/figure?type=bars&title=MiFIR%20Article%2026%20Data-Quality%20Error%20Vectors&subtitle=Primary%20XML%20rejection%20and%20NCA%20sanction%20triggers%20across%20cross-border%20EEA%20brokerages&steps=CONCAT%20Misuse%3A%3ASubmitting%20CONCAT%20where%20IT%2FES%2FPL%20tax%20ID%20is%20Priority%201%7CDual%20Nationality%3A%3AFailing%20ISO%20alphabetical%20sort%20rule%20under%20RTS%2022%20Art.%206%282%29%7CLapsed%20Client%20LEI%3A%3AAccepting%20corporate%20orders%20without%20No-LEI-No-Trade%20lock%7CArt.%2034%20Branch%20Tag%3A%3AFalsely%20populating%20client%20residence%20as%20a%20branch%20ISO&metrics=DUAL%20CITIZEN%20RULE%3A%3AAlpha%20ISO-2%3A%3ASort%20country%20codes%20A-Z%20%28DE%20%3C%20FR%29%7CRTO%20EXEMPTION%3A%3ARTS%2022%20Art.%204%3A%3AValid%20transmission%20agreement%20only%7CRECORD%20ARCHIVE%3A%3A5%20Years%3A%3AMiFIR%20Art.%2025%281%29%20minimum%20retention%7CMIFIR%20REVIEW%20SYNC%3A%3AOTC%20Scope%3A%3ARefined%20DSTI%2FUPI%20derivative%20IDs)

## Daily ARM Rejection Reconciliation and NCA Completeness Sampling

High-reliability cross-border brokers run automated T+1 reconciliation scripts comparing internal OMS execution ledgers against Approved Reporting Mechanism (ARM) ACK/NACK receipts and quarterly NCA feedback extracts—preventing silent systematic field omissions across foreign branch orders from compounding into multi-year enforcement fines.

## Dual-Nationality Sorting (RTS 22 Article 6(2)) and Article 4 RTO Transmission Safe Harbour

Two technical lifesavers protect cross-border operations: first, if a retail client holds **dual EEA nationality** (e.g., French FR and German DE), RTS 22 Article 6(2) dictates sorting the two ISO alpha-2 country codes **alphabetically** (DE precedes FR) and applying the first country's Annex II identifier (DE -> CONCAT)! Second, smaller EUR 75,000 [Article 34 RTO brokers](/bulletins/mifid-ii-article-34-freedom-provide-services-notification-sla) can avoid building an ARM pipeline only if they execute a formal **RTS 22 Article 4 written transmission agreement** shifting T+1 reporting onto their executing EEA broker—and periodically audit that executing broker's submissions alongside [remote MTF venue rules](/bulletins/mtf-otf-remote-member-access-passporting-mifid-article-34-6).

## Frequently asked questions

### Should a Milan Article 35 branch of a German investment firm send its MiFIR Article 26 transaction reports to CONSOB or BaFin?

Exclusively to BaFin (its Home NCA) via the firm’s Approved Reporting Mechanism (ARM). Under RTS 22 Article 14(1), the single home-NCA report populates "IT" in the relevant branch-country fields (16, 37, 46, or 58), and BaFin automatically forwards the record to CONSOB via ESMA TREM.

### What identifier do you report in Field 7 for an Italian retail client onboarded remotely under Article 34?

Under RTS 22 Annex II, Italy’s Priority 1 natural-person identifier is the Italian tax code (Codice Fiscale). Submitting a CONCAT string for an Italian citizen violates Annex II priority rules and triggers NCA data-quality remediation.

### What is the "No LEI, No Trade" rule under MiFIR Article 26 and RTS 22 Article 13?

RTS 22 Article 13(2) requires an investment firm to obtain a valid 20-character ISO 17442 Legal Entity Identifier from any corporate, trust, or foundation client BEFORE providing a service that triggers transaction reporting—blocking trade execution if no LEI is supplied.

### If a remote Article 34 firm serves clients living in France without a French branch, what goes in Field 37 (Country of Branch)?

If no Article 35 branch is involved, the firm populates its own Home Member State ISO country code—never the remote client’s country of residence—because remote cross-border services are legally executed from the head office.


## Source URLs

- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014R0600
- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32017R0590
- https://www.esma.europa.eu/sites/default/files/library/2016-1452_guidelines_mifid_ii_transaction_reporting.pdf

## Citation

- APA: Lukas Lindqvist, CEFA. (2026). MiFIR Article 26 & RTS 22: T+1 ARM Transaction Reporting for EEA Branches. Euro Firm Ledger. https://eurofirmledger.com/bulletins/mifir-article-26-arm-passport-branch-transaction-reporting-t1
- Canonical article: [MiFIR Article 26 & RTS 22: T+1 ARM Transaction Reporting for EEA Branches](https://eurofirmledger.com/bulletins/mifir-article-26-arm-passport-branch-transaction-reporting-t1)
- Site research index: [Euro Firm Ledger](https://eurofirmledger.com/llms-full.txt)