Definitions and comparisons

One-time vs recurring: how buyers view data licensing revenue in a QoE

By SourceX Editorial · Reviewed by Noah Loul · October 9, 2026

Short answer

In a quality of earnings review, data licensing revenue is judged mainly on whether it will repeat. A one-time snapshot license is usually treated as non-recurring and adjusted out of run-rate EBITDA, while a contracted recurring feed or a multi-year license with renewal evidence has a stronger case to stay in, subject to concentration and documentation.

Key takeaways

QoE providers normalize earnings, so a single license fee in the trailing period is a prime candidate for a non-recurring adjustment.
Contracted recurring deliveries with a history of payment are the strongest form of licensing revenue in diligence.
Revenue recognition timing under ASC 606 can differ sharply from when cash arrives, especially for upfront multi-year payments.
Concentration in one licensee and untracked preparation costs are common follow-up questions once licensing revenue is identified.
A separate general ledger account and a complete contract file make licensing revenue far easier to defend.

Why does a QoE separate one-time from recurring revenue?#

A quality of earnings review separates one-time from recurring revenue because a buyer pays a multiple on earnings it expects to continue. The QoE provider rebuilds adjusted EBITDA for the trailing period and removes items that will not repeat, so that the multiple is applied to a sustainable base.

Data licensing revenue is new to most diligence teams. With no established playbook, reviewers fall back on first principles: is there a contract that obliges future payments, has the pattern repeated, and does the revenue depend on one counterparty? A license that answers those questions well can be treated like any other contracted revenue. One that does not is usually set aside as a one-off gain.

Being adjusted out of run-rate EBITDA does not mean the revenue is worthless in a sale. The cash still counts, and a well-documented license can support a separate discussion about the asset that produced it.

Snapshot, feed or multi-year: likely QoE treatment#

The deal shape is the single biggest driver of QoE treatment. The table summarizes how reviewers commonly view each structure; actual treatment depends on the provider, the buyer and the contract wording.

Snapshot, feed or multi-year: likely QoE treatment
Deal shape	What the licensee receives	Likely QoE view	Evidence that helps
One-time snapshot license	A fixed set of historical records, delivered once	Non-recurring; adjusted out of run-rate	Signed license, delivery record, proof the cost base is also one-off
Snapshot with refresh option	Historical set plus an option to buy later updates	Non-recurring until an option is exercised	Option terms and any exercised refresh
Recurring feed	New records delivered on a schedule	Potentially recurring if contracted and paid as agreed	Delivery log, invoices, payment history, termination terms
Multi-year license, annual fees	Ongoing rights and updates over a defined term	Recurring for the committed term	Committed term, renewal and early termination terms
Multi-year license, paid upfront	Rights over a term, paid in one installment	Scrutinized for timing; cash and revenue may differ	ASC 606 memo and deferred revenue schedule

How revenue recognition interacts with the QoE#

Revenue recognition determines which period a license fee lands in, and the QoE works from those recognized figures. Under ASC 606, the timing of license revenue depends on what the contract promises, such as a single delivered snapshot versus ongoing updates over a term, so an upfront payment does not automatically become revenue on the day it arrives.

Two parts of the standard come up most for data licenses. A license to functional intellectual property is generally a right to use the IP as it exists when granted, with revenue recognized at a point in time, unless the licensor's ongoing activities are expected to substantively change it and the licensee must use the updates; a delivered snapshot may resemble that pattern, but the conclusion depends on the contract. Sales-based or usage-based royalties, such as per-use fees, are recognized only as the underlying usage occurs. Your accountants decide the treatment license by license.

The mismatch cuts both ways. A large upfront payment recognized at delivery can inflate one year and then disappear. A payment recognized over a term leaves a deferred revenue balance, and some buyers treat deferred revenue as a debt-like item in the price negotiation. Ask your accountants to document the treatment of each license when it is signed, not when diligence starts.

What diligence teams ask for#

Diligence teams ask for the documents that prove a license is real, paid, rights-cleared and free of hidden obligations. Having them in one folder shortens the conversation and avoids a discount for uncertainty.

Signed license agreements, amendments and any side letters.
Delivery records showing what was delivered, when, and any acceptance by the licensee.
Invoices, cash receipts and the general ledger account where the revenue is booked.
Term, renewal, termination and change-of-control provisions.
Exclusivity terms, field-of-use limits and any most-favored terms.
Continuing obligations such as deletion, audit rights, warranties and indemnities.
The rights review and privacy preparation record behind each package.
The costs of preparation, including staff time, tools and intermediary fees.

Concentration, margin and the cost side#

Concentration is the first follow-up question once licensing revenue is identified. If one licensee accounts for all of it, reviewers will ask how dependent the revenue is on that relationship and what happens if the licensee is acquired, changes strategy or terminates.

The cost side matters as much as the revenue. Preparation work, such as exports, de-identification, reviews and project management, is often absorbed into engineering or operations budgets and never tagged. A QoE provider may then adjust the margin, or question whether the revenue is as profitable as it looks. Tag those costs to a project code from the start.

Related-party and bundled deals draw extra scrutiny. If the licensee is also a customer, a vendor or a company connected to the sponsor, reviewers check whether the license fee was set on its own terms or traded against a discount elsewhere. Keep each license on separate paper with its own pricing rationale and approval record.

Illustrative: a fictional vertical SaaS company serving field service businesses is owned by a lower-middle-market sponsor. In the trailing year it licensed a de-identified snapshot of support tickets and engineering issue history to an AI developer, and it plans a sale process next year.

The CFO had booked the fee to a dedicated other revenue account and coded preparation time to a separate project. The sell-side QoE presented the license as non-recurring, kept it out of adjusted EBITDA and showed it as a separate line with its own margin. A second license under negotiation was described in the management presentation but not counted.

The buyer's QoE reached the same treatment. Because the contract file, delivery record and rights review were complete, the license raised no diligence issues, and the buyer's team asked about refresh options rather than about risk.

How to present licensing revenue before a sale#

Licensing revenue holds up best when it is visibly separate from the core business. Blending a license fee into SaaS ARR or service revenue invites a reviewer to question the whole revenue line, not just the license.

Book licensing revenue to its own general ledger account and its costs to a project code.
Keep a contract file per license with delivery records and payment history.
Ask your accountants for a short revenue recognition memo for each license.
Show licensing as a separate line in management accounts and board packs.
Avoid presenting pipeline licenses as run-rate before they are signed and delivered.
Consider whether a refresh or feed structure fits the records, rather than forcing one.

How SourceX documents licenses for diligence#

SourceX runs each license through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, and records the outcome in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. That packet is the kind of record a diligence team asks for.

SourceX does not predict whether a license will repeat or how a QoE provider will treat it. Deal shape depends on what the buyer needs and what the records support, and the supplier approves every term.

Frequently asked questions

Should data licensing revenue be counted in ARR?

Generally no. ARR describes subscription revenue from the core product, and mixing in license fees from a different activity makes the metric harder to trust. Report licensing as its own line, with recurring feeds shown as contracted revenue where the terms support it.

Can a one-time license still help a valuation?

It can, indirectly. The cash improves the balance sheet, and a documented, rights-cleared license shows a buyer that the records have value and that the company can transact safely. Some buyers will discuss that potential separately from the EBITDA multiple.

Does an exclusive license change the QoE view?

Exclusivity mainly affects diligence on the asset rather than the earnings adjustment. Reviewers will ask what the exclusivity blocks, for how long and in which fields, because it can limit the acquirer's own plans for the same records. An exclusive license that prevents future licenses can also weaken any argument that the revenue will repeat.

Will our lender treat licensing revenue the same way?

Not necessarily. Credit agreements define EBITDA for covenant purposes, and those definitions may include or exclude non-recurring income differently from a buyer's QoE. Check the EBITDA definition, any caps on non-recurring items and the reporting requirements in your credit agreement, and tell the lender early if license income will affect covenant calculations.

When should we start preparing for a QoE?

Start when the first license is signed. Setting up the ledger account, project code, contract file and revenue recognition memo at signing costs little, while reconstructing them during a sale process is slow and invites skepticism.

Sources

Under ASC 606, a license to functional intellectual property is generally a right to use the IP as it exists when the license is granted, with revenue recognized at a point in time, unless the IP's functionality is expected to substantively change through licensor activities and the customer is required to use the updated IP. Source
ASC 606 requires revenue for a sales-based or usage-based royalty promised in exchange for a license of intellectual property to be recognized only when the later of the subsequent sale or usage, or satisfaction of the related performance obligation, occurs. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

Plan data licensing before a sale process Talk to SourceX