DAC8 Reporting and Global Crypto Financial Reporting Standards Explained

Crypto financial reporting has moved well beyond a niche compliance concern. For accounting firms, CFOs, and finance teams managing clients with digital asset exposure, the convergence of DAC8 reporting obligations, CARF crypto reporting, US GAAP changes under ASC 350-60, and evolving IFRS guidance has created a genuinely complex multi-standard environment. Getting one framework wrong does not just create a technical misstatement. It can trigger regulatory scrutiny, audit qualification risk, and penalties across multiple jurisdictions simultaneously. This article maps the key frameworks, explains how they interact, and sets out what practitioners need to action right now to keep client files audit-ready.

Why Crypto Reporting Has Become a Multi-Standard Problem

Until recently, most accounting firms treated crypto assets as a peripheral issue, handled case by case with a general reference to intangible asset guidance. That approach is no longer defensible. Regulators and standard-setters across the US, EU, and internationally have now issued specific, binding guidance, and the frameworks do not always align neatly with each other.

A corporate client holding Bitcoin on its balance sheet may simultaneously face obligations under US GAAP if it files with the SEC, under IFRS if it has subsidiaries in IFRS-adopting jurisdictions, under DAC8 if it operates within the European Union, and under CARF if it transacts through a reporting crypto-asset service provider subject to OECD exchange rules. Each framework has its own measurement basis, disclosure requirements, and reporting deadlines. The risk of inconsistency between a client's tax filings and their audited accounts has never been higher, and auditors are increasingly expected to identify those gaps.

The table below summarises the four primary frameworks practitioners encounter and the core measurement approach each requires.

DAC8 Reporting: What EU-Facing Firms Must Understand

DAC8 is the eighth iteration of the EU's Directive on Administrative Cooperation, and it extends the automatic exchange of information framework to cover crypto-asset transactions. Under DAC8 reporting rules, crypto-asset service providers operating within the EU, or serving EU resident clients, are required to collect and report detailed transactional data to the relevant member state tax authority. That authority then exchanges the data with the tax authorities in the client's country of residence.

For accounting firms advising EU-based clients, or non-EU clients who use EU-based exchanges, the practical implication is significant. Client transaction histories that were previously difficult for tax authorities to access will become part of an automatic, annual data flow. This creates a direct reconciliation requirement: any crypto gains reported on a client's tax return must be consistent with the data their exchange is reporting to the member state authority under DAC8.

Firms that have already been supporting clients through crypto compliance reporting for similar regimes will recognise the pattern. DAC8 effectively mirrors the Common Reporting Standard logic that governs traditional financial accounts, but applied to digital assets. The scope covers not just straightforward buy-and-sell transactions, but also transfers between wallets, where the provider has information on the beneficial owner.

One practical challenge for firms is that DAC8 requires service providers to report fair market value at the time of each transaction. This means clients need to have defensible, time-stamped valuation records. A summary of year-end holdings is not sufficient.

CARF Crypto Reporting and Its Overlap with DAC8

The OECD's Crypto-Asset Reporting Framework, known as CARF, operates on a broadly similar basis to DAC8 but applies across a wider set of participating jurisdictions rather than being limited to EU member states. CARF crypto reporting is designed to close the information gap that exists because crypto asset transactions have historically fallen outside the scope of the Common Reporting Standard and the Foreign Account Tax Compliance Act.

Where DAC8 and CARF overlap in terms of the client population being reported on, firms need to be alert to the risk of double reporting. A crypto-asset service provider operating in an EU member state that has also adopted CARF may find itself submitting similar data through two separate channels. More practically, the definitions used in each framework are not identical. CARF has a broader definition of what constitutes a reportable crypto asset, and the two frameworks have slightly different approaches to wallet-to-wallet transfers. Firms advising service providers on their own reporting obligations need to map their client's product set against both frameworks, not just one.

For clients who are end-users rather than service providers, the key takeaway is that transaction data reported under CARF will feed into automatic exchange of information processes. Tax authorities in participating jurisdictions will receive that data and are expected to cross-reference it against filed returns.

FASB Crypto Fair Value Under ASC 350-60

The Financial Accounting Standards Board's update to ASC 350-60 represents a significant shift in how US GAAP filers account for crypto assets. Before the update took effect, most entities holding crypto were required to carry those assets at historical cost, with impairment recognised when fair value fell below cost, but no upward adjustment permitted. The result was a measurement basis that many preparers and users of accounts found deeply uninformative.

Under the revised ASC 350-60 crypto standard, entities that hold crypto assets meeting the specified criteria are required to measure them at fair value at each reporting date, with changes recognised in net income. This is a meaningful change for firms preparing US GAAP financial statements on behalf of clients with material crypto holdings. It affects not just the income statement but also deferred tax calculations, since unrealised fair value movements create temporary differences that must be tracked.

The FASB crypto fair value requirement also introduces new disclosure obligations. Preparers must disclose the nature and amount of crypto assets held, significant restrictions on those holdings, and a reconciliation of the opening and closing balance. For firms managing audit engagements, these disclosures need to be supported by verifiable, exchange-sourced pricing data rather than estimates.

The table below sets out the key differences between the pre- and post-update treatment under ASC 350-60.

IFRS Crypto Assets: The Ongoing Classification Challenge

IFRS does not yet have a dedicated standard for crypto assets, and the IASB project to address that gap is still in progress. In the meantime, IFRS preparers are required to apply existing standards by analogy, and the correct classification depends on the nature of the asset and the holder's business model. This creates genuine diversity in practice, which is a problem for auditors and for users of accounts trying to compare entities.

For most corporate holders of cryptocurrencies like Bitcoin or Ether, the current consensus under IFRS points to IAS 38 (intangible assets) as the primary standard, unless the entity is a commodity broker-trader holding crypto as inventory, in which case IAS 2 applies. Under IAS 38, entities can choose between the cost model and the revaluation model, but the revaluation model is only available if an active market exists, and there is ongoing debate about whether crypto markets qualify. Under IAS 2, measurement is at the lower of cost and net realisable value.

Crypto ifrs accounting gets more complex when the asset in question is a stablecoin, a tokenised debt instrument, or a token that conveys contractual rights. In those cases, IFRS 9 may be the more appropriate standard. Firms advising on IFRS financial statements need to document the classification rationale carefully, because auditors and regulators are paying closer attention to these judgements than they were even two years ago.

The tension between IFRS and US GAAP treatment is also a live issue for multinational groups that report under both frameworks. A crypto asset measured at fair value under ASC 350-60 in a US subsidiary may be carried at cost under IAS 38 in the consolidated IFRS group accounts, creating reconciling differences that need clear explanation in the notes.

Building an Audit-Ready Crypto Reporting Process

Given the number of frameworks now in play, accounting firms need a structured approach to crypto financial reporting rather than a patchwork of ad hoc treatments. The starting point is a client-level inventory: which assets are held, on which platforms, and under which legal entity. Without that foundation, it is impossible to determine which standards apply and whether the client's existing records are sufficient to support the required disclosures.

Data quality is the single most common failure point in crypto reporting engagements. Exchange CSV exports are frequently incomplete, contain inconsistent timestamp formats, or fail to capture all transaction types. Firms using specialist crypto compliance reporting tools can automate the aggregation and normalisation of this data, significantly reducing the manual reconciliation burden and the risk of misstatement.

For clients subject to DAC8 or CARF, firms should be proactively requesting confirmation from each service provider about what data will be reported, and reconciling that against the client's own records before the automatic exchange occurs. Waiting until a tax authority issues an enquiry based on third-party data is a much harder position to recover from than identifying and correcting discrepancies in advance.

Illustrative Scenario

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

Priya is a senior manager at a mid-tier accounting firm in London. One of her clients is a UK-incorporated holding company with a US subsidiary that holds a portfolio of Bitcoin and Ether acquired over several years. The parent prepares IFRS consolidated accounts; the US subsidiary files under US GAAP. The client also uses a major EU-based exchange, which means the exchange will be subject to DAC8 reporting obligations.

Priya's challenge is threefold. She needs to ensure the US subsidiary's accounts reflect the new ASC 350-60 crypto fair value requirements, including the expanded disclosures. She needs to classify the same assets correctly under IAS 38 in the consolidated IFRS accounts and document why the revaluation model is or is not available. And she needs to reconcile the transaction data the EU exchange will report under DAC8 against the client's own records, so there are no unexplained discrepancies when the UK tax authority receives the automatic exchange data.

Using CryptaCount, Priya pulls the client's full transaction history across all wallets and exchanges into a single sub-ledger, generates fair value schedules keyed to the correct reporting dates, and produces the reconciliation needed to support both sets of accounts. The DAC8 cross-check is completed before year-end, giving the client time to correct a small number of missing wallet transfers that would otherwise have created a reporting gap.

Frequently Asked Questions

What is DAC8 reporting and which firms are affected?

DAC8 is an EU directive that requires crypto-asset service providers to report transactional data on EU-resident clients to the relevant member state tax authority, which then exchanges the data automatically with other member states. Accounting firms are affected both as advisers to service providers that have direct reporting obligations, and as advisers to individual and corporate clients whose transaction data will be reported by exchanges they use.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD's equivalent framework, designed to apply across a broader set of participating jurisdictions rather than just EU member states. The two frameworks share the same core objective of making crypto transactions visible to tax authorities through automatic exchange of information, but they have slightly different definitions of reportable assets and different treatments for certain wallet transfers. Firms advising clients who operate across both EU and non-EU OECD jurisdictions need to consider both frameworks simultaneously.

What does the ASC 350-60 update mean for US GAAP financial statements?

The FASB's update to ASC 350-60 requires entities holding qualifying crypto assets to measure them at fair value at each reporting date, with all changes recognised in net income. This replaces the previous cost-less-impairment model and introduces expanded disclosure requirements. For firms preparing or auditing US GAAP statements, the change affects income statement presentation, deferred tax calculations, and the level of pricing documentation needed to support the accounts.

Which IFRS standard applies to crypto assets?

There is no dedicated IFRS standard for crypto assets yet. Most corporate holders apply IAS 38 (intangible assets), though commodity broker-traders may use IAS 2 (inventories), and some token types may fall under IFRS 9 (financial instruments). The correct classification depends on the nature of the asset and the holder's business model, and preparers must document their rationale carefully given the level of regulatory and auditor scrutiny in this area.

Can a client be subject to both DAC8 and CARF reporting on the same transactions?

Yes. A crypto-asset service provider operating in an EU member state that has also adopted CARF may be required to report the same underlying transactions through both channels. While there are coordination provisions being developed to avoid pure duplication, the definitions and reporting mechanics are not identical, so firms advising service providers need to map their obligations against both frameworks separately.

What records do clients need to support crypto fair value disclosures under IFRS or US GAAP?

Clients need time-stamped, exchange-sourced pricing data for each asset at each relevant reporting date, plus a complete transaction history showing acquisitions, disposals, and transfers. A summary of year-end holdings is not sufficient for either framework. Gaps in the underlying data are the most common cause of qualification risk in crypto-related audit engagements.

How should accounting firms approach clients with crypto holdings on multiple exchanges?

The starting point is a full inventory of all wallets and exchange accounts, mapped to the legal entity that holds them. Each exchange's data should be extracted, normalised, and reconciled against internal records before any financial statements or tax filings are prepared. Specialist sub-ledger tools designed for crypto compliance reporting can automate much of this aggregation, reducing both the time cost and the risk of error from manual spreadsheet work.

When does DAC8 come into effect for service providers and their clients?

DAC8 has been formally adopted by the EU, with reporting obligations phasing in from 2026 for most in-scope service providers. The precise implementation date in each member state depends on how quickly that state transposes the directive into national law. Firms advising EU-facing clients or service providers should be preparing data collection and reconciliation processes now rather than waiting for the first reporting deadline.

Source: CryptaCount