DAC8 Reporting and Global Crypto Accounting Standards: A Guide for Finance Teams
Crypto financial reporting is no longer a niche concern for a handful of specialist firms. From DAC8 reporting obligations landing on EU-based intermediaries to FASB's revised fair value rules reshaping balance sheets across the United States, finance teams and accounting practices now face a genuinely complex web of overlapping standards. The challenge is not simply knowing that these frameworks exist. It is understanding which ones apply to your clients, how they interact, and what the practical consequences of getting them wrong look like. This guide covers the major standards: DAC8, CARF, FASB ASC 350-60, and IFRS for crypto assets. It is aimed at accounting firms, CFOs, and finance directors who need a clear operational picture rather than a theoretical overview.
Why Global Crypto Reporting Has Fragmented Across Standards
The absence of a single global standard for crypto assets is the starting point for almost every compliance headache in this space. Accounting bodies and tax authorities developed their frameworks at different times, for different purposes, and with different underlying assumptions about what crypto assets actually are. The result is a patchwork: IFRS treats most crypto assets as intangible assets under IAS 38, subject to strict impairment rules. US GAAP, through FASB's updated ASC 350-60, has moved to a fair value model. Meanwhile, tax-reporting regimes like DAC8 in the EU and CARF at the OECD level are not accounting standards at all; they are information-exchange frameworks that create separate, parallel obligations.
This fragmentation matters because a client operating across jurisdictions can face obligations under all of these frameworks simultaneously. A US-listed company holding Bitcoin must follow ASC 350-60. If it also has a European subsidiary using a crypto exchange that falls within DAC8 scope, that exchange faces its own reporting obligations. The accounting treatment and the tax-reporting obligation are distinct, but the underlying transaction data feeds both. Finance teams that treat them as separate problems tend to create duplicated work and introduce reconciliation risk.
DAC8 Reporting: What EU Obligations Mean for Crypto Service Providers
DAC8 is the eighth iteration of the EU's Directive on Administrative Cooperation, and it extends automatic exchange of information to crypto-asset service providers. The core obligation under DAC8 reporting is that crypto-asset service providers operating in EU member states must collect, verify, and report information about their users' transactions to the relevant national tax authority. That authority then shares the data with tax administrations in other member states where those users are resident.
The scope is broad. It covers exchanges, brokers, and certain wallet providers. The types of transactions captured include exchanges of crypto for fiat, exchanges between different crypto assets, and transfers. Reportable information includes the user's identifying details, the type and volume of transactions, and the aggregate proceeds received during the reporting year.
For accounting firms advising crypto-asset service providers, DAC8 reporting creates an immediate client-service need. Providers must build or procure systems capable of capturing the required data fields at transaction level, mapping them to the correct reporting format, and submitting accurately and on time. Errors or omissions in DAC8 filings carry penalty exposure, and because the data flows to multiple tax authorities automatically, inconsistencies between a user's own tax return and the DAC8 data held by their domestic authority will surface.
The following table summarises the key reporting obligations under DAC8 for crypto-asset service providers.
| Obligation | Detail |
|---|---|
| Who must report | Crypto-asset service providers with an EU nexus (incorporated, managed, or serving EU-resident users) |
| What is reported | User identity data, transaction types, asset types, volumes, and aggregate fiat proceeds |
| Reporting destination | National competent authority in the relevant EU member state, then shared via automatic exchange |
| Data standard | Aligned with OECD CARF XML schema to facilitate cross-border exchange |
| Penalties | Set at member-state level; non-compliance risks fines and reputational consequences |
CARF Crypto Reporting and Its Relationship to DAC8
The OECD's Crypto-Asset Reporting Framework, known as CARF, is the international template from which DAC8 draws heavily. CARF crypto reporting was designed to close the gap that existed when the Common Reporting Standard was first introduced: crypto transactions fell outside CRS because they did not sit within traditional financial institutions in the same way that bank accounts and investment portfolios do.
CARF establishes a global standard for automatic exchange of information on crypto transactions between tax authorities. Its scope mirrors DAC8 in many respects: it targets reporting crypto-asset service providers, requires collection of user identification data consistent with due-diligence procedures, and mandates reporting of exchange and transfer transactions.
The practical significance for firms serving international clients is that CARF and DAC8 are designed to be interoperable. A service provider that implements a CARF-compliant reporting system will largely satisfy DAC8 requirements, subject to any EU-specific additions. This alignment reduces duplication for globally operating providers, but it also means that a firm's non-compliance in one jurisdiction can create discrepancies visible to tax authorities in another. Building compliant data infrastructure once, rather than retrofitting it jurisdiction by jurisdiction, is the more defensible approach for any client with multi-market operations.
FASB ASC 350-60 and Crypto US GAAP Accounting
FASB's Accounting Standards Update on crypto assets, codified under ASC 350-60, represents the most significant shift in crypto US GAAP accounting in years. The standard requires entities holding qualifying crypto assets to measure them at fair value, with changes in fair value recognised in net income each reporting period. This replaces the previous approach, under which entities generally applied indefinite-lived intangible asset accounting, meaning impairment charges were recognised on the way down but gains could not be recognised until disposal.
The practical consequences of ASC 350-60 are significant for any US-based or US-reporting client holding crypto on their balance sheet. Earnings volatility will increase for firms with material crypto holdings, since every mark-to-market movement flows through the income statement. Disclosures under the standard require entities to present the cost basis of their crypto holdings, unrealised gains and losses, and the fair value measurement methodology used.
The table below outlines the key differences between the old and new treatment under US GAAP.
| Aspect | Previous US GAAP Treatment | ASC 350-60 Treatment |
|---|---|---|
| Measurement basis | Cost less impairment (indefinite-lived intangible) | Fair value at each reporting date |
| Upward revaluation | Not permitted until disposal | Recognised in net income each period |
| Impairment | Required when fair value fell below cost | Not applicable; fair value model replaces impairment |
| Disclosure | Limited | Cost basis, unrealised gains and losses, fair value methodology required |
For accounting firms, this standard creates advisory revenue opportunities. Clients who adopted legacy accounting treatment need to transition their policies, update their systems to capture fair value data at period-end, and revise their financial statement disclosures. Firms that can guide clients through this process, and provide the sub-ledger infrastructure to support it, are well positioned. The crypto compliance reporting obligations that flow from ASC 350-60 also interact with tax reporting, since fair value movements affect the tax base in ways that differ from the prior impairment model.
IFRS Crypto Assets: The IAS 38 Framework and Its Limitations
Under IFRS, the treatment of crypto assets has historically been determined by IAS 38, the intangible assets standard, because most crypto assets lack physical substance and are not financial instruments under IAS 32. Crypto ifrs accounting under IAS 38 allows entities to choose between the cost model and the revaluation model, but the revaluation model is only available where an active market exists for the asset. For widely traded assets like Bitcoin or Ether, an active market can generally be demonstrated, which means revaluation is technically available. However, under IAS 38, revaluation gains go to other comprehensive income, not to profit or loss, while impairment losses flow through the income statement. This asymmetry is a known limitation.
The IASB has acknowledged that IAS 38 was not designed with crypto assets in mind. Work has been ongoing to develop more tailored guidance, but as of the time of writing, entities applying IFRS still navigate the standards that were written for a different class of asset. This creates judgement calls around active market determination, unit of account, and the appropriateness of the revaluation model, all of which require robust documentation to satisfy auditors.
For firms auditing or advising IFRS reporters with crypto holdings, the key risk areas are the active market assessment, impairment testing methodology, and disclosure adequacy. IFRS crypto assets held for strategic purposes require a different treatment conversation than those held by an exchange or broker as inventory, where IAS 2 may be more relevant.
FASB Fair Value and IFRS Convergence: Where the Gap Remains
The shift to FASB crypto fair value measurement under ASC 350-60 has widened the gap between US GAAP and IFRS in this area. Under IFRS, the revaluation model is optional and asymmetric. Under US GAAP, fair value measurement is now mandatory for qualifying crypto assets, with symmetric income statement recognition. A multinational group reporting under both frameworks will need to maintain parallel workstreams for the same underlying holdings, reconciling differences in recognised gains, losses, and carrying values across reporting periods.
This divergence has operational consequences. Finance systems need to be capable of producing both sets of outputs from the same transaction data. Intercompany eliminations involving crypto assets held in different subsidiaries require careful treatment. And where a group has entities in DAC8-scope jurisdictions, the tax-reporting obligations run alongside both sets of accounting obligations, each requiring its own data trail. The firms that will serve their clients best in this environment are those that have built or adopted technology capable of handling multi-standard treatment at the sub-ledger level.
Illustrative Scenario
To illustrate how this applies in practice, consider the following scenario:
James is the CFO of a mid-sized fintech group headquartered in London, with operating subsidiaries in Germany and the United States. The group holds a portfolio of crypto assets across all three entities. The US subsidiary reports under US GAAP and is now required to apply ASC 350-60, meaning James's team must produce fair value measurements for each crypto holding at every quarter-end and recognise the movements in net income. The German subsidiary falls within DAC8 scope because it operates a crypto exchange function for corporate clients, so it must implement user due-diligence procedures and file DAC8 reports with the German tax authority. The UK parent applies IFRS, navigating IAS 38 with a revaluation policy supported by active market evidence.
James's team was previously managing these obligations across three separate spreadsheet workstreams, each maintained by a different analyst. Reconciliation between the sub-ledger and the group consolidation was taking several days at each period-end, and the DAC8 data-mapping exercise had created a backlog. After moving to CryptaCount, the group consolidated its transaction data into a single platform capable of producing ASC 350-60 fair value outputs, IAS 38 revaluation schedules, and DAC8-ready reporting extracts from the same underlying data. Period-end close time for the crypto portfolio dropped materially, and the DAC8 filing process became a structured workflow rather than an ad hoc exercise.
For firms advising clients in similar multi-standard environments, the practical lesson is that the data architecture matters as much as the accounting policy. You can have the right policies on paper and still fail on execution if the underlying data is fragmented. Robust crypto compliance reporting infrastructure is not optional at this stage of the market.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 reporting is an EU directive requiring crypto-asset service providers with an EU nexus to collect information on user transactions and report it to national tax authorities, which then share the data automatically with other member states. It applies to exchanges, brokers, and certain other providers operating in or serving EU-resident users. The framework is closely aligned with the OECD's CARF standard to enable cross-border data exchange.
How does CARF crypto reporting differ from DAC8?
CARF is the OECD's global template for automatic exchange of crypto transaction data between tax authorities, while DAC8 is the EU's implementation of a comparable framework within the bloc. The two are designed to be interoperable. A provider that builds a CARF-compliant system will largely satisfy DAC8 requirements, though EU-specific requirements may add to the baseline CARF obligations.
What does ASC 350-60 require under crypto US GAAP accounting?
ASC 350-60 requires entities holding qualifying crypto assets to measure them at fair value at each reporting date, with changes in fair value recognised directly in net income. This replaced the previous cost-less-impairment model, which allowed only downward adjustments through the income statement. Entities must also provide enhanced disclosures covering cost basis, unrealised gains and losses, and fair value methodology.
How are crypto assets treated under IFRS?
Most crypto assets are classified as intangible assets under IAS 38 for IFRS reporters. Entities may apply either the cost model or the revaluation model, with the revaluation model only available where an active market exists. Unlike ASC 350-60, IFRS does not route revaluation gains through profit or loss: they go to other comprehensive income, while impairment losses hit the income statement, creating an asymmetric treatment.
What is FASB crypto fair value and how does it affect earnings?
FASB crypto fair value refers to the measurement approach mandated under ASC 350-60, under which qualifying crypto assets are marked to market at each period-end. Any increase or decrease in fair value is recognised in net income for that period. For entities with material crypto holdings, this introduces earnings volatility that did not exist under the prior impairment-only model, which is a material consideration for investors and analysts reviewing financial statements.
Do DAC8 and CARF obligations affect how crypto assets are accounted for on the balance sheet?
DAC8 and CARF are tax-reporting and information-exchange frameworks, not accounting standards, so they do not directly determine balance sheet treatment. However, they require accurate transaction-level data that overlaps substantially with the data needed for accounting purposes. Finance teams that maintain a clean, reconciled sub-ledger to support accounting under IFRS or US GAAP are better placed to meet DAC8 and CARF reporting requirements without building a separate data infrastructure.
Which accounting standard applies to a company holding crypto assets in Hong Kong?
Hong Kong financial reporting follows Hong Kong Financial Reporting Standards, which are substantially converged with IFRS. In practice, this means most Hong Kong entities holding crypto assets apply the IAS 38 intangible assets framework, subject to any specific guidance issued by the Hong Kong Institute of Certified Public Accountants. The treatment follows the same principles as IFRS: cost or revaluation model, active market determination, and asymmetric income recognition.
What are the audit risks for firms reviewing crypto assets under IFRS?
The main audit risks under crypto ifrs accounting include the active market determination for revaluation purposes, the completeness and accuracy of transaction records supporting the cost basis, impairment testing methodology for assets measured under the cost model, and the adequacy of financial statement disclosures. Custody arrangements and the controls around private key management are also areas that auditors increasingly examine as part of existence and rights-and-obligations assertions.
How should accounting firms approach multi-standard crypto reporting for group clients?
Firms should first map each entity in the group to its applicable accounting standard and tax-reporting regime, since a single group may have entities subject to US GAAP, IFRS, and DAC8 simultaneously. The most efficient approach is to centralise transaction data in a platform capable of producing outputs for multiple standards from the same source data, rather than maintaining parallel manual workstreams. This reduces reconciliation risk and accelerates period-end close for the crypto portfolio.
Source: CryptaCount
FAQ
DAC8 reporting is an EU directive requiring crypto-asset service providers with an EU nexus to collect information on user transactions and report it to national tax authorities, which then share the data automatically with other member states. It applies to exchanges, brokers, and certain other providers operating in or serving EU-resident users. The framework is closely aligned with the OECD's CARF standard to enable cross-border data exchange.
CARF is the OECD's global template for automatic exchange of crypto transaction data between tax authorities, while DAC8 is the EU's implementation of a comparable framework within the bloc. The two are designed to be interoperable. A provider that builds a CARF-compliant system will largely satisfy DAC8 requirements, though EU-specific requirements may add to the baseline CARF obligations.
ASC 350-60 requires entities holding qualifying crypto assets to measure them at fair value at each reporting date, with changes in fair value recognised directly in net income. This replaced the previous cost-less-impairment model, which allowed only downward adjustments through the income statement. Entities must also provide enhanced disclosures covering cost basis, unrealised gains and losses, and fair value methodology.
Most crypto assets are classified as intangible assets under IAS 38 for IFRS reporters. Entities may apply either the cost model or the revaluation model, with the revaluation model only available where an active market exists. Unlike ASC 350-60, IFRS does not route revaluation gains through profit or loss: they go to other comprehensive income, while impairment losses hit the income statement, creating an asymmetric treatment.
FASB crypto fair value refers to the measurement approach mandated under ASC 350-60, under which qualifying crypto assets are marked to market at each period-end. Any increase or decrease in fair value is recognised in net income for that period. For entities with material crypto holdings, this introduces earnings volatility that did not exist under the prior impairment-only model, which is a material consideration for investors and analysts reviewing financial statements.
DAC8 and CARF are tax-reporting and information-exchange frameworks, not accounting standards, so they do not directly determine balance sheet treatment. However, they require accurate transaction-level data that overlaps substantially with the data needed for accounting purposes. Finance teams that maintain a clean, reconciled sub-ledger to support accounting under IFRS or US GAAP are better placed to meet DAC8 and CARF reporting requirements without building a separate data infrastructure.
Hong Kong financial reporting follows Hong Kong Financial Reporting Standards, which are substantially converged with IFRS. In practice, this means most Hong Kong entities holding crypto assets apply the IAS 38 intangible assets framework, subject to any specific guidance issued by the Hong Kong Institute of Certified Public Accountants. The treatment follows the same principles as IFRS: cost or revaluation model, active market determination, and asymmetric income recognition.
The main audit risks under crypto ifrs accounting include the active market determination for revaluation purposes, the completeness and accuracy of transaction records supporting the cost basis, impairment testing methodology for assets measured under the cost model, and the adequacy of financial statement disclosures. Custody arrangements and the controls around private key management are also areas that auditors increasingly examine as part of existence and rights-and-obligations assertions.
Firms should first map each entity in the group to its applicable accounting standard and tax-reporting regime, since a single group may have entities subject to US GAAP, IFRS, and DAC8 simultaneously. The most efficient approach is to centralise transaction data in a platform capable of producing outputs for multiple standards from the same source data, rather than maintaining parallel manual workstreams. This reduces reconciliation risk and accelerates period-end close for the crypto portfolio.