What is Constraint on Variable Consideration?
IFRS 15.56 requires an entity to include variable consideration in the transaction price only to the extent that it is highly probable a significant revenue reversal will not occur. The standard does not define "highly probable" with a numerical threshold, but IFRS 15.BC209 confirms the term aligns with the existing IFRS usage (interpreted in most European jurisdictions as approximately 75–80% confidence or higher).
Two factors drive the assessment. IFRS 15.57 lists indicators of when a reversal is more likely: the amount is highly susceptible to external factors (market volatility, third-party actions, weather), the uncertainty will not be resolved for a long period, the entity has limited relevant experience with similar contracts, and the contract has a broad range of possible outcomes. The auditor's job under ISA 540.13(a) is to evaluate whether management's constraint assessment uses the right method and reflects conditions at the reporting date rather than optimistic assumptions from the bid stage.
In practice, the constraint bites hardest on long-term contracts with milestone-based variable payments. An entity might estimate €2M in performance bonuses across a three-year service contract, but if the first milestone has not yet been verified by the customer, including the full €2M in the transaction price would fail the constraint test. The entity includes only the portion for which reversal risk is acceptably low.
Key Points
- The constraint prevents entities from recognising revenue that is likely to reverse once performance bonuses, penalties, or rebates are finalised.
- Entities must reassess the constraint at every reporting date, not only at contract inception.
- Common application areas include volume rebates, performance bonuses, liquidated damages, and price concessions tied to future events.
- The FRC has flagged insufficient disclosure of constraint judgments as a recurring inspection finding in construction and technology sectors.
Worked example: Fernández Distribución S.L.
Client: Spanish wholesale distribution company, FY2025, revenue €34M, IFRS reporter. Fernández signs a two-year supply contract with a European supermarket chain for packaged goods. The base price is €8M per year, with two variable elements: a volume rebate of up to €600,000 if the customer exceeds 120% of its annual volume target, and a quality penalty of up to €200,000 if product defect rates exceed 1.5%.
Step 1 — Estimate the variable consideration
Fernández reviews internal data from four prior contracts with similar customers. Volume exceeded 120% in one of the four years (25% historical frequency). The defect rate exceeded 1.5% in none of the four years.
Documentation note: "Variable consideration estimated per IFRS 15.53. Volume rebate: most likely amount is €0 (threshold not met in 75% of comparable periods). Quality penalty: most likely amount is €0 (threshold never breached). Expected value cross-check performed: volume rebate expected value = 0.25 x €600,000 = €150,000.
Step 2 — Apply the constraint to the volume rebate
Although the expected value of the volume rebate is €150,000, Fernández must assess whether including any amount would create a significant reversal risk. The volume target depends on the customer's purchasing decisions (an external factor per IFRS 15.57(a)), the outcome range is binary (€0 or €600,000 with no intermediate tiers), and historical experience is limited to four data points. Management concludes that including €150,000 in the transaction price would fail the constraint. The constrained amount is €0.
Documentation note: "Constraint applied per IFRS 15.56. Volume rebate excluded from transaction price. Factors considered: binary outcome, dependence on customer purchasing behaviour, limited historical sample. Reversal risk assessed as not meeting 'highly probable' threshold.
Step 3 — Apply the constraint to the quality penalty
The defect rate has never exceeded 1.5% across four years of production data. Management concludes it is highly probable that no penalty will be incurred. The constrained transaction price excludes the penalty (i.e., no reduction for €200,000). The annual transaction price remains €8M.
Documentation note: "Quality penalty: constraint assessment indicates highly probable that no penalty will apply. Basis: zero breach in four years of production data, stable production processes, no changes in raw material sourcing.
Step 4 — Reassess at year-end
At 31 December 2025, the customer's actual volume is tracking at 115% of target with one month of purchasing remaining. Management reassesses the volume rebate constraint. Given the proximity to the 120% threshold, the probability of triggering the rebate has increased. However, the outcome remains binary and one month of uncertainty remains. Management maintains the €0 constrained estimate. If January 2026 data (pre-financial-statement authorisation) shows the threshold was met, this becomes an adjusting event and the constraint assessment must be updated.
Documentation note: "Reassessment at reporting date per IFRS 15.59. Volume at 115% of target. Rebate trigger not yet met. Constraint conclusion unchanged. Post-year-end monitoring flagged for events-after-reporting-period review.
Conclusion: the constrained transaction price of €8M per year is defensible because each variable element was assessed against specific IFRS 15.57 indicators with documented historical data, and the reassessment at the reporting date confirms the original conclusion holds.
Why it matters in practice
Teams frequently apply the constraint at contract inception and never revisit it. IFRS 15.59 requires the entity to update the estimated transaction price (including the constraint assessment) at each reporting date. The auditor should verify that the year-end constraint reflects conditions at the balance sheet date, not assumptions locked in when the contract was signed.
Entities with portfolio-based variable consideration (volume rebates across hundreds of customer contracts) sometimes apply the constraint at the portfolio level without assessing whether individual contracts contain different risk profiles. IFRS 15.56 operates at the contract level. ISA 540.13(b) requires the auditor to evaluate whether the data used in the estimate is relevant to the individual measurement unit, not just to the portfolio average.
Variable consideration vs. constraint on variable consideration
| Dimension | Variable consideration | Constraint on variable consideration |
|---|---|---|
| What it determines | The estimated amount of consideration that varies (discounts, bonuses, penalties, refunds) | The portion of that estimate permitted in the transaction price |
| Standard reference | IFRS 15.50–55 | IFRS 15.56–58 |
| Estimation method | Expected value or most likely amount | Reversal-risk assessment against IFRS 15.57 indicators |
| Timing of assessment | At contract inception and each reporting date | Same; always applied after the estimation step |
| Audit focus | Whether the estimation method is appropriate and inputs are complete | Whether the entity's judgment on reversal probability is supportable and current |
The distinction matters because an entity can correctly estimate variable consideration at €500,000 using the expected value method, yet the constraint may reduce the amount included in the transaction price to €200,000 (or €0). Auditing the estimate without auditing the constraint misses half the judgment.
Related terms
Frequently asked questions
How do I document the constraint on variable consideration?
Record each variable element separately in the revenue working paper. For each element, state the estimation method (expected value or most likely amount per IFRS 15.53), the constraint assessment against the IFRS 15.57 indicators, and the resulting amount included in the transaction price. IFRS 15.126(a) requires disclosure of the methods and inputs used to estimate variable consideration, and the constraint judgment is a required part of that disclosure.
Does the constraint apply to contract modifications?
Yes. When a contract modification introduces new variable terms or changes existing ones, the entity must apply the constraint to the modified transaction price. IFRS 15.18–21 governs whether the modification is treated as a separate contract or as an adjustment to the existing contract. In either case, the constraint in IFRS 15.56 applies to any variable consideration in the revised arrangement.
What happens if the constraint estimate turns out to be wrong?
A change in the constrained amount is a change in the transaction price, not a correction of an error. IFRS 15.87 requires the entity to allocate the revised transaction price to the performance obligations in the contract and recognise the adjustment as revenue (or a reduction of revenue) in the period of the change. The auditor checks whether the original constraint was reasonable given information available at the time, not whether it predicted the outcome correctly.