Key Points
- The entity must estimate variable consideration at contract inception and update the estimate at each reporting date.
- IFRS 15 permits two estimation methods: expected value (probability-weighted) and most likely amount (single outcome).
- The constraint limits recognised revenue to amounts where a significant reversal is not highly probable.
- Failing to identify variable consideration at contract inception is the single fastest route to a revenue misstatement.
What is Variable Consideration?
IFRS 15.50 requires the entity to estimate the amount of variable consideration using whichever method better predicts the outcome: the expected value (a probability-weighted sum of possible outcomes) or the most likely amount (a single best estimate from a range of possible outcomes). The expected value method works well when a contract has a large number of possible outcomes with similar probabilities. The most likely amount is more appropriate when the outcome is binary (the entity earns a bonus or it does not).
Once estimated, the variable amount is subject to the constraint on variable consideration. IFRS 15.56 restricts the cumulative revenue recognised to the amount for which it is highly probable that a significant reversal will not occur when the uncertainty resolves. The auditor's focus sits squarely on that probability assessment. ISA 540.13(a) requires the auditor to evaluate whether the entity's method for estimating variable consideration is appropriate under the applicable framework, which means testing the inputs to the probability weighting or the rationale for selecting a single most likely amount.
The estimate is not a one-time exercise. IFRS 15.59 requires the entity to update variable consideration estimates at each reporting date, with any changes allocated to performance obligations on the same basis as at inception.
Worked example: Fernandez Distribucion S.L.
Client: Spanish wholesale distributor, FY2025, revenue EUR 34M, IFRS reporter. Fernandez enters a 12-month supply contract with a supermarket chain for branded cleaning products. The contract specifies a base price of EUR 2.8M, a volume rebate of 4% if cumulative deliveries exceed 10,000 pallets, and a penalty of EUR 120,000 if on-time delivery falls below 95%.
Step 1 — Identify the variable elements
The base price of EUR 2.8M is fixed. Two variable components exist: the volume rebate (up to EUR 112,000 reduction) and the late-delivery penalty (up to EUR 120,000 reduction). The transaction price therefore ranges from EUR 2,568,000 to EUR 2,800,000.
Step 2 — Select the estimation method
For the volume rebate, the controller uses the most likely amount method. Historical data from three prior contracts with this customer shows Fernandez has exceeded 10,000 pallets in every year. The most likely outcome is that the rebate will be triggered in full (EUR 112,000). For the delivery penalty, the controller again applies the most likely amount: Fernandez's on-time rate has averaged 97.8% over the past four years, so the most likely outcome is no penalty.
Step 3 — Apply the constraint
The controller includes the full base price of EUR 2.8M, deducts the EUR 112,000 rebate (highly probable based on historical pattern), and includes zero penalty. IFRS 15.56 requires that revenue be constrained to the amount where a significant reversal is highly probable not to occur. Since Fernandez has triggered the rebate in all comparable periods, recognising revenue net of the rebate satisfies the constraint. The initial transaction price is set at EUR 2,688,000.
Step 4 — Update at reporting date
At 30 June 2025 (interim), Fernandez has delivered 5,800 pallets with an on-time rate of 96.1%. The volume rebate remains highly probable. The penalty remains unlikely but the margin has narrowed. The controller reassesses under IFRS 15.59 and concludes no change to the transaction price is required.
Conclusion: the transaction price of EUR 2,688,000 reflects two variable consideration elements estimated using the most likely amount method, constrained per IFRS 15.56, and is defensible because each estimate traces to historical delivery data from comparable contracts.
Why it matters in practice
Teams frequently identify the obvious variable elements (rebates and bonuses stated in the contract) but miss implicit price concessions. IFRS 15.52 requires the entity to consider customary business practices that create a valid expectation of a price reduction, even when the contract does not contain an explicit clause. If an entity routinely grants retrospective discounts to retain customers, that pattern is variable consideration regardless of whether the current contract mentions it.
The constraint assessment under IFRS 15.56-58 is often reduced to a single line in the working paper stating "significant reversal is not highly probable." ISA 540.18 requires the auditor to evaluate whether assumptions are reasonable. A bare conclusion without the supporting data (historical trigger rates, customer concentration, contract-specific factors listed in IFRS 15.57) does not meet the documentation standard.
Variable consideration vs. contract modification
Variable consideration and a contract modification can both change the amount of revenue recognised, but they operate through different mechanisms. Variable consideration exists within the original contract terms; the uncertainty is contemplated from inception. A contract modification is a separate event where the parties approve a change in scope, price, or both after the contract is already in force.
The distinction matters during testing. When the auditor encounters a price change mid-contract, the first question is whether the original contract contemplated that change (making it variable consideration under IFRS 15.50-58) or whether the parties negotiated a new term after inception (making it a modification under IFRS 15.18-21). Misclassifying a modification as variable consideration skips the IFRS 15.20-21 analysis of whether the modification creates a separate performance obligation, which can shift revenue between periods.
Related terms
Frequently asked questions
How do I choose between expected value and most likely amount?
IFRS 15.53 directs the entity to use whichever method better predicts the amount of consideration it will receive. Expected value works when several outcomes with similar probabilities exist (for instance, a portfolio of contracts with varying rebate tiers). Most likely amount fits binary outcomes where the entity either earns a bonus or does not. The entity must apply the chosen method consistently for similar contracts throughout the reporting period.
Does variable consideration apply to fixed-price construction contracts?
Yes. A fixed-price contract can still contain variable consideration if it includes performance bonuses, liquidated damages, or claims under IFRS 15.51. The entity must estimate the variable amount at inception and apply the constraint. IFRS 15.57(a)-(f) lists the factors the entity evaluates when determining whether including the estimate would cause a significant revenue reversal.
When do I reassess variable consideration during the contract?
IFRS 15.59 requires the entity to update the estimated transaction price at each reporting date. If the estimate changes, the entity allocates the change to the performance obligations in the contract on the same basis used at inception. For completed performance obligations, the change is recognised as revenue (or a revenue reduction) in the period of the change.