Revenue Recognition for Software Companies Under ASC 606: CPA Exam Guide

Software Revenue Under the ASC 606 Framework

Software revenue recognition was historically governed by industry-specific guidance under ASC 985-605, which created complex rules around vendor-specific objective evidence (VSOE) of fair value. ASC 606 eliminated most industry-specific guidance and replaced it with a single, principles-based five-step model. While this simplified the overall framework, software arrangements present unique challenges in applying each step, making this a favorite testing area on the CPA FAR exam.

Step 1: Identify the Contract

Software contracts often involve multiple documents: a master services agreement, a statement of work, an order form, and possibly amendments or change orders. Under ASC 606, these documents may constitute a single contract if they are negotiated as a package, the consideration in one depends on the other, or the goods and services are a single performance obligation. Additionally, contract modifications (upgrades, add-on users, feature expansions) require careful analysis of whether they create a new contract, are accounted for as a separate contract, or modify the existing contract prospectively or cumulatively.

Step 2: Identify Performance Obligations

This is often the most critical and challenging step for software companies. A performance obligation is a promise to transfer a distinct good or service. A good or service is distinct if the customer can benefit from it on its own or together with readily available resources and if the promise is separately identifiable from other promises in the contract.

Common Software Performance Obligations

• Software licenses (on-premise or term-based)
• SaaS subscriptions (cloud-hosted software)
• Implementation or setup services
• Post-contract customer support (PCS), including bug fixes and unspecified updates
• Professional services (customization, integration, training)
• Hosting services

A critical determination is whether implementation services are distinct from the software license. If the software requires significant customization or modification to function, the implementation and the license may be a single performance obligation recognized over time. If the software is functional without customization, they are separate obligations.

Step 3: Determine the Transaction Price

Software contracts frequently include variable consideration such as usage-based fees, performance bonuses, or tiered pricing. Under ASC 606, variable consideration is estimated using either the expected value (probability-weighted) method or the most likely amount method, and included in the transaction price subject to the constraint that it is probable that a significant reversal will not occur.

Example: Usage-Based Royalty Exception

A software company licenses its platform for a base fee of $100,000 plus $0.50 per transaction over 1 million transactions. Under the sales-or-usage-based royalty exception for intellectual property licenses, the variable portion is recognized as revenue only as the usage occurs, not estimated at contract inception.

Step 4: Allocate the Transaction Price

When multiple performance obligations exist, the transaction price is allocated based on relative standalone selling prices (SSP). For software companies, determining SSP can be challenging because bundles and discounts are common. Methods for estimating SSP include the adjusted market assessment approach, the expected cost plus margin approach, and the residual approach (permitted only when the SSP is highly variable or uncertain).

Allocation Example

A company sells a bundled package for $180,000 containing a software license (SSP: $120,000), implementation services (SSP: $40,000), and one year of PCS (SSP: $40,000). Total SSP: $200,000.

• License allocation: $180,000 x ($120,000 / $200,000) = $108,000
• Implementation: $180,000 x ($40,000 / $200,000) = $36,000
• PCS: $180,000 x ($40,000 / $200,000) = $36,000

Step 5: Recognize Revenue

Software Licenses: Point in Time vs. Over Time

The nature of the license determines the recognition pattern. A right to use (functional) intellectual property is recognized at the point in time when the customer can use and benefit from the license. A right to access (symbolic) intellectual property is recognized over the access period. On-premise software licenses are typically functional IP recognized at a point in time (when the license key is delivered). SaaS arrangements are service contracts recognized over the subscription period because the customer accesses the software hosted on the vendor's servers.

SaaS Recognition Example

A SaaS company sells a 12-month subscription starting April 1 for $120,000. Revenue is recognized ratably at $10,000 per month. At December 31 (9 months elapsed), the company has recognized $90,000 of revenue and reports $30,000 as deferred revenue.

Contract Costs

Sales commissions paid for obtaining a software contract are capitalized as contract acquisition costs under ASC 340-40 if they are incremental to obtaining the contract and the entity expects to recover them. They are amortized over the period of benefit, which may extend beyond the initial contract term if renewal commissions are not commensurate with the initial commission. A practical expedient allows expensing commissions when the amortization period would be one year or less.

Key Exam Tips

• Distinguish between functional IP (point-in-time recognition) and SaaS/access arrangements (over-time recognition).
• The sales-or-usage-based royalty exception applies to variable consideration based on customer usage of IP licenses.
• Allocate the transaction price using relative SSP, and know the three methods for estimating SSP.
• Contract modifications in software deals are frequently tested; analyze whether they create a separate contract or modify the existing one.