DAC8 Reporting and Crypto Accounting Standards: What Finance Teams Need to Know
Crypto financial reporting is no longer a niche concern for a handful of blockchain-native startups. Accounting firms, CFOs, and finance teams across the Netherlands and the wider European Union are now navigating a complex web of overlapping obligations. DAC8 reporting brings automatic exchange of crypto-asset data to EU tax authorities. CARF crypto reporting extends similar logic globally under the OECD framework. Meanwhile, FASB has overhauled how US GAAP treats digital assets under ASC 350-60, and the question of how IFRS handles crypto assets remains a live issue for many international groups. Getting this wrong is not just a compliance risk. It is a reputational and audit-readiness risk that affects every client engagement touching digital assets.
What DAC8 Reporting Actually Requires
DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation. It extends automatic exchange of information to crypto-asset service providers operating within the EU. Under the directive, crypto-asset service providers are required to collect and verify user data and report transaction information to the relevant national tax authority. That authority then shares the data with other EU member states where the user is tax-resident.
The Netherlands transposed DAC8 into domestic law, meaning Dutch-registered platforms and firms with reporting obligations must comply with local implementing rules. The scope is broad. It covers exchanges, custodians, and certain brokers dealing in crypto assets as defined by MiCA. Reportable transactions include sales, exchanges between crypto assets, and transfers to or from identified wallet addresses.
For accounting firms advising crypto-asset businesses, the compliance checklist is significant. Clients need robust KYC processes, accurate transaction logs, and the ability to generate compliant reports in the prescribed format. A gap in any one of these areas creates a filing failure, which national tax authorities can penalise.
The following table summarises the key reporting obligations under DAC8 for crypto-asset service providers.
| Obligation | Who It Applies To | Key Data Points | Reporting Destination |
|---|---|---|---|
| User identification | Crypto-asset service providers in EU | Name, address, tax ID, date of birth | National tax authority |
| Transaction reporting | Crypto-asset service providers in EU | Gross proceeds, transaction type, asset type | National tax authority |
| Cross-border exchange | EU member state authorities | All reportable data sets | Other EU member states |
CARF Crypto Reporting and the OECD Global Framework
CARF, the Crypto-Asset Reporting Framework, is the OECD's answer to the same problem DAC8 addresses at the EU level. The two frameworks share significant structural overlap, which is deliberate. The OECD designed CARF to function alongside the Common Reporting Standard, requiring reporting entities to collect and exchange data on crypto-asset transactions with the tax authorities of participating jurisdictions.
For multinational firms and clients with cross-border crypto activity, CARF crypto reporting adds a layer of complexity beyond DAC8. A Dutch entity with users or investors in non-EU OECD jurisdictions may face CARF obligations in those partner countries. The interaction between DAC8 and CARF is an area where accounting advisers can add real value, helping clients avoid duplicate reporting burdens or, worse, compliance gaps caused by assuming one framework satisfies the other.
The Netherlands, as an OECD member, is expected to align domestic rules with CARF timelines. Finance teams should track both the EU implementation calendar and OECD guidance updates simultaneously rather than treating them as separate workstreams.
FASB ASC 350-60 and Crypto US GAAP Accounting
For firms advising US-listed entities or subsidiaries of US groups, the FASB update to ASC 350-60 represents the most significant change to crypto US GAAP accounting in recent years. The updated standard requires entities to measure crypto assets at fair value at each reporting date, with changes recognised in net income. This replaced the previous indefinite-lived intangible model, under which impairment charges were recognised but gains were not until the asset was sold.
The FASB crypto fair value approach creates volatility in reported earnings, which has implications for covenant compliance, earnings-per-share calculations, and investor communications. Finance teams holding Bitcoin, Ether, or other qualifying assets on a corporate balance sheet now face a mark-to-market requirement every quarter. This is not merely a disclosure change. It affects how treasury policies are written, how hedge accounting is considered, and how audit committees evaluate risk.
ASC 350-60 crypto applies to crypto assets that meet the standard's definition: fungible, created on a distributed ledger, secured through cryptography, and not the reporting entity's own issued token. NFTs and certain governance tokens may fall outside the standard's scope depending on their characteristics. Getting the classification right from the outset is critical.
| Accounting Model | Standard | Measurement Basis | Gain or Loss Recognition |
|---|---|---|---|
| Previous US GAAP | ASC 350 (intangibles) | Cost less impairment | Impairment only; gains deferred |
| Updated US GAAP | ASC 350-60 | Fair value at each reporting date | Both gains and losses in net income |
| IFRS (current) | IAS 2 or IAS 38 | Cost or NRV (IAS 2); cost less impairment (IAS 38) | Impairment under IAS 38; write-downs under IAS 2 |
IFRS Crypto Assets: Where the Standards Stand
The treatment of crypto assets under IFRS remains more fragmented than under US GAAP. The IASB has not yet issued a dedicated standard for crypto assets, which means preparers apply existing standards by analogy. The two most common frameworks applied are IAS 38 (intangible assets) and IAS 2 (inventories), depending on the entity's business model and how it holds the asset.
Crypto IFRS accounting under IAS 38 means the asset is carried at cost less accumulated impairment unless the entity elects the revaluation model, which requires an active market. For many crypto assets, an active market arguably exists, but the practical application of the revaluation model and the treatment of revaluation gains through other comprehensive income rather than profit or loss creates complications for financial statement users.
Entities that hold crypto assets in the ordinary course of business as commodity broker-traders may apply IAS 2 and measure at fair value less costs to sell, with changes recognised in profit or loss. This produces an outcome closer to the FASB model for those entities. The IASB's ongoing agenda project on digital assets is worth monitoring. Any future standard would likely resolve the current inconsistency and may move IFRS closer to the fair value approach FASB has adopted. Finance teams preparing IFRS financial statements today should document their accounting policy choices carefully, as auditors are increasingly scrutinising these decisions.
How the Netherlands Fits Into the Broader Picture
Dutch entities preparing financial statements under Dutch GAAP (Titel 9 BW2) follow guidelines issued by the Dutch Accounting Standards Board (RJ). The RJ has issued guidance on crypto assets that draws on both IFRS principles and Dutch-specific considerations. In practice, many larger Dutch entities and groups prepare consolidated statements under IFRS, meaning the IFRS crypto assets question is directly relevant.
From a tax perspective, the Dutch tax authority (Belastingdienst) treats crypto assets as assets subject to wealth tax under Box 3 for individuals, and as business assets subject to corporate income tax for entities. Crypto-asset service providers operating in the Netherlands are subject to DAC8 reporting obligations once the directive is fully transposed. Finance teams at Dutch firms with international operations must also consider whether CARF crypto reporting obligations arise in partner jurisdictions where they have users or customers.
The convergence of DAC8, CARF, FASB, and IFRS developments means that no single framework can be treated in isolation. A Dutch subsidiary of a US parent, for example, may need to prepare IFRS financial statements at the group level, apply ASC 350-60 for US GAAP consolidation purposes, and comply with DAC8 for EU tax reporting. That is three separate frameworks, each with distinct measurement, disclosure, and filing requirements.
Audit Readiness and the Advisory Opportunity
Crypto holdings and crypto-related revenue streams are increasingly appearing in audit files, and audit teams are asking harder questions than they were even two years ago. For accounting firms, this creates a genuine advisory opportunity. Clients who hold crypto assets on their balance sheet need help with accounting policy documentation, fair value measurement processes, and disclosure drafting. Clients operating crypto-asset platforms need help building the data infrastructure for DAC8 and CARF crypto reporting.
Audit readiness in this context means more than having the right numbers. It means having a defensible audit trail from transaction level through to financial statement line item, with documented policy decisions at every stage. It means being able to demonstrate to auditors how fair value was determined at each reporting date, which exchange rates or pricing sources were used, and how impairment indicators were assessed under whichever standard applies.
Firms that invest in crypto compliance reporting capabilities now are better positioned to retain crypto-native clients and win mandates from traditional businesses adding digital assets to their treasury or payment operations. The technical complexity of DAC8, CARF, FASB fair value, and IFRS creates barriers to entry that reward firms with specialist knowledge.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario: Lars is a finance director at a mid-sized Dutch technology company that began holding Bitcoin and Ether on its balance sheet as part of a treasury diversification strategy. The group prepares consolidated financial statements under IFRS and files a US GAAP reconciliation for its American parent. Lars's team initially classified the crypto holdings as intangible assets under IAS 38, carrying them at cost less impairment. When the parent's auditors queried the treatment under ASC 350-60, which requires fair value measurement with gains and losses in net income, Lars realised the group was applying two inconsistent models without a documented rationale.
The firm's external accountants recommended moving to CryptaCount to centralise the transaction ledger, automate fair value calculations at each reporting date using verified pricing sources, and generate the disclosure notes required under both frameworks. The team also used the platform to map DAC8 reporting obligations for the group's Dutch-registered exchange subsidiary. What had been a reactive, manual process became a structured compliance workflow, and the year-end audit passed with no material findings on digital assets.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive requiring crypto-asset service providers to collect user data and report transaction information to national tax authorities, which then share it with other EU member states. It applies to exchanges, custodians, and certain brokers operating within the EU. Dutch-registered platforms must comply with the Netherlands' domestic implementation of the directive.
How does CARF crypto reporting differ from DAC8?
CARF is the OECD's Crypto-Asset Reporting Framework, designed for global automatic exchange of crypto transaction data between participating jurisdictions. DAC8 covers EU member states specifically, while CARF extends similar requirements to OECD partner countries outside the EU. The two frameworks share structural similarities but operate under different legal bases and timelines, so entities with cross-border activity may need to comply with both.
What does ASC 350-60 require for crypto US GAAP accounting?
ASC 350-60 requires entities to measure qualifying crypto assets at fair value at each reporting date, recognising both gains and losses in net income. This replaced the previous model under which crypto was treated as an indefinite-lived intangible, with only impairment charges recognised. The change affects any US GAAP preparer holding fungible crypto assets on its balance sheet.
What is the FASB crypto fair value measurement approach?
Under the FASB crypto fair value model, entities determine the fair value of qualifying crypto assets using observable market prices at the reporting date. Movements in fair value flow directly through the income statement each period, creating earnings volatility that finance teams need to manage in treasury policies and investor disclosures. The standard applies to fungible, publicly traded crypto assets rather than NFTs or entity-issued tokens.
How are crypto assets treated under IFRS currently?
IFRS does not yet have a dedicated standard for crypto assets. Preparers typically apply IAS 38 (intangible assets) and carry holdings at cost less impairment, or elect the revaluation model if an active market exists. Entities that trade crypto in the ordinary course of business may apply IAS 2 (inventories) and measure at fair value less costs to sell. The IASB has an active project on digital assets that may produce a dedicated standard in future.
What is the difference between crypto IFRS accounting and US GAAP for digital assets?
The key difference is measurement. US GAAP under ASC 350-60 requires fair value measurement with all changes in net income for most crypto assets. IFRS under IAS 38 generally allows cost less impairment, with revaluation gains going to other comprehensive income rather than profit or loss. This means a company holding the same asset could report very different earnings under each framework.
Do Dutch companies need to comply with DAC8 and CARF separately?
Dutch crypto-asset service providers must comply with DAC8 as transposed into Dutch law. If they also have users or customers in non-EU OECD jurisdictions that have adopted CARF, they may face separate CARF reporting obligations in those countries. The two frameworks are complementary but not identical, so firms should assess their obligations under each rather than assuming compliance with one satisfies the other.
How should accounting firms prepare clients for DAC8 reporting deadlines?
Firms should start by auditing the client's transaction data infrastructure to confirm it captures all reportable fields required under DAC8. KYC records, transaction logs, and asset classification data all need to be complete and verifiable. Clients operating on manual or fragmented systems will need to migrate to a structured platform before the first reporting period closes to avoid filing failures and the penalties that accompany them. Robust crypto compliance reporting processes are the foundation.
Can CryptaCount support both DAC8 reporting and FASB fair value calculations?
CryptaCount is designed to support crypto-asset compliance and accounting workflows across multiple frameworks, including DAC8 reporting, CARF data preparation, and fair value measurement for FASB and IFRS purposes. The platform centralises transaction data, applies verified pricing sources for fair value calculations, and generates the outputs needed for both regulatory filings and financial statement disclosures.
Source: CryptaCount
FAQ
DAC8 is an EU directive requiring crypto-asset service providers to collect user data and report transaction information to national tax authorities, which then share it with other EU member states. It applies to exchanges, custodians, and certain brokers operating within the EU. Dutch-registered platforms must comply with the Netherlands' domestic implementation of the directive.
CARF is the OECD's Crypto-Asset Reporting Framework, designed for global automatic exchange of crypto transaction data between participating jurisdictions. DAC8 covers EU member states specifically, while CARF extends similar requirements to OECD partner countries outside the EU. The two frameworks share structural similarities but operate under different legal bases and timelines, so entities with cross-border activity may need to comply with both.
ASC 350-60 requires entities to measure qualifying crypto assets at fair value at each reporting date, recognising both gains and losses in net income. This replaced the previous model under which crypto was treated as an indefinite-lived intangible, with only impairment charges recognised. The change affects any US GAAP preparer holding fungible crypto assets on its balance sheet.
Under the FASB crypto fair value model, entities determine the fair value of qualifying crypto assets using observable market prices at the reporting date. Movements in fair value flow directly through the income statement each period, creating earnings volatility that finance teams need to manage in treasury policies and investor disclosures. The standard applies to fungible, publicly traded crypto assets rather than NFTs or entity-issued tokens.
IFRS does not yet have a dedicated standard for crypto assets. Preparers typically apply IAS 38 (intangible assets) and carry holdings at cost less impairment, or elect the revaluation model if an active market exists. Entities that trade crypto in the ordinary course of business may apply IAS 2 (inventories) and measure at fair value less costs to sell. The IASB has an active project on digital assets that may produce a dedicated standard in future.
The key difference is measurement. US GAAP under ASC 350-60 requires fair value measurement with all changes in net income for most crypto assets. IFRS under IAS 38 generally allows cost less impairment, with revaluation gains going to other comprehensive income rather than profit or loss. This means a company holding the same asset could report very different earnings under each framework.
Dutch crypto-asset service providers must comply with DAC8 as transposed into Dutch law. If they also have users or customers in non-EU OECD jurisdictions that have adopted CARF, they may face separate CARF reporting obligations in those countries. The two frameworks are complementary but not identical, so firms should assess their obligations under each rather than assuming compliance with one satisfies the other.
Firms should start by auditing the client's transaction data infrastructure to confirm it captures all reportable fields required under DAC8. KYC records, transaction logs, and asset classification data all need to be complete and verifiable. Clients operating on manual or fragmented systems will need to migrate to a structured platform before the first reporting period closes to avoid filing failures and the penalties that accompany them.
CryptaCount is designed to support crypto-asset compliance and accounting workflows across multiple frameworks, including DAC8 reporting, CARF data preparation, and fair value measurement for FASB and IFRS purposes. The platform centralises transaction data, applies verified pricing sources for fair value calculations, and generates the outputs needed for both regulatory filings and financial statement disclosures.