ASC 606 Revenue Recognition: 5-Step Model With Worked SaaS Examples

ASC 606 (Revenue from Contracts with Customers) is the FASB-IASB joint revenue recognition standard, effective for public companies in 2018 and private companies in 2019. It replaced the patchwork of industry-specific guidance with a single principles-based framework. The core principle: recognize revenue when control of goods or services transfers to the customer, not when cash is received. The 5-step model operationalizes that principle: 1) identify the contract; 2) identify the performance obligations; 3) determine the transaction price; 4) allocate the transaction price to performance obligations; 5) recognize revenue when (or as) each performance obligation is satisfied. The challenge is in applying the steps consistently — particularly identifying performance obligations in bundled contracts, deciding whether revenue should be recognized over time or at a point in time, and handling variable consideration. SaaS subscriptions, multi-element software contracts, percentage-of-completion construction, and gift cards are four common scenarios that exercise all five steps.

A contract under ASC 606 must have all of: approval and commitment by the parties; identifiable rights and obligations; identifiable payment terms; commercial substance; and probability of collection. If any element is missing, the arrangement is not a contract under ASC 606 and revenue recognition is deferred until the criteria are met. Contracts can be written, oral, or implied by customary business practices. Combined contracts. When two or more contracts are entered into at or near the same time with the same customer, they may be combined and treated as a single contract if (a) negotiated as a package, (b) consideration in one depends on the other, or (c) the goods/services are a single performance obligation. This prevents companies from artificially separating contracts to manipulate timing. Contract modifications. A modification is a contract change. Treatment depends on whether the modification adds distinct goods/services and whether the price reflects stand-alone selling prices. If both yes, treat as a separate contract. If only the first, treat as a termination of the old contract and creation of a new one. If neither, treat as part of the original contract (cumulative catch-up).

A performance obligation is a promise to transfer a distinct good or service. Distinct means: capable of being distinct (the customer can benefit from the good or service on its own or with other readily available resources) AND distinct in the context of the contract (the promise is separately identifiable from other promises). Most mistakes happen here. Common scenarios: • SaaS + implementation services. The implementation is typically NOT distinct (the customer cannot benefit from implementation alone) — combined into a single performance obligation if implementation is required to use the SaaS. • Software license + post-contract support. License and PCS are typically distinct (license can be used independent of support; support is a separate ongoing service). • Construction contract phases (foundation, framing, finishing). Typically NOT distinct in the context of the contract — the customer wants a building, not a foundation. Treat as a single performance obligation satisfied over time. • Gift cards (with breakage estimable). The performance obligation is to provide goods or services in the future. Recognize when redeemed; recognize estimated unredeemed (breakage) over the redemption pattern. Warranties. Assurance-type warranties (assuring the product works as promised) are NOT a separate performance obligation; account for under ASC 460 (warranty accrual). Service-type warranties (extended coverage beyond standard) ARE separate performance obligations; recognize over the warranty period.

The transaction price is the amount of consideration the company expects to be entitled to in exchange for the goods or services. It includes: • Fixed consideration (the easy case). • Variable consideration (rebates, refunds, performance bonuses, contingent fees) — estimate using either the expected value method (probability-weighted) or the most-likely-amount method, whichever is most predictive. Apply a constraint: only include amounts that will not result in a significant revenue reversal in the future. • Significant financing components — adjust for time value of money if payment timing differs materially from delivery timing (>1 year between delivery and payment). • Non-cash consideration — measure at fair value of consideration received. • Consideration payable to the customer (rebates, slotting fees) — generally a reduction of transaction price unless for a distinct service from the customer. Worked example. SaaS contract: $120,000 annual fee + $20,000 implementation fee + 10% performance bonus if churn < 5%. The implementation is bundled with SaaS (single performance obligation). The bonus is variable consideration; estimate likelihood and apply constraint. If 75% likely the bonus is earned, expected value = 0.75 × $14,000 = $10,500. But if a significant reversal is possible, constrain the amount included in the transaction price. Variable consideration constraint is one of the trickiest judgments in ASC 606. The rule: include variable consideration in the transaction price only to the extent it is highly probable that a significant revenue reversal will not occur if the estimate is later updated. "Highly probable" is a higher threshold than "probable."

When a contract has multiple performance obligations, allocate the transaction price across them in proportion to their stand-alone selling prices (SSPs). Stand-alone selling price. The price the company would charge for that good or service if sold separately. If observable (separate price lists, recent sales of the same item alone), use it. If not observable, estimate using: • Adjusted market assessment approach (look at competitor pricing, customer willingness to pay). • Expected cost plus a margin approach (cost + appropriate margin). • Residual approach (only when the good is highly variable in price or never sold standalone — back into the SSP from total transaction price). Worked example. Software vendor sells: software license ($60,000 SSP), 1-year PCS ($20,000 SSP), training ($10,000 SSP). Bundle sold for $80,000. Allocate by SSP ratio: License: $80,000 × ($60,000 / $90,000) = $53,333 PCS: $80,000 × ($20,000 / $90,000) = $17,778 Training: $80,000 × ($10,000 / $90,000) = $8,889 Total: $80,000 (matches transaction price). Allocation matters because each performance obligation may have a different recognition pattern: license recognized at delivery (point-in-time); PCS recognized over service period (over-time straight-line); training recognized when delivered (point-in-time).

The recognition decision is the most-tested ASC 606 concept on the CPA FAR section. Revenue is recognized OVER TIME if any of these three criteria are met: 1. The customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine service contracts, SaaS subscriptions). 2. The entity's performance creates or enhances an asset the customer controls as it is created or enhanced (e.g., construction on customer-owned land). 3. The entity's performance does not create an asset with alternative use to the entity AND the entity has an enforceable right to payment for performance completed to date (e.g., custom-built equipment for a specific customer with a non-cancelable contract). If NONE of the three criteria is met, revenue is recognized at a POINT IN TIME — typically when control transfers to the customer (delivery, installation, customer acceptance, depending on the contract). Measuring progress for over-time recognition: input methods (cost-to-cost, hours-to-hours) or output methods (units delivered, surveys of work performed, milestones achieved). Cost-to-cost is the most common method and the focus of percentage-of-completion accounting. Worked Example: SaaS Subscription. Customer pays $120,000 for 12-month SaaS access. Performance obligation: provide SaaS access for 12 months. Recognition: over time (criterion 1 — customer simultaneously receives and consumes benefits as the entity performs). Method: straight-line $10,000/month. Journal entry per month: Dr. Cash (or Accounts Receivable depending on billing); Cr. Subscription Revenue $10,000. Worked Example: Multi-Element Software Contract. License $50,000, 1-year PCS $20,000, training $10,000. License recognized at delivery (point-in-time). PCS recognized over 12 months ($1,667/month). Training recognized when delivered (point-in-time, e.g., $10,000 in the month of training).

Construction Co contracts to build a custom warehouse for $5,000,000. Total estimated cost: $4,000,000. Cost incurred to date: Year 1 $1,000,000; Year 2 $2,500,000; Year 3 (project complete) $4,200,000 (final cost over-budget). The construction contract qualifies for over-time recognition under criterion 2 (customer-owned land — the building enhances an asset the customer controls). Use cost-to-cost method. Year 1: Percent complete = $1,000,000 / $4,000,000 = 25% Revenue recognized = 25% × $5,000,000 = $1,250,000 Gross profit = $1,250,000 − $1,000,000 = $250,000 Year 2: Total costs = $2,500,000. Estimated total cost still $4,000,000. Percent complete = $2,500,000 / $4,000,000 = 62.5%. Cumulative revenue = 62.5% × $5,000,000 = $3,125,000 Year 2 revenue = $3,125,000 − $1,250,000 (year 1) = $1,875,000 Year 2 gross profit = $1,875,000 − $1,500,000 (year 2 costs) = $375,000 Year 3: Project complete. Total costs $4,200,000 (final). Cumulative revenue = $5,000,000 (full contract) Year 3 revenue = $5,000,000 − $3,125,000 (cumulative through year 2) = $1,875,000 Year 3 cost = $4,200,000 − $2,500,000 = $1,700,000 Year 3 gross profit = $1,875,000 − $1,700,000 = $175,000 Total contract gross profit = $250,000 + $375,000 + $175,000 = $800,000 (= $5,000,000 contract − $4,200,000 actual cost). If the estimated total cost had increased above the contract price during execution (cost overrun), the entire estimated loss would have been recognized immediately when identified — the loss-recognition principle prevents deferring known losses.

Retailer sells $1,000,000 of gift cards in November. Historical experience: 90% redeemed within 12 months; 8% redeemed in months 13-24; 2% never redeemed (breakage). Breakage estimate is highly probable (long history; consistent pattern). Recognition pattern: recognize breakage in proportion to redemption pattern of redeemed cards. Simplified pattern: 92% of cards redeemed in some pattern; 8% (=2% breakage / 25% redemption) revenue recognized as breakage. Actually using the proportional method: as redemptions occur, recognize the related breakage proportionally. If $200,000 of cards is redeemed in December, recognize: • Cardholder revenue: $200,000 • Plus proportional breakage: $200,000 × (2/98) = $4,082 • Total revenue recognized: $204,082 The credit side is the gift card liability (Unearned Revenue) being reduced by the redemption + breakage portion. Net: gift card liability decreases by $204,082; revenue increases by $204,082. If breakage is NOT estimable (new product, no history), recognize breakage only when the likelihood of redemption becomes remote. Conservative approach. Gift cards with expiration dates have additional considerations under state escheat (unclaimed property) laws — some states require remitting unredeemed gift card balances to the state. ASC 606 treatment is unaffected by escheat; the state remittance is a separate liability.

ASC 606 problems span the CPA FAR section, intermediate accounting, and many real-world finance roles. The 5-step model is straightforward conceptually but tricky in application — particularly identifying performance obligations in bundled contracts and deciding over-time vs point-in-time recognition. Snap a photo of any ASC 606 problem and AccountingIQ walks through the 5-step model, identifies the performance obligations, allocates transaction price by SSP ratio, applies the over-time criteria, and produces the journal entries. For percentage-of-completion problems, AccountingIQ generates the period-by-period revenue, cost, and gross profit calculations. This content is for educational purposes only and does not constitute accounting advice.