Standalone selling price (SSP) is the price at which a company would sell a promised good or service separately to a customer (ASC 606-10-32-32). When a contract includes multiple performance obligations, the transaction price is allocated to each based on relative SSP (ASC 606-10-32-28). When observable prices don’t exist, companies estimate using one of three methods: adjusted market assessment, expected cost plus a margin, or residual. The residual approach is permitted only when SSP is highly variable or uncertain as defined by ASC 606-10-32-34 — not simply when estimation is inconvenient.
Allocation: ASC 606-10-32-28 through 32-30 · Estimation methods: ASC 606-10-32-31 through 32-35 · Discount allocation: ASC 606-10-32-36 through 32-38
SSP allocation sounds mechanical. You figure out what each deliverable would sell for on its own, divide up the contract price proportionally, and move on. But in practice, the complications arrive fast: you can’t observe SSP for most enterprise products, you have three estimation methods but not equal freedom to use them, and there’s a discount allocation rule that’s easy to miss until an auditor raises it.
The guidance here is more rule-driven than in some other parts of ASC 606. Companies still take shortcuts: applying the residual approach when conditions don’t support it, using SSP estimates that haven’t been updated in years, or allocating discounts in ways that shift revenue timing they didn’t intend
The Three Estimation Methods — and Why They’re Not Interchangeable
When you can observe SSP directly, because you regularly sell the product separately at a consistent price: use it. That’s the cleanest case and doesn’t require an estimation method at all. The judgment begins when you can’t observe it directly, which describes most enterprise software and services.
The standard identifies three estimation approaches, each suited to a different situation. The “adjusted market assessment” approach looks at what comparable goods or services sell for in the market, then adjusts your costs and margins, which is most useful when observable competitor or market pricing exists. The “expected cost plus a margin” approach estimates the costs to satisfy the performance obligation and adds an appropriate profit margin; it’s often the most defensible method for professional services and implementation obligations where cost data is available. Both require documented assumptions, but neither has conditions on when they can be used.
The residual approach is different. It calculates SSP as the total contract price minus the sum of observable SSPs of every other performance obligation, what’s left over is the residual SSP. ASC 606-10-32-34 permits it only when SSP is either:
- Highly variable — When the same product sells for a broad range of amounts across customers.
- Uncertain — Where no established price exists and the product has never been sold on a standalone basis.
Both conditions have real meaning. A common error is applying residual to a new product at launch on the grounds that historical data doesn’t exist yet. A published price list is generally strong evidence that SSP is neither highly variable nor uncertain — though facts and circumstances matter and the analysis shouldn’t stop at the price list. “We find SSP hard to estimate” doesn’t satisfy either condition.
How Discounts Get Allocated: The Rule Nobody Reads Twice
When the total transaction price is less than the sum of the SSPs of all performance obligations, there’s a discount. The default rule under ASC 606-10-32-36 is that you allocate that discount proportionately to every performance obligation in the contract. Not to the obligation you think the customer discounted. Not to the line item where the rep applied it in the CRM. To all of them, pro-rata.
There is an exception, but the bar is real. Under ASC 606-10-32-37, you can allocate a discount to one or more (but not all) performance obligations if all three of the following are true:
- You regularly sell each of those performance obligations separately, and you have observable SSPs for each.
- You also regularly sell a bundle of some (but not all) of those performance obligations together — and that bundle has an observable price.
- The discount implied by allocating to just those obligations is substantially the same as the discount embedded in the observable bundle price.
Discount allocation directly affects revenue timing. On a contract that bundles a software license (recognized at point in time) with multi-year support (recognized ratably), whether the discount lands on the license or the support determines how much revenue is front-loaded. The difference can be material, and the choice requires documentation.
Where the pro-rata default surprises people
The intuition most finance teams bring to discount allocation is deal-level: the customer negotiated the discount on the implementation fee, so it belongs there. ASC 606 doesn’t care about negotiation history — it cares about observable pricing. If you can’t meet all three criteria for the exception, the discount spreads across everything. This catches teams off guard on multi-element SaaS contracts where the discount structure is well-understood internally but not observable in the way the standard requires.
Setting SSP When Your Pricing Isn’t Standardized
SSP doesn’t have to be a single point estimate — a range is valid when selling prices vary across customers, if the range is meaningfully bounded. For SaaS companies with tiered pricing, defining SSP bands by customer segment (SMB, mid-market, enterprise) and applying the relevant band is a practical, auditor-friendly approach. This is conceptually similar to what ASC 606-10-10-4 contemplates for portfolios of contracts with similar characteristics. The point is, you don’t need to derive a unique SSP for every individual deal if the contracts share enough characteristics to support a consistent approach.
Heavily negotiated enterprise contracts, where deal economics genuinely vary widely across customers, are the more legitimate candidates for the residual approach. Even there, the analysis is required first: documenting that pricing is genuinely variable across customers, not just that each contract goes through a negotiation process. Those are different things.
When Your Price List Changes — What Happens to Existing Contracts
SSP is established at contract inception and locked for that contract. New contracts after a price change use updated SSPs; existing contracts don’t. There is, however, one situation where the locked allocation gets re-opened: contract modifications.
When a modification occurs:
- Adding seats
- Expanding scop
- Early renewal
- You re-evaluate the remaining performance obligations under ASC 606-10-25-12
A modification treated as a separate new contract allocates the new obligations using current SSPs. One accounted for a modification of the existing arrangement, with a cumulative catch-up adjustment, reallocates remaining transaction price using current SSPs for the remaining obligations. The locked-at-inception rule applies to original allocations; a qualifying modification can reset it. Teams that don’t track modification type carefully end up applying the wrong SSP vintage.
What your system needs to handle
SSP allocation requires the system to capture the SSP assumption at contract inception, apply it consistently across all performance obligations in that contract, and hold that allocation stable through the recognition period. Updated SSP estimates apply to new contracts only — not retroactively to existing ones. If billing and recognition aren’t sharing a data model, SSP updates tend to get applied inconsistently across the portfolio.
Frequently Asked Questions
What is standalone selling price under ASC 606?
SSP is the price at which an entity would sell a promised good or service separately to a customer (ASC 606-10-32-32). It doesn’t have to equal list price — it’s the estimated standalone price, which must be estimated when direct observation isn’t possible.
When can you use the residual approach for SSP?
Only when SSP is highly variable (the same product sells for a broad range of amounts) or uncertain (no established price, never sold standalone), per ASC 606-10-32-34. A published price list — even for a new product — generally means SSP is neither highly variable nor uncertain.
How are discounts allocated across performance obligations?
Proportionately across all POs by default (ASC 606-10-32-36). Allocating a discount to fewer than all POs requires meeting all three criteria in ASC 606-10-32-37: observable SSPs for each PO, an observable bundle price, and a discount substantially equal to what the exception would allocate.
Does a price change affect existing contract allocations?
No. SSP is locked at contract inception for existing contracts. New contracts use updated SSPs. Contract modifications are the exception — depending on modification type, remaining performance obligations may be reallocated using current SSPs.
Can a range of prices be used as SSP?
Yes, when selling prices vary across customers in a way that produces a bounded, defensible range. SaaS companies often segment SSP by customer tier (SMB, mid-market, enterprise) and apply the relevant band per contract. The range still needs documentation — “prices vary” without a defined methodology doesn’t satisfy the estimation requirement.
SSP allocation is a systems problem as much as an accounting one
Getting SSP right at contract inception is the accounting judgment. Keeping it right — consistently applied across contracts, stable through the recognition period, updated for new contracts when estimates change — requires a billing and revenue recognition system that treats SSP as a first-class data element, not a spreadsheet calculation done at period close.
For a deeper dive into how billing data flows into revenue recognition, see the BillingPlatform Revenue Recognition guide.
