ASC 606 and the Five-Step Revenue Model

Before 2018, a software company and an airline could recognize revenue under completely different rulebooks, and even within an industry, companies had latitude to pick a moment that flattered them. ASC 606 (and its international twin, IFRS 15) replaced that patchwork with one model that every company, in every industry, has to apply the same way: revenue is recognized when control of a good or service passes to the customer, not simply when cash changes hands or a contract is signed.

The five steps

1. Identify the contract. There has to be commercial substance and a real expectation of collection — a handshake with a customer unlikely to pay doesn't count.
2. Identify the performance obligations. Break the contract into its distinct promises. A software deal bundling a license, a year of support, and installation is really three obligations, not one.
3. Determine the transaction price. The total amount the company expects to be entitled to, including estimates for rebates, refunds, or bonuses.
4. Allocate the price to each obligation, based on what each piece would sell for on its own.
5. Recognize revenue as each obligation is satisfied — at a point in time (shipping a product) or over time (a multi-year service contract).

Worked example

A company sells a machine for $100,000 that comes bundled with two years of maintenance, normally sold separately for $20,000. Standalone, the machine alone would sell for $90,000.

1. Total standalone value: $90,000 (machine) + $20,000 (maintenance) = $110,000.
2. Allocate the $100,000 price proportionally. Machine gets $100{,}000 \times (90{,}000/110{,}000) \approx 81{,}818$, i.e. $81,818. Maintenance gets $100{,}000 \times (20{,}000/110{,}000) \approx 18{,}182$, i.e. $18,182.
3. Recognize on different schedules. The $81,818 for the machine is recognized at delivery, because that obligation is satisfied at a point in time. The $18,182 for maintenance is recognized ratably over 24 months — about $758 per month — because that obligation is satisfied over time.

Even though the customer is billed $100,000 up front, only $81,818 plus one month of maintenance hits revenue in month one. The rest sits on the balance sheet as deferred revenue until it's earned.

What this means in practice

Analysts read the ASC 606 footnotes to see how a company breaks contracts into obligations and how quickly it recognizes revenue relative to billings — recognizing faster than cash comes in builds receivables, recognizing slower builds deferred revenue. Both are normal; a sudden change in the pattern without a change in the business is worth asking about.