Who pays for data licensing preparation: fund, holdco or portfolio company?

The default rule: costs follow the entity that benefits and signs#

The entity that benefits from a data license and signs it should pay to prepare it, and in most portfolios that is the operating company. The operating company owns the support tickets, job records or order history, holds the customer contracts that govern them, and books the license revenue.

Keeping cost and revenue in one entity keeps the economics honest. If the holdco pays for redaction while the portfolio company keeps the fees, the portfolio company's margin looks better than it is, and someone has to unwind that later in diligence or in an earnout calculation.

Exceptions exist, but each needs a reason that can be written down: shared benefit across several companies, a shared-services entity that holds the systems, or a fund-level purpose the fund documents permit.

Cost types and their typical bearer#

Cost types sort cleanly once you ask who receives the benefit of each one. The table shows the usual starting point, which fund documents, credit agreements and intercompany agreements can change.

Two rows deserve a note. Lender consent costs usually sit with the borrower even when the sponsor negotiates the consent, because the facility and its fees belong to the borrower group. Operating partner time is the row most likely to be challenged, since partnership agreements differ on whether operating partners are adviser staff or outside consultants whose fees a portfolio company may pay.

When should the holdco carry the cost?#

The holdco should carry a cost when the work benefits several companies at once and cannot be split cleanly when it is done. A portfolio screen, a group policy, a shared template library or one counsel engagement covering common contract terms all fit that description.

Holdco spending still needs a final home. Most groups charge it back to participating companies under an intercompany services agreement, using an allocation key chosen before the work starts rather than after results are known.

If the records themselves sit in a shared-services entity, such as a central support desk serving several brands, the cost question links to the licensor question. Settle which entity signs the license first, then charge the services entity's export and preparation work to that licensor.

• 1Equal shares among participating companies, for policy and template work.
• 2Share of record volume or package size, for shared tooling and storage.
• 3Logged hours per company, for shared counsel or data engineering time.
• 4Share of license revenue, applied only once revenue exists and only if agreed in advance.

Why fund-level charges need the most care#

Fund-level charges need the most care because the partnership agreement, not convenience, decides what a fund may pay. Partnership agreements typically separate fund expenses, management company expenses and portfolio company expenses, and investors read those lists closely.

Expense allocation between advisers, funds and portfolio companies has long been a focus of regulatory examinations of private fund advisers and of investor due diligence. Operating partner fees, consultant costs and broken-deal expenses draw frequent questions. A data program adds a new category, so the fund CFO and chief compliance officer should settle its treatment before the first invoice arrives.

• 1Read the expense provisions of the partnership agreement and any side letters.
• 2Check whether fees a portfolio company pays the adviser or its affiliates offset the management fee.
• 3Confirm the allocation policy covers co-investment vehicles and continuation funds.
• 4Describe the treatment consistently in investor reporting.
• 5Keep invoices, time records and the allocation key in one file.

Illustrative: one fund, three companies, one program#

Illustrative: a fictional lower-middle-market fund owns a home services platform running ServiceTitan, a 3PL running a WMS alongside NetSuite, and a vertical software company running Jira and Zendesk. The operating partner proposes a data licensing program and asks the fund CFO how to pay for it.

The CFO sets three rules. The adviser absorbs the operating partner's time. The platform holdco pays for the portfolio screen and a shared policy, then charges both back equally to the companies that proceed. Each company pays its own exports, redaction and counsel review.

Outcome: the software company proceeds first, and its license revenue and preparation costs sit in the same entity. The 3PL pauses after the screen and carries only its share of the policy cost. The allocation memo is filed with the fund's expense records and reused when the home services platform joins later.

Allocation mistakes that cause trouble later#

The most common allocation mistake is paying portfolio company costs from whichever entity has cash on hand. It feels efficient at the time and leaves an undocumented intercompany balance that surfaces at the next audit, refinancing or exit.

Each of these mistakes is cheap to prevent at the start of a program and expensive to unwind at exit, when a buyer's diligence team rebuilds the cost history company by company.

• 1Charging operating partner time to a portfolio company without authority in the fund documents.
• 2Leaving preparation costs in one company while the revenue lands in another.
• 3Delivering holdco services with no intercompany agreement or allocation key.
• 4Skipping a project code, so costs cannot support net proceeds, add-backs or an earnout calculation.
• 5Choosing the allocation key after results are known.

How SourceX keeps costs tied to the supplier#

SourceX runs each license as a separate transaction for one supplier entity, using the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Because each package has one named supplier, its preparation work and its revenue attach naturally to the same company.

The SourceX Enterprise Data Value Framework counts preparation cost and privacy burden as factors that reduce net value, so tracking those costs per package is part of deciding whether a package is worth pursuing. The SourceX Evidence Packet names the supplier entity and its release authorization, which gives the fund CFO a clean reference for allocation.