Short answer: Variable consideration is any part of a contract price that can change, such as service credits, volume rebates, usage fees or price concessions. Under ASC 606 and IFRS 15, a SaaS company estimates it using either the expected value or the most likely amount, then includes it in revenue only to the extent that a significant reversal is not expected later. That limit is called the constraint.
For a SaaS finance team the question is practical: how much of this month's invoice is revenue, and how much should be held back for credits or rebates the customer may claim? Getting it wrong means revenue that has to be reversed in a later quarter, which is the outcome the constraint exists to prevent.
What counts as variable consideration in a SaaS contract
Variable consideration is any amount in the transaction price that depends on a future event. The IFRS Foundation summary of IFRS 15 puts the requirement simply: if consideration "includes a variable amount, an entity must estimate the amount of consideration" to which it expects to be entitled. ASC 606 contains the same requirement.
In SaaS contracts the usual sources are:
- Service level credits. A credit against future fees if uptime or support response falls below a stated level.
- Retrospective volume rebates. A lower unit price applied to the whole year once usage or seats pass a threshold.
- Usage and overage fees. Charges based on transactions, API calls or seats above an allowance.
- Price concessions. Discounts the vendor is expected to give, whether or not the contract states them, based on its past practice.
- Refund rights. Money-back terms during an initial period.
Variability can be stated in the contract or implied by the vendor's customary business practice. A history of granting credits on request is itself evidence that the price is variable. Our overview of revenue recognition types places these within the wider set of SaaS revenue streams.
Expected value or most likely amount
ASC 606 and IFRS 15 allow two methods of estimating variable consideration. A company uses the one that better predicts the amount it will be entitled to, and applies it consistently to similar contracts.
The table below compares the two methods.
| Method | How it works | Best suited to |
|---|
| Expected value | Sum of possible amounts, each weighted by its probability | Many similar contracts, such as SLA credits across a customer base |
| Most likely amount | The single most likely outcome in a range | Two possible outcomes, such as a rebate earned or not earned |
Source: summary prepared for this article from the ASC 606 and IFRS 15 estimation requirements.
The methods can produce very different numbers for the same contract. For a credit that is paid in a small share of cases, the most likely amount is zero, while the expected value is a small positive figure. Choose by contract type and record the reason.
How the constraint limits revenue
The constraint is the second step. After estimating variable consideration, a company includes it in the transaction price only to the extent that it is probable under ASC 606, or highly probable under IFRS 15, that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved.
The constraint tends to bite harder where:
- the amount depends on factors outside the vendor's control, such as customer usage;
- the vendor has limited experience with similar contracts;
- the uncertainty is not expected to resolve for a long time;
- there is a broad range of possible outcomes.
The constraint is applied to the estimate, not in place of it. A company estimates first, then asks how much of that estimate is safe to recognize now.
Service credits and SLA credits
Service level credits reduce the consideration a SaaS company is entitled to, so they are variable consideration rather than an expense. They are usually estimated with the expected value method, because the vendor has many customers on similar terms.
Illustrative example: a customer pays $10,000 a month from January 1, 2026. The contract grants a credit of 10% of the monthly fee in any month uptime falls below the committed level. Across similar contracts, the vendor has granted the credit in about 5% of customer-months. The expected credit is 10% times 5%, or 0.5% of fees: $50 a month. Monthly revenue is $9,950, and a $50 liability is recorded for expected credits.
If uptime is consistently above the committed level and credits are rare, the estimate may be immaterial. Document that conclusion and revisit it after any significant outage, because a single incident can change the history the estimate relies on.
Volume discounts and rebates
A retrospective volume rebate lowers the price on units already delivered once a threshold is reached. That makes the whole year's price uncertain from the start, so the expected rebate is estimated and the constraint applied each month.
Illustrative example: a customer pays $50 per seat per month in 2026. If its average seats for the year exceed 1,000, the price for the whole year falls to $45. The customer has 950 seats in January and is adding 10 a month. The most likely amount method suits this two-outcome case. If reaching the threshold is the most likely result, the company recognizes revenue at $45 per seat from January, even though it invoices at $50, and records the $5 difference as a refund liability.
A prospective tier, where only seats above the threshold are cheaper, works differently. Seats already delivered keep their price, so the rebate is not variable consideration on past service. It can raise a separate question about options for additional purchases, which is outside the scope of this article.
Promotional discounts and free months
A discount fixed at signing is not variable consideration. It simply lowers the transaction price, which is then recognized over the service period like any other fixed price.
Free months follow the same logic when they fall within a committed term. Illustrative example: a customer signs a 15-month non-cancelable contract on January 1, 2026, paying $120,000 for 12 months with the first three months free. The service is the same throughout, so total consideration of $120,000 is recognized over 15 months at $8,000 a month, starting in January.
| Period | Invoiced | Revenue recognized |
|---|
| January to March 2026 | $0 | $24,000 |
| April 2026 to March 2027 | $120,000 | $96,000 |
| Total | $120,000 | $120,000 |
Source: illustrative figures prepared for this article; not customer data.
If the customer can cancel at the end of the free period without penalty, the analysis changes. The enforceable contract may only cover the free months, with no consideration, and revenue starts when the paid term becomes binding. Read the termination clause before building the schedule.
Reassessing estimates at each close
Variable consideration is re-estimated at each reporting date. A change in estimate is a change in the transaction price, and the adjustment is recognized in the period of the change for the service already delivered.
A short month-end routine keeps this under control:
- Update inputs. Uptime records, seat counts, usage and credits granted in the month.
- Recalculate. Rerun the estimate with the same method used last period.
- Book the true-up. Adjust revenue and the related liability for the change.
- Document. Keep the calculation and the reason for any change in method.
Auditors often ask for this file. The ASC 606 compliance audit checklist for SaaS covers the evidence they expect, and the guides to ASC 606 and IFRS 15 for SaaS companies cover the wider model.
How ScaleXP supports variable pricing in revenue schedules
ScaleXP builds revenue schedules and journals from your invoice data in Xero or QuickBooks, including credit notes, and can use deal data from HubSpot, Salesforce or Pipedrive. Finance sets the estimate and the constraint judgment for variable amounts. ScaleXP prepares the revenue and deferred revenue journals, and they are posted once finance approves them.
See how revenue schedules and journals are built on the revenue recognition automation for Xero and QuickBooks page.
Conclusion
Variable consideration in SaaS covers service credits, retrospective rebates, usage fees and price concessions. Estimate it with the expected value or most likely amount, whichever predicts better, apply the constraint, and update the estimate at each close. Fixed discounts and free months inside a committed term are not variable; they lower the price, which is then spread over the service period.
Frequently asked questions
What is variable consideration under ASC 606?
Variable consideration is any part of the contract price that depends on a future event, such as service credits, volume rebates, usage fees, refunds or price concessions. ASC 606 requires a company to estimate it and include it in the transaction price only to the extent that a significant revenue reversal is not expected later. IFRS 15 contains the same requirement.
Are SLA credits variable consideration?
Yes, service level credits reduce the amount a SaaS company is entitled to, so they are variable consideration and reduce revenue rather than being booked as an expense. They are usually estimated with the expected value method, using the history of credits granted across similar contracts. If credits are rare, the estimate may be immaterial, but that conclusion should be documented and revisited.
What is the difference between expected value and most likely amount?
The expected value method weights each possible amount by its probability and adds them up, which suits large numbers of similar contracts. The most likely amount method takes the single most likely outcome, which suits cases with two possible results, such as a rebate earned or not earned. A company uses whichever better predicts the amount it will receive.
How do free months affect SaaS revenue recognition?
Free months inside a committed contract term are a discount, not variable consideration. The total fee is spread over the full service period, including the free months. A 15-month contract with $120,000 billed for 12 months is recognized at $8,000 a month from the start. If the customer can cancel after the free period without penalty, the paid term is assessed separately.
Is the variable consideration constraint different under IFRS 15?
The constraint works the same way under both standards, but the wording differs. ASC 606 uses "probable" and IFRS 15 uses "highly probable" when asking whether a significant revenue reversal will not occur.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
