How do you allocate revenue across multiple performance obligations in a single contract?
CFA Level II has deeper revenue recognition scenarios than Level I. I'm struggling with contracts that bundle software licenses, implementation services, and ongoing support into a single price. How do you identify separate performance obligations and allocate the transaction price when standalone prices aren't directly observable?
Multiple performance obligation contracts are common in technology, real estate, and telecom. IFRS 15 / ASC 606 requires identifying each distinct obligation and allocating the total price based on relative standalone selling prices (SSPs).
Step 1 — Identify Performance Obligations:
A promised good or service is a separate performance obligation if:
- The customer can benefit from it on its own or with readily available resources (capable of being distinct)
- It is separately identifiable from other promises in the contract (distinct within the contract)
Example: Nexbridge Technologies signs a $2,400,000 contract with Aldermere Healthcare:
- Perpetual software license
- 6-month implementation/customization
- 2-year post-implementation support
Are these distinct? The software has standalone functionality (sold separately to other clients). Implementation is highly specialized but could be performed by a third party. Support is a standard offering. All three are distinct obligations.
However, if the customization is so intertwined that it significantly modifies the software, the license and implementation might be combined into one obligation.
Step 2 — Determine Standalone Selling Prices:
| Obligation | Observable SSP? | Method | SSP |
|---|---|---|---|
| Software license | Yes — sold separately | Direct | $1,500,000 |
| Implementation | No | Adjusted market assessment | $600,000 |
| Support | Yes — renewal price | Direct | $900,000 |
| Total SSPs | $3,000,000 |
When SSP is not directly observable, use:
- Adjusted market assessment: Estimate what the market would pay
- Expected cost plus margin: Total expected costs plus a reasonable margin
- Residual approach: Only when SSP is highly variable or uncertain
Step 3 — Allocate Transaction Price:
Allocate based on relative SSPs:
- License: ($1,500,000 / $3,000,000) x $2,400,000 = $1,200,000
- Implementation: ($600,000 / $3,000,000) x $2,400,000 = $480,000
- Support: ($900,000 / $3,000,000) x $2,400,000 = $720,000
Step 4 — Recognize Revenue:
- License: At a point in time (when control transfers, likely at delivery)
- Implementation: Over time using input method (costs incurred / total estimated costs) over 6 months
- Support: Over time, straight-line over 24 months ($30,000/month)
Analyst Considerations:
- Companies with more bundled contracts have more judgment in SSP estimation — potential for manipulation
- Watch for changes in SSP estimates that shift revenue between periods
- Compare revenue recognition patterns across competitors for consistency
For bundled contract analysis practice, check our CFA Level II FRA course.
Master Level II with our CFA Course
107 lessons · 200+ hours· Expert instruction
Related Questions
What exactly is the Capital Market Expectations (CME) framework and why does it matter for asset allocation?
How do business cycle phases affect asset class return expectations?
Can someone explain the Grinold–Kroner model step by step with numbers?
How do you forecast fixed-income returns using the building-blocks approach?
PPP vs Interest Rate Parity for forecasting exchange rates — when do I use which?
Join the Discussion
Ask questions and get expert answers.