Normalized EBITDA: are data licensing preparation costs an add-back?

When can preparation costs be added back?#

Data licensing preparation costs can be added back when a buyer or quality of earnings provider agrees they will not recur in the business going forward. The test looks at the future run-rate, not at how unusual the cost felt when it was paid.

A first data license often involves work that will not repeat: a rights review of legacy customer contracts, an export from a system already retired, or a one-off cleanup of a help desk archive. Those costs have a credible one-time story. A licensing program that expects new deliveries every year does not.

Diligence teams test the claim from both directions. They check whether the cost category appears in prior years, and they ask management whether similar work is planned.

Cost-by-cost view of likely treatment#

Cost-by-cost treatment depends on the facts, but most preparation spending falls into a handful of familiar patterns. Use the table as a starting point for the conversation with your quality of earnings provider.

Two rows cause most disagreements. Privacy preparation looks one-time until the second package arrives, and allocated staff time looks real to management but adds nothing to cash costs, which is what buyers are trying to measure.

The matching problem: revenue and costs move together#

Costs to earn license revenue move with that revenue in a normalized view. If buyers treat a one-time license fee as non-recurring and remove it from run-rate EBITDA, the costs to earn it come out too, and the net adjustment may be small.

If the license is multi-year and buyers accept the revenue as recurring, its delivery and preparation costs stay in run-rate. Adding back costs while keeping the revenue is an asymmetric adjustment, and diligence teams look for exactly that pattern.

Timing complicates the picture. Revenue from a license may be recognized in a different period from the one in which preparation costs were incurred, so present each license as a unit, with its revenue and costs side by side across periods.

Why add-backs draw scrutiny in diligence#

Add-backs draw scrutiny because they raise the EBITDA a buyer applies a multiple to and a lender sizes debt against. Every one-time label is a claim the buyer is asked to accept, and unsupported claims tend to be discounted.

Lenders apply their own definitions. Credit agreement EBITDA definitions may permit certain non-recurring costs, sometimes with caps or time limits, and they will not always match a quality of earnings report. Check the facility definition before assuming a cost the buyer accepted also counts for covenants.

Repetition is the most common reason add-backs fail. A company that adds back one-time data costs in consecutive years is describing a program, whatever the label says.

Documentation checklist for data licensing add-backs#

Documentation for an add-back should be built while the work happens. Reconstructing support during diligence is slower and less convincing, and it invites the question of why the cost was not tracked in the first place.

Ask the quality of earnings provider early which categories it expects to accept. A short conversation before the sale process starts lets you close gaps in support while the invoices, and the people who approved them, are still easy to find.

• 1A project code or separate general ledger account for each license.
• 2Invoices from counsel, contractors and tooling vendors tagged to that code.
• 3Time records for any incremental internal hours, such as overtime or temporary staff.
• 4A board or management approval describing the project as discrete.
• 5The license agreement, showing term, delivery obligations and any refresh schedule.
• 6A note stating whether further licenses or deliveries are planned.
• 7A reconciliation showing each license's revenue and costs together.

Illustrative: a 3PL's first license meets a quality of earnings review#

Illustrative: a fictional PE-backed 3PL licenses warehouse exception records from a WMS it retired after a migration, together with linked customer service tickets about damaged and short shipments. Preparation includes outside counsel's review of older warehousing agreements, a contract data engineer for the legacy export, redaction tooling and time from existing operations supervisors.

The CFO books external costs to a dedicated project code from the start and asks the supervisors to log hours. When the company prepares for sale, the quality of earnings provider accepts counsel, contractor and tooling costs as non-recurring, because the license covers a single delivery from a system that no longer exists, and it removes the license fee from run-rate revenue.

Outcome: the supervisors' allocated time is rejected as an add-back because no incremental cost was incurred. When the company later signs a second license from its current WMS, the CFO books those costs as ordinary operating expense, consistent with licensing becoming a recurring activity.

How SourceX keeps preparation costs visible#

The SourceX Enterprise Data Value Framework lists preparation cost and privacy burden among the drivers that lower net value, which is why SourceX weighs them package by package rather than as general overhead. The SourceX five-step transaction separates Supply, Rights, Preparation, Approval and Delivery, which gives the CFO natural points to close out costs for each license.

The SourceX Evidence Packet documents scope, permitted use and release authorization for each package. That record supports the one-time or recurring story a CFO needs in diligence, because it shows what was delivered and whether further deliveries are expected.