# Who can license renewal reconciliation records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-contract-renewal-scope-reconciliation-records
Last updated: 2026-11-04

Introduce the CEO (in a founder-led company, usually the owner), and ask the commercial operations director to sponsor the conversation. The director runs vendor renewals, knows where renewal drafts, asset histories, approvals and invoice checks are kept, and can explain the work. The CLM administrator, the IT asset manager and any advisor with repository access can describe records but cannot agree to license them. Vendor confidentiality terms go to counsel, and what can actually be licensed stays unknown until SourceX's rights review.

This decision tree is part of the [contract renewal scope reconciliation guide](/guides/workflow-contract-renewal-scope-reconciliation). It answers one question for sourcing advisors and procurement consultants: when a company has years of evidence showing how it trimmed vendor renewals to match what it actually used, who is allowed to say yes to a conversation about that history?

## Map each renewal record to the person who holds it

Renewal reconciliation crosses four departments, and each holds a different piece. Start by naming the holders, then mark which of them carries authority. Most do not.

| Record | Usual system | Day-to-day holder | Can authorize a licensing talk? |
|---|---|---|---|
| Renewal drafts and vendor quotes | Contract repository, email attachments | Procurement or commercial operations | No, describes only |
| Opt-out dates and renewal calendar | Renewal fields in the contract system | Contract system administrator | No, describes only |
| Asset and consumption histories | Asset register, vendor usage portals | IT asset manager | No, describes only |
| Approved scope and sign-offs | Approval log, procurement tickets | Commercial operations director | Sponsors; rarely signs |
| Invoice checks against approved scope | ERP, accounts payable | Controller | No, describes only |
| Notice and opt-out letters | Contract repository, legal inbox | General counsel | Advises the CEO |
| Vendor agreements and their confidentiality clauses | Contract repository | General counsel | Advises the CEO |

Two documented tool behaviors show why the contract system administrator is a useful describer. Ironclad's Vendor Renewals dashboard view by default shows agreements whose expiration or opt-out date falls within the next 90 days, so the administrator knows what is coming up. In ServiceNow's contract renewal workflow, an asset selection step adds or removes assets from the renewal and shows what carried over. The administrator can tell you whether those fields and steps were used, and from which year. That is description, not permission.

## Walk the tree: five questions that find the signer

Ask these in order, ideally in one conversation with the commercial operations director. Each answer moves the introduction one box down.

1. **Were superseded drafts and asset changes kept?** If only signed renewals survive, there is little to describe: the reconciliation lived in the drafts, the retirements and the approval. If the earlier versions exist, continue.
2. **Who would sponsor a data licensing discussion?** The CFO if the director frames it as a revenue line, the COO if procurement reports into operations, the owner in a founder-led company. Get a name, not a title.
3. **Are the records only about the company's own purchasing?** Usually yes, which keeps the path short. If procurement runs buying for affiliates or a parent, the parent's finance lead becomes a box on the tree.
4. **Do vendor agreements carry confidentiality terms over pricing or scope?** Many do. Note that they exist and move on; reading them is counsel's job, not yours.
5. **Should any function stay out entirely?** Some companies want to keep, say, legal's notice correspondence out of any discussion. That is allowed; see [whether a company can exclude particular departments](/questions/can-a-company-exclude-particular-departments-from-a-licensing-discussion).

The lit path in the graphic ends at the CEO, with the sponsor and counsel beside them. That is who the introduction should reach. Access to a contract system, a shared drive of reconciliation worksheets or a vendor portal, whether it belongs to an analyst or an outside advisor, is never authority to discuss licensing.

## Vendor terms: the branch only counsel can close

Renewal records describe deals with other companies. That makes one branch of the tree belong to counsel, and a partner should flag it, not try to resolve it.

| Branch | Why it needs review | Who decides | Common outcome |
|---|---|---|---|
| Vendor pricing in quotes and invoices | Confidentiality clauses often cover commercial terms | General counsel | Prices removed or banded |
| Vendor names on drafts and approvals | Some agreements restrict naming the relationship | General counsel | Vendors pseudonymized |
| Usage reports downloaded from vendor portals | The portal and its data may belong to the vendor | General counsel, per agreement | Excluded or summarized |
| Employee names in approval chains | Personal data where privacy law applies | Counsel and privacy lead | Roles kept, names removed |
| Contracts under dispute or legal hold | Cannot be altered or moved | General counsel | Left out |

The employee row is easy to overlook. Approval chains name buyers, approvers and asset managers, and where EU law applies, the GDPR treats any information relating to an identifiable person as personal data. Roles usually carry the meaning; names rarely need to.

None of these ends the conversation. They decide scope. [Why data rights matter](/proof/why-data-rights-matter) explains how SourceX treats rights before anything else, and [customer contract data use restrictions](/guides/customer-contract-data-use-restrictions) covers the parallel case where the counterparty is a customer rather than a vendor.

## Three companies, three paths (Illustrative)

The tree produces different introductions depending on how purchasing is organized. All three companies are fictional.

| Question | 300-person founder-led distributor | 900-person logistics company | 1,400-person portfolio company of a buyout fund |
|---|---|---|---|
| Who describes the records? | Office manager and IT lead | Commercial operations director and contract system administrator | Group procurement lead and IT asset manager |
| Who sponsors? | Owner | Commercial operations director | Group procurement lead |
| Who signs? | Owner, as CEO | CEO | CEO, with sponsor consent |
| Counsel branch | Outside counsel reads the largest vendor agreements | General counsel, vendor pricing clauses | General counsel and the fund's counsel |
| Other consent | None | None | Private equity sponsor |
| Route length | One person | Two people | Three people plus sponsor consent |

The distributor's route is short but its records are thin: renewals were reconciled in email. The logistics company has used a contract system since a known year and an asset register older than that, so its history is richer and its route still short. The portfolio company has the most structured history, often because a sponsor pushed renewal discipline, as described in [SaaS renewal management for portfolio companies](/guides/saas-renewal-management-portfolio-companies), and the longest route.

## Left open until SourceX's rights review

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

- **Rights:** which record classes and years the company can license once vendor terms are read.
- **Preparation:** how vendor names, prices and employee names are removed or de-identified.
- **Demand:** whether any buyer wants vendor renewal reconciliation 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, systems and owners. Do not export a renewal, copy a quote or pull a worksheet to prove the point. The [referral brief template](/resources/contract-renewal-scope-reconciliation-referral-brief-template) puts the tree's answers on one page, the [records across systems map](/guides/contract-renewal-scope-reconciliation-records-across-systems) shows how the record sets join, and [procurement and vendor workflows](/data-types/procurement-and-vendor-workflows) describes the wider record type.

## 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 commercial operations director has agreed to bring in the CEO, who can say yes, and flagged any vendor terms for counsel, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://support.ironcladapp.com/hc/en-us/articles/40074088867863-Vendor-Renewals-View-on-the-Dashboard
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1603681
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
