Topics Tools Blog 5-Step Guide →
10 min read · Measurement

Variable Consideration

If any part of your price could change based on usage, volume, performance, or customer behavior, you have variable consideration — and specific estimation and constraint rules apply.

Educational content only. This page is not professional accounting advice. Consult a qualified accountant before making accounting policy decisions for your company.

Variable consideration is the #1 area where SaaS companies get tripped up on revenue recognition. The moment a price can go up or down based on something other than the passage of time — usage, volume, a performance milestone, a refund right, a discount — you have variable consideration, and you must estimate it, constrain it, and reassess it every reporting period.

Forms of Variable Consideration in SaaS

Variable consideration shows up in more places than most teams realize:

Estimation Methods

There are two acceptable methods for estimating variable consideration:

Expected value: The probability-weighted average across a range of possible outcomes. Best when there are multiple possible outcomes. Example: a volume rebate could result in $0, $5,000, or $10,000 depending on purchase levels. Weight each scenario by its probability and sum the result.

Most likely amount: The single most probable amount from a range of possible outcomes. Best for binary outcomes — either the milestone is hit or it isn't, either the refund is triggered or it isn't.

Use whichever method the entity expects to better predict the amount of consideration it will be entitled to. Once you pick a method for a contract, apply it consistently for that contract throughout its life.

The Constraint

The most consequential rule in variable consideration: you can only include estimated variable consideration in the transaction price to the extent it is highly probable (IFRS 15) or probable (ASC 606) that a significant revenue reversal will not occur when the uncertainty is resolved.

This is the constraint. It is asymmetric — you cannot include variable consideration if there's a significant risk of reversal, but you must recognize it when the constraint is lifted.

Factors that increase the likelihood that a revenue reversal would be significant (suggesting you should constrain the estimate):

Working Example: Usage-Based API Pricing with a Minimum Commitment

A SaaS company sells an API platform with the following structure:

Step 1 — Identify the variable components.

The $5,000/month is fixed — recognize it ratably. The overage charges and the retroactive volume discount are variable consideration.

Step 2 — Estimate using expected value.

Based on similar customers, the company estimates 65% probability the customer exceeds 250,000 calls/month (generating overages) and 30% probability the customer hits the quarterly volume tier. It calculates a probability-weighted estimate for monthly overage revenue: $1,400/month in expected overages.

Step 3 — Apply the constraint.

Is it highly probable (IFRS) / probable (ASC) that a significant reversal won't occur? The company has 2 years of history with similar customers. The estimate is based on stable usage patterns and the customer has already provided a forecast. The constraint is satisfied for the estimated overages.

Step 4 — Recognize and reassess.

Recognize $5,000 + $1,400 = $6,400/month in the transaction price for the current period. Each month, update the estimate based on actual usage to date. If the customer's actual usage deviates significantly from estimates, update the transaction price accordingly — recognize the cumulative adjustment in the current period.

The retroactive volume tier discount: Until the customer hits the threshold — or it becomes probable they will — constrain the discount. Once crossing the threshold is probable (e.g., in month 2 of the quarter the customer is on pace), include the retroactive rate reduction in the estimate.

Reassessment at Every Reporting Date

Variable consideration is not a set-it-and-forget-it calculation. At each reporting date (each quarter end for public companies, each year end for private), you must reassess:

Changes are recognized as cumulative catch-up adjustments in the current period — not by restating prior periods.

IFRS 15 vs. ASC 606

The frameworks are structurally identical — same two estimation methods, same constraint principle. The critical divergence is the probability threshold for the constraint: IFRS 15 uses "highly probable" (a higher bar, roughly 75%+) while ASC 606 uses "probable" (a lower bar). This means IFRS companies may constrain more variable consideration than US GAAP companies for the same contract.

Constraint threshold
IFRS 15

IFRS 15.56–57: include variable consideration only when it is "highly probable" that a significant reversal will not occur. "Highly probable" is generally interpreted as >75% likelihood.

ASC 606

ASC 606-10-32-11: include variable consideration only when it is "probable" that a significant reversal will not occur. "Probable" under US GAAP is generally >70–75%, but historically applied more broadly than IFRS "highly probable."

Estimation methods
IFRS 15

IFRS 15.53: expected value or most likely amount — same two options. Use the method that better predicts the entitled amount.

ASC 606

ASC 606-10-32-8: same two methods with same selection principle. No preference stated; consistency within a contract required.

Sales/usage-based royalties on IP
IFRS 15

IFRS 15.B63: special exception for IP licenses — recognize royalties only when the sale or usage occurs, regardless of the general variable consideration constraint guidance.

ASC 606

ASC 606-10-55-65: identical exception. Royalties on licensed IP are not estimated under the general variable consideration model — they are recognized as the underlying sale/usage happens.

Common Pitfalls
  1. Treating the minimum commitment as the entire transaction price. If a contract has a minimum plus usage-based upside, companies often recognize only the minimum. But the expected value of the overage — to the extent the constraint is satisfied — must also be included in the transaction price and allocated to performance obligations. Ignoring the overage estimate understates revenue.
  2. Applying the constraint as a blanket "recognize only when invoiced" policy. Some SaaS companies conservatively recognize variable consideration only when usage is confirmed and invoiced. This is too conservative if usage can be estimated reliably. Under-recognition of constrained estimates that are in fact probable is a misapplication of the standard, not a safe harbor.
  3. Forgetting to reassess estimates each reporting period. Variable consideration is not a year-end calculation — it must be reassessed at every reporting date. Companies that set initial estimates at contract signing and never revisit them will have inaccurate revenue throughout the contract life and potentially large, unexpected adjustments at period end.
  4. Confusing refund liabilities with contract liabilities. A refund right creates a refund liability — not a contract liability (deferred revenue). When you collect cash but the customer has a right to return or refund, the revenue is constrained and the expected refund amount sits as a refund liability on the balance sheet. The remaining amount (not subject to refund) is revenue. Presenting the whole amount as deferred revenue obscures the economics.
Key Takeaway

Variable consideration adds real complexity to transaction price measurement, but it is manageable with a disciplined process. The two-step approach — estimate using expected value or most likely amount, then apply the constraint — gives you a principled framework for any type of variable price. The IFRS/ASC divergence on the constraint threshold is the most important practical difference to track for dual-reporter companies. The biggest operational risk is not the initial estimate: it's failing to reassess and update that estimate every reporting period as actual data comes in.

Free Resource

5-Step Revenue Recognition Guide

Work through IFRS 15 and ASC 606 step by step with real SaaS examples.

Start the guide
Browse All Topics

More Application Guidance

Explore more deep dives on specific IFRS 15 and ASC 606 concepts.

All topics
Free Tool

27-Point Audit Checklist

Ensure your revenue recognition is audit-ready before your next close.

See the checklist
Free Tool

Revenue Memo Template

A 7-section auditor-ready memo documenting your revenue recognition policy.

Get the template