Revenue Recognition: How to Identify Performance Obligations

A performance obligation is a promise in a contract to transfer a distinct good or service to a customer. Under ASC 606, every contract must be analyzed to identify all performance obligations before revenue can be allocated and recognized. A good or service is “distinct”, which makes it a specific obligation, when: (1) the customer can benefit from it on its own or with other readily available resources, and (2) the promise to transfer it is separately identifiable from other promises in the contract. Most SaaS contracts contain 2–4 performance obligations: software access, implementation, support, and training.

Identifying performance obligations correctly is the foundation of accurate ASC 606 revenue recognition. Over 60% of SEC enforcement actions involving revenue fraud trace back to improper revenue recognition timing — most commonly, recognizing revenue before obligations are satisfied.

What Is a Performance Obligation?

Under ASC 606 and IFRS 15, performance obligations are defined as distinct, contractually promised: 

• Good or service
• Bundle of promised goods or services
• Series of goods or services that are materially the same and with the same pattern of transfer to the customer

Strictly defined, performance obligations are simply the promise itself rather than the actual delivery of the contractually agreed-upon task. Another key concept is buried in the word “distinct.” Essentially, this means the deliverables must benefit your customer.

Only once you’ve delivered upon your performance obligations can you recognize revenue that comes from them—regardless of down payments or any other exchanges before that. 

This makes performance obligations central to accurate revenue recognition and reporting. But how can you identify them? 

Arrangement	Distinct?	Rationale
Software license + standard off-the-shelf training	✅ Distinct (two separate obligations)	Customer can benefit from the software without the training; training is available from other vendors
Software license + heavily customized implementation (license cannot function without it)	❌ Not distinct (combined into one obligation)	Implementation significantly modifies the software; customer cannot benefit from the license independently
SaaS subscription + standard onboarding services	✅ Distinct (two separate obligations)	Generic onboarding does not integrate with or meaningfully modify the SaaS product; separately identifiable
SaaS subscription + proprietary integration build (customer-specific, deeply interrelated)	❌ Not distinct (combined into one obligation)	Proprietary integration is so interrelated with the SaaS that separating them changes the nature of both
Software license + standard annual support/maintenance	✅ Distinct (two separate obligations)	Support does not significantly modify the software; can be priced and sold independently
Hardware + commodity installation services	✅ Distinct (two separate obligations)	Commodity installation is available from other vendors; customer can benefit from hardware without it

Steps to Identify Performance Obligations

Despite their apparent complexity, identifying your performance obligations can be distilled into a four-step process.

Step 1: Contract Review 

This involves examining all promises made to the customer, whether explicit or implicit: 

• Explicit promises are clearly stated in the contract, where the entity promises specific goods or services with details like delivery quantities, dates, and payment terms.
• Implicit promises are not specifically mentioned but implied based on industry or business norms. Implicit promises not itemized in a contract may represent distinct goods and services that must be tracked internally for proper recognition, similar to how post-contractual support (PCS) functions in software agreements.

With that in mind, make note of clauses that could imply additional obligations, such as hints of ongoing support post-purchase or contingencies that leave room for adjustments before final delivery.

Step 2: Assessing Distinct Goods or Services

Next comes identifying which goods and services are distinct and considered separate performance obligations. 

How do you define “distinct?” According to ASC 606 and IFRS 15 guidelines, goods and services meet this criteria if: 

• The customer can benefit from it on its own or in conjunction with other readily available resources.
• The promise to transfer the good or service is separately identifiable from other promises in the contract.

For example, imagine if a B2B software entity determines that its customization services are a distinct performance obligation. This is valid—assuming that: 

1. The software functions without these services, and
2. The customer could receive such customizations from another vendor.

In this example, the customizations would be separately identifiable and therefore a separate performance obligation.

Step 3: Bundling and Unbundling 

Multiple goods or services may sometimes be bundled into one performance obligation. Or a single offering might need to be unbundled into separate performance obligations. 

Bundling might be appropriate when an entity promises goods or services that: 

• Are highly interdependent or interrelated (e.g., a software license bundled with support or installation services)
• Significantly modify or customize each other (e.g., a cell phone service plan bundled with a warranty)

To illustrate, a construction company building a house would likely treat this as a single performance obligation despite involving multiple distinct goods and services.

On the other hand, unbundling might occur if those same services could be sold and used separately—for example, if the company drafts architectural designs, completes site analysis, and offers interior design services; each service is considered a separate performance obligation.

Step 4: Transaction Price Allocation 

The final step involves pricing each performance obligation. The prices typically follow each distinct good or service’s relative standalone selling prices (SSP). 

If SSPs are not directly observable, they must be estimated using approaches such as:

• Adjusted market assessment: An estimate based on existing competition and market conditions
• Expected cost plus margin: The base cost of fulfilling the obligation with an appropriate margin for profit
• Residual approach: Total transaction price (if available) subtracted by the sum of observable SSPs

Challenges in Identifying Performance Obligations

As commerce shifts online and towards subscription services, performance obligations become harder to properly define. 

These challenges are exacerbated by: 

• Complex contracts: Technology and construction industries often have multiple deliverables, each with distinct goods, services, and revenue recognition patterns.
• Changing agreements: Even the smallest modification can have cascading effects from a revenue perspective. A customer seeking to add additional service or alter project scope may require a full performance obligation reassessment.

These challenges only compound in startups and niche industries. For example, a B2B SaaS company may need to determine whether updates and upgrades are bundled.

Accounting for Performance Obligations

Once performance obligations are identified, they must be accounted for in line with revenue recognition principles. 

Revenue should be recognized as the company satisfies each performance obligation, either all at once or over time, depending on the nature of the obligation.

For example, if an entity performs continuous services over a year on a $12,000 contract, revenue could be recognized on a $1,000 monthly basis. On the other hand, if a company delivers a single $12,000 product, revenue would be recognized when the customer gains control of that product.

Tools and Resources

Managing performance obligations can be complex, especially for companies with numerous or intricate contracts that include a variety of goods or services. Particularly challenging scenarios may warrant consulting with accounting professionals or auditors. 

For more information on performance obligations and similar revenue recognition resources, consider the following: 

• PwC, a leading provider of business advisory services
• IFRS Community, a knowledge base for all things relating to IFRS standards
• Deloitte Accounting Research Tool (DART) for GAAP and SEC compliance information
• BDO, an advisory firm with performance obligation advice specifically for the software industry

In addition, various software solutions can help you ensure compliance. However, standard ERPs and CRMs usually don’t have these capabilities. 

You’ll need a specialized solution. 

How RightRev Handles Performance Obligation Tracking

RightRev automates the performance obligation lifecycle from contract ingestion through final revenue recognition. When a contract is loaded from Salesforce or your billing system, RightRev applies your configured revenue rules to identify each distinct obligation, allocate the transaction price using your SSP methodology, and generate recognition schedules for each obligation — whether recognized over time or at a point in time.

For teams managing hundreds of active contracts with multi-element arrangements, this eliminates the obligation-tracking spreadsheets that create audit risk and extend month-end close. RightRev also handles contract modifications, automatically recalculating allocations when obligations are added, removed, or repriced.

Cut down on the spreadsheets and get back to what matters. Try a free demo today.

Back to Blogs