DAC8 and Stablecoins

The single most consequential scope decision in DAC8 is the one most people miss: e-money-token stablecoins are in scope. The OECD's CARF carves out specified e-money products and CBDCs. DAC8 pulls them back in to match the MiCA regulatory perimeter. For any business running on regulated stablecoins through an EU-facing CASP, this is the difference between "outside tax-authority visibility" and "fully reported."

This article explains the divergence, why it exists, and what it means operationally.

TL;DR

• EMT stablecoins are in DAC8 scope from 1 January 2026 — a deliberate alignment with the MiCA-regulated perimeter.
• CARF carves out specified e-money products and CBDCs. DAC8 does not. This is a primary DAC8/CARF divergence.
• A CASP serving EU-tax-resident users reports regulated stablecoin activity under DAC8.
• Tokenized money-market funds (BUIDL, BENJI) are generally not in DAC8 scope — they are MiFID II financial instruments, reported under CRS/DAC2 instead.
• For a stablecoin treasury, the activity is reported via the CASP — reconcile books to what the CASP will report.

The scope divergence in one table

The two divergence points that matter for a stablecoin business: EMTs are DAC8-reportable even where CARF would exclude them, and tokenized funds are not DAC8 stablecoins (they are securities).

Why the EU did this

CARF, the OECD model, deliberately keeps its scope narrow: it excludes CBDCs and specified e-money products so the framework focuses on the crypto-asset core.

The EU made a different policy choice. MiCA explicitly regulates e-money tokens (Title IV) and asset-referenced tokens (Title III) — they are inside the EU's regulated perimeter. The EU view is that tax reporting should match that perimeter. So DAC8 brings EMTs and ARTs back into the reportable scope.

The consequence is structural, not incidental: a global CASP running a regulated stablecoin rail has to report that activity under DAC8 for its EU-resident users, even if the same instrument is carved out of CARF reporting in a non-EU jurisdiction it also serves. One instrument, two different reporting answers depending on the framework — see DAC8 vs CARF.

What it means operationally

For stablecoin issuers and CASPs

A CASP that lists or processes regulated stablecoins must treat that activity as reportable. The data pipeline has to tag stablecoin transactions at the issuer + chain level — because the EMT-scope determination depends on what the instrument actually is (a MiCA-regulated EMT vs something else), not just its ticker.

For payment processors

DAC8 includes a €50,000 reference point for certain retail-payment transactions where a CASP acts as a payment processor. CARF leaves that threshold to adopting jurisdictions. A stablecoin invoice-payment rail is exactly the use case this targets — confirm the threshold treatment in each Member State you serve (see DAC8 data collected).

For treasuries

If a treasury holds and moves regulated stablecoins through a CASP that serves it as an EU-tax-resident entity, those flows are inside the CASP's DAC8 report. The treasury is not the reporting entity, but its activity becomes visible to tax authorities. The practical action: reconcile the treasury's own books to what the CASP will report, so there is no divergence to explain later. For the stablecoin selection angle, see USDC vs USDT vs DAI for treasury.

The tokenized-fund boundary

A frequent confusion: if EMT stablecoins are in scope, are tokenized money-market funds (BUIDL, BENJI, OUSG) also in scope?

Generally no. Those are financial instruments under MiFID II, which MiCA carves out, and DAC8 scope follows the MiCA crypto-asset definition. Tokenized funds fall under existing securities-reporting frameworks (CRS/DAC2 at the account level) rather than DAC8. The line is: regulated stablecoins (EMTs) are DAC8; tokenized funds are securities reporting (see tokenized RWA for treasury).

Getting this boundary wrong in either direction is a data-integrity exposure — reporting a tokenized fund as a DAC8 crypto-asset, or failing to report an EMT because it was treated as "just cash."

How Wag3s helps

Wag3s Ledger handles the issuer-and-chain-level tagging that the EMT scope decision depends on:

• Per-issuer stablecoin tagging (USDC, USDT, EURC, DAI) at the contract + chain level
• Classification of regulated EMT/ART activity vs tokenized-security activity (the DAC8 vs CRS/DAC2 boundary)
• Multi-chain reconciliation so cross-chain stablecoin movement is captured as one economic flow (see multi-chain reconciliation)
• Treasury-side reconciliation against expected CASP-reported activity

See the Wag3s Ledger product page for module details.

Further reading

• DAC8 Compliance Guide 2026
• DAC8 vs CARF Difference — the framework comparison this divergence sits inside
• DAC8 vs MiCA
• DAC8 Data Collected
• MiCA ART vs EMT Stablecoins
• USDC vs USDT vs DAI for Treasury
• Tokenized RWA for Treasury

Sources

• Council Directive (EU) 2023/2226 (DAC8) — EUR-Lex
• Regulation (EU) 2023/1114 (MiCA) — EUR-Lex
• OECD Crypto-Asset Reporting Framework — model rules and commentary
• EBA — Asset-referenced and e-money tokens (MiCA)