Why Your Hosting Arrangement Impacts Software Revenue Recognition
The Decision That Shapes Everything After It
A software company signs a three-year contract with a new customer. The platform is hosted on servers the company deploys and manages. The customer accesses the software though a SaaS arrangement. Thus, the customer never downloads the software, doesn’t install it, and has no contractual right to take possession of the underlying code.
Under ASC 606, the first question in any software revenue arrangement is not “what are we delivering?”, it’s “does the customer obtain a software license, or are we providing a service?” The answer determines which revenue recognition framework applies to the entire deal.
The Two-Part Test
Topic 606 applies the same framework that existed under legacy US GAAP to determine whether a cloud computing arrangement includes a software license. A license exists only when both conditions are met:
Condition 1: The customer has the contractual right to take possession of the software at any time during the hosting period without significant penalty.
Condition 2: It is feasible for the customer to run the software on their own infrastructure or through a third party, independent of the vendor.
If either condition fails, there is no software license. The arrangement is a SaaS arrangement.
Why Most Hosted Arrangements Are SaaS
In practice, many hosted software arrangements fail the first condition such as when the software vendor deploys and manages the hosting environment. The customer accesses the application through a web portal. There is no contractual provision allowing the customer to download the source code or run the software independently.
The result: upfront implementation fees are often deferred and recognized ratably over the service period, which starts when the customer can start using the software. There is no upfront license revenue event. The transaction price flows through the income statement on a time-based, straight-line basis.
The distinction is not about where the software runs. It is about whether the customer controls the right to run it elsewhere.
When a License Does Exist Inside a Hosting Arrangement
Some arrangements do include an embedded software license. This happens when the customer has a genuine contractual right to take possession, even if they never exercise it, and could feasibly operate the software independently.
When a license is present, the licensing implementation guidance applies. The software license is classified as functional intellectual property. If the license is distinct from other promised goods and services, revenue attributable to the license is recognized at the point in time when the customer obtains control.
This creates a fundamentally different revenue profile: upfront license revenue at delivery, with the hosting and support services recognized ratably over the remaining contract period.
The Hybrid Problem
Increasingly, software companies offer arrangements that combine both an on-premise element and a SaaS element, an on-premise application with cloud-based modules, or a SaaS application with an offline mode.
In many cases, these two elements will be distinct from each other. But when the on-premise software cannot function without the SaaS component, or only provides insignificant standalone value, the elements are not distinct. The combined item is generally accounted for as a service arrangement rather than a license.
The test here is whether the two elements are transformative to each other (combined into something new) or merely additive (each works independently). Transformative means single performance obligation. Additive means separate.
Real-World Application
Consider a software company that provides a proprietary platform to its customers. The platform is hosted on an environment the software company deploys and manages. The customer accesses it through a web portal and has no contractual right to take possession of the software at any time.
Because the customer cannot obtain the license, the entire arrangement is classified as SaaS. Fixed subscription fees are recognized ratably. Implementation services are evaluated separately under the complex versus non-complex framework discussed in Part 3 of this series: Your Implementation Services Aren’t All Created Equal
This classification drives every subsequent decision: how implementation fees are allocated, when contract costs are capitalized, and how the balance sheet reflects the economic substance of each software agreement.
The Bottom Line
The license vs. SaaS determination is not a secondary classification exercise. It is the foundational decision that shapes your entire revenue model. Get it wrong, and every downstream calculation, transaction price allocation, performance obligation timing, contract asset treatment, is built on the wrong premise.
If your software company hosts the product and the customer has no right to take possession, you are providing a service. Your revenue recognition framework needs to reflect that reality.
At Lavoie CPA, we work with software companies navigating complex hosting arrangements and SaaS revenue models.