Why FASB's Stablecoin Proposal Matters to Corporate Treasuries
For a company, holding a dollar-backed stablecoin is not automatically the same as holding cash. Even if the token is designed to track the US dollar, how it shows up on a balance sheet can affect liquidity metrics, internal treasury policies, and even the wording in financing agreements. That accounting friction can make a useful payment option harder to adopt.
A proposal from the Financial Accounting Standards Board (FASB) could change the picture for some stablecoins. A report from Tempo, a Stripe-backed blockchain project, says the proposed update could let qualifying tokens be classified as cash equivalents. The catch is some: the proposal reportedly turns on whether a company has direct redemption rights with the stablecoin issuer. Buying a token through an exchange may not, by itself, satisfy that requirement.
That distinction matters more than the label on the token. In this article, we'll look at what the proposal could change, why redemption arrangements sit at the center of the issue, what companies would still need to assess, and which milestones to watch as US stablecoin rules develop. The proposal isn't final yet, so businesses should treat it as a possible accounting change - not a confirmed reporting outcome.
Why accounting treatment matters to corporate treasuries
A company shouldn't think of a payment asset as "good for transfers" and stop there. It also needs to know how it will be classified, valued, controlled, and reported. Stablecoins can settle quickly and move across blockchain networks, but those features don't automatically make them equivalent to cash on a company's financial statements.
Under US accounting practice, cash equivalents generally mean short-term, highly liquid investments that convert into known amounts of cash and don't carry a significant risk of value changes. Where a stablecoin lands in that framework depends on its specific characteristics and the rules in force. A dollar peg matters, but it doesn't answer every accounting question by itself.
The balance-sheet effect is operational, not just cosmetic
If a stablecoin holding doesn't land in the cash or cash-equivalent buckets, it can be presented differently from a company's bank deposits. That presentation can change how investors and lenders interpret the balance sheet. It may also affect liquidity ratios and tests tied to financial covenants in credit agreements.
In practice, this is where treasury teams feel it. They may want to use stablecoins for supplier payments or settlement, while finance and legal teams focus on whether the accounting outcome adds review complexity or covenant risk. Even if the token is still redeemable for dollars, a less familiar balance-sheet classification can add work for approvals and scrutiny inside the company.
This is why accounting clarity can influence adoption without changing the underlying token at all. A company might already see speed or settlement benefits, then decide the reporting uncertainty isn't worth it. If qualifying holdings can be treated as cash equivalents, that trade-off becomes easier for some businesses.
Accounting classification does not remove other risks
Cash-equivalent treatment wouldn't magically turn a stablecoin into a bank deposit, make it insured, or ensure the price stays at exactly one dollar. It also doesn't eliminate risks tied to custody, access controls, blockchain operations, issuer solvency, or redemption delays.
Think of the accounting question as one layer of a bigger decision. A company still has to consider who controls the wallet, how transactions are authorized, what happens if a service provider becomes unavailable, and whether its policies allow digital assets in the first place. Classification can reduce one barrier, but it doesn't replace the treasury control framework.
What the FASB proposal could change
The FASB proposal described in Tempo's report is about how companies account for certain stablecoins they hold. It doesn't change how a stablecoin is built, and it doesn't create a new redemption promise on its own. Instead, it could allow qualifying holdings to be treated as cash equivalents, but only under specified conditions.
That's an important point. Accounting standards affect what a company can or must report, but they don't automatically make every token qualify. Companies would still need to evaluate the relevant terms and relationships under the final requirements and within their own accounting policies.
Qualification may depend on the issuer relationship
Tempo reports that the proposal would require direct redemption rights with the stablecoin issuer. If a business buys USDC through an exchange, for example, the purchase alone may not give that business the required redemption arrangement with Circle (the issuer).
Tempo summarizes the idea plainly: "Your contract with the issuer is what qualifies, and the token alone doesn't get you there." In other words, two companies could hold the same stablecoin and still have different contractual relationships - and therefore potentially different eligibility under the proposed approach.
So the focus shifts away from the token's ticker or public description and toward the legal and operational chain behind the holding. Who is the counterparty under the issuer agreement? Can that entity redeem directly? What minimums, procedures, or eligibility requirements apply? Those details could matter as much as the token's dollar peg.
The proposal remains a proposal
FASB's update was proposed in August, and the public comment period is scheduled to remain open until November 19. The board will review feedback before deciding whether to finalize the changes and when any final requirements would take effect.
That timeline matters to companies making decisions today. Proposed rules can be revised, delayed, or finalized with different details. Treasury teams shouldn't treat a possible classification as guaranteed until the board finishes the process and the final requirements are clear.
For companies already testing stablecoin payments, it helps to separate two questions: whether the payment use case works operationally, and how the holding would be reported under current accounting rules and any possible future update. Keeping those questions separate makes it easier to run a limited pilot without assuming the accounting issue is already solved.
Why direct redemption rights matter
A stablecoin's reserve model and redemption process are part of what supports its relationship to the dollar. But redemption in practice can depend on the holder's legal relationship with the issuer, not just the fact that the token is transferable on a public blockchain.
For a corporate treasurer, this creates a difference between holding a token and having a direct claim - or contractual route - to redemption. A company might acquire tokens through a third-party platform, keep them with a custodian, and depend on that intermediary for liquidity. That setup can work for payments, but it may not satisfy a rule that looks for a direct issuer relationship.
A familiar example: USDC and Coinbase
Tempo points to Coinbase's 2025 annual report, in which Coinbase classified USDC and other payment stablecoins as cash equivalents. Tempo says that treatment was supported by Coinbase's redemption arrangement with Circle.
The example shows why the issuer relationship could matter. It shouldn't be read as a blanket conclusion that every company holding USDC can use the same accounting treatment. Another company may have different agreements, hold tokens through a different intermediary, or face different facts and accounting judgments.
The practical takeaway is to review the arrangement, not copy a peer. A public filing can show how one company approached its circumstances, but it doesn't replace the need to assess your own contracts, custody setup, and reporting obligations.
Questions companies should put to their providers
Before building a treasury workflow around stablecoins, companies can ask issuers, exchanges, and custodians targeted questions:
- Does the company itself have a direct redemption agreement with the issuer?
- Which legal entity is party to that agreement, and does it match the entity that will hold the tokens?
- Are there minimum redemption amounts, eligibility checks, fees, or processing windows?
- If tokens are held with a custodian or exchange, who can initiate redemption and under what conditions?
- What records will be available to support accounting, audit, and internal control reviews?
These questions are still worth asking even before the final FASB outcome. They help surface operational dependencies and contractual gaps earlier - often before a pilot gets too far and finance, audit, or legal starts digging through the details.
What corporate treasurers should watch
The FASB proposal is only one piece of a broader US policy picture. Congress passed the GENIUS Act in July 2025, creating a federal framework for payment stablecoins. Tempo says the law is scheduled to take effect in January 2027, or 120 days after federal regulators finalize implementing rules, whichever comes first.
These two developments cover different parts of the system. The GENIUS Act sets requirements for stablecoin issuers, including reserve backing and redemption obligations. The FASB proposal is about how companies account for stablecoins they hold. Issuer regulation may influence confidence in the market, while accounting standards affect how a corporate holder reports its position. They shouldn't be treated as the same thing.
A larger market creates more pressure for clear rules
Tempo also reports that the market for US dollar-backed stablecoins surpassed $300 billion, citing DefiLlama data. That scale makes the accounting question relevant well beyond crypto-native companies. Businesses involved in cross-border commerce, digital asset markets, or round-the-clock settlement may increasingly evaluate stablecoins as an option for payments and treasury operations.
There's also a policy angle. The report describes US government interest in promoting dollar-backed stablecoins overseas, potentially involving public agencies and private companies. If that direction continues, stablecoins could become part of a broader push to extend dollar-denominated payments. Still, ambition doesn't eliminate the day-to-day issues businesses deal with around redemption, compliance, custody, and accounting.
For market context, readers can review DefiLlama's stablecoin data. As with any dashboard, figures are a snapshot and should be checked against the date and methodology relevant to your decision.
A practical monitoring checklist
Corporate finance teams don't have to wait for every policy detail to start doing useful work. They can prepare now without treating the proposal as final:
- Map the use case. Identify whether stablecoins would be used for payments, settlement, temporary liquidity, or another purpose. Don't assume the business needs to hold a large balance from day one.
- Trace the redemption path. Document the relationship between the company, issuer, exchange, and custodian. Confirm who has the contractual right and operational ability to redeem.
- Ask accounting and audit teams early. Have them assess current treatment and flag which proposal details could change their analysis. Don't assume a vendor's description automatically drives the accounting outcome.
- Review controls and contingencies. Define wallet permissions, approval thresholds, reconciliation procedures, incident response, and an alternative payment route if a provider or network is unavailable.
- Track the rulemaking calendar. Watch for FASB's review of public comments, the final accounting language and effective date, and the implementation timeline for the GENIUS Act.
Done this way, decisions stay anchored to the business case. If settlement benefits are modest and control work is heavy, it may make sense to wait. If the use case is valuable, run a constrained pilot - while keeping the option to adjust when the rules are finalized.
Conclusion
If finalized as described, the proposed FASB change could make stablecoins easier for some companies to use by reducing an accounting obstacle. But the reported emphasis on direct redemption rights means the answer isn't as simple as "pick a widely used token." The issuer relationship, custody route, internal controls, and the final accounting language all matter.
For now, corporate treasurers should map the use case and redemption path, loop in accounting and audit teams early, and avoid treating a proposed rule as settled policy. If stablecoin settlement solves a real operational problem, a limited, well-controlled pilot may be worth running. If it doesn't, clearer accounting alone isn't a good reason to adopt it.
For more context, read the original report on FASB's proposed stablecoin accounting changes and follow the board's process before making balance-sheet assumptions.
