Accounting & Reporting
Performance Obligations
One contract is almost never one sale. Learn to cut a deal into the separate promises the revenue standard actually recognizes — because that cut decides how much revenue you report this quarter and how much waits.
- Advanced
- 8 min total
- 12 chapters
What decision this helps you make: How many separate promises live inside a contract, what price attaches to each, and when each one turns into revenue.
- Related calculator: Financial Document Builder
What this topic is
A performance obligation is a promise in a contract to transfer something distinct to the customer. Modern revenue accounting works by finding every such promise, pricing each one on its own, and recognizing revenue promise by promise rather than contract by contract.
Why it matters
Getting the count wrong moves revenue between periods. Treat a bundle as one promise and revenue drips over years; split it into three and a large slice lands the day you deliver the first one. Auditors, acquirers and lenders all re-perform this analysis, and a wrong answer here is the single most common cause of revenue restatements at contract-heavy companies.
Who should learn it
Controllers and CFOs at companies that sell bundles, subscriptions, implementations or long projects; diligence analysts reading someone else's revenue; and founders who price a deal without realizing they just designed its accounting.
What you will understand
- The two-part "distinct" test and how to apply it to a real bundle
- When many deliveries collapse into one obligation under the series guidance
- Why a discount coupon or renewal option can itself be a promise you must defer
- How the transaction price gets split across obligations, and what to do when a price is not observable
Prerequisites
Common misconception
"We invoiced it, so we earned it." The invoice is a cash-collection document; it has no authority over revenue. A contract that bills 100% up front can carry three obligations recognized across three different patterns, and a contract that bills monthly in arrears can require a large chunk of revenue on day one. Billing tells you what the customer owes. Performance obligations tell you what you have actually delivered — and only delivery makes revenue.