A performance obligation is a promise in a contract with a customer to transfer a distinct good or service, or a series of distinct goods or services that are substantially the same. It is the basic unit of account in ASC 606 and IFRS 15, the converged revenue standards issued in 2014 by the Financial Accounting Standards Board and the International Accounting Standards Board. Revenue is recognized when, or as, each performance obligation is satisfied, so the way a contract is split into obligations decides both how much revenue is reported in a period and when.
Identifying performance obligations is the second of five steps in the standards' revenue model: identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations, and recognize revenue as each is satisfied. The concept matters most for businesses that sell bundles, such as software companies, telecoms operators, equipment makers and subscription services.
Identifying distinct goods and services
Promises may be written into the agreement or implied by customary business practice. Each promised good or service is a separate performance obligation only if it is distinct, and two tests must both be met:
- Capable of being distinct. The customer can benefit from the good or service on its own or together with resources that are readily available, such as items the seller or others sell separately.
- Distinct in the context of the contract. The promise is separately identifiable from the other promises rather than an input to a combined output. Significant integration or high interdependence points towards a single combined obligation.
Activities that transfer nothing to the customer, such as administrative setup tasks, are not performance obligations, so a one-off setup fee charged for them is normally added to the transaction price and recognized over the related service period rather than on the day it is billed. An option to buy more goods or services at a discount is a separate obligation only when it gives the customer a material right it would not otherwise receive.
Satisfaction over time or at a point in time
A performance obligation is satisfied when control of the good or service passes to the customer. It is satisfied over time if any one of three criteria is met: the customer receives and consumes the benefit as the seller performs; the seller's work creates or enhances an asset the customer controls; or the work creates an asset with no alternative use to the seller and the seller has an enforceable right to payment for performance to date. Revenue is then recognized by measuring progress with an input or output method, of the kind long used in the percentage-of-completion method.
If none of the criteria is met, the obligation is satisfied at a point in time. Indicators that control has passed include a present right to payment, legal title, physical possession, transfer of the significant risks and rewards of ownership, and customer acceptance.
Allocating the transaction price
Where a contract contains more than one performance obligation, the transaction price is allocated in proportion to the standalone selling price of each, meaning the price at which the seller would sell that good or service separately:
Here is the standalone selling price of obligation , and the denominator adds up the standalone selling prices of all obligations in the contract. Where no observable price exists, the seller estimates one.
Suppose a software company signs a one-year contract for $13,000 covering hosted software and an implementation project. Sold separately, the subscription would cost $12,000 and the implementation $3,000, a total of $15,000. The subscription is allocated dollars and the implementation dollars. The $10,400 is recognized at about $866.67 a month across the year, while the $2,600 follows the progress of the implementation work.
Performance obligations in subscription contracts
Access to hosted software, streaming content or a membership service is usually a stand-ready obligation satisfied over time, because the customer benefits continuously. A monthly or annual service of this kind is often treated as a series of distinct periods accounted for as one obligation and recognized evenly through straight-line revenue recognition. This differs from a license of on-premise software, where the right to use the software as it exists is usually satisfied at a point in time.
Common additional obligations in subscription billing include professional services, hardware shipped with a service, premium support and add-on features. Cash collected before an obligation is satisfied is recorded as deferred revenue, while revenue recognized before the seller has an unconditional right to bill is a contract asset. Upgrades and mid-term plan changes are treated as contract modifications.
Disclosure and judgment
The standards require disclosure about performance obligations, including when they are typically satisfied and the amount of transaction price allocated to obligations not yet satisfied. Many software-as-a-service companies report this figure as remaining performance obligations, a measure of contracted but unrecognized revenue. A practical expedient lets contracts with an original expected duration of one year or less be left out of that disclosure.
Several areas call for judgment. Deciding whether the seller is a principal or an agent determines whether revenue is reported at the gross amount or net of amounts passed to another party. Separating an assurance-type warranty, accounted for as a cost through a warranty liability, from a service-type warranty, which is its own obligation, also changes the timing of revenue.