The Residual Approach Under ASC 606-10-32-34: When You're Actually Allowed to Use It
Step 4 of ASC 606 allocates the transaction price across performance obligations in proportion to their standalone selling prices (SSPs). Simple — until one item in the bundle has no reliable SSP at all. The residual approach in ASC 606-10-32-34(c) exists for exactly that situation, and it is the most misused tool in Step 4: it looks like a shortcut ("total price minus the known pieces"), but the standard only opens the door in two narrow situations, and it adds a sanity check on the way out. Here is the full rule.
The setting: three ways to estimate an unobservable SSP
The best evidence of SSP is an observable price — what the entity actually charges for that good or service sold separately to similar customers (ASC 606-10-32-32). When there isn't one, ASC 606-10-32-34 offers three estimation methods:
- Adjusted market assessment — what would the market bear? Start from competitor pricing and adjust for the entity's own costs and positioning.
- Expected cost plus a margin — build the price from forecast costs and an appropriate margin.
- Residual approach — total transaction price minus the sum of the observable SSPs of the other promises; the remainder is the estimate. Permitted only in the two cases below.
The two gates in 606-10-32-34(c)
The residual approach may be used only if at least one of these holds:
- Highly variable pricing: the entity sells the same good or service to different customers, at or near the same time, for a broad range of amounts — the pricing history exists but is so scattered that no single number is representative. The textbook case is a software license sold at anywhere from a few hundred to many thousands of dollars depending on the deal.
- Uncertain pricing: the entity has not yet established a price for the item and it has never been sold on a standalone basis — a genuinely new offering with no track record.
Note what is not on the list: "estimating is hard," "we lack the data," or "the residual is easier." Inconvenience never qualifies. And the approach only functions at all when the other items in the bundle have observable SSPs to subtract — a residual of unknowns from unknowns is meaningless.
Worked example
SoftCo sells a bundle for $1,000: a perpetual software license plus one year of technical support. Support renews every year at a consistent, observable $200. The license, sold alone, has gone for anything between $600 and $2,400 depending on customer size and negotiation — same product, same period, broad range. That is textbook "highly variable": gate one is open.
- Transaction price: $1,000
- Less observable SSP of support: $200
- Residual SSP of the license: $800
Allocation: $800 to the license (recognized when control of the license transfers) and $200 to support (recognized over the support year). The $800 also passes the reasonableness look-back — it sits comfortably inside the observed $600–$2,400 range.
The guardrail: the allocation objective still rules
Meeting a gate is necessary but not sufficient. The result must still satisfy the overall allocation objective of ASC 606-10-32-28 — each obligation gets an amount depicting the consideration the entity expects for that promise. Two failure modes:
- A zero or trivial residual. If SoftCo's bundle price were $210, the residual would say the license is worth $10 — absurd for a product that has sold for $600+. A residual of approximately zero (or negative) is presumptive evidence the approach doesn't produce a faithful answer here, and another method must be used.
- A residual outside observable evidence. Even a positive, non-trivial residual fails if it lands outside the range of reasonable prices the entity's own history supports.
When the residual flunks its own sanity check, fall back to adjusted market assessment or cost-plus-margin — and when a bundle contains two or more items with unknown SSPs, ASC 606-10-32-35 permits combining methods: use the residual to price the unknowns as a group, then split that group using another technique.
Exam checklist
- Observable price first — estimation methods only when no observable SSP exists.
- Residual requires highly variable or not-yet-established pricing — quote the gate you're relying on.
- Every other obligation in the computation needs an observable SSP.
- Check the output: near-zero, negative, or out-of-range residuals mean the method fails the allocation objective.
- This is a Step 4 question — it changes how much revenue each obligation carries, never when each obligation recognizes it.
Practice the allocations: the ASC 606 revenue question bank drills SSP estimation, discount allocation, and the rest of Step 4 with worked explanations.
This page is educational material for exam practice and general understanding, not professional accounting advice — engage a qualified accountant for real transactions.
Source: FASB Accounting Standards Codification, ASC 606-10-32-28 (allocation objective), ASC 606-10-32-31 through 32-35 (standalone selling prices and estimation methods).