Skip to main content

Revenue recognition rules every investor should know

Revenue recognition is the process by which a company decides when to record revenue on the income statement. This sounds dry, but it is where many accounting problems hide. A company might book revenue before it should, recognize revenue from sales that never materialize, or structure transactions to boost reported revenue.

The accounting rules governing revenue are codified in ASC 606 (FASB Accounting Standards Codification Topic 606) in the United States and IFRS 15 internationally. These rules were updated in 2018 to bring greater consistency across industries and tighten loopholes that were previously exploited.

Yet despite the rules, significant judgment remains. Two companies in the same industry can apply ASC 606 differently and report different revenue. Investors who understand the rules can spot when a company is applying them aggressively.

Quick definition: Revenue recognition is the accounting process of determining when to record revenue on the income statement, governed by the five-step ASC 606 model that requires identifying contracts, performance obligations, transaction prices, and the timing of revenue recognition.

Key takeaways​

  • ASC 606 is the unified revenue recognition standard in the U.S., replacing industry-specific guidance
  • Revenue is recognized when a company satisfies its performance obligation and has the right to payment
  • The five-step model provides a framework, but judgment remains in applying it to complex contracts
  • Red flags include sudden revenue accelerations, contracts with unusual terms, and aggressive assumptions
  • Comparing a company's revenue recognition policy to peers' policies can reveal aggressive positioning
  • Auditor changes, restatements, or qualified opinions on revenue are serious warning signs

Before ASC 606: the Wild West​

Before 2018, revenue recognition varied wildly across industries. Software companies, retailers, real estate developers, and contractors each had their own rules. This created inconsistency: two companies with economically identical transactions could report them very differently.

Worse, companies exploited the lack of consistency. Channel stuffing (forcing distributors to buy products they didn't want) was common in software. Side agreements allowing customers to return products were hidden. Revenue was recognized upfront for services delivered over time.

The regulators eventually said: no more. In 2014, the FASB (Financial Accounting Standards Board) and IASB (International Accounting Standards Board) converged on a single standard: IFRS 15 / ASC 606.

The new standard took effect January 1, 2018, and its first year of application (2018-2019) saw numerous revenue restatements as companies adjusted their practices. Companies whose revenue accounting was aggressive had to restate earnings downward. This was a watershed moment: aggressive revenue recognition suddenly wasn't permitted.

The five-step ASC 606 model​

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

Step 1: Identify the contract with a customer. There must be an enforceable agreement with a customer, the parties must have approved the contract and committed to perform, and the contract must specify the payment terms and the company's right to payment.

This seems obvious, but it rules out fake revenue. If a company has no binding contract, or if the customer isn't creditworthy and can't pay, or if the contract terms are so vague that payment is uncertain, revenue shouldn't be recognized.

Step 2: Identify the performance obligations. A performance obligation is a promise to deliver a distinct good or service (or group of goods/services).

A simple transaction like a retail purchase has one performance obligation: deliver the item. A three-year software license with yearly maintenance updates has multiple performance obligations (the license, plus three years of support).

This step matters because it determines how to allocate the transaction price. If a bundle of goods/services includes some delivered upfront and others over time, some revenue is recognized immediately and some over time.

Step 3: Determine the transaction price. The transaction price is the amount the company expects to receive, including:

  • Fixed amounts (the stated price)
  • Variable amounts (volume discounts, penalties, rebates, contingencies)
  • Time-value adjustments if payment is deferred

A company selling a $10,000 product with a 10% volume discount if the customer buys three units has a variable transaction price. The transaction price is $9,000 per unit if all three units are purchased, but $10,000 if only one unit is purchased.

Determining this correctly requires estimating the variable amount. A company might use the "most likely amount" (the single most probable outcome) or the "expected value" (the weighted average of all possibilities), depending on the facts.

This is where aggressive judgment sometimes enters. A company trying to maximize revenue might estimate the variable amount optimistically (assuming discounts won't apply) rather than conservatively (assuming discounts will apply as promised).

Step 4: Allocate the transaction price to performance obligations. If a contract has multiple performance obligations, the transaction price must be split based on the standalone selling price of each obligation.

An enterprise software company bundles three-year software licenses ($300,000) with implementation services ($50,000) and three years of support ($150,000) for a total contract price of $450,000. Under ASC 606, the contract price is allocated proportionately:

  • License: $450,000 × ($300,000 / $500,000) = $270,000
  • Implementation: $450,000 × ($50,000 / $500,000) = $45,000
  • Support: $450,000 × ($150,000 / $500,000) = $135,000

The allocation determines the timing of revenue recognition. License revenue might be recognized upfront; implementation upfront; support over three years.

Step 5: Recognize revenue when (or as) the performance obligation is satisfied. Revenue is recognized either:

  • At a point in time (typically when the customer gains control of the product, like at the point of sale for retail)
  • Over time (as the company delivers the service, like for subscriptions or contracts)

For over-time recognition, the company measures progress toward completion using either output methods (units delivered, milestones reached) or input methods (costs incurred, time elapsed).

Where judgment creates opportunity for manipulation​

The five-step framework is logical, but it contains several judgment points where companies can be aggressive:

Variable consideration: When determining if and how much discount to apply, a company might estimate optimistically. Does the customer actually qualify for the 10% volume discount? Management might assume not, allowing them to record higher revenue now. If the discount is later applied, revenue is reversed.

Standalone selling price: When allocating revenue across multiple obligations, the standalone selling price might not be directly observable. A company might estimate it based on cost-plus markup or market comparables. An aggressive company might assume higher standalone prices for the earliest-recognized obligations and lower prices for later ones, front-loading revenue.

Over-time recognition: When measuring progress on a long-term contract, a company might use input methods (costs incurred) to accelerate revenue recognition, recognizing revenue faster than customers perceive they're receiving value.

Returns and refunds: A company must estimate expected returns. A conservative estimate is 2% of sales; an aggressive estimate is 0.5%. The difference compounds over time.

Real-world revenue recognition examples​

Apple's App Store: When a developer sells an app through the App Store, Apple takes a 30% commission. Apple has two performance obligations: (1) providing the technical platform, and (2) the app itself. Apple allocates 30% of the sale to its platform services and recognizes that over the period the app is available. The remaining 70% is paid to the developer, so Apple is not the principal and doesn't record revenue for the full amount. This distinction—principal vs agent—is crucial. Apple recognizes $30 of a $100 app sale, not $100.

Slack's subscription model: Slack offers annual subscriptions that customers pay upfront. On January 1, Slack receives $10,000 for a one-year subscription. Slack doesn't recognize $10,000 in revenue on January 1; it recognizes $833 per month as the service is delivered. At year-end, Slack has recognized $10,000 but still owes deferred revenue on subscriptions for the portion not yet delivered. This is conservative and reduces the temptation to book all revenue upfront.

Boeing's long-term contracts: Boeing builds commercial aircraft under contracts that span multiple years. Boeing estimates the total cost to build and the total revenue (contract price), then uses the percentage-of-completion method to recognize revenue monthly as the aircraft is built. If Boeing estimates a $500 million contract will cost $450 million and are 50% complete on costs incurred, Boeing recognizes $250 million in revenue. As the contract progresses, estimates might change—if completion costs rise to $480 million, Boeing would downwardly revise revenue and margins. This is volatile, but transparent.

Red flags in revenue recognition​

Unusual contract terms: Most contracts are standard within an industry. If a company is signing contracts with unusual terms—extended payment terms, customer return rights, side agreements, contingent pricing—it might be stretching what constitutes a performance obligation.

Revenue concentration: If a large portion of revenue comes from a single customer or narrow customer base, there's higher risk. If that customer's contract has unusual terms or one-time elements, watch carefully.

Deferred revenue declining: Deferred revenue on the balance sheet shows how much revenue the company will recognize in the future (it's a liability until earned). If deferred revenue is declining faster than revenue is growing, it might signal customer churn, contract cancellations, or reduced future growth.

Sudden revenue acceleration: If revenue growth suddenly jumps without clear business drivers (major marketing success, major product launch, major acquisition), investigate the cause. Is it real market traction, or aggressive accounting?

Changes in revenue recognition policy: If a company changes how it recognizes revenue (e.g., switching from over-time to point-in-time recognition), look at the financial impact. Large revenue increases from policy changes are a yellow flag.

Auditor change: If a company switches auditors, read the SEC filing (Form 8-K). Auditor changes can signal disputes over revenue recognition. The old auditor might have insisted on conservative revenue policies; the new one might not.

Comparison across companies​

Companies in the same industry should have similar revenue recognition policies. If not, dig deeper.

Consider two SaaS companies:

  • Company A: Recognizes subscription revenue monthly as the service is delivered. Also recognizes 100% of customer acquisition costs upfront against revenue.
  • Company B: Recognizes subscription revenue monthly as the service is delivered. Capitalizes customer acquisition costs and amortizes them over the customer lifetime (assume 5-year average customer life).

Company B's reported revenue is identical to Company A's, but its operating margins are different. Company A has lower margins because CAC (customer acquisition cost) is expensed upfront. Company B has higher margins because CAC is capitalized. Neither is wrong under ASC 606, but the difference is material.

Sophisticated investors normalize for these differences before comparing margins.

The auditor's role in revenue recognition​

The auditor is responsible for testing revenue recognition and opining on whether the company's revenue is fairly stated. Auditors typically perform substantive testing: selecting a sample of revenue transactions and verifying that:

  • A binding contract exists
  • The product was delivered or the service was performed
  • The customer is creditworthy and can pay
  • Revenue was recorded in the correct period

Auditors also assess revenue risks. High-risk areas might include:

  • Sales near the end of the accounting period (fourth quarter, year-end)
  • Revenue from new products or customers (policy application is less certain)
  • Revenue from new customer segments or geographies
  • Revenue from unusual transaction structures

If auditors identify revenue risk, they do more testing. If a company's revenue is extremely risky or the auditor can't obtain sufficient evidence, the auditor might qualify the opinion (state that the financial statements are fairly presented except for revenue).

A qualified opinion on revenue is a major red flag for investors.

ASC 606 vs IFRS 15​

Both standards arrived at the same five-step model, so they are largely aligned. However, some differences remain:

  • Contract combinations: IFRS 15 requires contract combinations to be treated as a single contract in more circumstances than ASC 606.
  • Licensing: IFRS 15 has specific rules for software licensing that differ from ASC 606 in timing.
  • Financing components: IFRS 15 requires adjusting the transaction price for financing components; ASC 606 has a practical exemption.

For an investor comparing U.S. and international companies, these differences are small but can affect revenue timing.

Common mistakes when analyzing revenue recognition​

  1. Not reading the revenue policy in the footnotes. The accounting policies note describes exactly how the company recognizes revenue. This is non-negotiable reading.

  2. Assuming all revenue in the industry is recognized identically. It's not. Compare the footnotes.

  3. Ignoring the relationship between revenue and cash flow. If revenue grows 20% but cash from operations grows only 5%, something is off. Investigate.

  4. Not questioning changes in estimates. If a company's estimate of product returns falls from 3% to 1%, revenue increases automatically. Is this justified by actual returns data?

  5. Missing contracts with contingent pricing. A contract that says "customer pays $100,000 if project is completed by date X, otherwise $80,000" has variable consideration. How is this estimated?

FAQ​

Q: Is ASC 606 the same as IFRS 15?
A: They are very similar (converged standards), but some differences remain in how they handle financing components, licensing, and contract modifications.

Q: How do I find a company's revenue recognition policy?
A: Read Note 1 or Note 2 to the financial statements, titled "Summary of Significant Accounting Policies" or "Accounting Policies." This section describes exactly how the company recognizes revenue.

Q: What does it mean if deferred revenue is increasing?
A: It means customers are prepaying for services the company hasn't yet delivered. This is positive because the company has cash but hasn't earned the revenue, signaling future growth is built in. Deferred revenue declining is concerning.

Q: Can a company have qualified revenue recognition despite following ASC 606?
A: Yes. ASC 606 is the standard, but applying it requires judgment. Two companies both following ASC 606 can make different judgments. Investors should compare policies between competitors.

Q: What happens if a company's revenue estimate is wrong?
A: If a company overestimated returns and later adjusted them downward, revenue is increased via a catch-up adjustment. This is a restatement of prior-period revenue, which is a red flag.

Q: Is upfront revenue recognition always aggressive?
A: Not always. If a customer pays cash at a store, recognizing revenue immediately is appropriate and conservative. But if a company recognizes multiyear subscription revenue upfront without a binding contract, that's aggressive.

Q: Why does revenue recognition matter if the same amount will eventually be recognized anyway?
A: Timing matters for investor analysis. A company recognizing revenue too early artificially inflates current-period earnings, which influences stock price and executive bonuses. Eventually the truth emerges, but by then damage is done.

Summary​

Revenue recognition is governed by ASC 606, a five-step model that requires a company to identify contracts, performance obligations, transaction prices, and the timing of recognition. Despite the rules, significant judgment remains, creating opportunities for companies to recognize revenue aggressively. Investors who understand ASC 606 can spot red flags: unusual contract terms, revenue concentration, declining deferred revenue, sudden acceleration without clear business drivers, policy changes, or auditor disputes. Comparing revenue recognition policies across competitors is essential because subtle differences can materially affect reported revenue timing. The auditor's opinion on revenue is the gatekeeper; a qualified opinion or auditor change signals potential problems. Aggressive revenue recognition is often the first sign of accounting trouble, and it always precedes serious restatements. Understanding and questioning how revenue is recognized is one of the most valuable skills an investor can develop.

Next​

Gross revenue vs net revenue: returns, discounts, allowances