Accounting

Revenue Recognition (ASC 606)

Definition

Revenue recognition is the set of accounting rules, codified in the U.S. under ASC 606, governing exactly when and how much revenue a company can record for a sale, based on when it actually delivers value to the customer rather than when cash is collected.

For a simple one-time sale, recognition is straightforward: revenue is recorded when the product or service is delivered. It gets more complex for subscriptions, bundled products, or long-term contracts, where ASC 606 requires breaking the contract into distinct performance obligations and recognizing revenue as each one is actually satisfied.

Getting revenue recognition wrong is one of the more common accounting mistakes at a growing company, especially one selling multi-year contracts or bundled packages, and it's exactly the kind of thing that gets restated during diligence if it wasn't handled correctly the first time. Worth setting up properly with an accountant early, rather than fixing it retroactively across multiple years of contracts.

The five steps of ASC 606

Every revenue decision under ASC 606 runs through the same five steps:

  • 1. Identify the contract with the customer: an agreement that creates enforceable rights and obligations.
  • 2. Identify the performance obligations, the distinct things you promised: software access, onboarding, support, hardware.
  • 3. Determine the transaction price, including discounts, credits, and usage-based amounts you can reasonably estimate.
  • 4. Allocate the price across the performance obligations, based on what each would sell for on its own.
  • 5. Recognize revenue when, or as, each obligation is satisfied: over time for a subscription, at a point in time for a one-off delivery.

Where startups get it wrong

  • Annual prepayments booked as revenue on day one. Cash collected for a year of service is deferred revenue until it's earned, month by month.
  • Setup or implementation fees recognized immediately. If the setup isn't a distinct service the customer benefits from on its own, it's usually spread over the contract.
  • Bundles treated as one line. Software plus hardware plus services usually means separate performance obligations, each with its own timing.
  • Multi-year deals with ramps or free months. The total contract value is allocated across the term, not recognized as invoiced.

Why it matters before a raise or exit

Revenue is the number investors and acquirers price you on, so it's the number diligence checks hardest. If revenue was recognized too early, a quality-of-earnings review restates it, and the restated figure is the one the deal uses. Setting up contracts, invoicing, and deferred revenue correctly as you sign customers costs far less than unwinding years of it later.

Worked example: a $36,000 contract with onboarding

Contract
A 12-month software subscription plus onboarding, $36,000 billed up front
If onboarding isn't distinct
All $36,000 is recognized evenly, $3,000 a month, as the software is delivered
If onboarding is distinct
Say its standalone value is $6,000 of the price: it's recognized when onboarding is done, and the remaining $30,000 is recognized at $2,500 a month
Either way
At signing, the unearned amount sits on the balance sheet as deferred revenue, not on the income statement

Illustrative. Whether a service is distinct, and how to allocate the price, depends on the contract's terms.

Questions founders ask

What are the 5 steps of revenue recognition under ASC 606?

Identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, and recognize revenue when or as each obligation is satisfied.

When should a SaaS company recognize revenue?

Ratably over the subscription period, as the service is delivered. An annual prepayment is recorded as deferred revenue and recognized month by month.

Do private startups have to follow ASC 606?

Any company that reports under GAAP does, private companies included. Even before an audit, investors and acquirers expect revenue to follow it and will restate it if it doesn't.

Is deferred revenue a liability?

Yes. It's cash collected for work you still owe the customer, so it sits on the balance sheet as a liability until the revenue is earned.

Want this handled, not just explained?

Staxiom closes your books every month and gives you reports you can actually read. Built by founders, investors, CPAs and startup people.

See if we're a fit