DAC8 Reporting and Global Crypto Financial Reporting Standards: A Guide for Accounting Firms

Accounting firms handling crypto-active clients face a reporting landscape that has changed dramatically over the past two years. DAC8 reporting is now live across EU member states, CARF crypto reporting is rolling out through OECD-adopting jurisdictions, and FASB has fundamentally altered how US entities account for digital assets under ASC 350-60. Meanwhile, IFRS crypto assets guidance continues to evolve, leaving firms outside the US navigating a patchwork of standards. Understanding how these frameworks relate to each other, and where they diverge, is no longer optional. Firms that treat crypto compliance as a side concern risk misstating client accounts, missing regulatory deadlines, and failing to spot advisory opportunities that are sitting in plain sight.

What DAC8 Reporting Requires from Firms and Their Clients

DAC8 is the eighth iteration of the EU Directive on Administrative Cooperation and it specifically targets crypto-asset service providers. Under DAC8, reportable crypto-asset service providers operating in any EU member state must collect and report user data, including names, addresses, tax identification numbers, and transaction values, to their local tax authority. Those authorities then exchange the data automatically with counterpart authorities across the EU.

The scope is broad. It covers exchanges, brokers, and certain wallet providers. Firms advising clients who qualify as reporting entities need to understand the data collection obligations as well as the reporting timelines set by each member state. Portugal, for example, transposed the directive in line with the broader EU schedule, meaning service providers based there were required to begin capturing reportable data from the start of the relevant reporting period.

For accounting firms, DAC8 creates two distinct advisory lanes. The first is helping crypto-asset service provider clients build the data infrastructure to meet reporting obligations. The second is helping individual and corporate clients understand that their transaction data is now flowing between tax authorities, which changes the risk calculus around undisclosed crypto holdings significantly. Firms that have not yet briefed their crypto-active clients on DAC8 are already behind.

The following table summarises the key components of a DAC8 report and who bears responsibility for each element.

CARF Crypto Reporting and Its Relationship to DAC8

CARF, the Crypto-Asset Reporting Framework developed by the OECD, is the global counterpart to DAC8. Where DAC8 governs information exchange within the EU, CARF is designed to standardise crypto reporting between OECD member countries and any jurisdiction that adopts the framework by agreement. The two frameworks are closely aligned in terms of the data they require, which was deliberate. The OECD and the European Commission coordinated during the design phase to minimise duplication for firms operating across both EU and non-EU jurisdictions.

CARF crypto reporting applies to crypto-asset service providers in adopting jurisdictions and covers a similar range of transaction types, including exchanges between crypto and fiat, transfers between wallets where a service provider is involved, and retail payment transactions. The first exchanges under CARF are scheduled for 2027 among early-adopting countries, though some jurisdictions have signalled earlier domestic implementation timelines.

For firms with clients operating internationally, the practical implication is that a service provider active in the EU and, say, Australia or Canada may face both DAC8 obligations and CARF obligations simultaneously. The data points required overlap substantially, but the filing formats and submission procedures differ by jurisdiction. Firms building compliance frameworks for these clients now, rather than waiting for enforcement to begin, will be in a much stronger position.

FASB ASC 350-60 and Crypto US GAAP Accounting

In the United States, the Financial Accounting Standards Board finalised ASC 350-60 as a dedicated standard for crypto US GAAP accounting. Before this standard came into effect, entities held most crypto assets at cost less impairment, which meant unrealised gains were never recognised in the income statement. The new standard requires entities to measure qualifying crypto assets at fair value at each reporting date, with changes recognised in net income.

This is a significant shift. FASB crypto fair value measurement means that a company holding Bitcoin or Ether on its balance sheet will now show mark-to-market movements through its profit and loss account every reporting period. For firms auditing US entities with crypto holdings, this increases the complexity of the audit substantially. Fair value inputs must be sourced, documented, and defended. The classification of assets as in-scope or out-of-scope under ASC 350-60 also requires careful analysis, because not all digital assets qualify.

Intangible assets that meet the definition of a crypto asset under the standard include fungible tokens that are created on distributed ledger technology and secured by cryptography. Wrapped tokens, NFTs, and certain stablecoins may fall outside the scope depending on their specific characteristics. Firms should build a classification procedure into their client onboarding process rather than making ad hoc determinations at year-end.

IFRS Crypto Assets: The Current Position and Where It Is Heading

Outside the US, most jurisdictions rely on IFRS for financial reporting, and IFRS crypto assets have historically been accounted for under IAS 38 as intangible assets with an indefinite useful life. Under that treatment, entities could revalue upward only if they adopted the revaluation model and an active market existed, a condition that Bitcoin and certain other assets arguably meet but that few preparers have elected to apply.

The IFRS Interpretations Committee confirmed in 2019 that crypto assets held in the ordinary course of business by commodity brokers could be measured at fair value less costs to sell under IAS 2. For all other holders, the default remained cost less impairment under IAS 38, with no upward revaluation unless the revaluation model was adopted. This created a significant asymmetry relative to FASB crypto fair value treatment.

The IASB has since added a project on crypto assets and related transactions to its work programme. While no final standard has been issued as of the current date, the direction of travel is toward a more nuanced framework that distinguishes between types of digital asset and their economic substance. Firms advising IFRS-reporting clients should be monitoring IASB exposure drafts and preparing clients for the likelihood that accounting treatment will change, possibly requiring retrospective adjustments.

For crypto ifrs accounting in practice, the key decisions firms need to document today are: the classification of each asset type held, the measurement basis chosen, disclosure of significant judgements, and the treatment of income from staking or lending. These are all areas where IASB guidance is still developing and where firms can add genuine advisory value by establishing clear policies now.

How the Frameworks Interact: A Practical Overview for Accounting Firms

The four frameworks described above, DAC8, CARF, ASC 350-60, and IFRS, address different layers of the reporting problem. DAC8 and CARF are tax information exchange regimes. They do not govern how an asset appears on a balance sheet. They govern whether transaction data reaches the tax authority. ASC 350-60 and IFRS, by contrast, govern financial statement presentation and measurement.

A firm advising a European company with US subsidiaries and a crypto treasury could face all four simultaneously. The US subsidiary measures its holdings at FASB crypto fair value under ASC 350-60. The parent reports under IFRS and makes its own classification and measurement decisions. Both entities may deal with counterparty exchanges that have DAC8 or CARF obligations. Coordinating across these layers requires a structured internal process, not a spreadsheet.

For firms using crypto compliance reporting tools, the ability to pull wallet and exchange data into a single system and then map it to the relevant reporting standard for each entity is the foundation. Manual reconciliation at scale is both error-prone and time-consuming. Firms that invest in purpose-built infrastructure now are better placed to absorb additional clients without a proportional increase in compliance overhead.

Building an Advisory Practice Around Crypto Reporting Compliance

Firms that understand these standards thoroughly are well-positioned to develop recurring advisory revenue. Most crypto-active businesses, whether they are traders, treasury managers, or service providers, do not have internal expertise across all four frameworks. They need external advisers who can translate regulatory change into practical accounting and reporting decisions.

The advisory opportunity starts at onboarding. When a new crypto client joins the firm, a structured intake process should capture the jurisdictions they operate in, the asset types they hold, whether they qualify as a reporting entity under DAC8 or CARF, and which accounting standard governs their financial statements. That intake feeds directly into the compliance calendar and the fee estimate.

Ongoing advisory work includes monitoring IASB developments on IFRS crypto assets, updating clients when ASC 350-60 scope interpretations shift, and ensuring DAC8 and CARF reporting deadlines are tracked and met. Firms that treat these as distinct engagements rather than bundled into a standard accounts preparation fee will find the revenue profile considerably more attractive. Crypto clients with complex holdings are also more likely to generate referrals within their networks, which tend to be crypto-heavy by nature.

Illustrative Scenario

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

Thomas is a senior manager at a mid-sized accounting firm in Lisbon with a growing book of fintech and crypto clients. One of his clients, a Portuguese-registered crypto exchange, received a letter from the tax authority asking for clarification on its DAC8 reporting obligations. The client had assumed that because it was a smaller platform, the requirements did not apply to it. Thomas quickly established that the client did qualify as a reporting entity and that the first reporting period had already begun.

Separately, Thomas had a corporate treasury client holding Bitcoin and Ether on its balance sheet and reporting under IFRS. The client's CFO had read about the FASB ASC 350-60 changes in a trade publication and was asking whether the same rules applied to them. Thomas was able to explain clearly that IFRS crypto assets are still measured under IAS 38 for their entity type, but that the IASB project was worth monitoring, and that adopting the revaluation model under IAS 38 was worth assessing given current market conditions.

Using CryptaCount, Thomas was able to pull transaction data from the exchange client's platform, map it to the DAC8 reporting template, and flag the relevant fields for review. The corporate treasury client's holdings were reconciled against exchange data automatically, saving several hours of manual work at year-end.

Frequently Asked Questions

What is DAC8 reporting and who does it apply to?

DAC8 is an EU directive requiring crypto-asset service providers operating in EU member states to collect and report user transaction data to their local tax authority. The data is then shared automatically with other EU member state authorities. It applies to exchanges, brokers, and certain other service providers, regardless of the size of the platform, if they meet the definition of a reporting entity under the directive.

How does CARF crypto reporting differ from DAC8?

CARF is the OECD's global framework for crypto-asset reporting, designed for cross-border data exchange between countries outside the EU as well as between OECD members more broadly. DAC8 covers intra-EU exchanges. The two frameworks were deliberately aligned so that firms operating in both contexts do not face entirely different data requirements, but the filing procedures and timelines vary by jurisdiction.

What does ASC 350-60 change for US entities holding crypto?

Under ASC 350-60, qualifying crypto assets must be measured at fair value at each reporting date, with gains and losses recognised in net income. Previously, entities held most crypto at cost less impairment, meaning unrealised gains were never shown in the income statement. This change increases income statement volatility and adds complexity to the audit process, particularly around fair value sourcing and documentation.

How are crypto assets currently treated under IFRS?

Under IFRS, most crypto assets are accounted for as intangible assets under IAS 38. Entities can choose between the cost model and the revaluation model, but the revaluation model is only available where an active market exists. Commodity broker-dealers may use IAS 2 and measure at fair value less costs to sell. The IASB is working on a dedicated standard, but no final guidance has been issued yet.

Is FASB crypto fair value treatment the same as IFRS treatment?

No. FASB ASC 350-60 requires fair value through net income for qualifying assets, which is a mandatory treatment for in-scope assets under US GAAP. IFRS does not currently require fair value measurement for most crypto asset holders. This creates a material difference in reported earnings between US GAAP and IFRS entities holding the same assets, which is particularly relevant for multinational groups preparing consolidated accounts.

Do Portuguese companies need to comply with DAC8 reporting?

Yes, if they qualify as a crypto-asset service provider under the directive. Portugal transposed DAC8 in line with the EU implementation schedule, so service providers operating from Portugal are subject to the same obligations as those in other member states. Accounting firms advising Portuguese crypto businesses should confirm whether each client meets the reporting entity definition and establish the relevant data collection and filing process.

What is the relationship between MiCA and DAC8 for accounting purposes?

MiCA is the EU's crypto-asset markets regulation, governing licensing and operational requirements for crypto-asset service providers. DAC8 uses MiCA's definitions to determine which entities and asset types fall within its reporting scope. For accounting firms, this means a client's MiCA status is directly relevant to its DAC8 obligations. Firms should be checking both frameworks together when onboarding crypto-active clients in the EU.

How should accounting firms manage crypto clients across multiple reporting frameworks?

The most practical approach is to build a structured onboarding intake that captures each client's jurisdictions, asset types, regulatory status, and applicable accounting standard. This feeds into a compliance calendar that tracks DAC8 and CARF deadlines separately from financial statement deadlines. Purpose-built crypto accounting software that reconciles exchange data and maps it to the relevant reporting framework reduces manual error and allows firms to scale their crypto practice without a proportional increase in staff time.

When will CARF crypto reporting first exchanges occur?

The OECD has scheduled the first automatic exchanges under CARF for 2027 among early-adopting jurisdictions, though individual countries may implement domestic reporting requirements on different timelines ahead of that date. Firms with clients in OECD member countries should monitor local transposition announcements, as some jurisdictions are moving faster than the baseline OECD schedule.

Source: CryptaCount