Crypto accounting got harder the moment ASU 2023-08 moved many digital assets to fair value. By May 2026, that change is no longer theory. It’s part of live closes, live audits, and live reporting.
For founders and finance leads, the pain point isn’t the headline rule. It’s the evidence underneath it. If we can’t prove a wallet exists, belongs to the reporting entity, and ties cleanly into the ledger, our audit support falls apart fast.
What ASU 2023-08 changed, and what it did not
ASU 2023-08 applies to certain fungible crypto assets that meet a narrow set of criteria. For many teams, that means Bitcoin and Ether are in scope. Some stablecoins may be too, if they meet the rules. The core change is simple: we now measure those assets at fair value each reporting period, with gains and losses in net income.
As of May 2026, the standard is already in effect for fiscal years starting after December 15, 2024. That means 2025 year-end audits already felt the shift, and 2026 interim reporting keeps the pressure on. PwC’s summary of ASU 2023-08 is useful if we need the scope and disclosure rules in one place.
What the update did not do is create a special crypto audit rulebook. Audit evidence for crypto still sits under normal audit standards and ASC 820. For public-company audits, AS 1105 and AS 2501 still matter. In plain English, auditors still need enough support to test ownership, existence, valuation, completeness, and disclosure.
That matters because fair value changes the audit rhythm. Under older GAAP crypto accounting, teams spent time on impairment and historical cost support. Now auditors spend more time on period-end units held, market pricing, restrictions, and whether the reporting entity actually owns what the wallets show.
If our parent company also asks about IFRS digital asset reporting, we can’t assume the answer matches US GAAP. The models can differ, so our crypto financial reporting needs a separate memo rather than a recycled US GAAP conclusion.
Wallet ownership is an accounting question, not a wallet screenshot
The biggest mistake we see is treating wallet control as enough. It isn’t. A private key proves access. It doesn’t always prove ownership for accounting purposes.
Private keys show who can move assets. They do not settle who should report them on the balance sheet.
That point shows up clearly in KPMG’s discussion of wallet control and ownership. A segregated wallet can still hold customer assets. An omnibus wallet can still contain company assets. The legal agreements, custody terms, entity mapping, and operating facts matter more than the wallet label.
This is where digital asset accounting and blockchain accounting stop being buzzwords and start looking like hard close work. We need a wallet register that names the legal entity, chain, purpose, signers, custodian, and general-ledger mapping for every address. That applies whether we hold BTC on Coinbase Custody, ETH on Ethereum, SOL on Solana, or operating cash equivalents in a stablecoin treasury.
For money transmitters, the line is even stricter. Money transmitter accounting, MTL accounting, and MSB accounting all depend on clean separation between customer obligations and house assets. If we run a payments business, crypto accounting for money transmitters has to document beneficial ownership, customer balances, reserve obligations, and restrictions on use. The same goes for stablecoin treasury management, where one mislabeled wallet can distort both cash controls and disclosure.
A real example makes this obvious. We saw a team bridge ETH from Arbitrum to Base at month-end. The explorer showed the asset arrived, but the subledger still carried the old chain location. Because the bridge transaction sat in a suspense bucket, ownership and completeness both looked shaky during review. That’s a multi-chain reconciliation issue, but it also becomes cross-chain accounting, L2 accounting, and crypto treasury reconciliation all at once.
A generic bookkeeper won’t catch that. A cryptocurrency accounting firm should.
Navigating DeFi and Staking: Challenges in Asset Verification
Existence sounds easy because blockchains are public. Then real operations show up.
If we hold native ETH in a treasury wallet, existence support may be straightforward. If we move that ETH into Uniswap, stake it through Coinbase, wrap it on Base, or post it into a DeFi protocol, the audit trail changes. Now we need to prove what asset we hold, where it sits, what rights it carries, and whether the ledger reflects the current position rather than last month’s export.
This is where DeFi accounting, on-chain reconciliation, DEX reconciliation, and Web3 accounting live or die. The same is true for Web3 bookkeeping and token project bookkeeping. A wallet balance alone doesn’t tell auditors whether we hold USDC, LP tokens, a staking derivative, or a claim on assets inside a smart contract.
Staking adds another layer. The question isn’t only how to account for staking rewards. We also need to prove when rewards were earned, whether they were claimable, and which wallet or validator address received them. That is why staking accounting often fails when teams rely on exchange CSVs without tying them back to validator reports, chain data, and the general ledger.
The same pattern hits DeFi yield farming accounting, airdrop accounting, token accounting, and stablecoin accounting. Airdrops may appear on-chain before anyone updates the ledger. Yield tokens may accrue daily while the close process runs monthly. Wrapped assets may move across chains without a clean cost basis handoff. One missing map between the explorer and the subledger, and the evidence package loses credibility.
We’ve seen founders search for a “rypto accountant” after that kind of mess lands in audit. The search term is funny. The pain isn’t.
This is why wallet reconciliation services matter. If our team uses CoinTracker, Cryptio, Tres Finance, or QuickBooks Online, the tool only helps when the source data, chain mapping, and wallet inventory are right. Crypto bookkeeping for startups breaks when the system treats every inflow as income, every transfer as a disposal, or every smart-contract position as if it were a simple wallet balance.
Fair value support now matters every close, not only at year-end
Because ASU 2023-08 moved in-scope assets to fair value, valuation evidence now sits next to ownership and existence. We need support for the units held, the pricing source, the measurement time, and the principal market policy. Screenshots alone usually don’t cut it.
a practical fair value support checklist highlights the evidence shift well. We need repeatable price capture, exchange selection logic, and workpapers that tie the fair value adjustment into posted journal entries. If we use Coinbase or Kraken quotes, we should document why. If a market is thin, the memo needs more than a hunch.
This is the short version of what auditors usually want:
| Audit area | Strong support | Common failure |
|---|---|---|
| Ownership | Wallet register, signer approvals, custody contracts, entity mapping | Treasury and customer assets mixed in one wallet |
| Existence | Explorer balances, custodian statements, tx hashes, subledger tie-out | Bridged, wrapped, or staked assets missing from the ledger |
| Valuation | Period-end price logs, exchange policy, fair value workpaper | Random screenshots, wrong timestamp, no market selection memo |
| Disclosures | Units, cost basis, restrictions, gain/loss tie-out | Lockups and staking restrictions omitted |
The takeaway is simple. Good evidence isn’t one document. It’s a chain of support that agrees across legal docs, wallets, subledger, and financial statements.
Audit-ready support starts with the month-end close
Most audit problems start months before the auditors arrive. If our monthly close is weak, no memo will save it.
Crypto subledger management has to sit inside the close, not outside it. That means entity-level wallet mapping, repeatable imports, reviewed classifications, and cut-off procedures for pending bridge transfers, failed swaps, gas, and custody movements. It also means assigning real owners inside finance. Otherwise crypto controller services turn into cleanup work, and the cleanup never ends.
This is true across crypto startup accounting and crypto fund accounting. It’s also true for a token issuer with a busy treasury, a DeFi protocol with incentives, or an MSB that settles in stablecoins. In every case, the books improve when we treat on-chain data as a source system that needs controls, not as a pile of exports we sort out later.
Monthly close work gets easier when we build it around professional crypto bookkeeping services instead of year-end rescue work. That’s where crypto bookkeeping, wallet mapping, cost basis policy, and review controls start to hold.
Founders who search for “fractional CFO crypto” help often need something more basic first. They need books that support board reporting, lender questions, and audit evidence in crypto without a fire drill every quarter.
Navigating DeFi and Staking: Challenges in Asset Verification
ASU 2023-08 didn’t invent new audit assertions. It raised the cost of weak ones. When we can’t prove wallet ownership, existence, and fair value with clean support, the audit slows down and the financials lose trust.
The fix is boring, which is why it works. Tight wallet inventories, strong on-chain reconciliation, a controlled subledger, and monthly review beat heroic cleanups every time.
If we want an audit-ready close before the next reporting deadline, we can start with a free consultation through our Web3 and crypto accounting services.
