When it comes to revenue recognition under ASC 606, few topics demand as much time and attention as variable consideration. It’s everywhere, and if your business offers discounts, rebates, or royalties, chances are you’re already managing it. The challenge is that variable consideration heavily impacts two of the five steps in ASC 606—Step 3, determining the transaction price, and Step 5, recognizing revenue. In other words, it affects both the amount of revenue you recognize and when you recognize it.
What Makes Variable Consideration Tricky
Before ASC 606, companies often waited to record revenue until uncertainties were resolved. Now, that option is no longer available. You must make a judgment call upfront—estimating revenue at the start of the contract and updating it in each reporting period. This means your accounting team has to work in a world of estimation, probability, and constraints.
Variable consideration can show up in many forms, including:
- Conditional rebates or refunds
- Volume-based discounts
- Penalties for missed performance targets (e.g., SLA penalties)
- Royalties (sales- or usage-based)
- Price protection clauses
- Even implicit concessions, such as a history of accepting returns not specified in the contract
Bottom line: If the price isn’t fixed, you have variable consideration.
Estimation and Constraint: The Two Key Steps
Handling variable consideration under ASC 606 involves two steps:
1. Estimation
Revenue must be estimated at contract inception and then re-evaluated at the end of each reporting period—typically as a cumulative catch-up. Companies have the option to choose between two methods.
- Expected Value Method: Most effective when used with a portfolio of similar contracts
- Most Likely Amount: Best when there is a single most probable outcome
This isn’t a “set it and forget it” situation. The best practice is to establish policies, but be prepared to review them regularly as new data comes in.
2. Constraint
This is where conservatism comes into play. ASC 606 requires you to include variable consideration only to the extent that it is probable (75% or more likely) that a significant revenue reversal won’t occur when the uncertainty is resolved.
This is often included in your estimate, so these aren’t necessarily two distinct steps. The main point is re-evaluation. For example:
- A performance bonus is paid only if the project is finished on time.
- A milestone payment is contingent upon regulatory approval.
You can’t recognize a significant amount of revenue unless you’re confident you won’t have to reverse it later.
SEC Scrutiny in Action: Questions and Consequences
Consider these real-world examples of variable consideration and what occurs when the SEC investigates for clarification and enforcement.
Case 1: SEC Inquiry
This is a case where the SEC requested clarification or additional disclosure regarding how the company was handling variable consideration under ASC 606.
Trip.com Group Ltd. – In 2019, the SEC questioned Trip.com about whether its commission revenue from hotel reservations should be classified as variable consideration, noting whether cancellation provisions in contracts had been properly accounted for under ASC 606. Trip.com argued that cancellation provisions did not affect the timing of revenue recognition because the amount was not variable when the performance obligation was fulfilled. The performance obligation for hotel reservation services is considered complete when a reservation becomes non-cancellable. In this context, the consideration in the service contract with a hotel customer does not include a variable amount when the performance obligation is fulfilled.
Case 2: Enforcement/Penalties
This is a more serious case where the SEC found violations or alleged that the company improperly recognized revenue contrary to ASC 606, often involving failure to properly estimate or constrain variable consideration or meet performance obligations.
Pareteum – The SEC charged Pareteum executives with recognizing revenue based on non-binding purchase orders without verifying if performance obligations had been met. Some amounts in the purchase orders were not payable unless downstream conditions were fulfilled, yet Pareteum recognized them anyway. This raised concerns about variable consideration, collectability, and whether performance obligations were completed—all elements of the ASC 606 revenue recognition framework.
Why You Can’t Rely on Spreadsheets Alone
Managing variable consideration is more than just calculations—it’s about the process. You’re updating estimates, applying constraints, tracking changes across reporting periods, and maintaining an appropriate audit trail along the way. That’s a lot to handle if you rely on manual tools or disparate systems.
This is where SOFTRAX fits in. Our revenue management software is built to handle the complexities of variable consideration, including:
- Centralized tracking of contracts and performance obligations
- Automated application of revenue recognition rules
- Clear audit trails to support changes in estimation and judgments of constraint
- Flexible reporting to demonstrate how these assumptions affect your revenue over time
While SOFTRAX won’t provide the initial estimate for you (that still requires judgment), it can re-evaluate your initial estimate and model updates to provide more accurate calculations of variable consideration as more information becomes available. SOFTRAX RMS also ensures your policies are applied consistently, updates are documented, and your compliance with ASC 606 is airtight.
Final Thoughts
Variable consideration isn’t going away—in fact, it’s becoming more prevalent as businesses get creative with pricing and performance terms. The key is to shift from manual guesswork to systems that can manage the ongoing updates and documentation needed.
If your team is still relying on spreadsheets during each reporting period, it may be time to consider a more efficient approach. SOFTRAX can assist you in managing variable consideration with confidence, accuracy, and compliance. Contact us to learn more.
