Transaction price allocation for SaaS performance obligations

Short answer: Under ASC 606 and IFRS 15, a SaaS company allocates the transaction price to each performance obligation in proportion to its standalone selling price (SSP), the price at which the company would sell that promise separately to a customer. A bundle discount is spread across the obligations in the same proportion, unless observable evidence meets three specific conditions that tie it to only some of them.

For a finance team selling subscriptions with implementation, training or premium support, allocation decides how much revenue lands in each month. Getting SSP wrong does not change the contract total, but it moves revenue between periods, and auditors test the method as well as the arithmetic.

Where allocation sits in the five-step model

Allocation is the fourth of the five steps that IFRS 15 and ASC 606 share. The IFRS Foundation summary of IFRS 15 lists them as: identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price to the performance obligations, and recognize revenue when each obligation is satisfied. The objective of step four (ASC 606-10-32-28, IFRS 15 paragraph 73) is to allocate an amount to each obligation that depicts the consideration the company expects to be entitled to for transferring it.

Allocation matters once a contract contains more than one performance obligation. A plain monthly subscription with nothing else attached has one obligation, so the whole price is recognized over the subscription term. Once a contract adds a distinct implementation service, a training package or a premium support tier with its own timing, the price has to be divided, because each piece is recognized on its own pattern. Our guides to ASC 606 revenue recognition in SaaS companies, IFRS 15 for SaaS and performance obligations in a SaaS bundle cover the earlier steps in more detail.

What standalone selling price means for a SaaS contract

Standalone selling price is the price at which the company would sell a promised good or service separately to a customer. The IFRS Foundation summary describes the allocation as based on "the relative stand-alone selling prices" of each distinct good or service. SSP is determined at contract inception (ASC 606-10-32-31, IFRS 15 paragraph 76), and it is a company-level estimate, not the number printed on one customer's order form.

That distinction matters in SaaS, where list prices are often a starting point for negotiation. The standards say a contractually stated price or a list price may be the SSP but is not presumed to be (ASC 606-10-32-32, IFRS 15 paragraph 77). If sales teams regularly discount the subscription by 15% to 30%, the list price is not the SSP. The SSP is the price the company actually achieves when it sells that subscription on its own, to similar customers, in similar circumstances.

How to determine standalone selling price: observable prices first, then estimates

The best evidence of SSP is an observable price. Only when that does not exist does the company estimate, using methods that maximize observable inputs and are applied consistently in similar circumstances (ASC 606-10-32-33, IFRS 15 paragraph 78). The standards name three suitable estimation methods and say the list is not exhaustive.

Observable price

The best evidence is the price the company charges when it sells the same item separately to similar customers. For a subscription sold on its own to many customers, a finance team can analyze the range of achieved prices and use a point within a narrow band, often the median. Deloitte's revenue roadmap describes one practice: a range that covers more than half of the relevant transactions and extends no more than 20% either side of its midpoint.

Adjusted market assessment

The company evaluates the market in which it sells and estimates the price a customer in that market would pay, which can include competitors' prices for similar services adjusted for the company's own costs and margins. This method suits a new add-on module before it has a sales history.

Expected cost plus a margin

The company forecasts the cost of satisfying the obligation and adds an appropriate margin. It suits services with measurable delivery costs, such as implementation or onboarding work delivered by an internal team, where hours and salary costs are tracked.

Residual approach

The residual approach takes the total transaction price, subtracts the observable SSPs of the other promises in the contract, and assigns what is left to the remaining one. It is permitted only when the SSP of that item is highly variable (the company sells it to different customers, at or near the same time, for a broad range of amounts) or uncertain (the company has not yet set a price and the item has not been sold on a standalone basis). It needs at least one other obligation with an observable SSP, and it cannot be chosen because it is convenient. If it allocates nil or very little to a distinct promise, the result indicates the approach is not appropriate for that contract.

When two or more items have highly variable or uncertain SSPs, a combination of methods may be needed: for example, the residual approach to estimate the total for those items as a group, then another method to split that total between them (ASC 606-10-32-35, IFRS 15 paragraph 80).

How to allocate a bundle discount

A discount exists when the sum of the SSPs exceeds the promised consideration. The default rule is to allocate the discount proportionately across the performance obligations in the contract, which is exactly what the relative SSP calculation does (ASC 606-10-32-36, IFRS 15 paragraph 81).

The standards allow the whole discount to be allocated to one or more, but not all, obligations only when all three of these conditions are met (ASC 606-10-32-37, IFRS 15 paragraph 82):

• the company regularly sells each distinct good or service (or each bundle) in the contract on a standalone basis;
• it also regularly sells a bundle of some of those items on a standalone basis at a discount to their SSPs; and
• the discount on that bundle is substantially the same as the discount in the contract, and analysis of the bundle provides observable evidence of the obligations to which the entire discount belongs.

When a discount is allocated this way, it is allocated before the residual approach is used to estimate any SSP (ASC 606-10-32-38, IFRS 15 paragraph 83). Few SaaS companies hold enough standalone and bundle sales data to meet the three conditions, so most apply the proportionate approach.

How to allocate variable consideration such as usage fees

Variable consideration can relate to the whole contract or to a specific part of it. A variable amount is allocated entirely to one performance obligation, or to one distinct period within a series such as a month of service, when both conditions are met: its terms relate specifically to the company's efforts to satisfy that obligation or transfer that period's service, and the result is consistent with the allocation objective across the whole contract (ASC 606-10-32-39 and 32-40, IFRS 15 paragraphs 84 and 85). The rest of the transaction price is then allocated on the relative SSP basis (ASC 606-10-32-41, IFRS 15 paragraph 86).

In SaaS, the common case is an overage fee. If a customer pays $0.02 for each API call above a monthly allowance that resets each month, the fee for March relates to March's service, so it is generally allocated to March rather than spread across the subscription, implementation and support. An annual allowance that does not reset gives a different answer, as Deloitte's roadmap examples show. Our guides to usage-based billing and variable consideration, discounts and credits cover estimation and the constraint.

Worked example: allocating a $136,000 SaaS bundle

Illustrative example: on January 1, 2026, a customer signs a noncancellable 12-month contract for $136,000, invoiced in full on signing with payment due in 30 days. It covers a platform subscription, an implementation service that the company has assessed as distinct, and a premium support tier. The table below shows each SSP, its basis and the relative allocation.

Source: illustrative figures, not customer data.

The $34,000 discount is 20% of the combined SSP, so each obligation receives 80% of its SSP. Implementation uses 50% of its budgeted hours in January, 30% in February and 20% in March, so its $16,000 is recognized as $8,000, $4,800 and $3,200.

Order-form prices versus relative SSP

Suppose the order form shows the subscription at $110,000, implementation at $10,000 and support at $16,000. The total is the same, but the first quarter is not, as the table below shows.

Source: illustrative figures, not customer data.

Using the order-form prices would understate first-quarter revenue by $4,500 and overstate the remaining nine months by the same amount. The order form decides what is billed; the SSP allocation decides what is recognized.

The journals for the first quarter

Because the contract is noncancellable and invoiced, the company records a receivable and a matching contract liability (deferred revenue) on January 1, then releases revenue at each month-end.

Source: illustrative figures, not customer data.

At March 31, deferred revenue is $90,000: nine months of subscription and support at $10,000 a month, released from April to December. If implementation were not distinct, there would be no separate allocation: the fee would be combined with the subscription and recognized over the service period. The question of distinctness comes first, and we cover it in our guides to revenue recognition types and implementation and onboarding fees.

Common allocation mistakes in SaaS

• Using list price as SSP. If deals are routinely discounted, list price overstates SSP and the allocation tilts toward items that are priced generously on paper.
• Allocating the whole discount to services. Pushing the discount onto implementation makes subscription revenue look stable, but it needs the three conditions described above.
• Using the invoice schedule as the allocation. Billing $40,000 upfront for implementation does not make $40,000 the implementation revenue. Billing and revenue are separate; the difference sits in deferred revenue or a contract asset.
• Treating the residual approach as a default. It is restricted to highly variable or uncertain prices, and a nil or near-nil residual needs another method.
• Not refreshing the SSP study. Price increases, new packaging and new segments change achieved prices. An updated study applies to new contracts; the price of a contract already signed is not reallocated because SSPs change after inception (ASC 606-10-32-43, IFRS 15 paragraph 88).

What auditors look for in an SSP policy

An auditor reviewing allocation usually asks three questions: what method was used for each obligation, what data supports it, and how often it is refreshed. A short SSP memo that answers those questions, with the analysis of achieved prices attached, covers most of the work. For any item on the residual approach, the memo should show why the price is highly variable or uncertain. Our ASC 606 audit checklist for SaaS lists the other documents to have ready.

How ScaleXP supports SSP allocation and revenue schedules

Once finance has set the standalone selling price for each element, the remaining work is recognizing each allocated amount on its own pattern, month after month, and keeping deferred revenue reconciled to the ledger. For bundles and multi-element contracts, ScaleXP allocates the price across the elements by standalone selling price (SSP), and each element of a multi-element contract gets its own schedule.

Schedules are built from your Xero or QuickBooks invoices, and ScaleXP uses AI to read service start and end dates from the wording on Xero and QuickBooks invoices. Contract dates can also come from the CRM deal in HubSpot, Salesforce or Pipedrive. ScaleXP can spread revenue by day or by whole month. ScaleXP prepares the schedules and journals, and they are posted once finance approves them. Every journal includes a full audit trail, downloadable as a spreadsheet.

You can see how the schedules and journals work on the revenue recognition automation for Xero and QuickBooks page.

Conclusion

Allocating the transaction price comes down to a defensible SSP for each performance obligation and a proportionate split of the contract price. Use observable prices where you have them, estimate with a documented method where you do not, keep the residual approach for genuinely variable or uncertain prices, and allocate discounts proportionately unless all three conditions for a targeted allocation are met. Then recognize each allocated amount on its own pattern, as the journals above show, and keep the SSP study current for new contracts.

Frequently asked questions

Sources (checked October 26, 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers; FASB ASC 606-10-32-28 to 32-43 as reproduced in Deloitte's Roadmap: 7.3 Determine the stand-alone selling price, 7.4 Allocation of a discount, 7.5 Allocation of variable consideration and 7.6 Changes in the transaction price; PwC Viewpoint, Revenue guide 5.3, Estimating a standalone selling price.