Short answer: In a SaaS bundle, each promised good or service is a separate performance obligation if it is distinct: the customer can benefit from it on its own or with readily available resources, and it is separately identifiable from the other promises in the contract. The subscription is usually one obligation, delivered as a series of service periods. Training and standard implementation are often separate. Setup activities that transfer nothing to the customer are not obligations at all.
The answer decides when revenue is recognized. If implementation is a separate obligation, its share of the price is recognized as the work is done. If it is combined with the subscription, that share is spread over the subscription term instead. For a SaaS company selling bundles to mid-market customers, this choice can move a meaningful amount of revenue between quarters.
Why performance obligations matter in a SaaS bundle
Identifying performance obligations is the second of the five steps in ASC 606 and IFRS 15. The IFRS Foundation defines performance obligations as "promises in a contract to transfer to a customer goods or services that are distinct." Every later step depends on this one: the price is allocated to each obligation, and revenue is recognized as each is satisfied.
A typical mid-market SaaS order form might include:
- a 12-month subscription to the platform;
- an implementation or onboarding project;
- a training package for the customer's team;
- a block of professional services hours;
- customer support.
Each line needs a conclusion. Get it wrong and revenue is recognized too early, when bundled services are treated as separate, or too late, when separate services are folded into the subscription. Our guide to ASC 606 revenue recognition in SaaS companies covers the full five-step model.
The two-part test for a distinct good or service
A promised good or service is distinct only if it passes both parts of the test.
- Capable of being distinct. The customer can benefit from the good or service on its own, or together with resources that are readily available to it. A service the vendor or others sell separately usually passes.
- Distinct within the context of the contract. The promise to transfer it is separately identifiable from the other promises. It fails this part if the vendor is integrating the items into a combined output, if one item significantly modifies or customizes another, or if the items are highly interdependent.
The second part does most of the work in SaaS. Nearly any implementation service could benefit a customer on its own. The real question is whether the vendor is promising two things, or one combined result.
Subscriptions and the series guidance
A SaaS subscription is a promise to give the customer access to the platform for a period. Each day or month of access is distinct, but recognizing each separately would add complexity without changing the result.
The series guidance resolves this. When a contract promises a series of distinct services that are substantially the same and transfer to the customer in the same pattern, they are treated as a single performance obligation. A 12-month subscription is therefore one obligation, satisfied over time, usually on a straight-line basis.
The series concept matters again when prices change or vary. It allows a usage fee or a price adjustment to be allocated to the specific period it relates to, rather than spread over the whole term.
Implementation, training and professional services
These are the services where judgment is needed. The table below summarizes the usual conclusions.
| Element | Usually distinct? | Key question | Typical pattern |
|---|
| Subscription | Yes, as one series | Is access the same each period? | Over time, straight-line |
| Standard implementation | Often yes | Could another provider do it? Does it customize the software? | Over time, as work is done |
| Significant customization | Often no | Does it significantly modify the platform for this customer? | Combined with subscription |
| Training | Usually yes | Is the customer able to use the platform without it? | When delivered |
| Professional services | Usually yes | Are they advisory or configuration work, sold separately? | As delivered |
Source: summary prepared for this article; conclusions depend on contract terms.
Implementation is usually the main judgment call. Configuration, data migration and integration set-up that third-party partners also perform, and that do not change the platform itself, usually make implementation distinct. Work that builds custom functionality into the software for one customer usually means implementation and subscription are a single combined obligation.
Training is usually distinct. The platform works without it, and the customer gains knowledge it can apply on its own.
Professional services sold by the hour, such as report design or process advice, are usually distinct and recognized as the hours are delivered.
When setup is not a separate obligation
Many SaaS contracts charge an upfront setup, onboarding or activation fee. The fee does not decide the accounting. What matters is whether the setup activity transfers a good or service to the customer.
Provisioning an account, creating user logins or loading standard templates are usually administrative tasks the vendor must perform to deliver the subscription. They transfer nothing to the customer on their own, so they are not performance obligations. The setup fee is then treated as an advance payment for the subscription and recognized over the subscription term.
Illustrative example: a customer pays a $6,000 activation fee and $60,000 for a 12-month subscription starting January 1, 2026. Activation consists of creating the account and users. The $6,000 is not a separate obligation, so the total of $66,000 is recognized at $5,500 a month. The unrecognized part of the fee sits in deferred revenue until it is earned.
If the fee gives the customer a significant advantage at renewal, for example because renewals carry no further fee, consider whether it creates a material right that extends recognition beyond the first term.
Allocating the price across obligations
Once the obligations are identified, the transaction price is allocated across them. The IFRS Foundation summary states the allocation is made "on the basis of the relative stand-alone selling prices" of each distinct good or service.
Illustrative example: a bundle signed on January 1, 2026 costs $115,000 in total. Stand-alone selling prices are $100,000 for the 12-month subscription, $20,000 for implementation and $5,000 for training, a total of $125,000. The bundle discount is shared in proportion.
| Obligation | Stand-alone selling price | Allocated price | Recognition |
|---|
| Subscription | $100,000 | $92,000 | Straight-line, $7,667 a month |
| Implementation | $20,000 | $18,400 | As the project progresses |
| Training | $5,000 | $4,600 | When the sessions are delivered |
| Total | $125,000 | $115,000 | |
Source: illustrative figures prepared for this article; not customer data.
The invoice may show different line prices from the allocation. Revenue follows the allocated amounts, not the invoice lines, and the difference is managed through deferred revenue and contract assets. The overview of revenue recognition types explains how these patterns combine.
Support and other stand-ready promises
Customer support in a SaaS contract is usually a stand-ready promise delivered over the same period as the subscription. Because it transfers in the same pattern, many companies account for it together with the subscription rather than as a separate line, since the revenue result is the same.
Premium support sold as a separate tier, or support that runs for a different period, should be assessed on its own. Record the conclusion, and keep the stand-alone selling price evidence used. The ASC 606 compliance audit checklist for SaaS lists what auditors usually request.
How ScaleXP supports revenue schedules for SaaS bundles
ScaleXP builds revenue schedules and journals from your invoice data in Xero or QuickBooks, and can use deal data from HubSpot, Salesforce or Pipedrive. Finance decides the performance obligations and the recognition pattern for each product or service. ScaleXP prepares the revenue and deferred revenue journals, and they are posted once finance approves them.
See how revenue schedules and journals are built on the revenue recognition automation for Xero and QuickBooks page.
Conclusion
Each item in a SaaS bundle needs a performance obligation conclusion. The subscription is usually one obligation under the series guidance, standard implementation and training are often separate, significant customization is usually combined with the subscription, and administrative setup is not an obligation. Allocate the price on relative stand-alone selling prices, document each conclusion, and apply it consistently across similar contracts.
Frequently asked questions
Is SaaS implementation a separate performance obligation?
SaaS implementation is often a separate performance obligation when other providers could perform it and it does not significantly customize the software. Configuration and data migration usually meet that test. If implementation builds custom functionality into the platform for one customer, it is usually combined with the subscription and recognized over the subscription term instead.
How should a SaaS setup fee be recognized?
A setup or activation fee is usually recognized over the subscription term, not when it is billed. If the setup work is administrative, such as creating accounts and logins, it transfers nothing to the customer and is not a separate performance obligation. The fee is then an advance payment for the subscription and is held in deferred revenue until earned.
What is the series guidance in ASC 606?
The series guidance treats a run of distinct services that are substantially the same, and that transfer in the same pattern, as a single performance obligation. A SaaS subscription is the common example: each month of access is distinct, but the subscription is accounted for as one obligation satisfied over time. IFRS 15 contains the same concept.
Is customer support a separate performance obligation in SaaS?
Customer support is usually a stand-ready promise delivered over the same period as the subscription. Because it transfers in the same pattern, many SaaS companies account for it together with the subscription, since the revenue result is the same. Premium support sold separately, or support running for a different period, should be assessed as a possible separate obligation.
How is the price allocated across performance obligations?
The transaction price is allocated across performance obligations in proportion to their stand-alone selling prices. If a bundle is sold at a discount, the discount is usually shared across all obligations in the same proportion. Revenue then follows the allocated amounts, which can differ from the prices shown on individual invoice lines.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
