Variable consideration contingent on customer-achieved performance milestones

Some enterprise SaaS deals hold back a portion of the fee, or add a success fee, contingent on the customer achieving a specific business outcome (a cost saving, an adoption threshold) rather than on the vendor's own usage-based delivery; this outcome-contingent variable consideration is highly uncertain because it depends substantially on the customer's own actions, and applying the constraint properly often means excluding the entire amount from revenue until the outcome is known, distinct from the more routine usage-metered or discount-based variable consideration seen elsewhere.

Is achievement of the customer's KPI substantially outside the vendor's control, increasing the uncertainty around whether the constraint should exclude the fee entirely? Is there a reliable historical basis, such as outcomes achieved with similar customers, to estimate the probability of the milestone being met? Should the success fee or holdback be excluded entirely from the transaction price until the constraint is resolved, or does partial inclusion have supportable evidence?

1. Identify any portion of the fee that is contingent on an outcome achieved by the customer (e.g., a cost-saving threshold, an internal adoption rate, a productivity metric) rather than on the vendor completing its own usage-based or milestone-based delivery.
2. Distinguish this from vendor-controlled variable consideration (usage tiers, service-level credits), since the constraint analysis differs when the resolving event is substantially outside the vendor's influence.
3. Assess the entity's ability to predict the outcome: consider the volatility of the outcome, the extent of the vendor's historical experience with similar contingent-fee arrangements and comparable customers, and how much the outcome depends on factors outside the vendor's control (e.g., the customer's own change-management effort).
4. Apply the constraint: include the contingent fee in the transaction price only to the extent it is highly probable that a significant revenue reversal will not occur once the customer's outcome is known.
5. Where the outcome is largely outside the vendor's influence and the entity lacks sufficient reliable historical data on similar arrangements, constrain the estimate to zero and exclude the entire contingent fee from the transaction price until the milestone is resolved, rather than including a partial, unsupported estimate.
6. Recognize the previously constrained amount as revenue only when the uncertainty is resolved (the customer's outcome becomes known) and it is confirmed the entity is entitled to the fee, reassessing the constraint at each reporting date in the interim as more information becomes available.

Where the constraint results in full exclusion, no measurement of the contingent fee is included in the transaction price until the outcome is resolved. Where partial inclusion is supportable (e.g., some reliable historical experience exists), use the expected value or most likely amount method consistent with the nature of the possible outcomes, applying a conservative estimate given the vendor's limited influence over the resolving event. Reassess the constrained estimate at each reporting period as more information about the likelihood of the customer achieving its outcome becomes available (e.g., interim adoption metrics trending toward or away from the threshold), recognizing any change as a cumulative catch-up to revenue in the period the assessment changes.

Disclose: the nature of outcome-contingent fees and how they differ from usage-based or discount-related variable consideration; the basis for any amount included in (or excluded from) the transaction price, including the key factors considered in the constraint assessment; the sensitivity of revenue to the constraint judgment where the amounts involved are significant; significant changes in the constrained estimate during the period and the resulting cumulative catch-up effect on revenue.

• Recognizing the full success fee as revenue at contract signing based on management'
• s optimism about the customer achieving the outcome, rather than a supportable, evidence-based probability assessment
• failing to distinguish outcome-contingent fees (largely outside vendor control) from usage-based fees (within the constraint framework already routinely applied to metered billing), applying an inappropriately lenient constraint to the former
• including a partial estimate of the contingent fee without sufficient reliable historical data to support it, rather than constraining fully to zero
• not reassessing the constraint as interim customer performance data becomes available during the contract term, missing an opportunity to recognize revenue earlier once the outcome becomes highly probable, or conversely, failing to reverse an overly optimistic earlier estimate.