Are you confident in accurately reporting cryptocurrency earnings on your tax returns?

How to account for cryptocurrency under GAAP: A controller's reference guide

A controller's reference guide to US GAAP crypto accounting: classification, fair value measurement, ASU 2023-08, impairment, and disclosure requirements.

How to account for cryptocurrency under GAAP: A controller's reference guide

Crypto has moved from a niche experiment to a balance sheet reality for thousands of companies. Yet most GAAP guidance was written before anyone imagined a controller would need to account for staking rewards, stablecoin treasury positions, or DeFi liquidity pool withdrawals.

This guide cuts through the ambiguity. It covers how US GAAP applies to digital assets today — classification, measurement, impairment, and the key regulatory updates reshaping the landscape — and offers a forward-looking view on where the standards still need to go.

The regulatory backdrop: What's changed

Before diving into the accounting mechanics, it's worth grounding the discussion in the three developments that have most significantly changed the operating environment for controllers managing crypto:

ASU 2023-08 (effective FY2025)

The FASB's fair value standard for qualifying crypto assets, replacing the prior cost-less-impairment model for Bitcoin, Ether, and similar fungible tokens. Gains and losses now flow through net income each reporting period.

SAB 122 (January 2025)

The SEC replaced SAB 121, which had required entities safeguarding digital assets to recognize both the asset and a corresponding liability on the balance sheet — a rule that created significant friction for banks and custodians considering crypto custody services. SAB 122 removes that requirement, easing a major structural barrier to institutional participation in digital asset custody.

GENIUS Act (July 2025)

The first federal law specifically regulating stablecoins. It mandates 1:1 backing by US dollars or short-term Treasuries, requires monthly public reserve disclosures, mandates annual audits for large issuers, and establishes strong AML safeguards. This legislation has meaningful implications for how fiat-backed stablecoins are classified on the balance sheet — specifically strengthening the case for cash equivalent treatment for compliant issuers.

Together, these three developments represent the most significant shift in the crypto accounting environment since digital assets first appeared on corporate balance sheets.

How digital assets are classified under US GAAP

The first question controllers face: what kind of asset is this?

The answer depends on the asset type and which standard governs it. Here is the current framework:

Asset typeAccounting treatmentGoverning standard
Bitcoin, Ether (fungible, FV-eligible)Fair value through earningsASC 350-60 (ASU 2023-08)
Stablecoins (fiat-backed, compliant)Cash equivalent or financial assetASC 305 / GENIUS Act guidance
Stablecoins (algorithmic, partially-backed)Indefinite-lived intangibleASC 350-30
Native tokens (issuer-held)Cost basis; excluded from ASC 350-60ASC 350-30
NFTs, RWAsIntangible asset; impairment model appliesASC 350-30
Wrapped tokensCost basis; disposition may be triggered on wrap/unwrapASC 350-30

The critical dividing line is whether an asset qualifies under ASU 2023-08. Qualifying assets — fungible, intangible, cryptographically secured, recorded on a distributed ledger, and not issued by the reporting entity — receive fair value treatment. Everything else defaults to the ASC 350-30 intangible asset model.

Measurement: Fair value under ASU 2023-08

Once an asset is confirmed in scope, measurement follows a consistent principle: mark to fair value at each reporting date, with changes recognized in net income.

Practical considerations for controllers:

Price sourcing: Apply a principal market or most advantageous market approach per ASC 820. For liquid assets like BTC or ETH, this is typically a reputable exchange price at the measurement date — not an average, not an intraday price. The closing price on the measurement date is the standard.

Fair value hierarchy:

  • Level 1: Quoted prices in active markets — applicable to BTC, ETH, and most liquid tokens traded on major exchanges
  • Level 2: Observable inputs other than quoted prices — applicable to less liquid tokens with comparable market data
  • Level 3: Unobservable inputs — required for illiquid or long-tail tokens where no active market exists

Measurement frequency: Given the volatile nature of crypto, impairment testing and fair value measurement should be performed at least monthly — not just at quarter-end. For in-scope assets under ASU 2023-08, fair value is marked at each reporting date. For out-of-scope assets still under ASC 350-30, impairment indicators should be assessed continuously and tested whenever material price movements occur.

SoDA alignment: The Statement of Digital Assets (SoDA) reporting framework recommends disclosing both book value and fair market value for all digital asset holdings, regardless of whether they qualify for ASU 2023-08 fair value treatment. This dual-disclosure approach improves liquidity transparency and supports audit readiness — and is increasingly expected by auditors and institutional counterparties.

Stablecoin classification: Evolving but still a judgment call

Stablecoins create the most classification complexity in crypto accounting today — and the GENIUS Act has meaningfully shifted the analysis for fiat-backed issuers.

Stablecoin typeLikely classificationKey consideration
Fiat-backed, GENIUS Act compliant (USDC, USAT)Cash equivalent (ASC 305)1:1 reserve backing + monthly disclosure + annual audit = strong basis for cash equivalent treatment
Fiat-backed, non-compliant or offshore (USDT pre-audit)Other current asset or intangibleRedemption mechanism and reserve quality require assessment
Algorithmic or partially-backedIntangible asset (ASC 350-30)Redemption risk too high for cash equivalent treatment
Yield-bearing stablecoinsPossibly investment (ASC 320/321)Contractual return creates instrument-like characteristics

The SEC Staff Accounting Bulletin issued August 5, 2025 further indicated that certain US dollar-pegged stablecoins with guaranteed redemption and proper reserves could qualify for cash or cash equivalent treatment rather than securities classification — providing additional support for the cash equivalent position for compliant fiat-backed stablecoins.

The bottom line: No single authoritative standard governs stablecoins comprehensively. Classification remains a judgment call, but the judgment is now better informed by the GENIUS Act framework and the SEC's August 2025 guidance. Document your position clearly and revisit it as the regulatory landscape continues to evolve.

Impairment: Legacy treatment for out-of-scope assets

For digital assets not covered by ASU 2023-08 — including NFTs, issuer-held tokens, wrapped assets, and non-compliant stablecoins — the ASC 350-30 impairment model applies:

  • Test frequency: Given the volatile nature of crypto, impairment should be assessed at least monthly, not just at quarter-end. A material price decline mid-period is an impairment indicator that requires evaluation.
  • Recognition trigger: If fair value drops below carrying value at any point during the period, recognize an impairment loss immediately for the difference.
  • No recovery: Once written down, the asset stays at the impaired value until disposal. Recoveries cannot be recognized under ASC 350-30 — this asymmetric treatment is one of the most significant remaining differences between legacy and current GAAP for out-of-scope crypto assets.
  • Documentation: Maintain a contemporaneous impairment analysis for each period, including the pricing source, the fair value determination, and the comparison to carrying value. Auditors will expect this documentation on demand.

Financial statement presentation

Under ASU 2023-08, crypto assets must be presented as a separate line item from other intangible assets on both the balance sheet and the income statement. They cannot be aggregated into a general "intangibles" or "other assets" line.

Required disclosures include:

  • A rollforward of crypto asset holdings by significant type (beginning balance, additions, disposals, fair value changes, ending balance)
  • Fair value hierarchy classification (Level 1, 2, or 3) for each significant holding
  • Impairment methodology for out-of-scope assets
  • Restrictions on holdings — staking lockups, regulatory freezes, custodial arrangements
  • Pricing sources and measurement date

For companies following the SoDA framework, the rollforward and wallet-level detail required by SoDA maps directly onto these disclosure requirements — making SoDA adoption a practical foundation for ASU 2023-08 compliance.

Operational and audit readiness: What controllers need in place

Accounting compliance is only as strong as the operational infrastructure behind it. The Controller's Guide identifies four operational requirements that directly enable GAAP compliance:

1. Custody model clarity

Self-custody offers control but creates sole responsibility for key management, access controls, and loss prevention. Third-party custody — now significantly simplified by SAB 122's removal of the safeguarding asset/liability recognition requirement — introduces counterparty considerations but provides institutional-grade security and audit documentation. Document the custody model for each asset and ensure it's reflected in your accounting policy.

2. Crypto subledger

Traditional accounting systems are not designed to ingest on-chain transaction data, calculate cost basis across wallets and exchanges, or produce ASU 2023-08-compliant fair value adjustments. A purpose-built crypto subledger connects directly to wallets, exchanges, and custodians; automates classification and cost basis tracking; and produces journal entries formatted for your ERP. Without one, the manual work required to close the books scales faster than the team.

3. Wallet reconciliation

Reconcile wallet balances to the subledger and general ledger at least monthly. Each on-chain address should be mapped to a business purpose (treasury, operations, custody, staking) to ensure transactions are classified correctly and to prevent commingling of funds.

4. Internal controls

  • Use multi-signature or MPC wallets for transaction authorization
  • Implement documented approval workflows for crypto transactions above defined thresholds
  • Maintain a key custody log with role-based permissions
  • Align crypto subledger data to GAAP trial balances before period close

These controls aren't just best practice — they're what auditors will look for when they examine your crypto accounting processes.

Where US GAAP still falls short

ASU 2023-08 was a meaningful step forward. But significant gaps remain — and controllers building infrastructure today should design systems flexible enough to absorb future guidance changes.

DeFi and yield-generating activity: No specific guidance exists for staking rewards, liquidity pool income, or lending protocol returns. Controllers are applying analogies to interest income, dividend income, or other revenue recognition frameworks — with limited consistency across firms. The FASB has this area on its agenda but has not issued specific guidance.

Cost basis tracking: GAAP does not prescribe a specific cost basis method. Controllers must choose (FIFO, HIFO, specific identification), document the selection, and apply it consistently. Method changes require disclosure and careful consideration of prior-period comparability.

Intercompany crypto transfers: Multi-entity companies transacting in crypto face significant complexity in intercompany elimination and consolidation with no specific guidance. Internal wallet transfers that cross entity boundaries require careful documentation to avoid phantom gain recognition.

NFTs and illiquid tokens: Still under ASC 350-30 with no fair value requirement, even as NFTs and tokenized real-world assets see growing commercial use.

The forward-looking question: tokenized deposits and securities

The GAAP gaps described above exist for crypto assets that are already on balance sheets today. The more significant challenge on the horizon is accounting for an entirely new category of assets that major financial institutions are actively building right now — tokenized deposits and tokenized securities — for which the accounting framework is almost entirely undefined.

Tokenized deposits: Banks are moving, standards are not

A tokenized deposit is a digital representation of a traditional commercial bank deposit on a distributed ledger. It is not a stablecoin — it remains on the bank's balance sheet, retains FDIC insurance (where applicable), and operates within the existing fractional reserve banking framework. But it moves like a blockchain token: 24/7, programmable, with atomic settlement.

The activity here is no longer theoretical. JPMorgan has launched JPMD (JPM Coin) on Base, the public Ethereum Layer 2, processing over $5 billion in daily transaction volume on its Kinexys platform. HSBC has expanded its tokenized deposit service to cross-border transactions. BNY Mellon — which handles $2.5 trillion in daily payments — is actively exploring tokenized deposit infrastructure. BMO just announced a tokenized cash platform with CME Group and Google Cloud in March 2026 to support 24/7 margin and settlement flows for institutional clients.

The accounting questions this creates are unresolved:

  • On-chain vs. off-chain ledger reconciliation: A tokenized deposit exists simultaneously as a liability on the bank's traditional balance sheet and as a token on a distributed ledger. Which record controls? How should discrepancies between the two be identified and resolved? Regulators and state banking supervisors have explicitly flagged the need for guidance on "reconciliation between on- and off-chain deposit liabilities" — it does not yet exist.
  • Continuous settlement and intraday accounting: Current accounting systems are built around end-of-day posting cycles. Tokenized deposits settle atomically and continuously — 24 hours a day, 7 days a week. Accounting systems designed around batch windows cannot accurately capture liquidity positions that change in real time. This is an infrastructure problem with direct financial reporting consequences.
  • Programmable payments and smart contract obligations: Tokenized deposits can be programmed with conditions — release payment when a shipment is confirmed, for example. The accounting treatment for contingent, programmable payment obligations under existing GAAP (ASC 420, ASC 450) has not been addressed in the context of smart contract execution.
  • FASB agenda item: The FASB added a project in late 2025 to clarify whether certain digital assets — including tokenized deposits — qualify as cash equivalents under GAAP. Initial deliberations have not yet produced guidance. Until they do, controllers holding tokenized deposits must apply judgment with no authoritative standard to lean on.

Tokenized securities: NYSE and Nasdaq are building, GAAP is behind

The same convergence is happening in equities. NYSE signed an MOU with Securitize in March 2026 to build a blockchain-based Digital Trading Platform for tokenized stocks and ETFs — 24/7 trading, near-instant settlement, stablecoin-funded transactions, with Securitize as the first digital transfer agent eligible to mint blockchain-native securities. Nasdaq, meanwhile, has already obtained regulatory approval for its own tokenized stock framework and tapped Kraken for global distribution. The DTCC — which processed $3.7 quadrillion in transactions in 2024 — received a no-action letter from the SEC to tokenize real-world assets including Russell 1000 equities and US Treasuries, with the service targeting launch in the second half of 2026.

These are not pilot programs. This is production-grade infrastructure being built by the institutions that define how capital markets operate. The accounting implications for controllers are significant and unaddressed:

  • Classification of tokenized equities: Is a tokenized share of Apple the same as a traditional share for ASC 320/321 purposes? The SEC's January 2026 tokenized securities taxonomy provides some framework, but GAAP has not been updated to address tokenized equity instruments specifically. Whether a tokenized equity is classified as a debt security, equity investment, or something else under existing standards depends on the structure — and different structures are being used by different platforms.
  • Instant settlement and trade date accounting: Under current GAAP, equity transactions are recorded on trade date (ASC 230, ASC 320). Traditional settlement is T+2. Tokenized equities settle in seconds. The mismatch between trade date recognition and the operational reality of instantaneous settlement creates timing and reconciliation questions that existing guidance does not fully address.
  • Stablecoin-funded equity purchases: NYSE's platform is designed for stablecoin-funded transactions. A company using USDC to purchase a tokenized equity position is executing two transactions — a stablecoin disposal (potentially taxable) and an equity acquisition — simultaneously. The accounting for this compound transaction has no specific guidance.
  • 24/7 fair value measurement: ASC 820 fair value measurement for equity securities is calibrated to exchange trading hours. Tokenized equities trading around the clock on blockchain platforms create measurement date questions — particularly for companies with significant equity holdings that now have observable prices outside traditional market hours.
  • Fractional ownership: Tokenized platforms enable fractional ownership of individual securities. The cost basis and lot tracking implications of fractional share positions at scale, across multiple wallets and platforms, go beyond what current accounting infrastructure was designed to handle.

What controllers should be doing now

The honest answer is that the accounting standards for tokenized deposits and tokenized securities will lag the infrastructure by years — just as ASU 2023-08 lagged Bitcoin's first appearance on corporate balance sheets by nearly a decade.

That doesn't mean controllers can wait. Three things to do now:

1. Monitor the FASB agenda actively. The FASB's 2026 projects on digital asset cash equivalents and digital asset transfers are the most relevant near-term developments. Initial deliberations will signal the direction of travel well before final standards are issued.

2. Document your judgment positions. For any tokenized deposit or tokenized equity position your organization holds or expects to hold, establish a written accounting policy that identifies the classification chosen, the standard applied by analogy, and the rationale. When authoritative guidance eventually arrives, you want to demonstrate that your position was reasoned — not arbitrary.

3. Build flexible infrastructure. The controllers who struggled most with ASU 2023-08 were those whose accounting systems couldn't support continuous fair value measurement. The same dynamic will play out with tokenized assets. Systems that can ingest on-chain data, reconcile across ledgers, and support real-time fair value measurement are not optional preparation — they are the baseline requirement for operating in the capital markets environment that is being built right now.

The bottom line

US GAAP crypto accounting is more structured than it was two years ago — but it still requires significant judgment, strong documentation, and systems capable of supporting ASC 820 fair value measurement, ASU 2023-08 disclosures, and SAB 122 custody treatment.

Controllers who fare best in audits have three things in common:

  1. Explicit, documented classification decisions for each asset type they hold
  2. A consistent, defensible fair value measurement process — assessed at least monthly
  3. A complete audit trail from on-chain transaction to posted journal entry

If your current tooling can't support all three, that's where to start.

Frequently asked questions

How do you account for cryptocurrency under GAAP?

Under US GAAP, most crypto assets are measured at fair value through net income each reporting period under ASU 2023-08. Controllers must classify each asset, apply ASC 820 pricing, and recognize gains and losses on the income statement. Assets outside ASU 2023-08 scope still follow the ASC 350 intangible asset model.

How are digital assets classified under US GAAP?

Most digital assets are classified as intangible assets under ASC 350. ASU 2023-08 requires fair value measurement for fungible, cryptographically secured assets recorded on a distributed ledger. Stablecoins, NFTs, wrapped tokens, and issuer-held assets fall outside that scope and require separate classification judgment.

What is ASU 2023-08 and how does it affect crypto accounting?

ASU 2023-08 requires companies to measure in-scope crypto assets at fair value each reporting period, with gains and losses flowing through net income. It eliminates the asymmetric impairment-only model under legacy ASC 350. The standard is effective for fiscal years beginning after December 15, 2024, with early adoption available.

How are stablecoins classified under GAAP?

Stablecoin classification depends on the asset's structure. Fiat-backed stablecoins like USDC are often treated as cash equivalents or receivables. Algorithmic or partially-backed stablecoins typically fall under ASC 350. No authoritative guidance exists specifically for stablecoins, so classification requires documented judgment and defensible reasoning.

What are the crypto disclosure requirements under ASU 2023-08?

Controllers must disclose the nature and composition of crypto holdings by significant type, cost basis and fair value, gains and losses recognized during the period, any restrictions on holdings, and the fair value inputs and methods used. Disclosures should align with the Level 1, 2, or 3 hierarchy under ASC 820.

What crypto accounting gaps remain under US GAAP?

Significant gaps remain for DeFi activity, staking rewards, NFTs, and intercompany crypto transfers. No specific guidance exists for liquidity pool income or lending protocol returns. Controllers are applying income recognition analogies with limited consistency. FASB has acknowledged these gaps and indicated further standard-setting is under consideration.

Related posts