Variable consideration ASC 606 affects revenue whenever the amount a company expects to receive can change. Performance bonuses, volume rebates, refunds, penalties, price concessions, and milestone payments can all create variable consideration.
However, identifying variability represents only the first step. Management must also estimate the amount, apply the revenue-reversal constraint, update the assessment, and document each judgment.
Parisa Global Advisory helps US businesses address these technical accounting questions. This guide explains how management can identify, estimate, constrain, update, and document variable consideration under ASC 606.
What Is Variable Consideration Under ASC 606?
ASC 606 requires a company to determine the transaction price for each contract with a customer. The transaction price represents the consideration that the company expects to receive for transferring promised goods or services.
Sometimes, the contract states a fixed price. In other cases, future events can change the amount of consideration. ASC 606 treats that changing amount as variable consideration.
Common forms of variable consideration
Variable consideration can arise from several contractual features.
For example, a company may earn a performance bonus when it meets a target. A customer may qualify for a volume rebate after purchases cross a stated threshold. Similarly, a contract may reduce the price when the company delivers late.
Common forms include:
- Performance bonuses
- Milestone payments
- Volume discounts and rebates
- Customer refunds
- Rights of return
- Service-level penalties
- Price protection clauses
- Credits and concessions
- Usage-based fees
- Claims and incentive payments
Additionally, a company may create variable consideration through its normal business practices. A formal contract does not need to describe every concession.
Explicit and implicit variability
Explicit variable consideration appears directly in the contract. For instance, a software provider may earn a $25,000 bonus when implementation finishes before a stated date.
Implicit variability develops through business practice. A company may regularly accept less than the invoiced amount from a certain class of customers. That pattern may indicate an implicit price concession.
Therefore, management must review more than the signed contract. The analysis should also cover side letters, amendments, emails, customer communications, collection history, and previous concessions.
Why identification matters
A company cannot estimate an item that it has not identified. Consequently, an incomplete contract review can overstate or understate revenue.
Suppose a company invoices a customer for $100,000. However, management expects to accept $90,000 based on established practice. Recording the full invoice as revenue may not reflect the consideration that the company expects to collect.
In that situation, management should determine whether the $10,000 difference represents:
- An implicit price concession;
- A credit-risk issue; or
- A contract modification.
That distinction matters because ASC 606 and credit-loss guidance address different economic conditions.
Step 1 — Identify Variable Consideration in the Contract
Management should begin with a structured contract review. The process must capture both written pricing terms and established commercial practices.
Review the complete commercial arrangement
Start with the signed agreement. Then review all supporting documents that may change the price.
The review should cover:
- Master service agreements
- Purchase orders
- Statements of work
- Side letters
- Contract amendments
- Customer emails
- Rebate programs
- Return policies
- Pricing approvals
- Sales incentive plans
Furthermore, management should speak with the sales, operations, legal, and collections teams. These teams often know about informal pricing arrangements that the accounting team cannot see in the general ledger.
Identify the event that creates variability
Next, determine which future event changes the consideration.
For example, a contract may change the price based on:
- The customer’s total purchase volume;
- Completion by a target date;
- Achievement of a quality measure;
- Customer usage;
- Product returns;
- Market prices; or
- A regulatory or commercial milestone.
Management should describe each event clearly. That description helps the company select the correct estimation method later.
Separate variability from uncertainty about collectability
Variable consideration does not cover every possible payment shortfall.
A company may expect a customer to pay less because of a customary price concession. Alternatively, the customer may owe the full amount but lack the financial ability to pay.
The first situation may affect the transaction price. In contrast, the second situation may create a credit-loss issue.
Therefore, management should ask why it expects to receive less. The answer determines which accounting guidance applies.
Consider multiple variable elements separately
One contract may contain several forms of variable consideration.
For instance, a service contract may include:
- A $20,000 completion bonus;
- A $5,000 late-delivery penalty; and
- A 3% volume rebate.
Each element may require a different estimation method. Moreover, each element may have a different level of reversal risk.
Consequently, management should not combine all variable elements into one unsupported estimate.
Step 2 — Estimate Variable Consideration ASC 606
ASC 606 provides two methods for estimating variable consideration:
- The expected value method; and
- The most likely amount method.
Management must select the method that better predicts the consideration the company expects to receive.
Expected value method
The expected value method uses a probability-weighted range of possible outcomes.
Management identifies the potential outcomes, assigns a probability to each outcome, and calculates the weighted average.
This method usually works well when a contract has many possible outcomes. Tiered volume rebates, portfolio-based refunds, and product returns often fit this method.
Consider the following rebate arrangement:
| Customer purchases | Rebate | Estimated probability |
|---|---|---|
| Less than $500,000 | 0% | 20% |
| $500,000–$749,999 | 2% | 35% |
| $750,000–$999,999 | 4% | 30% |
| $1,000,000 or more | 6% | 15% |
Management calculates the probability-weighted rebate rate as follows:
- 0% × 20% = 0.00%
- 2% × 35% = 0.70%
- 4% × 30% = 1.20%
- 6% × 15% = 0.90%
The expected rebate equals 2.80%.
However, management must still apply the constraint. The probability-weighted estimate does not automatically enter the transaction price.
Most likely amount method
The most likely amount method selects the single most probable outcome.
This method generally works well when a contract has two possible results. For example, the company may earn a bonus in full or receive nothing.
Assume a consulting contract includes:
- A fixed fee of $100,000; and
- A $20,000 bonus for completing the project before June 30.
Management believes the company has a 75% chance of meeting the deadline.
The most likely amount equals $20,000 because management considers the bonus outcome more probable than the zero outcome.
Nevertheless, management must assess the constraint before including the bonus in the transaction price.
Choosing the appropriate method
ASC 606 does not allow management to choose the method that produces the highest revenue. Instead, the company must use the method that better predicts the amount it expects to receive.
The expected value method may work better when:
- The contract has several possible outcomes;
- Historical data supports probability estimates;
- The company manages many similar contracts; or
- Outcomes fall across a continuous range.
In contrast, the most likely amount method may work better when:
- The contract has only two primary outcomes;
- The payment depends on one milestone;
- The company either earns the full amount or earns nothing; or
- A single outcome clearly dominates the alternatives.
Management should apply the selected method consistently to the same variable element. However, the company may use different methods for different elements within one contract.
Step 3 — Apply the Variable Consideration Constraint
The estimation method predicts the amount of variable consideration. The constraint determines how much of that estimate management can include in the transaction price.
Purpose of the constraint
ASC 606 limits variable consideration to an amount for which a significant reversal of cumulative revenue will not become probable when the uncertainty ends.
Therefore, management must evaluate two matters:
- The likelihood of a future reversal; and
- The possible magnitude of that reversal.
A probable but insignificant reversal may not require the same constraint as a large probable reversal. Similarly, a large possible reversal requires careful analysis even when management has confidence in the expected outcome.
The FASB framework focuses on the possible reversal of cumulative revenue and requires consideration of both likelihood and magnitude.
Factors that increase reversal risk
Several conditions may increase the risk of a significant revenue reversal.
First, factors outside the company’s control may influence the amount. Examples include market prices, weather conditions, regulatory decisions, customer actions, and third-party approvals.
Second, the uncertainty may continue for a long period. Longer uncertainty often reduces management’s ability to predict the result.
Third, the company may have limited experience with similar contracts. Existing experience may also have weak predictive value when circumstances have changed.
Fourth, management may frequently grant price concessions or change payment terms.
Fifth, the contract may contain a broad range of possible consideration amounts.
The presence of one factor does not automatically exclude the full amount. Instead, management should consider the combined effect of all relevant factors.
Applying the constraint in practice
Management should begin with the estimate from the expected value or most likely amount method.
Next, the company should assess whether including that amount could create a significant future revenue reversal.
Suppose a company estimates a $20,000 performance bonus. However, customer acceptance depends on subjective criteria, and the company has little experience with similar arrangements.
Management may decide that including the full $20,000 creates excessive reversal risk. The company may therefore exclude the bonus until stronger evidence becomes available.
Alternatively, management may conclude that $12,000 can enter the transaction price without creating a probable significant reversal.
The constraint does not always require an all-or-nothing answer. A company may include the portion that meets the constraint and exclude the remainder.
A practical constraint example
Assume a construction-support company signs a six-month service contract.
The contract includes:
- Fixed consideration of $300,000;
- A completion bonus of $60,000; and
- A delay penalty of $10,000 per week.
At contract inception, management expects to complete the work on time. However, the project depends on permits from a third party.
The most likely amount method may indicate a $60,000 bonus. Yet permit timing remains outside the company’s control.
Therefore, management may constrain the entire bonus at inception. After the company receives the permits and completes most of the work, the reversal risk may fall.
At that later date, management may include some or all of the bonus and record the related cumulative adjustment.
Step 4 — Allocate Variable Consideration When Appropriate
After determining the transaction price, management normally allocates consideration based on relative standalone selling prices.
However, variable consideration may relate specifically to one performance obligation.
Variable consideration related to one obligation
A company may allocate variable consideration entirely to one performance obligation when:
- The payment terms relate specifically to that obligation; and
- The resulting allocation remains consistent with ASC 606’s allocation objective.
For example, a contract may include software implementation and one year of support. A bonus may depend only on completing implementation by a target date.
In that case, the bonus may relate specifically to the implementation service. Allocating the bonus across both implementation and support could distort the economics.
However, management must evaluate the facts. Contract wording alone does not determine the answer.
Variable consideration related to a distinct period
Some service contracts contain variable payments tied to a specific month, quarter, or service period.
For instance, a property manager may receive 5% of monthly rental collections. The variable fee may relate directly to the services provided during that month.
When the allocation criteria apply, the company may allocate the fee to the related service period rather than spreading it across the full contract term.
This analysis requires careful documentation because it affects both timing and presentation of revenue.
Step 5 — Update the Estimate at Every Reporting Date
Variable consideration ASC 606 requires continuous reassessment. Management cannot complete the analysis at contract inception and ignore later information.
Why management must update the estimate
Facts and circumstances change throughout a contract.
A customer’s purchasing activity may provide better information about a rebate threshold. Project progress may increase confidence in a performance bonus. In contrast, delays may increase the risk of penalties.
Therefore, management should update:
- The estimated variable amount;
- The selected probabilities;
- The most likely outcome;
- The constraint assessment; and
- The related allocation conclusion.
The company records the effect of the updated estimate in the current reporting period.
Cumulative catch-up adjustments
When an estimate changes, management calculates the revenue that the company should have recognized from contract inception through the current date.
The company then compares that amount with the revenue recorded to date. The difference becomes a cumulative catch-up adjustment.
Assume a company initially excludes a $20,000 bonus. The company has completed 75% of the related performance obligation.
Later, management concludes that the bonus now meets the constraint.
The company may need to recognize $15,000 immediately:
$20,000 × 75% = $15,000.
The remaining $5,000 enters revenue as the company completes the final 25% of the obligation.
Month-end and quarter-end review process
Management should include variable consideration in the regular close process.
A practical review should include:
- A list of contracts with variable pricing;
- Current contract status;
- Updated performance or volume data;
- Revised probabilities;
- Constraint conclusions;
- Revenue adjustments;
- Management approval; and
- Supporting documentation.
Additionally, the accounting team should coordinate with sales and operations. Those teams may know about customer disputes, expected concessions, milestone delays, or probable returns.
Journal Entries for Variable Consideration
The appropriate journal entry depends on the contract terms and the nature of the estimate.
Volume rebate example
Assume a company invoices a customer for $100,000. Management expects to provide a $5,000 volume rebate.
The company may record:
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable | $100,000 | — |
| Revenue | — | $95,000 |
| Refund or rebate liability | — | $5,000 |
This entry presents revenue net of the expected rebate.
Later, management revises the expected rebate from $5,000 to $3,000.
The company may record:
| Account | Debit | Credit |
|---|---|---|
| Refund or rebate liability | $2,000 | — |
| Revenue | — | $2,000 |
As a result, the company increases revenue because it now expects to pay a smaller rebate.
Performance bonus example
Assume a company earns the right to bill a $20,000 bonus after meeting a contractual milestone.
When the bonus meets the constraint and the company has satisfied the related performance obligation, the entry may include:
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable or contract asset | $20,000 | — |
| Revenue | — | $20,000 |
The company uses accounts receivable when it has an unconditional right to payment. In contrast, it uses a contract asset when something other than the passage of time affects the right to payment.
Documentation and Disclosure Requirements
Strong documentation allows management to apply the estimate consistently. It also helps internal decision-makers understand the financial effect of changing assumptions.
What the accounting memo should contain
A variable consideration memo should explain:
- The relevant contract terms;
- Each source of variability;
- The estimation method;
- Why management selected that method;
- The possible outcomes;
- The probability assumptions;
- Historical evidence;
- The constraint assessment;
- The amount included in the transaction price;
- The amount excluded;
- The allocation conclusion;
- The reporting-date update process; and
- The proposed disclosures.
Furthermore, the memo should identify the information management used. Examples include sales forecasts, return history, customer correspondence, project reports, and approved pricing concessions.
Avoid unsupported conclusions
A conclusion such as “management expects to earn the bonus” does not provide enough support.
Instead, management should explain the basis for that expectation.
For example:
- The project has reached 80% completion;
- The company has met all interim milestones;
- No unresolved customer disputes exist;
- Third-party approval has occurred; and
- Similar projects achieved the target in 90% of cases.
Specific evidence strengthens the conclusion and makes future updates easier.
Disclosure considerations
ASC 606 requires disclosures about significant judgments and changes in judgments that affect revenue recognition.
Accordingly, management may need to explain:
- The nature of variable payment terms;
- The estimation methods used;
- How the company applies the constraint;
- Significant assumptions;
- Changes in estimates;
- Refund, rebate, or return liabilities; and
- Remaining uncertainty.
Public companies should provide entity-specific information. Generic wording may not help investors understand the company’s revenue profile.
Common Variable Consideration Mistakes
Several errors appear repeatedly in variable consideration assessments.
Including the estimate without applying the constraint
Some companies calculate an expected value or most likely amount and place the result directly into the transaction price.
However, ASC 606 requires a separate constraint assessment.
Therefore, every material estimate should show two conclusions:
- The estimated amount; and
- The amount that meets the constraint.
Excluding all variable consideration until final settlement
Other companies apply the constraint too conservatively. They exclude every variable amount until the customer confirms the final payment.
That approach can understate revenue.
ASC 606 does not require certainty. Instead, the standard requires management to determine the amount for which a significant reversal will not become probable.
Applying one method to every arrangement
A company may use the expected value method for every contract because its spreadsheet already supports that method.
However, a binary bonus may fit the most likely amount method more closely.
Similarly, the most likely amount method may not capture a tiered rebate with several possible outcomes.
Management should select the method based on the nature of each variable element.
Failing to reassess the estimate
An estimate can become outdated quickly.
Customer purchases may approach a rebate threshold. Product return trends may change. A regulatory milestone may become more or less likely.
Consequently, management should review material estimates during every reporting close.
Using unsupported probabilities
Probability estimates require evidence.
Management should not select 70% merely because the number appears reasonable. Instead, the company should use historical outcomes, current project status, customer behavior, external conditions, and other relevant information.
When data remains limited, management should acknowledge that limitation in the constraint assessment.
Failing to document the conclusion
An undocumented estimate creates inconsistency.
One team member may include the full amount. Another may exclude it. A later reviewer may not understand why the original conclusion changed.
Therefore, management should prepare a written analysis for every material variable consideration element.
Variable Consideration ASC 606 — Quick Reference
| Area | Management question | Recommended approach |
|---|---|---|
| Identification | Can any future event change the consideration? | Review contracts, amendments, practices, rebates, returns, bonuses, and penalties |
| Expected value | Are there several possible outcomes? | Calculate a probability-weighted estimate |
| Most likely amount | Does the arrangement have a binary outcome? | Select the single most probable outcome |
| Constraint | Could the estimate cause a probable significant reversal? | Include only the amount that meets the constraint |
| Allocation | Does the variability relate to one obligation or period? | Evaluate the specific allocation criteria |
| Reassessment | Have facts or assumptions changed? | Update the estimate at every reporting date |
| Adjustment | Does the revised estimate affect prior progress? | Record the cumulative catch-up effect |
| Documentation | Can management support each judgment? | Prepare an accounting memo with evidence |
| Disclosure | Would users understand the uncertainty? | Provide entity-specific judgments and assumptions |
Frequently Asked Questions
What is the difference between estimation and the constraint?
The estimation method predicts the amount of variable consideration. The constraint determines how much of that estimate can enter the transaction price.
Therefore, management completes the estimation first. It then applies the constraint.
A company should not automatically reduce every estimate to zero. Similarly, it should not include the full estimate without assessing reversal risk.
Does variable consideration apply only to long-term contracts?
No. Variable consideration can arise in short-term and long-term contracts.
For example, a retail sale with a right of return creates variable consideration. A one-month service agreement may also contain a performance bonus.
The contract duration does not determine whether variability exists.
Can a company use different estimation methods in the same contract?
Yes. A company may use different methods for different variable elements.
For example, management may use the most likely amount method for a binary completion bonus. At the same time, it may use the expected value method for a tiered volume rebate.
However, management should apply each method consistently to the related variable element.
How often should management update variable consideration?
Management should update the estimate and constraint at every reporting date.
Additionally, the company may need an interim update when a major event occurs. Examples include customer acceptance, milestone completion, a contract amendment, or a significant change in expected returns.
Regular updates help prevent large and unexpected catch-up adjustments.
What happens when management changes the estimate?
The company generally records the effect of the change in the current reporting period.
Management first calculates the cumulative revenue that the company should have recorded using the revised estimate. The company then compares that amount with revenue already recorded.
The difference creates the cumulative catch-up adjustment.
How does variable consideration affect multiple performance obligations?
Management allocates variable consideration using the general allocation principles unless the amount relates specifically to one performance obligation or distinct service period.
When the specific-allocation criteria apply, the company may allocate the amount entirely to the related obligation.
However, management should confirm that the allocation remains consistent with the overall allocation objective.
Does the constraint address contract profitability?
No. The variable consideration constraint addresses revenue-reversal risk.
A separate analysis may apply when expected contract costs exceed expected consideration. The relevant accounting depends on the nature of the contract and the applicable guidance.
Therefore, management should not use the variable consideration constraint as a substitute for a loss-contract assessment.
Key Takeaways
- Variable consideration ASC 606 includes bonuses, rebates, returns, penalties, concessions, and other amounts that depend on future events.
- Management must review both written contract terms and established business practices.
- The expected value method works well for multiple outcomes, while the most likely amount method often suits binary outcomes.
- A separate constraint assessment determines how much of the estimate enters the transaction price.
- Management must update estimates, assumptions, and constraint conclusions at every reporting date.
- Clear accounting documentation should support the method, inputs, constraint, allocation, adjustments, and disclosures.
About Parisa Global Advisory
Parisa Global Advisory LLC provides bookkeeping, technical accounting, financial reporting, and SEC reporting advisory services to US businesses, cross-border companies, and public-market companies.
Our team helps management evaluate complex revenue arrangements, prepare technical accounting documentation, strengthen monthly reporting processes, and maintain consistent financial reporting positions.
Learn more at https://www.parisaglobaladvisory.com.
Parisa Global Advisory LLC provides bookkeeping, accounting, and financial reporting advisory services. We are not an audit firm and do not provide audit, review, attestation, or assurance services.