In plain words
SaaS contracts may include rebates, usage credits or penalties that change the final price. Under IFRS 15 these are variable consideration. The company estimates them from the start, using expected value or most likely amount, and includes only the amount highly probable not to reverse later. Revenue is recorded net of the estimate, not gross with discounts booked as expenses, and the estimate is updated each reporting date.
Why it matters
Because discounts, rebates and usage-based credits are variable consideration, failing to estimate and constrain them from day one lets revenue run ahead of what the entity will actually be entitled to keep, so a later true-down reads as a revenue miss or one-off adjustment rather than a correction of an estimate that should have been made earlier, this directly affects reported growth trends and covenant or valuation metrics tied to revenue.
Diagnostic questions
Are the discounts, rebates, or usage credits contractual entitlements the customer can enforce, or purely discretionary goodwill gestures? Does the expected value method or the most likely amount method better predict the consideration the entity expects to be entitled to, given the range of possible outcomes? Is the estimate re-measured at every reporting date using the latest actual usage or performance data, not left at the original contract-inception estimate? Is the estimate constrained so that revenue is only recognized to the extent it is highly probable no significant reversal will occur later?
Recognition
- Identify every source of variability in the transaction price: volume rebates, prompt-payment discounts, usage thresholds triggering credits, SLA penalty clauses.
- Estimate the variable amount using either the expected value method (probability-weighted range of outcomes) or the most likely amount method, choosing whichever better predicts the consideration the entity will be entitled to.
- Apply the constraint: include variable consideration in the transaction price only to the extent it is highly probable that a significant revenue reversal will not occur when the uncertainty resolves.
- Recognize revenue net of the constrained estimate from the start of the contract, not gross with discounts booked separately as an expense.
- Update the estimate at each reporting date as new information becomes available, adjusting revenue in the current period (not restating prior periods) for the cumulative catch-up.
Measurement
Choose expected value when there is a range of possible outcomes with multiple scenarios (e.g., a range of possible rebate tiers), and most likely amount when the contract has only two possible outcomes (e.g., threshold met or not met). Re-measure at every reporting date using the latest usage or performance data, run-rating actual-to-date performance against the full-period threshold rather than assuming linear achievement. Document the constraint assessment factors considered (volatility of the outcome, length of time to resolution, extent of the entity's experience with similar contracts).
Presentation & disclosure
Disclose: (1) the methods (expected value or most likely amount) and significant assumptions used to estimate variable consideration; (2) how the constraint was applied and the factors considered; (3) significant changes in estimates of variable consideration and their revenue effect during the period; (4) the nature of discount, rebate and SLA credit arrangements affecting the transaction price.
Common mistakes
- Recognizing revenue at full list price and separately expensing anticipated discounts or rebates as a marketing or contra-revenue cost rather than netting them against revenue from inception
- ignoring probable SLA credits until they are actually issued
- applying an unconstrained most-likely-amount estimate for a highly uncertain, binary rebate outcome instead of properly weighing the probability of a significant reversal
- failing to true up the estimate promptly once actual usage or performance data diverges materially from the original assumption.
Simple example
A 12-month, SAR 1,200,000 contract (SAR 100,000/month) offers the customer a 10% rebate on the full annual fee if usage exceeds a defined threshold; based on the customer's historical usage pattern, management concludes it is highly probable the threshold will be met. Monthly journal entry recognizing revenue net of the expected rebate from month one (SAR 100,000 less 10% = SAR 90,000): Dr Contract asset / Accounts receivable 100,000 Cr Revenue - subscription 90,000 Cr Refund liability - rebate 10,000 At year-end, the threshold is confirmed met and the SAR 120,000 rebate (10% x 1,200,000) is settled as a credit note: Dr Refund liability - rebate 120,000 Cr Accounts receivable / Cash 120,000 (No further P&L impact, since the rebate was already fully constrained and provided for throughout the year.)
Professional judgment
The constraint on variable consideration is deliberately principles-based and requires weighing factors such as the volatility of the underlying outcome, the length of time before uncertainty resolves, the entity's experience with similar contracts, and the number of possible outcomes, reasonable preparers can reach different conclusions on borderline cases, particularly early in a contract term before usage data accumulates. Discretionary versus contractual credits also require judgment: a pattern of discretionary goodwill credits that recurs predictably may need to be treated as de facto variable consideration even without a contractual obligation, since the constraint is about substance, not just legal enforceability.
Source basis
IFRS 15 · Revenue from Contracts with Customers
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.