# Step-by-Step Solution: Multi-Element SaaS Contract Revenue Recognition (ASC 606) ## Scenario Recap A US SaaS company signs a **5-year contract** for: - Software licenses (right to access) - Customization services - Cloud hosting - Performance bonuses (variable consideration) - Renewal options We will identify performance obligations, allocate the transaction price, apply variable consideration constraints, and show the revenue recognition pattern using a diagram. --- ## 1. Identify Performance Obligations **A. Software Licenses:** - If "right to access," then a series service over the term. **B. Customization Services:** - Distinct if customization does not significantly modify the core software. - Recognized as a separate obligation if customer can benefit from it alone. **C. Cloud Hosting:** - Continuous service for 5 years. **D. Performance Bonuses:** - Variable consideration contingent on performance metrics. **E. Renewal Options:** - If option provides a material right, it is a separate performance obligation. **Obligation List:** 1. Software license (right to access, 5 years) 2. Customization (distinct service, upfront) 3. Cloud hosting (series, over 5 years) 4. Performance bonus (variable, estimate as probable) 5. Renewal option (only if material right) --- ## 2. Allocation of Transaction Price **Assume:** - Total contract value (fixed): $1,000,000 - Performance bonus: up to $100,000, estimated at $60,000 (probable to achieve) - Standalone Selling Prices (SSP): - Software license: $400,000 - Customization: $200,000 - Hosting: $400,000 - (Renewal option: assume immaterial for simplicity) **Step A:** Estimate transaction price - Fixed: $1,000,000 - Add variable: $60,000 (most likely amount method or expected value, constrained as per ASC 606-10-32-11) **Step B:** Allocate proportionally - Total SSP = $1,000,000 - Allocation ratio: - License: 40% ($400,000 / $1,000,000) - Customization: 20% - Hosting: 40% - Allocated amounts: - License: $424,000 ($1,060,000 × 40%) - Customization: $212,000 - Hosting: $424,000 --- ## 3. Variable Consideration Constraints - **Performance Bonus:** - Include only portion for which it is probable that revenue will not reverse. - If only $60,000 is probable, only that is included in the transaction price. --- ## 4. Revenue Recognition Pattern | Obligation | Pattern | Timing | |-----------------|---------------------|----------------------| | License | Over 5 years | Straight-line | | Customization | Over customization | Upfront (as delivered)| | Hosting | Over 5 years | Straight-line | | Performance Bonus | As earned (likely tied to hosting/license usage) | As probable/earned | --- ## 5. Multi-Stage Timeline Diagram ```mermaid gantt title SaaS Contract Revenue Recognition Timeline (5 Years) dateFormat YYYY-MM-DD section Contract Inception Contract Signed :a1, 2024-01-01, 1d section Customization (Obligation 2) Customization Work :a2, after a1, 90d Customization Revenue :milestone, after a2, 1d section Software License (Obligation 1) License Access :a3, 2024-01-01, 5y License Revenue :a4, 2024-01-01, 5y section Cloud Hosting (Obligation 3) Hosting Service :a5, 2024-01-01, 5y Hosting Revenue :a6, 2024-01-01, 5y section Performance Bonus (Obligation 4) Performance Metric Period:after a1, 5y Bonus Revenue Recognized :after a1, 1y Bonus Revenue Recognized :after a1+1y, 1y Bonus Revenue Recognized :after a1+2y, 1y Bonus Revenue Recognized :after a1+3y, 1y Bonus Revenue Recognized :after a1+4y, 1y ``` **[Diagram Alt Text: Gantt chart showing contract inception, customization completed upfront, license and hosting revenue recognized evenly over 5 years, performance bonus recognized as earned each year.]** --- ## 6. Summary Table: Revenue Recognition by Year | Year | Customization | License | Hosting | Perf. Bonus* | Total | |------|--------------|---------|---------|--------------|--------| | 1 | $212,000 | $84,800 | $84,800 | $12,000 | $393,600 | | 2 | – | $84,800 | $84,800 | $12,000 | $181,600 | | 3 | – | $84,800 | $84,800 | $12,000 | $181,600 | | 4 | – | $84,800 | $84,800 | $12,000 | $181,600 | | 5 | – | $84,800 | $84,800 | $12,000 | $181,600 | |**Total**|$212,000|$424,000|$424,000|$60,000|$1,120,000| *Assumes linear recognition of performance bonus over 5 years (actual pattern may vary based on performance). --- ## 7. Key Points - **Performance obligations** must be separately identified. - **Transaction price** (including variable consideration) is allocated based on relative SSP. - **Constraints** applied to variable consideration to avoid overestimating revenue. - **Revenue is recognized** as each obligation is satisfied: upfront for customization, ratably for license/hosting, as earned for bonuses. --- **Final Answer:** - Identify and separate all performance obligations. - Allocate transaction price (including probable variable consideration) based on SSP. - Recognize revenue for each obligation as it is satisfied, applying constraints for variable consideration. - The provided timeline diagram illustrates contract inception, obligation split, allocation, and revenue flow over the contract term.