ASC 350-60: Fair Value Accounting for Crypto, and the Tax Gap It Creates

The prior approach treated most crypto holdings as indefinite-lived intangible assets, which meant they sat on the books at cost and could only be written down through impairment if the price dropped, with no path back up to fair value even after a full recovery, until the asset was actually sold. The newer standard replaces that with fair value measurement each period for qualifying assets, so both increases and decreases in value now flow through net income as they happen, giving a far more honest picture of what a company's crypto holdings are actually worth on any given reporting date.

The scope is narrower than every digital asset a company might hold: it generally covers fungible crypto assets that exist on a blockchain or similar distributed ledger, are secured through cryptography, and don't grant the holder enforceable rights to underlying goods, services, or other assets. That scope generally covers something like Bitcoin or Ethereum held as an investment, but it doesn't automatically extend to every digital asset a company might touch, including certain wrapped or tokenized instruments, non-fungible tokens, and assets a company or a related party created itself. Confirm which specific holdings actually fall inside the scope before assuming this treatment applies uniformly across everything labeled crypto on your balance sheet.

Test each holding against these scope criteria:

• The asset is fungible, so one unit is interchangeable with another rather than unique like a non-fungible token.
• It exists on a blockchain or similar distributed ledger, rather than in a private database your company controls.
• It is secured through cryptography, which is part of what defines a qualifying crypto asset.
• It doesn't give the holder enforceable rights to underlying goods, services or other assets, which can exclude some wrapped or tokenized instruments.
• It wasn't created by your company or a related party.

For federal tax purposes, crypto is treated as property, not currency, which means gain or loss is recognized only when you actually dispose of it, selling it, spending it, or exchanging it for a different asset, not simply because its market value moved during a reporting period. That means an unrealized gain that shows up in your book net income under the fair value model has no matching taxable event yet, and won't until an actual disposal happens, which is exactly the kind of temporary difference that deferred tax accounting exists to capture.

An unrealized fair value gain on qualifying crypto holdings increases book income now, while the corresponding tax liability won't arise until a future disposal, so the difference between your book basis, now at fair value, and your tax basis, still at original cost, needs a deferred tax liability recorded against it. This is a newer, and for a lot of companies unfamiliar, intersection between two standards that used to rarely interact this directly: the fair value model driving book volatility that ASC 740's deferred tax framework then has to track and reconcile every period the fair value changes.

Every disposal, including spending crypto to pay for something or swapping one token for another, is its own taxable event requiring its own basis and gain or loss calculation, regardless of how the fair value accounting treats the holding on your books in that same period. Keeping tax-basis lot tracking and book fair value tracking as two clearly separate systems, rather than assuming one number feeds cleanly into the other, is what keeps your deferred tax calculation accurate instead of quietly drifting out of sync with your actual disposal activity. A small, frequently traded position can generate more of this reconciliation work than a much larger position that simply sits untouched for the whole year.

For example, imagine one token that sits untouched all year and another that the team swaps or spends every few weeks. The idle holding needs only a fair value mark and a deferred tax update, while the active one needs a basis and gain calculation for every disposal. A common mistake is using the fair value balance as the tax basis, which hides realized gains and losses. The fix is a lot-level tax register kept apart from the book ledger and reconciled each period, so the deferred tax liability matches the gap between the two. As a decision rule, whenever a holding changes hands, log its basis and the disposal details that same day.