Stablecoins as cash equivalents: FASB's three-part test decides what the dollars on your books are

What FASB proposed on August 18, 2026

The Financial Accounting Standards Board — the body that writes US GAAP — issued a proposed Accounting Standards Update on August 18, 2026 titled Cash Equivalents — Disclosure Enhancement and Evaluation of Certain Digital Assets. Technically it is modest: it does not change the long-standing definition of a cash equivalent. It adds examples to Topic 230, the statement-of-cash-flows standard, showing how that definition applies to fiat-backed stablecoins, and it opens a 90-day comment period that runs through November 19, 2026.

Practically, it answers the question every finance team asks in the second meeting about stablecoin acceptance. The first meeting is "can we take USDC?" The second is "and what is it once we have it — cash, or a crypto asset the auditor treats like inventory nobody ordered?" Until now, US GAAP had no stablecoin-specific answer. FASB's 2023 crypto standard (ASU 2023-08) put bitcoin-style assets at fair value, but tokens carrying a redemption claim largely sat outside its scope, in a gray zone each company negotiated with its auditor.

The proposed test resolves the gray zone with three conditions. A stablecoin can be presented as a cash equivalent only if all three hold:

1. An on-demand contractual redemption right, directly with the issuer. The holder must be able to go to the issuer — not a secondary buyer, not an order book — and demand cash.
2. Redemption for a known cash amount: par value in the referenced fiat currency. A dollar token redeems for a dollar, contractually, not "approximately a dollar, usually."
3. Segregated reserves of at least 1:1, held in short-term, highly liquid assets readily convertible into known amounts of cash.

Miss any one, and the token stays a digital asset on the balance sheet. Meeting all three doesn't force reclassification either — companies would retain the option to present qualifying stablecoins as cash equivalents, which is how cash-equivalent policy already works for things like commercial paper.

The clause that matters: it's about how you hold, not just what you hold

The headline writes itself as "FASB decides whether USDC is cash." That is not what the proposal says, and the difference is the whole story for a business that accepts stablecoin payments.

The first condition attaches to the holder, not the token. The question is not "does the issuer redeem?" but "do you have a contractual right to redeem, directly with the issuer?" A company that has onboarded with the issuer and holds redemption rights can present its holdings one way; a company holding the exact same token through an exchange account or a payment provider — with no direct line to the issuer — can reach a different answer entirely. FASB was explicit that secondary-market liquidity alone is insufficient: the ability to sell a token at roughly a dollar is not a contractual right to a dollar, because the market price can move away from the promised value exactly when it matters — in stress.

That logic will be familiar if you've read our analysis of counterparty risk in stablecoin payments. It is the same chain-of-claims reasoning, arriving from the accounting direction: what you actually own is not "a dollar" but a specific claim against a specific counterparty, and every intermediary between you and the issuer changes what that claim is worth and how it behaves under stress. The accountants have now written that intuition into a proposed standard.

Note also what the proposal is not. It is not a regulatory blessing. FASB's process runs separately from the GENIUS Act implementation underway at Treasury and the banking agencies — the customer identification rules proposed for permitted stablecoin issuers are one piece of that separate track. A token could satisfy federal issuance rules and still fail the accounting test for a given holder, and vice versa. Regulation decides which stablecoins may circulate; accounting decides what they are on your books. If you sell in the US, our guide to which stablecoins US merchants can accept covers the regulatory half.

Why an accounting exposure draft is merchant news

Most stablecoin news in 2026 has been about issuers, chains and regulators. This one is about the ledger — and the ledger is where stablecoin acceptance either becomes routine or quietly dies in the finance department.

Here is the pattern we see in practice. A business starts accepting stablecoins because the operational case is obvious: settlement in seconds, no chargebacks, no cross-border FX drag. Then quarter-end arrives, and the question of what those tokens are lands on someone's desk with no clean answer. Ambiguity has a price: audit hours, conservative treatments, and in the worst case a CFO who concludes that the simplest policy is not to hold the asset at all — or not to accept it in the first place. Accounting ambiguity has been a quiet ceiling on adoption in a way that no protocol upgrade could fix.

The proposal attacks that ceiling from two sides:

• It gives qualifying holdings a familiar destination. A stablecoin that passes the test can sit next to treasury bills and money market funds as a cash equivalent — a category every lender, investor and auditor already understands. No mark-to-market noise in P&L for what is functionally working cash.
• It normalizes the word "stablecoin" on every balance sheet. The disclosure requirement applies to all reporting entities: companies would annually disclose the significant components of their cash equivalents — treasury bills, commercial paper, money market funds and, where applicable, stablecoins. Once stablecoins are a named line in a standard disclosure, holding them stops being an exotic position that needs a memo and becomes a treasury choice that needs a policy.

For a merchant, that second point may matter more than the first. The infrastructure of normality — a place on the form, a name in the standard — is how a payment method stops being "crypto" and starts being money.

What this means if stablecoin revenue lands in your wallet

Assume the proposal is finalized in something like its current shape. A business accepting stablecoin payments ends each month holding tokens, and the test sorts the possible positions cleanly:

• You hold the token in your own wallet and have direct redemption rights with the issuer. This is the strongest position under the proposed test — you hold the asset itself, and condition one is satisfied by your own contractual arrangement. Issuers publish their redemption frameworks; Circle's USDC documentation describes 1:1 redeemability for eligible institutional account holders. Whether your specific facts qualify is a question for your accountant — but it is answerable, because both sides of the claim are yours.
• You hold the token in your own wallet without issuer onboarding. You still own the asset — no intermediary can freeze or lend it — but under the proposed test, exchange liquidity alone would not support cash-equivalent presentation. The token is a digital asset on your books, and if cash-equivalent treatment matters to you, direct issuer onboarding is the gap to close.
• You hold a balance at a custodial processor or exchange. Under the proposal's logic this is the weakest position, and it is worth saying plainly why: you may not be holding a stablecoin at all. A balance in someone else's system is a claim on that company — an IOU whose value depends on their solvency and their terms of service. That is precisely the arrangement we examined in what happens when a crypto payment provider shuts down: when the intermediary fails, the "stablecoin balance" turns out to be a line in their bankruptcy, not an asset in your wallet.

The through-line: every position improves as the distance between your business and the token shrinks. The accounting proposal did not invent that principle. It priced it.

Where Payzum fits

Payzum is a non-custodial crypto payment processor, and this news lands directly on what non-custodial means in practice.

• You are the holder — of the token itself. Every payment — hosted checkout, payment link, invoice, POS QR, subscription — settles to a wallet you control. There is no Payzum balance between you and the asset, so the question "what do we hold?" has a one-word answer: the token. Your accounting classification is then determined by your facts — your wallet, your redemption arrangements — not by a processor's terms of service.
• Auto-convert decides which stablecoin accumulates. Payzum can accept whatever your customers pay and auto-convert to USDC or USDT for volatility protection. After this proposal, that setting has an accounting dimension too: issuer redemption terms and reserve structures differ, and they are two-thirds of the test. Our comparison of USDT vs USDC for payments walks through the differences.
• The ledger work gets easier, not harder. Every settlement carries a public transaction hash; signed webhooks push confirmed payments into your accounting system without re-keying; a full audit log records who was paid what, when, on which chain. When your accountant asks for the record behind the stablecoin line, it exists — per payment, cryptographically timestamped.
• Holding is optional. Non-custodial also means nothing stops you from sweeping to an exchange and converting out on your own schedule. The FASB proposal is what makes holding viable for companies that want dollar-denominated working balances on-chain — but the rail doesn't force the treasury decision either way.

What Payzum does not do: we don't classify your holdings, and nothing here is accounting advice. The test is a proposal, comment runs through November 19, 2026, and outcomes are fact-specific. What the rail guarantees is the clean starting position — the token, in your wallet, with a complete record — from which your accountant can actually work.

The same dollar, four ways it can sit on your books

One dollar of value, four holding structures, four different answers under the proposed test. (Illustrative — your accountant applies the standard to your facts.)

Three fair objections

"We're a small private business. Why would we care what FASB proposes?"

Because GAAP concepts travel far beyond companies that formally report under GAAP. Your lender's covenant math, your investor's due diligence checklist, an acquirer's quality-of-earnings review — all of them borrow the categories. When "stablecoins" becomes a named component of cash equivalents in the standard, the bookkeeper, the banker and the buyer all inherit a shared answer to "what is this line?" That shared answer is worth more to a small business than to a large one, because the small business can't afford the audit hours the ambiguity used to cost.

"Does this make accepting stablecoins more complicated?"

No — it makes holding them simpler, and it changes accepting them not at all. The payment flow is untouched: customer pays, settlement confirms in seconds, funds land in your wallet, no chargebacks. What changes is that the asset you end up holding is on a path to a well-defined place on the balance sheet instead of a negotiation. If anything, the proposal removes the finance-department objection that has killed more stablecoin acceptance projects than any technical issue.

"Shouldn't we just convert everything out and avoid the question?"

You can — non-custodial settlement means the exit is always yours, and for some businesses immediate conversion is the right policy. But notice what the question assumes: that holding tokenized dollars is the risky, complicated option. The direction of this proposal is the opposite — it is the accounting profession building the shelf on which held stablecoins sit as near-cash. Businesses that collect in USDC and also pay in USDC — suppliers, contractors, affiliates — increasingly find the working balance is the point, not the problem. The right answer is a treasury policy, not a reflex.