Why Is My Auditor Making Us Defer Revenue on Bundled Contracts? SSP Allocation, Explained

Because your contract bundles multiple performance obligations, and ASC 606 does not let the contract's stated line-item prices decide how much revenue each obligation carries. The transaction price must be allocated on relative standalone selling price (ASC 606-10-32-31 through 32-32), and when your stated prices load value onto the up-front deliverable, the reallocation pushes revenue into the deferred obligations, support, hosting, unspecified upgrades, services. The deferral is not your auditor being difficult; it is the mechanical output of an allocation you haven't controlled. You can preview that output for any deal structure in the ASC 606 wizard.

What is standalone selling price, and why isn't it the contract price?

SSP is the price at which you would sell the good or service separately to a similar customer in similar circumstances, determined at contract inception (ASC 606-10-32-32). The stated contract price is the negotiated output of a bundle; SSP is what the components are worth on their own. They coincide only when your bundled discounting is proportionate across components, which almost never survives a look at actual deal data.

The classic small-cap software pattern: list price says license $500K, year-one support $50K. Renewal invoices show customers actually pay $90K to renew support standalone. Support's SSP is evidenced by the $90K renewals, not the $50K bundled figure, so the allocation moves roughly $40K out of day-one license revenue into ratable support revenue. Multiply across the contract portfolio and you have the deferral your auditor proposed.

How do I establish SSP when I never sell the item separately?

ASC 606-10-32-33 requires you to estimate it, considering all reasonably available information, market conditions, entity-specific factors, customer class, and maximizing observable inputs. ASC 606-10-32-34 sanctions three approaches:

• Adjusted market assessment, what would a customer pay in your market; what do competitors charge, adjusted for your positioning.
• Expected cost plus a margin, build up from forecast fulfillment cost; the workhorse for services and hosting.
• Residual approach, total price minus observable SSPs of the other items. Permitted only when the selling price is highly variable or highly uncertain (32-34(c)). It is not a shortcut for "we don't want to do the analysis," and auditors and the SEC staff both read residual-by-default as a red flag, particularly when it conveniently allocates maximum value to the up-front deliverable.

For items with genuinely variable pricing, a defensible middle path is an SSP range built from historical standalone or renewal transactions (for example, the interquartile range of renewal rates as a percentage of net license fee). Stated prices inside the range get respected; outliers get reallocated.

What does a defensible SSP study actually contain?

Four elements, refreshed at least annually:

1. The population, every standalone and renewal transaction by product, geography, and customer size, pulled from billing data, not memory.
2. The method per obligation, observable where possible; the 32-34 approach and inputs where estimated; the residual justification (highly variable or uncertain pricing, with evidence) in the rare case you use it.
3. The ranges and midpoints, with the stratification logic. One global SSP for a product sold at 60% discounts in EMEA and list in the US will not survive testing.
4. The reallocation math, a worked example showing how a representative bundle allocates, which is also what first-year auditors will reperform.

Skip the study and the auditor builds their own, from your renewal data, on their assumptions, at year-end, under deadline. You will like your version better. The wizard walks the allocation step with your actual deal inputs so the surprise happens in the model, not the audit.

Is there any way to allocate a discount to just one obligation?

Yes, narrowly. ASC 606-10-32-37 permits allocating a discount entirely to one or more (but not all) obligations only when you regularly sell each item standalone, regularly sell a bundle of some of them at a discount, and that bundle discount is substantially the same as the contract's discount and attributable to those specific items. The criteria are conjunctive and evidentiary. The same discipline applies to variable consideration: ASC 606-10-32-40 lets you allocate a variable amount to a single obligation only if the variable terms relate specifically to it and the result is consistent with the allocation objective. Both are documentation-heavy exceptions, not planning tools.

FAQ

Can we just use the prices stated in the contract?

Only if they equal SSP, meaning your standalone and renewal data proves each stated price is what that item sells for separately (ASC 606-10-32-32). Uneven bundle discounting breaks this immediately.

How often must SSP be reassessed?

SSP is set per contract at inception and not reallocated afterward for that contract (ASC 606-10-32-43 addresses later changes in price), but your SSP evidence should be refreshed periodically, annually is the common cadence, so new contracts allocate on current data.

When is the residual approach allowed?

Only when an item's selling price is highly variable or highly uncertain (ASC 606-10-32-34(c)), and only after establishing observable SSPs for the other items. Using it as a default for your flagship product invites a comment letter.

Does a bigger deferral hurt earnings permanently?

No, it retimes revenue. The deferred amounts recognize ratably or on delivery of the related obligation. The permanent damage comes from doing it wrong first and restating later.