# Vendor contract ended: the referral questions | SourceX

Canonical: https://refer.sourcex.si/guides/the-referral-questions-after-a-long-term-vendor-contract-ends
Last updated: 2026-11-05

After a long vendor contract ends, a company knows something it did not know before: which records came back, which ones the vendor kept or deleted, and which ones it can show are its own. That settled picture, not the scramble of the exit, is the right moment to ask the CEO whether the company wants to explore licensing. Wait until the return is complete, keep every question at the level of metadata, and let the company confirm its own rights. SourceX reviews rights during qualification.

This page is about the weeks after the end date. The weeks before it, when exports still have to be proved and notice dates still matter, are covered in [the referral review before an enterprise tool contract ends](/guides/the-referral-review-before-an-enterprise-tool-contract-ends).

## What a contract ending sorts, and who does the sorting

A long engagement with a logistics provider, a business process outsourcer, an IT services firm or a software platform leaves records in two places. When it ends, the contract's exit terms decide what is handed back, what the vendor may keep and what is destroyed. The company runs that sorting with its vendor. A partner is never part of it.

Personal data shows how firmly the decision sits with the company. The European Data Protection Board's guidelines on controllers and processors say that at the end of a processing arrangement it is "up to the controller to decide what the processor should do with regard to the personal data", and the processor "should confirm to the controller that the deletion has been completed within an agreed timescale and in an agreed manner". The same excerpt describes the processor deleting or returning the data at the controller's choice and deleting existing copies unless EU or Member State law requires storage (our paraphrase). The guidelines speak only to personal data under EU law, and personal consumer data is usually not what SourceX screens for anyway. The point for a partner is simpler: at contract end, the company's leaders have just been deciding what records the company keeps.

Every record family ends up in one of three places:

| Outcome | What it usually means | Who can tell you |
|---|---|---|
| Came back | The company now holds an export, files or system access it did not have before | Whoever ran the exit for the company |
| Stayed with the vendor | The vendor kept its own working records, or holds copies it must retain by law | The company, from its own exit paperwork |
| Deleted | Copies were destroyed, ideally with written confirmation to the company | The company, if it received that confirmation |

## Why the weeks after the exit suit the question

Before the end date, a licensing question competes with export deadlines and can sound like pressure. Afterward, three things change in the partner's favor.

- **The sorting is done.** The company knows what it holds, so the conversation runs on facts rather than guesses.
- **Records are on the CEO's mind.** Leaders who have just signed off an exit plan have recently thought about which history matters to them.
- **There is no clock left to lean on.** Nothing about the vendor's schedule needs mentioning, which keeps the question honest.

Run a short timing check before asking. Has the company confirmed the return is complete? Is there no open dispute with the vendor? Does someone you can ask hold a relationship the CEO would answer? And, if you advised on the exit, does your engagement let you raise an unrelated subject with this client? Any no means wait or route the question elsewhere.

## The vendor-transition metadata review

Ten lines in four blocks, answered by the company's exit lead or the relationship holder in conversation. Each answer is a sentence or a number, never a file. The partner writes down the answer and its date; the company confirms anything that touches rights.

| Line | Question | A useful answer sounds like | Who answers |
|---|---|---|---|
| A1 | Which record families came back, and in what form? | "Shipment and stock movement exports, as files" | Exit lead |
| A2 | Which years do they cover, and is the run unbroken? | "2016 to 2025, no gaps we know of" | Exit lead |
| A3 | Where do they live now, and who looks after them? | "Our archive server; IT manages it" | Exit lead or IT |
| B1 | What did the vendor keep, and why? | "Their own labor schedules and invoices" | Exit lead |
| B2 | What was deleted, and did you receive confirmation? | "Damage photos, confirmed in writing" | Exit lead |
| B3 | Is anything you would want still with the vendor? | "No" (or a question the company takes to its vendor itself) | Company only |
| C1 | Who created each family that came back: your staff, the vendor's staff or your clients? | "The vendor's system logged the movements; our staff made the claims decisions" | Operations owner |
| C2 | Has the company confirmed which of these it holds rights to? | "Counsel is reading the contract" | The company and its advisers |
| C3 | Has any of it been licensed for AI training before? | "Never" | The company |
| D1 | Would the CEO like a short note on how SourceX screens companies, to decide whether to talk? | The CEO's own yes or no | The CEO |

Lines C1 to C3 decide most outcomes. A record the company's own people created about their own work is the easy case. A record the vendor's system generated may or may not be the company's to license, and that is exactly the question the partner leaves alone: the company confirms its rights, and SourceX's process runs a rights check at qualification and asks the company to confirm the data has not been licensed for AI training before. A partner never reads the contract, never gives an opinion on it and never contacts the former vendor.

Mark the review with one of three results. **Ready to ask:** A1 to C1 answered, C3 is "never" and the company is comfortable with D1. **Company still confirming:** C2 is open; wait for the company. **Stop:** nothing came back that the company created or controls, or C3 shows an earlier AI-training license.

**Method note.** The review lines come from SourceX's screening profile and its company process page, both read on 2026-10-27, the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and the end-of-processing duties in the EDPB excerpt above. They have not been tested against completed introductions, and SourceX has not published how often companies leaving a vendor go on to license records.

## Who confirms what once the vendor is gone

| Party | Confirms | Never does |
|---|---|---|
| The company's CEO | Whether the company talks to SourceX, and signs for it | Leave the decision to an adviser or partner |
| The company's exit lead and advisers | What came back, what was deleted and which records the company holds rights to | Hand records to the partner |
| The former vendor | Its return and deletion, to the company | Hear from the partner at all |
| The partner | The question, the date and the CEO's answer | Read contracts, review or summarize records, or give a rights opinion |
| SourceX | Fit and rights, in its own review | Rely on the partner's view of either |

The fit facts sit underneath all of it: a full-time headcount that reached 50 at its high point, with contractors left out of the count; years of records the company itself produced; a clear right to license them; and a chief executive who asks for the call. 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. If the company was acquired while the contract wound down, the acquirer's CEO decides.

## A warehousing contract that ended after nine years (Illustrative)

Illustrative. The distributor, its vendor and every detail are invented, and nothing predicts how a review would end.

A building-products distributor with 410 full-time employees ended a nine-year contract with a third-party warehousing provider in June and moved the work to a new provider. Its outside accountant, a registered partner who signed the Channel Partner Agreement in the spring, waited until the controller confirmed in August that the exit was closed.

Over two calls the exit lead answered the review. Shipment and stock movement records for 2016 to 2025 came back as exports; the vendor kept its own labor schedules and invoices; damage photos were deleted and the deletion was confirmed in writing. The distributor's claims decisions and returns approvals had sat in its own ERP all along. Counsel was still reading the contract on the movement records, so C2 was open, and nothing had ever been licensed for AI training.

The accountant asked D1 in September. The CEO replied that it could wait until after year-end close. The record read "revisit in January", and nobody raised it before then. In January the CEO asked for the note and agreed to a call; the accountant made the introduction with the CEO's agreement, the distributor applied itself, and the open rights question on the movement records went to SourceX's review.

Had SourceX later paid the distributor $400,000, the default reward would be $70,000 (Illustrative). In the terms' own words (section 4), "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the distributor would receive the same amount with or without its accountant.

## Write down the answer and the next authorized step

Keep one entry: the contract and its end date, the date the company confirmed the return, the review answers with their dates, the CEO's words and the next step with its owner. Credit does not follow a click. Section 2 of the terms credits a company new to SourceX to the earliest valid introduction made within its 90-day attribution window, once that company files a verified application. Long vendor relationships often come with earlier contact of every kind, and section 3 treats any earlier application, lead, account or email exchange between SourceX and the company as a duplicate. If the company's adviser, its new vendor and a board member all know the company, only one introduction can be credited, and overlapping cases are settled in SourceX's duplicate review.

## Where the review can mislead

- **Contracts differ.** This page interprets no contract and gives no legal advice. What came back and who may license it are questions for the company and its advisers, and then for SourceX's review.
- **Returned is not the same as licensable.** An export the vendor's system produced can come back to the company and still carry rights questions.
- **Exports lose context.** Flat files can drop the links between records that made the history useful in the first place.
- **Personal data.** Records returned from a vendor often hold personal details, and personal consumer data is usually not a fit.
- **Platform contracts have their own guide.** For a CRM in particular, see [what happens to Salesforce data when a contract ends](/questions/what-happens-to-salesforce-data-when-contract-ends); for client terms that limit reuse, [customer contract data use restrictions](/guides/customer-contract-data-use-restrictions); and for how licensing review differs from vendor diligence, the [vendor due diligence comparison](/compare/vendor-due-diligence-vs-data-licensing-review).
- **No published outcomes.** Count reviews completed, CEOs asked and CEOs who said yes. The [metadata-only opportunity map](/guides/metadata-only-referral-opportunity-map) offers a way to log them, and other business-change guides sit in the [guides library](/guides).

## 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.

When the return is confirmed, the review reads ready to ask and the CEO wants a conversation, [register as a partner](/register), test the answers against [who qualifies](/who-qualifies), and go through sections 2 and 3 of the [program terms](/terms) before the introduction is sent.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.edpb.europa.eu/system/files/documents/2023-10/EDPB_guidelines_202007_controllerprocessor_final_en.pdf
