# Integrated IFRS 15 Revenue Recognition with Contract Modification --- ## (a) Identify and Separate Performance Obligations (Decision-Tree Diagram) **Step 1:** List all promised goods/services - Perpetual software license - Cloud hosting (stand-ready) - AI-based customization services - Variable usage-based consideration **Decision-Tree Diagram:** ```mermaid graph TD A[Start: Promised Goods/Services] --> B{Distinct?} B -->|Software License| C[PO1: Perpetual License] B -->|Cloud Hosting| D[PO2: Stand-Ready Hosting] B -->|AI Customization| E{Distinct?} E -->|Yes| F[PO3: AI Customization] E -->|No| G[Combine with License] B -->|Variable Usage| H[PO4: Usage-Based Service] ``` **Explanation:** Each distinct promised good/service is a separate performance obligation (PO) under IFRS 15 if the customer can benefit from it on its own and it is separately identifiable. In this case, all services are distinct. --- ## (b) Transaction Price Allocation Table under IFRS 15 **Step 2:** Allocate total transaction price to POs by their relative standalone selling prices (SSPs). | Performance Obligation | SSP (USD, Example) | % of Total SSP | Allocated Price (USD) | |----------------------------------|--------------------|----------------|----------------------| | Perpetual License | 400,000 | 40% | 400,000 | | Cloud Hosting (10 years) | 300,000 | 30% | 300,000 | | AI Customization | 200,000 | 20% | 200,000 | | Variable Consideration (Est. Yr1)| 100,000 | 10% | 100,000* | | **Total** | **1,000,000** | **100%** | **1,000,000** | \* Variable consideration is estimated based on expected value (constrained by IFRS 15 guidance). **Explanation:** The total transaction price (including estimated variable consideration) is allocated to each PO based on their relative SSPs. This ensures fair revenue allocation as per IFRS 15. --- ## (c) Revenue Recognition Timeline (Diagram) **Step 3:** Identify when and how revenue is recognized for each PO. ``` |-------------------|-------------------|-------------------|-------------------|-------------------| 1 2 ... 5 6 ... 10 (years) ^ |--- License: At contract inception (PO1) |-------------------- Hosting: Over 10 years (PO2) |---> Customization: Recognize as delivered (PO3) |---> Usage: As usage occurs (PO4) ``` **Alt Text:** Timeline showing point-in-time recognition for license, straight-line hosting over 10 years, customization as delivered, and usage-based revenue recognized as incurred. **Explanation:** - Perpetual license: Point-in-time (contract start) - Hosting: Over time (10 years, straight line) - Customization: Over time/as delivered - Usage: As incurred (variable) --- ## (d) Evaluate Contract Modification: Separate Contract or Cumulative Catch-Up **Step 4:** Analyze mid-contract modification due to regulatory change. - **Separate Contract?** *Criteria (IFRS 15.20):* New goods/services distinct + price reflects standalone SSP → Treat as separate contract. - **Cumulative Catch-Up?** If not distinct or price not at SSP, treat as modification to existing contract: reallocate remaining transaction price, cumulative catch-up adjustment. **Example:** - If regulatory intervention changes only cloud hosting price (same service), **not a new distinct PO**, so not a separate contract. - **Journal Entry (Cumulative Catch-Up):** ``` Dr. Contract Asset / Receivable XXX Cr. Revenue - Hosting XXX ``` **Explanation:** Contract modification is not a separate contract if it doesn’t add distinct goods/services at their SSP. Allocate the revised transaction price to remaining POs and use a cumulative catch-up adjustment as per IFRS 15. --- ## **Final Summary Answer** 1. **Identify distinct performance obligations** using a decision-tree: license, hosting, customization, usage-based. 2. **Allocate transaction price to each PO** by relative standalone selling prices, including estimated variable consideration. 3. **Recognize revenue:** License at inception, hosting over 10 years, customization as delivered, usage as incurred. 4. **Modification:** If only price of existing PO changes (not adding distinct goods/services), treat as cumulative catch-up, not a separate contract, with appropriate journal entry.