Most companies get SSP allocation right the first time. They set up their methodology at implementation, document the assumptions, and move on. The problem is what happens next: pricing changes, new products launch, discounts become routine, and nobody goes back to check whether the original SSP framework still holds. Auditors do.
The failures in SSP allocation aren't usually conceptual — most finance teams understand the relative SSP principle. They're methodological: the wrong estimation approach applied to the wrong situation, stale estimates applied to new contracts, and discount allocation rules that got simplified into something the standard doesn't actually permit.
Using the Residual Approach When Conditions Aren't Met
The residual approach is mathematically convenient. Instead of estimating SSP for every performance obligation, you observe SSP for the easy ones and assign the remainder to the hard one. It's tempting, especially for enterprise software where platform licenses are genuinely hard to price on a standalone basis.
ASC 606-10-32-34 permits the residual approach only in two specific situations: SSP is highly variable — the same product sells for a wide range of amounts across customers — or SSP is uncertain — the product has never been sold on a standalone basis and no established price exists. Both require a documented facts-and-circumstances analysis, and the threshold is higher than most teams assume.
A published price list is relevant evidence, but it doesn't automatically resolve the question — the broader facts and circumstances still govern. What matters is whether prices are genuinely variable across customers, not just negotiated. "We negotiate prices individually" isn't a sufficient basis for claiming high variability; documentation of actual price dispersion across customers is. Companies that use residual as a default because it's easier to apply are creating audit exposure that will eventually surface.
Letting SSP Estimates Go Stale
SSP is determined at contract inception and locked for that contract. When SSP estimates are updated, they apply to new contracts only — they don't retroactively change the allocation on existing contracts. That's the rule, and most finance teams know it.
What gets missed is the discipline around when to update. Companies often set SSP at implementation and revisit it infrequently. In the meantime, pricing shifts, product mix changes, and estimates that were defensible three years ago are describing a product and market that no longer exist.
A reasonable practice: review SSP estimates annually, document the review, and update for new contracts when market conditions or pricing economics have moved materially. That means you can defend current contracts with current analysis rather than explaining why you're still using 2021 market data.
Misapplying the Discount Allocation Rule
When a contract is priced at a discount to the sum of individual SSPs, ASC 606 defaults to allocating that discount proportionately across all performance obligations. There's an exception — but it has three conditions that must all be satisfied simultaneously.
A company can allocate a discount to only some performance obligations if: (1) it regularly sells each of those POs at observable standalone prices, (2) it regularly sells a bundle of those POs at a discount, and (3) the discount attributable to the bundle is substantially equal to the discount in the contract being evaluated. All three must be met at the same time. If any one condition fails, the discount goes pro-rata — there is no partial exception.
In practice, the exception gets misapplied when companies want to allocate discounts away from software licenses and toward services — usually to accelerate revenue on the license portion. Unless the company actually sells the relevant bundle at a consistent discount and can document all three criteria, the pro-rata default applies. Allocating a discount to specific POs to achieve a preferred revenue pattern without satisfying all three conditions is a misstatement.
Treating SSP Updates as Modifications
A change in your SSP estimate is a change in your internal model — not a change in contract terms, and not a contract modification. This distinction matters because the two have completely different accounting consequences.
When SSP estimates change, finance teams sometimes treat the revision as a triggering event and update allocations on existing contracts. It isn't a triggering event. The allocation established at contract inception governs the existing contract until there's an actual modification to the contract terms — a change initiated by the parties, not a change in your analysis of market data.
The practical consequence: if you've been applying a residual SSP to a multi-year contract and your estimate has since changed, the existing contract keeps its original allocation. Updated SSP applies when you enter a new contract or when an actual modification triggers reallocation under the applicable modification scenario. Updating existing contract allocations based on SSP estimate changes is a process error, not a correction.
The common thread across all four of these issues is documentation discipline. SSP methodology, estimation assumptions, and discount allocation rationale need to be established at contract inception, reviewed on a schedule, and traceable when auditors ask. The companies that handle SSP well aren't doing more complex analysis — they're doing the same analysis consistently and keeping the records to show it. Pull your SSP documentation and ask whether it could withstand a detailed auditor review today. That's usually a useful diagnostic.
Frequently Asked Questions
When is the residual approach for SSP permitted?
Only when SSP is highly variable across customers (not just negotiated individually) or genuinely uncertain because the product has never been sold separately. The conditions require documentation of actual price dispersion, not just a statement that pricing is flexible. A published list price is evidence that SSP may not meet the residual conditions, though the full facts still govern.
How often should SSP estimates be reviewed?
Annually at minimum, with updates applied to new contracts. The review should be documented so you can show current analysis supports current contracts. Three-year-old SSP estimates applied to contracts signed today are a common audit finding, particularly when pricing economics have shifted materially since the original estimate.
What happens when a discount can't be allocated to specific performance obligations?
It goes pro-rata across all performance obligations by default. The exception under ASC 606-10-32-37 requires three conditions simultaneously: observable SSP for each PO, an observable bundle price for the relevant subset, and the discount substantially matching that bundle. All three have to hold at the same time. One failure means pro-rata applies.
Does updating SSP estimates trigger reallocations on existing contracts?
No. SSP is locked at contract inception for existing contracts. An updated estimate applies to new contracts from that point forward. Reallocating existing contracts based on updated SSP estimates, without an actual contract modification, is a process error.
What's the most common SSP audit finding?
Using the residual approach without meeting the conditions. The second most common is applying it as a default because it's easier, which auditors recognize immediately. Document the facts-and-circumstances analysis that supports whichever method you use, particularly for new products or enterprise licenses where SSP is genuinely difficult to establish.
