Revenue Recognition Principle: Methods & 5-Step Model

Imagine an Ahmedabad-based software firm signs a ₹12 lakh deal on 28 March. The client pays 50% immediately. The software arrives in May, with support lasting a full year thereafter. What revenue figure must appear in the books for the fiscal year closing 31 March? 

Several business owners reply, ₹6 lakh, since that was our income. Others claim ₹12 lakh, given our contract. Both responses typically prove incorrect. The accurate figure stems from the revenue recognition rule, and securing it correctly influences your earnings, your taxes, your investor statements, and your examination. The principle, in plain words, walks through the main revenue recognition methods and breaks down the 5-step model used under Ind AS 115 with simple rupee examples.

Key Takeaways

• Revenue is recorded when it is earned, not when cash is received.
• Ind AS 115 uses a 5-step model: contract, performance obligations, transaction price, allocation, and recognition.
• Bundled deals must be split into separate performance obligations.
• GST is not revenue.
• Advances are liabilities until goods or services are delivered.
• Always confirm which standard applies to your company with your chartered accountant.

What Is the Revenue Recognition Principle?

The revenue recognition rule states that firms must log income once earned, rather than upon receiving funds. Earned implies the firm has provided agreed-upon goods or services and holds a claim to payment.

This concept stems from accrual accounting software principles. Within accrual accounting, revenues and costs are logged during their relevant periods regardless of when cash flows occur.

Here is why it matters: Honest profit reporting. Recording a whole year of revenue when cash arrives distorts one period to appear strong while making the remaining ten seem poor.

• Matching: Income ought to align with expenses incurred to generate it.
• Confidence: Creditors, backers, and examiners depend upon steady income figures.
• Compliance: Firms within India must adhere to relevant Accounts Receivable standards, and errors may result in audit qualifications and notices.

Which Standards Apply in India?

Indian businesses follow different rules depending on their type and size. Always confirm with your chartered accountant, since applicability depends on your company's category.

Revenue Recognition Methods Explained

Before the 5-step model, it helps to know the common methods businesses use. Which one applies depends on the nature of your contract.

1. Point-in-Time Recognition

Revenue is recognized at a specific point in time when control of the good or service is transferred to the customer.

Example: Revenue from Surat textile trade is recognized when the fabric worth ₹4 lakh has been delivered to the buyer.

Best for: Retailers, manufacturing industries, and sale of goods.

2. Over-Time Recognition

Revenue is recognized over time as the performance obligation is met.

Example: An IT support contract for 12 months is valued at ₹1.2 lakh. The company will recognize revenue at the rate of ₹10,000 per month.

Best for: Subscription-based businesses, SaaS, support services, and similar long-dated contracts.

3. Percentage of Completion Method

Revenue is recognized based on the percentage of work completed.

Example: A Pune-based building contractor has a contract worth ₹50 crore. The estimated cost of the project is ₹40 crore. At the end of the year, the company has spent ₹20 crore on the project. The company will recognize revenue of ₹25 crore (50% of ₹50 crore) as 50% of the estimated cost has been incurred.

Best for: Building construction, civil engineering, and similar large-scale contracts.

4. Completed Contract Method

Revenue is recognized on a contract completion basis. Companies can recognize revenue only when the contract is completed. The completed contract method is generally disallowed under Ind AS 115 for revenue that should be recognized over time, but it may still be discussed in the context of older accounting standards or smaller enterprises.

5. Input and Output Methods

These are the two methods to measure progress towards satisfying a performance obligation.

• Input method: This is based on the level of effort or investment made in completing the task. It can be measured in terms of cost incurred, staff hours, and more.
• Output method: This is based on the achievement or outcome of the task. It could be measured in terms of goods produced, services delivered, or any other survey method.

The company should choose between input and output methods for measuring the progress and apply it consistently.

6. Installment Method

Revenue is recognized when the installment amount has been received. It is only applicable in rare circumstances where there is uncertainty regarding the collection of cash. This method is not suitable under modern accounting practices.

7. Cash Basis (Not an Accrual Method)

Revenue is recognized only on the receipt of cash. Small proprietorships might follow this method for recognizing revenue, but it is generally not suitable for bigger companies as it fails to adhere to the revenue recognition principle.

The 5-Step Model for Revenue Recognition

Ind AS 115, IFRS 15, and ASC 606 all follow the same five steps. Think of them as a checklist you run for every customer contract.

Step 1: Identify the Contract with the Customer

A contract is an agreement that creates enforceable rights and obligations. For it to count, these conditions should be met:

• The parties have approved the contract and are committed to it.
• Each party's rights, including payment terms, can be identified.
• The contract has commercial substance.
• Collection of payment is probable.

A contract does not need to be a long written document. Emails, purchase orders, and even customary business practice can create one, as long as it is enforceable under Indian contract law.

Step 2: Identify the Performance Obligations

A performance obligation is a distinct promise to transfer a good or service. If a contract has several distinct promises, each must be accounted for separately.

Example: A software firm sells one package that includes:

1. A software licence
2. Implementation and setup
3. 12 months of technical support

These are three performance obligations, not one, because the customer can benefit from each on its own or with readily available resources.

Step 3: Determine the Transaction Price

The transaction price is the amount the company expects to receive in exchange for its promises. Remember to account for:

• Variable consideration: discounts, rebates, penalties, bonuses, or performance incentives.
• Significant financing component: if payment is delayed for a long time, part of the price may be interest.
• Non-cash consideration: payment in shares or goods.
• Amounts collected for third parties: GST software is collected on behalf of the government and is not your revenue. Exclude it from the transaction price.

Step 4: Allocate the Transaction Price to the Performance Obligations

When there are multiple obligations, divide the total price in proportion to each item's standalone selling price (the price you would charge if sold separately).

Worked example (₹ figures):

The customer got a ₹1 lakh discount, so the contract price is ₹12 lakh instead of ₹13 lakh. The discount is spread across all three items in proportion.

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

Revenue is recognised when control transfers to the customer. This can happen at a point in time or over time.

Applying it to the same example:

• Licence (₹7,38,462): recognised at the point in time when the customer gets access to the software.
• Implementation (₹2,76,923): recognised over time, as the work is completed.
• Support (₹1,84,615): recognised evenly across 12 months, about ₹15,385 per month.

Now go back to the opening question. If the contract was signed on 28 March and nothing was delivered before 31 March, the company may recognise little or no revenue in that financial year. The money received upfront would sit as a contract liability (also called deferred or unearned revenue) on the balance sheet.

Common Revenue Recognition Mistakes Indian Businesses Make

1. Booking advance payments as revenue. Advances received are liabilities until you deliver.
2. Ignoring bundled promises. Treating a licence, setup, and support as one lump sum overstates early revenue.
3. Including GST in revenue. GST is a pass-through amount, not income.
4. Skipping variable consideration. Expected discounts, returns, and penalties reduce revenue and should be estimated.
5. Recognising revenue before delivery. Bill and hold or year-end push sales can attract serious audit attention.
6. Inconsistent methods. Switching the progress measurement method every year without a valid reason.
7. Weak documentation. Auditors want contracts, delivery proofs, and acceptance records.

Quick Checklist Before Recording Revenue

• Do we have a valid, enforceable contract?
• Have we listed every distinct promise?
• Is the price after discounts, returns, and GST clearly calculated?
• Have we allocated the price using standalone selling prices?
• Has control actually passed to the customer, either now or over time?
• Do we have proof (delivery challan, acceptance email, timesheets, milestone sign-off)?

Conclusion

Mastering the revenue recognition principles, specifically through the Ind AS 115 5-step model, is essential for presenting an accurate, transparent financial picture of your business. By recording income only when it is actually earned rather than when cash changes hands, companies ensure matching alignment between revenues and expenses while maintaining compliance with Indian accounting standards. Properly unbundling contract obligations, excluding pass-through taxes like GST, and treating advance payments as liabilities prevents revenue distortion and audit complications. Ultimately, adhering to these structured recognition methods builds long-term trust with investors, creditors, and tax authorities, ensuring your financial reporting remains robust, reliable, and standardized.