Two Performance Obligations, a Delivery Bonus, and a Constrained Estimate
On January 1, Year 1, Halden Systems enters a $1,200,000 contract to deliver a server cluster, install it in the customer's data hall, and provide three years of post-installation support. Installation requires significant customization of the cluster's firmware, and the customer cannot benefit from the cluster or the installation on its own; Halden has never sold installation separately. Standalone selling prices are $600,000 for the cluster, $200,000 for the installation, and $200,000 for the support. Halden will earn a $100,000 bonus if the cluster achieves go-live by March 31, Year 1; based on similar projects and its limited control over the customer's site readiness, Halden concludes that only $40,000 is not subject to significant reversal. The customer prepaid $500,000 at signing.
1. Identify the performance obligations in the contract and explain the reasoning for each conclusion.
Read the worked answer
Two performance obligations.
1. Cluster plus installation - a single combined performance obligation. Installation is not distinct because the two criteria in ASC 606-10-25-21 are not both met:
- The customer cannot benefit from the cluster without the firmware customization and cannot benefit from installation without the cluster (criterion (a) fails).
- Within the contract, the installation significantly affects and customizes the cluster; the combined output is what the customer contracted for (criterion (b) fails). Because the good and service are highly interdependent, they are combined and treated as one performance obligation.
2. Post-installation support - a distinct service. The customer can benefit from the support together with the cluster, which is a readily available resource, and the support does not significantly modify or customize the cluster. It is separately identifiable in the contract and is a standstill/stand-ready service recognized over time.
The fact that installation has never been sold separately does not by itself preclude a distinct-unit-of-account conclusion, but here the integration analysis drives the answer, not the absence of a standalone price.
2. Determine the transaction price, including how the $100,000 bonus is constrained, and identify the triggers for remeasurement.
Read the worked answer
Transaction price = $1,200,000 fixed + $40,000 variable = $1,240,000.
Why only $40,000 of the bonus is included. Variable consideration is included only to the extent it is highly probable that a significant reversal will not occur when the uncertainty resolves (ASC 606-10-32-11). Factors pointing to a heavy constraint here:
- The amount is highly susceptible to factors outside Halden's influence - go-live depends on the customer's site readiness and third-party contractors.
- The uncertainty will not resolve for several months, and the experience with similar projects is limited.
- The contract has a large number of possible consideration amounts relative to the single fixed price.
- A single, binary milestone means a miss produces a full reversal of any amount recognized. Halden's expected-value or most-likely-amount analysis would be updated to $40,000.
Remeasurement. Reassess the estimate at each reporting date and on changes in circumstances. A change in the transaction price is allocated to the performance obligations and recognized on a cumulative-catch-up basis for already-satisfied obligations; the catch-up is recognized in the period of the change as an adjustment to revenue (a change in estimate, not a prior-period error). If the bonus becomes highly probable of being earned, the additional amount is recognized; if it becomes probable of reversal, previously recognized amounts are reversed.
3. Allocate the transaction price and explain how the $500,000 prepayment and the variable consideration are presented.
Read the worked answer
Allocation - apply ASC 606-10-32-36A to the bonus first. The $40,000 of variable consideration relates specifically to Halden's effort to satisfy the combined cluster-and-installation obligation (the go-live date is a milestone on that obligation) and is consistent with the allocation objective. It is therefore allocated entirely to that obligation rather than pro rata.
Fixed consideration of $1,200,000 allocated on relative standalone selling prices:
- Combined cluster/installation SSP: $600,000 + $200,000 = $800,000 (80%)
- Support SSP: $200,000 (20%)
- Total SSP: $1,000,000
- Combined obligation: $1,200,000 x 80% = $960,000, plus the $40,000 variable = $1,000,000
- Support: $1,200,000 x 20% = $240,000
- Check: $1,000,000 + $240,000 = $1,240,000.
The absence of an observable discount tied to a specific obligation means the 20% relative discount is allocated proportionately across the fixed consideration.
Presentation and timing.
- Support revenue is recognized ratably over three years at roughly $80,000 per year.
- Combined obligation revenue is recognized at the point in time when control of the installed cluster transfers (completion of installation, generally go-live). Given the March 31 milestone, most of the $1,000,000 is likely recognized in the first quarter.
- At signing, no performance has occurred, so the $500,000 prepayment is a contract liability (not revenue, not a receivable). If Halden performed before billing, the net position would be a contract asset. A contract asset is never presented net against a contract liability arising from a different contract; they are offset only for the same contract.