FA-301i · Module 1

Performance Obligations in SaaS

3 min read

The most common ASC 606 error in SaaS is misidentifying performance obligations. Is implementation a separate obligation or part of the subscription? Is premium support distinct from the platform? Is a free trial period a performance obligation? The answer depends on whether each element is "capable of being distinct" (the customer could benefit from it on its own) and "distinct within the context of the contract" (it is not highly interrelated with other elements). These are judgment calls — and they determine the timing of revenue recognition.

Common SaaS Performance Obligations:
──────────────────────────────────────────────────────
Element          Distinct?  Recognition   Timing
──────────────────────────────────────────────────────
SaaS subscription  Yes     Over time     Ratably over
                                         contract term

Standard setup     Maybe   Depends       If not distinct:
                                         combined with
                                         subscription

Custom implement.  Yes     Point in      Upon completion
                           time          and acceptance

Training           Yes     Point in      Upon delivery
                           time

Premium support    Yes     Over time     Ratably over
                                         support term

Usage overage      Yes     Over time     As consumed

Professional svcs  Yes     Over time     As delivered
                           or point      (depends on
                           in time       scope)
──────────────────────────────────────────────────────

Key judgment: Is standard setup distinct
from the subscription? If the customer
cannot use the platform without it, and
you would not sell setup separately,
it is likely combined — not distinct.

Do This

  • Evaluate each contract element against both the "capable of being distinct" and "distinct in context" criteria
  • Document the rationale for every distinctness determination — especially borderline cases
  • Apply the same judgment consistently across similar contracts — inconsistency triggers audit findings

Avoid This

  • Assume every line item on the invoice is a separate performance obligation — billing structure does not determine accounting treatment
  • Combine elements to defer revenue recognition or separate elements to accelerate it — let the framework drive the answer
  • Change the distinctness determination between similar contracts without documented rationale