Revenue Recognition for SaaS

ASC 606 explained—understand how to properly recognize subscription revenue and avoid the mistakes that derail fundraises.

Revenue recognition is one of the most important—and most often bungled—areas of startup accounting. For SaaS and subscription businesses, getting this right is critical. Get it wrong, and you could overstate revenue, face audit findings, or delay your next fundraising round.

The Stakes Are High

We've seen startups lose 15-20% of their valuation because of revenue recognition issues discovered during due diligence. The cost to fix these problems often delays fundraising by 3-6 months.

The Basic Principle

Under GAAP (and specifically ASC 606), you recognize revenue when you satisfy a performance obligation—i.e., when you deliver the goods or services you promised.

Not when you sign the contract.

Not when you invoice.

Not when you get paid.

For SaaS companies, this typically means recognizing subscription revenue monthly over the contract period, as the service is delivered.

The Revenue Recognition Rule

You recognize revenue when your customer receives the benefit of your service. For monthly subscriptions, that's every month—so you recognize 1/12 of an annual contract each month, not the full amount when you receive payment.

ASC 606: The Five-Step Framework

ASC 606 uses a five-step framework for revenue recognition:

Step 1: Identify the Contract
A contract is an agreement between you and a customer that creates enforceable rights and obligations. For most SaaS companies, this is a signed agreement or terms of service.

Step 2: Identify Performance Obligations
A performance obligation is a promise to transfer a distinct good or service. For simple SaaS subscriptions, there's typically one performance obligation: providing access to your software over time.

Step 3: Determine the Transaction Price
The transaction price is the amount of consideration you expect to receive. This includes variable consideration like discounts, rebates, and refunds.

Step 4: Allocate the Transaction Price
If a contract has multiple performance obligations, allocate the transaction price proportionally to each.

Step 5: Recognize Revenue When Performance Obligations Are Satisfied
Revenue is recognized when (or as) you satisfy each performance obligation.

How SaaS Revenue Recognition Works

For a typical SaaS subscription, here's how it works:

You sign a customer to a 12-month, $120,000 contract, paid upfront.

At signing, you record $120,000 as Deferred Revenue (a liability on your balance sheet).

Each month, as you provide the service, you recognize $10,000 in Revenue and reduce Deferred Revenue by $10,000.

At year-end, your Deferred Revenue balance should be $0 (assuming no new contracts signed in the last month).

This matches the economic reality: you're earning revenue as you deliver value, not when you get paid.

Common Mistakes

The most common revenue recognition mistake is treating prepaid annual subscriptions as revenue when cash is received instead of recognizing it over the service period.

When a customer pays $120,000 upfront for a 12-month contract, you cannot record $120,000 in January revenue. You must record $120,000 as deferred revenue (a liability) and recognize $10,000 each month as revenue.

This mistake overstates revenue significantly in the first month and creates problems for investors analyzing your financial statements.

What Investors Look For

During due diligence, investors will examine your revenue recognition policy, test a sample of contracts to ensure you're applying the policy correctly, and look for patterns like recognizing all revenue immediately upon contract signing. Any inconsistencies will raise red flags.

Other Revenue Recognition Considerations

Usage-Based Pricing: If you charge based on usage (e.g., API calls), recognize revenue as usage occurs. This requires tracking usage metrics and calculating revenue at each reporting period.

Freemium to Paid Conversions: When a free user converts to paid, the paid portion is recognized as revenue. The free portion was never revenue.

Contract Modifications: If you modify a contract (expand seats, add features), you need to determine whether this creates a new performance obligation or modifies an existing one.

Discounts and Credits: These reduce the transaction price and must be allocated to the relevant performance obligations.

How to Get This Right

Here's how to ensure proper revenue recognition:

Document Your Policy: Write down your revenue recognition policy in detail. What triggers revenue recognition? How do you handle different scenarios?

Be Consistent: Apply the same policy to all similar contracts. Inconsistency is a red flag.

Track Deferred Revenue: Maintain a deferred revenue schedule that shows the beginning balance, additions, reductions, and ending balance each month.

Get Expert Help: Have a fractional CFO or accountant review your revenue recognition before going to investors.

Give Yourself Time: If you need to restate financials, this takes 3-6 months. Don't start fundraising until your revenue recognition is clean.

Key Takeaways

•SaaS revenue is recognized monthly over the contract period, not when cash is received
•Record prepaid subscriptions as deferred revenue, then recognize monthly
•ASC 606 has five steps: identify contract, obligations, price, allocate, recognize
•The most common mistake is recording full payment as immediate revenue
•Get your revenue recognition correct 3-6 months before fundraising

This article is part of our Startup Accounting 101: Everything Founders Need to Know guide.