Variable consideration under ASC 606 is not optional math. If your AI or software company is selling on outcomes, your finance team owns a set of disclosures and estimates that your auditor will probe. Most AI and software companies selling on outcomes are handling this in spreadsheets. That's fine until the audit cycle, at which point it becomes an urgent problem.
What counts as variable consideration
Any portion of a transaction price that depends on future events. Performance bonuses. Shared savings. Penalties. Discounts tied to usage. Outcome-based fees. Clawbacks and reversals. If your contract has any of these, you have variable consideration, and ASC 606 has a prescribed approach to recognizing it.
The prescribed approach is not optional. Your auditor will ask whether you've applied it. The answer cannot be "we recognize revenue when we think we've earned it."
The two estimation methods
ASC 606 requires one of two approaches: the expected value method (probability-weighted average of possible outcomes) or the most likely amount method (the single most likely outcome). Choose based on which better predicts the consideration you'll be entitled to. Both require documentation.
Choose the wrong method — or switch methods without documentation — and you'll get an audit comment. Choose the right method but document it poorly and you'll get an audit comment. The documentation is not an afterthought.
The constraint
Even after estimating variable consideration, ASC 606 requires you to constrain the estimate — recognize only the amount that's probable will not result in a significant reversal. This is where most companies get into trouble. They estimate aggressively, fail to apply the constraint, and face audit adjustments.
The constraint requires judgment. Your auditor will probe that judgment. The defense is documented: what factors did you consider, what comparable transactions did you look at, and why did you conclude this amount meets the "probable no significant reversal" standard?
Period-end adjustments
Variable consideration estimates must be updated at each reporting period as circumstances change. This is not a one-time exercise. Your finance team needs a recurring process for reviewing estimates, documenting changes, and producing the audit trail.
If your outcome-based revenue is material and you don't have a period-end review process, you have an audit finding waiting to happen.
The evidence trail
Your auditor will ask how you know the estimate is reasonable. The answer cannot be "our sales team believes so." It needs to be documented evidence — historical performance data, contractual terms, market benchmarks, or independent verification.
Independent verification — outcome counts from a third party with no financial stake in the number — is the strongest possible evidence for a variable consideration estimate. It's also the evidence that takes the auditor's judgment about your judgment out of the picture.
What good looks like
A finance team with an ASC 606 methodology memo. Sample workpapers showing estimation and constraint analysis. Period-end review documentation. Integration between the outcome measurement system and the revenue recognition system. An audit trail that connects every dollar of recognized variable consideration back to specific verified outcomes.
This is achievable. It requires treating outcome measurement as a finance function, not just a sales function.