Quality of earnings: how diligence treats data licensing revenue

What does a quality of earnings review ask about data licensing revenue?#

A quality of earnings review asks whether data licensing revenue is real, correctly recorded and likely to continue under a new owner. The report recasts historical results into an adjusted EBITDA a buyer can price, and new or unusual revenue streams get the closest look.

Data licensing is unusual for most operating companies. It sits outside the core product or service, it may come from one or two contracts, and its timing follows deliveries rather than months. Expect the reviewer to trace each license from contract to invoice to cash to delivery, and to ask who outside finance can explain it.

Either side may commission the work. A sell-side review lets the company frame data revenue before buyers do; a buy-side review tests that framing. The same questions come up in both.

Recurring or non-recurring: the adjustment that matters most#

The recurring-or-non-recurring call matters most because it decides whether data licensing revenue is priced into the business or set aside as a one-off. Reviewers normalize earnings to remove items not expected to repeat, and a single license of an archive of past support tickets looks like a one-off unless the evidence says otherwise.

Evidence that supports recurrence includes contracted refresh deliveries, a renewal already signed or in negotiation, more than one licensee for the same record family, and new records the company keeps producing in the normal course of business. Evidence against it includes an exclusive license that blocks further sales, an archive with no refresh, and a buyer relationship that depended on a departing owner.

Do not argue recurrence from inbound interest alone. Reviewers weigh signed contracts and history; pipeline belongs in the management narrative, not in adjusted EBITDA.

Likely QoE treatment by license type#

QoE treatment by license type follows the shape of the contract more than its size. The table shows common structures, how a reviewer is likely to view each and what documentation it will request; the actual call depends on the facts and on the reviewer's judgment.

Upfront cash, deferred revenue and the working capital peg#

Upfront cash for a multi-year data license can help the seller's bank balance and hurt the purchase price at the same time. If the license requires refresh deliveries or continuing access after closing, part of the fee may sit as deferred revenue, and the buyer inherits the obligation to deliver without receiving the cash.

Buyers handle this in different ways. Some treat deferred revenue as a debt-like item that reduces the price, some fold it into the working capital peg, and some negotiate a specific adjustment. Have your accountants' revenue recognition memo ready before buyers ask, because the reviewer will start from it.

ASC 606 sets the timing rules the memo has to address. A license that gives a right to use intellectual property as it exists when granted is generally recognized at a point in time, while a right to access IP, such as symbolic IP or IP the licensor is expected to change substantively during the term, is recognized over the license period. Usage-based royalties are recognized only as the usage occurs, and revenue from a renewal is recognized no earlier than the start of the renewal period, so a renewal signed just before a sale does not pull revenue forward. Whether a particular dataset license is an IP license at all, or a service such as hosted access, is a judgment for your auditors.

Cash timing also shapes the story. A license billed and collected just before closing raises questions; one billed on a documented delivery schedule does not.

A short memo answering these points, agreed with the auditors before the sale process, prevents a reviewer from recasting the revenue on its own assumptions.

• 1Point-in-time or over-time recognition, and the reason for the choice
• 2Separate performance obligations, such as the archive delivery and each scheduled refresh
• 3How any usage-based or revenue-share fee is estimated and recognized
• 4The deferred revenue balance at each month end and the delivery that releases it
• 5Renewal dates and when renewal revenue may start

Costs and margin: what reviewers net against the revenue#

Reviewers net preparation, legal and channel costs against data licensing revenue to see what it actually contributes. A license that looks large on the revenue line can look modest once redaction work, outside counsel, engineering time for exports and intermediary fees are counted.

Track those costs from the first license under a separate department or project code. If staff time is not tracked, the reviewer may estimate it, and estimates tend to be conservative. One-time costs, such as building an export pipeline, may also be adjusted out, which partly offsets the revenue adjustment.

• 1Internal staff time on exports, review and approvals
• 2Outside counsel for rights review and contract negotiation
• 3Privacy preparation: redaction, de-identification and quality checks
• 4Secure delivery through encrypted drives or controlled storage access
• 5Intermediary or platform fees
• 6Tax advice on the license income

Concentration, termination and contract risk#

Concentration risk is the next question a reviewer raises, because data licensing revenue often comes from one buyer under one contract. The reviewer will read termination rights, refund or clawback terms, acceptance conditions and any deletion obligations that could unwind revenue already booked.

Contract terms that limit future revenue also appear in the report. Exclusivity, rights of first refusal and most-favored-nation pricing all reduce what a new owner can earn from the same records. Change-of-control and assignment clauses decide whether the license survives the sale at all.

Indemnities and liability caps are usually read by legal diligence rather than the QoE team. A large uncapped exposure can still turn into a specific indemnity or escrow request in the purchase agreement.

Illustrative: a 3PL prepares its data revenue for a sale#

Illustrative: a fictional third-party logistics company with several warehouses plans a sale to a strategic acquirer. It earlier licensed WMS exception records, carrier claim notes and customer service email threads to a model developer for a one-time fee, then signed a second license for scheduled refresh deliveries.

The CFO commissions a sell-side QoE and presents the first fee as non-recurring before the reviewer raises it. The refresh license is presented as recurring, supported by a delivery log, the buyer's acceptance notices, the remaining contract term and a cost schedule showing redaction and export time for each delivery.

The reviewer keeps the refresh revenue in adjusted EBITDA with a note on concentration, and the acquirer's counsel confirms the license can be assigned with the buyer's consent. The one-time fee is still discussed, but as evidence that the records have buyers rather than as run-rate earnings.

How SourceX approaches documentation for diligence#

SourceX approaches documentation as part of each transaction rather than a clean-up before a sale. In the SourceX five-step transaction, each license moves through Supply, Rights, Preparation, Approval and Delivery, and the supplier approves every step.

The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization for each package. Those are the documents a diligence team asks for when it tests whether data revenue was earned properly and can continue.