Example 1: Software Subscription
Assume a software company signs a 12-month subscription contract for $120,000. The customer receives continuous access to the hosted software throughout the year, and the service represents a single performance obligation satisfied over time.
If the consideration is allocated evenly, the monthly revenue is $120,000 ÷ 12 = $10,000. The company recognizes $10,000 each month as the service is provided, even if the customer is billed the full $120,000 at contract inception.
This example demonstrates why billing and revenue recognition can occur on different schedules. The invoice establishes the customer's payment obligation, while the service period determines the pattern of revenue recognition.
Example 2: Product Sale With Delivery
Consider a manufacturer that sells equipment for $50,000 and transfers control to the customer when the equipment is delivered. If the contract contains no separate service obligation and delivery occurs on March 28, the company generally evaluates whether the criteria for recognizing the $50,000 of revenue are satisfied in March.
The key evidence may include delivery records, acceptance terms, transfer-of-control provisions, and the customer's ability to direct the use of the equipment. The invoice date alone does not determine the recognition date.
Example 3: Multiple Performance Obligations
A technology company sells a package containing hardware, installation, and a one-year support service for $150,000. Suppose the standalone selling prices are $100,000 for hardware, $30,000 for installation, and $50,000 for support, totaling $180,000.
The $150,000 transaction price is allocated based on relative standalone selling prices. Hardware receives approximately $83,333, installation receives approximately $25,000, and support receives approximately $41,667. Revenue is then recognized according to when each performance obligation is satisfied.
This approach prevents the company from recognizing the entire contract value simply because the customer has been invoiced or paid.
Example 4: Variable Consideration
Suppose a consulting contract provides a fixed fee of $200,000 plus a potential $40,000 performance bonus. The company evaluates the variable consideration and estimates the amount that can be included in the transaction price based on the applicable constraint requirements.
If $30,000 of the bonus qualifies for inclusion, the transaction price used for the relevant allocation becomes $230,000. The company then recognizes the consideration according to the performance obligations and the applicable revenue recognition pattern.
Estimates should be reassessed as circumstances change. Changes in expected consideration can therefore affect revenue recognized in subsequent reporting periods.
Example 5: Contract Modification
Assume a contractor agrees to provide 100 units for $10,000. After delivering 60 units, the customer orders another 40 units at an agreed price. The accounting treatment for the modification depends on whether the additional goods are distinct and whether the modification reflects their standalone selling price and other applicable criteria.
A modification that meets the requirements for a separate contract is evaluated differently from a modification that changes the existing contract. This distinction can affect both the transaction price and the timing of revenue recognition.
For practical contract accounting, finance teams should document the original terms, modification date, revised consideration, remaining obligations, and conclusions supporting the accounting treatment.
ASC 606 Compared With Other Accounting Standards
ASC 606 focuses on revenue from contracts with customers, while other accounting standards address different types of transactions. ASC 815, for example, addresses derivatives and hedging activities, so its accounting requirements should not be substituted for the revenue recognition framework when evaluating ordinary customer contracts.
Similarly, ASC 842 addresses lease accounting. A contract involving the right to use an identified asset may require lease analysis rather than being treated entirely as a customer revenue arrangement. Identifying the applicable accounting standard is therefore an important step before applying a recognition model.
ASC 606 Examples in Finance Operations
Revenue accounting does not operate independently from other business processes. Contract information may originate in sales systems, while procurement and operational records provide supporting evidence for transactions associated with customer arrangements.
For example, finance teams may review a purchase order alongside contracts, delivery evidence, approvals, and fulfillment records when establishing transaction details and supporting accounting conclusions. Strong procurement controls can improve the quality of source information available to accounting teams.
Organizations designing procurement workflows can also use How to Create a Purchase Order System to understand how requisitions, approvals, sourcing controls, and purchase-order records can be structured. Where repetitive procurement activities are involved, Automate Purchase Order Processing provides guidance on applying automated workflows to purchase-order creation and processing.
ERP Data and ASC 606 Workflows
ASC 606 calculations often depend on information distributed across contracts, billing records, customer systems, and the general ledger. ERP architecture therefore affects how efficiently finance teams can gather transaction data and maintain consistent accounting records.
ERP Software Examples: Real Companies, Real Flows provides practical examples of ERP systems, ERP integrations, migration considerations, and finance workflows that can support broader accounting operations. A well-connected ERP environment can make it easier to trace transactions from source records through accounting entries and reporting.
Summary
ASC 606 examples demonstrate how the five-step revenue recognition framework applies to subscriptions, product sales, bundled arrangements, variable consideration, and contract modifications. The central accounting question is when and how a company satisfies its performance obligations, not simply when it bills or collects cash. Documenting contract terms, identifying performance obligations, allocating transaction prices, and maintaining reliable supporting records helps finance teams produce consistent revenue reporting and stronger financial statements.