Ind AS 115 Revenue Recognition: The 5-Step Model With Examples

Ind AS 115, Revenue from Contracts with Customers, is the single accounting standard that decides when and how much revenue an Indian company can show in its books. Mess this up and your financial statements are wrong — full stop. Whether you run a SaaS startup, a construction firm, or a retail chain, the standard forces you to answer one question before booking any revenue: have you actually delivered what the customer paid for? The five-step model is the structured way to answer that question every single time.

Why Ind AS 115 Replaced the Old Standards

Before Ind AS 115, Indian companies used AS 9 (for goods and services) and AS 7 (for construction contracts). The problem was inconsistency. A software company could book revenue differently from a hardware company selling the same bundled deal. Ind AS 115 — aligned with IFRS 15 — replaced that patchwork with one universal framework. It applies to all companies that prepare Ind AS-compliant financials, including listed companies, their subsidiaries, and large unlisted companies meeting the prescribed thresholds under the Companies (Indian Accounting Standards) Rules.

The 5-Step Model — Explained Simply

Think of these five steps as a checklist you run through for every contract before touching your revenue ledger.

Step 1: Identify the Contract with the Customer

A contract can be written, verbal, or implied by business practice. But it must meet all of these: both parties have approved it, each party's rights are identifiable, payment terms exist, the contract has commercial substance, and it is probable you will collect the consideration. If a customer has a history of not paying and you have no realistic way to recover the money, you cannot recognise revenue even if you delivered the goods.

Step 2: Identify the Performance Obligations

A performance obligation is a promise to transfer a distinct good or service. "Distinct" means the customer can benefit from it on its own or together with other readily available resources. A laptop sold with a one-year on-site maintenance contract has two separate performance obligations — not one. Many businesses collapse these into a single line and that is where the trouble starts.

Step 3: Determine the Transaction Price

The transaction price is the amount you expect to receive. Simple if it is a fixed price. Complicated when you have variable consideration — discounts, rebates, performance bonuses, refund obligations. Ind AS 115 says you estimate variable consideration using either the expected value method (probability-weighted average) or the most likely amount method, whichever predicts better. You include that estimate only to the extent it is highly probable a significant revenue reversal will not occur later.

Step 4: Allocate the Transaction Price

If you have multiple performance obligations, split the transaction price based on their relative standalone selling prices (SSP). SSP is what you would charge for that item if you sold it separately. If you cannot observe an SSP directly, you estimate it — using adjusted market assessment, expected cost plus margin, or (as a last resort) residual approach.

Step 5: Recognise Revenue When (or As) Each Obligation Is Satisfied

Revenue is recognised either over time or at a point in time. Over time applies when: the customer simultaneously receives and consumes the benefit, you create or enhance an asset the customer controls, or you create an asset with no alternative use and you have an enforceable right to payment for work done. If none of these conditions exist, you recognise revenue at a point in time — typically when control transfers to the customer.

Worked Example: Software + Annual Maintenance Contract

Imagine TechSolve Pvt Ltd signs a contract with a manufacturer for ₹12,00,000. The deal includes:

• A perpetual software licence — standalone price ₹9,00,000
• One year of on-site technical support — standalone price ₹3,00,000

Total standalone selling prices = ₹12,00,000 (equal to contract price, so no discount to allocate here). Allocation is straightforward:

So on Day 1 (software delivered), TechSolve books ₹9,00,000 as revenue. The remaining ₹3,00,000 goes to a Contract Liability (deferred revenue) and is released at ₹25,000 each month. If TechSolve had booked the full ₹12,00,000 on Day 1, it would be overstating revenue by ₹3,00,000 — a material misstatement.

Over Time vs. Point in Time — Quick Comparison

Contract Assets vs. Contract Liabilities — Don't Confuse Them

A Contract Asset arises when you have satisfied a performance obligation but your right to receive payment is conditional on something else (e.g., completing another phase). A Contract Liability arises when you receive payment before satisfying your obligation — the classic advance or deferred revenue scenario. These sit on the balance sheet and move as obligations are fulfilled. Many businesses incorrectly call both of these "debtors" or "advances" and bury them — that is a disclosure violation under Ind AS 115.

Common Mistakes Businesses Make

• Treating a bundle as one obligation: Selling a product with free installation, warranty, and a helpline? Each distinct promise is a separate obligation. Lumping them inflates early revenue and defers nothing.
• Ignoring variable consideration: If your contract has early-payment discounts or volume rebates, you must estimate and constrain them upfront — not adjust after the fact at year-end.
• Wrong measure of progress for over-time obligations: Using billing milestones as a proxy for revenue recognition only works if those milestones faithfully depict actual work done. Many construction firms use invoice dates — that is an input/output mismatch.
• Skipping the collectability test: A contract where recovery is doubtful should not even clear Step 1. Booking revenue and then writing it off later is not the same as never recognising it — the income statement effects differ.
• Not disclosing disaggregated revenue: Ind AS 115 requires you to break revenue into categories that show how economic factors affect its nature, timing, and uncertainty. A single line "Revenue from Operations" is almost never enough for a multi-product business.

Practical Tip for Small Businesses

If you are a small business owner trying to get your books Ind AS-compliant, start by listing every type of contract you sign and mapping it through the five steps on paper. Once that logic is clear, your accounting software or ERP should mirror it. For businesses that want professional oversight without a full-time finance team, KyaTax Books handles Ind AS-compliant bookkeeping and revenue recognition schedules as part of its virtual CFO service — so your numbers are audit-ready from the start.

Frequently asked questions

Who does Ind AS 115 apply to in India?

It applies to all companies that prepare financial statements under Indian Accounting Standards (Ind AS) — broadly, listed companies, their subsidiaries, associates, and joint ventures, and unlisted companies meeting the net worth or other thresholds prescribed under the Companies (Indian Accounting Standards) Rules. Smaller companies still under AS (not Ind AS) continue to use AS 9 for now.

What is a "performance obligation" under Ind AS 115?

It is a promise in a contract to transfer a distinct good or service to the customer. "Distinct" means the customer can benefit from it independently or together with other resources they already have. A single contract can contain multiple performance obligations, and revenue is recognised separately for each one as it is satisfied.

How is revenue recognised for long-term construction contracts under Ind AS 115?

If the contract meets the "over time" criteria — typically because the asset has no alternative use and the contractor has an enforceable right to payment for work completed — revenue is recognised progressively using either an input method (costs incurred relative to total expected costs) or an output method (milestones, surveys of work done). The old AS 7 percentage-of-completion concept survives in spirit but must now be applied within this structured framework.

What happens if a customer pays in advance under Ind AS 115?

The advance is recorded as a Contract Liability (deferred revenue) on your balance sheet. Revenue is recognised only when — and as — you satisfy the corresponding performance obligation. The liability reduces and revenue increases in step with delivery. If the advance carries a significant financing component (i.e., the gap between payment and delivery is more than a year), you may also need to account for an interest element under Ind AS 115's financing component guidance.

General information for FY 2026-27, not professional advice for your specific case. Rules change — verify against the latest notification or ask a KyaTax expert.
Related: All free tools · More guides · Virtual CFO