# Who can license covenant correction records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-covenant-reporting-corrections-records
Last updated: 2026-11-04

Introduce the CEO of the lending business, usually with the chief credit officer's support, and ask the credit operations or portfolio monitoring head to start the conversation. That head knows where certificates, calculation versions and clarification threads live and how complete they are, but rarely has authority to approve a licensing discussion. General counsel reads the credit agreement confidentiality terms. Platform administrators and analysts have access, not authority, and what can be licensed stays unknown until SourceX's rights review.

This decision tree is part of the [covenant reporting corrections guide](/guides/workflow-covenant-reporting-corrections). It answers one question for loan systems consultants: when a lender has years of covenant tests that were corrected, queried and signed off, who can say yes to a conversation about that history?

## Who holds covenant correction records, and who only describes them

The records are spread across credit, servicing and legal. Most holders can describe their piece accurately. Few can commit the lender.

| Record | Usual system | Day-to-day holder | Role on the tree |
|---|---|---|---|
| Compliance certificates and schedules | Document portal | Loan servicing | Describes only |
| Calculation spreadsheets, all versions | Spreadsheet library or covenant module | Credit analysts | Describes only |
| Clarification threads | Portal messaging, email | Relationship managers | Describes only |
| Covenant definitions and test results | Loan platform | Credit administration; platform administrator | Describes only |
| Correction coverage and gaps across all of the above | All systems | Credit operations or portfolio monitoring head | Starts the conversation |
| Determinations, waivers and amendments | Credit approval system, loan file | Chief credit officer and credit officers | Supports the CEO's decision |
| Credit agreements and their confidentiality terms | Legal files | General counsel | Advises; decides scope with the signer |

Each of those systems is run by people who can tell you a great deal about what it holds. That is why the credit operations head is the right first contact, and why they are not the last one.

## The yes path: questions in order

Work through these with the credit operations head. Each answer either moves the introduction forward or adds a box to the tree.

1. **Are superseded calculation versions and threads kept?** If only final results survive, the correction history is thin; note that and stop. Where analysts keep calculations in a SharePoint library, ask whether versioning is on and what the limit is: a library keeps only up to a set maximum number of versions and deletes the oldest when it reaches it. If versions exist, continue.
2. **Whose records are they?** For a bank or a specialty finance company, the lender's own. For a fund, ask whether the records belong to the fund, its manager or a third-party servicer before anyone discusses scope. A servicer's administrator can explain exports but cannot license the fund's records.
3. **Who would authorize a data licensing discussion?** The CEO of the lending business; the CFO or president often sponsors it. Get a name.
4. **Does the chief credit officer need to be in the room?** Usually yes. The corrections document how the lender read its own definitions; the credit officer will want a say in how that is described.
5. **What do the credit agreements say about borrower information?** Most carry confidentiality provisions. Note that they exist; counsel reads them.
6. **Is anyone else's consent needed?** A parent bank, a fund's investment committee or a board. Note it.

The lit path in the graphic runs from the credit operations head through the ownership fork and the counsel gate to the CEO as signer. That is who the introduction should reach.

## Branches that wait for counsel

Covenant files are full of other people's information. These branches belong to counsel, and a partner should flag them, not settle them.

| Branch | Why it needs review | Who decides | Common outcome |
|---|---|---|---|
| Borrower financial figures in schedules and spreadsheets | Credit agreement confidentiality terms | General counsel | Figures scaled, banded or removed |
| Counterparty and sponsor names | Identity of counterparties | General counsel | Pseudonymized |
| Clarification threads naming individuals | Personal data where privacy law applies | Counsel and privacy lead | Names removed, roles kept |
| Facilities in workout or litigation | Disputes and legal hold | General counsel | Excluded |
| Records held by a servicer under contract | Ownership and contract limits | General counsel, per servicing agreement | Scope set by the agreement |

The thread row deserves a note. Where EU law applies, the GDPR treats any information relating to an identifiable person as personal data, and a clarification thread usually names the borrowing company's controller or CFO and the lender's analyst. That shapes preparation; it does not rule the records out.

None of these closes the door. They decide scope, which is what [why data rights matter](/proof/why-data-rights-matter) explains: SourceX reviews rights before anything is licensed.

## Three lenders, three routes (Illustrative)

The same tree produces different introductions. All three lenders are fictional.

| Question | 300-person regional bank commercial lending unit | 180-person private credit manager | 260-person commercial finance company |
|---|---|---|---|
| Who starts the conversation? | Head of credit administration | Head of portfolio monitoring | Credit operations head |
| Ownership fork | The bank | Funds, with records kept by an outside servicer | The company |
| Who sponsors and signs? | The bank's CEO signs; the president of commercial banking and the chief credit officer sponsor | Manager's CEO, with the CFO and fund counsel | CEO, with the chief credit officer |
| Counsel branch | Bank counsel; borrower confidentiality | Fund counsel; servicing agreement and borrower confidentiality | General counsel; borrower confidentiality |
| Other consent | Parent bank approval | Fund governance as documented | None |
| Route length | Three people plus parent | Three people plus servicer and fund | Two people |

The commercial finance company has the shortest route because it owns its records and its systems. The private credit manager may have the richest correction history, with heavy add-back negotiation, and the longest route, because ownership has to be settled before scope. For the borrower's side of a covenant problem, see [options before a covenant breach](/guides/what-to-do-before-breaching-debt-covenant); for the lender audience, see the [referral program for commercial bankers](/for/referral-program-for-commercial-bankers) and [private credit portfolio monitoring](/for/private-credit-portfolio-monitoring-borrower).

## What stays open until SourceX's rights review

Once the signer agrees to talk, these remain, and only SourceX's review answers them:

- **Rights:** which record classes, facilities and years the lender can license once confidentiality terms are read.
- **Preparation:** how borrower figures, names and individuals are removed or de-identified.
- **Demand:** whether any buyer wants covenant correction histories when SourceX reviews them.
- **Terms:** whether an offer follows, and on what schedule.

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company.

Stay at metadata level: record classes, years, facility counts, systems and owners. Do not export a spreadsheet, forward a certificate or screenshot a thread. The [referral brief template](/resources/covenant-reporting-corrections-referral-brief-template) puts the tree's answers on one page, the [worked exception case](/guides/covenant-reporting-corrections-exception-examples) shows what a well-kept correction looks like, and the [covenant compliance certificate template](/resources/covenant-compliance-certificate-template) shows the document the chain starts from.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the credit operations head has agreed to bring in the CEO, who can say yes, and settled whose records they are, [register as a partner](/register), confirm the lender on [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/how-versioning-works-in-lists-and-libraries
