Crypto Financial Reporting Standards: US GAAP, IFRS, and DAC8 Reporting Explained

Crypto financial reporting has moved from a niche concern to a core obligation for accounting firms, CFOs, and finance teams worldwide. In the United States, the Financial Accounting Standards Board finalised new guidance that fundamentally changes how companies measure and report digital assets on their balance sheets. At the same time, international frameworks including IFRS, the OECD's Crypto-Asset Reporting Framework, and the European Union's DAC8 reporting regime are reshaping disclosure requirements far beyond US borders. For any firm with clients holding crypto, or any finance team managing digital assets directly, understanding where these standards align and where they diverge is no longer optional. The cost of getting it wrong ranges from restated financials to regulatory penalties, and the complexity is only increasing as asset classes multiply and jurisdictions harden their positions.

Why Crypto Accounting Standards Needed an Overhaul

Before the latest US GAAP updates, companies holding cryptocurrencies were forced to treat them as indefinite-lived intangible assets under existing guidance. That meant recording the asset at historical cost and writing it down whenever the fair value fell below that cost, but never writing it back up when prices recovered. The result was a profoundly distorted picture of a company's financial position. A firm that bought Bitcoin at a low price and held it through a market cycle could show an asset on its balance sheet worth a fraction of its current market value, with no mechanism to reflect the recovery. Auditors, investors, and analysts all recognised the absurdity, but the standards had not kept pace with the reality of how these assets behave.

The broader problem was one of fit. Intangible asset guidance was designed for things like patents and trademarks, assets with no active market and whose value is tied to proprietary rights. Cryptocurrencies traded on liquid exchanges behave more like financial instruments, with observable prices updated continuously. Applying an indefinite-lived intangible framework to them produced disclosures that misled rather than informed. Regulators and standard-setters eventually had to act, and the FASB's response arrived in the form of a dedicated subtopic that treats qualifying crypto assets as a distinct category requiring fair value measurement.

ASC 350-60 Crypto: What the FASB Rules Actually Require

The FASB's updated guidance, codified under ASC 350-60, requires entities to measure qualifying crypto assets at fair value at each reporting date, with changes recognised in net income. This is a significant departure from the previous impairment-only model and brings US GAAP treatment much closer to how these assets are economically experienced. For qualifying assets, the days of silent appreciation sitting off the income statement are over.

Not every digital asset falls within the scope of ASC 350-60. The guidance applies to assets that meet specific criteria: they must be intangible assets as defined under US GAAP, they must be created or reside on a distributed ledger, they must be secured through cryptography, they must be fungible, and the entity must not have created them. Non-fungible tokens, wrapped tokens in certain configurations, and assets issued by the reporting entity itself are outside the scope. The table below summarises the key eligibility criteria.

Criterion	Requirement Under ASC 350-60
Asset type	Intangible asset under US GAAP
Technology basis	Resides on a distributed ledger secured by cryptography
Fungibility	Must be fungible
Issuer	Not created or issued by the reporting entity
Measurement	Fair value at each reporting date, changes in net income

For accounting firms advising corporate clients, the practical implication is a need for robust fair value measurement processes. Level 1 inputs, meaning quoted prices on active exchanges, will apply for major cryptocurrencies. For less liquid assets, the valuation methodology requires careful documentation to satisfy audit scrutiny. Firms should also note the enhanced disclosure requirements: entities must disclose the cost basis of holdings, unrealised gains and losses recognised during the period, and the restrictions, if any, on the sale of assets.

Crypto US GAAP Accounting vs IFRS Crypto Assets: Key Differences

While ASC 350-60 brings US GAAP treatment closer to economic reality, the picture under IFRS is more fragmented. The International Accounting Standards Board has not issued a dedicated standard for crypto assets. Instead, preparers must apply existing standards by analogy, and the applicable standard depends on the nature of the asset and how the entity holds it. Most commonly, cryptocurrencies held as investments without a ready market fall under IAS 38 as intangible assets, while those held for sale in the ordinary course of business may qualify as inventory under IAS 2.

Under IAS 38, an entity can choose either the cost model or the revaluation model. The revaluation model permits carrying the asset at fair value, but only if an active market exists, and gains above historical cost go to other comprehensive income rather than profit or loss except to the extent they reverse a previously recognised impairment. Under IAS 2, inventory is measured at the lower of cost and net realisable value. Neither treatment fully mirrors the ASC 350-60 approach, which mandates fair value through profit or loss for qualifying assets. This divergence creates a genuine comparability challenge for multinational groups reporting under both frameworks.

Framework	Primary Standard Applied	Measurement Basis	Gains to Profit or Loss?
US GAAP (ASC 350-60)	Dedicated crypto subtopic	Fair value at each reporting date	Yes, fully
IFRS (IAS 38 cost model)	Intangible assets	Historical cost less impairment	No
IFRS (IAS 38 revaluation)	Intangible assets	Fair value, active market required	Only to reverse prior impairment
IFRS (IAS 2)	Inventories	Lower of cost and net realisable value	No

The IASB is aware that its existing guidance is an imperfect fit. An agenda decision from the IFRS Interpretations Committee confirmed that holdings of cryptocurrencies can qualify under IAS 38 or IAS 2 depending on circumstances, but that decision acknowledged the limitations without resolving them. Firms advising clients on crypto IFRS accounting should document the accounting policy selection carefully, apply it consistently, and monitor IASB project updates, as dedicated guidance may eventually emerge.

CARF Crypto Reporting: The OECD Framework Taking Shape Globally

The Organisation for Economic Co-operation and Development's Crypto-Asset Reporting Framework, known as CARF, represents the most significant change to international tax information exchange since the Common Reporting Standard. CARF establishes rules requiring crypto-asset service providers to collect and report user information to tax authorities, which then exchange that data automatically with other participating jurisdictions. The framework targets a reporting gap that has existed since crypto assets emerged: while traditional financial accounts have been subject to automatic exchange under CRS since 2017, crypto holdings sat largely outside that net.

CARF covers exchanges, wallet providers, and certain DeFi platforms that have sufficient control or involvement in transactions to be deemed reporting entities. The data points required include the user's identifying information, the type of crypto asset transacted, and the gross proceeds and fair market value of transactions. For accounting firms, CARF matters because it directly affects how clients' crypto activity will be visible to tax authorities. CARF crypto reporting obligations will require service providers to build data collection and reporting infrastructure, and advisers need to understand what data will flow to revenue authorities so they can help clients prepare accurate tax filings.

DAC8 Reporting: The EU's Crypto Tax Disclosure Regime

The European Union's Directive on Administrative Cooperation 8th Amendment, commonly called DAC8, is the EU's implementation of the OECD's CARF principles, extended to cover additional asset classes including e-money tokens and central bank digital currencies. DAC8 reporting obligations fall on crypto-asset service providers operating in the EU, requiring them to report transaction data on EU-resident users to their local tax authority, which then shares it across member states through the existing DAC infrastructure.

DAC8 is particularly relevant for firms with EU-based clients who use centralised exchanges or custody services. The data reported under DAC8 will flow directly to the tax authorities in the client's country of residence, making it essential that clients' self-reported crypto income matches the records held by their service providers. Discrepancies between reported figures and DAC8 data will attract scrutiny. For advisory firms, this creates both a risk management obligation and an opportunity: clients who understand what DAC8 reporting will reveal about their crypto activity are far more likely to engage professional help to get their filings right before the data arrives at the tax authority.

Framework	Jurisdiction	Who Reports	Primary Purpose
CARF	OECD member countries	Crypto-asset service providers	Automatic international tax data exchange
DAC8	European Union	CASPs operating in EU member states	EU-wide crypto transaction disclosure
ASC 350-60	United States	US GAAP reporting entities	Fair value financial statement presentation
IFRS (IAS 38 / IAS 2)	Global (IFRS adopters)	Entities preparing IFRS financial statements	Consistent balance sheet and income recognition

FASB Crypto Fair Value Disclosures and Audit Readiness

Adopting FASB crypto fair value measurement is not simply a policy choice that happens at the accounting software level. It requires firms to build or source reliable, auditable price feeds, establish a consistent methodology for determining fair value at the balance sheet date, and maintain records of how those valuations were derived. For audit clients with large or diverse crypto holdings, the documentation burden is substantial. Auditors will want to see the price source, the timestamp, the conversion methodology for assets not priced in the reporting currency, and evidence that the entity has applied the same approach consistently across periods.

Firms supporting audit clients should also be aware that the enhanced disclosure requirements under ASC 350-60 extend beyond the balance sheet value. Clients must disclose, at a minimum, the cost basis of their crypto holdings, the amount of unrealised gains and losses recognised during the period, and any restrictions on the ability to sell. For entities with staking income, lending arrangements, or assets held in custody with third parties, additional disclosures may be required. Building these disclosures into the year-end reporting process early, rather than retrofitting them after the fact, is the only practical way to meet audit timelines without errors. This is precisely where a dedicated crypto compliance reporting solution adds measurable value by centralising the data needed for both financial statement preparation and regulatory submission.

Illustrative Scenario

To illustrate how this applies in practice, consider the following scenario: Michael is the CFO of a mid-sized US technology company that began holding Bitcoin and Ethereum on its treasury balance sheet. Before the ASC 350-60 updates, the firm's auditors had required a write-down when prices fell, but there was no mechanism to recognise the subsequent recovery in earnings. Under the updated guidance, Michael's finance team now measures the crypto holdings at fair value at each quarter end, with movements recognised directly in net income. The first challenge was sourcing an auditable price feed: the team needed timestamped, exchange-sourced pricing that could withstand scrutiny from the external auditors. The second challenge was disclosure. The notes to the financial statements now required the cost basis of each position, the unrealised gains recognised during the year, and a description of any custody or transfer restrictions. Michael's team integrated CryptaCount to automate the fair value data pull, reconcile it against the sub-ledger, and generate the disclosure-ready output the auditors needed. The process that previously took two weeks of manual spreadsheet work was reduced to a structured, repeatable workflow completed in two days.

Frequently Asked Questions

What is ASC 350-60 and which crypto assets does it cover?

ASC 350-60 is the FASB subtopic that governs how US GAAP reporting entities account for qualifying crypto assets. It requires fair value measurement at each reporting date with changes recognised in net income. The scope covers fungible, cryptographically secured intangible assets on distributed ledgers that were not created by the reporting entity. NFTs, certain wrapped tokens, and self-issued assets are excluded.

How does crypto US GAAP accounting differ from IFRS crypto assets treatment?

Under ASC 350-60, qualifying crypto assets are measured at fair value through profit or loss at every reporting date. IFRS has no dedicated crypto standard, so preparers apply IAS 38 as intangible assets or IAS 2 as inventory depending on the circumstances. Neither IFRS route produces the same outcome as ASC 350-60, which creates comparability challenges for multinational groups.

What is CARF crypto reporting and who does it affect?

CARF is the OECD's Crypto-Asset Reporting Framework, which requires crypto-asset service providers to collect and report user transaction data to tax authorities for automatic international exchange. It affects exchanges, wallet providers, and certain DeFi platforms. Accounting advisers need to understand CARF because it determines what data tax authorities will receive about their clients' crypto activity.

What is DAC8 reporting and how does it differ from CARF?

DAC8 is the European Union's implementation of CARF principles, extended to cover e-money tokens and CBDCs, and integrated into the EU's existing Directive on Administrative Cooperation infrastructure. While CARF is an OECD standard adopted voluntarily by member countries, DAC8 is binding EU law applicable to crypto-asset service providers operating within the EU. Both result in transaction data flowing to national tax authorities.

Does IFRS crypto accounting require fair value measurement?

Not automatically. Under IAS 38, an entity can choose the cost model or the revaluation model. The revaluation model permits fair value, but only where an active market exists, and gains above cost go to other comprehensive income rather than profit or loss except to reverse a prior impairment. This is materially different from the ASC 350-60 approach, where all fair value changes go through net income.

What disclosures are required under FASB crypto fair value rules?

Entities applying ASC 350-60 must disclose the cost basis of crypto holdings, the unrealised gains and losses recognised in the period, and any restrictions on the ability to sell or transfer assets. For entities with more complex arrangements, such as staking, lending, or third-party custody, additional disclosures may be necessary. These requirements make robust sub-ledger records essential for audit readiness.

When will DAC8 reporting obligations come into effect?

The DAC8 directive was adopted by the European Union and member states are required to transpose it into national law according to the schedule set out in the directive. Crypto-asset service providers operating in the EU should be building their data collection and reporting infrastructure now to ensure they can meet the first reporting cycle. Firms advising EU-resident clients should review what DAC8 data their clients' service providers will submit.

How should accounting firms prepare clients for CARF and DAC8?

The most practical first step is a full inventory of the client's crypto-asset service providers and the jurisdictions in which those providers operate. Firms should then reconcile the client's self-reported crypto income against the transaction records held by those providers, because DAC8 and CARF data will flow directly to tax authorities and any discrepancies will attract scrutiny. Early remediation of errors or omissions is far less costly than a post-disclosure compliance investigation.

Can a company use different accounting policies for different crypto assets?

Under US GAAP, ASC 350-60 applies to all qualifying assets within its scope, so an entity cannot selectively apply the old intangible asset rules to some holdings while using fair value for others. Under IFRS, the accounting policy selected under IAS 38 or IAS 2 must be applied consistently to assets of the same class. Mixing approaches within a class is not permitted, though different classes of assets may follow different policies if the classification is appropriately supported.

What role does crypto accounting software play in meeting these standards?

Dedicated crypto accounting software addresses the core operational challenge: sourcing, reconciling, and auditing the transaction data needed to support fair value disclosures, CARF submissions, and DAC8 reporting. Manual spreadsheet approaches become impractical at any meaningful volume of transactions. Purpose-built tools maintain auditable price feeds, calculate cost basis across multiple accounting methods, and generate the disclosure-ready outputs that both financial statement preparers and regulators require.

Source: CryptaCount