Revenue recognition is the accounting rule set that determines when a startup can record revenue, not just how much. Under ASC 606, the U.S. GAAP standard, a startup cannot recognize a customer’s full contract value the moment it’s signed or paid. Revenue is recognized as the product or service is actually delivered, following a five-step framework.

That’s why “bookings” (what a customer commits to) and “revenue” (what’s been earned so far) are different numbers, and why upfront payments sit in a deferred revenue liability until they’re earned.

For venture-backed startups, revenue recognition isn’t just an accounting technicality. It’s the rule set that determines whether your top-line number is trustworthy to a board, an auditor, or a VC running diligence. Get it wrong, and you risk restating financials mid-raise, which is about as bad as fundraising timing gets.

This guide breaks down ASC 606 in plain English, with a specific focus on revenue recognition SaaS scenarios, including subscriptions, deferred revenue, and the errors Kruze Consulting sees most often when we onboard a new venture-backed client.

This guide covers:

  • Basics: What ASC 606 is and its five-step model
  • Bookings vs. revenue: Why these numbers never match, and why that’s normal
  • Subscriptions: How SaaS companies recognize revenue and handle deferred revenue
  • Investor lens: Why VCs and boards care about how you recognize revenue
  • Common errors: The ASC 606 mistakes that show up most often in diligence

What Is ASC 606, and Why Does It Exist?

ASC 606, “Revenue from Contracts with Customers,” is the revenue recognition standard issued by the Financial Accounting Standards Board (FASB). It replaced a patchwork of older, industry-specific revenue rules with one consistent framework that applies to virtually every company reporting under U.S. GAAP – SaaS, hardware, professional services, biotech, all of it.

The core principle is simple to state, even if it’s not always simple to apply: Recognize revenue when (or as) you transfer control of a good or service to the customer, in an amount that reflects what you actually expect to be paid. ASC 606 operationalizes that principle through a five-step model:

  1. Identify the contract with the customer.
  2. Identify the performance obligations in the contract – the distinct goods or services you’ve promised to deliver.
  3. Determine the transaction price – what you expect to be entitled to in exchange.
  4. Allocate the transaction price across each performance obligation.
  5. Recognize revenue as (or when) each performance obligation is satisfied.

For most venture-backed startups, this means moving off cash-basis bookkeeping and ontoaccrual accounting. At Kruze, we often refer to this as “GAAP with exceptions” for early-stage companies, since full public-company-level GAAP compliance usually isn’t necessary (or cost-effective) pre-Series B.

Bookings vs. Revenue: Why They’re Never the Same Number

One of the most common points of confusion, for founders and sometimes for VCs reading a board deck, is the difference between bookings, billings, and revenue. All three are real, all three matter, and none of them should be used interchangeably:

  • Bookings are the total contract value a customer has committed to, recorded on the date the deal is signed, regardless of when you’ll bill or deliver.
  • Billings are what you actually invoice the customer for in a given period.
  • Revenue is what you’ve earned. It’s the portion of the contract for which you’ve actually delivered the product or service, recognized under ASC 606.

Here’s a concrete example: a customer signs a $120,000, 12-month contract in January and pays the full amount upfront. That’s a $120,000 booking and a $120,000 billing, which are both recorded in January. But revenue is only $10,000 in January, with the remaining $110,000 sitting on the balance sheet as deferred revenue until it’s earned, month by month, over the rest of the contract.

Bookings is a useful sales-momentum metric, but it isn’t defined by GAAP and won’t appear on your financial statements. Our deeper breakdown on bookings vs. revenue walks through more examples, including how ARR fits into this picture.

Subscriptions and Deferred Revenue: How SaaS Companies Actually Recognize Revenue

For a subscription business, revenue recognition SaaS scenarios almost always come down to one pattern: revenue is recognized ratably over the service period, not when cash is collected.

Using the same $120,000 annual contract from above:

  • The full $120,000 is invoiced and collected in January.
  • $10,000 is recognized as revenue each month, as the service is delivered.
  • The unrecognized balance sits in deferred revenue, a liability account on the balance sheet, until it’s earned.
  • By month 6, $60,000 has moved from deferred revenue into recognized revenue, and $60,000 remains deferred.

Deferred revenue matters for reasons beyond compliance. It “smooths out” your revenue line so it actually reflects delivery, and it’s a required input for calculating clean SaaS metrics like MRR, ARR, and the Rule of 40. If your books are still on cash basis, none of those metrics will be reliable. Our guide on switching from cash to accrual accounting covers when and how to make that change.

Subscriptions with bundled elements, like onboarding, implementation, and premium support, add another wrinkle. ASC 606 requires you to evaluate whether each of those is a distinct performance obligation. If onboarding is distinct from the core subscription, its revenue may need to be recognized separately (often upon completion) rather than spread across the same 12-month period as the subscription itself.

Why Investors Care About Revenue Recognition

VCs and board members care about ASC 606 compliance for a few very practical reasons:

  • Comparability. Accrual-basis, ASC 606-compliant revenue lets investors compare your company’s growth to other startups and to public SaaS benchmarks on an apples-to-apples basis.
  • Trustworthy metrics. ARR, MRR, gross margin, and the Rule of 40 are only meaningful if the revenue feeding them was recognized correctly. Garbage in, garbage out.
  • Diligence speed. Revenue recognition is one of the first things a diligence team checks. Clean, consistent policies speed up a raise; restatements slow it down or kill it.
  • Audit and exit readiness. Acquirers and auditors expect ASC 606-compliant revenue. Cleaning it up years later, retroactively, is far more expensive than doing it right from the start.

This is a big part of why due diligence preparation and revenue recognition go hand in hand. Investors aren’t just checking your growth rate, they’re checking whether the accounting behind that growth rate will hold up.

Common ASC 606 Errors Startups Make

In our experience working with venture-backed startups, the same handful of mistakes show up again and again:

  • Recognizing the full contract value upfront. The most common error: booking a prepaid annual contract as 100% revenue in the month it’s paid, instead of spreading it over the service period.
  • Treating bookings as revenue in board decks. Presenting bookings or total contract value as if it were recognized revenue overstates performance and creates a credibility problem when the real numbers surface.
  • Not separating distinct performance obligations. Bundling onboarding, support, or professional services into the subscription revenue line instead of evaluating each as its own obligation.
  • Inconsistent treatment of discounts and free trials. Promotional pricing should reduce the transaction price before allocation, not get layered on inconsistently deal by deal.
  • Staying on cash-basis bookkeeping too long. Once you have recurring, contract-based revenue, cash-basis books simply can’t produce ASC 606-compliant numbers. The conversion to accrual needs to happen before it becomes a fundraising fire drill.

Most of these errors trace back to the same root cause: a startup’s books weren’t built onaccrual accounting from the start. The fix almost always involves a clean-up project: Restating history, documenting a consistent revenue policy, and putting a repeatable monthly close process in place.

Getting Revenue Recognition Right, Before It’s a Problem

ASC 606 isn’t optional once you’re raising institutional capital, and it isn’t something you want to reconstruct retroactively in the middle of due diligence. The startups that handle this well treat revenue recognition as a foundational accounting policy. Decisions are made early, documented clearly, and applied consistently every month, not as a scramble before a raise.

Kruze Consulting builds GAAP-with-exceptions, ASC 606-compliant books for hundreds of venture-backed startups, from a company’s first dollar of revenue through Series C and beyond. Our startup accounting team can review your current revenue recognition policy, fix the errors before they show up in diligence, and make sure your ARR, MRR, and deferred revenue numbers are ones your board and investors can actually trust. Talk to a Kruze startup accountant today and get your revenue recognition built right, before your next raise or audit forces the issue.

Kruze logo

FAQs - Revenue Recognition for Startups: ASC 606 Guide

How do startups recognize revenue?

Venture-backed startups generally use accrual accounting under ASC 606: revenue is recognized as a product or service is delivered to the customer, not when cash is collected or a contract is signed. For a subscription, that typically means recognizing an equal portion of the contract each month over the service period, with the unearned balance held as deferred revenue on the balance sheet.

What is ASC 606?

ASC 606, “Revenue from Contracts with Customers,” is the U.S. GAAP standard issued by the FASB that governs how and when companies recognize revenue. It replaced older, industry-specific revenue rules with a single five-step framework: Identify the contract, identify performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied.

What's the difference between bookings and revenue?

Bookings are the total value of a contract a customer has committed to, recorded when the deal is signed. Revenue is the portion of that contract you’ve actually earned by delivering the product or service, recognized under ASC 606. A large booking can produce very little revenue in its first month if the contract term is long. Both numbers are useful, but they answer different questions.

How do I handle deferred revenue?

Record the full amount billed or collected as a deferred revenue liability on the balance sheet, then recognize it as revenue on the income statement in proportion to the service actually delivered, typically ratably, month by month, for a subscription contract. Deferred revenue shrinks and recognized revenue grows as the company fulfills its obligation to the customer.

Do early-stage startups need to follow ASC 606?

Yes, in practice, once a startup raises institutional venture capital. VCs expect accrual-basis, ASC 606-aligned financials because they underpin trustworthy SaaS metrics like ARR and MRR and because diligence teams check revenue recognition closely. Most early-stage companies apply “GAAP with exceptions” – accrual accounting and the core ASC 606 principles, without every disclosure requirement a public company would need.