Revenue Recognition Under Ind-AS 115 for SaaS Businesses

Revenue recognition for a SaaS business looks deceptively simple on the surface — bill the customer monthly or annually, recognise revenue as the service is delivered. In practice, Ind-AS 115 (the Indian convergence with IFRS 15) introduces a five-step model that converts what most founders intuitively understand as revenue into a structured exercise that auditors, investors and eventual IPO due diligence will scrutinise line by line.

Get the framework right early and the SaaS company carries clean revenue numbers through every fundraise, every audit and ultimately the listing process. Get it wrong, and the retrospective adjustments at Series C diligence become a serious credibility issue. This is the practitioner’s walkthrough.

The five-step model — what Ind-AS 115 actually says

The standard prescribes a structured analysis for every customer contract:

Step 1 — Identify the contract. A contract is an agreement between two or more parties that creates enforceable rights and obligations. The agreement can be written, oral or implied by customary business practices. Critically, collection must be probable — if a customer’s ability to pay is in serious doubt, no contract exists for accounting purposes even if a legal agreement is signed.

Step 2 — Identify the performance obligations.A performance obligation is a promise to transfer a distinct good or service to the customer. A contract may contain one or many performance obligations. The distinctness test asks: can the customer benefit from the good or service on its own, and is the promise separately identifiable from other promises in the contract?

Step 3 — Determine the transaction price. The amount the entity expects to be entitled to in exchange for transferring the promised goods or services. Includes variable consideration (discounts, rebates, performance bonuses), significant financing components, non-cash consideration and amounts payable to the customer.

Step 4 — Allocate the transaction price. Where there are multiple performance obligations, the transaction price is allocated to each on a standalone selling price (SSP) basis. SSP is the price at which the entity would sell the good or service separately to a customer.

Step 5 — Recognise revenue when (or as) the performance obligation is satisfied. Revenue is recognised when control of the good or service is transferred to the customer. This may be at a point in time (e.g., one-time setup) or over time (e.g., subscription service).

The SaaS subscription — recognised over time

A SaaS subscription is a classic over-time performance obligation — the customer simultaneously receives and consumes the benefit of the service throughout the subscription period. Revenue is recognised ratably over the contract term, typically straight-line.

Example: ₹1.2 lakh annual subscription invoiced upfront. Recognise ₹10,000 per month over the 12 months of the subscription. The ₹1.2 lakh sits as deferred revenue (a contract liability) at invoice date; ₹10,000 transfers to revenue each month; closing deferred revenue at month 12 is zero.

This is mechanically simple but creates a structural balance sheet feature — significant deferred revenue (contract liability) on the balance sheet at all times, equal roughly to half of annual contracted recurring revenue. Investors are comfortable with this; auditors test it tightly for cut-off.

The setup fee problem — multi-element arrangements

A B2B SaaS contract typically includes both a one-time setup / implementation fee and an ongoing subscription. The question: is the setup fee a separate performance obligation, or is it part of the subscription?

The distinctness test: can the customer benefit from the setup service on its own? Usually NO — the setup is a prerequisite to using the SaaS but has no standalone economic value if the subscription doesn’t continue. In that case, the setup fee is NOT a separate performance obligation; it is deferred and recognised as revenue ratably over the expected customer relationship period (often longer than the subscription term — typically 3-5 years for enterprise SaaS).

The implication: a ₹5 lakh setup fee on a ₹2 lakh annual subscription doesn’t flow through P&L as ₹5 lakh revenue on signature. It sits as deferred revenue and trickles through over (say) 36 months — ₹13,889 per month. Founders frequently are surprised by this; the cash hit the bank account on day 1, but the revenue is recognised over years.

The exception: if the setup service includes deliverable IP (e.g., a custom integration, a configured workflow, a data migration output) that the customer can use independently of the SaaS subscription, then the setup may be a separate performance obligation recognised at a point in time. This requires real standalone value — the test is rigorous.

Usage-based pricing — variable consideration

Usage-based SaaS (per-API-call, per-message, per-transaction) falls under variable consideration. The transaction price for each billing period is the usage actually incurred — recognised when the usage occurs, since the customer simultaneously receives and consumes the service.

For contracts that mix a committed minimum with usage above the minimum (e.g., “you commit to 1 million API calls per month at ₹0.10 per call, with overage at ₹0.15 per call”), the committed portion is recognised ratably; the variable portion is recognised as usage materialises. Tracking is more intricate than pure subscription accounting; the systems need to consume real usage data in close-to-real-time.

Contract modifications — when the deal changes mid-term

Mid-term contract changes (upsells, downgrades, term extensions, mid-cycle pricing changes) are explicitly addressed in Ind-AS 115. The accounting treatment depends on whether the modification adds distinct goods/services at their SSP:

(a) Modification adds distinct services priced at SSP — treat as a separate contract. Original contract continues unchanged; new contract accounted for prospectively.

(b) Modification adds distinct services NOT at SSP — terminate the original contract and treat the remaining old performance obligation plus the new addition as a new contract. Reallocate all remaining transaction price.

(c) Modification doesn’t add distinct services (e.g., a price reduction on the existing subscription) — adjust revenue recognition prospectively to reflect the modified contract.

The case (b) treatment — terminate + restart — is the one most founders are unaware of, and it causes the most revenue volatility. A customer upgrading mid-term from a ₹5 lakh contract to a ₹15 lakh contract at a discount can require a revenue re-allocation that produces a one-time true-up in the quarter of modification.

Sales commissions — the deferral question

Ind-AS 115 also addresses incremental costs of obtaining a contract — most notably, sales commissions. If a commission is paid to the salesperson specifically because the contract was won, and the commission would not have been paid otherwise, it must be capitalised and amortised over the expected customer relationship period (consistent with how the related revenue is recognised).

For a ₹10 lakh ARR contract with a ₹1 lakh sales commission, the commission is capitalised as a contract acquisition cost asset and amortised over (say) 36 months — ₹2,778 per month through opex. Common practical exception: if the amortisation period would be 12 months or less, the commission can be expensed in the period incurred under the practical expedient.

The deferred commission asset adds complexity to the balance sheet but matches the cost recognition to the revenue recognition — important for investors evaluating gross margin and CAC trends.

The IPO impact — why this matters now, not at filing

For a SaaS company on an IPO trajectory (SME or mainboard), revenue recognition is the single most scrutinised area in DRHP financial diligence. Restated financials under Ind-AS for the three years preceding the IPO must be Ind-AS 115 compliant; any material misstatement or change in policy is a flag for the BRLM, the auditor, and ultimately SEBI.

Companies that converted to Ind-AS 115 at the deadline (FY18-19 for most listed companies) and have applied it consistently are clean. Companies that have been growing fast on aggressive revenue recognition (recognising upfront fees as revenue, not deferring setup, missing variable consideration estimates) need restatement that can move revenue by 10-25% across years. Investors notice; valuations suffer.

The right time to fix revenue accounting is when the company is small, not when the company is preparing for an IPO 18 months out. The cost of fixing it early is the engagement of a competent auditor / CA; the cost of fixing it late is restated financials, lower revenue numbers in the DRHP, and a damaged credibility narrative with investors.

The disclosure requirements

Ind-AS 115 mandates extensive revenue disclosures in the financial statements: disaggregation of revenue by category (product, geography, customer type, timing of transfer), contract balance reconciliations (opening receivables, closing receivables, contract assets, contract liabilities), remaining performance obligations and the expected timing of recognition, significant judgements applied in the five-step model.

For unlisted private SaaS companies, full Ind-AS 115 disclosure isn’t mandatory until the company crosses the Ind-AS applicability threshold or the company applies Ind-AS voluntarily. For listed companies and for companies approaching IPO, full disclosure is mandatory and is one of the most prominent sections of the financial statements.

Bottom line

Ind-AS 115 is a five-step framework that converts the intuitive “bill the customer, recognise revenue” into a structured exercise around performance obligations, transaction price, allocation and timing. For SaaS businesses, the standard’s key working features are: subscription revenue over time (ratable); setup fees deferred over customer relationship period (not on signature); usage-based revenue recognised as variable consideration; sales commissions capitalised and amortised. Get the model right early, document the judgements, and the financials carry through every fundraise and every audit cleanly — instead of being restated 18 months before the IPO at significant cost to credibility.