Variable Consideration Constraint Explained

Revenue from uncertain sources—rebates, discounts, price adjustments, performance bonuses—cannot be fully recognized upfront just because the contract is signed. ASC 606 imposes the variable consideration constraint: include only the amount of uncertain revenue that is “highly probable” to stick, avoiding large earnings reversals later.

The constraint problem

Without rules, a sales manager might argue: “We have a $1 million contract with a $200,000 performance bonus if we hit targets. We’re 60% confident we’ll hit them, so we should recognize $1.2 million in revenue (60% × $200,000) upfront.”

That logic fails the constraint test. ASC 606 says: do not include variable amounts in the transaction price unless, at the time of sale, it is highly probable you will not reverse that revenue later. A 60% confidence level means a 40% chance of reversal—far too risky.

The constraint is a breakpoint between optimism (marketing wants to recognize all possible upside) and prudence (auditors want stable, defensible figures). Companies must choose a high-confidence threshold—typically understood as 75–80%+ probability that the amount will not be reversed—before including variable revenue.

Expected value versus most-likely amount

ASC 606 offers two estimation methods, both subject to the constraint:

Expected value approach: Sum all possible outcomes weighted by probability.

• Contract: $100,000 base sale + possible $50,000 rebate.
• Outcomes: 70% chance $50,000 rebate is claimed (customer redeems it), 30% chance $0 (customer does not).
• Expected value of rebate = (70% × $50,000) + (30% × $0) = $35,000.
• Recognized revenue = $100,000 − $35,000 = $65,000 (reduced by the expected rebate).

This method works well for high-volume, predictable scenarios (e.g., retail return rates across millions of customers).

Most-likely amount approach: Choose the single most probable outcome.

• Same contract: $100,000 base + $0 or $50,000 rebate.
• Most likely outcome is no rebate (70% probability).
• Recognized revenue = $100,000 (no deduction).

This method suits binary or discrete outcomes (ship on time or late; hit milestone or miss it). It can be more aggressive than expected value if the single most-likely scenario is to the company’s benefit.

In both cases, the constraint applies: only include the estimated amount if reversal is highly improbable. Absence of a constraint would let companies record the maximum optimistic case upfront, then reverse later if reality disappointed.

Applying the constraint in practice

Price contingencies and bonus revenue

A software vendor signs a $5 million contract. The client receives a 15% discount ($750,000 off) if they pay upfront instead of in installments. Is the discounted price guaranteed?

• If upfront payment is virtually certain: include the $750,000 discount adjustment (lower recognized revenue). The constraint is met; reversal risk is near zero.
• If the client often defaults or switches to installments: hold the discount until received. Reversal risk is material.

Rebates and returns

A manufacturer offers a 10% rebate to distributors who hit quarterly volume targets. Historical data shows 55% achieve the rebate.

• Expected value method: Deduct 55% of potential rebates from revenue upfront.
• Most-likely method: Do not assume the rebate (since 45% don’t achieve it), so recognize full revenue.
• Constraint check: If historical data is stable and 55% is predictable, the company can use either method and meet the constraint. But if rebates are volatile or disputes are common, the company must hold more rebate contingency, deferring revenue.

Performance obligations and milestones

A contractor agrees to build a bridge for $100 million, with a $10 million bonus for finishing early.

• Early completion probability: 30%.
• Expected value = $100 million + (30% × $10 million) = $103 million.
• Constraint test: Is a 30% probability of the bonus “highly probable”? No. The company should not include the bonus in revenue initially.
• Instead: Recognize $100 million as work progresses. Later, as completion nears and early finish becomes likely (say, 85% probable), adjust revenue upward.

Reversal thresholds and monitoring

The constraint is not a one-time gate at contract signing. Companies must update estimates as new information arrives.

A company recognizes $100 million from a contract with a $20 million variable component at 80% confidence (meeting the threshold). Three months later, market conditions shift and confidence drops to 60%. The company must:

1. Reduce revenue in the current quarter to reflect the lower estimate (often called a “revenue reversal” even though it’s a reassessment).
2. Disclose the change in footnotes.
3. Monitor quarterly as facts evolve.

This creates earnings volatility, which is why companies often choose conservative upfront estimates—locking in a “floor” revenue and avoiding frequent reversals.

Strategic use of the constraint

Some companies deliberately use the constraint to manage earnings:

• Recognize only highly-certain revenue upfront, build a “reserve.”
• As actual results improve, release the reserve, boosting earnings in later quarters.

Auditors watch for this “earnings management” through the constraint, but within bounds it is standard practice. A conservative interpretation of “highly probable” is defensible and even encouraged by regulators.

Others use the constraint more aggressively, setting the probability threshold at exactly 75–80% to recognize as much variable revenue as they reasonably can without inviting audit objections.

See also