Is SaaS training a separate performance obligation?

Training is one of the most common items in a SaaS order form and one of the least documented. Whether it is a separate performance obligation decides how much of the contract price is recognised when a session is delivered, and how much stays in the subscription. This post covers the distinct test, recognition timing, SSP evidence and the questions auditors ask, with a $72,000, 24-month contract run through the Soluqube engine. For the full Step 4 picture, see our ASC 606 SSP allocation guide, which explains how SSP allocation works across a bundle. Key terms: performance obligation, distinct good or service and standalone selling price.

When is training distinct?

Training is distinct when two tests are met under ASC 606-10-25-19. The customer can benefit from it, with the software or with readily available resources, and it is separately identifiable from the subscription. Standard admin or user training usually passes both. Training that is part of a significant customisation of the software usually does not.

The second test is where judgement sits. ASC 606-10-25-21 asks whether the vendor is integrating the training with the software into a combined output, whether the training significantly modifies the software, and whether the two are highly interdependent. Training on how to use a product as it is sold rarely meets any of these. Signs that training is distinct include:

1. The vendor or third parties sell the same training on its own.
2. The customer can use the software without it.
3. The training does not change the software's code or configuration.

Is training recognised at a point in time or over time?

Training is a service, so it is recognised as it is delivered. A live session delivered on one day is in practice recognised on that day, which looks like point-in-time recognition. A programme of sessions over several months is recognised over time as each session is delivered, using an input or output measure of progress.

What matters is the delivery date, not the invoice date or the contract start. If training is billed upfront but delivered in month four, its revenue stays deferred until month four. See point-in-time recognition and ratable recognition for how each pattern behaves in a schedule.

How do you estimate SSP for training?

Use an observable price first: the price at which the company sells the same training on its own, such as a published day rate. If there is none, estimate it with expected cost plus margin, built from trainer days, preparation time and a margin consistent with other services.

A list price that is always discounted is weak evidence. A day rate actually charged on standalone training orders is strong evidence. Keep the source of each SSP in the workpaper next to the figure, so the reviewer can trace it without asking.

How is a $72,000 contract with two trainings allocated?

Take a $72,000.00, 24-month contract starting February 2027, with a subscription, live admin training in month 1 and a train-the-trainer workshop in month 4. Their SSPs total $72,400.00, so the $400.00 discount is spread pro rata. The allocations are $63,646.41, $4,773.48 and $3,580.11, which tie to $72,000.00.

The workshop takes what is left: $72,000.00 − $63,646.41 − $4,773.48 = $3,580.11.

The subscription recognises $2,651.93 for 23 months and $2,652.02 in month 24, so the final month absorbs $0.09 (terminal-period remainder absorption). Total recognised is $72,000.00. The engine result's SHA-256 hash is f6c0569d8f32cec97b8ab2e5c6fcc9c4702c63a04b781d65f67c315553d836ff. This schedule is engine behaviour: the app's upload workbook gives the same allocation but puts every point-in-time item in month 1. You can re-perform the allocation in the SSP allocation calculator.

What do auditors ask about training?

Auditors ask four things: why the training is distinct, where its SSP comes from, when it was actually delivered, and what happens to training the customer has not used. The answers belong in the workpaper before fieldwork, with the contract clause and delivery evidence attached to each training line.

In practice that means:

1. The distinct assessment, citing the clause that describes the training.
2. The SSP source: standalone orders, a day rate or a cost build.
3. Delivery evidence, such as attendance records or a customer sign-off, dated within the period.
4. Cutoff: training delivered just after period end stays deferred.
5. Expiry terms for unused training, and whether breakage applies.

For a related service line, our post on allocating SSP to subscription and implementation shows the same workpaper structure. The sample SSP workpaper shows it as a finished document.

How can you test this on your own contracts?

Send us three of your hardest bundled contracts through the design partner programme, and you get a free 3-contract workpaper. You confirm the obligations and stated prices. We send back the relative SSP allocation, a schedule that ties to the cent, clause evidence for each obligation, and a hashed export.

Founding prices for the first 10 customers are available on pricing. The engine doesn't model contract modifications, variable consideration, breakage estimates or billing schedules yet, so treat those topics as guidance only.