DAC8 Reporting and Global Crypto Financial Reporting Standards Explained
Crypto financial reporting has moved from a niche concern to a core compliance obligation. Accounting firms advising clients who hold, trade, or issue digital assets now face a layered set of demands: standards-based accounting under IFRS or US GAAP, automatic tax information exchange through DAC8 reporting and CARF crypto reporting, and jurisdiction-specific disclosure rules that continue to evolve. For finance teams, the challenge is not simply knowing that these frameworks exist. It is understanding which ones apply simultaneously, how they interact, and what records must be in place before an auditor or tax authority asks. This article sets out the principal frameworks, how they differ, and what accounting professionals need to do now to keep clients compliant across multiple jurisdictions.
Why Crypto Reporting Has Become a Multi-Framework Problem
A mid-sized UK business holding bitcoin on its balance sheet is not subject to one reporting rule. It is potentially subject to several at once. IFRS sets the accounting treatment. HMRC's self-assessment regime governs UK tax. DAC8 reporting, which applies across EU member states, requires crypto-asset service providers to collect and report client transaction data automatically. CARF crypto reporting, developed by the OECD, extends a similar automatic exchange mechanism to over 50 participating countries. The US adds a further layer: any entity with US counterparties or US tax obligations must consider ASC 350-60 crypto rules under US GAAP.
The practical consequence is that a single transaction, say a corporate treasury swap from fiat to stablecoin, may need to be recorded under IFRS crypto assets rules, disclosed under CARF to the relevant tax authority, and potentially reported under DAC8 if the service provider is EU-based. Firms that treat these as separate workstreams rather than a unified compliance obligation tend to create gaps. Those gaps become audit findings.
The table below summarises the four major frameworks and the entities they primarily affect.
| Framework | Governing Body | Primary Scope | Applies To |
|---|---|---|---|
| IFRS (IAS 38 / IAS 2) | IASB | Balance sheet classification and measurement | IFRS-reporting entities globally |
| ASC 350-60 (US GAAP) | FASB | Fair value measurement of crypto assets | US GAAP reporters holding qualifying crypto |
| DAC8 | European Commission | Automatic exchange of crypto transaction data | CASPs operating in or serving EU residents |
| CARF | OECD | Global automatic exchange of crypto tax data | Reporting crypto-asset service providers in participating jurisdictions |
IFRS Crypto Assets: How UK and Global Firms Account for Digital Holdings
The IASB has not issued a dedicated IFRS standard for crypto assets. Instead, existing standards apply by analogy. Crypto assets held as inventory are measured under IAS 2. Those held for capital appreciation or as treasury assets typically fall under IAS 38 as intangible assets, measured at cost less impairment unless the entity elects the revaluation model, which requires an active market. Neither model permits upward revaluation to fair value through profit and loss in the way many finance teams expect.
This creates a presentation problem. A company that bought bitcoin at a lower price than its current market value cannot recognise that gain on the income statement under IAS 38 unless it qualifies for and applies the revaluation model. The gain sits off the income statement in other comprehensive income. For clients whose stakeholders expect to see crypto gains reflected in earnings, this is a conversation that needs to happen early in the reporting cycle, not at audit fieldwork.
For crypto ifrs accounting in practice, the classification decision is made at initial recognition and drives every subsequent measurement. Firms advising clients on this should document the classification rationale contemporaneously, because auditors will scrutinise it and a post-hoc reclassification is difficult to defend.
ASC 350-60 Crypto and FASB Crypto Fair Value Under US GAAP
The FASB took a different path. Its ASC 350-60 crypto standard, effective for fiscal years beginning after 15 December 2024 for calendar-year entities, requires entities to measure certain crypto assets at fair value through net income each reporting period. This is a significant departure from the previous indefinite-lived intangible asset model, which required impairment testing but did not allow upward adjustments.
Under ASC 350-60, qualifying crypto assets, defined broadly as fungible assets secured through cryptography and residing on a blockchain, are remeasured at fair value at each balance sheet date. Gains and losses flow through the income statement. The standard also requires specific tabular disclosures: the name, cost basis, fair value, and number of units held for each significant crypto asset holding.
For firms with US-listed clients or clients preparing US GAAP financial statements, FASB crypto fair value treatment represents a material change in how balance sheet volatility is reported. The table below compares the IFRS and US GAAP approaches side by side.
| Characteristic | IFRS (IAS 38 default) | US GAAP (ASC 350-60) |
|---|---|---|
| Measurement basis | Cost less impairment (revaluation model optional) | Fair value at each reporting date |
| Upward revaluation through P&L | Not permitted under cost model | Required |
| Impairment testing | Required under cost model | Not applicable; fair value replaces impairment |
| Disclosure requirements | General IFRS disclosure principles | Specific tabular disclosure by asset required |
| Income statement impact | Gains recognised in OCI under revaluation model | All fair value movements through net income |
DAC8 Reporting: What Accounting Firms Need to Know
DAC8 reporting is the EU's mechanism for bringing crypto-asset transactions into the automatic exchange of information regime that already covers bank accounts, dividends, and other financial instruments. Under DAC8, crypto-asset service providers (CASPs) operating in the EU, or providing services to EU-resident clients, must collect identifying information on users and report transaction data to the relevant national tax authority. That authority then shares the data automatically with the tax authority of the user's country of residence.
For accounting firms, DAC8 has two distinct implications. First, if a firm's client is a CASP, that client has direct reporting obligations and needs help building the data collection and reporting infrastructure. Second, if a client is a retail or institutional crypto user, DAC8 means that their transactions are now visible to HMRC, the German Bundeszentralamt für Steuern, or whichever authority is relevant. The era of assuming crypto activity was invisible to tax authorities has ended.
The data collected under DAC8 includes the full name, address, tax identification number, and date of birth of each reportable user, alongside aggregate transaction values by asset type. The reporting is annual. Firms advising clients on crypto compliance reporting for accounting firms should treat DAC8 as an ongoing data governance question, not a one-time filing project.
CARF Crypto Reporting: The OECD's Global Extension
The CARF, or Crypto-Asset Reporting Framework, is the OECD's answer to the same problem that DAC8 addresses in the EU, but with a broader geographic reach. CARF creates a standardised template for the automatic exchange of crypto transaction information between tax authorities in participating jurisdictions. Over 50 countries have committed to implementing CARF, with exchanges expected to begin for many in 2027.
CARF crypto reporting covers a wider set of crypto assets than DAC8 in some respects, including certain stablecoins and some tokenised derivatives. It applies to reporting crypto-asset service providers, defined similarly to CASPs under MiCA, who must collect due diligence information and report aggregated transaction data annually. The OECD designed CARF to sit alongside the Common Reporting Standard, meaning firms already familiar with CRS obligations will find the structure familiar even if the asset classes are new.
For UK-based accounting firms, CARF is particularly relevant because the UK has committed to implementation. HMRC will receive CARF data from partner jurisdictions covering UK-resident clients who use non-UK exchanges, closing the gap that previously allowed offshore crypto activity to go unreported.
Crypto US GAAP Accounting for UK-Linked Entities
The question of which accounting standard applies is not always straightforward for UK entities with US connections. A UK subsidiary of a US parent will typically consolidate into US GAAP financial statements. A UK company listed on a US exchange, or seeking US investment, may prepare or reconcile to crypto us gaap accounting requirements. In those cases, the ASC 350-60 fair value model applies even though the entity is domiciled in the UK.
The practical implication is that some UK finance teams must maintain dual accounting records or prepare reconciliations between IFRS and US GAAP treatment for the same crypto holdings. The difference in measurement basis can be substantial. An entity holding a large bitcoin position will show different earnings figures under each standard, which has implications for covenant compliance, executive compensation tied to earnings, and investor communications.
Firms advising on this intersection should build reconciliation processes into the monthly close, not treat them as a year-end adjustment. The more volatile the holdings, the more material the difference between IFRS and ASC 350-60 outcomes is likely to be.
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. One of her clients, a fintech company with around 80 employees, holds a mix of bitcoin and stablecoins on its treasury balance sheet and operates a small exchange facility for EU-based customers. In preparing the client's year-end accounts, Priya identifies three simultaneous obligations. Under IFRS crypto assets rules, she must confirm the classification of each holding, document the active market assessment for revaluation eligibility, and test for impairment under IAS 38 where the cost model applies. Because the client's exchange facility serves EU residents, it qualifies as a CASP under DAC8, which means an annual DAC8 reporting obligation to HMRC covering EU-resident users. And because the UK has committed to CARF, Priya's client will also need CARF-compatible data collection in place ahead of the first CARF exchange cycle.
Priya uses CryptaCount to centralise the client's transaction data, map each holding to the correct accounting treatment, and generate the structured reports needed for both DAC8 and CARF submissions. What would have been three separate workstreams managed in spreadsheets becomes a single audit-ready workflow, with every classification decision documented and every reportable transaction captured.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive requiring crypto-asset service providers to collect user data and report transaction information to national tax authorities, which then share it automatically across EU member states. It applies to CASPs operating within the EU or providing services to EU-resident clients. Firms with clients in either category have direct compliance obligations to address.
How does IFRS treat crypto assets on the balance sheet?
Under current IFRS, most crypto assets are classified as intangible assets under IAS 38 or as inventory under IAS 2. The IAS 38 cost model restricts upward revaluation through profit and loss, meaning unrealised gains may not appear in earnings unless the revaluation model applies and an active market exists. For crypto ifrs accounting purposes, the classification decision made at initial recognition determines measurement for the life of the holding.
What changed under ASC 350-60 for US GAAP reporters?
The FASB's ASC 350-60 standard requires entities to measure qualifying crypto assets at fair value at each balance sheet date, with all movements recognised in net income. This replaced the previous approach of treating crypto as indefinite-lived intangibles subject to impairment testing only. The change means crypto holdings now introduce direct income statement volatility for US GAAP reporters.
How is CARF different from DAC8?
DAC8 operates within the EU and covers EU-resident users of CASPs. CARF is an OECD framework designed for global automatic exchange of crypto tax information between participating jurisdictions, of which over 50 have signed up. CARF crypto reporting uses a standardised template aligned with the Common Reporting Standard and has a broader asset scope in some areas. Both frameworks are moving toward simultaneous implementation in many jurisdictions.
Does DAC8 affect UK accounting firms after Brexit?
UK-based CASPs serving EU-resident clients remain within DAC8's scope because the obligation is triggered by the location of the user, not only the provider. HMRC will also receive DAC8 data from EU authorities covering UK-resident clients who use EU-based exchanges. The UK has additionally committed to CARF, meaning UK firms face both inbound data from partner jurisdictions and outbound reporting obligations.
Can a UK entity need to apply both IFRS and ASC 350-60?
Yes. A UK subsidiary consolidating into a US parent's financial statements, or a UK entity preparing US GAAP reconciliations for US investors, may need to apply ASC 350-60 alongside IFRS. The two standards produce different outcomes: IFRS under the cost model restricts upward revaluation, while ASC 350-60 mandates fair value through net income. Firms should build reconciliation into the monthly close rather than treating it as a year-end task.
What records does a CASP need to keep for DAC8 compliance?
Under DAC8, CASPs must collect and retain the full legal name, address, tax identification number, date of birth, and country of residence for each reportable user, alongside annual aggregate transaction values by crypto-asset type. These records must be sufficient to support the annual report filed with the national competent authority. Firms advising CASPs should assess current data collection processes against these requirements before the first reporting deadline.
How should accounting firms prepare clients for CARF?
The first step is identifying which clients qualify as reporting crypto-asset service providers under CARF's definitions, which are broader than many expect. Firms should then assess whether existing KYC and AML data collection captures the fields CARF requires, and whether transaction records are stored in a format that allows aggregation by asset type and user. Building this infrastructure early avoids a last-minute scramble when the first exchange cycle approaches.
Is FASB crypto fair value treatment mandatory for all US GAAP entities holding crypto?
ASC 350-60 applies to in-scope crypto assets, defined as fungible, intangible assets secured through cryptography that reside on a distributed ledger. Not all digital assets meet this definition; some may fall under other GAAP guidance. Entities should assess each holding individually to determine whether it qualifies, and document that assessment as part of their accounting policy disclosure.
Where can accounting firms get practical support managing multi-framework crypto compliance?
Firms handling clients with crypto holdings across multiple frameworks benefit from software that centralises transaction data, maps holdings to the correct accounting treatment under both IFRS and US GAAP, and generates structured reports for DAC8 and CARF submissions. Handling each framework in a separate spreadsheet creates duplication and audit risk. Integrated crypto compliance reporting for accounting firms reduces both.
Source: CryptaCount
FAQ
DAC8 is an EU directive requiring crypto-asset service providers to collect user data and report transaction information to national tax authorities, which then share it automatically across EU member states. It applies to CASPs operating within the EU or providing services to EU-resident clients. Firms with clients in either category have direct compliance obligations to address.
Under current IFRS, most crypto assets are classified as intangible assets under IAS 38 or as inventory under IAS 2. The IAS 38 cost model restricts upward revaluation through profit and loss, meaning unrealised gains may not appear in earnings unless the revaluation model applies and an active market exists. For crypto ifrs accounting purposes, the classification decision made at initial recognition determines measurement for the life of the holding.
The FASB's ASC 350-60 standard requires entities to measure qualifying crypto assets at fair value at each balance sheet date, with all movements recognised in net income. This replaced the previous approach of treating crypto as indefinite-lived intangibles subject to impairment testing only. The change means crypto holdings now introduce direct income statement volatility for US GAAP reporters.
DAC8 operates within the EU and covers EU-resident users of CASPs. CARF is an OECD framework designed for global automatic exchange of crypto tax information between participating jurisdictions, of which over 50 have signed up. CARF crypto reporting uses a standardised template aligned with the Common Reporting Standard and has a broader asset scope in some areas. Both frameworks are moving toward simultaneous implementation in many jurisdictions.
UK-based CASPs serving EU-resident clients remain within DAC8's scope because the obligation is triggered by the location of the user, not only the provider. HMRC will also receive DAC8 data from EU authorities covering UK-resident clients who use EU-based exchanges. The UK has additionally committed to CARF, meaning UK firms face both inbound data from partner jurisdictions and outbound reporting obligations.
Yes. A UK subsidiary consolidating into a US parent's financial statements, or a UK entity preparing US GAAP reconciliations for US investors, may need to apply ASC 350-60 alongside IFRS. The two standards produce different outcomes: IFRS under the cost model restricts upward revaluation, while ASC 350-60 mandates fair value through net income. Firms should build reconciliation into the monthly close rather than treating it as a year-end task.
Under DAC8, CASPs must collect and retain the full legal name, address, tax identification number, date of birth, and country of residence for each reportable user, alongside annual aggregate transaction values by crypto-asset type. These records must be sufficient to support the annual report filed with the national competent authority. Firms advising CASPs should assess current data collection processes against these requirements before the first reporting deadline.
The first step is identifying which clients qualify as reporting crypto-asset service providers under CARF's definitions, which are broader than many expect. Firms should then assess whether existing KYC and AML data collection captures the fields CARF requires, and whether transaction records are stored in a format that allows aggregation by asset type and user. Building this infrastructure early avoids a last-minute scramble when the first exchange cycle approaches.
ASC 350-60 applies to in-scope crypto assets, defined as fungible, intangible assets secured through cryptography that reside on a distributed ledger. Not all digital assets meet this definition; some may fall under other GAAP guidance. Entities should assess each holding individually to determine whether it qualifies, and document that assessment as part of their accounting policy disclosure.
Firms handling clients with crypto holdings across multiple frameworks benefit from software that centralises transaction data, maps holdings to the correct accounting treatment under both IFRS and US GAAP, and generates structured reports for DAC8 and CARF submissions. Handling each framework in a separate spreadsheet creates duplication and audit risk. Integrated crypto compliance reporting for accounting firms reduces both.