A Stablecoin Isn’t A Cash Equivalent Until You Can Prove It — What FASB’s New Proposal Actually Requires
FASB just clarified when stablecoins qualify as cash equivalents under U.S. GAAP. Qualification is narrower – and more holder-specific – than most institutions assume. Here’s what the proposal says, who it touches, and the data it takes to defend the answer.
On August 18, 2026, the Financial Accounting Standards Board (FASB) published proposed Accounting Standards Update, Statement of Cash Flows (Topic 230): Cash Equivalents—Disclosure Enhancement and Evaluation of Certain Digital Assets. Public comments are open until November 19, 2026.
For most of the past decade, “Is this stablecoin cash?” was a question accountants answered inconsistently, if at all. That ambiguity is now on the clock. And for institutions holding, settling in, or reporting on stablecoins, the proposal turns a philosophical debate into a line item, one your auditors, your controllers, and eventually your investors will expect you to defend.
Here’s the part most coverage will miss: the FASB didn’t make it easier to call a stablecoin cash. It made it clearer, and clarity cuts both ways.
The “why”: diversity in practice was becoming a liability
Stablecoins have quietly become settlement infrastructure. Institutions use them for payments, treasury operations, and value transfer, increasingly as a substitute for moving dollars through legacy rails. As those balances grow, how they’re classified stops being academic. Whether a stablecoin sits in “cash and cash equivalents” or somewhere else changes the face of the balance sheet, the statement of cash flows, and every liquidity ratio and analysis an investor or lender runs off them.
The problem: some entities were already presenting certain stablecoins as cash equivalents, and others weren’t, sometimes for the same token. The FASB flagged this “diversity in practice” as the core issue, informed by its 2025 agenda consultation, the President’s Working Group on Digital Asset Markets, and the regulatory framework for payment stablecoins under the GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins).
Inconsistent classification erodes comparability. Two companies with identical stablecoin exposure could report very different liquidity pictures. The proposal is the FASB’s move to close that gap.
The “what”: the definition didn’t change, but the bar got explicit
Critically, the proposal does not rewrite the Master Glossary definition of cash equivalents. Cash equivalents remain short-term, highly liquid investments that are (a) readily convertible to known amounts of cash and (b) so near maturity that changes in interest rates present insignificant risk to value.
Instead, the FASB added illustrative examples showing how that existing, intentionally narrow definition applies to a stablecoin. To qualify, a stablecoin designed to hold a stable value against a reference asset (like the U.S. dollar) would generally need to demonstrate three attributes:
- An on-demand contractual cash redemption right, redeemable without significant fees or restrictions.
- A direct redemption right with the issuer for a known amount of cash, not merely the ability to sell on a secondary market.
- Segregated reserve assets held by the issuer on at least a 1:1 basis, in short-term, highly liquid assets (think cash and short-dated U.S. Treasury bills).
The proposal also directs entities to consider relevant laws and regulations (the GENIUS Act among them) when setting their cash equivalents accounting policy, and it introduces a new disclosure requirement: any entity presenting assets as cash equivalents must disclose the significant components, such as U.S. Treasury bills, commercial paper, stablecoins, and money market funds, together with the related amounts. That requirement applies whether or not any of those assets are digital, and it moves U.S. GAAP closer to the IAS 7 disclosure model.
And that disclosure change may be the quiet win in the proposal. It isn’t limited to digital assets or to stablecoins — it applies to every entity that presents a cash equivalents line, requiring them to break out the significant components and their related amounts rather than report a single, undifferentiated total. That’s a genuine step forward for comparability and transparency: investors, lenders, and auditors finally get to see what “cash equivalents” actually contains, instead of taking the label on faith.
An often overlooked and underappreciated fact is captured in these attributes–i.e., that the underlying facts and circumstances, and the overt terms and conditions matter, sometimes more than simply knowing the name of a given stablecoin. The attributes can vary among coins with the same name.
The catch most institutions will underestimate
Read the FASB’s three worked examples and the real story emerges. It’s not a list of “approved” coins. It’s a test, and it’s unforgiving:
- Case A qualifies. The holder has a direct, on-demand right to redeem with the issuer for $1 per unit, and the issuer keeps segregated reserves 1:1 in cash and short-dated T-bills.
- Case B fails, and this is the one that will surprise people. Same stablecoin, same near-$1 price, active secondary markets where the holder can sell. But no direct contractual redemption right with the issuer. Result: not a cash equivalent. A liquid market price is not a redemption guarantee.
- Case C fails on reserve quality. The peg is backed 1:1, but by crypto assets and gold, which can move in value for reasons that have nothing to do with interest rates. Not a cash equivalent.
The through-line is simple: the guarantee is the key. If an issuer contractually promises you a known amount of cash on demand, and stands behind that promise with high-quality liquid reserves, you have something that behaves like cash. Absent that, you have a token that happens to trade near a dollar, which is not the same thing, and the FASB just said so in writing.
Two consequences follow, and both are data problems:
- Qualification is holder-specific, not just asset-specific. The difference between Case A and Case B isn’t the coin but whether you hold a direct redemption arrangement with the issuer. The same stablecoin can be cash for one institution and not for another.
- “Fiat-backed” is not a free pass. Reserve composition and quality decide it. A stablecoin marketed as fully backed can still fail if the backing isn’t short-term and highly liquid, or if it’s over-collateralized with the wrong assets.
There is no shortcut, no static “these are cash” list you can license and forget. Every position demands an evidence-backed, asset-level, issuer-level determination, the kind an auditor can inspect and an investor can trust.
The “who”: this lands on more desks than you’d think
- CFOs, controllers, and technical accounting teams who own the classification policy and the new disclosure.
- Auditors who must test whether a stablecoin genuinely meets the definition: redemption rights, reserve composition, and all.
- Corporate treasury and operations teams using stablecoins for settlement, whose cashflow presentation now hinges on the answer.
- Fund administrators and asset managers reporting NAV and liquidity to investors who care about what “cash equivalents” really contains.
- Any entity presenting cash equivalents at all, because the disclosure requirement reaches beyond digital assets to the full composition of the line item.
If your organization touches any of these, the comment window closing November 19, 2026 is not the deadline that matters most. The determination and disclosure obligations that follow are.
Where the commodity data breaks, and where the real work begins
Here’s the uncomfortable truth for the market-data status quo: a price feed cannot answer this question.
Most stablecoin data stops at a ticker, a price near $1.00, and a market cap. That tells you nothing about whether the peg is contractually guaranteed by the issuer, whether redemption is direct and on-demand, what the reserves actually consist of, or how a given asset is treated under the GENIUS Act, MiCA, or an EMI regime. A scraped number won’t survive a hard question from your risk committee, and it certainly won’t survive an auditor asking you to prove the position is cash.
How Lukka closes the gap
Lukka was built for exactly this determination: the institutional data operating system behind compliant, auditable digital dollars. The FASB’s three attributes map, almost line for line, to data Lukka already produces.
Lukka’s Reference Data: classification that goes past the ticker. Lukka classifies more than 840 stablecoins and flags what actually matters for the cash equivalents test. Is the asset truly a stablecoin? Is it backed by real collateral, meaning USD reserves rather than rebase or synthetic exposure? What collateral is permitted, so you can assess quality? And, critically, is the peg guaranteed by the issuer? That last point is tracked in the governance layer. The Lukka Digital Asset Classification Standard (LDACS), Lukka’s digital asset taxonomy, separates fiat-backed, crypto-backed, and hybrid mechanisms, so a Case A asset never gets confused with a Case C one.
Lukka Prime: valuation your auditors accept. A peg is a target, not a fixed price. Lukka Prime prices stablecoins from live markets with GAAP/IFRS-aligned Fair Market Value and tracks peg deviation as a risk signal rather than hardcoding par. That directly supports the “insignificant risk of changes in value” attribute and gives you audit-ready, defensible pricing instead of an assumed $1.00.
Regulatory and entity lineage: know who stands behind the peg. Lukka maps regulatory status (SEC, MiCA, EMI) to the issuing authority, alongside the issuers, custodians, and auditors behind each asset. When the FASB tells you to weigh relevant laws and regulations, that’s lineage you can hand to a regulator or attach to your accounting memo.
Disclosure-ready, normalized data. Because Lukka normalizes stablecoin data into one institutional view of price, peg, reserves context, classification, and regulatory status, the raw material for the FASB’s new significant-components disclosure is already structured, sourced, and consistent.
All of it rests on an institutional backbone: 108+ blockchains, 50K+ VASPs and entities, 1.2B+ addresses attributed, $4.4T+ in value processed, and 10+ years of pricing history. And it is backed by independently audited controls, including SOC 1, SOC 2, ISO 27001, NIST, and IOSCO adherence.
The outcome: classification decisions and disclosures that hold up, to your auditor, your risk committee, and the FASB’s own examples. Not a scraped price. A source of truth.
Stop quoting stablecoins. Start proving them.
The FASB just raised the bar on what it takes to call a digital asset cash. Meeting that bar is a data challenge, and it’s the one Lukka was purpose-built to solve.
Talk to Lukka about building audit-ready, defensible stablecoin classification and reporting before the standard is final.
About Lukka
Founded in 2014, Lukka provides enterprise blockchain data and software solutions to financial institutions, exchanges, fund administrators, and government agencies. Its platform transforms raw on- and off-chain activity into audit-ready intelligence–powering accounting, compliance, risk, and reporting workflows across the digital asset ecosystem.
Lukka’s institutional control and assurance framework includes AICPA SOC 1 Type I & Type II Service Organization Controls, AICPA SOC 2 Type I & Type II Service Organization Controls, ISO 27001 – ISO/IEC 27001 Certification, NIST Cybersecurity Assessment Complete, and an IOSCO Financial Benchmarks Statement of Adherence.
Learn more: Website | X (Twitter) | LinkedIn
Disclaimer
This content is provided by Lukka, Inc. for general informational purposes only. It does not constitute investment, legal, tax, accounting, regulatory, or other professional advice and should not be relied upon as such. Nothing herein is an offer, solicitation, or recommendation to buy, sell, or hold any digital asset or financial instrument. Product features, capabilities, coverage figures, certifications, and availability are current as of publication and subject to change without notice; certain offerings may be in development or unavailable in some jurisdictions. Any references to laws, regulations, or frameworks are provided for context only, and Lukka does not guarantee any compliance, audit, tax, or reporting outcome, each of which depends on an institution’s own facts, controls, and obligations.
All trademarks, product names, and logos are the property of their respective owners.