A CFO checklist for evaluating a data licensing agreement

What the CFO owns in a data licensing agreement review

Counsel reads a data licensing agreement for enforceability and liability; the CFO reads it for money, timing, obligations and what the company gives up. Split the review that way and the finance side fits on one page: scope, exclusivity and term, field of use, price and payment timing, de-identification, termination and assignment, and accounting and reporting.

The checklist

Work through it with the draft agreement, the company's data inventory and the cash forecast open side by side.

Scope and exclusions

• The agreement names the systems, date ranges and record types covered, and they match the company's data inventory line by line.
• Excluded categories are listed by name, for example customer-identifying details, price files, HR records and privileged legal communications.
• There is a process for records found later that fall outside the agreed scope.
• Delivery volume and format are defined well enough to budget the preparation effort.

Exclusivity, term and field of use

• Exclusivity is limited to AI training, with a stated start date and end date.
• The company's own internal use of its data is expressly preserved.
• The field of use says what the buyer may do; everything else is reserved to the company.
• You have listed the opportunities the exclusivity blocks, and the owner has accepted that trade in writing.

Price and payment timing

• The price is one all-in figure, with SourceX's fee included and no separate charges.
• The payment trigger is explicit. Under SourceX's process the company receives a one-time payment, typically within about 60 days of invoicing once the buyer selects the data.
• Taxes, currency and the invoicing entity are named.
• The cash forecast uses the expected payment date, not the signing date.

De-identification and delivery

• Redaction and de-identification requirements are written down and were agreed before any preparation work began.
• The agreement says who performs that work and who pays for it, and you have estimated the internal hours.
• Nothing is delivered before the agreement is executed and the company authorizes delivery.
• Transfer security and the buyer's handling obligations are specified.

Termination, assignment and change of control

• You know what survives termination, including the buyer's rights to data already delivered and confidentiality.
• You know whether the license binds a future acquirer and whether the company may assign it.
• Any notice or consent needed on a change of control is listed in the closing checklist for a future sale.

Accounting, covenants and reporting

• Revenue recognition has been discussed with the auditors before signing. Under ASC 606, a license of intellectual property is recognized at a point in time or over time depending on whether it gives a right to use the IP as it exists or a right to access it throughout the term; Deloitte's roadmap chapter on the nature of a license sets out the analysis.
• Lender treatment is checked against the credit agreement's EBITDA definition; see whether data licensing income counts toward covenant EBITDA.
• The board pack presents the income as one-time and explains the exclusivity; the board presentation guide suggests a structure.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

How to read the results

Red flags in a draft agreement

• Scope defined as all company data, with no schedule of systems or dates.
• Exclusivity with no end date, or covering every use rather than AI training.
• Delivery due before signature, or before redaction rules are agreed.
• Charges or deductions on top of the agreed all-in price.
• No restriction on attempts to re-identify people in the data.
• Payment that depends on how the buyer's models perform later.

Reading a headline contract value

Reported deal figures are easy to misread. Reddit's February 2024 Form S-1 disclosed data licensing arrangements with an aggregate contract value of $203.0 million over terms of two to three years, of which it expected to recognize a minimum of $66.4 million in 2024. A contract value is a multi-year total, not one year's revenue. Apply the same discipline to your own board materials: show the price, the payment date and the recognition pattern separately.

If you introduced the company, disclose it first

A fractional CFO who referred the company as a SourceX partner has a financial interest in the deal closing. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and the reward becomes payable only after the buyer pays and SourceX receives its fee. The reward never reduces what the company receives, but the owner should still know about it before you review the terms. A written notice built from these sample disclosure clauses does the job, and your client NDA governs what you share along the way; the NDA disclosure question is answered separately.

Next step

If the company has not yet decided whether to license at all, start with the ten go or no-go questions to answer first. Advisors who want to bring qualifying clients to SourceX can register as a partner, and the partner page for fractional CFOs covers the rest of the role.