Right to Use vs Right to Access: ASC 606 Software Guide

The foundational distinction under ASC 606 and IFRS 15

In software, technology, and media licensing, determining the precise timing of revenue recognition under ASC 606 and IFRS 15 is one of the most contentious technical accounting determinations.

When an entity licenses intellectual property (IP) to a customer, accounting standard setters established a strict bifurcation under ASC 606-10-55-54 and IFRS 15.B52:

1. Right to Access IP: The customer has access to the vendor's intellectual property as it exists throughout the license period. Revenue is recognized over time.
2. Right to Use IP: The customer has the right to use the vendor's intellectual property as it exists at the specific point in time the license is granted. Revenue is recognized at a point in time.

This single distinction drives whether a $500,000 multi-year software agreement is recognized upfront on Day 1 or ratably across a 36-month subscription term. Misclassifying a right to use as a right to access defers earned revenue and distorts GAAP operating margins; conversely, recognizing a right to access upfront at contract inception triggers audit restatements and SEC/PCAOB comment letters.

Functional IP vs symbolic IP: The classification framework

To establish whether a license provides a right to access or a right to use, ASC 606-10-55-58 through 55-64 directs preparers to evaluate the fundamental nature of the underlying intellectual property: Functional IP vs Symbolic IP.

The Critical Rule for Software

Software code is inherently functional IP. When compiled code executes on a CPU, performs database queries, or automates a workflow, it possesses standalone functionality. Therefore, under ASC 606-10-55-59, an on-premises software license is presumed to be a right to use, recognized at the point in time the customer receives the download key and can benefit from the asset.

The 3-part test for right to access (ASC 606-10-55-55)

Under ASC 606-10-55-55, a license of intellectual property is classified as a right to access if—and only if—all three of the following criteria are satisfied:

1. Contractual or Constructive Expectation of Activity: The contract requires, or the customer reasonably expects, that the licensor will undertake activities that significantly affect the intellectual property to which the customer has rights (ASC 606-10-55-55(a)).
2. Direct Exposure to Vendor Activities: The rights granted by the license directly expose the customer to any positive or negative effects of the licensor's activities identified in criterion (a) (ASC 606-10-55-55(b)).
3. No Transfer of a Separate Good or Service: The activities identified in criterion (a) do not result in the transfer of a distinct good or service to the customer as those activities occur (ASC 606-10-55-55(c)).

What Constitutes "Significantly Affecting" the IP?

Under ASC 606-10-55-57, a vendor's ongoing activities significantly affect the intellectual property only if:

• The activities change the form (e.g., the design or character) or the functionality of the IP; or
• The ability of the customer to obtain benefit from the IP is substantially derived from, or dependent upon, those activities.

If the vendor merely provides routine bug fixes, security patches, or unspecified version upgrades through post-contract support (PCS), those activities do not convert functional software into a right to access. Instead, PCS is treated as a separate performance obligation satisfied over time, while the underlying term license remains a right to use recognized at delivery.

SaaS, on-premise, and hybrid software: where do they sit?

Modern enterprise software distribution models fall across three primary architectures, each requiring a distinct revenue recognition path:

1. Pure Hosted Cloud SaaS

In standard multi-tenant cloud software (e.g., Salesforce, Workday, ServiceNow), the customer accesses software hosted on the vendor's cloud infrastructure.

• Guidance: Under US GAAP (ASC 350-40) and IFRS, standard cloud hosting does not transfer a software license if the customer cannot take possession of the software without significant operational penalty.
• Classification: Because no license is transferred, this is accounted for as a service contract satisfied over time under ASC 606-10-25-27(a), recognizing revenue ratably across the subscription term.

2. On-Premise Term Software License

The customer downloads executable binaries or containerized images onto their own infrastructure or private cloud.

• Classification: The license component is functional IP and represents a right to use. Revenue allocated to the license is recognized upfront at the point in time the license key is delivered and the term begins (ASC 606-10-55-58). Bundled maintenance and technical support (PCS) are distinct performance obligations recognized ratably over the term.

3. Hybrid Software with Continuous Cloud Dependencies

Certain modern enterprise software tools combine a local on-premises agent or edge binary with continuous proprietary cloud services (e.g., threat intelligence feeds, continuous machine learning weight re-training, or real-time fraud scoring databases).

• Classification: If the local binary cannot function without the continuous cloud connection, the software license and the cloud service are not distinct within the context of the contract (ASC 606-10-25-14(b)). They are combined into a single bundled performance obligation recognized over time over the subscription period.

Worked example 1: On-premise term license with maintenance (split model)

Consider an enterprise software vendor that executes a 3-year term license contract for on-premise database optimization software on January 1, 2026:

• Contract Transaction Price: $180,000 billed annually ($60,000 upfront each year).
• Contract Deliverables:
  1. 3-Year On-Premise Term Software License (functional IP).
  2. 3-Year Post-Contract Customer Support (PCS: technical support desk and unspecified maintenance releases).
• Standalone Selling Price (SSP) Determination:
  • The vendor regularly sells perpetual or term licenses standalone; historical pricing establishes an observable SSP of $120,000 for the software license.
  • The vendor sells standalone support renewals at $30,000 per year, establishing an observable SSP of $90,000 for the 3-year PCS period.
  • Total Standalone Selling Price = $120,000 + $90,000 = $210,000.
  • Contract Discount = $210,000 - $180,000 = $30,000 (14.2857% discount).

Step 4 Relative SSP Allocation

Under ASC 606-10-32-28, the $180,000 transaction price is allocated proportionally based on relative standalone selling prices:

• Allocation to Software License: $180,000 × ($120,000 / $210,000) = $102,857.14
• Allocation to 3-Year PCS: $180,000 × ($90,000 / $210,000) = $77,142.86
• Total Verification Check: $102,857.14 + $77,142.86 = $180,000.00

Recognition Pattern

• Software License (Right to Use - Point in Time): $102,857.14 recognized immediately on January 1, 2026, when license keys are provisioned.
• PCS Support (Right to Access / Stand-Ready Service - Over Time): $77,142.86 recognized ratably over 36 months ($2,142.86 per month).

Worked example 2: Hosted cloud SaaS subscription (right to access)

Now consider a B2B SaaS platform delivering automated accounts payable reconciliation:

• Contract Terms: 12-month access to the multi-tenant web application from January 1, 2026 to December 31, 2026.
• Contract Price: $48,000 billed upfront.
• Contract Deliverables: Platform access and routine customer support.

Analysis

1. Does the customer have the contractual right to take possession of the software onto their own servers? No.
2. Can the customer run the software on third-party hardware without significant penalty? No.
3. Conclusion: Under ASC 350-40, no software license exists. The contract is a service contract under ASC 606-10-25-27(a).
4. Recognition Schedule:
   • January 1, 2026: Cash / Accounts Receivable debited for $48,000; Deferred Revenue (Contract Liability) credited for $48,000.
   • Monthly Amortization: $48,000 / 12 = $4,000.00 recognized per month.
   • Upfront recognition on Day 1 = $0.00.

Worked example 3: Hybrid AI model with continuous cloud verification

Enterprise AI deployments present nuanced licensing dilemmas. Consider a fraud prevention vendor:

• Contract: An enterprise bank licenses the vendor's fraud detection model weights to run on the bank's on-premise bare-metal cluster.
• Contract Dependency: The on-premise model weights rely on daily cryptographic vector synchronization and dynamic fraud signature feeds from the vendor's cloud network. Without these continuous daily vector syncs, the model degrades within 48 hours and produces fatal false negatives.
• Term: 12 months for $120,000.

Step 2 Distinctness Analysis (ASC 606-10-25-14)

1. Capable of being distinct: In theory, raw machine learning weights can run offline.
2. Distinct within the context of the contract: Under ASC 606-10-25-14(b), the on-premise weights and the cloud vector service are highly interrelated and interdependent. The vendor provides a continuous integrated service.
3. Classification: The license is not distinct from the continuous cloud service. The entire contract is accounted for as a single performance obligation satisfied over time ($10,000/month).

Journal entries and balance sheet tie-out schedules

Returning to Worked Example 1 (On-premise term license with PCS: $180,000 total price, $60,000 annual billing, $102,857.14 upfront license, $77,142.86 PCS over 36 months):

1. Inception & Delivery (January 1, 2026)

Year 1 invoice issued for $60,000; software license delivered:

Balance Sheet Check: Revenue recognized on Day 1 ($102,857.14) equals billings ($60,000) plus unbilled contract asset ($42,857.14).

2. Year 1 Monthly PCS Amortization (January 31, 2026)

Monthly PCS revenue = $77,142.86 / 36 = $2,142.86 per month:

3. Year 2 Invoice Issuance (January 1, 2027)

Second annual installment of $60,000 billed:

4. 36-Month Amortization Tie-Out Table

Schedule Tie-Out Guarantee: At Month 36, cumulative revenue recognized equals cumulative cash billed exactly ($180,000.00), and the contract asset balance ties out to $0.00 through terminal-period remainder absorption.

PCAOB audit workpaper requirements for software licenses

External auditors inspect software revenue contracts under PCAOB AS 1105 (Audit Evidence) and AS 2301 (The Auditor's Responses to the Risks of Material Misstatement). When reviewing Right to Use vs Right to Access claims, auditors demand specific documentation:

1. Proof of Software Delivery: Cryptographic proof, download server logs, electronic license key transmission receipts, or signed customer acceptance certificates proving control transferred on or before the balance sheet date.
2. Contract Clause Grounding: Exact citations to:
   • Grant clause (identifying whether the grant is perpetual, term, non-exclusive, or hosted).
   • Maintenance clause (specifying whether updates are major releases, minor patches, or stand-ready support).
   • Hosting & possession terms (confirming whether the customer possesses the right to run code off-cloud).
3. Standalone Selling Price (SSP) Support: Historical observable pricing data (such as bell-curve discount analyses of standalone term license sales or standalone PCS renewals) justifying the relative allocation weights.
4. Exact Mathematical Tie-Out: Schedules that show zero unexplained rounding plugs, preserving precision across multi-period amortization.

How Soluqube structures software licensing allocations

Soluqube eliminates the manual spreadsheet risk in software licensing accounting:

• Heuristic Clause Extraction: Ingests technology contracts and extracts the license grant, PCS terms, and pricing tiers with verbatim page citations.
• Objective Classification Support: Provides structured workflows for accounting teams to document functional vs symbolic IP criteria and justify point-in-time vs over-time treatments.
• Deterministic SSP Allocation: Calculates relative standalone selling prices using exact integer arithmetic with terminal-period remainder absorption so deferred revenue and contract asset balances tie out to $0.00.
• Audit-Ready Cryptographic Workpapers: Exports immutable, SHA-256 hashed workpapers that auditors can independently re-perform in 60 seconds (Patent Pending App. No. 202621096305).

To model your software licensing allocations, test our free SSP Allocation Calculator or explore our ASC 606 Revenue Recognition Guide.