How to account for data licensing revenue under ASC 606

How does ASC 606 treat a data license?#

Most companies analyze a data license under ASC 606's guidance on licenses of intellectual property, and the first judgment is whether the buyer receives a right to use data as it exists when the license is granted or a right to access data the company keeps changing. A dataset delivered as a fixed snapshot is often analyzed as functional intellectual property, which points to recognition at a point in time.

The standard five-step model still applies: identify the contract, identify the performance obligations, determine the transaction price, allocate it, and recognize revenue as each obligation is satisfied. The licensing guidance mostly affects step two, what was promised, and step five, when each promise is satisfied, while the royalty exception changes how usage-based fees enter the price.

Few data licenses are a bare snapshot, though. Refreshes, preparation services, exclusivity and usage-based fees each move the answer, which is why the CFO should map the contract structure before the first invoice goes out.

Point in time or over time? A decision table by deal structure#

The recognition pattern for data licensing revenue follows the structure of the deal more than its size. The table lists the common structures for software companies licensing support, engineering or product records.

Treat the table as a starting point for the auditor conversation, not a conclusion. Two contracts that look alike commercially can land in different rows because of a single clause about access or updates.

Are refreshes and preparation work separate performance obligations?#

Refreshes are usually separate performance obligations when each delivery is a distinct dataset the buyer can use on its own. The transaction price is then allocated between the initial snapshot and the promised refreshes, and the refresh portion stays deferred until each one is delivered.

Preparation work is less clear-cut. De-identification and formatting performed before delivery are typically inputs to delivering a usable dataset rather than something the buyer benefits from separately, so they usually sit inside the license obligation. Custom labeling or annotation that the buyer could have bought elsewhere and uses independently is more likely to be distinct.

Write down the reasoning for each promise when the contract is signed. Auditors test these judgments, and a short memo prepared at signing is far easier to defend than one reconstructed at year end.

How are revenue shares and usage fees recognized?#

Revenue shares and usage-based fees on a license of intellectual property are generally recognized under the sales- or usage-based royalty exception: at the later of when the buyer's usage or sales occur and when the related license obligation is satisfied. The exception replaces the usual estimate of variable consideration, so the company does not book expected future royalties at signing.

That timing matters for cash and board planning. A deal with a modest upfront fee and a share of downstream revenue may show little revenue in early periods even if the buyer projects heavy use. Make sure the contract gives the company reporting and audit rights, so royalties can be measured and recorded in the right period.

Minimum guaranteed royalties are a common variation. For a point-in-time license, the guaranteed minimum is generally treated as fixed consideration recognized when control transfers, while royalties above the minimum follow usage. Auditors look closely at how the two pieces interact, so model a few usage scenarios in the memo.

Contract terms that change the accounting#

Several ordinary data license clauses change when or how revenue is recognized. Flag them during negotiation, not after signing, so finance can weigh in while terms can still move.

• 1Exclusivity: usually an attribute of the license rather than a separate obligation, but it affects standalone price estimates and allocation.
• 2Refund or clawback rights tied to data quality: may make part of the fee variable consideration subject to the constraint.
• 3Acceptance clauses: can delay the point at which control transfers until the buyer accepts the delivery.
• 4A license start date later than delivery: point-in-time revenue generally waits until the buyer can use and benefit from the data.
• 5Ongoing support for the buyer's questions about the dataset: may be a separate obligation recognized over time.
• 6Deletion or return duties on termination: rarely change timing, but record them in the accounting memo because they shape what happens on early termination or a dispute.

Illustrative: a logistics software company books its first data license#

Illustrative: a fictional logistics software company licenses a snapshot of de-identified support-to-fix histories, with two scheduled refreshes during the license term and a share of the buyer's revenue from a product built with the data. The CFO identifies three performance obligations: the initial snapshot and each refresh.

The fixed fee is allocated across the snapshot and the refreshes using estimated standalone selling prices. Snapshot revenue is recognized when the dataset is delivered and the license term has begun; each refresh portion stays deferred until its delivery. The revenue share is recognized only as the buyer reports sales. De-identification is treated as part of delivering the dataset, not as a separate service, and the auditors review the memo before the quarter closes.

What investors and acquirers will look for#

Investors and acquirers will look at whether data licensing revenue is recurring or one-time, because a snapshot fee and a recurring refresh contract imply very different quality of earnings. Where the stream is material, present it as a separate revenue category or disclosure rather than folding it into subscription revenue.

They will also look for deferred revenue tied to undelivered refreshes and for obligations that survive a sale of the company, such as deletion duties and exclusivity. Clean contract files and the accounting memo keep those diligence questions short.

How SourceX supports the finance side#

SourceX does not give accounting advice, but the SourceX five-step transaction produces records finance teams rely on. Delivery confirmations show when each dataset was handed over, and the SourceX Evidence Packet documents permitted use and release authorization, which define what was licensed. Together they help the CFO support timing judgments with the company's auditors.