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

Crypto financial reporting has moved from a niche compliance concern to a board-level priority. Across the EU, the United States, and international markets, the rules governing how digital assets are recognised, measured, and disclosed have changed substantially in recent years. DAC8 reporting obligations now require EU-based crypto-asset service providers to share client transaction data with tax authorities automatically. Simultaneously, FASB's ASC 350-60 has redefined crypto US GAAP accounting by mandating fair value measurement for most fungible digital assets. IFRS crypto assets guidance continues to evolve, and the OECD's CARF crypto reporting framework is being adopted by dozens of jurisdictions. For accounting firms, auditors, and CFOs managing multi-entity or multi-jurisdictional crypto exposure, understanding how these frameworks interact is not optional. The cost of misclassification, missed disclosures, or late reporting is rising fast.

What DAC8 Reporting Requires and Who It Affects

DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation, specifically extended to cover crypto-asset transactions. It requires crypto-asset service providers operating within the EU to collect, verify, and report user transaction data to the tax authority in their member state of registration. That authority then shares the data automatically with other EU member states where the user is tax-resident. The scope is broad: it covers exchanges, brokers, and certain wallet service providers that facilitate transfers above defined thresholds.

For accounting firms advising clients who operate crypto platforms, or who hold crypto through EU-regulated intermediaries, DAC8 creates a direct compliance obligation. Firms need to confirm that their clients' service providers are correctly categorised under the directive, that the right legal entity is registered, and that reporting timelines align with client year-end cycles. Importantly, DAC8 and the OECD's CARF crypto reporting framework are designed to be interoperable. EU member states that implement DAC8 are effectively satisfying their CARF obligations simultaneously, which simplifies cross-border coordination but raises the stakes for any gap in domestic implementation.

The table below summarises the core obligations DAC8 places on reporting crypto-asset service providers.

FASB ASC 350-60 and Crypto US GAAP Accounting

The Financial Accounting Standards Board introduced ASC 350-60 to give preparers a dedicated accounting model for certain crypto assets, replacing the patchwork of indefinite-lived intangible asset guidance that had been applied previously. Under the updated standard, entities must measure qualifying crypto assets at fair value at each reporting date, with changes in fair value recognised in net income. This is a material shift. Under the old indefinite-lived intangible model, entities could only write assets down, never up, meaning unrealised gains were invisible on the income statement until disposal.

The standard applies to fungible crypto assets that are created or reside on a distributed ledger, secured through cryptography, and do not give the holder a claim on underlying goods, services, or financial assets. This definition excludes NFTs, wrapped tokens with contractual redemption rights, and certain tokenised securities. For accounting firms advising US entities or foreign private issuers reporting under US GAAP, understanding which assets fall within ASC 350-60 and which do not is the first step in any crypto US GAAP accounting engagement.

FASB also requires enhanced disclosures, including a rollforward of crypto asset holdings, the cost basis of assets sold during the period, and significant concentrations of crypto asset risk. These disclosures are designed to give financial statement users a clearer picture of both realised and unrealised performance.

IFRS Crypto Assets: The Current Framework and Its Limitations

Unlike FASB, the International Accounting Standards Board has not yet issued a dedicated IFRS standard for crypto assets. Entities reporting under IFRS must apply existing standards by analogy, and the outcome depends heavily on the nature of the asset and the entity's business model. The IASB's agenda decision, confirmed through the IFRS Interpretations Committee, concluded that holdings of crypto assets that do not give the holder a contractual right should generally be accounted for under IAS 38 as intangible assets, unless the entity holds them for sale in the ordinary course of business, in which case IAS 2 may apply.

Crypto ifrs accounting under IAS 38 means cost less impairment as the default, with the revaluation model available only if an active market exists. In practice, the revaluation model is rarely applied because most preparers are cautious about asserting an active market for assets whose trading characteristics may not meet the standard's criteria. This creates an asymmetry with ASC 350-60: IFRS preparers may carry the same Bitcoin holding at a lower book value than their US GAAP counterparts during a bull market, and the financial statements will look materially different despite identical economic exposure.

The IASB has indicated that crypto assets remain on its research agenda, but no exposure draft had been published as of the time of writing. Accounting firms advising IFRS clients should document the accounting policy choices made for each asset type and revisit them annually as guidance develops. IFRS crypto assets treatment also intersects with presentation: where holdings are material, entities need to consider whether separate line items or enhanced notes disclosures are warranted to avoid misleading financial statement users.

CARF Crypto Reporting and Its Relationship with DAC8

The Common Reporting Framework for Crypto Assets, known as CARF, is the OECD's response to the gap that existed in international tax information exchange. The Common Reporting Standard covered traditional financial accounts, but crypto assets held directly with a service provider fell outside its scope. CARF closes that gap by requiring reporting crypto-asset service providers to collect standardised data on their users' transactions and report it to the tax authority in the provider's jurisdiction, which then exchanges it with other participating countries.

CARF crypto reporting covers exchanges between crypto assets and fiat currencies, exchanges between different crypto assets, and transfers to or from wallets where the service provider can identify the user. The framework also includes retail payment transactions above a specified threshold. For accounting firms, CARF matters in two ways. First, clients who operate or invest through crypto service providers in CARF-adopting countries will have their transaction data shared with HMRC, the IRS, or other revenue bodies, which increases audit risk for any client whose self-reported figures do not reconcile. Second, clients operating crypto businesses may themselves be reporting entities under CARF, creating a compliance burden that firms need to help them manage.

The interoperability between CARF and DAC8 is intentional. The EU designed DAC8 to satisfy CARF obligations for member states, meaning a single reporting infrastructure can serve both frameworks. Firms advising EU-based crypto businesses should confirm that their clients' reporting systems produce data that meets both sets of technical requirements, since the data schemas are aligned but not identical.

How These Frameworks Interact in a Multi-Jurisdictional Audit

Large accounting firms and audit teams increasingly encounter clients with crypto holdings that span multiple jurisdictions, multiple asset types, and multiple custodians. In that environment, no single framework governs the engagement. A US-listed company with a European subsidiary holding crypto assets on an EU-regulated exchange will face ASC 350-60 at the group level, IFRS crypto assets treatment at the subsidiary level if the sub reports under IFRS, and DAC8 reporting obligations at the exchange level. Reconciling all three requires a clear mapping of which entity holds which assets, under which accounting policy, and through which regulated intermediary.

The practical starting point is asset-level data. Firms need complete transaction histories from every custodian or exchange the client uses, mapped to the correct legal entity, with cost basis calculated under the methodology required by each applicable standard. Cost basis methodology is not uniform: FIFO, specific identification, and weighted average cost produce different figures, and different jurisdictions prescribe different methods for tax versus financial reporting purposes. A structured crypto compliance reporting for accounting firms process, supported by purpose-built software, reduces the risk of inconsistency between the tax return, the statutory accounts, and any DAC8 or CARF data already submitted by the exchange.

Practical Steps for Accounting Firms Setting Up a Crypto Reporting Framework

Firms that want to build a repeatable crypto reporting service need to address four layers: data collection, accounting policy documentation, compliance filing, and client advisory. Data collection means establishing automated feeds from the exchanges and custodians your clients use, rather than relying on client-exported spreadsheets which are prone to gaps and formatting errors. Accounting policy documentation means recording, for each client and each asset type, which standard applies, which measurement model has been chosen, and what the rationale is. This documentation is the first thing an auditor or tax inspector will ask for.

Compliance filing encompasses DAC8 and CARF obligations for clients who operate crypto platforms, as well as the tax reporting obligations for clients who simply hold or trade crypto assets. These are distinct workflows and should be managed separately to avoid confusion between the client's own reporting obligations and the reports they will receive from exchanges about their own activity. The advisory layer sits above all of this: firms that understand how FASB ASC 350-60 interacts with CARF crypto reporting, and how IFRS crypto assets treatment affects a client's reported earnings, are positioned to offer genuinely valuable guidance rather than just compliance processing.

Illustrative Scenario

To illustrate how this applies in practice, consider the following scenario: Priya is a senior manager at a mid-tier UK accounting firm that recently onboarded a fintech client operating a crypto exchange registered in an EU member state. The client also holds a treasury allocation of Bitcoin on its own balance sheet and files consolidated accounts under IFRS at the UK parent level.

Priya's team needed to address three distinct reporting layers simultaneously. At the exchange subsidiary level, the firm had DAC8 reporting obligations requiring annual submission of user transaction data to the local tax authority. At the group level, the Bitcoin treasury holding required an accounting policy decision under IFRS crypto assets guidance: the team documented a policy under IAS 38 using the cost model, with a note disclosing the fair value of the holding at year end for reader transparency. At the individual asset level, they had to confirm that the exchange's transaction data matched the figures the client had self-reported on its own corporate tax return, ahead of the automatic exchange that DAC8 would trigger.

Using CryptaCount, Priya's team imported exchange data directly, reconciled it against the client's internal ledger, and produced the DAC8-ready data file alongside the IFRS disclosure notes in a single workflow. The engagement that previously took several weeks of manual reconciliation was completed in a fraction of the time, and the audit trail was fully documented.

Frequently Asked Questions

What is DAC8 reporting and which businesses does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers registered in EU member states to collect user transaction data and report it annually to their national tax authority. The authority then shares this data automatically with other EU member states where users are tax-resident. It applies to exchanges, brokers, and certain wallet service providers that facilitate qualifying transactions above defined thresholds.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD's global framework for crypto-asset transaction reporting, designed to extend international tax information exchange to cover crypto held through service providers. DAC8 is the EU's domestic implementation, deliberately designed to be interoperable with CARF so that EU member states satisfy both obligations through a single reporting infrastructure. Outside the EU, jurisdictions adopt CARF independently on their own timelines.

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

ASC 350-60 requires entities reporting under US GAAP to measure qualifying fungible crypto assets at fair value at each reporting date, with changes recognised in net income. This replaced the previous practice of treating crypto as an indefinite-lived intangible asset, which only allowed downward impairment. The standard also requires enhanced disclosures including a holdings rollforward and cost basis of assets sold.

Which IFRS standard applies to crypto assets?

There is no dedicated IFRS standard for crypto assets. The IFRS Interpretations Committee concluded that most crypto asset holdings should be accounted for under IAS 38 as intangible assets, using cost less impairment as the default measurement model. If an entity holds crypto for sale in the ordinary course of business, IAS 2 may apply instead. The IASB has indicated ongoing research into this area.

Can crypto assets be measured at fair value under IFRS?

Under IAS 38, fair value measurement through the revaluation model is permitted only if an active market exists for the asset. Preparers must assess whether the trading characteristics of each crypto asset meet the IAS 38 definition of an active market. In practice, many firms default to the cost model due to uncertainty about this assessment, which creates a divergence from ASC 350-60 fair value treatment.

How does FASB fair value measurement affect the income statement?

Under ASC 350-60, both unrealised gains and unrealised losses on qualifying crypto assets flow through net income at each reporting date. This means earnings volatility increases for entities holding significant crypto positions, because mark-to-market movements are recognised immediately rather than deferred until disposal. Finance teams need to communicate this clearly to investors and lenders who may be evaluating covenant compliance.

What data do accounting firms need to support DAC8 and CARF compliance for clients?

Firms need complete transaction-level data from every exchange or custodian the client uses, including timestamps, counterparty identifiers where available, asset types, quantities, and fiat equivalent values at the time of each transaction. This data must be mapped to the correct legal entity and reconciled against the client's internal accounting records. Gaps in exchange data are a common problem and should be identified early in the engagement.

Is there a single cost basis method required across DAC8, CARF, and ASC 350-60?

No. Different frameworks and jurisdictions prescribe or permit different cost basis methods. ASC 350-60 allows specific identification or other methods consistent with US GAAP. IFRS does not mandate a single method for crypto assets. Tax authorities in various jurisdictions may require FIFO, weighted average, or specific identification for capital gains purposes. Firms should document the methodology applied for each client and each purpose separately to avoid inconsistency between financial reporting and tax filings.

How should accounting firms document crypto accounting policy choices for audit purposes?

Firms should prepare a written accounting policy memo for each client that specifies the applicable standard for each asset type held, the measurement model selected, the cost basis methodology, and the rationale for each choice. This memo should be updated whenever the client acquires a new asset type or when relevant guidance changes. It forms part of the permanent audit file and is typically the first document requested during an external audit or regulatory review.

When is a dedicated crypto accounting platform necessary rather than general ledger software?

General ledger software is not designed to handle the volume, frequency, or data structure of crypto transactions. Firms managing clients with active trading histories, staking rewards, DeFi activity, or multi-exchange exposure will quickly find that manual data entry into a standard ledger is error-prone and unsustainable. Dedicated platforms automate data ingestion, apply cost basis calculations consistently, and produce audit-ready outputs aligned with DAC8, CARF, ASC 350-60, and IFRS crypto assets requirements.

Source: CryptaCount