Topics Tools Blog 5-Step Guide →
9 min read · Special Topics

Licensing

Whether you deliver a perpetual license, a subscription, or a hybrid determines not just your product — it determines when you recognize revenue.

Educational content only. This page is not professional accounting advice. Consult a qualified accountant before making accounting policy decisions for your company.

The distinction between a right-of-use license and a right-of-access license is one of the most consequential judgments in software revenue recognition. Get it wrong and you shift potentially large amounts of revenue between point-in-time and over-time recognition — two very different income statement outcomes.

The Core Distinction

Both ASC 606 (paragraphs 606-10-55-54 through 55-65) and IFRS 15 (paragraphs 56–63) use a functional vs. symbolic IP framework to make this determination:

Functional IP has significant standalone functionality at the time of transfer. The customer can use it independently — the licensor's ongoing activities do not significantly affect the IP's utility. The customer gets the IP as it exists today. Revenue is recognized at a point in time when the license is transferred.

Symbolic IP does not have significant standalone functionality, or its value is derived from an ongoing relationship with the licensor — brand value, content libraries, access to a platform that continues to evolve. Revenue is recognized over time.

Functional vs. Symbolic: The Decision Test

Ask three questions:

A "yes" to the last two usually means symbolic. A "yes" to the first and "no" to the others usually means functional.

Working Example: Three SaaS Licensing Structures

Scenario A — On-Premise Perpetual License

A company sells a perpetual license for a software product. The customer installs it on their own servers. The licensor has no ongoing obligation to update the software (a separate annual maintenance agreement covers updates). The software functions independently without the licensor's involvement.

→ Functional IP, right-of-use, point-in-time. Recognize the license revenue when the software is delivered and the customer can use it. Maintenance fees (updates) are a separate performance obligation, recognized over time.

Scenario B — SaaS Subscription

A company provides cloud-based software on a subscription basis. The customer accesses it via a browser. The vendor continuously updates, maintains, and evolves the product. The customer is not receiving a static snapshot — they're receiving ongoing access to the vendor's evolving platform.

→ Symbolic IP, right-of-access, over time. Recognize revenue ratably over the subscription term. The customer's value derives from the ongoing relationship, not a transferred snapshot.

Scenario C — Perpetual License + SaaS Maintenance Bundle

A company sells an on-premise perpetual license bundled with mandatory SaaS-delivered updates and support. Two performance obligations: (1) the perpetual license (functional, point-in-time) and (2) the update/support service (over time). Allocate the transaction price to each using relative SSPs. Recognize the license at transfer, recognize the update service ratably over the maintenance term.

This hybrid structure is common in companies transitioning from perpetual licensing to SaaS. The allocation judgment can be significant.

IFRS 15 vs. ASC 606

Largely aligned conceptually, but with nuanced differences in how "functional" vs "symbolic" IP is described. Both require point-in-time recognition for functional IP (right-of-use) and over-time for symbolic (right-of-access).

Framework reference
IFRS 15

IFRS 15.56–63 and Appendix B (B52–B63): functional vs symbolic IP test

ASC 606

ASC 606-10-55-54 through 55-65: mirrors IFRS framework with similar criteria

"Right to use" trigger
IFRS 15

IFRS 15.B62: right-of-use criteria include "the customer can direct the use of, and obtain substantially all of the remaining benefits from, a licence"

ASC 606

ASC 606-10-55-58: functional IP criteria include "significant standalone functionality" — practically the same test

Sales/usage-based royalties
IFRS 15

IFRS 15.B63: exception — recognize sales/usage royalties on IP licenses only when the sale/usage occurs or performance obligation satisfied (whichever is later)

ASC 606

ASC 606-10-55-65: identical exception. One of the few areas specifically called out as a constraint on estimated variable consideration.

Common Pitfalls
  1. Treating all SaaS as always over-time without analysis. Most SaaS subscriptions are right-of-access — but if you sell an "on-premise" tier or a downloadable product with perpetual rights, you may have functional IP that qualifies for point-in-time recognition. Blanket treatment without analysis can be wrong.
  2. Confusing term and treatment. A 3-year perpetual license is still a right-of-use if functional IP — recognize upfront, not over 3 years. The term of access is not the same as the recognition period.
  3. Ignoring the royalty exception for usage-based licensing. If you charge per API call or per usage on licensed IP, the sales/usage royalty exception applies — you recognize based on actual usage, not estimates, even if the general variable consideration guidance would otherwise require estimation.
  4. Failing to separate license from maintenance. Bundling a perpetual license with ongoing maintenance (updates, support) is common. If the maintenance is a distinct performance obligation — and it usually is — the revenue must be allocated and recognized separately.
Key Takeaway

The functional/symbolic IP distinction sits at the core of software revenue recognition. The key question is not "what did we deliver?" but "what does the customer's value depend on?" If the customer's ongoing benefit derives from the vendor's continuing activities — updates, platform evolution, access management — it's a right-of-access. If the customer could take the IP and go dark on the vendor relationship without losing value, it's likely a right-of-use. Most modern SaaS subscriptions are right-of-access, but hybrid and on-premise models require careful analysis.

Free Resource

5-Step Revenue Recognition Guide

Work through IFRS 15 and ASC 606 step by step with real SaaS examples.

Start the guide
Browse All Topics

More Application Guidance

Explore more deep dives on specific IFRS 15 and ASC 606 concepts.

All topics
Free Tool

27-Point Audit Checklist

Ensure your revenue recognition is audit-ready before your next close.

See the checklist
Free Tool

Revenue Memo Template

A 7-section auditor-ready memo documenting your revenue recognition policy.

Get the template