SaaS Revenue Recognition (boy, these rules are different)

Short answer: SaaS revenue recognition follows different rules, and different instincts, than traditional perpetual-software licensing. Under today’s ASC 606 standard you recognize revenue as you satisfy your obligations to the customer, usually ratably across the subscription term, and what you promise about your roadmap can change that timing.

Years ago I met Jay Howell of BDO, a technical guru on SaaS accounting, at a seminar I presented in Washington DC. A few of his points stuck with me, and they still hold up after the accounting standards modernized. (Quick caveat: revenue recognition is ultimately your CPA’s call. What follows is how the contract drives it.)

1. SaaS Accounting Is Genuinely Different.

SaaS recognition works differently from old-style software licensing, with different rules and different interpretations. Do not assume SaaS and perpetual-license accounting are similar; they are not. A perpetual license often supported a chunk of revenue up front. A SaaS subscription is a service you deliver continuously, so the revenue typically spreads out over the term you are delivering it.

2. The Old VSOE Regime Gave Way to ASC 606.

When this conversation first happened, software revenue lived under rules that leaned heavily on VSOE (vendor-specific objective evidence) of fair value, and SaaS got more flexibility than traditional licensing. The standards have since been unified under ASC 606 (“Revenue from Contracts with Customers”), which recognizes revenue as control of each promised good or service transfers, broken into performance obligations. The old software-specific VSOE machinery is largely gone, but the underlying lesson survived: how you structure and describe the deal still drives when you can book it. (For the specific contract clauses that move the needle, see SaaS Agreement Revenue Recognition Issues.)

3. Be Careful What You Promise About the Roadmap.

This one is still very real. If you commit too much about future features, those promises can become separate performance obligations that pull revenue out of the current period and spread it over time. SaaS gives you some breathing room here compared to a traditional licensing competitor, but only if you do not over-commit the roadmap in the contract or in side communications. Watch the same trap with acceptance rights and refund rights, which can defer revenue or make it variable.

The practical move: get the right person (your CPA or a SaaS-savvy accountant) to look at your model and your standard agreement together, because the words in the contract quietly decide when, and over what period, you get to recognize the money. The sales-tax side of SaaS is a separate but related headache (see Sales Tax on SaaS). I hope this helps.

Resources:

• SaaS Agreement Revenue Recognition Issues
• Sales Tax on SaaS
• What SaaS Customers Expect in Their Contracts

Disclaimer:

This post is for informational and educational purposes only, and is not legal advice. You should hire an attorney if you need legal advice, which should be provided only after review of all relevant facts and applicable law.