A $1.2M software license signed on January 1 can be recognized as $1.2M of revenue on January 1, or $100K per month over twelve months, under ASC 606. Same contract. Same cash. Two completely different revenue curves. The choice is not policy. It is determined by whether the underlying IP is functional or symbolic, and whether the customer's value comes from a snapshot of the IP at the moment of transfer or from an ongoing feed of the licensor's activities.
Software license revenue recognition is where the five-step model gets concrete at Step 5, and getting it wrong is one of the most common rev rec errors among growth-stage software companies. This is the test, the worked examples, and where the call quietly goes wrong. (If a license is bundled with support, start with the performance obligations split first.)
The two types of license, side by side
- Examples
- Software, films, recordings, drug compounds
- Value comes from
- The IP itself
- Updates / maintenance
- Optional; separate POs if bundled
- Customer dependency
- None after delivery
- Examples
- Brands, trademarks, team logos, franchises
- Value comes from
- The entity's continuing activities
- Updates / maintenance
- Critical; value decays without them
- Customer dependency
- High and ongoing
These characteristics come straight from ASC 606-10-55-58 through 55-65. The classification, not the contract's label or its cash schedule, decides the recognition pattern.
The snapshot vs feed test
Functional IP is a snapshot the customer takes home. Symbolic IP is a feed that depends on the licensor's continued performance. The recognition pattern follows the value-delivery pattern, not the cash-collection pattern.
License types, classified
See it in motion
Cadel classifying a license and applying the correct recognition pattern
Where the call goes wrong
Three misclassifications that move revenue into the wrong period
What good looks like
A clean licensing assessment classifies each license at contract inception as functional or symbolic, with the classification documented and justified against the standard. Functional licenses recognize at delivery; symbolic licenses recognize over the license period. Bundled support and maintenance are separated as their own performance obligations, and SaaS subscriptions are correctly identified as service contracts (not licenses) with ratable recognition over the term. The license-by-license classification is preserved in the audit trail and reviewed when the arrangement changes.
At Cadel, the license classification runs as a structured workflow at contract intake. The functional vs symbolic test is applied against contract terms, the recognition pattern is set, and bundled POs (support, training, hosting) are separated automatically. SaaS contracts route to the service-recognition workflow, the point-in-time vs over-time decision is documented, and the recognition schedule is generated from source contract data.
See how Cadel automates revenue recognition under ASC 606, or get in touch to classify one of your license arrangements (perpetual, term, subscription, brand, or franchise) and set its recognition schedule.