Token Transferred, But Still on the Balance Sheet? FASB's Crypto Derecognition Reckoning
A company moves 100 bitcoin on-chain. The blockchain is unambiguous: the tokens have left one address and arrived at another. But under US GAAP, the accounting question has barely begun. Was that a sale, a loan, a wrapping operation, or a contribution to a liquidity pool? Which rights were surrendered, which were retained, and which new obligations were assumed? On 19 August 2026, the Financial Accounting Standards Board reached a set of tentative decisions that answer some of those questions in ways that will surprise firms still relying on earlier SEC staff guidance, and that leave others deliberately open until a formal exposure draft is issued. For CFOs, controllers, and auditors with any crypto exposure on their books, these decisions are not a future problem. They are an active accounting policy question right now.
Why the On-Chain Picture Is Never the Whole Story
ASC Subtopic 350-60 currently governs a defined category of fungible crypto assets, including bitcoin and ether. It requires subsequent measurement at fair value, with fair value changes flowing through net income. That much is settled. What is not settled is when an entity stops recognising a crypto asset after transferring it, and what it recognises instead.
The gap exists because blockchain technology and accounting standards were designed with entirely different questions in mind. A blockchain answers: did the token move? Accounting asks: did the entity lose control of an asset, and if so, what replaced it? Those two questions have different answers far more often than practitioners have historically assumed.
Three Transfers, Three Accounting Outcomes
Consider three transactions, each starting with the same on-chain event: crypto leaves Company A's wallet.
In the first, Company A lends 100 bitcoin to Company B for six months. Company B may sell, pledge, or otherwise deploy the bitcoin during the term, but must return 100 bitcoin plus a fee at maturity. Company A receives no token in return, only a contractual right against Company B.
In the second, Company A wraps 100 ether and receives 100 wrapped ether (WETH). Economically, the exposure to ether price movements is similar. But the accounting asset has arguably changed: Company A now holds a token whose value depends on the wrapping protocol's rules, not ether directly.
In the third, Company A contributes 100 ether and an equivalent value of a second ASC 350-60 asset to a two-asset liquidity pool, receiving an LP token. That token represents a proportional claim on a pool whose composition shifts continuously as other users trade through it. When Company A exits, it may receive a different quantity and mix of assets from those originally contributed.
Same starting point. Three fundamentally different residual positions. The accounting treatment for each hinges not on what token arrived on-chain but on the bundle of rights and obligations that exists after the transaction closes.
FASB's August 2026 Tentative Decisions
FASB has been running a project to expand and clarify ASC 350-60 to address these fact patterns. On 19 August 2026, the board continued its deliberations and reached further tentative decisions in two areas: crypto asset lending and the scope of ASC 350-60 itself.
Lending: Lent Assets Stay on the Balance Sheet
This is the decision most likely to require firms to revisit existing accounting policies. For transactions that qualify as crypto asset lending arrangements involving crypto intangible assets, FASB has tentatively decided that the lender should not derecognise the transferred asset. Instead, the asset remains on the balance sheet under ASC 350-60, reclassified as an encumbered asset, measured at fair value, and adjusted to reflect the borrower's credit risk.
That directly diverges from the approach that SEC staff signalled at the 2022 AICPA and CIMA Conference on Current SEC and PCAOB Developments. At that conference, SEC staff indicated they would not object to a treatment under which a lender derecognises the transferred crypto asset, because it no longer controls the asset during the loan term, and recognises a crypto asset loan receivable measured at the fair value of the lent assets. Changes in that fair value would run through net income, and an allowance for credit losses under ASC 326 would be recognised to reflect the borrower's risk.
Under the SEC staff model, the 100 bitcoin leaves the balance sheet and a receivable takes its place. Under FASB's tentative model, the 100 bitcoin stays as an encumbered asset. The blockchain transfer is identical. The income statement and balance sheet presentation are not.
Non-Lending Transfers: ASC 606 Control Model With Crypto-Specific Guidance
For transfers of crypto intangible assets that do not qualify as lending arrangements, FASB has tentatively decided to continue applying the ASC 606 control model, supplemented by crypto-specific implementation guidance still being developed. This matters because the boundary between a lending transaction and a non-lending transfer is not always obvious, particularly for transfers to decentralised protocols.
A direct loan to an identifiable counterparty fits the lending model relatively cleanly. A transfer to a smart-contract protocol, where there is no single identifiable borrower and redemption may be subject to liquidity conditions or protocol governance, raises harder questions. FASB has not yet definitively drawn that boundary, and the staff has been directed to draft a proposed accounting standards update for a written ballot, followed by a 60-day public comment period.
Scope Expansion: Wrapped Tokens and Receipt Tokens
FASB has also tentatively decided to expand the scope of ASC 350-60 to include certain wrapped tokens and receipt tokens, specifically those that give the holder the right to receive another crypto asset that itself falls within ASC 350-60's existing scope. The expansion is conditional on the rights analysis: a wrapped token only enters ASC 350-60's scope if it actually confers a right to the underlying scoped asset. The label "wrapped" does not determine the outcome; the contractual and protocol-level rights do.
This matters practically. If WETH qualifies, it will be measured at fair value with changes in net income, aligned with the treatment of ether itself. If an LP token represents a proportional claim on a changing pool rather than a right to receive a specific scoped asset, it may not qualify, and a different accounting model will apply.
The Classification Boundary That Can Change Everything
There is a further complication that the FASB project highlights, even if it does not resolve it entirely. Not all digital assets are crypto intangible assets. If a digital asset qualifies as a financial asset and falls within the scope of ASC 860, the transfer is accounted for under ASC 860's derecognition framework rather than ASC 606 or ASC 350-60. Two tokens sitting in the same wallet, moving through the same on-chain transaction, could land in entirely different accounting models depending on whether they are classified as intangible assets or financial assets.
This classification question is not new, but FASB's current deliberations make it more urgent. Firms that have applied a single consistent treatment to all crypto transfers need to audit that assumption against each asset's legal and contractual characteristics.
What the Rights Analysis Actually Requires
FASB's tentative framework points toward a consistent analytical sequence that practitioners should apply to any crypto transfer, regardless of how it is labelled on-chain.
The Questions That Drive the Accounting
The core questions are: Can the entity demand the return of the same quantity of the same asset? Against whom is that right enforceable, and is that counterparty identifiable? Is the entity exposed to a specific counterparty's credit risk, or to the risk of a protocol? Does the token received represent a claim on one specific underlying asset, or a proportional interest in a pool whose composition is continuously changing? Can redemption be restricted, suspended, or made conditional by protocol governance?
Holding 100 ether directly is not the same as holding a receivable from a borrower for the return of 100 ether. Both differ from a proportional interest in a shifting liquidity pool. The accounting follows the rights, not the token label, and not the on-chain transaction record.
This is also why the tentative scope expansion of ASC 350-60 to wrapped tokens and receipt tokens does not short-circuit the analysis. It creates a fast path for assets that clearly satisfy the rights criteria, but the rights analysis must happen first.
Practical Implications for Accounting Firms, CFOs, and Auditors
These are tentative decisions. They do not yet change US GAAP. A formal exposure draft with a 60-day comment period will follow, and firms will have an opportunity to shape the final standard through comment letters. That said, the direction of travel is clear enough to require action now, not when the standard is finalised.
Audit and Policy Considerations
Firms that have derecognised lent crypto assets in reliance on the 2022 SEC staff position need to assess whether a policy change will be required when FASB's standard is finalised, and begin modelling the balance sheet and income statement impact of keeping those assets on the books as encumbered assets. The credit risk adjustment on an encumbered asset measured at fair value is a different calculation from an ASC 326 allowance on a receivable, and the difference will affect both earnings and disclosure.
For wrapped tokens and LP tokens, the immediate task is completing the rights analysis for each position. That means going beyond the token name and reviewing the underlying protocol documentation, smart-contract terms, and any off-chain legal agreements to determine what the holder can actually demand, from whom, and under what conditions. Where that analysis is ambiguous, the firm's accounting policy choice and the disclosure around it will be subject to heightened auditor scrutiny.
Auditors should also be raising this with audit committee chairs now. The BDO 2026 audit committee priorities already flagged crypto accounting as a focus area; see what the BDO 2026 audit committee priorities signal for stablecoin and crypto accounting for context on the broader assurance environment. The FASB project will intensify that focus, particularly for clients with material crypto lending or DeFi positions.
On the regulatory side, the intersection with securities law classification also matters. The question of whether a digital asset is a security affects not only how it is regulated but potentially whether it falls under ASC 860 rather than ASC 350-60. For more on how regulatory classification and financial statement treatment interact, see how the SEC's proposed crypto offering framework reshapes financial statement disclosures.
Finally, comment letter preparation deserves serious attention. The 60-day comment period on the proposed accounting standards update is the industry's opportunity to influence whether the lending boundary is drawn in a way that is operationally workable for DeFi transactions. Firms with significant protocol-level crypto exposures should be drafting their responses now, informed by specific client fact patterns rather than generic concerns.
Frequently Asked Questions
Do FASB's August 2026 tentative decisions change US GAAP right now?
No. Tentative decisions are working conclusions reached during deliberations. They do not amend US GAAP until a final accounting standards update is issued. A proposed ASU with a 60-day comment period is the next step. Firms should monitor the exposure draft and prepare comment letters, but no mandatory policy change is required yet.
How does FASB's lending approach differ from what SEC staff said in 2022?
SEC staff indicated in 2022 that they would not object to a lender derecognising lent crypto assets and recognising a fair-value-measured loan receivable with an ASC 326 credit loss allowance. FASB's tentative decision moves in the opposite direction: the lent asset stays on the balance sheet as an encumbered asset measured at fair value, adjusted for the borrower's credit risk. The same on-chain transfer produces a different balance sheet presentation under each approach.
How should firms treat wrapped tokens and LP tokens under ASC 350-60 today?
The existing scope of ASC 350-60 does not explicitly address wrapped tokens or LP tokens. FASB's tentative decision to expand the scope to certain wrapped and receipt tokens depends on a rights analysis: the token must confer a right to receive an asset already within ASC 350-60's scope. Until the final standard, firms should document their rights analysis for each position and disclose their accounting policy clearly. Auditors will scrutinise consistency between the documented rights and the treatment applied.
What is the ASC 606 control model and why does it matter for non-lending crypto transfers?
ASC 606 is the revenue recognition standard. Its control model determines whether control of an asset has passed to another party by examining whether the transferee has the ability to direct the use of and obtain substantially all the remaining benefits from the asset. FASB has tentatively decided to apply this model, with crypto-specific guidance, to crypto intangible asset transfers that do not qualify as lending. The practical challenge is that decentralised protocol transfers do not map neatly onto the control indicators developed for traditional revenue transactions, which is why crypto-specific supplemental guidance is needed.
Does the ASC 860 versus ASC 350-60 classification boundary affect most corporate crypto holders?
For companies holding standard fungible crypto assets such as bitcoin or ether directly, ASC 350-60 is the applicable framework and ASC 860 is unlikely to apply. The boundary becomes relevant where a digital asset has characteristics that could make it a financial asset, such as certain stablecoins backed by financial instruments or tokens that represent debt-like claims. Any firm holding a diverse crypto portfolio should confirm the classification of each asset type rather than assuming all digital assets fall under ASC 350-60.
Source: Accounting Today