Group CFO checklist before the first data license in a portfolio

Why the first license needs a group-level checklist#

The first data license in a portfolio needs a group-level checklist because it sets precedents the CFO will live with on every later deal: which entity contracts, how proceeds are treated, what lenders are told and how the revenue shows up in reporting. Decisions made quickly for one company become the group template by default.

This checklist is general information. Revenue recognition, tax and covenant questions depend on the specific contract and structure, so take them to the group's auditors, tax advisors and counsel before relying on any answer.

The checklist, by area and owner#

The checklist covers entity, covenants, consents, revenue recognition, tax, transfer pricing, cash routing, costs, reporting and records, and each item has a single owner. One owner per item keeps the checklist from stalling between finance, legal and the operating company. Fill it in once at group level, then copy it for each company that follows.

Entity: who signs and who receives#

The supplier is the operating company that holds the records, so that company signs the license and receives payment. A holding company that signs for a subsidiary without clear authority raises questions about who granted the rights, who carries liability and where the revenue belongs.

If the holding company coordinates packages from several subsidiaries, keep a separate license or schedule for each entity, and record any services the holding company provides under an intercompany agreement. The separation also makes it easier to sell one company later without unwinding a group-wide contract.

Covenants and consents at each level#

Covenants can sit at more than one level of the structure: an operating company facility, a holding company facility and investor documents with their own consent rights. A license permitted under one may need consent under another.

Many credit agreements permit ordinary-course non-exclusive licenses without consent, but qualifiers such as consistency with past practice can make a first-ever license unclear. Where the answer is uncertain, a written confirmation from the lenders' agent removes doubt before signing.

• 1Credit agreements at each borrower level: disposition, lien, investment, affiliate and restricted payment covenants.
• 2Security agreements: limits on licensing collateral.
• 3Shareholder or LLC agreements: reserved matters and sponsor consent rights.
• 4Board delegation of authority: the limits on what officers may sign without the board.
• 5Material customer and vendor contracts: data-use restrictions that could turn a license into a breach.

Revenue, tax and cash: questions for advisors#

Revenue recognition for a data license depends on what is promised and when it is delivered. Questions for auditors include whether the license and any delivery or update obligations are separate performance obligations under ASC 606, and how milestone or usage-based payments are treated. Ask too whether the buyer receives a right to use records as delivered or a right to access records that keep updating, since that can change the timing of recognition, and whether any part of the fee relates to services rather than the license itself.

Tax questions include how the income is characterized, whether sales or use tax applies to data or digital products in the relevant states, whether withholding applies to payments involving foreign parties, and how preparation costs are treated. Answers vary by state and structure, so do not assume one company's answer carries over to another.

Cash routing is easy to overlook. If the operating company's accounts sit under an account control agreement or a cash sweep, license receipts flow through them like any other revenue, and lenders will expect to see them in reporting.

What to settle now and what can wait#

Items that affect validity, consents or cash must be settled before the first license is signed; items about presentation and standardization can wait until a second or third license shows a pattern worth standardizing. Not every item needs a final answer on day one.

Resist building a full group policy before any company has finished a fit check. A policy written in the abstract tends to answer questions nobody asks and miss the ones the first deal raises.

Illustrative: a holding group sets the template#

Illustrative: a fictional vertical software holding group with seven operating companies receives a proposal to license support and engineering records from one of them, a field service software company. The group CFO decides to treat the first deal as the template for any that follow.

The CFO confirms that the operating company will sign and receive payment, and that the group's own services are covered by an existing intercompany agreement. Counsel reads the operating company facility and the holding company facility; one expressly permits ordinary-course non-exclusive licenses, the other is silent, so the CFO asks that lender for confirmation. Auditors review the draft structure before payment terms are discussed, and the tax advisor flags a sales tax question tied to the delivery method.

The CFO turns the answers into a one-page group policy. When a second company considers a license, the group-level items are already settled, and only the company-specific ones remain.

How SourceX works with finance teams#

SourceX runs each license as a separate transaction for the supplier entity, using the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. There is no SourceX price list; value is known only when a buyer engages with a specific package.

For each package, the SourceX Evidence Packet gives finance teams and auditors a record of provenance, licensing rights, permitted use, the privacy record and release authorization, which supports the filing and diligence items on the checklist.