Revenue recognition for SaaS companies determines when and how subscription payments, implementation fees, and usage-based charges are recorded as revenue — following specific accounting standards (ASC 606 in the US, Ind AS 115 in India) that require revenue to be recognised only when performance obligations are satisfied, not simply when cash is received. For Indian SaaS companies — now the second-largest SaaS ecosystem globally — getting revenue recognition right is critical for financial reporting, investor due diligence, and eventual IPO or acquisition readiness. This guide explains the standards and their practical application in 2026.
Last updated October 2026
Why Revenue Recognition Is Complex for SaaS
Unlike a product company that ships goods and recognises revenue at delivery, SaaS revenue involves:
- Subscriptions: Annual contracts paid upfront but services delivered monthly over 12 months. Can you recognise ₹12 lakh upfront or must you spread it across 12 months?
- Implementation and setup fees: One-time fees for onboarding, data migration, customisation. Are these separate revenue or part of the subscription?
- Multi-element arrangements: A deal includes subscription + implementation + training + support. How do you allocate revenue across these elements?
- Usage-based pricing: Revenue varies based on consumption (API calls, storage, users). When do you recognise it?
- Free trials and freemium: No revenue during trial — but what about costs incurred to deliver the trial?
- Discounts and credits: Volume discounts, promotional pricing, and customer credits affect recognised revenue.
The Five-Step Revenue Recognition Framework
Both ASC 606 (US GAAP) and Ind AS 115 (India) follow the same five-step model:
Step 1: Identify the Contract
A contract must have: approval by both parties, identified rights and payment terms, commercial substance, and probable payment collection. For SaaS:
- Your subscription agreement or order form is the contract.
- Click-through terms of service (for self-serve plans) are valid contracts.
- Month-to-month subscriptions create a new contract each month (or a single contract with monthly performance obligations).
Step 2: Identify Performance Obligations
A performance obligation is a distinct promise to deliver a good or service. SaaS companies typically have:
- Subscription/access: The core SaaS service — a “stand-ready” obligation delivered over time.
- Implementation: Setup, data migration, configuration. Is it distinct? If the customer can benefit from implementation independently (e.g., a third party could do it), it’s a separate obligation. If implementation is highly intertwined with the subscription and not separately valuable, it’s combined.
- Training: Usually a distinct performance obligation if it has standalone value.
- Premium support: If sold separately from standard support, it’s distinct.
Step 3: Determine the Transaction Price
The total amount you expect to receive. Considerations:
- Fixed subscription fees — straightforward.
- Variable consideration (usage-based revenue) — estimate or constrain to the amount not likely to reverse.
- Discounts and rebates — reduce the transaction price.
- Significant financing component — if there’s more than 12 months between payment and delivery, you may need to account for interest (rare for most SaaS contracts).
Step 4: Allocate the Transaction Price
If there are multiple performance obligations, allocate the total price based on standalone selling prices (SSP). Methods:
- Observable SSP: What you charge for each element when sold separately.
- Adjusted market assessment: What competitors charge for similar services.
- Expected cost plus margin: Your cost to deliver + reasonable margin.
- Residual approach: Allocate remaining price to one obligation after allocating known SSPs to others.
Step 5: Recognise Revenue
- Over time: SaaS subscriptions are recognised ratably over the subscription period. ₹12 lakh annual contract = ₹1 lakh/month revenue.
- At a point in time: Distinct implementation or training — recognised when delivered and accepted.
- Usage-based: Recognised as usage occurs (measured monthly/quarterly).
Indian Accounting Standards: Ind AS 115
Ind AS 115 is India’s revenue recognition standard, converged with IFRS 15 (which is itself closely aligned with ASC 606). For Indian SaaS companies:
- Applicability: Mandatory for listed companies, companies with net worth ≥ ₹250 crore, and their holding/subsidiary/associate companies. Most funded SaaS startups fall under this.
- Key differences from ASC 606: Minimal for SaaS. The five-step model is identical. Differences exist in specific industries (construction, real estate) but SaaS treatment is essentially the same.
- GST treatment: GST collected is excluded from the transaction price (it’s collected on behalf of the government). Revenue is recognised net of GST.
- Foreign currency: For Indian SaaS companies billing in USD, revenue is recognised at the exchange rate on the date the performance obligation is satisfied. Exchange differences are separately recorded.
Common SaaS Revenue Recognition Scenarios
Annual Subscription Paid Upfront
Customer pays ₹12,00,000 for a 12-month subscription on January 1. Revenue recognised: ₹1,00,000 per month from January to December. The remaining amount is “deferred revenue” (a liability on the balance sheet).
Multi-Year Contract with Annual Price Escalation
3-year contract: Year 1 = ₹10,00,000, Year 2 = ₹11,00,000, Year 3 = ₹12,00,000. Total: ₹33,00,000 over 36 months. Recognise ₹91,667/month (₹33,00,000 / 36) throughout the contract — straight-line, not matching invoice amounts.
Implementation Fee + Subscription
₹5,00,000 implementation fee + ₹1,00,000/month subscription (12-month contract). If implementation is a separate performance obligation: recognise ₹5,00,000 when implementation is complete. Recognise ₹1,00,000/month for subscription. If implementation is not distinct (highly intertwined with subscription): combine into total ₹17,00,000 and recognise ratably over 12 months (₹1,41,667/month).
Metrics Affected by Revenue Recognition
- ARR (Annual Recurring Revenue): The annualised value of recurring subscription revenue. NOT the same as total invoiced amount.
- MRR (Monthly Recurring Revenue): ARR / 12. Should reflect recognised revenue, not cash collected.
- Deferred Revenue: Cash collected but not yet recognised. A healthy SaaS company has growing deferred revenue (indicates future recognised revenue).
- Revenue per Employee: Important efficiency metric for Indian SaaS companies targeting ₹1 crore+ revenue per employee for profitability.
Frequently Asked Questions
Can an Indian SaaS startup recognise annual subscription revenue upfront?
No, under Ind AS 115 or ASC 606. Annual subscription revenue must be recognised ratably over the service period (typically monthly over 12 months). Upfront recognition is only permitted when the performance obligation is satisfied at a point in time — for a SaaS subscription, the obligation is satisfied over time as you provide continuous access to the software. Recognising upfront would overstate current-period revenue and misrepresent financial performance.
How should Indian SaaS companies handle free trials for revenue recognition?
Free trials generate no revenue — there’s no contract with consideration (payment). Costs incurred during the trial period are operating expenses. If the trial converts to a paid subscription, revenue recognition begins when the paid contract starts. For freemium models, the free tier is a marketing cost; revenue is recognised only from paying customers.
Is revenue recognition different for companies under Indian GAAP vs Ind AS?
Yes. Companies following Indian GAAP (not yet migrated to Ind AS) use AS 9 for revenue recognition, which is less prescriptive than Ind AS 115. AS 9 doesn’t have the five-step model or detailed guidance on multi-element arrangements. Most funded SaaS startups that plan to go public or raise significant rounds should adopt Ind AS early — investors and auditors will expect it during due diligence.
What happens to revenue recognition during customer churn?
If a customer churns mid-contract: stop recognising revenue from the contract termination date. Any deferred revenue (prepaid but undelivered) is reversed or adjusted based on contract terms. If the contract allows for refunds, you should have already estimated the refund liability. If no refund is due, the remaining deferred revenue is recognised when the termination obligation is fulfilled (usually immediately upon contract end).
Do Indian SaaS companies need a revenue recognition audit?
Any company required to follow Ind AS (and getting statutory audits) will have revenue recognition as a key audit area. For startups before Ind AS applicability, your statutory auditor still reviews revenue recognition under AS 9. For investor-backed startups: your investors’ financial due diligence will scrutinise revenue recognition practices regardless of the applicable standard. Get it right from the start — retroactive corrections are expensive and damage credibility.
