CryptaCount
🌐 EN
EnglishENDeutschDEEspañolESFrançaisFRItalianoIT日本語JA한국어KONederlandsNLPolskiPLPortuguêsPT
Log in Start Free

DAC8 Reporting and Crypto Financial Reporting Standards: A Guide for Finance Teams

DAC8 Reporting and Crypto Financial Reporting Standards: A Guide for Finance Teams

Crypto assets now sit inside balance sheets, client portfolios, and corporate treasuries across Europe and beyond, and the accounting rules governing them are no longer a niche concern. DAC8 reporting has shifted the compliance burden firmly onto crypto-asset service providers and the accountants who advise them, while parallel updates to IFRS, US GAAP, and national frameworks like France's Plan Comptable Général have created a layered set of obligations that cannot be treated in isolation. For finance teams, accounting firms, and CFOs managing digital assets, understanding how these frameworks interact is no longer optional. It is a core professional responsibility. This article maps the key standards, explains how they differ, and shows where DAC8 reporting obligations connect with the broader accounting picture.

What DAC8 Reporting Requires and Why It Matters

DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation. It extends automatic exchange of financial information to cover crypto assets, bringing them within the same reporting infrastructure that already governs bank accounts and financial instruments under earlier DAC iterations. From a compliance standpoint, the directive targets crypto-asset service providers (CASPs) authorised under MiCA, as well as operators that are resident in an EU member state or facilitate transactions involving EU-resident users. These entities must collect, verify, and report data on their users' crypto transactions to the relevant national tax authority, which then shares that data automatically with other member states.

The information captured under DAC8 includes aggregate proceeds from disposals, transfers, and exchanges, as well as fair market values where applicable. Tax authorities across the EU will receive this data and cross-reference it against individual and corporate tax returns. For accounting firms advising clients who hold or trade crypto, this creates a new advisory angle: clients may receive information notices from their tax authority based on DAC8 data, and they will need professional help reconciling those figures with their own records. Firms that are not prepared to handle that conversation risk losing client trust at a critical moment. Good crypto compliance reporting infrastructure is the foundation for managing that risk.

The following table summarises the core DAC8 obligations relevant to finance teams and their clients.

Obligation Who It Applies To Key Data Points Reported Direction of Data Flow
User transaction reporting CASPs resident or operating in the EU Disposal proceeds, asset type, user identity CASP to national tax authority
Automatic exchange EU member state tax authorities Aggregated user data per jurisdiction National authority to other member states
User notification CASPs Summary of data reported about the user CASP to individual user

CARF Crypto Reporting: The Global Dimension

DAC8 did not emerge in isolation. It was designed in close alignment with the OECD's Crypto-Asset Reporting Framework, known as CARF. The OECD published CARF to provide a global standard for the automatic exchange of crypto tax information between jurisdictions, mirroring what the Common Reporting Standard already does for traditional financial accounts. DAC8 essentially incorporates CARF logic into EU law, meaning that jurisdictions outside the EU that adopt CARF will be exchanging compatible data with EU member states.

For firms with clients who operate internationally, whether holding assets on non-EU exchanges or running treasury operations across multiple countries, CARF crypto reporting creates a genuinely global compliance footprint. A UK-based investor using a US-licensed exchange and holding assets staked through a protocol with European users could, in principle, generate reportable data under multiple CARF-aligned regimes simultaneously. The practical implication is that firms cannot view DAC8 as a purely domestic EU matter. It is the EU's implementation of a global shift toward full crypto transaction transparency, and firms with international client bases need to think about it in that context.

France has committed to implementing both DAC8 and CARF, and the French tax authority, the Direction Générale des Finances Publiques, is expected to begin receiving DAC8 data from French-registered CASPs in line with the EU transposition timeline. This makes France a relevant jurisdiction both for domestic accounting firms and for European groups with French subsidiaries or French-resident shareholders.

IFRS Crypto Assets: The Accounting Standards Backdrop

While DAC8 governs what gets reported to tax authorities, IFRS crypto assets rules govern how those same assets appear on the balance sheet. The International Accounting Standards Board has not issued a dedicated standard for crypto assets, but it published narrow-scope amendments to IAS 38, the intangible assets standard, in 2019, and issued further guidance through the IFRS Interpretations Committee. Under this guidance, most crypto assets that do not meet the definition of a financial instrument are classified as intangible assets and measured at cost or, if the entity elects, at revaluation under IAS 38's revaluation model.

The revaluation model under IAS 38 requires an active market for the asset. For major cryptocurrencies like Bitcoin and Ether, that condition is generally considered met. Gains from revaluation go to other comprehensive income rather than profit or loss, which is a significant difference from the approach now required under US GAAP. For IFRS preparers, this means crypto holdings can appreciate on the balance sheet without generating a profit or loss entry, but impairment losses must still be recognised when the carrying amount exceeds recoverable amount. The asymmetric treatment of gains and losses under IAS 38 has long been criticised as failing to reflect the economic reality of holding volatile digital assets, and the IASB is continuing to consider whether a more tailored standard is needed.

Crypto ifrs accounting also raises consolidation questions. Where a group holds crypto through a special purpose vehicle or a decentralised protocol, determining whether that entity falls within the consolidation scope under IFRS 10 requires careful analysis of the control criteria. These are not theoretical issues; they arise regularly in audit engagements involving crypto-native businesses.

FASB Crypto Fair Value and ASC 350-60

US entities preparing financial statements under US GAAP now follow ASC 350-60, the FASB standard for crypto assets that took effect for fiscal years beginning after December 2024. The FASB's approach marks a decisive break from the previous indefinite-lived intangible asset model. Under ASC 350-60, qualifying crypto assets must be measured at fair value at each reporting date, with changes in fair value recognised directly in net income. This is what the market means when it refers to FASB crypto fair value treatment.

The scope of asc 350-60 crypto is deliberately narrow. It applies to fungible intangible assets that are secured through cryptography, exist on a distributed ledger, and are not produced or held by the reporting entity. Stablecoins, NFTs, and wrapped tokens generally fall outside the scope, as do crypto assets held by investment companies already measuring at fair value under other GAAP guidance. For corporate treasuries holding Bitcoin, however, ASC 350-60 is directly applicable and the fair value requirement is not optional.

The contrast with IFRS is significant. Under crypto US GAAP accounting, every fair value movement goes through the income statement. Under IFRS, revaluation gains bypass profit or loss entirely unless the asset is subsequently derecognised. This creates a situation where two companies holding identical assets can report very different earnings, purely because of the accounting framework they apply. For multinational groups preparing both IFRS and US GAAP financials, or for auditors reviewing group accounts that include US subsidiaries, understanding this divergence is essential.

Framework Primary Standard Measurement Basis Gains and Losses Scope Notes
IFRS IAS 38 (amended) Cost or revaluation model Gains to OCI; impairment to P&L Most crypto treated as intangible
US GAAP ASC 350-60 Fair value All movements to net income Fungible, non-produced crypto only
French PCG ANC Regulation 2018-07 Cost with impairment Gains on disposal only; write-downs recognised Applies to digital assets as defined under French law

French Accounting Rules for Crypto Assets

France has its own layer of accounting regulation that sits beneath IFRS for entities not required to use international standards. French generally accepted accounting principles, codified in the Plan Comptable Général and supplemented by regulations from the Autorité des Normes Comptables, treat crypto assets primarily as digital assets under the framework introduced by the PACTE law. For accounting purposes, French entities typically classify crypto holdings similarly to inventories or financial instruments depending on the nature of the holding, though the ANC's guidance has been refined over time to address specific situations such as mining income and token issuances.

The tax treatment in France adds another dimension. Individuals are taxed on crypto gains at a flat rate, but companies holding crypto assets as part of a trading activity or as long-term investments face different rules depending on how those assets are classified on the balance sheet. Finance teams at French companies need to ensure that the accounting classification chosen under French GAAP is consistent with the tax position taken, because misalignment between the two can trigger adjustments on inspection. French-registered CASPs also face the dual obligation of applying French accounting rules to their own books while simultaneously preparing DAC8 reporting data for submission to the tax authority.

Illustrative Scenario

To illustrate how this applies in practice, consider the following scenario:

Antoine is the Finance Director at a mid-sized fintech group headquartered in Paris, with subsidiaries in Germany and the United States. The group holds a treasury allocation in Bitcoin across all three entities. The US subsidiary prepares its standalone financials under ASC 350-60, recognising fair value movements through net income each quarter. The French parent applies French PCG rules, carrying the Bitcoin at cost with write-downs taken when the carrying value exceeds market price. The German subsidiary follows IFRS and has elected the revaluation model under IAS 38.

At consolidation, Antoine's team must reconcile three different carrying values for what is economically the same asset. The group files consolidated IFRS accounts, so the French and US subsidiary figures must be restated on consolidation. Separately, the French parent entity is a registered CASP under MiCA and must submit DAC8 reporting data to the Direction Générale des Finances Publiques covering all transactions conducted through its platform. Antoine's team uses CryptaCount to automate the fair value data feeds, generate the DAC8 reporting file, and maintain the audit trail that external auditors will need across all three jurisdictions. Without a single platform handling the sub-ledger and compliance outputs, the manual reconciliation risk across three frameworks would be substantial.

Frequently Asked Questions

What is DAC8 reporting and who does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers to report user transaction data to national tax authorities, who then exchange it automatically with other member states. It applies to CASPs authorised under MiCA and to operators resident in or facilitating transactions involving EU-based users. The goal is to bring crypto into the same automatic information exchange infrastructure that covers traditional bank accounts.

How does DAC8 relate to CARF crypto reporting?

DAC8 incorporates the OECD's Crypto-Asset Reporting Framework into EU law, meaning the two are structurally aligned. Jurisdictions outside the EU that adopt CARF will exchange compatible data with EU member states. For firms with internationally active clients, both frameworks are relevant and may generate overlapping reporting obligations depending on which exchanges and platforms the client uses.

What accounting standard applies to crypto assets under IFRS?

Most crypto assets are treated as intangible assets under IAS 38, based on guidance from the IFRS Interpretations Committee. Entities can measure at cost or, if an active market exists, under the revaluation model. Revaluation gains go to other comprehensive income rather than profit or loss, and impairment losses must be recognised when the carrying amount exceeds recoverable amount.

What changed under ASC 350-60 for US GAAP preparers?

ASC 350-60 requires qualifying crypto assets to be measured at fair value at each reporting date, with all fair value changes recognised in net income. This replaces the previous indefinite-lived intangible asset model under which impairments were recognised but gains were not. The standard applies to fungible, non-produced crypto assets and took effect for fiscal years beginning after December 2024.

How does FASB crypto fair value treatment differ from IFRS?

Under ASC 350-60, every fair value movement passes through the income statement, making earnings more volatile in periods of significant price movement. Under IFRS using the IAS 38 revaluation model, gains go to other comprehensive income and only reach profit or loss on disposal or impairment. Two companies holding identical crypto assets can therefore report very different earnings figures depending solely on the framework they apply.

How are crypto assets treated under French accounting rules?

French entities follow the Plan Comptable Général as supplemented by ANC guidance, which generally treats crypto assets as digital assets at cost with write-downs when the carrying value exceeds market value. The classification can vary depending on whether the entity is holding crypto as a long-term investment or as part of a trading activity. Consistency between the accounting classification and the tax position taken is important to avoid adjustments on inspection.

Do French companies face both DAC8 and French tax reporting obligations?

Yes. French-registered CASPs must comply with DAC8 reporting to the Direction Générale des Finances Publiques while also applying French GAAP to their own financial statements. These are separate obligations with different data requirements, but they draw on the same underlying transaction records. Firms advising French CASPs need processes that satisfy both sets of requirements from a single source of truth.

What should accounting firms do now to prepare for DAC8 reporting?

Firms should audit which clients are CASPs or have CASP exposure, assess whether those clients have the data collection and verification processes required under DAC8, and build an advisory offering around compliance gap analysis. Investing in crypto compliance reporting infrastructure early means firms can support clients proactively rather than reactively when the first reporting cycles produce discrepancies flagged by tax authorities.

Can a single platform handle DAC8, CARF, and accounting standard requirements?

Purpose-built crypto accounting platforms can consolidate transaction data, apply the correct cost basis and fair value methodologies, and generate DAC8 and CARF-aligned output files from the same underlying sub-ledger. This reduces the risk of inconsistencies between what is reported to tax authorities and what appears in the financial statements, which is a key audit risk for entities subject to multiple frameworks simultaneously.

Source: CryptaCount

FAQ

What is DAC8 reporting and who does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers to report user transaction data to national tax authorities, who then exchange it automatically with other member states. It applies to CASPs authorised under MiCA and to operators resident in or facilitating transactions involving EU-based users. The goal is to bring crypto into the same automatic information exchange infrastructure that covers traditional bank accounts.

How does DAC8 relate to CARF crypto reporting?

DAC8 incorporates the OECD's Crypto-Asset Reporting Framework into EU law, meaning the two are structurally aligned. Jurisdictions outside the EU that adopt CARF will exchange compatible data with EU member states. For firms with internationally active clients, both frameworks are relevant and may generate overlapping reporting obligations depending on which exchanges and platforms the client uses.

What accounting standard applies to crypto assets under IFRS?

Most crypto assets are treated as intangible assets under IAS 38, based on guidance from the IFRS Interpretations Committee. Entities can measure at cost or, if an active market exists, under the revaluation model. Revaluation gains go to other comprehensive income rather than profit or loss, and impairment losses must be recognised when the carrying amount exceeds recoverable amount.

What changed under ASC 350-60 for US GAAP preparers?

ASC 350-60 requires qualifying crypto assets to be measured at fair value at each reporting date, with all fair value changes recognised in net income. This replaces the previous indefinite-lived intangible asset model under which impairments were recognised but gains were not. The standard applies to fungible, non-produced crypto assets and took effect for fiscal years beginning after December 2024.

How does FASB crypto fair value treatment differ from IFRS?

Under ASC 350-60, every fair value movement passes through the income statement, making earnings more volatile in periods of significant price movement. Under IFRS using the IAS 38 revaluation model, gains go to other comprehensive income and only reach profit or loss on disposal or impairment. Two companies holding identical crypto assets can therefore report very different earnings figures depending solely on the framework they apply.

How are crypto assets treated under French accounting rules?

French entities follow the Plan Comptable Général as supplemented by ANC guidance, which generally treats crypto assets as digital assets at cost with write-downs when the carrying value exceeds market value. The classification can vary depending on whether the entity holds crypto as a long-term investment or as part of a trading activity. Consistency between the accounting classification and the tax position taken is important to avoid adjustments on inspection.

Do French companies face both DAC8 and French tax reporting obligations?

Yes. French-registered CASPs must comply with DAC8 reporting to the Direction Générale des Finances Publiques while also applying French GAAP to their own financial statements. These are separate obligations with different data requirements, but they draw on the same underlying transaction records. Firms advising French CASPs need processes that satisfy both sets of requirements from a single source of truth.

What should accounting firms do now to prepare for DAC8 reporting?

Firms should audit which clients are CASPs or have CASP exposure, assess whether those clients have the data collection and verification processes required under DAC8, and build an advisory offering around compliance gap analysis. Investing in crypto compliance reporting infrastructure early means firms can support clients proactively rather than reactively when the first reporting cycles produce discrepancies flagged by tax authorities.

Can a single platform handle DAC8, CARF, and accounting standard requirements?

Purpose-built crypto accounting platforms can consolidate transaction data, apply the correct cost basis and fair value methodologies, and generate DAC8 and CARF-aligned output files from the same underlying sub-ledger. This reduces the risk of inconsistencies between what is reported to tax authorities and what appears in the financial statements, which is a key audit risk for entities subject to multiple frameworks simultaneously.