How do I true up estimated variable consideration under the ASC 606 constraint?

Re-estimate the constrained amount at every reporting period, not just once at contract inception. ASC 606-10-32-14 requires updating the estimate of the transaction price as uncertainty resolves, and adjusting revenue for the change using the same allocation basis established at the start — the constraint caps the estimate, it doesn't freeze it.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the revenue recognition guide.

The constraint itself	Include variable consideration only to the extent it's probable a significant reversal won't occur later (606-10-32-11)
What triggers a true-up	New information resolving some of the original uncertainty
Re-estimation requirement	606-10-32-14 — update the estimated transaction price at each reporting period
What both likelihood and magnitude matter for	Assessing whether the constraint still applies, not just whether it applied initially
Where the adjustment lands	Revenue, using the same transaction-price allocation basis set up at contract inception

The constraint is a ceiling, not a one-time decision

ASC 606-10-32-11 caps the amount of variable consideration an entity can include in the transaction price at the point it's probable a significant revenue reversal won't be needed later. That test isn't performed once at contract signing and then left alone — 606-10-32-14 requires re-estimating the transaction price, including the constrained amount, at every reporting period as new information becomes available.

What actually changes between periods

As a contract progresses, uncertainty that justified a constrained (lower) estimate often resolves — a performance bonus becomes more likely to be earned, a volume threshold that determines a rebate becomes clearer, a right-of-return window narrows. Each reporting period, both the likelihood and the magnitude of a potential reversal need reassessing against the latest facts, not just whether the constraint applied at all when the contract began.

Applying the true-up

When the re-estimate changes the transaction price, the adjustment is allocated using the same basis established at contract inception — it doesn't get to be reallocated as if the contract were being priced fresh. In practice, that usually means a change is recognized as an adjustment to revenue in the current period, catching up the cumulative recognized amount to what it would have been under the new estimate, rather than only affecting revenue prospectively.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

A performance bonus that goes from constrained to earned over three quarters

A services contract includes a $50,000 bonus payable if a project completes two weeks early. At Q1, the project is behind schedule and the bonus is far from probable — the entity constrains the transaction price to exclude the full $50,000, recognizing revenue as if the bonus won't be earned. By Q2, the team has caught up and the bonus now looks probable; the entity re-estimates the transaction price to include the full $50,000 and recognizes a cumulative catch-up adjustment to revenue in Q2 for the portion attributable to work already delivered. In Q3, the project finishes early and the bonus is confirmed — no further estimate change is needed, since the Q2 re-estimate had already brought the recognized revenue in line with the now-certain outcome.

Frequently Asked Questions

It goes both ways — if new information makes a previously-included amount less likely (a volume threshold now looking unreachable, for example), the re-estimate lowers the transaction price and produces a downward revenue adjustment, the same mechanism working in the other direction.

At minimum, every reporting period — ASC 606-10-32-14 doesn't set a looser cadence. A contract with fast-changing variable consideration may warrant checking more often internally even if formal reporting is quarterly or annual.

No — a true-up re-estimates variable consideration within the contract as originally agreed. A contract modification is a change to the contract's actual scope or price, which ASC 606 evaluates under its own separate guidance, not the variable-consideration re-estimation rules.

Sources

Topic

Revenue Recognition

Revenue recognition determines when — not just how much — revenue hits the books. Under ASC 606 (US GAAP) and its international counterpart IFRS 15, revenue is recorded as a company satisfies its perf…

How-to

How do you calculate a contract's transaction price under ASC 606?

Transaction price is the consideration a company expects in exchange for goods or services. Start with the stated contract price, add variable consideration using the expected-value or most-likely-amount method, constrained to amounts unlikely to reverse, adjust for any significant financing component, then subtract noncash consideration and amounts payable to the customer.

Diagnostic

How do I account for a mid-contract upgrade under ASC 606?

It depends on two tests: are the added goods/services distinct from what's already delivered, and is the added price in line with their standalone selling price? Distinct-and-priced-right modifications become a separate contract; distinct-but-mispriced ones get prospective treatment; not-distinct modifications require an immediate cumulative catch-up adjustment.

Definition

What SOX controls are typically required around revenue recognition?

The PCAOB requires auditors to treat improper revenue recognition as a presumed fraud risk unless that's documented and rebutted — which is why revenue controls sit at the center of most SOX programs. Typical controls split into preventive (segregation of duties across contract approval and billing) and detective (management review of estimates, reconciliations, flux analysis).