Most contracts have a price. Some contracts have a range. Variable consideration is what ASC 606 (and IFRS 15, paragraphs 50 through 58) calls the consideration that depends on a future event: a customer hitting a usage tier, a refund window closing, a performance bonus being earned. Step 3 of the model says estimate that consideration, include it in the transaction price, and then constrain the estimate so revenue does not reverse on the next reporting date.
This is the Step 3 detail the five-step overview only gestures at. It pairs with the performance obligations post (Step 2) and the contract modifications post, since a reassessment delta posts the same way a cumulative catch-up does. The estimation method, the constraint, and the reassessment cadence are where most of the rev rec close work hides.
What Counts as Variable Consideration
Each follows the same workflow under ASC 606-10-32-5 through 32-9: estimate the variable amount, decide which method to use, apply the constraint, and reassess every reporting date. Skip any of these and the income statement absorbs the reversal later.
Two Estimation Methods: Expected Value vs Most Likely Amount
ASC 606-10-32-8 says to pick the method that better predicts the consideration. The method is locked at contract inception and applied consistently to similar contracts. Auditors expect a documented policy stating which method applies to which contract type and why.
One Scenario, Two Methods, Two Numbers
A SaaS contract has a $100K annual base price, with a 5% rebate if the customer exceeds 10,000 API calls in the year. Historical data on similar customers gives a 70% probability of exceeding the threshold. The two methods produce different transaction prices.
| Step | Expected value method | Most likely amount method |
|---|---|---|
| Scenarios considered | 70% probability of $95K (rebate triggered), 30% probability of $100K (no rebate) | Single most likely scenario: customer exceeds the threshold |
| Calculation | (0.70 × $95K) + (0.30 × $100K) | Single outcome: customer exceeds threshold |
| Estimated transaction price | $96.5K | $95K |
Both methods are acceptable under ASC 606. The choice depends on the contract pattern, and the same method must be used for similar contracts to keep the policy defensible.
The Variable Consideration Constraint
A long time horizon, high judgment, a history of revisions, customer-specific factors, and a broad range of possible outcomes all push the estimate downward toward the amount that is highly probable.
A short time horizon, observable history, mechanical formulas with low judgment, and a narrow outcome range all support including more of the estimate in the transaction price.
When Variable Consideration Is Allocated to One PO, Not All
Variable consideration is normally allocated across all performance obligations in the contract in proportion to their standalone selling prices, the same way fixed consideration gets allocated under Step 4.
Under ASC 606-10-32-39 through 32-41, if the variable amount relates specifically to one PO AND allocating it entirely to that PO is consistent with the overall allocation objective, the variable amount is allocated entirely to that PO, not spread across all.
Common example: a SaaS contract has two POs (subscription and premium support), and a performance bonus tied only to the support SLA. Under the exception, the bonus is allocated entirely to the support PO, not split by SSP across subscription and support. The auditor reads both conditions: does the variable amount relate specifically to that PO, and is allocating it there consistent with the allocation objective?
See It in Motion
Where the Estimate Breaks
Three failure modes in variable consideration accounting
What Good Looks Like
A clean variable consideration workflow has the estimation method locked per contract type and applied consistently. The estimate is re-run at every reporting date with updated probabilities or scenarios. The constraint test runs at the time of estimation, not as a year-end true-up. The reassessment delta posts as a cumulative catch-up adjustment in the period the estimate changes, with the disclosures required by ASC 606-10-50.
At Cadel, variable consideration estimates are linked to the contract data that drives them. When the probability assumptions or the underlying performance metric changes, the estimate updates automatically. The constraint test runs continuously with documented evidence, the reassessment delta is calculated, the journal entry is generated, and the audit trail is preserved.
See how Cadel automates revenue recognition under ASC 606, or get in touch to walk through one variable consideration estimate (a rebate, performance bonus, or volume tier) and the constraint and reassessment cadence around it.