IFRS 15 Performance Obligations: Identifying and Allocating Transaction Price

IFRS 15 Performance Obligations: Identifying and Allocating Transaction Price

By Sai Manikanta Pedamallu (ACCA, CMA US, CSCA US, CGMA, ACMA, Dip IFRS, M.Com, MBA, MA)

Lead Instructor, Global Fin X | www.globalfinx.in/manikanta

---

IFRS 15 Revenue Recognition: The 5-Step Model Explained (Part 2)

In Part 1 I covered Steps 1 and 2: identifying the contract and identifying the performance obligations within it. That part answered two questions. What contract am I dealing with? What separate promises does it contain?

This part answers the next three. How much am I entitled to? How do I split that amount across the promises? When do I recognise the revenue for each one?

Steps 3, 4, and 5 are where the numbers happen. Step 1 and 2 are judgment about units of account. Steps 3 to 5 are judgment plus arithmetic. The arithmetic is where Dip IFRS candidates lose marks they should not lose, usually because they rush the variable consideration estimate or allocate a discount to the wrong obligation. I will work through each step with calculations, and I will keep the Indian context running throughout.

One thing worth saying up front. You cannot do Step 4 without Step 3, and you cannot do Step 3 properly without Step 2. The model is sequential for a reason. If you misidentify the performance obligations, the allocation in Step 4 lands on the wrong buckets, and the timing in Step 5 follows the wrong buckets. Errors compound forward.

---

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration an entity expects to be entitled to in exchange for transferring the promised goods or services. It is not the invoice value. It is not the contract headline price. It is the amount the entity expects to keep.

That distinction matters. A contract might state Rs. 10 crore, but if Rs. 1 crore of that is a refundable performance bonus the entity does not expect to earn, the transaction price is not Rs. 10 crore. Step 3 is the discipline of working out the real number.

Four elements adjust the headline price into the transaction price:

• Variable consideration, and the constraint on it
• The existence of a significant financing component
• Non-cash consideration
• Consideration payable to the customer

I will take each in turn.

Variable Consideration

Consideration is variable when the amount the entity will receive depends on future events. Discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, and penalties all create variability. So do contracts where the amount depends on usage or on hitting a target.

IFRS 15 requires the entity to estimate variable consideration using one of two methods, whichever better predicts the amount the entity will be entitled to:

• Expected value: the sum of probability-weighted amounts across a range of possible outcomes. This suits contracts with many possible outcomes, like a large portfolio of similar transactions.
• Most likely amount: the single most likely outcome. This suits contracts with a binary or near-binary result, like a bonus that is either earned in full or not at all.

The method is chosen per contract, based on which one better predicts. An entity does not get to pick freely. It picks the method that fits the structure of the uncertainty.

Worked example: Larsen & Toubro construction bonus (most likely amount)

L&T signs a contract to build a metro segment for Rs. 800 crore. The contract includes a completion bonus of Rs. 40 crore if the project finishes by a target date, and nothing if it misses. Based on its current schedule and past performance on similar projects, L&T believes it is more likely than not to hit the date.

This is a binary outcome: bonus earned in full, or not at all. The most likely amount method fits. The single most likely outcome is that L&T earns the bonus. So the variable consideration estimate is Rs. 40 crore, and the transaction price before constraint is Rs. 840 crore.

Worked example: pharma volume rebate (expected value)

A pharmaceutical distributor sells to a hospital chain with a tiered annual rebate. If annual purchases exceed Rs. 5 crore, a 4% rebate applies to the whole year. If they exceed Rs. 8 crore, the rebate rises to 6%. The distributor has hundreds of such arrangements and good historical data.

Here there is a range of outcomes across a large population. Expected value fits. Suppose the distributor estimates a 60% chance of the 4% tier, a 30% chance of the 6% tier, and a 10% chance of no rebate:

The expected rebate is 4.2% of sales. On Rs. 6 crore of sales, that is a Rs. 25.2 lakh reduction to the transaction price. Revenue is recognised net of that estimate, with a refund liability for the rebate expected to be paid.

The Constraint on Variable Consideration

This is the part candidates forget. Estimating variable consideration is only half of Step 3. The entity then applies a constraint.

Variable consideration is included in the transaction price only to the extent that it is highly probable that a significant reversal of cumulative revenue will not occur when the uncertainty is later resolved. "Highly probable" is a high bar, higher than "probable." The point is to stop entities recognising optimistic estimates that later collapse.

Factors that increase the risk of reversal, and therefore tighten the constraint: the amount is highly susceptible to factors outside the entity's control, the uncertainty will not resolve for a long time, the entity has limited experience with similar contracts, the entity has a practice of offering price concessions, and the range of possible outcomes is wide.

Worked example: applying the constraint

Return to the L&T bonus. Suppose instead the bonus depends partly on weather and partly on a government clearance that is outside L&T's control, and L&T has limited experience with this specific type of contract. Even if the most likely outcome is that the bonus is earned, the constraint may prevent recognising the full Rs. 40 crore. L&T might conclude only Rs. 20 crore meets the highly probable threshold. The transaction price becomes Rs. 820 crore, not Rs. 840 crore. The remaining Rs. 20 crore is recognised later, if and when the uncertainty resolves favourably.

The constraint is reassessed at each reporting date. As uncertainty resolves, more variable consideration may become recognisable.

Significant Financing Component

When the timing of payment gives the customer or the entity a significant benefit of financing the transfer of goods or services, the transaction price is adjusted for the time value of money. The entity recognises revenue at the cash selling price, and the financing element is recognised separately as interest income or interest expense.

This cuts both ways. If the customer pays well in advance, the entity is effectively borrowing, and there is interest expense. If the customer pays well in arrears, the entity is effectively lending, and there is interest income.

Worked example: advance payment with financing

A capital equipment manufacturer receives Rs. 1 crore upfront for a machine that will be delivered in two years. The cash selling price for immediate delivery would be lower, because the customer has prepaid. Suppose the appropriate discount rate is 8%. The entity has received Rs. 1 crore now but will deliver in two years.

The financing component means the entity recognises interest expense on the advance over the two years (it has the customer's cash). At delivery, revenue recognised is the advance plus the accreted financing: Rs. 1 crore compounded at 8% for two years, which is approximately Rs. 1.166 crore. The Rs. 16.6 lakh difference is financing expense recognised over the two years, and revenue at delivery reflects the higher amount.

The practical expedient. An entity need not adjust for a significant financing component if, at contract inception, the period between transfer and payment is one year or less. This expedient removes the time-value adjustment for most ordinary trade terms. A 30-day or 90-day credit period does not trigger financing component accounting.

Non-Cash Consideration

When a customer pays in something other than cash, such as shares, goods, or services, the non-cash consideration is measured at fair value. If fair value cannot be reasonably estimated, the entity measures it indirectly by reference to the standalone selling price of the goods or services promised.

This appears in barter arrangements and in some startup deals where a service provider takes equity in lieu of fees. An Indian agency taking shares in a client startup instead of a cash retainer measures the consideration at the fair value of those shares at contract inception.

Consideration Payable to the Customer

Sometimes the entity pays the customer, through slotting fees, cooperative advertising allowances, or rebates. Consideration payable to a customer is treated as a reduction of the transaction price, unless the payment is in exchange for a distinct good or service the customer transfers to the entity.

Worked example: slotting fee

An FMCG company like Britannia pays a Rs. 50 lakh listing fee to a retail chain to stock its biscuits on prime shelves. If the entity receives nothing distinct in return, that Rs. 50 lakh reduces revenue. If, instead, the retailer provides a distinct advertising service at fair value, the payment is an expense, not a revenue reduction, up to the fair value of that service. Any excess over fair value still reduces revenue.

This is a frequent real-world adjustment and a common exam trap. The default is a reduction of revenue. The exception requires a genuinely distinct good or service at fair value.

---

Step 4: Allocate the Transaction Price to the Performance Obligations

Once the transaction price is known and the performance obligations are identified, the price is allocated across those obligations. The objective is to allocate an amount that depicts the consideration the entity expects for each separate promise.

The allocation is based on relative standalone selling prices (SSP). The SSP is the price at which the entity would sell the good or service separately to a customer.

Determining Standalone Selling Price

The best evidence of SSP is an observable price when the entity sells the good or service separately in similar circumstances. When no observable price exists, the entity estimates it. IFRS 15 describes three estimation approaches:

• Adjusted market assessment: estimate the price the market would pay, considering competitors' prices adjusted for the entity's costs and margins.
• Expected cost plus a margin: forecast the costs of satisfying the obligation and add an appropriate margin.
• Residual approach: total transaction price less the observable SSPs of other goods or services. This is permitted only in limited cases, mainly where the selling price is highly variable or uncertain.

The residual approach is restricted on purpose. Entities cannot dump all uncertainty into one obligation to manipulate timing.

Worked example: Airtel handset and network bundle

Return to the telecom example from Part 1. Airtel sells a bundle for Rs. 24,000, paid as Rs. 1,000 per month over 24 months. The bundle has two performance obligations: the handset (point in time) and 24 months of network service (over time).

Standalone selling prices:

• Handset sold separately: Rs. 18,000
• Network service sold separately: Rs. 800 per month, so Rs. 19,200 over 24 months
• Sum of SSPs: Rs. 37,200

The transaction price of Rs. 24,000 is below the sum of standalone prices, so there is a Rs. 13,200 bundle discount. Allocate the Rs. 24,000 in proportion to SSP:

Airtel recognises Rs. 11,613 when the handset is delivered, even though the customer has paid almost nothing yet. The remaining Rs. 12,387 is recognised over 24 months, roughly Rs. 516 per month. This is the single biggest practical change IFRS 15 brought to Indian telecom accounting. Under the old approach, much of the value could sit with the service. Now a chunk is recognised upfront with the handset, creating a contract asset for the difference between revenue recognised and cash received early in the contract.

Allocating a Discount

When the sum of standalone prices exceeds the transaction price, the difference is a discount. The default is to allocate the discount proportionately to all performance obligations, which is what the Airtel example does.

There is an exception. A discount is allocated to one or more specific obligations, rather than all of them, when the entity has observable evidence that the entire discount relates only to those obligations. This happens when those items are regularly sold at a discount as a bundle while others are sold at full price.

Worked example: targeted discount

A software vendor sells three products. Products A and B are routinely sold together at a Rs. 2 lakh discount. Product C is always sold at full SSP. A bundle of all three is priced so the total discount equals Rs. 2 lakh. Because observable evidence shows the discount belongs to A and B, the entire Rs. 2 lakh is allocated to A and B only. Product C is allocated its full SSP. This prevents understating Product C's revenue.

Allocating Variable Consideration

Variable consideration may relate to the entire contract or to a specific performance obligation. When the variable amount relates entirely to one obligation, or to a distinct good in a series, it is allocated to that obligation alone, provided that allocation depicts the consideration the entity expects for that item.

A performance bonus for early completion of one phase of a multi-phase contract, where each phase is a separate obligation, is allocated to that phase, not spread across all phases.

---

Step 5: Recognise Revenue When (or As) Performance Obligations Are Satisfied

Revenue is recognised when the entity satisfies a performance obligation by transferring control of a good or service to the customer. The central concept is control, not risk and reward, and not delivery in the old physical sense.

Control means the ability to direct the use of, and obtain substantially all the remaining benefits from, the asset. A customer that controls an asset can deploy it, sell it, pledge it, or prevent others from using it.

The first decision in Step 5 is binary. Is the obligation satisfied over time, or at a point in time?

Over Time: The Three Criteria

A performance obligation is satisfied over time if any one of three criteria is met. Only one is needed.

Criterion 1: The customer simultaneously receives and consumes the benefits as the entity performs.

This fits routine recurring services. A cleaning contract, a managed IT support service, a payroll processing service. The customer consumes the benefit continuously, and another entity would not need to redo the work already done if it took over.

Criterion 2: The entity's performance creates or enhances an asset the customer controls as it is created or enhanced.

This fits work performed on an asset the customer already owns or controls. Building an extension on the customer's land, where the customer controls the work in progress, is the classic case.

Criterion 3: The entity's performance does not create an asset with an alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date.

This is the one Indian real estate developers and bespoke manufacturers must understand. Two parts, both required. The asset has no alternative use (it is so customised the entity cannot redirect it to another customer), and the entity can demand payment for work done so far, including a reasonable margin, if the contract is cancelled.

If none of the three criteria is met, the obligation is satisfied at a point in time.

The Indian real estate question. This is a live and consequential debate. For a residential apartment sold off-plan, does the developer recognise revenue over the construction period or at handover? The answer turns on Criterion 3. Is the unit so customised it has no alternative use, and does the developer have an enforceable right to payment for work to date including margin? In most Indian residential pre-sale contracts, units are standardised within a building and the developer can resell on default, and the enforceable-right-to-payment condition is often not met. So control transfers at handover, and revenue is recognised at a point in time. This was a real change from the percentage-of-completion approach widely used under old Indian GAAP, and it moved a lot of revenue later in time for several listed developers.

Point in Time: The Indicators

When an obligation is not satisfied over time, it is satisfied at a point in time, being the moment control transfers. IFRS 15 lists indicators of that transfer:

• The entity has a present right to payment
• The customer has legal title
• The customer has physical possession
• The customer has the significant risks and rewards of ownership
• The customer has accepted the asset

No single indicator is decisive. The entity weighs them together to judge when control passes. Physical possession usually matters, but not always. In a bill-and-hold arrangement, control can pass before physical delivery if specific conditions are met.

Measuring Progress for Over-Time Recognition

When an obligation is satisfied over time, the entity measures progress toward complete satisfaction. Two families of methods exist:

• Output methods: revenue recognised based on the value transferred to date, such as surveys of work performed, units delivered, or milestones reached.
• Input methods: revenue recognised based on the entity's inputs, such as costs incurred, labour hours, or machine hours, relative to total expected inputs.

The cost-to-cost method, an input method, is the most common in construction and long-term contracts. It is also the most examined.

Worked example: cost-to-cost progress

A construction company has a contract with a transaction price of Rs. 50 crore and total expected costs of Rs. 40 crore. By year-end, it has incurred Rs. 16 crore of costs.

Progress = Rs. 16 crore / Rs. 40 crore = 40%.

Revenue recognised to date = 40% x Rs. 50 crore = Rs. 20 crore.

Costs recognised = Rs. 16 crore. Profit to date = Rs. 4 crore.

A caution on input methods. If a cost is incurred that does not reflect progress, such as a large amount of uninstalled materials delivered to site but not yet used, that cost should be excluded from the measure, or revenue recognised only to the extent of the cost (zero margin on those materials) until they are installed. Otherwise the cost-to-cost ratio overstates progress. This adjustment is a common exam point and a common audit finding.

When progress cannot be measured. If an entity cannot reasonably measure progress but expects to recover its costs, revenue is recognised only to the extent of costs incurred, until progress can be measured reliably. Zero profit, full cost recovery, until clarity arrives.

---

How Steps 3, 4, and 5 Fit Together: A Full Worked Contract

Let me run one contract end to end to show the steps connecting.

An IT company signs a contract with a bank for Rs. 90 lakh. It contains two performance obligations identified in Step 2: a software licence delivered upfront, and 12 months of post-go-live support. The contract includes a Rs. 10 lakh bonus if the system passes an uptime test after six months, which the company assesses as highly probable and not subject to significant reversal.

Step 3. Transaction price = Rs. 90 lakh fixed plus Rs. 10 lakh variable that survives the constraint = Rs. 100 lakh.

Step 4. Standalone selling prices: licence Rs. 75 lakh, support Rs. 25 lakh, sum Rs. 100 lakh. No discount. Allocation: licence Rs. 75 lakh, support Rs. 25 lakh.

Step 5. The licence is delivered upfront and the bank controls it at delivery: point in time, Rs. 75 lakh recognised on delivery. Support is consumed continuously: over time, Rs. 25 lakh recognised across 12 months, roughly Rs. 2.08 lakh per month.

Notice the bonus. Because it relates to overall system performance, not solely to support, it is allocated across both obligations in proportion to SSP, which is why each SSP above already reflects the Rs. 100 lakh total. If the bonus had related only to the support obligation, it would have been allocated to support alone.

That is the whole model in one contract. Identify, identify, price, allocate, recognise.

---

Ind AS 115 vs IFRS 15: Differences That Touch Steps 3 to 5

Ind AS 115 is substantially converged with IFRS 15. The five-step mechanics for transaction price, allocation, and recognition are identical. The differences that matter for these three steps are narrow and presentational.

The indirect tax point is the one to remember for Indian reporting. GST collected from customers is collected on behalf of the government. It is not part of the transaction price and not revenue. This sounds obvious, but the exam and real filings still see errors where gross billed amounts including GST are recognised as revenue.

---

Disclosures Relevant to Steps 3 to 5

The disclosure objective remains the same as in Part 1: users should understand the nature, amount, timing, and uncertainty of revenue. The disclosures most connected to Steps 3 to 5 are:

• The methods, inputs, and assumptions used to determine the transaction price, including estimating variable consideration and assessing the constraint
• The methods used to allocate the transaction price, including estimating standalone selling prices
• The methods used to recognise revenue for over-time obligations, and why those methods faithfully depict transfer
• The transaction price allocated to remaining performance obligations (the order book or backlog), and when it is expected to be recognised

That last one, remaining performance obligations, is heavily scrutinised for Indian IT companies because it signals future revenue visibility. Analysts read it as the contracted backlog.

---

Dip IFRS Exam: What You Need for Steps 3 to 5

These three steps generate the calculation marks in IFRS 15 questions. Step 2 generates the judgment marks. A complete answer needs both.

Most Tested Areas

Variable consideration plus constraint. The examiner gives a bonus, rebate, or penalty and expects you to estimate it using the correct method and then apply the constraint. Estimating without constraining is a frequent half-answer that loses marks.

Allocation of a bundle discount. A contract with multiple obligations priced below the sum of SSPs. You allocate the discount, usually proportionately, occasionally to specific obligations where evidence supports it.

Cost-to-cost progress. A construction or long-term service contract where you compute percentage complete and the revenue and profit to date. Watch for uninstalled materials and cost overruns that change total expected costs.

Over time vs point in time. Applying the three over-time criteria, especially Criterion 3, to decide the timing. Real estate and bespoke manufacturing scenarios are common.

Significant financing component. Advance or deferred payment with a discount rate, requiring you to separate revenue from interest.

Common Examiner Traps

Forgetting the constraint. Students estimate variable consideration correctly, then include all of it without testing whether a significant reversal is highly probable not to occur.

Allocating discount to the wrong obligations. Defaulting to specific allocation without the observable evidence the standard requires, or vice versa.

Including GST in revenue. In Indian-flavoured questions, recognising gross amounts including indirect tax.

Uninstalled materials in cost-to-cost. Counting materials delivered but not installed as progress, overstating percentage complete.

Changing total expected costs mid-contract. When the question revises total expected costs, the cumulative catch-up must be recomputed on the new total, not the old one.

Exam Technique

Show the calculation on the page. State the method you chose for variable consideration and why. Lay out the SSP allocation as a small table even if the question does not ask for one, because it earns method marks and reduces arithmetic slips. For over-time questions, name the criterion you are relying on before you conclude. As I said in Part 1, a defensible conclusion reached by visible reasoning beats a bare answer.

---

FAQ

What is the difference between the transaction price and the contract price?

The contract price is the stated headline amount. The transaction price is what the entity expects to be entitled to keep, after adjusting for variable consideration and its constraint, any significant financing component, non-cash consideration, and amounts payable to the customer. They are often different.

How is variable consideration measured?

Using either expected value (probability-weighted, suited to many possible outcomes) or most likely amount (the single most likely result, suited to binary outcomes). The entity picks whichever better predicts the amount it will be entitled to, then applies the constraint.

What does the constraint on variable consideration mean?

Variable consideration is included only to the extent it is highly probable that a significant revenue reversal will not occur when the uncertainty resolves. It stops entities recognising optimistic estimates that later have to be reversed.

When must I adjust the transaction price for a financing component?

When the timing of payment gives a significant financing benefit to either party. You need not adjust if the gap between transfer and payment is one year or less, which is the practical expedient covering most ordinary trade credit terms.

How do I allocate the transaction price across performance obligations?

In proportion to the standalone selling price of each obligation. Where an observable separate selling price does not exist, estimate it using adjusted market assessment, expected cost plus margin, or, in limited cases, the residual approach.

How do I decide if revenue is recognised over time or at a point in time?

Test the three over-time criteria. If any one is met, recognise over time and measure progress with an output or input method. If none is met, recognise at the point control transfers, weighing the transfer indicators such as right to payment, legal title, physical possession, risks and rewards, and acceptance.

Which progress method should I use for over-time obligations?

Choose the method that best depicts the transfer of control. Output methods measure value delivered to date; input methods measure resources consumed, with cost-to-cost the most common. Exclude inputs that do not represent progress, such as uninstalled materials.

How is GST treated in the transaction price under Ind AS 115?

GST collected from customers is collected on behalf of the government and is not revenue. It is excluded from the transaction price. Only the entity's own consideration is revenue.

What happens if I cannot measure progress on an over-time obligation?

If you expect to recover your costs but cannot yet measure progress reliably, recognise revenue only to the extent of costs incurred, at zero profit, until you can measure progress.

---

Enroll with Global Fin X

Steps 3, 4, and 5 are where IFRS 15 turns from principle into numbers, and where Dip IFRS candidates earn or lose the calculation marks. Our programme works through every part of the five-step model with in-depth lectures, fully worked numerical examples, exam-style MCQs, and an LMS built for working professionals who study around a job.

Enroll Now: Dip IFRS Programme

Faculty profile: www.globalfinx.in/manikanta

---

This is Post 12 of the Global Fin X IFRS Series. Previous: IFRS 15 The 5-Step Revenue Model: Logic, Not Just Rules. Next: IFRS 15 Part 3: Contract Costs, Variable Consideration in Depth, and Special Topics.