Revenue Recognition Under ASC 606 and Ind AS 115: A Practical Guide

Revenue recognition is arguably the most judgment-intensive area of accounting. ASC 606 (under US GAAP) and its converged counterpart Ind AS 115 (under Indian GAAP) introduced a unified five-step model that applies across all industries. Understanding this model is essential for any business with complex revenue arrangements.

The Five-Step Model

The framework requires five sequential steps: identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price, and recognize revenue when (or as) each performance obligation is satisfied.

Each step involves judgment, and the cumulative effect of those judgments determines when and how much revenue appears on your income statement.

Step 1: Identify the Contract

A contract exists when there is mutual agreement, identifiable rights and obligations, commercial substance, and probable collectability. For most businesses, this is straightforward - a signed agreement or purchase order. But consider subscription businesses where a customer clicks "agree" on a terms-of-service page. That click creates a contract.

Step 2: Identify Performance Obligations

A performance obligation is a promise to deliver a distinct good or service. The critical word is "distinct" - can the customer benefit from the good or service on its own, and is it separately identifiable within the contract?

For a SaaS company selling software access, implementation services, and training as a bundle, the question is whether each component is distinct. If the implementation significantly customizes the software, it may not be distinct from the software access - resulting in a single performance obligation recognized over time.

Step 3: Determine Transaction Price

The transaction price includes fixed consideration, variable consideration (discounts, rebates, performance bonuses), and the time value of money for long-term contracts. Variable consideration requires estimating the most likely amount or expected value and applying a constraint for amounts not highly probable of non-reversal.

Step 4: Allocate the Transaction Price

When a contract has multiple performance obligations, allocate the total price based on standalone selling prices. If you sell software for 10,000 and training for 2,000 individually, but bundle them for 10,500, allocate based on relative standalone prices: 8,750 to software and 1,750 to training.

Step 5: Recognize Revenue

Revenue is recognized when control transfers to the customer. This happens either at a point in time (product delivery) or over time (service delivery, construction). For over-time recognition, measure progress using input methods (costs incurred) or output methods (milestones completed).

Practical Examples

Construction companies recognize revenue over time using the percentage-of-completion method. A project with a 1 crore contract and 60 percent completion recognizes 60 lakhs in revenue.

SaaS businesses recognize subscription revenue ratably over the subscription period. A 12-month subscription of 1,20,000 generates 10,000 in revenue each month. Implementation fees may need to be spread over the subscription period if not distinct.

Professional service firms recognize revenue as services are performed, typically based on hours delivered relative to total estimated hours.

Automation for Revenue Recognition

Manual revenue recognition tracking in spreadsheets breaks down with scale. When you have hundreds of contracts with varying terms, tracking performance obligations, measuring progress, and computing the correct monthly recognition becomes a significant operational burden.

ThynkBooks revenue recognition module automates the five-step model. Define your revenue arrangement templates, and the system handles allocation, schedule generation, and journal entry creation - with full audit trail for each calculation.