MiFIR Article 26 & RTS 22: T+1 ARM Transaction Reporting for EEA Branches

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 and the EEA passporting hub, 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, AFM, and 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 or 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.

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!).

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 or B2Prime, the firm cannot simply patch forward; it must cancel (CANC) and replay (NEWT) every defective historical XML record.

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