Variable Consideration Under ASC 606
Estimation Methods & the Constraint
Variable consideration is any part of the transaction price that can change — usage fees, rebates, bonuses, credits. This guide covers the two estimation methods ASC 606 allows, how the constraint limits what you can recognize, and worked examples for the scenarios B2B SaaS companies actually hit.
Variable Consideration Definition
Variable consideration is the portion of a contract's transaction price that depends on the outcome of future events — usage volume, discounts, rebates, credits, incentives, performance bonuses, penalties, or refund rights. Under ASC 606 and IFRS 15, you estimate variable consideration using the expected value or most-likely-amount method, then apply the constraint so only amounts unlikely to reverse are included in recognized revenue.
Governed by ASC 606-10-32-5 through 32-13 (and the converged IFRS 15.50–58).
Where variable consideration shows up in B2B SaaS contracts
Almost every modern SaaS contract has at least one of these.
Usage-based / consumption fees
Per-unit, metered, or tiered pricing where the amount billed depends on volume the customer has not yet generated.
Discounts, rebates, and credits
Volume rebates, prompt-payment discounts, and service credits owed if an SLA is missed.
Performance bonuses and penalties
Fees contingent on hitting a milestone, uptime target, or renewal — common in enterprise and usage-hybrid contracts.
Price concessions and refund rights
Implicit or explicit price protection, right of return, or true-up clauses that could reduce the transaction price.
The two estimation methods
ASC 606 requires whichever method better predicts the amount you'll actually be entitled to — applied consistently for similar contract types.
Expected value
Use when you have a large number of contracts with similar characteristics — a probability-weighted sum of possible outcomes.
Example: A SaaS company estimates that of 200 similar usage-based contracts, 60% will land in a $10K/mo tier and 40% in a $15K/mo tier. Expected value = (0.6 × $10K) + (0.4 × $15K) = $12K/mo.
Most-likely-amount
Use when the contract has only two possible outcomes (e.g., hit a bonus threshold or not) — the single most likely outcome.
Example: A contract pays a $50K renewal bonus if the customer renews, $0 if not. If renewal is more likely than not, the most-likely-amount is $50K, not a probability-weighted blend.
Applying the constraint
Estimating the amount is step one. The constraint decides how much of that estimate you're actually allowed to recognize.
Estimate the variable amount
Apply expected value or most-likely-amount, whichever better predicts the entitlement for that contract type.
Identify constraint indicators
Check for factors that increase reversal risk: susceptibility to factors outside your influence, long resolution periods, limited experience with similar contracts, broad price concessions, or a large range of possible outcomes (ASC 606-10-32-12).
Include only what is probable
Recognize variable consideration in the transaction price only to the extent it is probable that a significant reversal will not occur when the uncertainty resolves.
Re-estimate every period
At each reporting date, update the estimate and the transaction price for changes in circumstances — this is not a one-time calculation at contract inception.
How the constraint applies to common contract structures
| Scenario | Treatment |
|---|---|
| Pure pay-as-you-go, invoiced in arrears | Right-to-invoice practical expedient usually applies (ASC 606-10-55-18) — recognize the amount you have the right to bill, no separate estimate needed. |
| Usage with a minimum commitment | Recognize the committed minimum as usage occurs; estimate and constrain only the portion above the minimum if it is uncertain. |
| Volume rebate paid at year-end | Estimate expected rebate using expected value across the customer base; constrain to the amount probable of not reversing; true up quarterly as actual volume becomes known. |
| Renewal bonus contingent on a future event | Most-likely-amount; often fully constrained (excluded) until the renewal is reasonably certain, since reversal risk is high and resolution is far out. |
How LedgerUp handles variable consideration
Ari reconciles usage and contract terms, applies your estimation method and constraint policy consistently, and re-estimates every period — with a documented trail from raw usage to recognized revenue.
Related Guides
Variable Consideration FAQ
What is variable consideration under ASC 606?
Variable consideration is any part of a contract's transaction price that can change — usage-based fees, discounts, rebates, refunds, credits, incentives, performance bonuses, penalties, or price concessions. Under ASC 606 (and the converged IFRS 15), you estimate variable consideration using either the expected value or most-likely-amount method, then apply the constraint so you only include amounts you are confident will not later reverse.
What is the difference between the expected value and most-likely-amount methods?
Expected value is a probability-weighted average of a range of possible outcomes — appropriate when a company has many similar contracts. Most-likely-amount is the single most probable outcome in a binary or near-binary scenario — appropriate when there are only two realistic outcomes, such as a bonus that is either earned or not. ASC 606 requires you to use whichever method better predicts the amount you will actually be entitled to, applied consistently for similar types of contracts.
What is the constraint on variable consideration?
The constraint (ASC 606-10-32-11 through 32-13) limits how much variable consideration you can include in the transaction price. You include an estimated amount only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved. Indicators that increase constraint risk include susceptibility to factors outside the entity's influence, a long time until the uncertainty resolves, limited experience with similar contracts, a history of offering broad price concessions, and a broad range of possible consideration amounts.
How often do I need to re-estimate variable consideration?
At the end of each reporting period. ASC 606 requires updating the estimated transaction price throughout the contract to reflect changes in circumstances — new information about usage trends, revised probability of hitting a bonus, or an updated rebate forecast. Changes are generally accounted for as a cumulative catch-up adjustment to revenue in the period the estimate changes, allocated on the same basis as at contract inception.
Does the right-to-invoice practical expedient avoid the need to estimate variable consideration?
For pure usage-based or consumption pricing invoiced in arrears, yes — if the invoiced amount corresponds directly to the value the customer has received to date, ASC 606-10-55-18 lets you recognize revenue at the amount you have the right to invoice, without separately estimating and constraining variable consideration. The expedient does not apply if invoicing lags value transfer, if there are minimum commitments or tiered/retroactive pricing that decouple invoice amount from value delivered, or under IP licensing arrangements governed by the royalty exception instead.
How does variable consideration interact with usage-based billing specifically?
Usage fees are variable consideration by definition — the amount depends on consumption that has not yet happened at contract inception. Most usage-based SaaS either qualifies for the right-to-invoice expedient (recognize as billed) or requires an expected-value estimate when commitments, tiers, or retroactive pricing break the direct link between invoice and value delivered. Reconciling actual metered usage against the contract each period is what keeps the estimate — and the eventual invoice — accurate.
What disclosures does ASC 606 require for variable consideration?
Entities must disclose the methods, inputs, and assumptions used to estimate variable consideration and apply the constraint, including how those estimates are affected by factors outside the entity's influence. Public companies typically address this in the revenue recognition policy note and, where material, in a dedicated variable consideration or significant judgments disclosure.
How does LedgerUp handle variable consideration?
LedgerUp reconciles usage, minimums, tiers, and contract terms automatically, generates the expected-value or most-likely-amount estimate for each contract, applies a documented constraint policy, and re-estimates every period as usage data updates — producing an audit-ready trail from raw usage events to the recognized revenue number.