Revenue Recognition (ASC 606): The 5-Step Model

What Is Revenue Recognition (ASC 606)?

Revenue recognition (ASC 606) is the accounting rule that determines when a company records revenue on its income statement. Under ASC 606, and its international twin IFRS 15, revenue is recognized when control of a good or service transfers to the customer, not when the contract is signed and not when cash arrives.

How Revenue Recognition Works

Revenue recognition is an accrual concept, which means it is deliberately decoupled from the bank account. The unit of analysis is the contract. Once a contract exists, the accounting team breaks it into the distinct promises it contains, prices those promises, and then releases revenue into the income statement as each promise is satisfied.

Satisfaction happens in one of two patterns. Some obligations transfer at a point in time, such as a perpetual license delivered on day one or a hardware unit shipped to a customer site. Others transfer over time, which covers most software subscriptions, hosting, and support. Over time obligations are usually recognized ratably, meaning an equal slice each month across the service period. A 24 month subscription worth $240,000 recognizes $10,000 a month, whether the customer paid the whole amount upfront, paid monthly, or has not paid at all yet.

The Five Step Revenue Recognition Model

ASC 606 replaced a patchwork of industry rules with one five step model. Step one is to identify the contract with the customer, which requires enforceable rights, commercial substance, and a probable collection of consideration. Step two is to identify the performance obligations, meaning each distinct good or service the customer could benefit from on its own. A platform subscription, an implementation project, and a training package are typically three obligations, not one line item. Step three is to determine the transaction price, including variable consideration such as usage overages or service credits, constrained so that a significant reversal is not probable. Step four is to allocate that price across the obligations based on standalone selling price, the price you would charge if each element were sold alone. This is where discounting gets interesting: a blanket discount on a bundle must be spread across obligations rather than parked on whichever line is convenient. Step five is to recognize revenue as each obligation is satisfied.

Revenue Recognition in Plain English

You do not earn money when you sign a deal. You earn it when you deliver what you promised. A three year contract signed in December for a service that starts in January produces zero revenue in December, no matter how large the number is. The rules exist so that two companies with identical delivery obligations report the same revenue even if one bills annually in advance and the other bills quarterly in arrears.

Deferred Revenue, Contract Assets, and Contract Liabilities

The gap between billing and delivery lands on the balance sheet. When you invoice ahead of delivery, you record deferred revenue, a liability that says you owe the customer service. When you deliver ahead of your right to invoice, you record a contract asset, which is not yet a receivable because the billing trigger has not occurred. Once you have an unconditional right to payment, the contract asset becomes a receivable. Watching deferred revenue and contract assets move is how a CFO sees the shape of a business: a rising deferred revenue balance means you are collecting earlier than you deliver, which is a working capital advantage. A rising contract asset balance means the opposite.

Why Revenue Recognition Is Not the Same as Getting Paid

This is the most common founder error in the category. Financing a contract changes when cash arrives. It does not change when revenue is recognized. If you sell a 24 month subscription and a financing partner pays you the full contract value in week one, you still recognize 1/24th of the revenue each month, because your delivery obligation has not moved. The upfront cash sits as deferred revenue and unwinds on the same schedule it always would have. The same logic runs in reverse: agreeing to let a customer pay over 36 months does not delay revenue recognition on a product that transferred at delivery. Confusing the two produces two bad outcomes, an income statement that overstates performance and a cash forecast that is not connected to reality.

Revenue Recognition (ASC 606) and the Closing Motion

Revenue recognition sits underneath every stage of the Closing Motion, but it does not control any of them. Propose and Close set the contract, the obligations, and the transaction price, which is exactly what step one through step four of ASC 606 read. Collect is a separate question: when does the cash actually land. Ratio is built on that separation. With Ratio Trade, the buyer pays monthly or quarterly while the seller collects the full contract value upfront, and the accounting still recognizes revenue as service is delivered. Nothing about the schedule changes, only the cash position behind it. Renew then restarts the cycle with a new contract and a new set of obligations. Treating recognition and collection as two independent timelines is what lets a finance team forecast both without distorting either.

Common Questions About Revenue Recognition (ASC 606)

Does invoicing a customer create revenue?

No. Invoicing creates a receivable and, if the service has not been delivered, a deferred revenue liability. Revenue appears only as the performance obligation is satisfied, which for most subscription software means ratably over the service term.

How does ASC 606 treat a multi element software deal?

Each distinct element is a separate performance obligation with its own recognition pattern. A platform subscription recognizes ratably, a fixed fee implementation typically recognizes as the work is performed, and the total transaction price is allocated across them using standalone selling prices rather than the prices printed on the order form.

Does taking financing on a contract change revenue recognition?

No. Financing affects the timing of cash and the balance sheet presentation, not the timing of revenue. The obligation to deliver is unchanged, so the recognition schedule is unchanged.

Revenue Recognition (ASC 606)