The Five-Step Model

ASC 606 replaced the patchwork of industry-specific revenue recognition standards with a single, principles-based framework. It answers one question through five steps: when and how much revenue should a company recognize from a contract with a customer? For SaaS companies, this framework governs how subscription fees, implementation services, professional services, and usage-based revenue are recognized — and getting it wrong creates audit findings, restatement risk, and investor distrust.

1. Step 1: Identify the Contract A contract exists when both parties have approved it, each party's rights are identifiable, payment terms are defined, the contract has commercial substance, and collection is probable. In SaaS, the contract is typically the signed subscription agreement plus any SOWs. A verbal agreement or an unsigned order form is not a contract under ASC 606 — regardless of what the CRM says.
2. Step 2: Identify Performance Obligations A performance obligation is a promise to deliver a distinct good or service. A SaaS contract may have multiple: the subscription (ongoing access), implementation (one-time setup), training (knowledge transfer), and premium support (ongoing service). Each distinct obligation is a separate unit of account — and may be recognized on a different timeline.
3. Step 3: Determine the Transaction Price Total consideration expected from the contract, adjusted for variable consideration (usage fees, SLA credits), significant financing components (extended payment terms), and non-cash consideration. A $120K annual contract with net-90 terms and a 2% SLA credit risk has a transaction price below $120K.
4. Step 4: Allocate the Transaction Price Allocate the total price to each performance obligation based on relative standalone selling prices. If the subscription has a standalone price of $100K and implementation has a standalone price of $25K, the $120K contract allocates $96K to subscription and $24K to implementation (ratio of 100:25 applied to $120K).
5. Step 5: Recognize Revenue Recognize revenue when (or as) each performance obligation is satisfied. Subscriptions are satisfied over time — recognized ratably over the subscription term. Implementation is satisfied at a point in time — recognized when the implementation is complete and the customer accepts. The timing of recognition is driven by the obligation, not the invoice.