Variable consideration audit findings rarely come from not understanding ASC 606. Most finance teams can explain the constraint, walk through an expected value calculation, and point to the right codification paragraphs. The problem is the gap between knowing the standard and running a process that holds up when actuals diverge — six months in, under audit pressure. The three patterns below are where that discipline breaks down.
The Estimate That Never Gets Revisited
The initial constraint analysis gets written into a memo at contract inception. Variable consideration of $X included at expected value; constraint applied; reversal deemed not probable. Good work. File closed.
Three quarters later, actuals have diverged. The catch-up is material. The auditor asks for the quarterly re-estimation documentation. There isn't any — because the team treated the initial memo as a permanent policy decision rather than the first in a series of required updates.
ASC 606-10-32-14 is explicit: the transaction price, including constrained variable amounts, must be updated at each reporting period to reflect current information. That re-estimation has two sequential steps. First, update the estimate using current data — revised probabilities, performance to date, updated actuals. Second, re-apply the constraint to the new estimate, not to last quarter's number. A team that re-estimates upward without retesting the constraint has done half the work. The adjustment might be supportable; it might not. Without the documentation, you can't tell — and neither can your auditor.
The fix isn't elaborate. A quarterly re-estimation calendar with contract-level documentation: original estimate, methodology, what changed, updated estimate, resulting catch-up. Two pages per contract is enough. The absence of that documentation is what creates the audit problem — not the accounting.
"Probable" Is Only Half the Constraint Test
Teams tend to focus on the "probable" prong and move on. "We concluded there's a high likelihood of no reversal — therefore we've included the full variable amount." That's not wrong, but it's incomplete in a way auditors notice.
The constraint has two independent prongs under ASC 606-10-32-11: probable and not significant reversal. "Significant" requires a separate judgment, and that judgment is inherently context-dependent. A 4% revenue reversal might look clearly immaterial as a percentage of total revenue. That same reversal might be significant in context — if it moves a reported quarter below a debt covenant threshold, flips the period from profitable to breakeven, or affects a metric central to investor guidance. Whether any of those factors makes a reversal significant is a judgment call. The point is that significance has to be evaluated and documented with reference to the specific facts, not just declared in the abstract.
The analysis also needs to engage with the five risk factors in ASC 606-10-32-12 — not as a checklist, but as a totality-of-circumstances judgment. A constraint memo that doesn't address these factors, even briefly to explain why they don't apply, reads to an auditor as a conclusion without reasoning. Document the analysis, not just the outcome. Build re-evaluation of the constraint into your quarterly re-estimation process explicitly — the standard expects you to revisit the judgment each period.
When Billing and Rev Rec Live in Separate Worlds
The third pattern is structural. Billing systems capture usage actuals. Revenue recognition teams work from a separate system or a periodic export. The re-estimation process requires a reconciliation between them — which introduces lag, introduces manual error, and means updated actuals often arrive after close has started.
The result: re-estimation happens late, or the team defers it to next quarter because the data isn't clean enough to use. Neither is right. The standard doesn't have a "we didn't get the billing export in time" exception.
You don't need a new platform to address this. You need a defined process with four things documented and consistently applied:
- When actuals from billing become available for each contract type
- Who is responsible for the reconciliation between billing and rev rec data
- What the escalation path is if the data is late or inconsistent
- How the reconciliation is documented as part of the close
Auditors aren't expecting a perfect automated system — they're expecting evidence that you know what your process is and that you run it consistently.
What Audit-Ready Documentation Actually Looks Like
If someone pulled ten contracts at random from your portfolio today and asked for the variable consideration documentation for each one, what would they find?
At the contract level, auditors expect to see the original estimate (method, inputs, probability weights or most likely outcome selection), the initial constraint analysis (both prongs addressed, with reference to the five risk factors), and a quarterly update trail showing what changed each period and why. The update doesn't need to be elaborate — a one-page memo per contract per quarter is sufficient if it's actually there.
What they consistently find instead: a detailed inception memo, nothing for the next six quarters, and then a large catch-up adjustment with a brief explanation. That's not a documentation failure in the narrow sense — it's evidence that the re-estimation process wasn't running. The accounting conclusion might still be right, but the team has to reconstruct the reasoning retroactively under audit pressure, which is both unpleasant and avoidable.
Variable consideration compliance is a documentation and process problem more often than it's an accounting problem. Build re-estimation into your close calendar the same way reconciliations are built in — it's required by the standard and it's the only thing that makes the judgment calls defensible when they're examined later.
Frequently Asked Questions
How often does ASC 606 require re-estimating variable consideration?
Every reporting period. ASC 606-10-32-14 is explicit: the transaction price must be updated to reflect current information each period. An inception-date memo is the first required document, not the only one. Missing quarterly re-estimation documentation is one of the most common audit findings in variable consideration.
What are the two prongs of the variable consideration constraint test?
Probable reversal won't occur, and the reversal won't be significant. Both must be assessed independently. Teams that focus on "probable" and skip the significance analysis have done half the work. Significance is context-dependent -- a reversal that looks immaterial as a percentage of total revenue might still be significant if it affects a covenant, guidance metric, or reported margin.
What does a quarterly variable consideration re-estimation document need to include?
The original estimate and methodology, what changed in the current period (actuals, probabilities, market conditions), the updated estimate, how the constraint was re-applied, and the resulting catch-up or no-change conclusion. Two pages per contract per quarter is enough if the reasoning is there.
Why do billing and revenue recognition systems need to be connected for variable consideration?
Because re-estimation requires updated actuals, and usage actuals live in billing. If the rev rec team is estimating from management forecasts while actual usage data sits in the billing system unused, the re-estimation process is producing conclusions based on stale inputs. That's the harder audit conversation, because the data existed and wasn't used.
What triggers a significant reversal concern?
High susceptibility to factors outside your control, a long period before uncertainty resolves, limited experience with similar contracts, a broad range of possible outcomes, and history of changes in payment terms. ASC 606-10-32-12 lists these risk factors. A constraint memo that doesn't address them, even to explain why they don't apply, looks like a conclusion without reasoning.
