Revenue is the most scrutinized line on every financial statement — and the most manipulated. Libby's Chapter 6, expanded by ASC 606, establishes the authoritative answer to 'when is a sale a sale?' The five-step model governs every revenue transaction across every industry, replacing decades of industry-specific rules with a single conceptual framework.
For a hot dog stand, revenue recognition is trivial: customer pays $3, hot dog delivered, $3 of revenue recorded. But modern business rarely works this cleanly. Software companies sell annual subscriptions with implementation services and hardware bundled together. Construction companies sign multi-year contracts for complex projects. Real estate developers collect deposits years before delivering homes. Retailers sell gift cards, loyalty points, and extended warranties alongside the primary product. For every one of these, 'when is the sale a sale?' requires careful analysis.
Before ASC 606, revenue recognition rules were a patchwork: different standards for software, construction, real estate, and retail. Companies in adjacent industries followed different rules, making comparison difficult. In 2018, ASC 606 replaced this patchwork with a single five-step framework applicable to all revenue contracts in all industries. Understanding the five steps means you can analyze any revenue transaction.
The core principle of ASC 606: recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. Translation: record revenue when you've actually delivered what the customer paid for, at the amount you expect to receive. Not when cash arrives. Not when the contract is signed. When the obligation is fulfilled.
ASC 606 — Five-Step Revenue Recognition Framework
Applies to all revenue contracts in all industries since 2018
Identify the Contract
Does a valid contract exist?Approved by both parties. Identifies rights and payment terms. Commercial substance. Collection is probable.
Identify Performance Obligations
What distinct promises were made?Each distinct good or service is a separate obligation. Bundled contracts must be decomposed. Distinct = customer can benefit from it independently.
Determine Transaction Price
How much will we receive?Fixed consideration + variable consideration (discounts, returns, royalties, rebates). Constrain variable amounts — only include amounts that are 'highly probable' not to reverse.
Allocate Price to Obligations
How is the price split?Based on standalone selling prices (SSP) of each obligation. If total SSP = contract price, allocation = SSP. Otherwise allocate proportionally.
Recognize Revenue
When is each obligation satisfied?Point in time: when control transfers (most goods). Over time: customer simultaneously receives & consumes, or asset built on customer's site, or no alternative use + right to payment.
Point-in-Time Recognition
When control of the asset transfers to the customer. Most product sales.
Over-Time Recognition
Subscriptions, long-term contracts, services performed continuously.
Figure 6.1 — ASC 606 replaced dozens of industry-specific standards with a single principles-based framework in 2018.
| Step | Question | Software Bundle Example ($120,000 contract) |
|---|---|---|
| Step 1: Identify the contract | Does a valid contract exist? Are the parties committed? Payment terms defined? | Yes — written SaaS agreement, $120K price, 2-year term, both parties signed |
| Step 2: Identify performance obligations | What distinct goods/services did you promise? Each distinct promise = one performance obligation | 3 obligations: (1) software license, (2) implementation services, (3) ongoing support/maintenance |
| Step 3: Determine transaction price | What is the total consideration expected? Variable consideration (discounts, returns, rebates)? | $120,000 total; no variable consideration; no significant financing component |
| Step 4: Allocate price to obligations | Allocate transaction price based on standalone selling prices of each obligation | License: $70,000 (standalone $80K / $140K total SSP × $120K); Implementation: $25,000; Support: $25,000 |
| Step 5: Recognize revenue when (or as) each obligation is satisfied | At a point in time (when control transfers) or over time (continuous delivery)? | License: at delivery (point in time, $70K day 1); Implementation: over 3-month project; Support: ratably over 2 years |
ASC 606 defines a distinct performance obligation as one that the customer can benefit from on its own (or with other readily available resources) and is separately identifiable from other promises in the contract. The software license in the example is distinct — customers could license the software without the implementation service. But if the software requires the company's proprietary implementation to function at all, the license and implementation might be combined into a single performance obligation. This distinction has enormous revenue timing implications.
Revenue is recognized over time if: (1) the customer simultaneously receives and consumes the benefit (a cleaning service), or (2) the company's work creates or enhances an asset the customer controls (construction on customer's land), or (3) the company's work has no alternative use and it has an enforceable right to payment for work done to date. If none of these apply, revenue is recognized at a point in time — specifically when control of the asset transfers to the customer.
The transition to ASC 606 changed revenue timing for many companies. Understanding the industry-specific applications helps analysts anticipate where revenue recognition risk concentrates.
| Industry | Key Revenue Recognition Issue | ASC 606 Treatment | Financial Statement Signal |
|---|---|---|---|
| SaaS / Subscriptions | Annual or multi-year subscription fees received upfront | Recognized ratably over the subscription period | Deferred Revenue (liability) on balance sheet; watch for sudden declines |
| Construction / Engineering | Long-term contracts spanning multiple accounting periods | Percentage-of-completion: revenue recognized as work is performed | Contract assets (unbilled AR) on balance sheet; cost overruns reverse prior revenue |
| Retail / E-commerce | Right of return; loyalty points; gift cards; bundled warranties | Constraint revenue for expected returns; loyalty points allocated separately | Refund liability; deferred revenue for unredeemed gift cards/points |
| Pharma / Biotech | Milestone-based license agreements, royalties, collaborative arrangements | Variable consideration recognized only when highly probable it won't reverse | Large deferred revenue on balance sheet during development phases |
| Automotive | Dealer incentives, extended warranties, residual value guarantees | Volume rebates constrain revenue; warranties are separate performance obligations | Deferred warranty revenue recognized over coverage period |
ASC 606 created two new balance sheet categories. Contract assets (also called 'unbilled receivables'): revenue recognized before the customer has been billed — common in construction and long-term contracts. Contract liabilities (deferred revenue): cash received before revenue has been earned. A company with a large, growing contract asset balance and falling deferred revenue is pulling revenue forward. A company with growing deferred revenue is building a backlog of future recognition — a positive quality signal. Both deserve scrutiny.
Revenue is the most frequently restated line item in financial statements. The five most common manipulation patterns under ASC 606 and prior standards are:
DSO — Days Sales Outstanding
DSO = (Accounts Receivable ÷ Revenue) × 365
Rising DSO while revenue grows signals revenue booking ahead of cash collection — quality risk.
Check 1: Deferred Revenue — is it growing with the business? Flat or declining deferred revenue while revenue grows can mean future revenue is being pulled forward. Check 2: DSO trend — is collection time increasing? Rising DSO signals revenue booked before customers actually pay. Check 3: Revenue-to-cash ratio — take operating cash flow divided by revenue; this should be relatively stable. A declining ratio means more reported revenue is not converting to cash. These three checks, run consistently over 8–12 quarters, will surface most material revenue quality problems.
Key Takeaways
A software company signs a 2-year contract for $240,000 covering: a software license ($140,000 standalone price), 3 months of implementation ($40,000 standalone price), and 24 months of technical support ($60,000 standalone price). The total standalone selling price is $240,000. How much revenue is recognized in month 1?