What is the residual approach to SSP and when am I allowed to use it?

The residual approach estimates one obligation's SSP as the total transaction price minus the sum of every other obligation's observable SSP. ASC 606-10-32-34(c) restricts it to cases where that obligation's price is highly variable (a broad range of observed prices) or uncertain (never sold standalone, no established price) — and even then, only if the result falls within a reasonable range.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

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

Part of the revenue recognition guide.

Governing guidance	FASB ASC 606-10-32-34(c)
Formula	Total transaction price − sum of observable SSPs of all other obligations = residual SSP
Highly variable	The item is sold to different customers at or near the same time for a broad range of prices, so no representative price is discernible
Uncertain	No established price exists and the item has never been sold on a standalone basis
Extra check	The residual result must fall within a reasonable range of SSPs, or the method isn't appropriate regardless of meeting the eligibility criteria

Why residual is the last method, not the easy one

The residual approach looks like the simplest way to handle an obligation without an observable price: subtract everything you do know from the total, and whatever's left is the answer. That simplicity is exactly why ASC 606-10-32-34(c) restricts it — using residual by default means one obligation's SSP is never actually estimated on its own merits, it's just whatever falls out of the math after the other obligations are priced. The standard only permits it when the specific obligation's price is highly variable or uncertain, not as a general substitute for the adjusted market assessment or expected cost plus margin approaches covered on the standalone-SSP-estimation page.

What "highly variable" actually means

Highly variable means the same good or service is sold to different customers, at or near the same time, for a broad range of amounts — broad enough that no single representative price is discernible from past transactions. A usage-tier or heavily negotiated add-on that routinely sells anywhere from $2,000 to $40,000 depending on the customer is a plausible candidate. A service that consistently sells within a tight band, even if that band isn't a single fixed price, generally isn't — a narrow range is still a discernible price for the adjusted market assessment method to work with.

What "uncertain" actually means

Uncertain means no established price exists and the item has never been sold on a standalone basis at all — not that the price is merely hard to estimate. A brand-new bundled feature that's never once been sold outside a package deal fits this. An implementation service that's routinely quoted (even if never actually invoiced separately) is a weaker case for "uncertain," because a quoted price is itself observable evidence an estimation method could use instead.

The check that comes after you're eligible to use it

Meeting the highly-variable-or-uncertain test doesn't end the analysis. If the residual calculation produces a result that falls outside a reasonable range of SSPs for that item, or contradicts other observable evidence, the residual approach isn't appropriate for that obligation even though the eligibility criteria were met — the standard is explicit that the outcome still has to make sense on its own terms, not just satisfy the entry test.

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

Residual approach applied, then abandoned when it fails the reasonable-range check

A $150,000 bundled contract includes three obligations: a platform subscription (observable SSP $100,000), a data migration service (observable SSP $30,000, based on standard hourly billing), and an add-on analytics module that's never been priced consistently — historical standalone quotes for it have ranged from $8,000 to $65,000 depending on negotiation, which is exactly the highly-variable profile 606-10-32-34(c) describes.

Applying the residual approach: $150,000 total − $100,000 (platform) − $30,000 (migration) = $20,000 residual SSP for the analytics module. That figure sits inside the $8,000–$65,000 observed range, so it passes the reasonable-range check and the residual approach is appropriate here.

Change one input: if the platform's observable SSP were instead $145,000 (a premium-tier customer), the same formula gives $150,000 − $145,000 − $30,000 = a negative $25,000. A negative or near-zero residual, or one that falls well outside the $8,000–$65,000 observed range, fails the reasonable-range check outright — at that point residual has to be abandoned for the analytics module, and an expected-cost-plus-margin or adjusted-market-assessment estimate has to be built instead, even though the module still meets the highly-variable eligibility test.

Frequently Asked Questions

Only if more than one obligation independently meets the highly-variable-or-uncertain test — and even then, applying it to multiple obligations in the same allocation compounds the risk that the result won't fall within a reasonable range for either one. In practice it's most defensible applied to a single obligation.

Comparable market pricing for similar items, internal cost-based estimates as a sanity check, or pricing guidance used in negotiations are all reasonable range indicators even without standalone sales history — the point is having something independent to check the residual figure against, not requiring actual standalone transactions.

No — only the obligation the residual approach was being used for needs a different estimation method. The observable SSPs for the other obligations in the contract don't change; only the failed obligation's estimate gets replaced.

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 determine standalone selling price (SSP) when I never sell the item separately?

ASC 606-10-32-33 requires using all available information to estimate SSP, maximizing observable inputs. The two primary methods are adjusted market assessment (what the market would pay) and expected cost plus a margin (your cost to deliver it, plus a reasonable margin). A residual approach exists but is restricted to narrow cases. Never allocate by an arbitrary split.