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.

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-33 (estimating SSP when not directly observable)
Primary methods	Adjusted market assessment approach; expected cost plus a margin approach
Restricted method	Residual approach — only when SSP is highly variable or uncertain (see the companion page on that method)
Requirement	Maximize the use of observable inputs before falling back to an estimate
Not acceptable	List price, an arbitrary percentage split, or a number picked to hit a target margin

Why you can't just use list price or a round-number split

ASC 606's allocation step requires the transaction price to be split across performance obligations in proportion to each one's standalone selling price — the price you would charge a customer for that item on its own. When you've genuinely never sold the item separately, there's no observed price to allocate against, which is exactly the gap 606-10-32-33 addresses: it requires an entity to estimate SSP using all information reasonably available, maximizing observable inputs first. An arbitrary split, or a number chosen to make the schedule look a particular way, doesn't satisfy that requirement even if it nets to the same total transaction price.

What the two primary estimation methods actually are

The adjusted market assessment approach estimates what the market would pay for the item, adjusted for your specific costs and margins — it works when there's a reasonable comparable in the market, even if you personally don't sell the item standalone. The expected cost plus a margin approach starts from the other direction: estimate what it actually costs you to deliver the item, then add a margin consistent with what you'd expect a similar item to earn. Neither method requires you to have sold the item before; both require the inputs to be genuinely observable and defensible, not backed into from a desired result.

Which method fits an implementation or professional-services item

A one-time implementation or onboarding service bundled with a SaaS subscription is the most common case where SSP has to be estimated: the SaaS subscription has an observable standalone price, but the implementation work is rarely sold on its own. The expected cost plus margin approach usually fits best here, since implementation work has a knowable internal cost (hours × loaded rate, plus any third-party cost) that a market-assessment approach can't easily substitute for without a comparable vendor to benchmark against.

What documentation actually supports the estimate

Whichever method is used, the estimate needs to be traceable back to real inputs: actual internal cost data for expected-cost-plus-margin, or real comparable market pricing for adjusted market assessment. A number that can't be traced back to something observable — even if it's labeled with the right method name — doesn't meet 606-10-32-33's "all available information" requirement, and it's the first thing a reviewer or auditor will ask to see.

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

Estimating SSP for a never-sold-separately implementation service

A SaaS company sells a $60,000/year subscription (observable SSP: it's sold standalone to other customers) bundled with a mandatory implementation service that has never been sold on its own. The implementation requires 120 hours of internal work at a $150/hour loaded cost, so expected cost is $18,000. Applying the company's standard 40% margin on services work (consistent with what it charges for other billable professional-services engagements) gives an estimated SSP of $18,000 × 1.40 = $25,200.

The contract's total transaction price is a bundled $70,000. Total observable-plus-estimated SSP is $60,000 + $25,200 = $85,200, so the subscription gets 60,000/85,200 = 70.4% of the price ($49,296) and the implementation gets 25,200/85,200 = 29.6% ($20,704). Compare that to a naive 50/50 split of the $70,000 bundle: $35,000 to each. The naive split overstates the implementation obligation's allocated price by nearly $14,300 relative to its actual estimated SSP — which matters because the implementation revenue recognizes over a matter of weeks, while the subscription recognizes ratably over a full year. Overallocating to the fast-recognizing obligation front-loads revenue that the estimate-based method wouldn't support.

Frequently Asked Questions

The estimate should be reassessed periodically and whenever the underlying inputs change materially — updated internal cost data, a shift in typical margin, or new market evidence — rather than fixed once and reused indefinitely. It doesn't need to be recalculated contract-by-contract if the inputs haven't changed.

A small number of standalone sales is still observable evidence and generally takes priority over an estimate — ASC 606-10-32-33's "maximize observable inputs" requirement means you use what real data exists rather than defaulting straight to an estimation method, even if the data set is thin.

No — different obligations in the same contract can use different estimation methods if that better reflects how each one's price would actually be determined. A combination of methods is explicitly contemplated when obligations have different pricing characteristics.

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

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.