IFRS Crypto Assets vs. FASB Fair Value: What the GAAP Gap Means for Digital Asset Reporting

The accounting treatment of crypto assets is not uniform across borders, and the gap between US GAAP and IFRS is wide enough to produce materially different financial statements for entities holding identical positions. Grant Thornton's comparison of the two frameworks, updated for standards in force at the end of 2018 and still a widely referenced baseline for understanding structural divergence, makes clear that crypto assets sit at the intersection of some of the sharpest disagreements between the two regimes. Since that comparison was published, FASB has moved decisively with ASC 350-60, shifting qualifying crypto assets to a fair value model. IFRS has not made an equivalent move, leaving IFRS reporters under IAS 38's intangible-asset rules. For CFOs, group auditors, and accounting firms serving clients on both sides of the Atlantic, understanding where the two frameworks converge, and where they do not, is now a practical necessity rather than an academic exercise.

The Structural Starting Point: Why the Frameworks Diverge on Crypto

US GAAP and IFRS were not designed with digital assets in mind. Both frameworks reached crypto assets through their existing asset-classification hierarchies, and that journey produced different destinations.

How IAS 38 Captures Crypto Under IFRS

Under IFRS, crypto assets held for purposes other than sale in the ordinary course of business are generally treated as intangible assets under IAS 38. That standard permits two subsequent measurement models: cost (carrying value less accumulated amortisation and impairment) or revaluation to fair value, but only where an active market exists for the asset. Critically, the revaluation model allows upward revaluations, but gains flow to other comprehensive income rather than the income statement unless they reverse a prior impairment charge. Impairment losses, by contrast, flow directly to profit or loss and cannot be reversed once recognised under IAS 36. The practical effect is an asymmetric model: losses hit earnings immediately, gains largely do not.

Entities whose business model involves selling crypto in the ordinary course (brokers, exchanges, miners treating inventory as stock-in-trade) may instead apply IAS 2 on inventories, which permits measurement at net realisable value for commodity broker-traders, allowing fair value movements through profit or loss. That carve-out is narrow, however, and most corporate holders do not qualify.

FASB's Fair Value Pivot Under ASC 350-60

FASB's Accounting Standards Update introducing ASC 350-60 changed the US GAAP landscape materially. Qualifying crypto assets, defined broadly to capture fungible, non-security, non-wrapped tokens that reside on a distributed ledger, must now be measured at fair value at each reporting date. Both unrealised gains and unrealised losses flow through net income. There is no impairment-only constraint and no OCI parking. A company that holds Bitcoin and sees its price rise between quarter-end dates recognises that gain in its income statement, period. The same applies on the downside.

The scope of ASC 350-60 is meaningful: it covers assets that are created or reside on a blockchain or distributed ledger using cryptography, are fungible, and are not produced or acquired for the entity's own use. NFTs, tokenised securities, and stablecoins backed by fiat or other assets generally fall outside the definition and continue under other GAAP literature. For those excluded assets, earlier GAAP treatments involving indefinite-lived intangible asset rules with impairment-only write-downs may still apply, creating a two-tier US GAAP landscape even before the IFRS comparison begins.

For more on how ASC 350-60 interacts with corporate treasury strategies, see our analysis of FASB ASC 350-60 and bitcoin treasury company reporting.

Key Differences That Show Up in the Financial Statements

The divergence between the two frameworks is not a single issue. It manifests across several line items and disclosures in a set of crypto financial statements, each of which carries its own audit and tax provisioning implications.

Income Statement Volatility

The most visible difference is income statement volatility. Under ASC 350-60, a US GAAP entity with a material crypto position will see net income move with the market at every reporting date. A CFO managing earnings-per-share guidance or a loan covenant tied to EBITDA needs to account for this mechanically, not as a one-off. An IFRS entity using the cost model avoids that volatility on the upside but absorbs it fully on the downside through impairment. An IFRS entity using the IAS 38 revaluation model smooths the upside into OCI but still takes downside hits through profit or loss. Neither IFRS path mirrors the symmetric US GAAP treatment.

Balance Sheet Presentation

US GAAP now requires crypto assets within ASC 350-60's scope to be presented separately on the balance sheet, with the carrying amount reflecting fair value. IFRS does not have an equivalent specific presentation requirement for crypto assets, leaving more room for preparers to slot holdings into existing intangible asset line items. That flexibility can make cross-entity comparison harder for investors and auditors working across a group with entities in multiple jurisdictions.

Impairment Asymmetry and Its Audit Implications

Auditors examining an IFRS entity's crypto holdings must assess whether impairment indicators existed at the balance sheet date and, if so, whether the recoverable amount calculation is supportable. Because IFRS impairment losses on intangibles cannot be reversed, a write-down made in a period of market stress permanently reduces the carrying value even if prices recover substantially. That creates a deferred tax asset position that itself requires careful assessment of recoverability. US GAAP auditors, by contrast, are focused on fair value hierarchy inputs (typically Level 1 for exchange-traded crypto) and disclosure of the valuation technique, a far simpler audit pathway for liquid, publicly priced assets.

Tax Provisioning Differences

The accounting model determines the temporary difference base for deferred tax calculations. Under ASC 350-60, unrealised fair value gains recognised in net income create taxable temporary differences that require deferred tax liabilities unless an exception applies. Under IFRS cost model accounting, no such temporary difference arises until the asset is sold or impaired. The result is that two entities holding identical crypto positions can show materially different effective tax rates and deferred tax balances, purely as a function of their accounting framework. For group finance teams consolidating entities across jurisdictions, aligning the tax footnote with the right underlying model is a genuine complexity. Our coverage of the digital asset accounting implications of the IRS Nationwide Tax Forums 2026 sets out related US tax reporting considerations.

Where the Two Frameworks Agree (and Why That Matters)

Recognition and Derecognition Principles

Despite the measurement divergence, US GAAP and IFRS share broadly consistent principles on when an asset is recognised and when it is derecognised. An entity recognises a crypto asset when it obtains control (IFRS) or when the risks and rewards have transferred (with control increasingly the operative concept under both frameworks for financial assets). Derecognition occurs on disposal or transfer, and the gain or loss on disposal is calculated as proceeds less carrying value at the date of sale. For IFRS cost-model holders, that carrying value may be significantly lower than fair value if the asset appreciated without triggering a revaluation, meaning the income statement gain on sale can be dramatic compared to what a US GAAP entity would report cumulatively over the holding period.

Disclosure Philosophy

Both frameworks require sufficient disclosure for users to understand the nature, risks, and carrying amounts of significant asset classes. In practice, regulators and standard-setters on both sides have pushed for crypto-specific disclosures covering concentration risk, custody arrangements, and the basis of fair value determination. The substance of what auditors expect to see in the notes is converging even where the measurement models are not.

Practical Implications for Accounting Firms and CFOs

Entity-by-Entity Framework Mapping

A multinational group may include US entities reporting under GAAP and non-US subsidiaries reporting under IFRS before consolidation. If both hold crypto assets, the group finance team needs a clear map of which standard applies to which entity, which measurement model that entity has adopted within IFRS, and how intercompany crypto transfers are eliminated on consolidation. Getting that map wrong produces errors that propagate through the group income statement, OCI, and the deferred tax note simultaneously.

System and Workflow Requirements

Digital asset accounting software used at the entity level needs to be able to output data in the format the applicable framework requires. A system configured only for impairment-based tracking will not produce the correct output for an ASC 350-60 entity that needs fair value at each reporting date with gains and losses allocated to net income. Conversely, a system built around FASB's fair value output may not capture the impairment indicators and recoverable amount calculations an IFRS entity's auditors will request. Firms advising clients across both regimes should audit their own tooling to ensure it is framework-aware, not just crypto-aware.

Covenant and Reporting Consideration for CFOs

Lenders and bond indentures often include financial covenants referenced to GAAP or IFRS metrics. A CFO at a US GAAP entity now needs to consider that a sharp rise in crypto asset fair values will increase reported net income and retained earnings, which may be positive for equity-based covenants but may also affect leverage ratios if the asset is not treated as debt service coverage-eligible. The reverse applies on a price decline: a mark-to-market loss under ASC 350-60 hits net income in the period, potentially tripping an EBITDA-adjacent covenant even if the company's operating cash flows are healthy. Flagging this to treasury and legal teams before a volatile quarter closes is a practical step that falls squarely within the finance function's responsibility.

What Firms Should Do Before the Next Reporting Period

The gap between the two frameworks is established and unlikely to close quickly. IFRS has acknowledged the inadequacy of IAS 38 for crypto assets and the IASB has had the topic on its agenda, but no IFRS equivalent of ASC 350-60 is yet effective. That means the divergence will persist through at least several more reporting cycles.

Firms should take the following steps now:

• Confirm which accounting framework applies to each entity holding crypto assets and document it formally.
• For IFRS entities, determine whether the IAS 38 cost model or revaluation model has been adopted and whether any holdings might qualify for IAS 2 treatment.
• For US GAAP entities, confirm which assets fall within ASC 350-60's scope and which remain under earlier intangible asset literature.
• Review deferred tax calculations at each entity to ensure the temporary difference base reflects the correct carrying value model.
• Assess digital asset accounting software configurations to confirm they produce the correct measurement output for each framework.
• Communicate the income statement volatility implications of ASC 350-60 to the board, lenders, and any counterparties whose agreements reference GAAP metrics.

The accounting standards governing crypto assets are not static. Staying current with both FASB and IASB developments, and mapping those developments to specific entity obligations, is the baseline standard of care for any firm or CFO with material digital asset exposure. For broader context on compliance and reporting obligations, visit our crypto compliance and reporting hub.

Source: Grant Thornton

Frequently Asked Questions

Does IFRS require fair value accounting for crypto assets?

Not as a default. IFRS entities typically classify crypto assets as intangible assets under IAS 38 and may choose the cost model or, where an active market exists, the revaluation model. Under the revaluation model, upward movements go to OCI rather than profit or loss. There is no IFRS equivalent to FASB's ASC 350-60 fair value through net income requirement yet in force.

What does ASC 350-60 require for US GAAP entities?

Entities reporting under US GAAP must measure qualifying crypto assets, broadly fungible, non-security, blockchain-based tokens, at fair value at each reporting date, with both unrealised gains and unrealised losses recognised in net income. The standard also requires separate balance sheet presentation and specific disclosures covering the nature of holdings and fair value inputs.

How does the accounting framework choice affect the tax provision?

The measurement model drives the temporary difference base for deferred tax. A US GAAP entity recognising unrealised fair value gains in net income creates taxable temporary differences requiring deferred tax liabilities. An IFRS entity on the cost model does not recognise a temporary difference until disposal or impairment. Two entities holding the same crypto position can therefore show different effective tax rates and deferred tax balances solely because of their accounting framework.

Can a multinational group have entities under both GAAP and IFRS holding crypto?

Yes, and this is a real complexity for group consolidations. Each entity applies its own framework at the entity level. On consolidation, the group must eliminate intercompany crypto transfers and align measurement consistently with the group's reporting standard, typically IFRS for most non-US listed groups or US GAAP for US-listed multinationals. Finance teams need a documented framework map and systems that can output data in the format each framework requires.

Is the IASB working on a specific crypto asset standard?

The IASB has acknowledged that IAS 38 was not designed with crypto assets in mind and has considered the topic. However, as of the date of this analysis, no IFRS standard equivalent to ASC 350-60's fair value through net income model for crypto assets is effective. Preparers and auditors should monitor IASB agenda decisions for updates, as the position could change within the medium-term planning horizon.