Have You Ever Faced These Challenges?
- Your entity bundles products and services at a single price, but the standalone selling prices of the individual components are not directly observable — and you are uncertain which estimation method to use
- You allocated a discount evenly across all performance obligations, only to be challenged by your auditors on whether the discount should have been attributed to a specific subset of the bundle
- Your revenue recognition pattern changed materially when you revised your standalone selling price estimates — and you struggled to explain the adjustment to management and the audit committee
What You Will Learn From This Article
- The three methods for estimating standalone selling prices when observable prices are not available — and the conditions that govern their use
- How to allocate discounts and variable consideration to specific performance obligations rather than across the entire contract
- Why standalone selling price policy documentation is essential for audit defence and internal control
Who This Article Is For
- Finance professionals at entities that sell bundled products and services
- Those responsible for establishing or reviewing standalone selling price policies
- Practitioners in SaaS, telecommunications, software, and manufacturing industries where bundled pricing is standard
The Purpose of Step 4: Connecting the Transaction Price to Each Performance Obligation
Steps 2 and 3 operate independently of each other. Step 2 identifies what the entity has promised to deliver. Step 3 determines how much total consideration the entity is entitled to receive. Step 4 connects these two outputs by allocating the transaction price to each performance obligation identified in Step 2.
The allocation determines how much revenue is associated with each performance obligation — and therefore how much revenue is recognised when each obligation is satisfied in Step 5. A contract with two performance obligations and a transaction price of ¥100 million does not automatically result in ¥50 million allocated to each. The allocation is driven by economics, not arithmetic.
The Allocation Principle: Relative Standalone Selling Prices
The transaction price is allocated to each performance obligation in proportion to its standalone selling price (SSP) relative to the sum of the SSPs of all performance obligations in the contract (IFRS 15.74).
The standalone selling price is the price at which the entity would sell the promised good or service separately to a customer. It represents the observable or estimated market value of that specific performance obligation on a standalone basis.
When SSPs Are Directly Observable
The most reliable evidence of SSP is the price at which the entity actually sells the good or service on a standalone basis to similar customers in similar circumstances. Where such transactions exist and are representative, the observed price is used directly.
Worked example — directly observable SSPs:
An entity sells a hardware unit (SSP: ¥60 million) and a three-year service contract (SSP: ¥40 million) as a bundle for ¥90 million.
| Performance obligation | SSP | Allocation ratio | Allocated amount |
|---|---|---|---|
| Hardware unit | ¥60m | 60% | ¥54m |
| Three-year service | ¥40m | 40% | ¥36m |
| Total | ¥100m | 100% | ¥90m |
The ¥10 million discount (¥100m SSP total vs ¥90m transaction price) is allocated proportionally across both obligations — ¥6 million from the hardware and ¥4 million from the service contract. Revenue of ¥54 million is recognised when the hardware is delivered; ¥36 million is recognised over the three-year service period.
Estimating SSPs When Observable Prices Are Not Available
In many commercial arrangements, the entity does not sell all components of a bundle on a standalone basis. In these cases, SSP must be estimated. IFRS 15.78 describes three estimation methods.
Method 1: Adjusted Market Assessment Approach
The entity analyses the market in which it sells the relevant goods or services and estimates the price that customers in that market would be willing to pay. This may involve reference to competitors’ prices for similar goods or services, adjusted for differences in the entity’s cost structure, market positioning, or customer base.
When to use it: This method is most appropriate where external market data is available and where the entity’s offering is broadly comparable to alternatives available in the market.
Practical challenge: The definition of “comparable” requires judgement. Selecting market comparables that support a preferred SSP, rather than those that genuinely reflect market conditions, is an area of audit focus. The entity should document the basis for selecting comparables and the adjustments made.
Method 2: Expected Cost Plus a Margin Approach
The entity forecasts the costs expected to be incurred in satisfying the performance obligation and adds an appropriate profit margin. The margin should reflect the entity’s typical margin on similar types of goods or services, or an industry benchmark where internal data is limited.
When to use it: This method is most appropriate where costs are well understood but market pricing data is not readily available — for example, proprietary after-sales services or highly specialised support contracts.
Worked example:
An entity provides a bespoke technical support service that it does not sell separately. The expected cost of providing the service over a three-year period is ¥18 million. The entity’s typical margin on service contracts is 25%.
SSP = ¥18 million ÷ (1 − 25%) = ¥24 million
Practical challenge: The choice of margin rate requires justification. Using a margin rate that is inconsistent with the entity’s actual profitability on similar services — or with observable industry benchmarks — will attract audit challenge. The documentation should clearly explain how the margin rate was determined.
Method 3: Residual Approach
Under the residual approach, the SSP of a performance obligation is estimated as the transaction price less the sum of the observable SSPs of all other performance obligations in the contract.
This method is only permitted in limited circumstances (IFRS 15.79). Specifically, the residual approach may be used only where:
- The entity sells the same good or service to different customers for a broad range of prices — meaning that a representative SSP cannot be determined from observed transactions, or
- The price of the good or service has not yet been established — for example, a new product or service for which pricing has not yet been set
Why the residual approach is restricted: In the wrong hands, the residual approach can be used to manipulate the allocation by inflating the SSPs of other components, thereby driving the residual SSP of the target component to whatever value is desired. IFRS 15’s restriction to genuinely uncertain or highly variable pricing situations prevents this.
When the residual approach is unavailable: Where neither of the two conditions is met, the entity cannot use the residual approach and must use Method 1 or Method 2. If both are impractical, the entity should combine multiple estimation approaches and document the basis for the resulting estimate in detail.
Allocating Discounts
Where the sum of the standalone selling prices of all performance obligations exceeds the transaction price, the difference is a discount. The default treatment is to allocate the discount proportionally across all performance obligations (IFRS 15.81).
However, IFRS 15.82 permits the discount to be allocated entirely to one or more — but not all — performance obligations if all three of the following conditions are met:
- The entity regularly sells each of the performance obligations in the contract on a standalone basis
- The entity also regularly sells a subset of those performance obligations together as a bundle, at a discount
- The discount associated with the bundle of performance obligations is substantially the same as the discount in the contract, and analysis of the goods or services in each bundle provides observable evidence of which performance obligation the discount belongs to
Worked example — discount allocation to a specific subset:
An entity regularly sells three products on a standalone basis:
| Product | SSP |
|---|---|
| Product A | ¥50m |
| Product B | ¥30m |
| Product C | ¥20m |
| Total | ¥100m |
The entity also regularly sells Products A and B together for ¥70m (a ¥10m discount relative to their combined SSP of ¥80m). Product C is always sold at its full SSP of ¥20m.
A contract is entered into for all three products at a total price of ¥90m (a ¥10m discount vs total SSP of ¥100m).
Because the entity can demonstrate that the ¥10m discount relates specifically to the A+B bundle — consistent with its regular pricing of that combination — the entire ¥10m discount is allocated to Products A and B. Product C retains its full SSP of ¥20m in the allocation.
| Performance obligation | Allocated amount |
|---|---|
| Product A | ¥43.75m (¥50m × 70/80) |
| Product B | ¥26.25m (¥30m × 70/80) |
| Product C | ¥20m (full SSP, no discount) |
| Total | ¥90m |
Allocating Variable Consideration
Variable consideration is generally allocated across all performance obligations in proportion to their relative SSPs — the same principle as the base allocation. However, IFRS 15.84 permits variable consideration to be allocated entirely to a specific performance obligation (or to a specific distinct good or service within a series) if both of the following conditions are met:
- The terms of the variable payment specifically relate to the entity’s efforts to satisfy that performance obligation, or to a specific outcome from satisfying it
- Allocating the variable consideration entirely to that performance obligation is consistent with the overall allocation objective — that is, it approximates the amount of consideration to which the entity would be entitled if that obligation were sold separately
Practical examples where specific allocation is appropriate:
- A performance bonus payable only if a specific project milestone is achieved — where the bonus relates exclusively to the entity’s performance on that milestone
- A usage-based royalty on a specific software licence — where the royalty is directly tied to the customer’s use of the licence component and not to any other element of the contract
Changes in Standalone Selling Prices After Contract Inception
Standalone selling prices are determined at contract inception and are not updated for subsequent changes in market conditions or pricing strategies (IFRS 15.74). Where the entity revises its general pricing — for example, by changing list prices — this does not trigger a reallocation of the transaction price for existing contracts.
However, where the transaction price itself changes (for example, due to a change in the estimated amount of variable consideration), the updated transaction price is allocated using the original SSPs determined at contract inception. The change in the allocated amounts is recognised as a cumulative catch-up adjustment in the period of the change.
The Importance of SSP Policy Documentation
Step 4 is an area where robust policy documentation is not optional — it is essential for both audit defence and internal control purposes.
At a minimum, the entity’s SSP policy documentation should address:
- The SSP for each distinct performance obligation — whether observed directly or estimated, and the basis for the determination
- The estimation method applied where SSPs are not directly observable — and the rationale for selecting that method over the alternatives
- The basis for the profit margin used in cost-plus estimates — with reference to historical margin data or industry benchmarks
- The frequency of SSP review — including the trigger events that prompt a reassessment (new products, significant pricing changes, changes in competitive conditions)
- The treatment of bundled pricing — how discounts are identified and whether the conditions for allocating discounts to specific performance obligations are met
For entities in the SaaS and telecommunications industries, where pricing models evolve rapidly and contract structures are highly varied, SSP documentation must be maintained at a level of granularity that allows the allocation to be consistently applied and defended across a large volume of contracts.
Comparison with Japanese GAAP
| Area | IFRS 15 | Japanese GAAP (ASBJ No. 29) |
|---|---|---|
| Allocation principle | Relative SSP | Same |
| SSP estimation methods | Three methods described | Same |
| Residual approach | Restricted to specific conditions | Same |
| Discount allocation | Proportional unless specific conditions met | Same |
| Variable consideration allocation | Specific allocation permitted under conditions | Same |
The frameworks are substantially aligned. The principal practical difference is the availability under Japanese GAAP of certain simplifications that are not available under IFRS 15, particularly in relation to shipping and handling costs.
Summary
The key takeaways from Step 4 are as follows:
- The transaction price is allocated to performance obligations in proportion to their relative standalone selling prices
- Where SSPs are not directly observable, three estimation methods are available: adjusted market assessment, expected cost plus margin, and residual approach — the last of which is restricted to genuinely uncertain or highly variable pricing situations
- Discounts are allocated proportionally by default; specific allocation to a subset of performance obligations requires evidence that the discount is attributable to that subset
- Variable consideration may be allocated to a specific performance obligation where the variable payment terms specifically relate to that obligation and specific allocation is consistent with the overall allocation objective
- SSP documentation is essential — it supports consistent application, audit defence, and internal control over financial reporting
The next article examines Step 5: recognising revenue when or as each performance obligation is satisfied — with a focus on the over-time versus point-in-time distinction and progress measurement methods.
Comments