FASB Crypto Assets Project: What the Q3 2026 Update Means for Finance Teams
A quarterly reporting update from Forvis Mazars, covering standard-setting developments through September 30, 2026, puts digital assets on two separate FASB tracks: an exposure draft related to cash equivalents and certain digital assets, and a project on crypto assets expected to lead to forthcoming proposals. For anyone preparing crypto financial statements, the message is practical: nothing in this update changes today's accounting, but the pipeline is moving, and teams that wait for final standards will be short on time and data.
What the Q3 2026 update actually says about digital assets
The update is a general roundup of financial reporting developments, not a crypto-specific publication. That matters for how you read it. Crypto appears as a few lines inside a much longer list, and the source does not spell out the detailed mechanics of each proposal. What it does establish is the direction of travel, and that is worth taking seriously on its own.
The exposure draft on cash equivalents and certain digital assets
Among the quarter's exposure drafts, the update lists one related to cash equivalents and certain digital assets. It sits alongside drafts on residential mortgage servicing rights and targeted Codification improvements. An exposure draft is a proposal released for public comment, not an effective requirement. Until FASB finalizes a proposal and issues an Accounting Standards Update, existing US GAAP continues to apply.
The pairing of cash equivalents with certain digital assets in one document is itself informative. It suggests the standard-setter is looking at how particular digital assets are classified and presented, not only how they are measured. The source does not say which digital assets are in scope, so finance teams should read the draft itself before drawing conclusions about stablecoins, tokenized instruments or anything else.
The forthcoming crypto assets and commodities projects
The update also names crypto assets and commodities among projects expected to result in forthcoming proposals. Those sit with debt classification, equity method accounting and retail electricity contracts. The wording signals that proposals are anticipated, not that they have been issued. Treat it as an early planning signal.
Where US GAAP and IFRS stand today for crypto holdings
The update is a US-focused document, but crypto holders rarely operate in one framework. Groups with US parents and IFRS subsidiaries, or the reverse, need to understand how a US development interacts with the rest of the reporting stack.
US GAAP: the fair value baseline
The topic is often shorthand in the market as ASC 350-60 crypto accounting, which is the fair value approach for in-scope crypto assets under US GAAP. The Q3 update does not restate that guidance, and this article does not add detail beyond what the source supports. The point for planning is that a further FASB project on crypto assets means the current framework is not being treated as the last word. Any new proposal could refine scope, presentation or disclosure.
IFRS: a different starting point
Under IFRS, there is no standalone crypto standard in the source material, and the update does not discuss IFRS crypto guidance. Teams reporting under IFRS should not assume a US proposal will carry across. For groups preparing both sets of statements, the safest working assumption is divergence until a standard-setter says otherwise, and the practical task is keeping records granular enough to support either treatment. That is where crypto IFRS accounting and US GAAP workstreams share a common dependency: clean, asset-level data.
Why this matters for accounting firms, auditors and CFOs
For B2B readers, the exposure draft and the crypto project create both a technical agenda and an operational one. The technical agenda is reading and, where appropriate, commenting on proposals. The operational agenda is making sure the finance function can implement whatever comes out the other end.
Accounting implications
A proposal touching cash equivalents and digital assets could affect classification on the balance sheet and the cash flow statement, depending on its final content. We cannot say how, because the source does not describe the details. What a CFO can say is which questions to be ready for:
- Which of our digital asset holdings are held for operating, treasury, custody or customer purposes?
- Could any holdings be argued to function like cash for liquidity management, and do we have documentation behind that view?
- Are our fair value inputs, valuation timing and source policies defensible if scope changes?
Firms advising clients should also watch the interplay with disclosure. A growing pipeline of proposals typically means more disaggregation and more explanation expected in notes, so early drafting of disclosure templates is cheaper than late rework.
Audit and assurance implications
The update points to regulatory emphasis on audit quality, financial reporting oversight and the importance of validating AI-generated information. For crypto engagements, that combination has a direct reading: auditors will want evidence that wallet addresses, exchange statements and on-chain records reconcile to the ledger, and that any automated or AI-assisted extraction has been validated by a person with the right judgment. Documentation of research and professional judgment is explicitly called out as important in the update, and crypto balances are an area where thin documentation shows quickly.
Tax and AML touchpoints
This update concerns financial reporting, not tax or AML rules. Even so, the same underlying records feed all three. Book measurement and tax basis are separate calculations, and a change in book classification does not by itself change tax treatment. Likewise, a more structured view of holdings helps with AML and sanctions screening, because you cannot screen exposure you have not mapped. For firms already working on exposure analysis, our piece on enterprise risk management for crypto-active financial services firms covers the control side of that picture.
What the broader regulatory backdrop adds
The update does not stop at standards. It also describes regulatory activity with a continued focus on capital formation, investor protection, financial reporting oversight, audit quality and emerging technologies.
SEC priorities and enforcement initiatives
The source highlights SEC regulatory priorities and new enforcement initiatives aimed at retail and financial reporting fraud, along with accounting and auditing misconduct. It does not tie these to crypto specifically, so we won't. The relevant takeaway for crypto-active issuers is general: reporting accuracy and auditor conduct are under scrutiny, and digital asset balances that are hard to evidence are exactly the sort of line item that draws questions.
AI-generated information and internal controls
The update stresses research, professional judgment, internal controls, documentation and validation of AI-generated information. Finance teams increasingly use automation to classify transactions and draft memos. The reminder is that output from those tools is an input to judgment, not a substitute for it. If you want a deeper look at questions to ask of automated tooling, see our article on agentic AI for digital asset risk.
Effective dates and the DISE reminder
The update also reminds readers about implementation of FASB's Disaggregation of Income Statement Expenses standard, with visual references to effective dates across public business entities, private companies and nonprofits. For crypto holders the connection is indirect but real: finance teams will be juggling several implementation timelines at once, and a crypto proposal will land on top of them. Sequencing matters.
A practical readiness plan for crypto financial statements
The source closes with a simple point: early planning helps organizations evaluate potential impacts, prepare for effective dates and strengthen the processes and controls behind reporting. Here is how that translates for a team that holds or services digital assets.
Step 1: Inventory and classify holdings
Build a register by asset, wallet or account, custodian, purpose and legal ownership. Separate assets held for the entity from assets held for customers. This is the foundation for any future classification question and is useful regardless of what FASB finally issues.
Step 2: Test your data lineage
Check that every balance can be traced from the ledger to source evidence, whether on-chain data or custodian statements. Where you use digital asset accounting software or crypto bookkeeping software, confirm that cost, fair value and classification are stored as separate fields so a change in one policy does not force a rebuild of the whole dataset. Good crypto accounting software should let you re-run measurement under an alternative policy without overwriting history.
Step 3: Document judgments now
Write down how you currently determine fair value sources, timing and principal market assumptions. The update's emphasis on documentation and professional judgment suggests that undocumented positions are the ones that become problems at audit time.
Step 4: Monitor and respond to proposals
Assign someone to read the exposure draft on cash equivalents and certain digital assets, track the crypto assets project, and decide whether to submit comments. Comment letters are the formal channel through which preparers and practitioners shape final text.
Step 5: Align with tokenization and market structure changes
Standards will have to accommodate how assets are actually issued and settled. Developments in tokenized markets, such as those covered in our note on DTCC tokenization and what finance teams must prepare for, are a reminder that the asset universe is widening faster than any single standard. For the wider framework, see our hub on crypto compliance and reporting.
What we still don't know
It is worth being plain about the limits. The source does not state the scope, the proposed measurement or classification outcomes, the comment deadline or any proposed effective date for the digital asset items. It also does not name specific digital assets in scope. Anyone relying on this update alone to change policy would be going further than the evidence allows. Read the primary FASB documents, then decide.
The sensible posture is neither alarm nor complacency. Proposals can change substantially between exposure and final standard, and some do not progress. But the cost of preparing the data foundation is low, and it pays off under almost any outcome, including simply passing a tougher audit under existing rules.
FAQ
Does the Q3 2026 update change how crypto is accounted for today?
No. The update summarizes proposals and projects. Exposure drafts are not effective requirements, so existing US GAAP and IFRS treatment continues until a final standard is issued and becomes effective.
What is the exposure draft on cash equivalents and certain digital assets?
The update lists it among the quarter's exposure drafts but does not describe its detailed content. Review the draft published by the standard-setter to understand scope, proposed treatment and comment deadlines before changing any policy.
Does this affect IFRS reporters?
The update is a US-focused summary and does not discuss IFRS crypto guidance. IFRS reporters should not assume a US proposal applies to them, but groups with US and IFRS reporting lines should keep asset-level data that can support either framework.
Is the crypto assets project a final standard?
No. The update describes crypto assets as one of the projects expected to result in forthcoming proposals. That means proposals are anticipated, not issued.
What should finance teams do first?
Inventory and classify digital asset holdings, confirm data can be traced to source evidence, and document current judgments on fair value. Then monitor the exposure draft and the crypto project so you can respond when proposals are published.
Source: Forvis Mazars