- Determine whether a license is distinct from other promises in the contract
- Classify intellectual property as functional or symbolic
- Apply the point-in-time and over-time patterns to licenses
- Apply the sales- or usage-based royalty exception and the renewal timing rule
Is the license distinct
Start with step 2. A license is often bundled with services: installation, customization, hosting, updates or support. If the license is not distinct, the entity accounts for the combined performance obligation and applies the licensing guidance only to the extent needed to decide the pattern of transfer for the bundle. A license that is an input to a combined output (for example, software that only works with significant customization the entity is providing) is not distinct.
Functional or symbolic
ASU 2016-10 sorted intellectual property into two types:
- Functional IP has significant standalone functionality, such as the ability to process a transaction, perform a task, or be played or aired. Software, films, music and drug formulas are common examples. The customer gets most of the value from that functionality.
- Symbolic IP is everything else: brands, trade names, logos, franchise rights, sports team names. Its utility comes from the entity's past or ongoing activities that support the name.
Timing for each
Symbolic IP gives the customer a right to access the IP, satisfied over time because the customer simultaneously receives and consumes the benefit of the entity's continuing support. The entity picks a measure of progress, often time elapsed.
Functional IP gives a right to use the IP as it exists when the license is granted, satisfied at a point in time, unless both of these are met:
- the functionality is expected to change substantively during the license period because of entity activities that do not transfer a separate good or service; and
- the customer is contractually or practically required to use the updated IP.
When both are met (rare in practice), the license is a right to access, recognized over time. Software updates that the customer can choose to install are separate promises, not a reason to treat the license as over time.
The start of the license period
Under 606-10-55-58C, revenue for a license cannot be recognized before both:
- the entity provides (or otherwise makes available) a copy of the IP to the customer; and
- the period begins during which the customer can use and benefit from the license.
This drives renewal timing. If a customer signs a renewal of a three-year term license in October for a period that starts in January, revenue for the renewal is not recognized until January, even though the customer already has the software.
Restrictions are attributes, not promises
Contract terms that restrict time, territory or use define the attributes of a single license. They do not create extra performance obligations. A promise to defend a patent is also not a separate performance obligation. Contrast terms that require the entity to transfer additional rights, such as rights to a second territory starting next year, which are separate promises.
Sales-based and usage-based royalties
Under 606-10-55-65, a sales-based or usage-based royalty promised in exchange for a license of IP is recognized only when (or as) the later of these occurs:
- the subsequent sale or usage occurs; or
- the performance obligation to which the royalty is allocated has been satisfied (or partially satisfied).
This exception replaces the general variable consideration estimate and constraint for those royalties. It applies when the license is the predominant item to which the royalty relates. Minimum guarantees are fixed consideration and are recognized under the normal model.
Audit focus
Read the license and the related statements of work together. Test the start date of each license period against delivery evidence (keys, download logs). For royalty revenue, obtain licensee reports and compare them to cash receipts and contractual rates. The software licensing guide and the franchisor guide apply these rules.
A term software license with a royalty and a renewal
Meridian Code licenses inventory software to a retailer for three years starting February 1, Year 1. Fee: $90,000 fixed, plus 1 percent of the retailer's online sales processed through the software. Meridian delivers the license key January 20. Under a separate contract priced at its standalone selling price, the retailer also buys support for $12,000 per year. Meridian releases occasional updates the retailer may install.
Nature: the software has significant standalone functionality. Updates do not substantively change functionality and the retailer is not required to install them. Functional IP, right to use, point in time.
Timing of the fixed fee: key delivered January 20, but the period starts February 1. Revenue of $90,000 is recognized February 1; the support fee is recognized over each support year.
Royalty: in Year 1 the retailer processes $4,000,000 of sales; the royalty is $40,000. Under the sales-based royalty exception, Meridian recognizes it as the sales occur, quarter by quarter, and does not estimate the full three-year royalty at inception.
Renewal: on November 15, Year 3, the retailer renews for two years starting February 1, Year 4 for $60,000. Revenue: February 1, Year 4.
Self-check
Answer each question before you open the answer.
What is the difference between functional and symbolic intellectual property?
Show answer
Functional IP has significant standalone functionality (software, films, formulas). Symbolic IP does not; its value comes from the entity's ongoing activities that support it (brands, franchise names).
When is a license of functional IP recognized over time?
Show answer
Only when its functionality is expected to change substantively during the license period from entity activities that do not transfer a separate good or service, and the customer is contractually or practically required to use the updated IP.
A customer renews a term license in August for a period that starts the next January. When is renewal revenue recognized?
Show answer
No earlier than January, when the renewal period begins. Under 606-10-55-58C, revenue cannot be recognized before the period in which the customer can use and benefit from the license begins.
How is a sales-based royalty on a license recognized?
Show answer
At the later of when the subsequent sale or usage occurs and when the performance obligation to which the royalty is allocated is satisfied or partly satisfied (606-10-55-65).
Use it on the file
- GuideSoftware Licensing and Term License Revenue Audits Under ASC 606
- GuideFranchisor Audit Guide: Franchise Fee Revenue, Royalties and ASC 606
- GuideSaaS Revenue Recognition Audit: Multi-Element Contracts, SSP and Hosting Licenses
Sources
- FASB, ASU 2016-10, Revenue from Contracts with Customers (Topic 606): Identifying Performance Obligations and Licensing
- FASB, ASU 2014-09, Revenue from Contracts with Customers (Topic 606), Section A
Standards are paraphrased from the primary sources listed above; read the source before relying on a requirement. This lesson is training material, not professional advice. Report an error