Private equity and portfolios
Lender consent before licensing company data: what credit agreements say
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Lender consent before licensing company data is needed when a credit agreement's negative covenants reach the license and no permitted-license carve-out fits. Read the clauses on asset dispositions, liens, restrictive agreements, affiliate transactions and the security agreement. If consent is needed, send a precise term summary through the administrative agent to the required lenders.
Key takeaways
- Credit agreements regulate data licenses through several general clauses, so a clear disposition covenant does not end the review.
- A permitted-license carve-out applies only if the license meets every qualifier the clause uses, such as non-exclusive and non-interfering.
- Licensee-proposed terms, such as limits on transferring or pledging the records, can trip a restrictive agreements covenant.
- Consent requests go through the administrative agent, and the required lenders usually decide.
- A narrow request naming the license, the clauses and the cash flows gets a cleaner answer than an open question.
What do credit agreements say about licensing company data?#
Credit agreements rarely mention data licenses by name, but they regulate them through general clauses on asset dispositions, liens, restrictive agreements, affiliate transactions and collateral. A license of operational records needs lender consent only when one of those clauses reaches it and no carve-out applies.
Read the clauses as a set. A license can sit inside the disposition carve-out and still trip the liens covenant, or pass both and fail an affiliate test because the licensee shares an owner with the sponsor. The checklist below follows the order most facilities use.
| Clause | Where it usually sits | What to check for a data license |
|---|---|---|
| Asset dispositions | Negative covenants | Whether licenses or grants of rights count as a disposition |
| Permitted licenses | Disposition covenant or Permitted Dispositions definition | Whether the license is non-exclusive, ordinary course and non-interfering |
| Liens and Permitted Liens | Negative covenants and definitions | Whether a license is treated as an encumbrance and which licenses are listed as permitted |
| Restrictive agreements | Negative covenants, sometimes titled burdensome agreements | Whether license terms limit the company's ability to grant liens or transfer the records |
| Affiliate transactions | Negative covenants | Whether the licensee is a sponsor affiliate or a sister portfolio company |
| Line of business | Negative covenants | Whether licensing records is a new activity outside the described business |
| IP covenants | Security agreement | Promises not to license collateral in ways that impair it |
| Notice and reporting | Affirmative covenants | Whether material contracts or schedule updates must go to the agent |
How are permitted-license carve-outs usually worded?#
Permitted-license carve-outs are built from a few qualifiers, and a license has to satisfy every qualifier the clause uses, not most of them. Copy the carve-out into a working document and test the draft license against it line by line.
When a qualifier is ambiguous, shape the license so it fits without argument. That is usually cheaper than debating with lender counsel whether a first data license is ordinary course for a distributor or a field service company.
| Qualifier | What it generally means | Evidence from the license |
|---|---|---|
| Non-exclusive | The company can grant the same rights to others | No exclusivity clause, or a narrow one counsel accepts |
| Ordinary course of business | Consistent with how the company normally operates | Board minutes or a policy treating licensing as a planned activity |
| Does not materially interfere | The business keeps using its records as before | Systems and full records stay put; only a prepared copy leaves |
| Does not impair collateral | The lender's security keeps its value | No ownership transfer, no perpetual grant, fees paid to the borrower |
| Arm's-length terms | Terms an unrelated party would accept | Written terms with an unrelated licensee |
Which clauses do reviews usually miss?#
The clauses reviews most often miss are the liens covenant, the restrictive agreements covenant and the security agreement, because teams stop reading once the disposition covenant looks clear. Each can catch a data license on its own.
Liens matter because many agreements treat a license as an encumbrance on collateral, which is why Permitted Liens definitions often list ordinary course licenses. If that wording is narrower than the disposition carve-out, the narrower test is the one the license must pass.
Restrictive agreements covenants bite on terms the licensee proposes. A clause that bars the company from pledging the records, licensing them in a field or transferring them without the licensee's approval can look like a restriction on the lender's collateral. Read the licensee's first draft with that covenant open.
The security agreement may add its own promise not to license collateral in a way that impairs it, and an intercreditor agreement can give a second-lien or holdco lender a say. If license fees are meant to fund a distribution, check the restricted payments covenant as well.
Who should you ask, and in what order?#
The borrower's deal counsel should read the facility first, and the administrative agent should hear about the license only once the company knows exactly what it is asking for. An open question to lenders invites a broad answer, often with conditions the license never needed.
- Deal counsel reads the credit agreement, security agreement and any intercreditor agreement against the draft license and records the clauses relied on.
- The portfolio CFO confirms covenant headroom, where fees will be deposited and whether any notice or schedule update is triggered.
- The sponsor's financing or capital markets lead knows the lender group and can pre-sound the agent informally.
- The operating partner confirms the license fits the value creation plan and that the portfolio company's board is ready to approve it.
- The administrative agent receives the formal request, circulates it and collects lender signatures.
- The required lenders decide most consent requests; matters such as collateral releases may need a larger group.
What should a consent request to the agent include?#
A consent request to the agent should describe the license so precisely that a lender can approve it without reading the contract. Lenders mainly want to see that the collateral stays in place, the cash stays in the credit group and nothing in the license ranks ahead of their security.
- A one-page term summary: licensee, record families, permitted use, term, exclusivity and territory.
- Confirmation that ownership of the records and systems stays with the borrower and only a prepared copy is delivered.
- How personal and confidential details are removed before delivery.
- The account that will receive license fees, ideally one already under the lender's control arrangements.
- The clauses the company believes apply and the exact consent wording requested.
- A statement that no default exists and that the licensee receives no lien or security interest.
Consent, waiver, amendment or notice: which one applies?#
The right instrument depends on whether the license is permitted, prohibited, already signed or the first of several. Choosing it up front avoids a second round with the lender group.
Check the license's confidentiality clause before sending anything. Many licenses restrict disclosure of their terms, so the draft should expressly permit sharing with lenders, the agent and their advisors.
| Instrument | When it fits | What to watch |
|---|---|---|
| Notice only | The license is permitted but notice or updated schedules are required | A missed notice can be a default on its own |
| Consent | A single license falls outside the carve-outs | Scope it to the named license to avoid wider conditions |
| Amendment | Renewals, refreshes or several licenses are planned | A standing carve-out for non-exclusive data licenses covers later deals |
| Waiver | A license was signed without a needed consent | Negotiated from a weaker position, often with tighter terms |
Illustrative: a regional 3PL reviews a licensee's draft#
Illustrative: a fictional sponsor-backed third-party logistics company runs a WMS and a TMS holding years of order exceptions, carrier claims and resolution notes. A model developer wants to license a prepared copy of the exception records. It borrows under a senior term loan and revolver.
Deal counsel finds a disposition carve-out covering non-exclusive grants that leave normal operations untouched. The licensee's draft, however, bars the company from licensing exception records to logistics software vendors and from transferring the dataset without approval. Counsel flags both terms under the restrictive agreements covenant, and the CFO notices that fees would go to a new account outside the lender's control agreement.
The company drops the transfer restriction, routes fees to its controlled operating account and keeps a narrow field restriction the licensee values. It sends the agent a one-page request naming that clause. The required lenders consent to the named license only, and the CFO adds a data-license carve-out to the list for the next refinancing.
How SourceX handles credit agreement checks#
Within the SourceX five-step transaction, lender consent is checked during Approval, once Rights and Preparation have fixed what will be delivered. Reading the credit documents stays with the company's counsel, because SourceX does not give legal advice.
The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, so counsel can lift the exact scope of a release into a notice or consent request. The release authorization notes which consents were checked or obtained, keeping the lender file and the license file consistent.
Frequently asked questions
Do lenders charge for consenting to a data license?
Sometimes. Lenders may ask for a consent fee, and credit agreements usually make the borrower pay the agent's legal costs for consents and amendments. Whether a fee comes up often depends on how much the request asks of the lenders, so a narrow, well-documented request is easier to approve on ordinary terms.
Will the licensee ask about our credit agreement?
Often, indirectly. Licenses commonly include a representation that signing and performing the license does not breach the licensor's other agreements. Give that representation only after the credit agreement review is complete and any consent is in hand. Some licensees also ask whether their rights survive a lender enforcement, which may need the agent's cooperation.
Does one consent cover later refreshes of the same records?
Not necessarily. A consent tied to a named license may not reach renewals, refresh deliveries or a second licensee. If recurring deliveries are likely, ask for wording that covers renewals and refreshes on the same terms, or seek an amendment adding a standing carve-out for non-exclusive data licenses.
How does an asset-based facility change the review?
Asset-based lenders focus on receivables and inventory, so ask whether license receivables count toward the borrowing base and how they are reported. Many asset-based agreements also let the lender use the company's IP to sell collateral after a default. Confirm the data license does not conflict with that right.
Does the operating partner need to sign anything?
Usually not for the credit facility itself. The borrower signs the consent request and the license, and its board approves the transaction. The sponsor may hold approval rights under the shareholder or LLC agreement, so the operating partner should confirm those are satisfied before the borrower writes to the agent.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.