Key points
A performance obligation is a promise to transfer a distinct good or service, or a series of substantially the same ones (ASC 606-10-25-14; IFRS 15 paragraph 22).
A promise is distinct if the customer can benefit from it on its own and it is separately identifiable within the contract (ASC 606-10-25-19).
SaaS access is usually one stand-ready obligation made of a series of distinct periods, recognized over time.
Bonus credits, renewal discounts and other options can be material rights, which are separate obligations.
Each obligation gets its own share of the price and its own recognition pattern, so the list you make here drives every number that follows.
Performance obligation in one paragraph
A performance obligation is a promise in a customer contract to transfer a distinct good or service, or a series of distinct goods or services that are substantially the same and transfer the same way. ASC 606-10-25-14 sets this out, and IFRS 15 paragraph 22 says the same. Identifying them is step 2 of the ASC 606 five steps.
The list matters because every later step works per obligation. The transaction price is split across them, and each one has its own timing. Get the list wrong and revenue lands in the wrong month even when the contract total is right.
The two-part distinct test
Under ASC 606-10-25-19, a promised good or service is distinct only if both of these are true:
Capable of being distinct. The customer can benefit from it on its own or with resources readily available, including things sold separately by you or others.
Distinct within the context of the contract. The promise is separately identifiable from the other promises. ASC 606-10-25-21 lists factors against this: significant integration, significant modification or customization, and high interdependence.
Promises that fail either test are combined until the bundle is distinct. Promises that are immaterial in the context of the contract can be ignored under ASC 606-10-25-16A.
Series guidance and why SaaS is usually one obligation
Platform access is a promise to stand ready every day of the term. Each day is distinct and substantially the same, and each is satisfied over time with the same measure of progress. ASC 606-10-25-15 therefore treats the days as a series, which is a single performance obligation.
That has a practical payoff for usage pricing. Variable fees that relate to one period of a series can often be allocated to that period alone under ASC 606-10-32-40. Revenue then follows usage month by month without re-estimating the whole contract.
Decision table for a typical AI contract
Illustrative only. Fieldnote AI is a fictional Series B company with usage-based pricing. A standard enterprise order form includes the items below. Your conclusions depend on your facts, so treat this as a starting point to document.
Contract element | Separate obligation? | Usual reasoning | Timing |
|---|---|---|---|
Platform access for 12 months | Yes, one series | Stand-ready service, same each period | Over time, ratably |
Metered API or token usage | Judgment: variable fee within the series, or an optional purchase | Depends on whether the customer makes a new buying decision per unit | As used |
Prepaid credit pack | Yes | Right to future consumption already paid for | As credits are consumed, plus breakage |
Bonus credits granted on signing | Often a material right | Customer gets something it would not get without the contract | When used or when they expire |
Onboarding and configuration | Usually yes | Others could do it; it does not modify the platform | As performed |
Custom model fine-tuning tied to the platform | Often combined with access | Significant customization and interdependence | Over the access term |
Standard support | Yes, but often same pattern as access | Stand-ready; can be combined for practical purposes | Over time |
The usage judgment that matters most
For usage fees, the core question is whether the customer has already contracted for the service, or makes a new purchase decision with each unit. If the platform is a stand-ready series and usage is the price, usage is variable consideration. If each call is a separate purchase at a stated price, usage can be a customer option that becomes a contract only when exercised.
The two views often give the same monthly revenue but different disclosures, especially for remaining performance obligations. Pick one per pricing model, document it, and apply it consistently. Discounted per-unit prices are where material rights appear, so compare them with standalone pricing.
Common mistakes
Splitting by invoice line. Order forms list items for sales reasons. Line items are not obligations until they pass the distinct test.
Missing material rights. Bonus credits and steep renewal discounts get booked as free, which overstates early revenue.
Separating customization that is integral. If the fine-tuning only works inside your platform, it usually is not distinct in context.
No written memo. Auditors expect a short memo per contract type. Without it, every contract is re-argued at year end.
How Quanta handles it
Quanta is built around how a company charges, including usage, credits and hybrid plans. Quanta’s in-house accounting team maps each pricing model to its performance obligations once, then applies the pattern to every contract. That way revenue recognition follows the same logic each month and traces back to journal entries.
Quanta perspective
For AI companies, performance obligations are set by the pricing page more than by the contract. Every new credit bundle or promotional grant can create a new obligation. Bring finance into pricing changes early so the accounting is decided before the first invoice.
Frequently asked questions
What makes a good or service distinct?
The customer can benefit from it on its own or with readily available resources, and it is separately identifiable from other promises in the contract.
Is a SaaS subscription one performance obligation or many?
Usually one. Each period of access is distinct and substantially the same, so the series guidance treats the whole term as a single obligation recognized over time.
Is implementation a separate performance obligation?
Often yes, if the customer could get it from another provider and it does not significantly modify the software. If it customizes the platform significantly, it is usually combined with access.
What is a material right?
An option that gives the customer something it would not receive without entering the contract, such as a significant discount on future credits. It is a separate obligation and part of the price is deferred to it.
What is a remaining performance obligation?
The contracted revenue not yet recognized, covering both deferred revenue and amounts not yet billed. Public companies disclose it in the revenue footnote.