Private equity and portfolios
Intercompany data license between a holdco and a subsidiary: key terms
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
An intercompany data license between a holdco and a subsidiary is a written agreement in which the operating company that holds the records grants the holdco defined rights to use or sublicense them. The most important rule: the subsidiary stays the licensor, and the agreement must say what happens to those rights when the subsidiary is sold.
Key takeaways
- The subsidiary that holds the records and the customer contracts is normally the licensor, even when the holdco owns all of its shares.
- Scope should name record families, source systems and date ranges rather than a general reference to company data.
- Related-party fees generally need arm's-length support, so document how the fee basis was chosen with tax advisers.
- Termination on sale of the subsidiary is the term most often left vague, and a buyer's counsel will read it closely.
- Sublicenses to outside AI developers should require the subsidiary's written sign-off for each buyer and use.
When does a holdco need an intercompany data license?#
A holdco needs an intercompany data license whenever it wants to use, combine or sublicense records that a subsidiary holds. Owning the subsidiary's shares gives the holdco control of its board, but it does not by itself move the subsidiary's records, contracts or intellectual property up to the parent.
The question usually comes up in three situations. The group wants a central team to negotiate with outside AI developers on behalf of several companies. The holdco wants to build shared tools on records from more than one subsidiary. Or a lender, minority investor or auditor asks how value moves between entities.
Without a written license, the group can end up with the holdco signing an outside license for records it does not hold. That gap is usually the first thing a buyer's counsel questions, and it is far easier to close before an outside deal than during one.
Key terms at a glance#
The key terms of an intercompany data license fit on one page, and a group CFO should be able to read that page without opening the full agreement. The table lists the terms that matter most when records will be licensed onward to AI developers.
| Term | What to decide | Why it matters |
|---|---|---|
| Licensor entity | The subsidiary that holds the records and the contracts they came from | Rights flow from the entity that collected the records, not from the parent |
| Licensee | The holdco or a dedicated group licensing entity | The licensee is the party that will sign with outside buyers |
| Licensed records | Named record families, source systems and date ranges | Vague scope invites disputes and over-delivery |
| Permitted use | Internal tool building, sublicensing to outside developers, or both | Each use raises different rights and privacy questions |
| Sublicensing | Whether the subsidiary approves each outside buyer and use | Keeps the operating company in control of its own records |
| Fee basis | Share of outside income, fixed fee or cost-plus | Decides where income lands inside the group |
| Arm's-length support | How the fee basis was chosen and by whom | Related-party terms draw tax and lender scrutiny |
| Derived materials | Who holds prepared datasets, labels and documentation | Cleaned, documented datasets take real work and are often what a buyer actually receives |
| Termination on sale | What ends, what survives and who keeps derived materials | Shapes diligence when the subsidiary is sold |
AI-specific terms that ordinary intercompany licenses miss#
AI-specific terms govern what happens after records reach a model developer, and most intercompany license templates were written for trademarks or software rather than training data. If the holdco will sublicense records outward, the intercompany license has to carry the same limits the subsidiary would demand if it signed with the developer directly.
These terms should flow down word for word into every outside license. If the holdco agrees to something broader with a buyer than the subsidiary granted to the holdco, the difference becomes the holdco's exposure.
- Training-only scope: records may be used to train and evaluate models, not republished or redistributed as a dataset.
- No onward resale: the outside developer may not pass records to other model builders.
- Model and output rights: the license states whether the subsidiary keeps any claim to models, weights or outputs.
- Privacy warranties: who warrants that personal and confidential details were removed, and on what review.
- Survival: which obligations, such as confidentiality and deletion, continue after the license ends.
- Audit and deletion: how the subsidiary can confirm that its limits were followed.
How should the fee basis be set?#
The fee basis for an intercompany data license should mirror how outside licenses are priced and how the subsidiary bears its costs. Related-party transactions are commonly reviewed under transfer pricing rules, which generally expect terms that unrelated parties would accept, so the choice needs a short written rationale.
| Fee basis | When it fits | What to document |
|---|---|---|
| Share of outside license income | The holdco sublicenses to outside developers case by case | How the share was chosen and which costs come off first |
| Fixed annual fee | The holdco uses records for internal tools across the group | The comparable or cost evidence behind the amount |
| Cost-plus for preparation | The subsidiary performs export and privacy work for the holdco | Time and cost records for the preparation work |
| No fee, with board approval | Small internal pilots with no outside income | Board minutes, tax advisers' view on whether a charge may still be expected, and a review point before any outside use |
What happens when the subsidiary is sold?#
Termination on sale of the subsidiary is the term that decides whether an intercompany data license helps or hurts an exit. A buyer acquiring the subsidiary will want to know what rights the former parent keeps, which outside sublicenses are still running and who holds the prepared datasets.
Groups generally choose among three approaches. The license ends at closing and sublicenses already granted run to the end of their own term. The license ends and the holdco assigns active sublicenses to the subsidiary. Or the license continues for a wind-down period agreed with the buyer. Whatever the choice, the agreement should say who keeps cleaned exports and documentation and require deletion of copies the holdco no longer needs.
Write this term before any outside license is signed. Renegotiating it during a sale process, with a bidder watching, costs leverage.
Illustrative: a software holding group sets up its first intercompany licenses#
Illustrative: a fictional holding group owns three acquired vertical software companies serving fleet maintenance shops, property managers and event venues. Each runs its own Jira, GitHub and Zendesk instances. The group CFO wants one central team to handle outside licensing of engineering and support records.
Counsel drafts a short intercompany license for each subsidiary. Each names the licensed systems and date ranges, excludes the product databases that hold customer records, requires the subsidiary CEO's written sign-off for every outside buyer and sets the fee as a share of outside license income after preparation costs. Termination on sale lets running sublicenses finish and hands prepared datasets back to the subsidiary.
When the group later sells the event-venue business, the buyer's counsel reviews one agreement and one schedule of sublicenses instead of reconstructing who agreed to what from email.
How SourceX handles holdco and subsidiary licensing#
SourceX treats the entity that holds the records as the supplier in the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. When a holdco is the contracting party, the Rights step traces the chain from the subsidiary's systems and contracts through the intercompany license to the entity that signs.
That chain is recorded in the SourceX Evidence Packet under provenance, licensing rights, permitted use, the privacy record and release authorization, so the holdco, the subsidiary and the outside developer work from the same account of who approved what. Drafting the intercompany agreement itself stays with the group's counsel and tax advisers.
Frequently asked questions
Does a wholly owned subsidiary still need its own license agreement?
Usually yes. Full ownership gives the holdco control, but the subsidiary remains a separate legal entity that holds its own records and contracts. A written license documents the rights the holdco is using, protects the subsidiary's directors and makes the arrangement easy to show to lenders, auditors and future buyers.
Should the holdco or a separate entity be the licensee?
Either can work. Some groups use the holdco directly because it already signs group contracts. Others create a dedicated licensing entity to keep outside license income, liabilities and records separate. The choice depends on tax, lender and liability considerations that your advisers should review for your structure.
Can the holdco combine records from several subsidiaries into one package?
It can if each subsidiary has licensed its records for that use, but combining rarely adds value on its own. Outside developers usually want well-documented packages by record type. Each subsidiary's scope, exclusions and privacy record still need to travel with its part of any combined delivery.
Do lenders need to approve an intercompany data license?
They may. Credit agreements often restrict transfers or licenses of intellectual property between group entities, or require certain assets to stay with the borrower. Check the covenants and security documents before signing, and ask counsel whether a lender consent or notice is needed.
What changes if the subsidiary has minority shareholders?
Minority shareholders change the analysis because the subsidiary's directors generally owe duties to all shareholders, not only the holdco. Fee terms that look generous to the parent can be challenged. Independent approval, a written fee rationale and disclosure to minority holders are common protections to discuss with counsel.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.