How are performance obligations identified and allocated under ASC 606?

Core rule Under ASC 606 Performance Obligations, an entity must identify each distinct promise to transfer a good or service to a customer, treat each as a separate performance obligation, and allocate the transaction price based on relative standalone selling prices before recognizing revenue upon satisfaction. How it works - Identifying distinct promises: A promised good or service is distinct if the customer can benefit from it on its own or together with other readily available resources and the promise is separately identifiable from other promises in the contract (ASC 606-10-25-19). Both criteria must be met simultaneously — this is the "capable of being distinct" and "distinct within the context of the contract" dual test. - Series of distinct goods or services: If a series of distinct goods or services are substantially the same and transfer to the customer in the same pattern (e.g., daily cleaning services), they may be treated as a single performance obligation (ASC 606-10-25-14(b)), simplifying allocation and recognition. - Indicators of non-separability: When goods or services are highly interdependent, significantly integrated, or when one good or service significantly modifies another, they are not separ

How do you apply the residual approach to estimate standalone selling price when SSP is highly variable or uncertain under ASC 606-10-32-34?

ately identifiable and must be combined into one performance obligation (ASC 606-10-25-21). - Allocating the transaction price: The transaction price is allocated to each performance obligation in proportion to its relative standalone selling price (SSP) at contract inception (ASC 606-10-32-28). SSP is the price at which an entity would sell the good or service separately — observable prices are preferred, but estimates using adjusted market assessment, expected cost plus margin, or residual approaches are permitted when SSP is not directly observable (ASC 606-10-32-34). - Variable consideration and discounts: Discounts are allocated proportionally across all performance obligations unless observable evidence demonstrates the discount relates specifically to one or more (but not all) obligations (ASC 606-10-32-36 through 32-38). Variable consideration follows similar allocation rules when it relates specifically to satisfying a particular obligation. - Recognition trigger: Revenue is recognized when (or as) each performance obligation is satisfied by transferring control of the promised good or service — either at a point in time or over time per the criteria in ASC 606-10-25-27. Practical example Scenario: A SaaS com

When a contract modification adds new goods at a discount, how do you determine whether it creates a new contract or modifies the existing one under ASC 606-10-25-12?

pany sells a software license ($60,000 SSP), implementation services ($20,000 SSP), and one year of post-contract support ($20,000 SSP) in a bundled contract for $90,000 total. Total SSP = $100,000. Allocation: | Performance Obligation | SSP | Allocation % | Allocated Price | |---|---|---|---| | Software license | $60,000 | 60% | $54,000 | | Implementation services | $20,000 | 20% | $18,000 | | Post-contract support | $20,000 | 20% | $18,000 | | Total | $100,000 | 100% | $90,000 | At contract signing — cash received upfront: | Account | Dr | Cr | |---|---|---| | Cash | $90,000 | | | Deferred Revenue (Implementation) | | $18,000 | | Deferred Revenue (Support) | | $18,000 | | Revenue — Software License | | $54,000 | Assume the license transfers at a point in time (control passes at delivery), implementation is recognized over 3 months as completed, and support is recognized ratably over 12 months. Common pitfalls - Conflating "capable of being distinct" with "distinct in context": Practitioners routinely satisfy one prong but not both under ASC 606-10-25-19. A delivered component may be capable of standalone use, yet if the contract's integration promise makes it inseparable from other deliverables, it fails the second

How should a SaaS company account for material rights (e.g., renewal options at a discount) as separate performance obligations under ASC 606-10-55-42?

criterion — a frequent audit finding in complex technology arrangements. - Using list price as a proxy for standalone selling price: SSP must reflect what the entity would charge if sold separately, not the list price or invoice price. Using catalog prices without adjustment for customer class, geography, or volume discounts understates or overstates allocated revenue in each period. - Improper treatment of contract modifications: When a modification adds distinct goods or services at their SSP, it is treated as a separate contract (ASC 606-10-25-12). When it does not, it is either a prospective catch-up or a cumulative adjustment — confusing these treatments misstates both current-period revenue and deferred revenue balances. Key paragraphs to know - ASC 606-10-25-14 — Defines performance obligations and the series provision. - ASC 606-10-25-19 — The two-part "distinct" test for separating performance obligations. - ASC 606-10-25-21 — Indicators that goods or services are not separately identifiable. - ASC 606-10-32-28 — Allocation of transaction price based on relative SSP. - ASC 606-10-32-34 — Estimation methods when SSP is not directly observable. - ASC 606-10-25-27 — Over-time vs. point-in-time recognition criter

ASC 606 Performance Obligations

ASC 606 Performance — Core Rule

Under ASC 606 Performance Obligations, an entity must identify each distinct promise to transfer a good or service to a customer, treat each as a separate performance obligation, and allocate the transaction price based on relative standalone selling prices before recognizing revenue upon satisfaction.

ASC 606 Performance Obligations

ASC 606 Performance — Core Rule

How ASC 606 Performance Works