IFRS Crypto Assets vs FASB Fair Value: What CFOs and Auditors Must Act On Now
Two major accounting frameworks now account for crypto assets in fundamentally different ways, and the gap between them is wide enough to produce material differences in reported earnings, balance-sheet values, and audit opinions. FASB's fair-value model under ASC 350-60 is already effective for US public companies, while IFRS preparers continue to navigate IAS 38 and the patchwork of agenda decisions issued by the IFRS Interpretations Committee. For CFOs, controllers, and the internal-audit functions that serve them, the divergence is not a theoretical concern — it is a live financial-reporting risk that regulators on both sides of the Atlantic are watching.
Why the Framework Divergence Matters for Crypto Financial Statements
For most of crypto's history, both US GAAP and IFRS defaulted to an indefinite-lived intangible-asset model, where impairment charges could be recognised but upward revaluations could not. That created a well-documented asymmetry: companies holding Bitcoin or Ether could only mark assets down, never up, during a reporting period, leading to financial statements that understated economic reality when prices recovered.
The FASB Shift to Fair Value Under ASC 350-60
FASB addressed that asymmetry directly. Its final standard, codified as ASC 350-60, requires entities that hold qualifying crypto assets — broadly, fungible digital assets secured through cryptography that reside on distributed ledgers — to measure those holdings at fair value at each reporting date. Changes in fair value flow through the income statement in the period they arise. For US public companies, this treatment is now mandatory; it is not an option that can be declined.
The practical consequences for crypto financial statements are significant. A company holding a large Bitcoin position will see its net income move in tandem with spot prices, quarter by quarter. That volatility is visible, and it is auditable. External auditors must now obtain evidence for fair-value measurements, assess the appropriateness of the pricing sources used, and consider whether any holdings are in markets with reduced liquidity that would complicate Level 1 or Level 2 classification under ASC 820.
Where IFRS Crypto Accounting Currently Stands
IFRS preparers do not yet have a dedicated standard for crypto assets. The IFRS Interpretations Committee has confirmed that crypto assets held for sale in the ordinary course of business may qualify as inventory under IAS 2, while others fall under IAS 38 as intangible assets. Under IAS 38, an entity may elect the revaluation model — but only if an active market exists for the asset in question, and the revaluation surplus goes to other comprehensive income rather than profit or loss. Most IFRS preparers choose the cost model under IAS 38, meaning impairment-only treatment persists.
The IASB has crypto assets on its agenda. Preparers in the EU, the UK, and elsewhere should anticipate that a dedicated IFRS standard will eventually narrow the gap with FASB, but the timeline remains uncertain. In the interim, the choice of accounting policy under IAS 38 — cost model versus revaluation model — requires clear documentation and consistent application, and auditors will scrutinise it closely given how much it affects reported numbers.
Internal Audit Coverage: The Risks CAEs Cannot Ignore
Beyond the accounting-policy choice itself, the operational infrastructure required to support crypto financial statements introduces its own audit risk surface. Forvis Mazars, in its analysis of the risk priorities facing chief audit executives in large financial institutions, identifies several interconnected risk categories that apply with particular force to entities that hold or transact in digital assets.
Credit and Asset-Quality Risk in Crypto Portfolios
For banks and financial institutions with crypto-lending books or exposure to crypto-collateralised lending, geopolitical pressure and market volatility directly affect the creditworthiness of borrowers. CAEs need to ensure that risk assessments cover asset quality at a granular level, including any real estate or consumer credit that has indirect crypto exposure through collateral arrangements. The volatility inherent in digital assets means that collateral valuations can move sharply between reporting dates, creating credit-risk concentrations that standard quarterly reviews may not capture in time.
Liquidity Risk and Funding-Cost Pressures
Institutions that hold crypto assets on their balance sheet, or that have committed to crypto-related funding arrangements, face an additional layer of liquidity risk. Deposit growth is slowing across the sector, and funding costs are rising. Liquidity stress-testing programmes need to incorporate digital-asset scenarios — including the possibility of rapid price dislocation — and the assumptions underpinning those tests must be reviewed continuously rather than annually. CAEs should evaluate whether governance structures around liquidity risk management have kept pace with the institution's digital-asset activity.
Cybersecurity and the Digital-Asset Attack Surface
The more an institution's financial statements depend on digital-asset holdings, the more attractive it becomes as a target for sophisticated cyberattacks. Ransomware and phishing remain the dominant vectors, but the proliferation of AI-assisted attack tooling has materially expanded the threat landscape. Internal audit functions must assess whether cybersecurity frameworks have been updated to reflect digital-asset custody risks — private key management, hot-versus-cold wallet controls, and the integrity of the data feeds used to derive fair-value measurements are all audit-relevant. Gaps in any of these areas could compromise the reliability of the fair-value figures that flow directly into FASB-compliant crypto financial statements.
DORA and ICT Risk: The EU Dimension for IFRS Preparers
For accounting firms and CFOs operating in the EU, the Digital Operational Resilience Act adds a regulatory layer that intersects directly with crypto-asset operations. DORA imposes binding requirements on ICT risk management, incident reporting, and operational resilience testing for financial entities in scope. Banks and investment firms that hold crypto assets or provide related services must ensure their ICT risk management frameworks are formally aligned with DORA's requirements — not just in policy documentation, but in tested practice.
What Auditors Must Test Under DORA
Internal auditors with EU-facing mandates need to cover three specific areas. First, they should assess whether the organisation's ICT risk management framework meets DORA's standards, including the governance structures that sit above it. Second, they should evaluate incident-response and reporting procedures — DORA sets specific timelines for reporting ICT-related incidents to supervisors, and crypto exchanges or custody operations are particularly exposed given the frequency of attempted intrusions. Third, business-continuity and disaster-recovery plans must be tested against DORA's operational resilience expectations, not just general best practice. A failure in any of these areas is not a theoretical concern; supervisors will reference the quality of internal audit work when assessing an institution's overall risk management capability.
For firms that use digital asset accounting software to generate or support the numbers that flow into IFRS or US GAAP financial statements, the reliability and auditability of that software becomes a DORA concern as well as an accounting one. The data lineage from blockchain transaction to ledger entry to financial statement must be traceable, and the controls around that process must be documented and tested.
Practical Steps for CFOs and Accounting Firms
The accounting-standards divergence and the operational risks described above translate into a concrete list of actions for finance and audit teams operating in 2026.
For US GAAP Preparers
Confirm that all qualifying crypto holdings are captured within the scope of ASC 350-60 and are being measured at fair value each reporting period. Review the pricing hierarchy under ASC 820: are the fair-value inputs drawn from active markets, and are they independent? Assess whether the income-statement volatility introduced by fair-value accounting has been communicated clearly in MD&A and whether it is reflected in any covenant calculations tied to reported earnings. Ensure the disclosure requirements under ASC 350-60 — including the table of crypto asset activity for the period — are complete and auditor-reviewed before filing.
For IFRS Preparers
Document the accounting policy choice under IAS 38 (cost model or revaluation model) and apply it consistently. If the revaluation model is applied, confirm that an active market exists for each asset class covered and that the revaluation surplus is correctly routed to other comprehensive income. Monitor IASB agenda activity: any new pronouncement on crypto assets could require a change in accounting policy with retrospective or prospective application, and early engagement with auditors on the transition approach is advisable. Consider whether any holdings qualify as inventory under IAS 2, which would require a different measurement basis entirely.
For Internal Audit Functions
Risk assessments should be reviewed to confirm that crypto-asset holdings, crypto-related credit exposures, and the technology infrastructure supporting fair-value measurement are all within audit scope. CAEs should map their organisation's digital-asset activity against the risk categories above — credit, liquidity, cyber, and DORA compliance — and prioritise coverage accordingly. Where the audit team lacks specialist digital-asset expertise, co-sourcing arrangements or targeted training should be considered before the next audit cycle begins. For more on how the CLARITY Act is reshaping the environment for CFOs with digital-asset exposure, see our analysis of how the CLARITY Act affects crypto accounting and CFO obligations.
CFOs seeking a deeper understanding of how FASB is thinking about stablecoin classification alongside its broader crypto reporting agenda should also read our coverage of FASB chair guidance on stablecoin accounting and semiannual reporting, which sets out the standard-setter's current thinking in detail.
The Audit and Reporting Landscape: A Side-by-Side View
The table below summarises the key differences between the two frameworks as they currently apply to crypto asset holdings, to help teams identify where their financial statements may diverge from peer disclosures.
| Dimension | US GAAP (ASC 350-60) | IFRS (IAS 38 / IAS 2) |
|---|---|---|
| Primary classification | Crypto asset (dedicated standard) | Intangible asset (IAS 38) or inventory (IAS 2) |
| Measurement basis | Fair value at each reporting date | Cost model or revaluation model (IAS 38); lower of cost or NRV (IAS 2) |
| Gains on price recovery | Recognised in profit or loss immediately | Not recognised under cost model; OCI only under revaluation model |
| Income statement impact | Directly volatile with crypto prices | Limited to impairment (cost model) or OCI movements (revaluation) |
| Dedicated standard | Yes — ASC 350-60 effective for fiscal years after 15 Dec 2024 | No — IASB project ongoing; agenda decisions only |
| Disclosure requirements | Tabular disclosure of activity and fair-value measurements required | Standard IAS 38 / IAS 2 disclosures; no crypto-specific table mandated |
Frequently Asked Questions
Does ASC 350-60 apply to all crypto assets a US company holds?
ASC 350-60 applies to crypto assets that meet its definition: fungible digital assets secured through cryptography that reside on distributed ledgers and are not produced or held by the reporting entity as inventory. Tokens that function as equity or debt instruments in the hands of the holder, or that are classified differently under other US GAAP guidance, fall outside the standard's scope. Preparers should map each holding to the correct classification before applying the fair-value measurement requirement.
Can an IFRS preparer voluntarily adopt fair-value measurement for crypto assets today?
Under IAS 38's revaluation model, an entity can measure intangible assets at fair value, but only if an active market exists for the specific asset. The revaluation surplus is recognised in other comprehensive income, not in profit or loss — so the income-statement treatment still differs from ASC 350-60. Entities that qualify for and elect the revaluation model must apply it consistently to the entire class of assets, not selectively to individual holdings.
How should a CAE prioritise crypto-asset audit coverage given competing risk areas?
CAEs should start by quantifying the institution's digital-asset exposure — balance-sheet holdings, crypto-collateralised lending, custody obligations, and any derivative positions. That materiality assessment drives the audit priority. Where crypto holdings are material to reported net assets or earnings, the fair-value measurement process, pricing-source independence, and IT controls over the data pipeline from blockchain to ledger should be high-priority audit objectives. Liquidity and credit risk associated with those holdings should be layered in alongside the technology and cybersecurity risks.
What do DORA's ICT requirements mean specifically for crypto custody operations?
Crypto custody — the safekeeping of private keys and the operational processes around them — is precisely the kind of ICT function DORA targets. Institutions in scope must have documented ICT risk management policies covering custody infrastructure, must be able to detect and report ICT incidents within DORA's prescribed timelines, and must test business-continuity plans that include scenarios such as key-management system failure or a successful cyberattack on custody infrastructure. Supervisors will review audit coverage of these areas as part of their assessment of overall operational resilience.
How does the FASB fair-value model affect debt covenants tied to reported earnings?
Because ASC 350-60 routes fair-value gains and losses through the income statement, a company with significant crypto holdings will see its reported net income — and therefore any earnings-based covenant ratios — move with crypto prices. CFOs should review all credit agreements and bond indentures to determine whether covenant calculations reference GAAP net income and, if so, whether the lender or trustee has agreed to any carve-outs or adjustments for digital-asset fair-value movements. Addressing this proactively, before a covenant breach arises, is materially less costly than dealing with it after the fact.
Source: Forvis Mazars