Key takeaways
- →ASU 2023-08 (ASC 350-60) requires in-scope crypto to be measured at fair value every period, with gains and losses in net income — effective for fiscal years beginning after Dec 15, 2024 (Jan 1, 2025 for calendar-year entities).
- →In scope: fungible, blockchain-based, cryptographically secured tokens not issued by the entity and conveying no rights to other assets. Excluded: NFTs, the entity's own tokens, and many wrapped tokens and fiat-backed stablecoins.
- →Disclosures are granular: name, cost basis, fair value, and units held for each significant holding at interim and annual dates, plus the cost-basis method and a rollforward annually.
- →On-chain accounting is a distinct discipline. Staking, rebasing, bridges, and cost-basis selection break naive tooling because the chain records mechanical events while GAAP cares about economic substance.
- →Audit-ready crypto books require a reconciled subledger that ties to the GL, AI for high-volume classification, and senior accountants owning every judgment and disclosure call.
Crypto accounting under GAAP changed fundamentally on January 1, 2025. Under FASB's ASU 2023-08, in-scope crypto assets are no longer parked at the lower of cost or impaired value — they are remeasured to fair value every reporting period, with the gains and losses flowing straight through net income. For any business holding bitcoin, ether, or other qualifying tokens on its balance sheet, the old books may no longer comply, and the disclosures are materially more demanding. This guide is the practitioner's view: what the standard actually requires, why on-chain accounting is a distinct discipline rather than a software plug-in, and how to keep your ledger audit-ready.
Most articles on this topic are written by software vendors selling a reconciliation tool. We come at it differently. A tool can ingest a wallet; it cannot make the judgment call on whether an auto-compounding staking position, a rebasing token, or a cross-chain bridge transfer is a taxable disposal, a cost-basis event, or a non-event. That is senior accounting work — and it is where audit-ready crypto books are won or lost.
What changed under ASU 2023-08 (and why your old crypto books may no longer comply)
Before 2025, U.S. GAAP forced most companies to treat crypto as an indefinite-lived intangible asset. That meant a one-way ratchet: you wrote the asset down when its price dropped below cost, but you could never write it back up, even after a full recovery. The Journal of Accountancy described the model bluntly — it "recognizes only decreases, not increases, in cryptoasset values." A company that bought bitcoin at $30,000, watched it fall to $16,000, then saw it recover to $90,000 still carried it at $16,000 on the balance sheet. The number was both wrong and expensive to maintain, requiring constant impairment monitoring throughout each period.
ASU 2023-08 effective date for calendar-year entities (fiscal years beginning after Dec 15, 2024). Early adoption was permitted, and many holders adopted in 2024.
Source: FASB / The CPA Journal, 2024
ASU 2023-08 created a new subtopic, ASC 350-60, and flipped the model. In-scope crypto is now measured at fair value under ASC 820 each period, with remeasurement gains and losses recognized in net income — not buried in equity, not deferred. Crypto assets are also presented separately from other intangibles on the balance sheet. (The standard's cash-flow guidance is narrower than many assume: crypto received as noncash consideration in the ordinary course of business and converted to cash nearly immediately is classified as operating; crypto held as an investment generally flows through investing.) If your books still carry digital assets at impaired cost, or commingle them with goodwill and other intangibles, they no longer reflect current GAAP.
Fair value vs cost-less-impairment: the new measurement model explained
The mechanical difference is straightforward; the operational difference is not. Under the old model you needed a process to detect impairment. Under ASU 2023-08 fair value crypto accounting you need a defensible fair value at every measurement date for every in-scope asset — sourced from a principal market under ASC 820, documented, and tied to units you can prove you held. The table below shows why the same transaction history produces very different financial statements.
| Dimension | Old model (cost-less-impairment) | New model (ASU 2023-08 / ASC 350-60) |
|---|---|---|
| Measurement | Cost, written down for impairment | Fair value each reporting period (ASC 820) |
| Recoveries | Never recognized (write-ups prohibited) | Recognized in net income |
| Income statement | Impairment losses only | Both gains and losses each period |
| Balance sheet | Grouped with other intangibles | Presented separately from other intangibles |
| Ongoing burden | Continuous impairment monitoring | Period-end fair value + unit substantiation |
| Disclosure | Limited | Name, cost basis, fair value, units per significant holding |
Note what the new model demands of the ledger, not just the policy. Recognizing gains and losses correctly requires accurate cost basis by lot, a complete and reconciled record of units held at each date, and a fair value source you can defend to an auditor. None of that is automatic when your activity spans a dozen wallets, three exchanges, and a handful of DeFi protocols.
Why on-chain accounting is its own discipline
Here is the claim most vendor content avoids: on-chain accounting for funds and operating companies is a separate discipline from fiat bookkeeping, not a feature you bolt onto QuickBooks. Fiat reconciliation has a trusted third party — the bank — that produces an authoritative statement. On-chain, the blockchain is the source of truth, but it is pseudonymous, irreversible, and indifferent to your chart of accounts. There is no statement; there is a ledger of cryptographic events you must interpret.
Public companies now hold bitcoin as a treasury asset — every one of them inside ASU 2023-08's scope, with new fair-value and disclosure obligations each reporting period.
Source: CryptoBriefing, 2025
Four realities make this work distinct. First, multi-chain: a single treasury may transact across Ethereum, Solana, Bitcoin, and several L2s, each with different address formats, gas tokens, and finality rules. Second, DeFi: liquidity provision, lending, and staking generate continuous economic events the chain records as raw transfers with no labels. Third, wallet sprawl: self-custody means dozens of addresses with no central authority to confirm ownership. Fourth, fair value sourcing: thinly traded tokens may have no clean principal market, forcing genuine ASC 820 judgment. Software can surface these; it cannot resolve them.
The hardest reconciliation edge cases: staking, rebasing, bridges, cost basis
DeFi wallet reconciliation breaks naive tooling on a predictable set of edge cases. These are exactly the transactions where an automated classifier guesses — and where a senior accountant's judgment determines whether your books survive an audit.
- 01Auto-compounding staking. Rewards accrue and re-stake without a discrete on-chain transfer. The chain shows a growing balance with no clear acquisition events — yet each accrual has a cost basis and a fair value at receipt that the subledger must capture.
- 02Rebasing tokens. The token supply in your wallet changes algorithmically. Your unit count moves without a buy or sell, so a tool that infers acquisitions from balance deltas will fabricate phantom transactions unless someone configures the rebase logic correctly.
- 03Cross-chain bridges. Moving an asset from one chain to another typically burns it on the source chain and mints a wrapped version on the destination. To a classifier this looks like a disposal plus a purchase; in substance it is usually a transfer of the same economic position — a distinction that materially changes reported gains.
- 04Cost-basis method selection. FIFO, specific identification, and average cost produce different gains, different disclosures, and different tax outcomes. The method must be chosen deliberately, applied consistently, and disclosed annually — it is a controller-grade decision, not a software default.
From wallet to ledger: building a crypto subledger that ties to your GL
The deliverable that makes everything else possible is a crypto subledger to general ledger mapping that actually ties out. A subledger that doesn't reconcile to the GL is just a spreadsheet; a GL with no subledger detail can't support the ASU 2023-08 disclosures. The bridge between them is where digital-asset bookkeeping becomes accounting.
- 01Complete address inventory. Every wallet, exchange account, and protocol position the entity controls — confirmed, not assumed. Missing one address means an incomplete ledger.
- 02Raw on-chain ingestion + classification. Pull every transaction across every chain, then classify each into accounting events: acquisition, disposal, transfer, reward, fee, fair-value remeasurement.
- 03Cost-basis tracking by lot. Maintain FIFO or specific-ID lots so each disposal pulls the correct basis and each holding carries a defensible fair value.
- 04Period-end fair value. Mark in-scope assets to fair value under ASC 820, documenting the principal market and source.
- 05Tie-out to the GL. Roll the subledger into journal entries that reconcile to the trial balance — units, cost basis, fair value, and gain/loss all agree.
This is precisely the scope of our crypto bookkeeping and accounting work: we reconcile wallets, exchanges, and DeFi across any chain into one clean, GAAP-aligned ledger that ties to your GL. For the strategy layer above the ledger — treasury policy, stablecoin structuring, and operating model — see our companion piece, the Crypto CFO playbook for 2026.
ASU 2023-08 disclosure requirements you must be ready to produce
The disclosures are where many teams discover their books aren't ready. ASU 2023-08 requires granular, holding-level detail at interim and annual dates — information you can only produce if the subledger has been maintained correctly all year. You cannot reconstruct it from a year-end balance snapshot.
| Disclosure item | Interim periods | Annual periods |
|---|---|---|
| Name of each significant crypto asset | Required | Required |
| Cost basis per significant holding | Required | Required |
| Fair value per significant holding | Required | Required |
| Number of units held | Required | Required |
| Aggregated cost / fair value of non-significant holdings | Required | Required |
| Cost-basis method used (FIFO, specific-ID, average, other) | — | Required |
| Rollforward (opening to closing balances) | — | Required |
| Income-statement line where gains/losses sit | — | Required |
ASU 2023-08 requires the name, cost basis, fair value, and units held for every significant crypto holding — at both interim and annual reporting dates.
Source: Deloitte Roadmap / ASC 350-60-50, 2024
How AI-augmented, senior-led crypto accounting under GAAP stays audit-ready
The volume problem is real — a single active DeFi treasury can generate tens of thousands of on-chain events a quarter — but volume is not the hard part. Judgment is. The right operating model uses AI exactly where it is strong and senior people exactly where they are irreplaceable.
At OpsFi, AI runs the high-volume first pass: ingesting every transaction across every chain, clustering wallets, and proposing a classification for each event at a speed no human team can match. Then experienced accountants own the judgment — the rebase, the bridge, the staking accrual, the cost-basis method, and the ASU 2023-08 fair-value and disclosure calls. This is the human-in-the-loop model done properly: AI makes senior practitioners faster, more thorough, and more consistent; it does not replace them with juniors or with raw automation. Every number that reaches your financials has been owned by someone who can defend it to an auditor.
Auditors are systematically challenged to prove existence and ownership of on-chain assets — regulators ask how a firm knows a wallet belongs to the company and not, say, the CFO personally, and demand evidence of controls over private-key custody. Audit teams often don't have the answers regulators are looking for.
In-house vs specialist on-chain accounting partner: how to choose
On-chain accounting requires a rare combination: blockchain fluency and controller-grade GAAP rigor. Most in-house teams have one or the other, and most generalist firms have neither. The decision usually comes down to transaction complexity, the proximity of an audit or raise, and whether your people actually understand DeFi mechanics — not just spot bitcoin.
| Factor | In-house generalist | Specialist on-chain partner |
|---|---|---|
| DeFi / multi-chain fluency | Often limited | Native — any chain, any protocol |
| GAAP / ASU 2023-08 judgment | Varies | Controller-grade, standard-aligned |
| High-volume classification | Manual or basic tooling | AI first pass + senior review |
| Audit readiness | Reactive at year-end | Maintained every period |
| Cost at scale | Fixed senior headcount | Senior expertise without full-time overhead |
If your crypto activity is occasional and simple, a capable in-house controller may suffice. If you run an active treasury, transact across chains and DeFi, or are heading into an audit or a raise, a specialist partner that pairs on-chain fluency with senior accounting judgment is the lower-risk path — and the one auditors find far easier to work with. For audit firms themselves facing crypto-heavy engagements without bench depth, see our work supporting dedicated audit teams.
The bottom line
Crypto accounting under GAAP is now a fair-value discipline with real disclosure teeth. The mechanics of ASU 2023-08 are knowable; the hard part is a clean, reconciled, audit-ready ledger built from messy on-chain reality. That takes blockchain-native skill, controller-grade rigor, and AI leverage pointed at volume — with senior people owning every judgment call.
Sources
- 01FASB's New Guidance on Accounting for Crypto Assets — The CPA Journal
- 02Heads Up — FASB Issues Final Standard on Crypto Assets (ASU 2023-08) — Deloitte DART
- 03ASU 2023-08 Clarifies Accounting for Certain Crypto Assets — Grant Thornton
- 04New Crypto Accounting Rules May Spur Early Adoption — Journal of Accountancy
- 056.3 Disclosures About Crypto Assets Within the Scope of ASU 2023-08 — Deloitte Roadmap (ASC 350-60)
- 06Auditors of Crypto Assets Struggle to Satisfy PCAOB — CFO.com
- 07Top 100 Public Bitcoin Treasury Companies Each Hold Over 100 BTC — CryptoBriefing
- 08Cryptoasset Auditing and Attestation: What's Changed and Why It Matters — NJCPA
FAQ
Frequently asked questions
When does ASU 2023-08 take effect?+
For fiscal years beginning after December 15, 2024 — January 1, 2025 for calendar-year entities — including interim periods within those years. The standard applies to all entities, and early adoption was permitted, so many crypto holders adopted in 2024 to recognize previously understated fair value.
Which crypto assets are in scope, and what's excluded?+
In scope: assets that meet the intangible-asset definition, grant no enforceable rights to other goods or services, reside on a blockchain, are secured by cryptography, are fungible, and are not issued by the reporting entity or its related parties. Excluded: NFTs (non-fungible), an entity's own issued tokens, and many wrapped tokens and fiat-backed stablecoins whose structure conveys rights to underlying assets.
How is the fair value model different from the old cost-less-impairment approach?+
Previously, crypto was an indefinite-lived intangible written down for impairment and never written back up. Under ASU 2023-08 it is remeasured to fair value under ASC 820 every reporting period, with both gains and losses recognized in net income, and presented separately from other intangibles on the balance sheet.
What exactly must I disclose under ASU 2023-08?+
At interim and annual dates: the name, cost basis, fair value, and number of units held for each significant crypto holding, plus aggregated figures for non-significant holdings. Annually you also disclose the cost-basis method (FIFO, specific identification, average cost, or other), a rollforward of activity, and the income-statement line where gains and losses are reported.
Why can't accounting software handle crypto reconciliation on its own?+
Software ingests transactions well but guesses on the events that matter most — auto-compounding staking, rebasing tokens, cross-chain bridges, and cost-basis method selection. The blockchain records mechanical events; GAAP cares about economic substance. Resolving that gap, and defending it to an auditor, requires senior human judgment, not a default classification.
What makes crypto books hard to audit?+
Auditors must prove existence and ownership of pseudonymous on-chain assets and verify controls over private-key custody — areas where many audit teams struggle to satisfy regulators. A signed address inventory, documented custody controls, and a subledger that reconciles to the GL every period are what make a crypto audit routine rather than painful.