Picture this: it's the middle of the next quarter and your auditor is asking why last period's revenue suddenly looks different. The culprit isn't fraud or a typo. It's a volume rebate that finally tipped over a tier, a performance bonus that you never expected the customer to hit, and a service-level penalty you booked once and then forgot. Each one looked small in isolation, and together they forced a cumulative catch-up that wiped out two weeks of bookings.
If you sell anything more complicated than a one-time, fixed-price widget, ASC 606's rules on variable consideration apply to you. So do the rules on stand-ready performance obligations—the quiet promise you make every month that the platform will be there, the warranty desk will pick up, and the volume tier will reset on January 1. Get these two concepts right and your revenue line stops surprising people. Get them wrong and you'll be restating numbers and explaining yourself to investors and lenders.
This guide walks through what variable consideration is, how to choose between the expected-value and most-likely-amount methods, when the constraint forces you to defer revenue, what makes a stand-ready obligation different from a series of distinct services, and how to keep all of it tied back to the journal entries that hit your general ledger.
What Counts as Variable Consideration
ASC 606's transaction price is the amount of consideration an entity expects to be entitled to in exchange for transferring promised goods or services. The word "expects" is doing a lot of work. Real contracts rarely promise a single fixed number. Instead they include conditional adjustments that move the eventual cash up or down based on something that hasn't happened yet.
The standard lists the common forms explicitly. Variable consideration shows up as:
- Discounts and rebates: cash or credits the customer earns by hitting purchase thresholds, paying early, or qualifying for a promotional program.
- Performance bonuses and penalties: extra payments for finishing a construction milestone ahead of schedule or deductions for missing a service-level target.
- Refunds, credits, and price concessions: amounts you might give back if the customer is dissatisfied, if a market price moves, or if you offered an "if-then" clause.
- Royalties: payments calculated as a percentage of the customer's downstream sales or usage of licensed intellectual property.
- Rights of return: contractual or implicit promises to refund part or all of the purchase price.
- Contingent fees and commission clawbacks: amounts that depend on future events such as a successor sale or a referred customer staying for a defined period.
If your contract contains any of these, you have variable consideration and you need to estimate it. Not estimating is not an option. The standard explicitly tells preparers that "an entity shall estimate" the amount expected; you do not get to defer the question until uncertainty resolves except in one narrow case discussed below.
Choosing an Estimation Method
ASC 606 offers two methods. You pick the one that better predicts what you will eventually be entitled to receive. You apply the same method consistently within similar contracts, but nothing forces you to use the same method across dissimilar contract types.
Expected Value Method
The expected value method is a probability-weighted sum across the range of possible outcomes. It is the right tool when there is a continuum of possibilities or a large enough portfolio of similar contracts to build a meaningful probability distribution.
Imagine a software company that signs a 12-month contract with a customer for a usage-tier license. Based on the customer's historical behavior and signed forecast, the company estimates:
- 30% chance of $100,000 in fees (low tier)
- 50% chance of $130,000 in fees (mid tier)
- 20% chance of $160,000 in fees (high tier)
Expected value = (0.30 × $100,000) + (0.50 × $130,000) + (0.20 × $160,000) = $127,000.
That $127,000 becomes the starting transaction price. It is not constrained yet—we will get there.
Most Likely Amount Method
The most likely amount method picks the single most probable outcome. It works best when there are only two possible outcomes, typically a yes-or-no event such as hitting a bonus threshold or failing to.
Picture a construction contractor with a $2,000,000 base fee and a $200,000 bonus for finishing 15 days before the deadline. There is no in-between: either the contractor delivers early or it doesn't. If the project manager believes early completion is more likely than not based on the current schedule and past performance, the most likely amount is $2,200,000. If late delivery is more probable, the most likely amount is $2,000,000.
A useful heuristic: think binary, pick "most likely"; think continuum, pick "expected value." Either way, document the inputs and probabilities. Auditors test the math, but they also test the support behind the probabilities, and a spreadsheet with no source data won't survive.
The Constraint: The Single Most Important Sentence
Once you have an estimate, you apply the constraint. Variable consideration is included in the transaction price only to the extent that it is probable that a significant reversal of cumulative revenue recognized will not occur when the uncertainty resolves.
In English: don't book optimistic numbers you might have to take back. If there is a meaningful chance you'll later need to reverse some of the revenue you recognized, hold that piece back until you have more information.
The standard lists factors that increase the risk of a significant reversal:
- The amount depends on factors outside the entity's influence (markets, weather, customer behavior).
- The uncertainty is not expected to be resolved for a long time.
- The entity has limited experience with similar contracts.
- The contract has a wide range of possible outcomes.
- The entity has a history of changing payment terms or offering concessions.
Apply the constraint at the contract level (or sometimes at the performance-obligation level) and re-evaluate it every reporting period. If your initial estimate said $127,000 but the constraint says you can only justify $115,000, recognize $115,000 and hold $12,000 in reserve. When new data arrives, lift the constraint and recognize a catch-up, or tighten it and trim revenue. Either move flows through the income statement in the period when the estimate changes.
The Sales- and Usage-Based Royalty Exception
There is exactly one carve-out worth memorizing. For sales- or usage-based royalties promised in exchange for a license of intellectual property, you do not estimate and constrain. You recognize revenue only when the customer's sale or usage actually occurs (or when the related performance obligation is satisfied, if later).
This exception is narrow on purpose. It applies to IP licenses—music, film, brand licensing, franchise royalties tied to franchisee sales, certain technology licenses. It does not apply to general usage-based pricing in SaaS arrangements where the customer doesn't receive a transferable IP license, and it does not apply to volume rebates or performance bonuses that happen to look royalty-flavored.
If you are tempted to use the exception, stop and verify three things: there is a license, the license is of intellectual property, and the consideration is based on the customer's downstream sales or usage. Miss any of those and you are back to estimating and applying the constraint.
Stand-Ready Obligations: The Quiet Performance Promise
Variable consideration is about how much you'll receive. Stand-ready obligations are about what you've promised. ASC 606-10-25-18(e) describes a stand-ready obligation as a promise of "standing ready to provide goods or services" or "making goods or services available for the customer to use as and when the customer decides."
The classic example is a gym membership. The gym is not promising any specific class, any specific machine, or any specific amount of usage. It is promising to be open and operational. The customer's benefit is the availability, regardless of whether they show up.
Other typical stand-ready obligations include:
- Software-as-a-service subscriptions where the vendor provides continuous access to the platform.
- When-and-if-available software updates, where the customer pays for the right to receive updates the vendor may or may not release.
- Service-type extended warranties sold as separately priced products covering a future repair the customer may or may not need.
- Snow plowing or on-call IT support where the customer pays a flat fee for availability, not for usage.
- Cloud uptime commitments under master service agreements.
Why the Distinction Matters
A stand-ready obligation is a single performance obligation satisfied over time. Revenue typically recognizes on a straight-line basis across the period of availability, because the customer consumes the benefit evenly: the gym door is unlocked equally on day 1 and day 365.
Contrast that with a series of distinct goods or services that are substantially the same, which can also be treated as a single performance obligation under ASC 606-10-25-15. The difference matters when you're allocating variable consideration. For a series, the standard lets you allocate variable consideration to specific distinct goods or services within the series if it relates specifically to that part (the "exception" to allocating across the whole performance obligation). For a single stand-ready obligation, variable consideration spreads across the period of availability.
Get this wrong and you'll over- or under-recognize revenue in early periods of a multi-year contract. Get it right and the pattern matches the economics.
Assurance Warranties vs. Service Warranties
Stand-ready logic clarifies a frequent stumbling block. Warranties come in two flavors. An assurance-type warranty simply promises the product works as intended. It is not a separate performance obligation; it is a cost accrual recognized as warranty expense as products ship. A service-type warranty provides something beyond mere assurance—extended coverage, on-site repair guarantees, scheduled maintenance—and represents a stand-ready obligation to perform repair services over a defined period. Recognize the service-warranty portion of the price as deferred revenue on signing and amortize it straight-line over the coverage period.
A product with a one-year assurance warranty plus a separately priced three-year extended warranty gives you both treatments at once. Book the assurance piece as a warranty accrual. Book the extended-warranty fee as deferred revenue and release it over three years.
Putting It Together: A Walk-Through
Consider a SaaS company that signs a three-year subscription with annual fees of $300,000, a 10% volume rebate if annual usage exceeds 1,000,000 transactions, and a $50,000 SLA penalty per year for any quarter with sub-99.9% uptime. The platform is a continuous access service—a stand-ready obligation.
Step 1: Identify the performance obligation. Continuous platform access for three years is one stand-ready obligation, satisfied over time, recognized straight-line.
Step 2: Determine the transaction price for the next 12 months.
- Base fee: $300,000.
- Rebate: most-likely-amount method. The company estimates a 60% chance of crossing the threshold based on usage to date. Most likely amount: rebate triggers. Expected rebate: $30,000. Apply the constraint—if uptime to date is solid and history supports the estimate, recognize the gross fee net of $30,000, i.e., $270,000.
- SLA penalty: expected value method. Historical probability of a quarterly miss is 5% per quarter. Expected penalty: roughly $10,000 over the year. The constraint generally allows this estimate. Net it from the transaction price: $270,000 − $10,000 = $260,000.
Step 3: Allocate and recognize. With one stand-ready obligation, no allocation across performance obligations is needed. Recognize $260,000 ÷ 12 = $21,667 per month for the year, subject to true-up.
Step 4: Re-estimate quarterly. If actual usage at Q3 has clearly crossed the threshold and uptime is on track, lift the constraint and book a catch-up. If a major outage hits in Q4, trim the estimate and reduce revenue in the period of change.
Sample Journal Entries
At each month-end during year 1:
Dr Contract asset (or A/R) $25,000
Cr Subscription revenue $21,667
Cr Refund/rebate liability $2,500
Cr SLA penalty accrual $833If the customer's quarter ends and uptime hits 99.95%, the SLA accrual reverses to revenue:
Dr SLA penalty accrual $2,500
Cr Subscription revenue $2,500If usage falls short of the rebate threshold by year-end, the rebate accrual reverses too. If the threshold is hit, the accrual settles when the rebate is paid or credited.
These entries are simplified, but the structure is intentional: keep the rebate, refund, and penalty estimates on the balance sheet as liabilities (or contra-receivables), and move them to revenue (or away from it) when uncertainty resolves. Never let the variable component live only in a spreadsheet—it needs to hit the ledger.
Common Mistakes That Force Restatements
A few patterns show up over and over in revenue restatements involving variable consideration and stand-ready obligations.
Treating estimates as optional. Some preparers wait for the variable component to resolve before recognizing it. Unless the sales- and usage-based royalty exception applies, this is wrong. Estimate, constrain, recognize, and re-estimate. Waiting causes catch-up entries that distort comparative results.
Confusing a stand-ready obligation with a series of distinct services. A two-year managed-services contract where the provider responds to tickets as they arise is often a stand-ready obligation; revenue spreads straight-line. The same contract priced per ticket might be a series of distinct services. Mislabel the structure and your allocation of variable consideration—and your revenue pattern—will be off.
Misapplying the royalty exception. SaaS metered pricing is not a royalty on a license of IP unless you actually transfer a license. Audit firms have flagged this misapplication repeatedly.
Forgetting to re-estimate. The constraint isn't a one-and-done determination. Every period you're supposed to revisit estimates with new data. Companies that lock in a Q1 estimate and never touch it again end up with Q4 restatements.
Ignoring portfolio considerations. ASC 606 lets you apply the standard to a portfolio of similar contracts if doing so wouldn't materially differ from contract-by-contract application. For a SaaS company with 10,000 monthly subscribers, portfolio-level expected value can be both more accurate and far less work than 10,000 individual estimates.
Treating service-type warranties as assurance warranties. The separately priced extended warranty must be deferred and amortized; booking it all up front overstates revenue and understates the liability.
Keep Your Revenue Ledger Audit-Ready
Accurate variable-consideration accounting is part estimation, part documentation, and part bookkeeping discipline. Every estimate needs source data, every constraint decision needs a written rationale, and every accrual needs a journal entry that ties to the supporting workpapers. The companies that get this right are the ones that treat their general ledger as a living, plain-text record of every assumption rather than a black box.
Beancount.io provides plain-text accounting that's transparent, version-controlled, and AI-ready—so when an auditor or board member asks why this quarter's revenue moved, you can show them the exact entry, the exact estimate, and the exact change in assumptions. Get started for free and bring the same engineering rigor to your books that you bring to the rest of your business.