IFRS vs GAAP for Crypto Assets: What Finance Teams Need to Know
Reviewed by Wag3s Editorial Team — verified against ASU 2023-08, IAS 38, and IFRIC agenda decisions · Last reviewed April 2026
IFRS vs GAAP for Crypto Assets: What Finance Teams Need to Know
For most of crypto's short accounting history, IFRS and US GAAP treated cryptoassets in broadly similar ways. Both pushed holders toward an indefinite-lived intangible asset model: book at cost, test for impairment, and never write the value back up if the price recovered. The numbers in your financials looked nothing like the numbers on Coingecko, but at least the two frameworks were ugly in roughly the same way.
That ended with ASU 2023-08. The FASB moved US GAAP to a fair value model for in-scope cryptoassets, effective for fiscal years beginning after December 15, 2024. IFRS, meanwhile, kept the IAS 38 intangible-assets framework that an IFRIC agenda decision codified in June 2019. The result is that two companies holding the same Bitcoin on the same balance sheet date can now report meaningfully different earnings depending on which framework they file under.
If you run finance at a Web3 company that reports under either standard, or worse, both, the divergence is no longer academic.
The starting point: cryptoassets aren't cash, securities, or inventory
Before either framework gets to a measurement model, both have to answer a more basic question: what is a cryptoasset, accounting-wise? The short answer in both worlds: not what you'd hope.
Cash and cash equivalents require legal-tender status or the ability to be readily converted into a known amount of cash with insignificant risk of changes in value. Bitcoin doesn't qualify. Neither does ETH, USDC, or any other crypto asset most teams hold. Even algorithmic stablecoins that intend to track a dollar fail the "insignificant risk of changes in value" test once you scrutinize the redemption mechanism.
Financial instruments under IAS 32 / ASC 320 require a contractual right to receive cash or another financial asset. A Bitcoin held in a wallet gives you no contractual right against any counterparty. It gives you a private key. That's not a financial instrument.
Inventory works only if you hold the cryptoasset in the ordinary course of business for sale. A crypto exchange or a market maker, for example, can apply IAS 2 or ASC 330. A SaaS company that took some BTC as payment cannot.
That elimination process leaves intangible assets as the default home under IFRS, and either intangible assets or (post-ASU 2023-08) a new fair value bucket under US GAAP. Both frameworks landed there because cryptoassets meet the IFRS definition of an intangible (identifiable, non-monetary, without physical substance), and not because anyone thinks an indefinite-lived intangible classification is intuitive for an asset that trades 24/7 on liquid markets.
IFRS treatment: IAS 38 and the revaluation model option
Under IFRS, the IFRIC June 2019 agenda decision concluded that holdings of cryptocurrencies meet the definition of an intangible asset under IAS 38. That puts holders into one of two measurement models.
Cost model (default). Carry the cryptoasset at cost less accumulated impairment losses. Test for impairment whenever there's an indicator that the recoverable amount might be below carrying value. If impairment is recognized, it goes through profit or loss. Reversals of previous impairments are allowed if the recoverable amount recovers, which is one important difference from pre-2024 US GAAP. But you cannot write the asset above original cost.
Revaluation model (optional). If the cryptoasset is traded on an active market (and Bitcoin, ETH, and most major tokens clearly are), IAS 38 allows holders to elect a revaluation model. Carry the asset at fair value. Increases above cost go to a revaluation surplus through other comprehensive income. Decreases below cost go through P&L. This is closer to what crypto-native teams expect, but it introduces an OCI versus P&L split that many finance teams find awkward, and it requires a consistent policy across the relevant class of intangibles.
Most IFRS reporters end up on the cost model. The revaluation election is more administratively heavy, and the OCI treatment makes the headline P&L look conservative even when the asset's fair value has moved meaningfully.
Some IFRS reporters with cryptoassets held for sale in the ordinary course of business apply IAS 2 (inventories) instead. For traders and exchanges that's often the better fit, with measurement at fair value less costs to sell, and changes through P&L. Outside that narrow scenario, IAS 38 governs.
US GAAP before ASU 2023-08: cost less impairment, no upward recovery
Pre-ASU 2023-08, US GAAP treated cryptoassets as indefinite-lived intangible assets under ASC 350. The mechanics were brutal.
Holders measured cryptoassets at cost. They had to test for impairment whenever events or circumstances indicated the fair value might be below carrying value, which for any volatile asset effectively meant continuously. Once impairment was recognized, the new lower carrying value became the floor. There was no recovery: even if Bitcoin doubled the next quarter, the books stayed at the impaired number.
The result: balance sheets that were systematically understated, P&Ls full of impairment charges with no offsetting recoveries, and earnings that bore no resemblance to the economic reality of holding an asset that moved 50% in either direction in a year. MicroStrategy's pre-2025 financials are the most famous case study, but every public-company holder of crypto under US GAAP faced the same distortion.
This is the regime ASU 2023-08 was designed to replace.
What ASU 2023-08 changed
In December 2023, the FASB issued Accounting Standards Update 2023-08, Accounting for and Disclosure of Crypto Assets. It is effective for fiscal years beginning after December 15, 2024, with early adoption permitted. For a calendar-year filer, that means 2025 financials are the first reported under the new model.
The headline change: in-scope cryptoassets are now measured at fair value, with changes recognized in net income each reporting period. Not OCI. Net income.
Scope. The fair value model applies to crypto assets that meet six criteria, including: meeting the definition of an intangible asset under US GAAP, not providing the holder with enforceable rights to or claims on underlying goods, services, or other assets, being created or residing on a distributed ledger, being secured through cryptography, being fungible, and not being created or issued by the reporting entity or its related parties. In practice this captures Bitcoin, ETH, and most fungible tokens. It does not capture NFTs (not fungible), wrapped tokens with claims on underlying assets, stablecoins backed by enforceable redemption rights against the issuer, or tokens issued by the reporting entity itself.
Presentation. Crypto assets in scope are presented separately from other intangible assets on the balance sheet. Gains and losses from remeasurement are presented separately from changes in carrying amounts of other intangibles on the income statement.
Disclosures. ASU 2023-08 introduced substantial disclosure requirements: name, cost basis, fair value, and units held for each significant crypto asset; aggregate fair value and cost basis for the rest; a reconciliation of beginning and ending balances by asset type, showing additions, dispositions, gains, losses, and other changes; and disclosure of restrictions on the assets.
The cumulative-effect adjustment on adoption goes to retained earnings, which means the catch-up for previously impaired but recovered positions hits equity directly rather than running through the income statement.
Side-by-side comparison
The two frameworks now diverge on most of the dimensions that matter:
| Topic | IFRS (IAS 38) | US GAAP post-ASU 2023-08 |
|---|---|---|
| Default classification | Indefinite-lived intangible asset | In-scope crypto assets in their own balance sheet line |
| Initial measurement | Cost | Cost |
| Subsequent measurement (default) | Cost less impairment | Fair value |
| Subsequent measurement (alternative) | Revaluation model if active market | None — fair value is the model |
| Upward changes in value | OCI (revaluation model) or not recognized (cost model) | Net income |
| Downward changes in value | P&L impairment | Net income |
| Impairment reversals | Allowed under cost model | N/A — fair value already captures recovery |
| NFTs | IAS 38 (intangible, cost or revaluation) | Out of scope of ASU 2023-08; remain under ASC 350 cost-less-impairment model |
| Stablecoins with redemption rights | Often a financial asset under IFRS 9 | Often out of scope; analyze under existing financial-instruments guidance |
| Inventory exception | IAS 2 for held-for-sale in ordinary course | ASC 330 for similar fact pattern |
| Disclosure burden | Lighter; standard IAS 38 / IAS 36 disclosures | Heavier; ASU 2023-08 specific schedules |
The consequence: a US GAAP reporter and an IFRS reporter holding identical crypto positions will report different numbers on the balance sheet, in net income, and in OCI. The US GAAP reporter's financials will track market value and show full earnings volatility. The IFRS reporter on the cost model will hold a stale carrying value and report only impairments. The IFRS reporter on the revaluation model will track market value but route gains to OCI rather than P&L.
Stablecoins, NFTs, governance tokens — scope nuances
Beyond the headline frameworks, the asset-by-asset scope decisions are where most of the work happens.
Stablecoins. A USDC or USDT position with a contractual redemption right against the issuer is arguably a financial asset, not an intangible. Under IFRS, that pushes the holder into IFRS 9. Under US GAAP, it falls outside ASU 2023-08's scope and the analysis depends on the specific terms. Algorithmic stablecoins without an issuer-backed redemption right behave more like crypto under both frameworks. The distinction matters: a financial-asset classification typically gets you fair value through P&L under IFRS 9 anyway, but with a different disclosure profile and different impairment mechanics.
NFTs. Non-fungible by definition, so they fail the fungibility criterion in ASU 2023-08 and stay in the indefinite-lived intangible bucket under US GAAP, which means they're now treated less favorably than fungible crypto under the same framework. Under IFRS, they remain under IAS 38 with the same cost or revaluation model election available, though active-market evidence for NFTs is usually thin enough that the revaluation model is hard to support.
Governance tokens. Whether a governance token is in scope of ASU 2023-08 depends on whether holding it provides enforceable claims on goods, services, or other assets. A pure governance right to vote on protocol parameters generally does not. Tokens that entitle the holder to a share of protocol revenue, treasury distributions, or other economic claims need a closer look, both for ASU 2023-08 scope under US GAAP and for the intangible-versus-financial-asset analysis under IFRS.
Wrapped and staked assets. Wrapped tokens (wBTC, wETH) and liquid staking tokens (stETH, rETH) introduce a contractual claim against the wrapping or staking protocol. Under IFRS, that contractual element can push the asset out of IAS 38 and into IFRS 9. Under US GAAP, the same fact pattern can take the asset out of ASU 2023-08 scope. In both cases the answer depends on the specific protocol mechanics.
Disclosure requirements: where IFRS and GAAP diverge most
The measurement gap gets most of the attention. The disclosure gap is arguably bigger.
US GAAP under ASU 2023-08 requires a detailed quantitative roll-forward by significant asset, with units, cost basis, and fair value. It requires disclosure of any restrictions, the methodology for determining fair value, and the principal market used. Annual financials get more detail than interim periods, but interim disclosures are still substantive.
IFRS under IAS 38 has no crypto-specific disclosure regime. You disclose what IAS 38 and IAS 36 require for any intangible asset class: useful lives, impairment testing methodology, key assumptions, and so on. The result is that IFRS financials often tell you less about the actual crypto position than US GAAP financials do, even though IFRS measurement is more conservative.
For a Web3 company concerned about transparency to investors, lenders, and counterparties, the heavier US GAAP disclosure regime is in many ways an advantage even though it costs more to produce.
Practical implications for Web3 companies
The on-the-ground consequences of the divergence are concentrated in a few areas.
P&L volatility. US GAAP reporters now run their crypto position's mark-to-market through net income every quarter. For a treasury holding meaningful BTC or ETH, that is the largest swing factor in the income statement most periods. Boards, audit committees, and investors need to be educated on this before the first quarter under the new regime, otherwise the first 30% Bitcoin move generates uncomfortable conversations about earnings quality.
KPIs and covenants. Debt covenants, equity-based comp metrics, and bonus plans drafted before ASU 2023-08 may now produce results their drafters didn't intend. A net income covenant that worked fine when crypto sat at impaired cost is going to behave very differently when fair value swings hit the bottom line. This is a 2025-2026 cleanup item that hasn't fully worked through public-company filings yet.
Reporting cadence. Fair value measurement at quarter-end requires a reliable source of fair value at quarter-end. For thinly traded assets, that's a meaningful exercise. For BTC and ETH, it's mostly a question of which exchange and which timestamp, with a documented policy.
Audit cost. The disclosure regime under ASU 2023-08 increased the work auditors have to do on crypto positions. For Web3 companies coming out of audit season, the change has been noticeable, particularly for first-year adopters who didn't have prior-period fair values readily available.
What to do if you report under both frameworks
A non-trivial number of Web3 companies file under both frameworks: a Swiss or Singapore HoldCo on IFRS for statutory purposes, with a US-incorporated subsidiary on US GAAP. After ASU 2023-08, those entities now carry the same crypto at different values in different sets of financial statements.
A few practical patterns that work:
Maintain a single source-of-truth ledger of cost basis and unit holdings, and apply the framework-specific measurement on top. Don't try to keep two parallel sub-ledgers; that's where reconciliation breaks down.
Document the framework-difference adjustment as a formal reconciling item in the consolidation, the same way a foreign-currency translation difference is documented. Auditors on both sides of the consolidation will look for it.
If the IFRS reporter is on the cost model, expect a meaningful gap between the two sets of financials in any period where prices have moved. If the IFRS reporter is on the revaluation model, the balance sheets will line up but the income statement and OCI will still differ.
For a finance team that wants the framework-specific reports without rebuilding the supporting work each close, this is exactly the use case Wag3s Ledger is built for: eight financial reports including IFRS-compliant outputs, generated from the same underlying transaction data.
FAQ
Does ASU 2023-08 apply to NFTs? No. ASU 2023-08 requires the asset to be fungible, and NFTs by definition are not. NFTs remain under the prior US GAAP indefinite-lived intangible model: cost less impairment, no upward recovery.
Can an IFRS reporter elect fair value through P&L for crypto? Not directly. Under IAS 38, the alternative to the cost model is the revaluation model, which routes gains above cost through OCI rather than P&L. Some entities with crypto held in the ordinary course of business apply IAS 2 (inventories), which can produce something closer to fair value through P&L, but only in narrow fact patterns.
Does US GAAP now mark stablecoins to fair value? Generally no. Stablecoins backed by enforceable redemption rights against the issuer typically fall outside ASU 2023-08's scope and are analyzed under existing financial-instruments guidance. Algorithmic or unbacked stablecoins are more likely to land in scope.
What's the cumulative-effect adjustment on adoption of ASU 2023-08? It's the difference between the previous carrying value of the in-scope crypto assets and their fair value at the beginning of the adoption period, recognized as a cumulative-effect adjustment to retained earnings. For most early adopters, this was a positive equity adjustment because previous impairments hadn't been allowed to reverse.
Is IFRS likely to converge toward the US GAAP fair value model? There is no current IASB project to do so. Crypto-asset accounting is on the IASB's research agenda but no exposure draft is in flight as of this writing. For now, the divergence is structural.
Further reading
- Wag3s product: Wag3s Ledger — accounting and financial reports for Web3 teams, including IFRS-compliant output
- Crypto Accounting Revolution — how blockchain analytics changed the day-to-day practice of crypto bookkeeping
- Crypto Audit Readiness — what an auditor expects when they show up to test your crypto balances
- FASB ASU 2023-08, Accounting for and Disclosure of Crypto Assets
- IFRIC, Holdings of Cryptocurrencies — agenda decision, June 2019
- IAS 38, Intangible Assets
Crypto Accounting for Startups: From Pre-Seed to Series A
What crypto accounting actually looks like at each startup stage — from pre-seed spreadsheets to Series A audit-readiness — without overbuilding.
Crypto Audit Readiness: What Auditors Actually Look For
What auditors expect from Web3 companies in 2026 — wallet existence, valuation evidence, transaction completeness, and the gaps that derail audits.