Revenue Recognition: When Sales Get Recorded

Key Takeaways

• Revenue recognition determines timing, not amount, a sale is recorded when control transfers to the customer, not when cash is collected.
• ASC 606 and IFRS 15 replaced dozens of industry-specific rules with a single five-step model effective for public companies in 2018.
• A growing deferred revenue balance is a positive signal for subscription businesses; a shrinking one can warn of slowing demand before revenue declines.
• Ballooning accounts receivable relative to revenue growth is a classic early warning of channel stuffing or premature revenue booking.

What It Is

Revenue recognition determines the timing and amount of revenue reported to shareholders. Under accrual accounting, revenue is recognized when it is earned, which is not necessarily when cash changes hands. A software company that collects three years of subscription fees upfront does not get to report all that revenue on day one. A consulting firm that completes a project in December but invoices in February still reports the revenue in December.

The rule matters because revenue is the top line of the income statement. Every margin, every growth rate, and every valuation multiple flows from it.

The Intuition

Without a consistent rule, two identical transactions could be reported differently by two companies, or by the same company in two different years. Revenue recognition standardizes the question of "when did this sale happen?" so investors can compare businesses on the same basis.

The guiding idea is transfer of control. You earn revenue when you give the customer what you promised, priced to reflect what you expect to collect. Cash timing is a separate matter handled on the cash flow statement and the balance sheet.

How It Works

The controlling standard is ASC 606 in US GAAP and IFRS 15 under international rules. Both were published jointly by FASB and the IASB in May 2014 and became effective for public companies in 2018. They replaced dozens of industry-specific rules with a single principle-based framework that works across software, construction, manufacturing, media, and services.

The standard sets out a five-step model:

1. Identify the contract with a customer. A contract can be written, oral, or implied, as long as it creates enforceable rights.
2. Identify the performance obligations in the contract. These are the distinct goods or services the company has promised.
3. Determine the transaction price. This includes fixed amounts, variable consideration (discounts, rebates, bonuses), and any significant financing component.
4. Allocate the transaction price to the performance obligations, usually in proportion to their standalone selling prices.
5. Recognize revenue when (or as) each performance obligation is satisfied, meaning when the customer obtains control of the promised good or service.

Obligations can be satisfied at a point in time (typical for product sales, when goods ship and title transfers) or over time (typical for services and long construction contracts, recognized as work progresses). IFRS 15 and ASC 606 are worded almost identically on these points, which is why a multinational can prepare one set of figures that serves both US and international investors.

Worked Example

A software vendor signs a three-year contract with a customer for $360,000. The deal bundles a perpetual software license ($120,000 standalone price), three years of post-contract support ($180,000 standalone price, $60,000 per year), and one training workshop ($60,000 standalone price).

Applying the five steps:

1. The written contract is the agreement.
2. Three performance obligations: license, support, training.
3. Transaction price: $360,000.
4. The $360,000 is allocated across the three obligations in proportion to their $360,000 standalone selling prices. The allocation matches the standalone prices exactly.
5. Recognition timing:
   • License is recognized at the point in time control transfers, typically at contract inception: $120,000.
   • Support is recognized over time as the service is delivered: $60,000 per year for three years.
   • Training is recognized when the workshop is delivered: $60,000 on that date.

In year one, reported revenue could be $120,000 (license) + $60,000 (year one support) + $60,000 (training) = $240,000, even though the company may have collected the entire $360,000 in cash. The uncollected portion, or the unearned portion of collected cash, sits on the balance sheet as deferred revenue until the obligation is satisfied.

Common Mistakes

1. Assuming bookings equal revenue. Bookings are the total value of contracts signed. Revenue is the portion that has been earned under ASC 606 or IFRS 15. Subscription businesses routinely have bookings far larger than current-period revenue, with the difference sitting in deferred revenue on the balance sheet.

2. Ignoring deferred revenue. A growing deferred revenue balance is usually a healthy sign for a subscription business, because it represents future revenue already contracted. A shrinking balance can be an early warning of slowing demand, even when reported revenue still looks fine.

3. Confusing revenue with cash from customers. Revenue is an accrual figure. Cash collections appear in the operating activities section of the cash flow statement. Large, persistent gaps between revenue and cash collected, driven by ballooning accounts receivable, have preceded many major accounting scandals.

4. Missing channel-stuffing and bill-and-hold red flags. Shipping excess product to distributors at quarter-end to book revenue (channel stuffing), or invoicing for goods the customer has asked the seller to hold (bill-and-hold), have been the basis of repeated SEC enforcement cases, including Sunbeam and Bristol-Myers Squibb. Both are often designed to pull revenue forward in ways ASC 606 does not permit.

5. Overlooking software and SaaS nuances. For software, the distinction between a license recognized at a point in time and hosted services recognized over time changes the shape of reported revenue dramatically. Under ASC 606, many previously front-loaded software arrangements now recognize revenue more ratably, which can make year-over-year comparisons across the adoption boundary misleading.

Frequently Asked Questions

Q: What is revenue recognition in simple terms? It is the accounting rule that decides when a sale counts. A company cannot record revenue whenever it wants; it must record it when it has fulfilled its promise to the customer, whether that happens all at once or gradually over time.

Q: How does revenue recognition affect investment decisions? Because every valuation ratio starts from the top line, the timing of revenue recognition shapes reported growth rates, margins, and earnings quality. A company booking revenue aggressively pulls forward results that inflate current-period metrics at the expense of future periods.

Q: What is a real-world example of revenue recognition? Under the old rules, many software companies recognized the entire license value upfront. Under ASC 606, bundled arrangements that include ongoing support must split the revenue across deliverables and recognize the support portion ratably over the service period, compressing reported near-term revenue.

Q: How can investors spot revenue recognition problems? Compare revenue growth to changes in accounts receivable and deferred revenue each quarter. If receivables are growing significantly faster than revenue, cash is not following the booked sales. If deferred revenue is flat or falling while revenue rises, future contracted work may not be growing as fast as reported results suggest.

Q: How is revenue recognition different from cash collection? Revenue recognition is an accrual concept, it records when the obligation to the customer is satisfied. Cash collection is a cash-basis concept, it records when money arrives. The gap between the two sits on the balance sheet as either accounts receivable (revenue earned, cash not yet received) or deferred revenue (cash received, revenue not yet earned).

Sources

1. Financial Accounting Standards Board. "Revenue from Contracts with Customers (Topic 606), Accounting Standards Update No. 2014-09." https://storage.fasb.org/ASU%202014-09_Section%20A.pdf
2. Financial Accounting Standards Board. "Revenue Recognition, Project Summary." https://fasb.org/page/PageContent?pageId=/projects/recentlycompleted/revenue-recognition-summary.html
3. IFRS Foundation. "IFRS 15 Revenue from Contracts with Customers." https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/
4. Financial Accounting Standards Board. "Comparison of Topic 606 and IFRS 15." https://storage.fasb.org/Comparison%20of%20Topic%20606%20and%20IFRS%2015.pdf
5. US Securities and Exchange Commission. "In the Matter of Sunbeam Corporation, Administrative Proceeding 33-7976." https://www.sec.gov/enforcement-litigation/administrative-proceedings/33-7976

Disclaimer

This article is educational content only and is not financial advice. Nothing here is a recommendation to buy, sell, or hold any security. Consult a licensed advisor before making investment decisions.