The close got harder once crypto moved to fair value. In crypto accounting, ASU 2023-08 disclosures look clean on paper, but they fail fast when wallet balances, cost basis, and restrictions do not tie out.
By May 2026, most companies with corporate Bitcoin or Ether have already felt that pain. We need a disclosure package that holds up in audit, board review, and lender conversations, not a pile of exchange exports and screenshots. The template matters, but the support behind it matters more.
What ASU 2023-08 changed for corporate holders
ASU 2023-08 moved qualifying crypto assets into a fair value model under ASC 350-60. If the asset is fungible, secured on a blockchain, and does not give the holder enforceable rights to other assets or services, it is usually in scope. Bitcoin and Ether are the easy examples. Most stablecoins are not, because their legal rights can push them outside the rule.
As of May 2026, there have been no major changes to the standard since issuance. The core rule still requires fair value each reporting period, gains and losses through net income, and separate balance sheet presentation for in-scope crypto assets. The source rule is in FASB’s ASU 2023-08 text, and AICPA’s overview of the standard is a solid companion.
For interim and annual periods, the note needs more than a year-end fair value number. We disclose each significant holding by name, units, cost basis, and fair value. We also aggregate non-significant holdings, disclose restrictions, and explain where gains and losses hit the income statement. Annual reporting adds a rollforward and the cost basis method. Texas CPA’s summary of quarterly and annual items lays those items out well.
The note is not the hard part. Proving the units, ownership, cost basis, and restrictions behind the note is the hard part.
That is why ASU 2023-08 disclosures sit inside broader Web3 accounting, DeFi accounting, digital asset accounting, and blockchain accounting. They also feed straight into crypto financial reporting, GAAP crypto accounting, and, for some groups, separate IFRS digital asset reporting packages.
A disclosure template that works in the real close
A useful template has to match how finance teams actually close the books. We usually keep the interim note simple, then attach a support pack with wallet rollforwards, pricing support, restriction memos, and tie-outs to the subledger.
Here is a practical example for the note itself.
| Significant crypto asset | Units held | Cost basis | Fair value at period end | Restriction |
|---|---|---|---|---|
| Bitcoin | 125.00 | $6,000,000 | $8,125,000 | None |
| Ether | 2,000.00 | $4,400,000 | $5,200,000 | 400 ETH locked as validator collateral through 9/30/2026 |
| Non-significant holdings, aggregated | N/A | $650,000 | $710,000 | None |
That table covers the fields readers expect first. Then we add short prose that states the measurement basis, the income statement line used for remeasurement gains and losses, and the ASC 820 fair value level. For large liquid assets priced on Coinbase, Kraken, or another active market, Level 1 is common. If pricing is less direct, we document the hierarchy choice and keep the evidence.
Annual filings need one more layer. We add a rollforward that shows beginning carrying value, additions, dispositions, fair value changes recorded in earnings, and ending carrying value. We also state the cost basis method, usually FIFO or specific identification. If crypto is received as customer consideration and sold almost immediately in the ordinary course, the annual rollforward can narrow, but the policy memo still needs to say why.
This is where token accounting meets disclosure writing. If the treasury also receives rewards, wrapped assets, or treasury airdrops, the template should separate those sources in the support file even if the note stays aggregated. Airdrop accounting, staking accounting, and stablecoin accounting often affect the same month-end package. So do crypto subledger management and crypto treasury reconciliation.
Where corporate crypto notes usually break
The first break point is on-chain data. A team bridges ETH from Arbitrum to Base, the subledger misses the destination wallet, and quarter-end units no longer match the note. That is an on-chain reconciliation failure, but it also becomes a disclosure failure. We see the same thing with Solana staking accounts, Uniswap LP exits, and treasury wallets that were never tagged by legal entity or purpose.
This is why multi-chain reconciliation, cross-chain accounting, DEX reconciliation, and L2 accounting are not side topics. They drive the numbers in the note. If Ethereum, Arbitrum, Base, and Solana all feed one corporate treasury, the close needs a traceable position report by asset, wallet, entity, and date. CSVs rarely do that well. Tools like CoinTracker, Cryptio, Tres Finance, and QuickBooks Online can help, but only if the mapping rules are right.
Staking adds a second problem. Founders still ask us how to account for staking rewards, because reward timestamps, dominion and control, and later fair value moves do not land on the same day. IRS Revenue Ruling 2023-14 addresses tax timing for staking income, while the books still need a clean month-end cutoff and later fair value remeasurement. Our staking reward cutoff guide covers that timing issue, and our piece on Web3 token lockup accounting addresses the restriction side when tokens are locked, vested, or subject to staged unlocks.
Then there are operating models that need extra schedules. Money transmitter accounting, MTL accounting, and MSB accounting do not stop at fair value. If you hold customer stablecoins, crypto accounting for money transmitters has to separate corporate treasury from customer obligations, line up with FinCEN MSB rules, and respect state-level MTL requirements. Stablecoin treasury management adds another layer because reserve assets, customer flows, and company-owned tokens cannot be mixed. That is true even when the ASU note only covers in-scope assets.
For many teams, this spills into DeFi yield farming accounting, token accounting, and wallet reconciliation services. It also hits crypto bookkeeping, Web3 bookkeeping, crypto bookkeeping for startups, and token project bookkeeping long before quarter-end.
The support behind the note matters as much as the table
We build the disclosure pack backward from audit evidence. First, we confirm wallet ownership and legal entity mapping. Next, we run wallet-level rollforwards and match them to the subledger. Then we lock price sources, timestamps, and cost basis logic. Only after that do we draft the note.
That process matters for crypto startup accounting and crypto fund accounting alike. A founder treasury, a protocol foundation, and a payments company do not use the same template. A fractional CFO crypto workflow may own materiality, covenants, and board reporting, while crypto controller services own close checklists and support files. When the books are messy, a generic bookkeeper will not fix it. Plenty of founders start by searching for a “rypto accountant” after midnight; what they need is a cryptocurrency accounting firm that can tie the wallets to the ledger and the ledger to the disclosure.
We also keep adjacent reporting in view. If broker reporting or tax basis support is in the same stack, our 2026 Form 1099-DA guide helps separate book treatment from tax reporting. If the team is still building controls around fair value, our guide to ASU 2023-08 fair value controls is the right next read. For teams setting up close evidence, fair value evidence examples are useful because they show the exact support auditors ask for.
The practical goal is simple. We want one disclosure file that ties to the trial balance, the subledger, and the wallets without manual guesswork. That is the difference between a note that survives review and one that gets rewritten at the last minute.
Building Audit-Ready Crypto Disclosures for Future Success
ASU 2023-08 disclosures are only as strong as the data under them. If the units, restrictions, pricing, and activity are clean, the note is straightforward. If they are not, the disclosure becomes the place where every weak policy shows up at once.
We see that across treasury companies, token issuers, DeFi teams, and licensed payment businesses. The fix is not a prettier template. The fix is better classification, tighter reconciliation, and audit-ready support before quarter-end.
If your corporate crypto note still depends on exchange exports, manual wallet tagging, or last-minute fair value spreadsheets, book a free consultation with us.
