Which entity should book data license revenue in a holding structure?

The default: the record owner signs and books#

The default licensor in a holding structure is the operating company that created the records and holds the rights to them. That company's customer contracts, vendor terms and employee notices decide what can be licensed, so it is the entity able to give the representations a licensee will ask for.

Revenue follows the contract. If the operating company signs, the operating company books the revenue, and the group sees it on consolidation. Signing at a different entity without an intercompany license leaves a gap in the chain of rights that a licensee's counsel, or a later acquirer, will find.

The holdco still has a role. It often approves the license under a group policy, coordinates counsel and sets common terms. Approving and coordinating are not the same as being the licensor.

Five tests for choosing the licensor entity#

Five tests settle most entity choices. When all five point to the operating company, there is no reason to sign anywhere else. When they split, counsel and the group CFO decide which test controls and paper the gap with intercompany agreements.

When records sit in a shared-services entity#

Records in a shared-services entity are the main exception to the default. Software holding companies often run a central support desk, hosting team or engineering group that serves several products, so tickets and code reviews may sit in an instance the services entity owns.

Owning the instance is not the same as owning the content. The services entity usually processes records on behalf of the operating companies, whose customer agreements govern the underlying data. Three structures are common.

• 1Operating company as licensor: each product company licenses its own records, and the services entity performs export and preparation under an intercompany services agreement.
• 2Services entity as licensor: each operating company grants the services entity an intercompany license, and the services entity licenses outward.
• 3Holdco as master licensor: the holdco signs one external license, and each subsidiary grants the holdco an intercompany license.

Which structure fits which group?#

The operating company structure is the simplest and keeps revenue next to the rights, so it suits groups where each company has its own customer agreements and approvals. The other two suit a licensee who wants one contract across several products, at the cost of more paperwork.

A master license through the holdco needs an intercompany license from each subsidiary, approval in each subsidiary, and a decision about how warranties flow back down. A services-entity license needs the same grants and raises the question of whether the services entity has the substance to stand behind them.

Whichever structure the group chooses, write it into the group data licensing policy so the next license follows the same path. Auditors and buyers care more about consistency across licenses than about which structure was picked.

Booking revenue when the holdco signs for several subsidiaries#

When the holdco signs for several subsidiaries, the holdco books the external revenue and each subsidiary earns an intercompany royalty or fee. That intercompany price needs support, because it moves profit between entities that may have different lenders, minority holders or tax positions, and cross-border groups add transfer pricing review.

Revenue recognition is assessed at the booking entity. Under ASC 606, licenses of intellectual property are classified as functional or symbolic. A license to functional IP is generally a right to use the IP as it exists when granted, recognized at a point in time, while a license to symbolic IP is a right to access recognized over the license period. How a dataset license fits is a judgment for the group's accountants, based on the contract terms.

Earnouts add one more test. If an acquired subsidiary's sellers earn payments on its revenue, booking license revenue at the holdco instead of the subsidiary can start a dispute. Choose the entity with the earnout definition in front of you.

Illustrative: a vertical software holdco with a shared support desk#

Illustrative: a fictional software holding company owns four vertical products for property managers, construction estimators, field inspectors and equipment dealers. Each product has its own operating company and customer agreements, but all support runs through one Zendesk instance owned by a shared-services subsidiary, and two of the products share one GitHub organization.

A developer asks to license support conversations linked to engineering fixes across all four products. The group CFO applies the five tests: rights sit with each product company, the systems sit with shared services, and the credit agreement covers every entity.

Decision: each product company signs as licensor for its own records, the shared-services subsidiary performs exports under an amended services agreement, and the holdco signs only a coordination letter. Outcome: revenue lands where the customer contracts sit, and each product's earnout calculation stays clean.

Entity mistakes that surface in diligence#

Entity mistakes rarely stop a license from being signed, but they surface at the next audit, refinancing or sale, when someone rebuilds the chain of rights from the contracts.

• 1The holdco signs for records it does not own and holds no intercompany license for.
• 2Revenue books at one entity while preparation costs sit at another.
• 3A non-guarantor subsidiary licenses records without a check of investment and disposition covenants.
• 4Records from an acquired company merged into another subsidiary carry old contract restrictions that nobody reviews.
• 5Minority shareholders at the operating company are not consulted where their agreement requires it.

How SourceX identifies the supplier entity#

SourceX identifies the supplier entity at the fit check by asking which legal entity holds the records, which entity is party to the relevant contracts and who can sign. In the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, that answer shapes the Rights and Approval steps.

The SourceX Evidence Packet records provenance and licensing rights for the named supplier, along with release authorization. Where a holdco or shared-services entity is involved, the packet shows the intercompany grants that connect the records to the signing entity.