ASU 2023-08 crypto changed crypto accounting fast, but many treasury teams still treat it like a pricing update. That misses the real issue. If our wallets, subledger, and policy memo don’t line up, the disclosure note falls apart before the fair value entry does.
By April 2026, the rule is live for all covered reporters. So the question isn’t whether we adopt. It’s whether we can defend the numbers in close, in audit, and in the board deck.
What ASU 2023-08 changed, and what we now have to disclose
Under ASU 2023-08, qualifying crypto assets move to fair value through net income. They also sit separately from other intangible assets on the balance sheet. The rule applies only when the asset clears all scope tests in ASC 350-60, which include fungibility, blockchain recording, cryptographic security, and no enforceable rights to other assets or services.
That last point trips people up. Native BTC or ETH may fit. Wrapped assets, some stablecoins, and some receipt-style tokens may not. If we hold those, we need a scope memo before we touch the disclosure table. The full ASU 2023-08 text and the AICPA summary of ASU 2023-08 are still the cleanest starting points.
For interim and annual reporting, we disclose significant holdings by name, units, cost basis, and fair value. Less significant holdings can be grouped. Annual reporting goes further. We also disclose the cost basis method, a rollforward of activity, and any sale restrictions, such as lockups or other contractual limits.
Implementation questions haven’t stopped. There hasn’t been a major new ASU on this topic since the original standard, but the Deloitte implementation FAQ has helped teams work through scope and example disclosures.
If the unit count is wrong, the fair value disclosure is wrong.
That’s why the accounting standard and the wallet data have to meet in the same place.
The disclosure checklist we use before close
We keep the checklist short because close teams don’t need theory. They need items that tie to the ledger, the explorer, and the note.
Here is the core framework we use:
| Disclosure area | What we verify | Common failure |
|---|---|---|
| Scope | Each token passes or fails ASC 350-60 | Wrapped or issued assets mixed with in-scope coins |
| Units held | Wallet and exchange balances tie by cutoff | Missing bridge receipts or double-counted internal transfers |
| Fair value | Pricing source and principal market are documented | Back-solving price from the wrong market |
| Cost basis | Method is consistent and audit-ready | FIFO in one tool, specific ID in another |
| Rollforward | Additions, disposals, gains, and losses reconcile | Buys, swaps, and staking events collapsed badly |
| Restrictions | Lockups and sale limits are captured | Treasury forgets contract-level restrictions |
The hardest part is never the table. It’s the data feed. If we bridge ETH from Arbitrum to Base, receive WETH, unwrap later, then move part to Coinbase, that can look like four unrelated events in the subledger. The economic story is one treasury flow. The ledger story can become noise. That’s why we build multi-chain crypto accounting strategies into the disclosure process, not after it.
We also test edge cases before quarter-end. If treasury holds WBTC, wETH, or bridged USDC, we review Accounting failed bridges and wrapped assets because one bad mapping can overstate both holdings and income. If treasury holds stETH, rETH, or cbETH, we review ASU 2023-08 scope for liquid staking tokens because fair value only helps after scope is settled.
Tooling matters, but only if the logic is clean. CoinTracker can help with intake. Cryptio and Tres Finance can support crypto subledger management. QuickBooks Online can still be the general ledger. However, none of them will fix bad wallet ownership, bad cutoff rules, or a missing valuation policy under ASC 820.
We also separate book from tax. ASU 2023-08 changes financial reporting, not IRS treatment. So annual disclosures need one cost basis method for book, while tax workpapers may still need separate support for broker reporting and transfer history.
Where treasury teams still blow this, especially in Web3
This checklist isn’t only for public filers with simple wallets. It supports Web3 accounting, DeFi accounting, digital asset accounting, blockchain accounting, crypto bookkeeping, Web3 bookkeeping, token project bookkeeping, crypto startup accounting, and crypto bookkeeping for startups. It also drives on-chain reconciliation, multi-chain reconciliation, cross-chain accounting, DEX reconciliation, L2 accounting, crypto treasury reconciliation, crypto financial reporting, and wallet reconciliation services.
The same control stack supports staking accounting, airdrop accounting, token accounting, stablecoin accounting, DeFi yield farming accounting, and the ugly question of how to account for staking rewards. If a team holds ETH on Ethereum, uses Uniswap, bridges to Base, and restakes on Arbitrum, the note disclosure only works if those flows reconcile before close.
Regulated operators have another layer. Money transmitter accounting, MTL accounting, MSB accounting, crypto accounting for money transmitters, and stablecoin treasury management all require clean separation between corporate treasury and customer obligations. FinCEN expectations and state MTL rules don’t care that a bridge was hard to parse.
That matters whether we need crypto fund accounting, crypto controller services, or fractional CFO crypto support. A good cryptocurrency accounting firm, or even the late-night search for a rypto accountant, should know when GAAP crypto accounting and IFRS digital asset reporting diverge, and where ASU 2023-08 stops applying.
The strongest disclosure note starts with boring work. We classify each asset. We prove wallet ownership. We tie units to source data. Then we mark the right assets to fair value.
If our team still closes from wallet screenshots and CSV dumps, the problem isn’t disclosure drafting. The problem is control.
Book a free consultation with us, and we’ll help clean up the policy, reconciliation flow, and disclosure process before the next close.