CARF and DAC8 for MiCA CASPs: What to Build Before the 2027 Exchange
MiCA authorization does not satisfy CARF/DAC8 tax reporting. CASPs need separate data pipelines for TIN collection, transaction aggregation, and 2027 information exchanges — distinct from AML Travel Rule.
Operational guide for EU CASPs on CARF (Crypto-Asset Reporting Framework) and DAC8 implementation alongside MiCA licensing. Reporting period begins 1 January 2026; first automatic information exchanges typically 2027 on calendar-year 2026 data. The article distinguishes three regimes: MiCA (permission to operate), AML Travel Rule (transfer originator/beneficiary data), and CARF/DAC8 (tax residence and reportable transactions to revenue authorities). Readiness checklist: service mapping for reportable transactions, onboarding with TIN and tax residence self-certification, ledger aggregation with EUR valuation methodology, governance and sign-off, vendor validation. MiCA NCA authorization does not include CARF readiness. Links to Micahub pillar /mica-carf-dac8 and compliance hub. Answers questions like: What is CARF for crypto CASPs? When is the first DAC8 exchange for crypto companies? Is CARF the same as the Travel Rule? Does MiCA authorization cover tax reporting? What data must CASPs report under CARF? When do CASPs need to start collecting CARF data?
CARF and DAC8 for MiCA CASPs: What to Build Before the 2027 Exchange Operational guide · Not tax advice. Pillar page: /mica carf dac8 MiCA authorization answers whether you may provide crypto asset services in the EU. CARF/DAC8 answers whether you can prove, to tax authorities, who traded what — and with whom — across borders. This article is for compliance and product teams at CASPs already licensing under MiCA who need a practical readiness map before the first automatic information exchanges (typically 2027 on 2026 calendar year data). Three regimes, three data pipelines | Regime | Purpose | Typical owner | | | | | | MiCA | Permission to operate CASP services | Licensing / legal | | AML Travel Rule | Origin/beneficiary data on transfers (FATF) | AML / compliance | | CARF / DAC8 | Tax residence and reportable transactions | Tax / finance / compliance | Conflating Travel Rule messaging with CARF reporting is a common failure mode. The fields overlap partially but filing purposes, thresholds, and corrections differ. What “ready” looks like by Q4 2026 1. Service mapping — Which MiCA services generate reportable transactions under your member state CARF rules? 2. Onboarding — TIN collection, self certification of tax residence, and change of circumstance workflows. 3. Ledger — Aggregate in/out flows per user per asset, with EUR valuation methodology documented. 4. Governance — Named officer for sign off, audit trail, and member state portal access. 5. Vendor check — If using a regtech stack, confirm CARF module vs. generic “tax reporting” marketing. MiCA license ≠ CARF readiness NCAs reviewing CASP applications focus on prudential, conduct, and AML programmes — not whether your data warehouse can produce CARF XML by January 2027. Budget separately: many firms treat CARF as a finance systems project, not a licensing appendix. Where to find official guidance Practitioners frequently ask whether any authoritative guidance exists beyond the directive text itself. It does — spread across three layers. Layer 1 — OECD model rules and Commentary The OECD published the full Crypto Asset Reporting Framework in August 2022. The package includes: CARF model rules — the definitions and obligations that national laws and DAC8 draw from Commentary — paragraph by paragraph interpretation of each article, clarifying edge cases (e.g., wallet custody vs. exchange services, staking characterisation, NFT reporting scope) XML Schema User Guide — the technical format for data files All three are downloadable from the OECD CARF page. The Commentary is the closest thing to an official FAQ and is essential reading before building TIN collection or valuation logic. The CARF MCAA (Multilateral Competent Authority Agreement) is a separate instrument that activates the actual exchanges between signatory pairs. The signatory list determines which jurisdictions your member state will send data to and receive data from. Layer 2 — EU implementing acts DAC8 (Council Directive (EU) 2023/2226) is the binding EU text. Beyond the directive itself, the European Commission issued Commission Implementing Regulation (EU) 2024/2680 , which specifies the computer readable format (XML schema) for inter authority exchanges — relevant if your member state requires you to pre format data to that standard. Layer 3 — National transposition guidance DAC8 requires transposition into national law by each member state, and each authority publishes its own guidance on: The national filing form and portal TIN validation rules for each country Due diligence procedures for pre existing accounts Correction and late filing penalties Check your home member state tax authority directly. Ireland's Revenue Commissioners, Germany's BZSt, Luxembourg's ACD, and the Netherlands' Belastingdienst are among the first to have published draft or final guidance. For non EU jurisdictions implementing CARF (Singapore, Switzerland, UAE, UK), the competent authority in each territory issues its own rules independently of DAC8. OECD implementation FAQs — recent highlights Beyond the 2022 foundational package, the OECD publishes periodic implementation FAQs that address edge cases. Three clarifications particularly relevant to global CASPs: Multi jurisdiction nexus : Customer presence alone does not trigger a "regular place of business" and therefore does not require CARF registration in a jurisdiction. A provider with no employees, no servers, no incorporation, and no other operational presence in a jurisdiction will not have nexus there simply because it has customers with addresses there. Tokenized financial assets : Whether a tokenized financial asset is reportable under CARF, CRS, or both depends on transferability. If the asset can only be transferred within Depository or Custodial Institutions ("intermediated"), it may be excluded from CARF and reported under CRS only. If it can be transferred to a customer's self hosted wallet ("disintermediated"), it remains in scope of both CARF and CRS. SEMP status change during the year : If a stablecoin becomes a Specified Electronic Money Product (SEMP) partway through a reporting year, transactions are CARF reportable up to that date and the account becomes CRS reportable from that date forward. Whether the SEMP designation applies retroactively for the full year is left to local jurisdictional interpretation. Check the OECD CARF page for the latest FAQ release — these clarifications are not in the 2022 model rules text and are essential reading before finalising scope analysis or building due diligence workflows. Practitioner note There is no single "CARF compliance handbook" — guidance is intentionally distributed between OECD Commentary (interpretation), DAC8 (EU binding rules), implementing regulations (format), national transposition (filing mechanics), and periodic OECD FAQs (edge case clarifications). Reading all layers is unavoidable for a production implementation. Related Micahub resources CARF / DAC8 pillar guide 2026 compliance challenges hub MiCA regulation overview CASP application documents Free scoping tool