License Revenue Recognition: Right to Use vs. Right to Access

The distinction between a right-to-use license and a right-to-access license is where tens of millions in annual revenue recognition timing rest. One grants a discrete right to the customer’s benefit at a point in time; the other grants ongoing access as the vendor performs. Under ASC 606 and IFRS 15, the classification triggers two opposite revenue schedules.

The ASC 606 / IFRS 15 framework

Under ASC 606 (the U.S. standard) and IFRS 15 (the international standard), license revenue is recognized only when a customer obtains the right to use (or access) an intellectual property asset, and the entity satisfies its performance obligation.

The critical question: Does the customer obtain a right that allows them to direct the use of the IP? If yes, it is typically a point-in-time recognition (a right-to-use license). If no—if the vendor retains control and the customer simply accesses the IP as the vendor performs—it is a right-to-access license, recognized over time.

This distinction was added to clarify the explosion of software-as-a-service (SaaS) and subscription models, where the old textbook assumption (a license = point-in-time cash) was breaking down.

Right-to-use licenses: point-in-time recognition

A right-to-use license grants the customer a standalone, unilateral right to use the IP. Once granted, the customer controls how the IP is used, when, where, and in what form. The vendor has no further involvement in directing the use.

Examples:

• A perpetual software license with no updates or support (rare, but still exists): the customer buys the code and can run it forever, modify it, or integrate it however they like.
• A trademark license allowing a franchisee to use the brand in a defined territory; the franchisor has no control over daily use.
• A patent license permitting a manufacturer to produce goods using a patented process; the licensor is not involved operationally.

Recognition timing: Revenue is recognized at the moment the customer obtains the license. If the customer pays upfront, the full amount is recorded as revenue immediately. If payment is deferred, the full amount is still recorded immediately (the performance obligation is satisfied; payment timing is separate). If the customer pays in installments and the contract spans years, revenue is still recognized upfront—the deferral is not due to unsatisfied obligations, but rather is treated as a financing arrangement.

Why point-in-time? The vendor’s work is done. The customer has the right and the ability to benefit from the IP without the vendor’s further input. No ongoing performance obligation exists.

Right-to-access licenses: over-time recognition

A right-to-access license does not grant the customer independent control of the IP. Instead, the customer accesses the IP as managed by the vendor. The vendor controls how the IP changes, updates, improvements, restrictions, and availability over time. The customer’s benefit depends on the vendor’s ongoing performance.

Examples:

• A SaaS product (Salesforce, Slack, Adobe Creative Cloud): the customer accesses cloud-hosted software; the vendor controls updates, features, security, and availability.
• A music or video streaming service: the customer accesses a catalog that the vendor curates, removes, and updates continuously.
• A cloud storage subscription: the vendor controls infrastructure, backup, and security.
• An API with a service-level agreement: the vendor controls uptime, performance, and feature roadmap.
• A cloud database: the vendor provides the platform, patches, and availability guarantees.

Recognition timing: Revenue is recognized over the subscription period, typically monthly or annually. A one-year SaaS contract worth $120,000 would record $10,000 per month as revenue, assuming even performance. If the vendor promises major feature releases mid-year, revenue might be adjusted for the timing of each release.

Why over-time? The vendor is performing continuously. The customer’s benefit is created and sustained only as the vendor fulfills its obligations (updates, availability, security, etc.). The vendor retains control of the IP itself; the customer merely accesses it.

The critical distinction: customer control

The dividing line is whether the customer can direct the use of the IP independently of the vendor’s further actions.

Consider two software licenses:

1. Perpetual license with no updates: The vendor delivers the code, license expires, the customer owns the code forever, and may use it however they wish (subject to IP law). The vendor has no further obligation. This is right-to-use; revenue is point-in-time.

2. Perpetual license with mandatory annual updates: The vendor delivers code and commits to annual updates and security patches. The customer cannot dictate what updates are delivered; the vendor controls the roadmap. The customer’s benefit—being able to run secure, current software—depends on the vendor’s performance. This is right-to-access; revenue is over-time.

The subtlety: even if the customer purchased the right “perpetually,” if the vendor retains control over the form and content of what the customer accesses, it is a right-to-access license.

Worked example: SaaS vs. perpetual software

Scenario A: Perpetual Software License

A company buys a statistical software package for $100,000. The vendor provides the executable and source code; the customer can install it on any machine, modify it, or integrate it into other systems. The vendor provides 90 days of support, then the license is standalone.

• Classification: Right-to-use.
• Revenue recognition: $100,000 at the moment the license is issued and the customer can download the code.
• The 90-day support is a separate, immaterial performance obligation (or bundled as immaterial).

Scenario B: SaaS Cloud Platform

A company subscribes to a web-based platform for $100,000 per year. The vendor hosts the code, controls all updates, manages uptime, provides 24/7 support, and commits to releasing new features quarterly. The customer cannot download or modify the code.

• Classification: Right-to-access.
• Revenue recognition: $8,333 per month ($100,000 ÷ 12) as the vendor performs.
• If the vendor commits to a major feature release in month 6, revenue timing might be adjusted to reflect the timing of that performance trigger.

If the customer signs a multi-year contract (e.g., $300,000 for three years, paid upfront), revenue is still spread: $8,333 per month over 36 months, not $300,000 upfront.

Common grey areas and auditor scrutiny

Update commitments. A contract stating “we will provide updates and improvements” tilts toward right-to-access, because the vendor is controlling the benefit stream. Audit teams closely read update language.

Standalone functionality. If a customer can use the software in a meaningful, standalone way without further vendor involvement, it leans toward right-to-use. If the software requires ongoing platform services (hosted features, data syncing, cloud infrastructure), it is right-to-access.

Customization and configuration. If the vendor customizes the software for the customer at contract inception and then hands it off, that is often a right-to-use (one-time performance obligation). If the vendor continuously configures or maintains the customer’s instance (as in a managed SaaS service), it is right-to-access.

Termination clauses. Perpetual licenses with the ability to use the software even if the vendor ceases business point toward right-to-use. Subscription licenses that terminate abruptly if the vendor fails (e.g., no ability to run the hosted code locally) point toward right-to-access.

Practical implications for revenue forecasting

The distinction directly impacts quarterly revenue recognition and financial statements:

• Right-to-use: Large upfront revenue events (new perpetual licenses sold) are recognized immediately. Quarterly revenue swings with new sales.

• Right-to-access: Revenue is smoothed over the subscription term. A $1 million three-year SaaS deal contributes $27,777 per month over 36 months. This creates more predictable, recurring revenue lines, but defers cash recognition if the customer pays upfront.

For investors and analysts, a company with a mix of right-to-use perpetual licenses and right-to-access subscriptions will show lumpier revenue than one purely reliant on subscriptions. Companies often aim to shift more toward subscriptions for revenue predictability.

See also