Crypto Financial Reporting Standards: IFRS, US GAAP, DAC8 and CARF Explained
Crypto financial reporting has moved from an afterthought into a central compliance challenge for accounting firms, corporate finance teams, and auditors worldwide. The frameworks governing how digital assets are measured, disclosed, and reported to tax authorities are no longer confined to a single jurisdiction or standard-setter. Today, firms must navigate IFRS crypto assets guidance, US GAAP rules under ASC 350-60, OECD-driven CARF crypto reporting, and the European Union's DAC8 reporting regime, often simultaneously. Getting this wrong carries real consequences: audit qualifications, regulatory penalties, and reputational damage. This article sets out what each framework requires, where they overlap, and how accounting firms can build a practice that stays ahead of all of them.
Why Crypto Financial Reporting Has Become So Complex
Three forces have converged to make crypto financial reporting genuinely difficult. First, digital assets do not map neatly onto the asset categories that existing accounting standards were designed for. A stablecoin, a governance token, and a wrapped bitcoin are legally and economically distinct, yet all three arrive on a balance sheet demanding classification. Second, standard-setters in different jurisdictions have responded at different speeds, producing a patchwork of rules that a multinational firm or a client with cross-border holdings must reconcile. Third, tax reporting obligations have accelerated through mechanisms like CARF and DAC8 that impose data-collection and exchange requirements on a wide range of intermediaries, including some that did not previously regard themselves as reporting entities at all.
For accounting firms, the practical consequence is that a single client relationship may now require expertise in IFRS crypto assets treatment, familiarity with US GAAP fair value elections, an understanding of CARF's definition of a Crypto-Asset Service Provider, and knowledge of how DAC8 reporting rules apply to EU-based exchanges and custodians. These are not interchangeable. Each framework has its own scope, measurement basis, disclosure requirements, and deadlines.
IFRS Crypto Assets: Classification and Measurement
The International Accounting Standards Board has not yet issued a dedicated IFRS standard for crypto assets, which means firms applying IFRS must work through existing standards using judgment. The IFRS Interpretations Committee confirmed in 2019 that most cryptocurrencies do not meet the definition of cash or a financial instrument under IAS 32, and that they should generally be accounted for either as intangible assets under IAS 38 or as inventory under IAS 2 when held for sale in the ordinary course of business.
Under IAS 38, intangible assets are measured at cost on initial recognition. Subsequently, an entity may apply the revaluation model only if an active market exists for the asset, which is a threshold that not all crypto assets meet. Where the revaluation model is permitted, increases in carrying amount go to other comprehensive income rather than profit or loss, while decreases are charged to the income statement unless a revaluation surplus exists. Impairment must also be assessed under IAS 36, and write-downs cannot be reversed under the cost model. This asymmetric treatment, gains deferred but losses recognised immediately, has significant implications for how crypto holdings are presented to investors and lenders.
The table below summarises the key measurement outcomes under each IFRS model.
| IFRS Model | Initial Measurement | Subsequent Measurement | Gains to P&L? | Impairment Reversals? |
|---|---|---|---|---|
| IAS 38 Cost Model | Cost | Cost less accumulated amortisation and impairment | No | No |
| IAS 38 Revaluation Model | Cost | Fair value (if active market exists) | Via OCI only | Up to revaluation surplus |
| IAS 2 Inventory | Cost | Lower of cost and net realisable value | No (NRV write-down only) | Yes, up to original cost |
ASC 350-60 and FASB Crypto Fair Value Under US GAAP
The Financial Accounting Standards Board took a more decisive step in 2023 when it finalised ASC 350-60, a dedicated subtopic for certain crypto assets within the broader intangible assets standard. This was a meaningful departure from prior US GAAP practice, where most entities accounted for crypto holdings at cost less impairment with no ability to write back gains once prices recovered.
Under ASC 350-60, entities that hold crypto assets meeting specific criteria must measure those assets at fair value at each reporting date, with changes recognised in net income. The FASB crypto fair value requirement applies to assets that are fungible, created or residing on a blockchain or distributed ledger, and secured through cryptography, among other conditions. Assets that represent ownership of another asset, such as certain tokenised securities, fall outside the scope. Enhanced disclosures are also required, including a rollforward of crypto asset activity and information about significant holdings.
The practical effect is that US GAAP reporters with qualifying crypto holdings now face more volatile income statements but a balance sheet that more accurately reflects current market values. Firms advising US corporate clients, or clients preparing US GAAP financial statements for any reason, need to understand the scope criteria carefully before applying the standard.
| Framework | Standard | Measurement Basis | Gains in Net Income? | Effective For |
|---|---|---|---|---|
| US GAAP | ASC 350-60 | Fair value through net income | Yes | Fiscal years beginning after 15 December 2024 |
| IFRS | IAS 38 / IAS 2 | Cost or revaluation (IAS 38); NRV (IAS 2) | Limited | Ongoing, pending dedicated IFRS standard |
CARF Crypto Reporting: The OECD Framework for Tax Authorities
The Crypto-Asset Reporting Framework, known as CARF, was developed by the OECD to close the gap that crypto assets had created in the automatic exchange of financial account information. Under the Common Reporting Standard, banks and financial institutions report account information to tax authorities, who then share it across borders. Crypto assets largely fell outside that system. CARF is designed to bring them in.
CARF requires Reporting Crypto-Asset Service Providers to collect and report information on their clients' crypto transactions. The scope covers exchanges, brokers, dealers, and certain wallet providers. The data collected includes the client's identifying information, the type and value of assets transacted, and whether transactions involved the transfer of crypto assets to or from external accounts. That information is then exchanged with the tax authorities of the relevant jurisdictions, mirroring how CRS operates for traditional financial accounts.
For accounting firms, CARF matters in two ways. Clients who operate crypto exchanges or custody services may themselves be Reporting Crypto-Asset Service Providers with direct obligations. And clients who are individual or corporate investors will find that their transaction data is increasingly visible to their home tax authority, making accurate self-reporting more important and more easily verified than before. Firms providing crypto us gaap accounting or IFRS advisory services should understand how CARF data interacts with the figures their clients are reporting on financial statements.
DAC8 Reporting: The EU's Domestic Implementation of CARF
DAC8 is the European Union's mechanism for implementing CARF principles within the EU's existing administrative cooperation framework. Adopted in 2023, DAC8 amends the Directive on Administrative Cooperation to require crypto-asset service providers operating in the EU, as authorised or registered under MiCA, to collect and report client transaction data to the tax authorities of their member state of registration. That data is then shared automatically across all EU member states.
DAC8 reporting obligations are not identical to CARF in every detail, but the underlying logic is the same: create a trail of transaction data that tax authorities can match against filed returns. The reporting covers transfers, exchanges, and consideration received in the course of crypto asset services. Service providers must carry out due diligence on their reportable users, following procedures that echo the CRS due diligence rules adapted for a crypto context.
For firms with EU-based clients, particularly those in financial centres with significant crypto activity, DAC8 represents a hard operational deadline rather than a future aspiration. Crypto-asset service providers that have not built compliant data collection and reporting workflows face enforcement risk. Advisers who help those clients understand and implement DAC8 can develop a significant new advisory revenue stream. Detailed guidance on building those workflows is available through our crypto compliance reporting for accounting firms resources.
| Framework | Originator | Geographic Scope | Who Reports | Data Exchanged With |
|---|---|---|---|---|
| CARF | OECD | Adopting jurisdictions globally | Reporting Crypto-Asset Service Providers | Partner tax authorities |
| DAC8 | European Union | EU member states | MiCA-authorised or registered CASPs | All EU member state tax authorities |
How the Frameworks Interact in Practice
A client that operates a crypto exchange authorised under MiCA, holds treasury crypto assets on its own balance sheet, and has investors in multiple jurisdictions may face all four frameworks at once. DAC8 reporting governs its obligations as a service provider to EU users. CARF governs equivalent obligations in non-EU adopting jurisdictions. Its balance sheet treatment depends on whether it reports under IFRS crypto assets rules or ASC 350-60. And its auditors need to opine on fair value disclosures that are themselves shaped by whichever measurement model applies.
Accounting firms that serve this kind of client need a coordinated approach. The financial reporting team cannot ignore what the tax compliance team is doing, and vice versa. Discrepancies between reported transaction volumes in CARF filings and the figures used to value assets on the balance sheet will attract scrutiny. Consistent data is not only good practice; it is a prerequisite for withstanding the kind of cross-referencing that CARF and DAC8 are specifically designed to enable.
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 audit clients is a fintech company that launched a crypto exchange for retail users in 2023. The firm has grown quickly and obtained MiCA registration through an EU subsidiary. Priya's team faces three simultaneous challenges heading into the year-end audit: classifying the company's own treasury holdings of bitcoin and ether under IAS 38, reviewing whether the subsidiary's DAC8 reporting workflows are sufficiently documented to withstand regulatory scrutiny, and advising the CFO on how the transition to fair value measurement under ASC 350-60 would affect the US GAAP reconciliation in the group accounts.
Priya's firm had previously handled each of these as separate workstreams, but the overlap in source data made that inefficient and introduced reconciliation errors. By adopting CryptaCount, the team was able to pull consistent transaction-level data into both the financial reporting and the DAC8 compliance workflows from a single source, reducing the risk of discrepancies and cutting the time spent on manual reconciliation significantly. The audit went ahead without qualification on the crypto disclosures, and the firm identified an additional advisory opportunity in helping the client prepare for CARF obligations in non-EU jurisdictions where it was expanding.
Frequently Asked Questions
What is DAC8 reporting and who does it apply to?
DAC8 is an EU directive that requires crypto-asset service providers registered or authorised under MiCA to collect and report client transaction data to their home member state's tax authority. That data is then shared automatically across all EU member states. It mirrors the logic of the OECD's CARF framework but operates within the EU's existing administrative cooperation system.
How are crypto assets treated under IFRS?
Under current IFRS, most crypto assets are classified as intangible assets under IAS 38 or as inventory under IAS 2 when held for sale in the ordinary course of business. The IASB has not yet issued a dedicated standard. Classification depends on the nature of the asset and how the entity holds it, which requires professional judgment and documentation.
What does ASC 350-60 require for 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 recognised directly in net income. This replaced the older cost-less-impairment approach under US GAAP and results in a more volatile income statement but a balance sheet that reflects current market prices more accurately.
What is FASB crypto fair value and when does it apply?
FASB crypto fair value refers to the measurement approach mandated by ASC 350-60 for crypto assets meeting the standard's scope criteria. The requirement became effective for fiscal years beginning after 15 December 2024. Assets that represent ownership interests in other assets, such as certain tokenised securities, fall outside the scope of ASC 350-60.
How does CARF crypto reporting differ from DAC8?
CARF is an OECD model framework that participating jurisdictions adopt into domestic law. DAC8 is the EU's specific implementation within its administrative cooperation directive. The scope and definitions are broadly aligned, but DAC8 is legally binding on EU member states while CARF adoption elsewhere depends on each jurisdiction's own legislative process and timetable.
Does IFRS crypto accounting require fair value measurement?
Not as a default. Under IAS 38, the revaluation model, which uses fair value, is only available if an active market exists for the crypto asset. Many entities use the cost model instead, which does not allow upward revaluation. The result is an asymmetric treatment where impairment losses are recognised immediately but gains are deferred or excluded from the income statement entirely.
Which accounting firms need to understand these frameworks?
Any firm that audits, advises, or prepares financial statements for clients holding crypto assets or operating as crypto-asset service providers needs working knowledge of these frameworks. This includes firms with clients in the EU facing DAC8, clients in CARF-adopting jurisdictions, and any client group preparing either IFRS or US GAAP financial statements with crypto on the balance sheet.
How should accounting firms prepare clients for CARF and DAC8 compliance?
Preparation starts with identifying whether the client qualifies as a Reporting Crypto-Asset Service Provider under either framework. If it does, the firm should review the client's due diligence procedures, data collection infrastructure, and reporting workflows against the relevant rules. Where gaps exist, remediation planning should begin well in advance of reporting deadlines, as building compliant data pipelines from scratch takes time.
Can the same transaction data be used for both financial reporting and CARF or DAC8 reporting?
Yes, and consistency between the two is strongly advisable. Discrepancies between transaction volumes reported under CARF or DAC8 and the figures used to value assets on an audited balance sheet will attract scrutiny from both tax authorities and auditors. A single authoritative data source that feeds both workstreams reduces reconciliation risk and simplifies the audit process.
What is the relationship between MiCA and DAC8 reporting obligations?
MiCA is the EU regulation that authorises and regulates crypto-asset service providers operating in the EU. DAC8 uses MiCA's authorisation and registration regime as the trigger for reporting obligations: if an entity is authorised or registered as a CASP under MiCA, it falls within the scope of DAC8. The two frameworks are therefore closely linked, and compliance with MiCA does not by itself satisfy DAC8 obligations.
Source: CryptaCount
FAQ
DAC8 is an EU directive that requires crypto-asset service providers registered or authorised under MiCA to collect and report client transaction data to their home member state's tax authority. That data is then shared automatically across all EU member states. It mirrors the logic of the OECD's CARF framework but operates within the EU's existing administrative cooperation system.
Under current IFRS, most crypto assets are classified as intangible assets under IAS 38 or as inventory under IAS 2 when held for sale in the ordinary course of business. The IASB has not yet issued a dedicated standard. Classification depends on the nature of the asset and how the entity holds it, which requires professional judgment and documentation.
ASC 350-60 requires entities holding qualifying crypto assets to measure them at fair value at each reporting date, with changes recognised directly in net income. This replaced the older cost-less-impairment approach under US GAAP and results in a more volatile income statement but a balance sheet that reflects current market prices more accurately.
FASB crypto fair value refers to the measurement approach mandated by ASC 350-60 for crypto assets meeting the standard's scope criteria. The requirement became effective for fiscal years beginning after 15 December 2024. Assets that represent ownership interests in other assets, such as certain tokenised securities, fall outside the scope of ASC 350-60.
CARF is an OECD model framework that participating jurisdictions adopt into domestic law. DAC8 is the EU's specific implementation within its administrative cooperation directive. The scope and definitions are broadly aligned, but DAC8 is legally binding on EU member states while CARF adoption elsewhere depends on each jurisdiction's own legislative process and timetable.
Not as a default. Under IAS 38, the revaluation model, which uses fair value, is only available if an active market exists for the crypto asset. Many entities use the cost model instead, which does not allow upward revaluation. The result is an asymmetric treatment where impairment losses are recognised immediately but gains are deferred or excluded from the income statement entirely.
Any firm that audits, advises, or prepares financial statements for clients holding crypto assets or operating as crypto-asset service providers needs working knowledge of these frameworks. This includes firms with clients in the EU facing DAC8, clients in CARF-adopting jurisdictions, and any client group preparing either IFRS or US GAAP financial statements with crypto on the balance sheet.
Preparation starts with identifying whether the client qualifies as a Reporting Crypto-Asset Service Provider under either framework. If it does, the firm should review the client's due diligence procedures, data collection infrastructure, and reporting workflows against the relevant rules. Where gaps exist, remediation planning should begin well in advance of reporting deadlines, as building compliant data pipelines from scratch takes time.
Yes, and consistency between the two is strongly advisable. Discrepancies between transaction volumes reported under CARF or DAC8 and the figures used to value assets on an audited balance sheet will attract scrutiny from both tax authorities and auditors. A single authoritative data source that feeds both workstreams reduces reconciliation risk and simplifies the audit process.
MiCA is the EU regulation that authorises and regulates crypto-asset service providers operating in the EU. DAC8 uses MiCA's authorisation and registration regime as the trigger for reporting obligations: if an entity is authorised or registered as a CASP under MiCA, it falls within the scope of DAC8. The two frameworks are therefore closely linked, and compliance with MiCA does not by itself satisfy DAC8 obligations.