DAC8 Reporting and Crypto Financial Reporting Standards: What Firms Need to Know
DAC8 reporting has moved from a legislative proposal to an operational reality for crypto-asset service providers and the accounting firms that serve them across the European Union. Estonia, as a digitally advanced EU member state with a well-established e-residency and fintech ecosystem, sits squarely in the scope of this directive. But DAC8 does not operate in isolation. Firms must reconcile its automatic exchange-of-information requirements with the measurement and disclosure rules set out under IFRS, and with the US GAAP framework for any clients with transatlantic reporting obligations. Getting this right means understanding not just what DAC8 requires, but how it interacts with IFRS crypto assets guidance, the FASB's fair value model, and the OECD's Crypto-Asset Reporting Framework. This article sets out the full picture for finance teams and accounting practitioners who need a joined-up view.
What DAC8 Reporting Requires and Why It Matters
The EU's Eighth Directive on Administrative Cooperation, known as DAC8, extends the bloc's automatic exchange of information regime to cover crypto-asset transactions. Crypto-asset service providers authorised or registered in any EU member state, including Estonia, are required to collect and report transaction data on their clients to their domestic tax authority. That authority then shares the data with the tax authorities of the clients' countries of residence.
The scope is broad. DAC8 covers transfers of crypto assets, exchanges between crypto assets and fiat currency, and exchanges between different crypto assets. Providers must report identifying information about each reportable user alongside transaction values and asset types. Aggregate annual reporting thresholds apply, and de minimis exemptions are narrow.
For accounting firms, this creates a direct obligation at the client level. If a firm's client is a crypto-asset service provider, the firm must help that client build data collection workflows, verify user identification records, and structure annual report submissions in the format prescribed by the directive. Clients who are not service providers but who transact in crypto assets may find their transaction histories shared with Estonian or other EU tax authorities, which in turn heightens the need for accurate crypto financial reporting standards in the underlying books.
The table below summarises the key reporting categories under DAC8.
| Reportable Event | Data Points Required | Reporting Party |
|---|---|---|
| Crypto-to-fiat exchange | Transaction date, value in fiat, asset type, user identity | Crypto-asset service provider |
| Crypto-to-crypto exchange | Transaction date, fair market value at exchange, both asset types | Crypto-asset service provider |
| Transfer of crypto assets | Transfer date, quantity, asset identifier, counterparty details where available | Crypto-asset service provider |
| Retail payment in crypto | Transaction date, fiat equivalent, merchant and user identity | Crypto-asset service provider |
IFRS Crypto Assets: The Measurement Problem
DAC8 reporting tells tax authorities what happened. IFRS tells the world what it was worth. The two frameworks address different questions, but they depend on the same underlying data: reliable, timestamped transaction records with accurate fair values.
The IFRS Interpretations Committee issued agenda decisions confirming that crypto assets held by most entities should be accounted for either as intangible assets under IAS 38 or, where an entity holds them for sale in the ordinary course of business, as inventory under IAS 2. Neither standard was designed with digital assets in mind, and neither provides a clean fair value through profit or loss model for general holders.
Under IAS 38, crypto assets are carried at cost less impairment unless the entity adopts the revaluation model, which requires the existence of an active market. Many tokens traded on regulated exchanges can satisfy that active market criterion, but the accounting team must document the assessment. Impairment under IAS 36 is one-directional: losses are recognised, but gains above historical cost are not recognised through profit or loss under the cost model.
This asymmetry is operationally significant for firms advising clients on crypto ifrs accounting. A client holding a large position in a volatile token may have recognised impairment losses in prior periods, only to see the token recover. Under IFRS, that recovery does not reverse through profit or loss at the same rate under the cost model. Finance teams need to track cost layers carefully, and the notes to the financial statements must disclose the accounting policy, the carrying amount, and any restrictions on title.
ASC 350-60 Crypto and the US GAAP Fair Value Shift
For firms with US clients or dual-reporting obligations, the contrast with US GAAP is now stark. The Financial Accounting Standards Board introduced ASC 350-60, a dedicated subtopic for crypto assets, which requires entities to measure certain crypto assets at fair value at each reporting date with changes recognised in net income.
The FASB crypto fair value model applies to crypto assets that meet a specific definition: intangible assets that are created or reside on a distributed ledger, are secured through cryptography, are fungible, and are not produced or issued by the reporting entity or its related parties. Tokens that fall outside this definition, including many governance tokens, wrapped tokens, and staking receipt tokens, may need to be assessed under other guidance.
The practical effect of ASC 350-60 is that crypto us gaap accounting now produces income statement volatility that IFRS does not, at least for entities using the IFRS cost model. A firm advising a company that reports under both standards must maintain parallel valuation schedules and reconcile the two treatments in any consolidation or dual-reporting exercise.
| Standard | Default Measurement Basis | Upward Revaluation Through P&L | Impairment |
|---|---|---|---|
| IFRS (IAS 38 cost model) | Cost less impairment | Not permitted under cost model | Required when recoverable amount falls below carrying value |
| IFRS (IAS 38 revaluation model) | Fair value via revaluation reserve | To other comprehensive income only | Standard IAS 36 applies |
| US GAAP ASC 350-60 | Fair value at each reporting date | Yes, recognised in net income | No separate impairment test; fair value movements capture losses |
CARF Crypto Reporting and Its Relationship to DAC8
The OECD's Crypto-Asset Reporting Framework, commonly called CARF, is the global template from which DAC8 was substantially derived. CARF establishes a common standard for the automatic exchange of information on crypto-asset transactions between tax jurisdictions worldwide. While DAC8 is the EU's mandatory implementation of that standard within the bloc, CARF crypto reporting is intended to operate on a much broader multilateral basis, covering jurisdictions outside the EU that adopt the framework.
For accounting firms in Estonia serving internationally mobile clients or clients with assets on exchanges registered in multiple jurisdictions, CARF is directly relevant. A client using a non-EU exchange that is registered in a CARF-adopting jurisdiction may have their transaction data reported to Estonian tax authorities through the CARF multilateral channel, not through DAC8. The data fields are similar, but the legal gateway is different, and the deadlines for first exchange may vary by jurisdiction.
The practical implication is that no client with significant crypto holdings should assume their activity is visible only to the platform they use. Firms should audit their clients' exchange relationships, identify which platforms are subject to DAC8 and which are subject to CARF, and ensure the transaction records held in the client's own books are sufficient to explain and reconcile any inbound data exchange that a tax authority might reference.
Estonia's Regulatory Context for Crypto Firms
Estonia has historically been one of the more accessible EU jurisdictions for crypto-asset businesses, with a licensing framework administered by the Financial Intelligence Unit. Regulatory tightening in recent years has raised the bar for anti-money laundering compliance and capital requirements, meaning that the pool of licensed entities is smaller but more robustly supervised than it once was.
For the accounting firms that serve these licensed entities, DAC8 compliance sits alongside existing AML reporting obligations, MiCA authorisation preparation, and the need to produce auditable financial statements. The intersection of these obligations means that data architecture matters as much as the accounting policy itself. A crypto-asset service provider that cannot produce a complete, timestamped transaction ledger will struggle to satisfy both its auditors and its DAC8 reporting deadline.
Firms advising Estonian crypto clients should also note that the Estonian Tax and Customs Board has published guidance on the domestic tax treatment of crypto assets, covering income tax on gains and the treatment of mining and staking income. While that guidance predates DAC8, it shapes the context in which DAC8 reports will be reviewed, and discrepancies between reported figures and tax returns will likely attract scrutiny. Ensuring alignment between the client's self-reported tax position and the transaction data that DAC8 will place in the hands of the tax authority is a key advisory task for any engaged firm.
Building an Audit-Ready Crypto Reporting Stack
Accounting firms that want to serve crypto clients well across DAC8, IFRS, and CARF need a reporting stack that connects raw transaction data to financial statement outputs without manual rekeying. The risk of manual processes is not just efficiency: it is auditability. An auditor examining a crypto balance will want to trace each asset from wallet or exchange to the sub-ledger, from the sub-ledger to the trial balance, and from the trial balance to the financial statements. Any break in that chain creates a qualification risk.
The workflow typically involves four layers. First, exchange and wallet integrations that pull transaction data in a structured format. Second, a classification engine that assigns each transaction to an accounting category, applying the correct cost basis method. Third, a fair value pricing layer that attaches auditable market prices to each transaction at the relevant measurement date. Fourth, a reporting layer that produces both the financial statement schedules and the regulatory submission formats required by DAC8 and CARF.
Firms exploring this infrastructure should look at purpose-built platforms designed around crypto compliance reporting for firms, which are built to handle the intersection of tax reporting, accounting standards, and regulatory disclosure in a single audit trail rather than across disconnected spreadsheets.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario:
Markus is the head of tax and compliance at a mid-size accounting firm in Tallinn with three clients holding active crypto-asset service provider licences. As the first DAC8 reporting cycle approaches, Markus realises that two of those clients are collecting user transaction data across multiple exchanges and storing it in separate, unreconciled spreadsheets. One client reports under IFRS and holds a significant portfolio of tokens measured under the IAS 38 cost model, with several positions that have experienced price volatility requiring impairment assessment. A third client has recently taken on US institutional investors and needs a parallel ASC 350-60 schedule for its US GAAP reporting package.
Markus begins by mapping each client's exchange relationships against the DAC8 reportable event categories and identifying gaps in the transaction data. He then works with each client to connect their exchange accounts to CryptaCount, which consolidates the transaction history, applies consistent fair value pricing, and generates both the IFRS sub-ledger schedules and the DAC8 report templates in a single audit trail. The result is that all three clients enter the reporting period with reconciled books, documented accounting policies, and submission-ready DAC8 data, rather than facing a last-minute scramble across disconnected records.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive that requires crypto-asset service providers registered or authorised in any EU member state to collect and automatically report transaction data on their users to national tax authorities. Those authorities then share the data with the tax authorities of the users' countries of residence. It applies to any entity that qualifies as a crypto-asset service provider under the directive's definition, including exchanges, brokers, and certain transfer services.
How does DAC8 interact with the OECD's CARF crypto reporting framework?
CARF is the OECD's global standard for automatic exchange of crypto-asset transaction information, and DAC8 is the EU's mandatory domestic implementation of that standard. Both frameworks require similar data fields and serve the same transparency purpose. Clients using non-EU exchanges in CARF-adopting jurisdictions may have their data reported through the CARF multilateral channel rather than DAC8, so firms must track which framework applies to each platform a client uses.
How should crypto assets be measured under IFRS?
Under current IFRS guidance, most crypto assets are treated as intangible assets under IAS 38 and carried at cost less impairment, unless the entity adopts the revaluation model and can demonstrate the existence of an active market. Entities holding crypto as inventory in the course of business may apply IAS 2 instead. Gains above historical cost are not recognised through profit or loss under the cost model, which creates an asymmetry with how losses are treated.
What changed with ASC 350-60 for crypto US GAAP accounting?
The FASB introduced ASC 350-60 to require entities to measure qualifying crypto assets at fair value at each reporting date, with all changes recognised directly in net income. This replaced an older intangible asset model that only permitted downward impairment. The change means that crypto us gaap accounting now produces income statement volatility in both directions, which is a significant departure from the IFRS cost model.
What is the FASB crypto fair value model and which assets does it cover?
The FASB crypto fair value model under ASC 350-60 applies to crypto assets that are intangible, reside on a distributed ledger, are secured through cryptography, are fungible, and are not created or issued by the reporting entity or its related parties. Assets that fall outside this definition, such as certain governance tokens or staking receipt tokens, may need to be assessed under other accounting guidance and could receive different treatment.
Does Estonia have specific crypto accounting or tax rules beyond DAC8?
Estonia applies IFRS-based accounting standards for entities required to prepare statutory financial statements, so the general IFRS crypto assets framework applies. The Estonian Tax and Customs Board has also published domestic guidance on the income tax treatment of crypto gains, mining, and staking. DAC8 reporting obligations layer on top of these existing requirements rather than replacing them, and discrepancies between DAC8 data and tax returns are likely to attract scrutiny.
What data does a firm need to collect to satisfy DAC8 and IFRS simultaneously?
Both frameworks depend on the same foundation: complete, timestamped transaction records with accurate fair values at the point of each transaction. DAC8 requires this data in a structured format for submission to tax authorities, while IFRS requires it to support balance sheet carrying values, impairment assessments, and financial statement disclosures. Firms that build a single, reconciled transaction ledger can serve both requirements from one data source rather than maintaining separate records.
How should an accounting firm structure its crypto compliance workflow to be audit-ready?
An audit-ready workflow connects exchange and wallet data to a sub-ledger through automated integrations, applies a consistent cost basis method and fair value pricing layer, and produces traceable outputs that link each asset to the financial statements. The key risk in manual processes is breaks in the audit trail that prevent an auditor from tracing a balance from wallet to financial statement. Purpose-built crypto accounting platforms are designed to maintain that chain of evidence across the full reporting cycle.
Source: CryptaCount
FAQ
DAC8 is an EU directive that requires crypto-asset service providers registered or authorised in any EU member state to collect and automatically report transaction data on their users to national tax authorities. Those authorities then share the data with the tax authorities of the users' countries of residence. It applies to any entity that qualifies as a crypto-asset service provider under the directive's definition, including exchanges, brokers, and certain transfer services.
CARF is the OECD's global standard for automatic exchange of crypto-asset transaction information, and DAC8 is the EU's mandatory domestic implementation of that standard. Both frameworks require similar data fields and serve the same transparency purpose. Clients using non-EU exchanges in CARF-adopting jurisdictions may have their data reported through the CARF multilateral channel rather than DAC8, so firms must track which framework applies to each platform a client uses.
Under current IFRS guidance, most crypto assets are treated as intangible assets under IAS 38 and carried at cost less impairment, unless the entity adopts the revaluation model and can demonstrate the existence of an active market. Entities holding crypto as inventory in the course of business may apply IAS 2 instead. Gains above historical cost are not recognised through profit or loss under the cost model, which creates an asymmetry with how losses are treated.
The FASB introduced ASC 350-60 to require entities to measure qualifying crypto assets at fair value at each reporting date, with all changes recognised directly in net income. This replaced an older intangible asset model that only permitted downward impairment. The change means that crypto us gaap accounting now produces income statement volatility in both directions, which is a significant departure from the IFRS cost model.
The FASB crypto fair value model under ASC 350-60 applies to crypto assets that are intangible, reside on a distributed ledger, are secured through cryptography, are fungible, and are not created or issued by the reporting entity or its related parties. Assets that fall outside this definition, such as certain governance tokens or staking receipt tokens, may need to be assessed under other accounting guidance and could receive different treatment.
Estonia applies IFRS-based accounting standards for entities required to prepare statutory financial statements, so the general IFRS crypto assets framework applies. The Estonian Tax and Customs Board has also published domestic guidance on the income tax treatment of crypto gains, mining, and staking. DAC8 reporting obligations layer on top of these existing requirements rather than replacing them, and discrepancies between DAC8 data and tax returns are likely to attract scrutiny.
Both frameworks depend on the same foundation: complete, timestamped transaction records with accurate fair values at the point of each transaction. DAC8 requires this data in a structured format for submission to tax authorities, while IFRS requires it to support balance sheet carrying values, impairment assessments, and financial statement disclosures. Firms that build a single, reconciled transaction ledger can serve both requirements from one data source rather than maintaining separate records.
An audit-ready workflow connects exchange and wallet data to a sub-ledger through automated integrations, applies a consistent cost basis method and fair value pricing layer, and produces traceable outputs that link each asset to the financial statements. The key risk in manual processes is breaks in the audit trail that prevent an auditor from tracing a balance from wallet to financial statement. Purpose-built crypto accounting platforms are designed to maintain that chain of evidence across the full reporting cycle.