Holding BTC and WBTC in the same treasury can produce two different book answers. That is the core problem in wrapped token accounting, and it’s now a live issue in Web3 accounting as teams close 2026 periods.
ASU 2023-08 moved many native crypto assets to fair value. However, it did not pull most wrapped tokens along with them. If we treat every wrapped asset like native BTC or ETH, our close can break fast.
Why most wrapped tokens miss ASU 2023-08
Under FASB’s ASU 2023-08 text, an asset has to clear six scope tests. One of the most important is easy to miss: the token can’t give the holder enforceable rights to underlying goods, services, or other assets. That is where WBTC, wETH, and many wrapped stablecoins usually fall out.
A wrapped token often points back to something else. WBTC traces to BTC held with a custodian. wETH usually gives us a path back to native ETH through the wrapper contract. Some bridged USDC versions add another layer of redemption or settlement rights. So while the price exposure may look the same, the legal form often is not.
There is no blanket rule that says all wrapped tokens are out. We still test each one. Some instruments could land outside ASC 350 entirely if the holder’s rights look more like a financial asset or another contractual claim. That is why we write a memo per token, not per chain.
By April 2026, this is no longer theory. A lot of teams have already learned that GAAP crypto accounting now splits native and wrapped holdings into different lanes. A practical ASU 2023-08 summary lands in the same place, wrapped assets are often out of scope and need older rules or another model based on their terms.
This quick comparison helps:
| Asset | Likely ASU 2023-08 scope | Common outcome |
|---|---|---|
| BTC or ETH | Usually in scope | Fair value through net income |
| WBTC or wETH | Usually out of scope | Often ASC 350 or other case-by-case model |
| Wrapped or bridged stablecoins | Case by case | Depends on redemption rights and structure |
If we hold BTC and WBTC side by side, one may remeasure each period while the other may not. That feels wrong to founders, but it is exactly why the scope memo matters. It also affects disclosures. In-scope assets get fair value presentation and rollforward disclosures, while out-of-scope wrapped assets still need a clear policy note. For global groups, IFRS digital asset reporting can land differently again.
What wrapped token accounting looks like in a real close
The mess usually starts in the subledger, not in the memo. We might bridge ETH from Arbitrum to Base, receive WETH, deploy it on Uniswap, unwrap later, and then send funds to Coinbase or Kraken. Economically, that may be treasury movement plus protocol activity. Operationally, it can explode into ten wallet events.
In one close, we may need to post a bridge out, a destination-chain receipt, a wrap event, gas on both chains, and later LP or collateral activity. None of that is revenue by default. If the system posts one leg as income, month-end will tie to the explorer but not to the economics.
If native ETH and WETH sit in the same account mapping, one bad rule can misstate both value and income.
That is why on-chain reconciliation matters as much as the accounting conclusion. We need to collapse internal transfers, tag wrap and unwrap events, separate gas, and preserve lot history. Otherwise multi-chain reconciliation, cross-chain accounting, DEX reconciliation, L2 accounting, and crypto treasury reconciliation all start drifting at once.
We also need to define the unit of account. Are we tracking the wrapped token, the underlying asset claim, or both for control purposes? If that answer changes between Ethereum, Solana, and Base, the close won’t tie. In DeFi accounting, the wrapper can hide inside an LP token, lending position, or vault share, which makes the legal form even easier to miss.
CoinTracker can help with intake, while Cryptio or Tres Finance can handle crypto subledger management before posting to QuickBooks Online. Still, no tool fixes bad logic. That is why our guide on multi-chain reconciliation challenges matters here. Wrapped token accounting sits inside broader digital asset accounting, blockchain accounting, and crypto financial reporting. Teams that skip wallet reconciliation services usually find the error at month-end, not when it starts.
The controls that keep wrapped assets from blowing up the books
We don’t fix this with one journal entry. We fix it with a policy stack. First, we document which tokens are in scope under ASU 2023-08 and which are not. Next, we map each wrapped asset to its custody, redemption terms, pricing source, and expected journal flow. Then we keep book treatment separate from tax treatment, because tax basis doesn’t disappear when fair value changes.
At a minimum, our policy should pin down:
- the legal rights behind each wrapped token
- the pricing source and principal market
- the wallet ownership map
- the journal rules for wrap, unwrap, bridge, and fees
The same control stack supports staking accounting, airdrop accounting, token accounting, stablecoin accounting, and DeFi yield farming accounting. It also answers the founder question we hear all the time, how to account for staking rewards, because the real issue is usually timing, valuation, and wallet ownership.
For operators, this is bigger than close mechanics. Good crypto bookkeeping, crypto bookkeeping for startups, crypto startup accounting, Web3 bookkeeping, and token project bookkeeping all depend on the same clean wallet map. The same is true for stablecoin treasury management, especially when treasury and customer funds sit near each other. If that issue is in play, our guide to stablecoin accounting and compliance is a useful companion.
Regulated businesses need even tighter controls. Money transmitter accounting, MTL accounting, MSB accounting, and crypto accounting for money transmitters all require traceable movement of value, not loose wallet labels. FinCEN and state-level MTL rules won’t care that a bridge contract was hard to parse. They will care whether we can prove who owned what, when, and why.
Tax adds another twist. ASU 2023-08 changes book value, not cost basis. Under IRS 1099-DA reporting and Revenue Procedure 2024-28 account-based basis rules, transfer records still matter when wrapped assets move between brokers and self-custody. That is why 1099-DA transfer statement controls belong in the same conversation.
As companies grow, the staffing question changes too. A founder may start with spreadsheets, then move to a cryptocurrency accounting firm, then add crypto controller services or fractional CFO crypto support. Funds feel the same pressure in crypto fund accounting. If we wait until someone on the team is searching “rypto accountant” after a failed close, we’ve waited too long.
Wrapped token accounting under ASU 2023-08 is a scope problem first, and a data problem second. Native coins may sit at fair value, while wrapped versions may not, even when market exposure looks nearly identical.
If our team is sorting WBTC, wETH, bridged stablecoins, or broken subledger logic, we should book a free consultation now. That is faster than cleaning up a bad year after the audit starts.