Revenue Recognition Under Ind AS 115: The Five Steps That Decide When Sales Hit the Results

Revenue recognition under Ind AS 115 decides something most of us never think about when a results headline flashes on the screen: in which quarter a sale actually counts. The order may be signed in June and the cash may land in December, yet the revenue line follows its own rulebook. If you read quarterly numbers seriously, that rulebook is worth an evening of your time.

Here’s the short version. Ind AS 115, “Revenue from Contracts with Customers”, is the Indian standard that mirrors the global IFRS 15. Both ask a company to run every customer contract through the same five steps before a single rupee goes into the top line. Once you know those steps, a lot of odd-looking results (a sudden revenue jump, a fat “unbilled” balance, a quarter that looks weak despite big order wins) start to make sense.

Where Ind AS 115 comes from

India’s accounting standards, the Ind AS, are named and numbered the same way as the International Financial Reporting Standards, as the overview of Indian Accounting Standards notes. So Ind AS 115 lines up with IFRS 15, and the same overview lists Ind AS 115 as applicable from April 2018. It also shows the old Ind AS 11 on construction contracts as omitted by the Companies (Indian Accounting Standards) Amendment Rules, 2018.

On the global side, the IFRS Foundation’s page on IFRS 15 says the standard was issued in May 2014 and is effective for annual periods beginning on or after 1 January 2018. It replaced a patchwork of older rules, including IAS 11 on construction contracts and IAS 18 on revenue. In plain words: before 2018 a builder, a software exporter and a soap maker could lean on different rules. Now they all start from one framework.

The core idea, in the IFRS Foundation’s own framing, is that revenue should show the transfer of promised goods or services to the customer, at the amount the company expects to be entitled to in exchange. Read that twice. It’s about transfer and entitlement, not about invoices or bank credits.

The five steps of revenue recognition under Ind AS 115

Every contract goes through these five steps, in this order.

Step 1: Identify the contract

First, there has to be a contract with a customer. That sounds obvious, but Investopedia’s explainer on revenue recognition points out that a contract can be written, verbal or implied. What matters is that both sides have clear responsibilities. A purchase order clicked on a portal can qualify just as much as a 200-page EPC agreement.

Step 2: Identify the performance obligations

This is where most of the judgement sits. A performance obligation is a promise in the contract to transfer a good or service that is distinct. One contract can carry several of them. Sell a machine with two years of maintenance, and you’ve likely made two promises, not one.

Step 3: Determine the transaction price

The transaction price is the amount the company expects to be entitled to for delivering what it promised. If part of that is variable, say a bonus for finishing early or a penalty for delay, the company has to estimate the variable amount. This is the step to watch when management talks about “incentive income” or “claims”.

Step 4: Allocate the price to each obligation

If there are several promises, the total price gets split across them on the basis of their relative stand-alone selling prices. In other words, what each piece would sell for on its own decides its share.

Step 5: Recognise revenue when each obligation is satisfied

Revenue is booked when the company satisfies an obligation by transferring the good or service, which the IFRS Foundation describes as the point when the customer obtains control. That can happen at a point in time, which is typical for goods, or over time, which is typical for services. For obligations satisfied over time, the company picks a measure of progress to decide how much revenue belongs in each period.

The top line isn’t a record of cash collected. It’s a record of promises kept, priced the way the contract says they should be.

A worked example: one contract, two revenue streams

Let’s make it concrete with a made-up company. Company M sells industrial pumps. On 1 April it signs a contract with a customer: one pump plus 24 months of maintenance, for a bundled price of ₹12 lakh. The pump is delivered and installed on 1 April. These figures are purely illustrative.

Run it through the steps.

• Contract: signed, with clear terms. Step 1 is done.
• Performance obligations: two. The pump, and the maintenance service.
• Transaction price: ₹12 lakh, with no variable element for now.
• Stand-alone prices: Company M normally sells the pump alone for ₹10 lakh and a 24-month maintenance plan alone for ₹5 lakh. Together that’s ₹15 lakh, so the customer is getting a discount of ₹3 lakh on the bundle.

Allocation uses the relative stand-alone prices. The pump’s share is 10 out of 15, the maintenance plan’s share is 5 out of 15.

Now the timing. The pump is a good, and control passes on delivery, so ₹8 lakh is recognised on 1 April, in the first quarter. The maintenance is a service delivered evenly over 24 months, so ₹4 lakh spread over 24 months works out to about ₹16,667 a month, or ₹50,000 a quarter.

So for this contract, Company M’s first quarter shows ₹8 lakh plus ₹50,000, which is ₹8.5 lakh. Each of the next seven quarters shows just ₹50,000. Same contract, same customer, but the quarterly picture is lumpy at the start and thin after that.

Notice what would happen if the customer paid the full ₹12 lakh upfront. The cash would sit on the books on day one, but only ₹8.5 lakh of it would be revenue in the first quarter. The remaining ₹3.5 lakh would wait on the balance sheet as an obligation still owed to the customer, released quarter by quarter as the maintenance is performed.

What if there’s a bonus?

Change one detail. Suppose the contract adds a ₹1 lakh bonus if the pump runs without a breakdown for the first year. That’s variable consideration, so step 3 needs an estimate of how much Company M expects to be entitled to. A cautious estimate keeps the bonus out until it’s reasonably clear it’ll be earned. An aggressive one books it early. Two companies with identical contracts can show different revenue simply because of how they judge this one line. When you see a management commentary mention “variable consideration” or “estimates of incentives”, this is the trade-off they’re making.

Point in time vs over time: why it changes the results you read

The fifth step is what really shapes a quarterly result. Investopedia gives a neat contrast: a retailer records revenue right after a customer buys something, while an engineering company on a five-year infrastructure project might record revenue as milestones are hit over those five years.

For Indian markets this plays out in a few familiar places.

• Capital goods and EPC companies: long contracts often fall under “over time” recognition, so revenue tracks progress on the project. A big order win shows up in the order book first and in revenue only as work gets done.
• IT services: multi-year deals usually get recognised as the service is delivered. That’s why a large total contract value announcement rarely lifts the very next quarter’s revenue by much.
• Real estate: whether a project’s revenue comes over the construction period or only when control of the flat passes to the buyer depends on the contract terms. That single judgement can swing a developer’s reported revenue sharply between quarters.
• FMCG and retail: mostly point-in-time sales, which is why their revenue lines tend to be smoother and easier to read.

When a company’s revenue jumps in a quarter, ask first whether the business grew or whether a big obligation just happened to finish.

How to read revenue recognition in a quarterly result

You don’t need to be a chartered accountant to use this. A few habits go a long way, and they fit neatly into our wider checklist on how to analyse quarterly results of a company.

1. Read the accounting policy note. The annual report explains when the company treats revenue as earned. If the policy changes between years, find out why.
2. Compare revenue with collections. Revenue growing fast while cash from operations lags is a reason to dig deeper. Our piece on operating cash flow vs net profit walks through that gap.
3. Watch receivables and unbilled revenue. Revenue booked before invoicing shows up as unbilled or contract assets. A steady rise relative to sales deserves a question on the earnings call.
4. Watch advances and deferred revenue. Cash received before the work is done sits as a liability. A growing pile can be good news (customers paying upfront) and it also tells you revenue that’s already locked in for later quarters.
5. Look at the order book alongside revenue. For project businesses, the order book is the pipeline and revenue is the pace of execution. Both matter.

Revenue that runs well ahead of cash is also one of the signals forensic screens look for. If you want to test a company more formally, the Beneish M-Score includes a receivables-to-sales check that picks up exactly this pattern.

Common misreads to avoid

We see three mistakes again and again when people react to results.

Treating an order win as revenue. Say a company announces a ₹500 crore order in a stock exchange filing. That isn’t ₹500 crore of revenue this quarter. Under the five steps, it becomes revenue only as obligations are met.

Treating a cash advance as profit. Money in the bank before delivery is a liability until the company performs. It doesn’t belong in this quarter’s top line.

Comparing two companies without checking their policies. Two developers, or two engineering firms, can apply the same standard to different contract terms and land in very different places. The numbers aren’t wrong. They’re just not like-for-like.

The takeaway

Ind AS 115 gives every Indian listed company the same five-step test: identify the contract, find the promises, fix the price, split it across the promises, and book revenue when each promise is kept. It doesn’t make results foolproof. Judgement still creeps in at the allocation and variable-pricing steps, and at the call on whether something is delivered at a point in time or over time.

But once you know where those judgements sit, you read a results release differently. You stop asking only “how much did revenue grow?” and start asking “which promises were kept this quarter, and how much is still waiting on the balance sheet?” That second question tends to tell you more.

Disclaimer: This article is for educational purposes only and is not investment advice. The company and figures in the worked example are hypothetical. Please consult a SEBI-registered investment adviser before making investment decisions.