DAC8 Reporting and Global Crypto Accounting Standards: What Firms Need to Know

Crypto financial reporting has moved from a niche curiosity to a board-level compliance obligation. DAC8 reporting is now live across EU member states, CARF crypto reporting is being adopted by OECD jurisdictions at pace, and the FASB has fundamentally changed how US entities measure digital assets under ASC 350-60. At the same time, IFRS-reporting entities globally are waiting on long-overdue authoritative guidance, navigating patchwork interpretations in the interim. For accounting firms, auditors, and CFOs, the combined effect is a reporting environment that is simultaneously more structured and more demanding than it has ever been. Understanding where each framework applies, how they interact, and what they require in practice is no longer optional. It is the baseline.

Why Crypto Financial Reporting Has Become a Compliance Priority

For most of the past decade, crypto assets sat in an awkward gap between existing accounting categories. They were not cash, not financial instruments under most interpretations, and not inventory in the conventional sense. Firms and their clients improvised, applying nearest-fit treatments and hoping auditors would accept the rationale. That era is closing.

Regulators have caught up. Tax authorities across the OECD are implementing automatic exchange of information specifically for crypto. The EU has enacted DAC8, the US has deployed Form 1099-DA requirements, and the global CARF framework is being transposed into domestic law across dozens of jurisdictions. On the accounting standards side, the FASB issued ASC 350-60 to require fair value measurement for certain crypto assets, a significant departure from the previous indefinite-lived intangible model. IFRS-reporting entities remain in a more ambiguous position, but IFRS Interpretations Committee agenda decisions and IAS 38 interpretations have at least created a working consensus in many markets.

The cumulative result is that firms advising clients who hold, trade, or issue crypto assets must now maintain competence across at least three distinct reporting regimes: tax information exchange, financial statement accounting, and disclosure. Each has its own definitions, timelines, and compliance mechanics.

DAC8 Reporting: Scope, Obligations, and Key Deadlines

DAC8 is the eighth amendment to the EU Directive on Administrative Cooperation. It extends the EU's automatic tax information exchange infrastructure to crypto-asset service providers, or CASPs, operating within the EU. The directive draws heavily on the OECD's Crypto-Asset Reporting Framework, meaning the two regimes share a common conceptual architecture even where their precise legal mechanics differ.

Under DAC8 reporting, CASPs are required to collect, verify, and report information about their EU-resident users to the relevant national tax authority. That authority then exchanges the data with the tax authority in the user's country of residence. The types of assets covered are broad, encompassing cryptocurrencies, stablecoins, certain e-money tokens, and some categories of non-fungible token depending on their characteristics. CASPs outside the EU that serve EU-resident users may also fall within scope if they do not already report equivalent information under a recognised third-country regime.

The following table summarises the key parameters of DAC8 as enacted.

For accounting firms advising CASPs or institutional clients who use them, the practical implication is that transaction-level data must be captured, categorised, and reportable by counterparty. Firms that support clients in building that infrastructure now have a clear advisory opportunity.

CARF Crypto Reporting: The OECD Framework Underpinning DAC8

The Crypto-Asset Reporting Framework, or CARF, was developed by the OECD and approved in 2022. It serves as the international standard on which DAC8 and many domestic regimes are modelled. CARF crypto reporting covers a similar asset perimeter to DAC8, focusing on crypto assets that can be held and transferred in a decentralised manner, and it requires reporting intermediaries to collect user due diligence information and report transaction data to tax authorities.

The key distinction between CARF and DAC8 is jurisdictional reach. DAC8 is an EU instrument enforceable within member states. CARF is an OECD framework that individual countries adopt and transpose into their own domestic legislation. Several major economies, including the UK, Canada, Australia, and Japan, have committed to implementing CARF-based reporting. The US has taken a parallel but distinct path through its own broker reporting rules under the Infrastructure Investment and Jobs Act.

For firms with clients operating across multiple jurisdictions, the interaction between CARF and DAC8 is important. The two frameworks include coordination provisions designed to avoid double reporting, but those provisions depend on a jurisdiction being recognised as having an equivalent regime. Firms should not assume equivalence without verifying the specific bilateral arrangements in place. Robust crypto compliance reporting infrastructure is the foundation for managing this complexity at scale.

FASB ASC 350-60 and Crypto US GAAP Accounting

The FASB's update to ASC 350-60 represents the most significant change to crypto accounting under US GAAP in years. Before the update, entities holding crypto assets typically treated them as indefinite-lived intangible assets, recognising impairment losses when fair value fell below carrying value but never writing values back up when prices recovered. The result was financial statements that could significantly understate the economic value of crypto holdings in rising markets.

ASC 350-60 now requires entities to measure qualifying crypto assets at fair value each reporting period, with changes recognised in net income. The scope covers assets that meet specific criteria: they must be intangible assets, secured through cryptography, reside on a distributed ledger, and not be produced or created by the reporting entity. Importantly, the standard does not apply to wrapped tokens, NFTs, or stablecoins unless they independently meet the definitional criteria.

For US-based accounting firms and CFOs at entities holding crypto, the shift to FASB crypto fair value accounting increases both the accuracy of financial statements and the operational burden of maintaining real-time or period-end pricing data. Audit trails linking exchange prices to ledger entries become critical.

IFRS Crypto Assets: The Current Consensus and Its Limits

IFRS does not yet have a dedicated standard for crypto assets. The IASB added a crypto-assets project to its agenda, but authoritative guidance remains pending. In the interim, IFRS-reporting entities rely on the IFRS Interpretations Committee's June 2019 agenda decision, which concluded that holdings of cryptocurrency generally fall within the scope of IAS 38 as intangible assets, unless they are held for sale in the ordinary course of business, in which case IAS 2 inventories may apply.

Crypto IFRS accounting under IAS 38 defaults to the cost model unless an entity elects the revaluation model. The revaluation model under IAS 38 is only available when an active market exists, and even then, gains are typically recognised in other comprehensive income rather than profit or loss, reversing impairment losses only to the extent of prior write-downs. This creates a structural asymmetry compared to the US GAAP approach under ASC 350-60.

The practical consequence for firms auditing IFRS clients is that significant judgement remains embedded in crypto asset classification and measurement. Detailed documentation of the rationale for each treatment, supported by contemporaneous evidence of market conditions and asset characteristics, is not optional. It is what stands up to scrutiny.

How the Frameworks Interact for Multinational Clients

A client with operations in both the EU and the US, holding crypto assets on their balance sheet and using a CASP to manage custody, faces obligations across all of the frameworks discussed above simultaneously. Their CASP must report under DAC8. Their financial statements may need to comply with both US GAAP and IFRS depending on their reporting structure. Their tax positions in each jurisdiction will be shaped by how CARF-based rules are implemented locally.

The definitions of crypto assets are not identical across these frameworks. An asset that qualifies for fair value treatment under ASC 350-60 may not fall within DAC8's reporting perimeter and vice versa. Stablecoins, for instance, are generally excluded from the FASB's fair value scope but are included in DAC8 and CARF. Firms must map each asset type held by a client against the applicable framework definitions, not assume uniform treatment.

This mapping exercise is where specialised tooling pays for itself. Maintaining separate worksheets per framework per client is not scalable at the firm level. The case for integrated crypto compliance reporting infrastructure becomes compelling the moment a firm has more than a handful of clients with material crypto exposure.

Illustrative Scenario

To illustrate how this applies in practice, consider the following scenario: Marcus is the Finance Director at a mid-sized asset management firm based in Frankfurt. The firm holds a portfolio of crypto assets on behalf of its own treasury and reports under IFRS. It also uses a licensed CASP for custody, meaning the CASP has DAC8 reporting obligations covering the firm's transactions.

As the year-end audit approaches, Marcus faces three simultaneous demands. The auditors want documentation of the IAS 38 treatment applied to each crypto asset class, including evidence that the revaluation model has been consistently applied where elected. The group's US subsidiary requires a reconciliation of the same holdings under ASC 350-60 for its US GAAP reporting. And the compliance team needs assurance that the CASP's DAC8 reporting aligns with the firm's own internal transaction records, with no gaps or mismatches that could trigger a query from the Bundeszentralamt für Steuern.

Using CryptaCount, Marcus runs a single reconciliation that maps each asset across all three reporting contexts, generating the documentation the auditors need and flagging any DAC8 reporting discrepancies before they become a problem. What would have taken weeks of manual spreadsheet work is completed in a single workflow.

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 transaction and user information to national tax authorities, who then exchange that data automatically with other member states. It applies to CASPs licensed under MiCA and, in certain circumstances, to non-EU CASPs serving EU-resident users. The first reporting period covers calendar year 2026.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD framework on which DAC8 is modelled, but it operates at the international level rather than within the EU specifically. Individual countries adopt and transpose CARF into their own domestic law. DAC8 is EU-specific and legally binding on member states. The two include coordination provisions to prevent double reporting where a jurisdiction is recognised as having an equivalent regime.

What does ASC 350-60 require for crypto US GAAP accounting?

ASC 350-60 requires entities to measure qualifying crypto assets at fair value each reporting period, with changes recognised in net income. It replaces the previous cost-less-impairment model that prevented upward revaluations. The standard covers assets that are intangible, cryptographically secured, and held on a distributed ledger, but excludes stablecoins, wrapped tokens, and NFTs unless they independently meet the criteria.

What is the FASB crypto fair value approach and why does it matter?

The FASB's shift to fair value measurement under ASC 350-60 means that balance sheets of US GAAP entities now reflect current market values for in-scope crypto assets rather than historical cost reduced by impairment. This improves the economic accuracy of financial statements but increases the operational need for reliable, auditable pricing data at each reporting date.

How are crypto assets treated under IFRS?

In the absence of a dedicated IFRS standard, most crypto asset holdings are classified as intangible assets under IAS 38, or as inventory under IAS 2 if held for sale in the ordinary course of business. Under IAS 38, entities can apply either the cost model or the revaluation model where an active market exists. Crypto IFRS accounting involves significant judgement, and detailed documentation of each treatment decision is essential for audit purposes.

Are the asset definitions consistent across DAC8, CARF, and FASB standards?

No. The definitions diverge in meaningful ways. Stablecoins, for example, are generally within scope for DAC8 and CARF but fall outside the FASB's ASC 350-60 fair value requirement unless they independently meet the definitional criteria. Firms must map each asset type against the relevant framework definition rather than assuming uniform treatment across all reporting obligations.

When do DAC8 reporting obligations first take effect?

EU member states were required to transpose DAC8 into national law by 31 December 2025. The first reporting period is calendar year 2026, with reports due to national tax authorities in 2027. CASPs and their advisers should use the current period to build the data infrastructure needed to meet those obligations without last-minute pressure.

What should accounting firms do now to prepare clients for these frameworks?

Firms should begin by mapping each crypto-holding client against the frameworks that apply to them, covering DAC8 and CARF for EU-connected clients, ASC 350-60 for US GAAP reporters, and IAS 38 or IAS 2 for IFRS reporters. Each mapping exercise should produce a documented treatment rationale and identify any data gaps. Firms with multiple such clients benefit from centralised crypto compliance reporting infrastructure rather than client-by-client manual processes.

Does IFRS have a dedicated standard for crypto assets?

Not yet. The IASB has a crypto-assets project on its agenda, but no finalised standard has been issued. IFRS entities currently rely on the IFRS Interpretations Committee's 2019 agenda decision, which pointed to IAS 38 as the primary applicable standard for most crypto holdings. Firms should monitor IASB developments, as a dedicated standard would likely change measurement and disclosure requirements materially.

How does Brazil's approach to crypto financial reporting fit into the global picture?

Brazil has been an active jurisdiction in developing domestic crypto regulation and tax reporting rules, generally following OECD-aligned principles. Brazilian entities reporting under IFRS apply the same IAS 38 framework as other IFRS jurisdictions. For DAC8 and CARF specifically, Brazil's implementation timeline and bilateral exchange agreements will determine when and how automatic information exchange becomes active with EU and OECD partner jurisdictions.

Source: CryptaCount