Module 5: Step 4 — Allocate the Transaction Price

1. Why Allocation Matters

Step 4 of the 5-step model answers a deceptively simple question: when you sell a bundle of promises to a customer, how much of the contract price belongs to each promise?

Get this wrong and you front-load or back-load revenue. In SaaS, a common mistake is allocating nearly everything to the software license — recognizing it at contract start — while underallocating to multi-year support obligations. Auditors and the SEC have challenged exactly this pattern repeatedly.

In a $300K bundle of software + implementation + 3-year support, all three are separate obligations (if they passed the Module 3 distinctness test)
Each gets a slice of the $300K based on its standalone selling price (SSP)
Revenue is recognized as each obligation is satisfied — not as cash is collected

Common restatement trigger: Incorrectly bundling implementation (a point-in-time obligation) with the ongoing SaaS license (an over-time obligation) results in recognizing too much revenue at contract inception. The Big 4 flag this as one of the most frequent ASC 606 errors in tech company audits.

2. Standalone Selling Price (SSP): The Foundation

The standalone selling price is the price you would charge for a good or service if you sold it separately to a similar customer under similar circumstances.

Best evidence: An observable price — a list price you actually charge when selling the item standalone. If you sell Platform Plus at $200K/year to enterprise customers who buy it alone, that's your SSP.

Most entities can't observe SSP for every obligation. When direct observation isn't possible, you estimate SSP using one of three methods.

Key principle (ASC 606-10-32-33 / IFRS 15.79): SSP must represent the price the entity would charge — not necessarily what it does charge in bundled arrangements. A significant and consistent discount in bundles does not reduce SSP; instead, the discount gets allocated separately (see Section 6).

Observable vs. Estimated SSP

Type	When it applies	Examples
Observable SSP	You sell the item standalone with consistent, identifiable pricing	List price, standalone transaction data, price book entries
Estimated SSP	Never sold standalone, or pricing is variable/bundled-only	Enterprise implementation services, AI model fine-tuning, bespoke integrations

3. Three SSP Estimation Methods

When you can't directly observe SSP, the standards require you to estimate it. Both IFRS 15 and ASC 606 describe three approaches. You pick the one that best reflects the price you would charge.

Method 1

Adjusted Market Assessment Approach

Look at the market price for comparable goods or services — from competitors or from your own historical standalone transactions — and adjust for entity-specific factors (your cost structure, customer segment, geographic pricing).

How it works: Research what comparable solutions sell for in the market. If a standalone platform license from competitors ranges from $180K–$220K, and your product is at the high end on features, SSP = ~$200K is defensible.

Best for: Products with active markets and observable competitor pricing. Common for SaaS licenses, API access, software seats.

Use when: You have market data (competitor pricing, industry benchmarks) and can adjust for your entity's specific positioning.

Method 2

Expected Cost Plus Margin Approach

Forecast the costs you'll incur to satisfy the obligation, then add an appropriate profit margin consistent with similar contracts or your business margins.

How it works: Implementation services cost you $40K in labor + $5K in infrastructure. Your target gross margin on services is 25%. SSP = $45K ÷ (1 − 0.25) = $60K.

Best for: Services, implementation, professional services, custom development — anything where costs are measurable and margins are consistent. Especially useful when there's no external market data.

Use when: You can reliably estimate the cost to deliver the obligation and have consistent margin expectations for similar services.

Method 3

Residual Approach

Assign the observable SSPs to all other obligations first; whatever's left over is the SSP for the final obligation. It's a "plug" — but it's only permitted in specific circumstances.

Requirements (both must be met):

The SSP is highly variable (the entity sells the same good/service at a wide range of amounts), OR
The SSP is uncertain (the good/service has never been sold separately and is therefore not established in the market)

How it works: Total transaction price = $500K. Observable SSPs: software license $300K + training $75K. The remaining obligation (AI customization never sold standalone) gets residual SSP = $500K − $300K − $75K = $125K.

IFRS 15 vs ASC 606 nuance: Under ASC 606, the residual approach is only valid when the SSP is "highly variable or uncertain." IFRS 15 has similar language but additionally permits a combination of approaches (e.g., residual for one obligation, cost-plus for another). Neither standard permits using the residual approach for two obligations in the same arrangement.

Use when: One obligation has highly variable or uncertain pricing — and you have observable SSPs for all other obligations first.

4. The Relative SSP Allocation Method

This is the primary allocation method under both IFRS 15 and ASC 606. Once you have an SSP for each obligation (observed or estimated), you allocate the transaction price proportionally.

Relative SSP Allocation Formula

Allocated Amount (Obligation X) =
Transaction Price × [SSP(X) ÷ Sum of all SSPs]

Worked Example: SaaS Platform Bundle

TechCorp signs a $240K contract. Three performance obligations:

Platform license — observable SSP: $150K/year (list price)
Implementation services — estimated via cost-plus: $30K
Premium support (Year 1) — estimated via market assessment: $20K

Total SSP: $150K + $30K + $20K = $200K

Allocation:

Obligation	SSP	SSP%	Allocated ($240K)	Recognition timing
Platform license	$150K	75%	$180K	Over 12 months (ratable)
Implementation	$30K	15%	$36K	At completion of implementation
Premium support	$20K	10%	$24K	Over support period

Notice: The customer paid $240K but total SSP is $200K — a $40K discount (20%). The relative SSP method automatically allocates this discount proportionally across all three obligations.

Practical implication: Even though the implementation services only cost $36K to the customer (vs. $30K SSP), the relative SSP method allocates more than the element's standalone price when a bundle discount is spread proportionally. This is correct — the allocation is always based on the SSP ratio, not the contractual price of each line item.

5. Discount Allocation: When to Assign Discounts Specifically

Normally, the relative SSP method spreads any discount across all performance obligations proportionally. But there's an exception: if there's observable evidence that a discount relates entirely to a subset of obligations, you allocate it only to those obligations.

The Exception (ASC 606-10-32-36 / IFRS 15.82)

You can allocate a discount to a specific subset of obligations only when ALL three conditions are met:

You regularly sell each obligation in the subset on a standalone basis
You regularly bundle those obligations together and sell at a discount
The discount you observe when selling the subset matches the total discount in the arrangement

Worked Example: Specific Discount Allocation

SoftwareCo sells a three-element bundle for $150K:

Software license — standalone SSP: $100K
Implementation — standalone SSP: $60K
Hardware — standalone SSP: $40K

Total SSP = $200K. Discount = $50K. BUT: SoftwareCo has observable data showing it regularly sells software + implementation together for $120K (the $160K total minus a $40K discount). The hardware is never discounted.

Under the exception: allocate $150K − $40K (hardware at full SSP) = $110K to software+implementation; then pro-rate between them using their SSPs ($100K:$60K ratio → $68.75K software, $41.25K implementation). Hardware gets full $40K.

Without the exception: The $50K discount would be spread proportionally — software gets $25K off, implementation $15K off, hardware $10K off. With the exception: hardware gets no discount, software/implementation absorb it all. This accelerates relative revenue to hardware and decelerates it to the service elements.

6. Variable Consideration in Allocation

Variable consideration (Module 4) usually gets allocated to all performance obligations proportionally (same SSP ratio). But there are two exceptions where variable consideration is allocated entirely to one obligation:

The variable consideration relates specifically to one obligation — e.g., a usage-based fee tied only to the API access obligation, not to implementation or support
The allocation reflects the amount of consideration the entity expects to receive for satisfying that obligation

SaaS Practical Example

A contract includes: $60K fixed annual SaaS license + variable usage-based charges for API calls (estimated $20K). Implementation services are $15K fixed.

Allocation approach: The variable API charges relate specifically to the API access obligation. Allocate variable consideration entirely to API access. Fixed amounts ($60K + $15K) are allocated using relative SSP between license and implementation.

Why this matters for SaaS: Usage-based AI platforms frequently have a fixed base platform fee plus variable consumption-based fees. The variable portion almost always relates specifically to the usage obligation — making specific allocation the right approach, not proportional allocation.

7. SSP Method Selection: Decision Tree

Use this tree to determine which SSP estimation method to apply for each performance obligation.

SELECTING THE RIGHT SSP ESTIMATION METHOD

Performance Obligation: Need SSP

Is there an observable standalone price
(list price or standalone transaction data)?

YES

Use observable SSP directly
(most reliable evidence)

NO — Must Estimate

Is there active market data or
competitor pricing available?

YES

Method 1: Adjusted Market
Assessment Approach

Can you estimate cost to
deliver with reliable margin?

YES

Method 2: Expected Cost
Plus Margin Approach

Is SSP highly variable or
uncertain? (Never sold standalone,
or very wide pricing range?)

YES

Method 3: Residual Approach
(only if observable SSPs exist
for all other obligations first)

Combine approaches / seek
observable market data.
Document assumptions thoroughly.

8. Real Company Case Studies

CASE STUDY

HubSpot: Bundle Allocation Across Software + Services

HubSpot sells CRM platform subscriptions (Marketing Hub, Sales Hub, Service Hub) bundled with onboarding services and professional services. Under ASC 606, HubSpot identifies each product subscription and significant service deliverable as separate performance obligations.

SSP approach: For subscriptions, HubSpot uses observable SSPs from standalone subscription sales — these have consistent list prices. For onboarding and professional services, they use expected cost-plus-margin since standalone pricing varies by customer complexity.

Revenue impact: The allocation shifts revenue recognition — subscription revenue flows over the subscription term, while onboarding revenue is recognized at completion (point-in-time). A $30K contract with 70% allocated to a 12-month subscription ($21K) and 30% to onboarding ($9K) means $1,750/month subscription recognition + $9K lump sum on go-live.

From HubSpot 10-K: "We allocate the transaction price to each performance obligation based on its relative standalone selling price. SSP is determined by observable prices when they exist and estimated using the cost-plus margin or adjusted market assessment approach when they do not."

CASE STUDY

Adobe: Creative Cloud & Multi-Year License Allocation

Adobe's Creative Cloud bundles access to all Creative applications + cloud storage + Adobe Fonts + updates. For enterprise agreements, customers may also receive onboarding, training, and premium support as part of one negotiated deal.

SSP challenge: Adobe Creative Cloud has never been disaggregated — you can't buy "just Photoshop" at a separate price. For enterprise bundles, Adobe estimates SSP using the adjusted market assessment approach (referencing SMB subscription pricing as a starting benchmark) and the cost-plus approach for training/support.

Residual approach use case: When Adobe signs enterprise "custom enterprise agreements" with bespoke customizations (AI model integration, custom API endpoints), the customization has no observable SSP and highly variable historical pricing. Adobe applies the residual approach — subtract the observable Creative Cloud SSP and support SSP, leaving the residual for the custom development work.

Key takeaway: Even when you can't observe SSP for every element, the residual approach is a valid backstop — as long as you have solid observable or estimated SSPs for all the other obligations first.

9. IFRS 15 vs. ASC 606: Allocation Differences

Topic	IFRS 15	ASC 606
Primary allocation method	Relative SSP — same as ASC 606	Relative SSP — same as IFRS 15
SSP estimation methods listed	Adjusted market assessment, expected cost-plus margin, residual. Permits combining methods.	Same three methods. Also permits combinations.
Residual approach trigger	SSP is highly variable OR uncertain (IFRS 15.79)	SSP is highly variable OR uncertain (ASC 606-10-32-34)
Discount allocation exception	Allowed when observable evidence ties discount to subset (IFRS 15.82)	Allowed on same conditions (ASC 606-10-32-36)
Variable consideration allocation	Allocate to specific obligation if directly related and allocation is consistent with how entity expects to receive (IFRS 15.84–85)	Same principle (ASC 606-10-32-39 to 32-41)
Practical expedient for renewals	No specific expedient; entities apply judgment	Same — no explicit expedient for renewal pricing

Bottom line: IFRS 15 and ASC 606 are substantially converged on Step 4. The primary differences arise in judgment calls around when pricing is "highly variable" and the extent to which you can combine estimation methods. Documentation standards for SSP methodologies are also more thoroughly specified in US GAAP literature.

Flashcard Drill

Click any card to flip it. Work through all 10 before the quiz.

Standalone Selling Price (SSP)

Step 4 foundation

tap to flip ↻

The price at which an entity would sell a promised good or service separately to a customer under similar circumstances. Best evidence = observable price. If not observable, must be estimated.

Relative SSP Allocation

Primary allocation method

tap to flip ↻

Allocate transaction price proportionally to each obligation's SSP. Formula: Allocated Amount = Transaction Price × [SSP(i) ÷ Sum of all SSPs]. Any bundle discount is spread pro-rata across all obligations.

Adjusted Market Assessment Approach

SSP Method 1

tap to flip ↻

Evaluate the market for comparable goods/services (competitor pricing, industry benchmarks) and adjust for entity-specific factors (cost structure, margin, customer segment). Best when active market data exists.

Expected Cost Plus Margin Approach

SSP Method 2

tap to flip ↻

Forecast expected cost to satisfy the obligation, then add an appropriate profit margin consistent with similar contracts. SSP = Cost ÷ (1 − target margin %). Best for services with measurable costs.

Residual Approach

SSP Method 3 — limited use

tap to flip ↻

Subtract observable SSPs of all other obligations from total transaction price; the remainder is the SSP of the final obligation. Only permitted when that obligation's SSP is either highly variable or highly uncertain (never sold standalone).

Residual Approach — Eligibility

When can you use it?

tap to flip ↻

Must meet one of two conditions: (1) Highly variable SSP — entity sells same item across a wide price range with no clear pattern. (2) Uncertain SSP — item has never been sold separately and SSP is not established in the market. Cannot use for two obligations simultaneously.

Discount Allocation Exception

When not to spread discount ratably

tap to flip ↻

If observable evidence shows a discount relates entirely to a specific subset of obligations, allocate the discount only to that subset. All three conditions must hold: regularly sell subset standalone; regularly bundle that subset at a discount; observed discount matches arrangement discount.

Variable Consideration Allocation

When to allocate to a specific obligation

tap to flip ↻

Variable consideration should be allocated entirely to a specific obligation if: (1) it relates specifically to satisfying that obligation, and (2) this allocation is consistent with the amount of consideration the entity expects for satisfying that obligation. E.g., usage-based API fees → API access obligation only.

Observable SSP vs. Estimated SSP

Hierarchy of evidence

tap to flip ↻

Observable SSP (direct standalone sales data) is always preferred over estimated SSP. A significant bundle discount does NOT reduce observable SSP — the discount is allocated separately. If multiple SSP estimation methods give different results, use the one that best represents the price you would charge.

IFRS 15 vs. ASC 606: Allocation

Key differences

tap to flip ↻

Substantially converged. Both use relative SSP as the primary method. Both permit residual approach only for highly variable or uncertain SSPs. Both permit specific discount allocation with observable evidence. IFRS 15 explicitly mentions combining estimation approaches; ASC 606 allows this implicitly. Documentation expectations differ under US GAAP guidance.

Knowledge Check

Three scenario-based questions. Select an answer to reveal the explanation.

Question 1 of 3

A SaaS company signs a $240K contract with three performance obligations: Platform license (observable standalone SSP: $150K), Implementation services (estimated SSP via cost-plus: $30K), and Premium support (estimated SSP via market assessment: $20K). Total SSP = $200K. Using the relative SSP method, how much transaction price is allocated to the Platform license?

A $150,000 — use the observable standalone price directly as the allocated amount

B $180,000 — platform's 75% SSP proportion ($150K / $200K) applied to $240K

C $195,000 — $240K minus implementation ($36K) and support ($9K), leaving the balance for the license

D $80,000 — equal three-way split of $240K

Correct: B — $180,000.

The relative SSP method allocates the transaction price proportionally using SSP percentages — not dollar amounts directly. Platform's SSP share = $150K / $200K = 75%. Allocated amount = 75% × $240K = $180K.

The $240K bundle represents a $40K discount vs. the $200K total SSP. The relative SSP method automatically spreads this discount proportionally: platform gets 75% of the $40K discount = $30K off its SSP, for a net of $180K.

Why A is wrong: SSP is used for the ratio — not as the allocation amount itself. If you simply used SSP amounts as allocations, the three allocations would sum to $200K, not $240K.

Why C is wrong: You cannot allocate by "residual after removing other elements at their allocated amounts" — that circular logic doesn't follow the standard. The formula is always: Transaction Price × [SSP(i) / Sum of SSPs].

Question 2 of 3

An AI company develops a bespoke machine learning model for a client as part of a $500K contract. The contract also includes a 2-year platform license (observable SSP: $300K) and standard training sessions (estimated SSP via cost-plus: $75K). The bespoke ML model has never been sold separately and has no meaningful market comparables. What SSP estimation approach is most appropriate for the ML model, and what is the resulting SSP?

A Adjusted market assessment approach — research competitor ML development pricing; estimated SSP ~$200K

B Expected cost-plus margin approach — forecast ML development cost (~$80K labor) + 40% margin = $133K SSP

C Residual approach — $500K − $300K − $75K = $125K SSP for the ML model

D Equal allocation — $500K / 3 = $167K per obligation

Correct: C — Residual approach, SSP = $125K.

The bespoke ML model qualifies for the residual approach because its SSP is highly uncertain — it has never been sold separately and has no established market price. Both IFRS 15 and ASC 606 permit residual when SSP is uncertain.

Calculation: $500K total − $300K (platform, observable SSP) − $75K (training, estimated via cost-plus) = $125K residual SSP for ML model. Since this is also the allocated amount (one contract, one price), the model gets $125K of revenue recognized as the ML development obligation is satisfied.

Why A is questionable: "Never sold separately" means there's no meaningful external market data to adjust — market assessment would be speculative. The residual approach is explicitly designed for this scenario.

Why B might also be valid: Cost-plus is always an option when you can estimate costs reliably. However, when SSP is "highly uncertain," the residual is the cleanest approach and avoids allocating a discount to the ML obligation artificially. The question specifically flags "no meaningful market comparables" — pointing to the residual.

Question 3 of 3

DataFlow Inc. sells a $180K bundle: Analytics Platform license ($120K SSP), Professional Services implementation ($40K SSP), and Hardware appliance ($60K SSP). Total SSP = $220K. DataFlow has strong evidence that it regularly sells the Analytics Platform + Professional Services bundle together for $140K (a consistent $20K discount vs. their combined SSPs of $160K), and has never offered a discount on hardware. The discount in this contract is $40K. How should DataFlow allocate the $40K discount?

A Spread all $40K proportionally across all three obligations using their SSP ratios (~$21.8K to license, ~$7.3K to services, ~$10.9K to hardware)

B Allocate $20K discount to the platform+services subset (per observable evidence); spread remaining $20K proportionally across all three

C Allocate the full $40K discount only to the Analytics Platform + Professional Services obligations; hardware gets no discount

D Allocate $40K discount entirely to the largest obligation (Analytics Platform) as it has the highest SSP

Correct: A — Proportional allocation across all three obligations.

This is a trap question testing whether you check all three conditions for the specific discount allocation exception. The exception does NOT apply here because condition 3 fails: the observable discount on the Platform+Services subset ($20K) does not match the total arrangement discount ($40K). Since $20K ≠ $40K, you fall back to default proportional allocation.

Proportional allocation (Answer A): Total SSP = $220K. Platform: $120K/$220K × $40K = ~$21.8K off. Services: $40K/$220K × $40K = ~$7.3K off. Hardware: $60K/$220K × $40K = ~$10.9K off. All obligations absorb a share of the discount.

Why C is wrong: Allocating the full $40K only to Platform+Services requires the observable subset discount to match the total discount. DataFlow's regular bundle discount on that subset is $20K, not $40K. The extra $20K of discount is unexplained by the subset data — the exception cannot be used for the full amount.

Key lesson: Condition 3 of the specific discount allocation exception — the observed subset discount must equal the total arrangement discount — is the most commonly overlooked element. When it fails, default proportional allocation applies entirely.