How do you estimate and constrain variable consideration under ASC 606?

What counts as variable consideration?

Step 3 of the revenue model is determining the transaction price, and ASC 606-10-32-5 requires an entity to estimate any variable amount in it. ASC 606-10-32-6 lists the usual sources — discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties — and adds the catch-all: consideration is variable whenever the entity's entitlement depends on whether a future event occurs. A product sold with a right of return and a fixed bonus payable on hitting a milestone are both variable, even though each individual payment is a fixed number.

Variability does not have to be written into the contract. Under ASC 606-10-32-7, consideration is also variable when:

• the customer has a valid expectation, from the entity's customary business practices, published policies, or specific statements, that the entity will accept less than the stated price (an implicit price concession); or
• other facts indicate that the entity intends at inception to offer a price concession.

That second leg is where implicit price concessions get separated from credit losses. If a company knowingly sells to a customer expecting to collect only part of the invoice and to accept that outcome, the shortfall is a price concession that reduces revenue. If the company expects to collect in full and the customer later cannot pay, the loss is a credit loss outside revenue. The answer turns on what the entity expected at inception, and documentation of that expectation is what a reviewer will ask for.

Common fact patterns that produce variable consideration:

Step one: estimate it (expected value or most likely amount)

ASC 606-10-32-8 allows two methods, and the choice is not a free policy election — an entity uses the method it expects to better predict the consideration it will be entitled to:

Two rules in ASC 606-10-32-9 sit around the choice, plus one point of interpretation:

1. Consistency within the contract. Once a method is chosen for a particular uncertainty, it is applied to that uncertainty for the life of the contract. A single contract can use different methods for different uncertainties — expected value for a daily delay penalty with many possible outcomes and most likely amount for a binary completion bonus is a standard illustration.
2. Use all reasonably available information — historical, current, and forecast — and identify a reasonable number of possible outcomes. The information typically resembles what management uses in bidding and pricing.
3. The expected value can be a number that is not itself a possible outcome — a point made in interpretive guidance rather than the Codification text. A 3.3% expected rebate rate across a portfolio is a valid estimate even if every individual customer will land on 0%, 3%, or 6%.

Step two: constrain it

The constraint in ASC 606-10-32-11 is what keeps estimates from front-loading revenue. Variable consideration is included in the transaction price only to the extent it is probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty is resolved. "Probable" carries its usual US GAAP meaning — the future event is likely to occur.

ASC 606-10-32-12 requires considering both the likelihood and the magnitude of a reversal, and lists factors that increase either:

• the amount is highly susceptible to factors outside the entity's influence (market volatility, third-party judgment or actions, weather, a high risk of obsolescence);
• the uncertainty will not be resolved for a long time;
• the entity's experience with similar contracts is limited or has limited predictive value;
• the entity has a practice of offering a broad range of price concessions or changing payment terms in similar circumstances; and
• the contract has a large number and broad range of possible consideration amounts.

Points practitioners get wrong:

• Magnitude is assessed against the contract as a whole — the cumulative revenue for the contract, fixed and variable consideration together — not against the variable piece alone or the amount allocated to one performance obligation. A possible $50,000 reversal on a $2 million contract may not be significant even if it is 100% of the variable amount.
• The constraint is not all-or-nothing. An entity includes the portion of the estimate that clears the threshold — the "some or all" in ASC 606-10-32-11. If a fee could range from $0 to $1 million and the entity is confident of at least $400,000, it includes $400,000.
• No single factor is determinative. A fee exposed to market movements is not automatically constrained to zero; the entity weighs the factors together.
• Sales- and usage-based royalties on licenses of intellectual property are excluded. ASC 606-10-32-13 sends them to ASC 606-10-55-65, which recognizes the royalty only when the later of the subsequent sale or usage and the satisfaction of the related performance obligation occurs.

Step three: reassess every reporting period

ASC 606-10-32-14 requires updating the estimated transaction price — including whether the estimate is constrained — at the end of each reporting period. Changes are accounted for under ASC 606-10-32-42 through 32-45: a change is allocated to the performance obligations on the same basis as at inception, and the portion allocated to obligations already satisfied is recognized as revenue (or a reduction of revenue) in the period of the change. That is a cumulative catch-up, not a prospective spread.

One exception narrows where a change lands. If the variable payment relates specifically to the entity's efforts to satisfy one performance obligation (or one distinct period in a series), and allocating it there is consistent with the allocation objective, ASC 606-10-32-40 allocates the variable amount — and later changes to it — entirely to that obligation or period. This is why a usage fee for March in a monthly service contract is recognized in March rather than spread over the contract.

Worked example 1: a performance bonus (most likely amount)

A contractor agrees to build a facility for a fixed $2,000,000 plus a $200,000 bonus if the facility is complete by June 30. Revenue is recognized over time using a cost-to-cost measure of progress. There are two possible outcomes for the bonus, so the most likely amount is the better predictor.

At March 31 the project is 40% complete. The contractor has a strong record of on-time completion on similar builds, the remaining work is within its control, and it concludes the bonus is the most likely outcome and that including it is not expected to cause a significant reversal. Transaction price: $2,200,000.

Quarter ended March 31 (40% complete)
Cumulative revenue = $2,200,000 x 40% = $880,000

Dr. Contract asset / receivable          880,000
Cr. Revenue                                     880,000

At June 30 the project is 70% complete, but a supplier delay means the June 30 date will be missed. The bonus is now not expected, and the transaction price drops to $2,000,000. Under ASC 606-10-32-42 through 32-45, the change is reflected on a cumulative basis:

Cumulative revenue at 70% = $2,000,000 x 70% = $1,400,000
Less: revenue recognized in Q1                  (880,000)
Q2 revenue                                       520,000

Of which: catch-up reversal of the bonus previously
included ($200,000 x 40%)                        (80,000)

The $80,000 reduction is not a separate entry; it is embedded in the Q2 revenue figure. Disclosure of revenue recognized from obligations satisfied in prior periods may be required (ASC 606-10-50-12A).

Worked example 2: a right of return (expected value)

A manufacturer sells 1,000 units at $100 each to retailers, with a 30-day right of return. Cost is $60 per unit. Across a large population of similar sales, returns have run at 5% and the pattern is stable, so the expected value method fits and the estimate is not constrained beyond the 5%. The manufacturer expects returned units to be resaleable at no recovery cost.

Under ASC 606-10-55-23 through 55-27, revenue is recognized for the 950 units not expected to be returned; a refund liability is recognized for the 50 expected returns (ASC 606-10-32-10); and an asset for the right to recover the products is measured at their former carrying amount less expected recovery costs (ASC 606-10-55-27).

At sale
Dr. Cash / receivable                   100,000
Cr. Revenue (950 x $100)                         95,000
Cr. Refund liability (50 x $100)                  5,000

Dr. Cost of sales (950 x $60)            57,000
Dr. Asset for recovery (50 x $60)         3,000
Cr. Inventory (1,000 x $60)                      60,000

The refund liability and the asset for recovery are presented separately (gross), and both are remeasured each reporting date, with refund liability changes recorded in revenue (ASC 606-10-55-26 and 55-27). Exchanges of one product for an identical one of the same type, quality, condition, and price are not returns (ASC 606-10-55-28).

Worked example 3: a retroactive volume rebate, reassessed mid-year

A component supplier sells to an OEM at $50 per unit. If the OEM's calendar-year purchases reach 100,000 units, the supplier rebates 4% of the price on every unit purchased in the year. The rebate is binary at the contract level, so the supplier uses the most likely amount.

Q1: The OEM buys 30,000 units. Its forecast and purchase history indicate it will pass 100,000 units, so the supplier estimates the rebate will be earned. Including the full $50 price would risk a significant reversal if the threshold is reached; the constrained price is $48.

Q1 (30,000 units)
Dr. Receivable (30,000 x $50)          1,500,000
Cr. Revenue (30,000 x $48)                     1,440,000
Cr. Refund liability (30,000 x $2)                60,000

Q2: Another 25,000 units at the same estimate: revenue of $1,200,000 and a further $50,000 refund liability, bringing the liability to $110,000.

Q3: The OEM loses a major program. It buys 20,000 units in Q3 (75,000 cumulative) and its revised forecast for Q4 is about 12,000 units — roughly 87,000 for the year. The supplier now concludes the threshold will not be reached and that recognizing the full $50 price is not expected to produce a significant reversal. Under ASC 606-10-32-14 and 32-43, the change in transaction price for units already transferred is recognized in the period of the change:

Q3 (20,000 units, plus release of the rebate accrual)
Dr. Receivable (20,000 x $50)          1,000,000
Dr. Refund liability                     110,000
Cr. Revenue                                    1,110,000

The expected-value alternative is worth seeing for contrast. If the supplier had a portfolio of similar distributors with tiered rebates of 0%, 3%, and 6% and probabilities of 20%, 50%, and 30%, the expected rebate rate would be 3.3% (0.2 x 0% + 0.5 x 3% + 0.3 x 6%). Whether a probability-weighted rate or a most-likely rate better predicts the entitlement is the ASC 606-10-32-8 judgment, made per uncertainty and documented.

Variable consideration or something else?

Several features look like variable consideration but are analyzed elsewhere:

• Optional purchases. A customer's option to buy additional goods is not variable consideration in the existing contract; it is evaluated as a potential material right under ASC 606-10-55-41 through 55-45. The distinction matters for volume discounts: a retroactive discount on purchases already made is variable consideration, while a discount that applies only to future purchases is analyzed as an option.
• Consideration payable to a customer. Slotting fees, coupons, and credits paid to a customer reduce the transaction price unless they are payment for a distinct good or service (ASC 606-10-32-25), and some of them are themselves variable.
• Credit risk. As above, an expected inability to pay is a collectibility or credit-loss question, not an implicit price concession, unless the entity intends at inception to accept less.
• Significant financing components and noncash consideration are separate adjustments to the transaction price under ASC 606-10-32-15 and 32-21.

Disclosure

ASC 606-10-50-20 requires disclosure of the methods, inputs, and assumptions used to estimate variable consideration and to assess whether an estimate is constrained, as well as to measure obligations for returns, refunds, and similar items. Entities other than public business entities and certain other entities may elect out of most of that disclosure, but not the methods, inputs, and assumptions used to assess whether an estimate of variable consideration is constrained, which remain required (ASC 606-10-50-21). Auditors also expect a contemporaneous constraint analysis — the factors considered, the evidence, and why the included amount clears the "probable" threshold — for each significant variable term.