License-plus-hosting arrangements: distinct license versus combined service

Some enterprise SaaS deals grant the customer a software license, sometimes paired with a source-code escrow or on-premise fallback right if the vendor stops hosting, in addition to the ongoing hosting service; whether that license is distinct from the hosting service determines whether part of the fee is recognized upfront at a point in time (license) or the entire fee is recognized over time as a single combined hosting service, a distinction that can shift very large amounts of revenue into the wrong period if assessed mechanically.

Can the customer use, run, or transfer the software independently of the vendor's hosting, such as through a functioning and substantive escrow release right? Is the escrow or on-prem fallback right substantive and realistically exercisable, or merely a remote contingency with no practical effect on distinctness? If the license is distinct, is it a right to use (recognized at a point in time) or a right to access (recognized over time), and is the transaction price allocated by relative SSP?

1. Identify what the license actually grants: a right to use functional intellectual property that the customer could exploit independently of the vendor's hosting (e.g., a genuine right to run the software on its own or a third party's infrastructure), versus a nominal or nearly unusable right that only has practical substance if paired with the vendor's hosting.
2. Assess whether the license is distinct from the hosting service by testing whether the customer can benefit from the license on its own or with other readily available resources, and whether it is separately identifiable from the promise to host.
3. Evaluate any escrow or on-premise fallback right specifically: determine whether the triggering event (e.g., vendor ceasing operations, prolonged service failure) is realistically capable of occurring and whether the customer would have the practical ability and technical capacity to actually operate the software independently if triggered, or whether it is a remote, protective clause unlikely ever to be exercised.
4. If the license is genuinely distinct and provides a right to use functional intellectual property, allocate part of the transaction price to it based on relative standalone selling price and recognize that portion at the point in time the customer can first use and benefit from the license.
5. If the license is not distinct (the fallback right is remote and the license has no standalone practical utility without the vendor's hosting), treat the entire arrangement as a single hosting service and recognize the full transaction price over time as the hosting is delivered.
6. Revisit the assessment if contract terms change (e.g., the escrow trigger conditions are loosened, making the fallback right more realistically exercisable).

Where the license is distinct, allocate the transaction price between the license and the hosting service based on their relative standalone selling prices, estimating the license's SSP through observable comparable licenses, an adjusted market approach, or a cost-plus approach if never sold separately. Where the license is not distinct, no separate measurement is needed, measure the full transaction price as a single combined performance obligation recognized on a straight-line or usage basis over the hosting period, consistent with how undifferentiated access arrangements are measured elsewhere.

Disclose: the judgment applied to license-plus-hosting arrangements and the resulting revenue recognition pattern (point in time versus over time); the basis for concluding an escrow or fallback right is or is not substantive enough to make the license distinct; the standalone selling price methodology used to allocate the transaction price when the license is distinct; the amount of revenue recognized at a point in time under such arrangements where material.

• Automatically splitting out point-in-time license revenue whenever a contract uses the word '
• license,'
• without assessing whether the escrow or fallback right is substantive enough to make the license distinct from the hosting service
• concluding a license is distinct simply because a separate line item or dollar figure is stated for it in the contract, rather than assessing actual practical utility independent of hosting
• ignoring that even a technically triggerable escrow right may still fail the distinctness test if the customer has no realistic technical capability to operate the software independently
• failing to reassess the conclusion when contract renewal terms change the escrow trigger conditions.