How SaaS should record revenue received in stablecoins

SaaS companies must record revenue when the service is delivered and at the contract currency price. The method a customer uses to pay does not change when revenue is earned. Stablecoins received are recorded separately as an asset on the balance sheet and do not alter the revenue schedule.

Monthly subscriptions are recognised in the month the service is provided. Annual subscriptions paid upfront are recorded as deferred revenue at receipt and recognised ratably over the service term. Those timing rules apply regardless of whether the customer pays by card, wire transfer or stablecoin.

Revenue is recorded at the contract dollar amount. If a plan is priced at $2,400, the company recognises $2,400 of revenue even if the customer pays with a token amount that differs slightly. Quoting prices in dollars and accepting stablecoins only as the settlement method preserves revenue measurement in fiat. Quoting prices in token amounts changes the commercial nature of the transaction and the accounting treatment.

Under current U.S. practice many companies classify stablecoins as noncash assets, often as intangible assets rather than cash or cash equivalents. The Financial Accounting Standards Board has proposed a three-part test for cash-equivalent treatment that requires a direct redemption right with the issuer. Most SaaS companies lack that right. When stablecoins are treated as noncash consideration, accounting standards require measuring them at fair value on receipt; for coins tracking a dollar peg that fair value generally aligns with the contract price on receipt.

Changes in stablecoin value after receipt do not affect revenue. Any difference between the value recorded on receipt and the value realised on conversion is recognised as a gain or loss on the asset, not as revenue. Payment processing fees and network or gas fees are recorded as expenses. Refunds reduce revenue in the period to which they relate and are typically refunded at the dollar contract amount.

Prepaid credit top-ups create contract liabilities on receipt and revenue is recognised as customers consume credits. Estimating breakage and recognising unused balances follow the same rules used for any prepaid program.

Finance teams should maintain separate ledger entries for deferred revenue and stablecoin holdings and agree the treatment of noncash consideration with auditors before the quarter close. Converting stablecoins to fiat promptly shortens the period in which classification and valuation affect reported balances.