A referral program for SAP partners rolling out to US subsidiaries

SAP partners rolling out a group template to a US subsidiary can introduce the company to SourceX before its legacy systems are retired. Ask the US CFO, group IT and group legal who owns the records, never extract data, and let the company decide whether to license.

Why is an SAP rollout to a US subsidiary an introduction moment?

When a group template goes live at a US subsidiary, the old ERP, the spreadsheets around it and often the helpdesk and document stores are about to be retired or frozen. That is the one point at which a company decides what happens to years of operational history. An SAP partner in Frankfurt, Pune, Warsaw or Sydney is in the room when that decision is made.

SourceX is the data transaction layer between companies that hold operational records and AI developers who license them. The company keeps ownership and signs only if price and terms work. As the SAP partner you introduce; you do not extract, copy or look at any data.

The rollout gives you an honest reason to ask a question you would otherwise have no business asking: before the legacy system is decommissioned, does anyone want to know whether its history has value?

Which US subsidiaries fit?

The baseline for the entity or group is 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data and an authorized sponsor. In a subsidiary, the harder test is usually rights and which entity holds the records.

Signal in the rolloutWhat to look forWhy it matters
Legacy ERP being retiredFive to ten years of orders, invoices, inventory and approvalsOutcomes tied to decisions
Acquired subsidiary with its own historyRecords from before the group bought itArchives that predate the group
Many satellite systems being replacedCRM, helpdesk, document stores, time sheetsCross-system context
Mostly English transactional recordsUS customers and US staffLanguage fit
A local finance team with an owner of the dataA named controller or CFOA route to a sponsor

Who holds the records when the instance is shared?

Many groups run one SAP instance with company codes for each entity, or a shared client for several subsidiaries. That means a table of US transactions may physically sit in a German or Indian data center and belong legally to the US entity, to the group parent, or to both.

Before anyone discusses a license, the questions are legal rather than technical:

  1. Which legal entity owns the US records under the intercompany agreements?
  2. Does the group parent have the right to license them, or only the US entity?
  3. Do customer or employee contracts, works council agreements or group policies restrict use?
  4. Are third-party records mixed in, such as shared-service customers?
  5. Who at the group can authorize a license?

Do not try to answer these yourself. Raise them as questions and let the company's legal team decide. The company completes a data inventory with SourceX after it applies, and rights are reviewed there.

Who should you ask?

RoleWhat they care aboutA good first question
US finance director or CFOClose, audit trail, retention"What is planned for the old ledgers after cutover?"
Group CIO or head of ITDecommissioning cost, archive tooling"Is the legacy system being archived or switched off?"
Group legal or general counselOwnership and restrictions"Who owns the US entity's records on a shared instance?"
Project sponsor or steering committee chairBudget and timeline"Is there a line for legacy data value?"

The sponsor who can say yes is an owner, CEO, CFO or authorized representative. Ask the steering committee chair who that is rather than assuming.

When in the project do you raise it?

Project phaseWhat to doNotes
Blueprint or fit-to-standardNote the legacy landscape; no pitchYou learn what will be retired
Data migration designAsk whether history is being archivedThis is the natural window
Testing and cutover planningMention before systems are frozenLate is risky
HypercareOnly if the topic is already openRetirement decisions may be final
Post go-live decommissioningLast chance before deletionCheck if retention rules require deletion

What to say

Offer the owner the choice of applying directly through a referral link. The link sends the company to sourcex.si/apply with your referral code attached, so credit is preserved.

Illustrative scenario

Illustrative and fictional: a Munich consultancy is migrating a Texas distribution subsidiary, acquired six years ago, onto the group S/4HANA template. During data-migration design, the consultancy's lead asks the US controller what happens to the old ledgers, order history and the helpdesk that sits beside them. The controller says the old system will be archived read-only for audit purposes.

The lead then asks who could authorize a license, learns it is the subsidiary's president with sign-off from group legal, and offers a referral link. Group legal replies that the acquisition agreement needs checking before anything proceeds. The consultancy waits, does nothing else, and the company decides. Nothing here involved extracting a single record.

What does the partner never do?

  • Never export tables, reports or extracts from the client's system.
  • Never describe confidential records in an email or chat.
  • Never hold credentials or run transactions for this purpose.
  • Never promise a license, a price or a reward.
  • Never delay or alter the client's retention and archiving duties.

De-identification and redaction requirements are agreed with the company before any work begins, and data is delivered only after an executed agreement and the company's authorization.

How do rewards work?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee. A lead, meeting or signed agreement alone does not trigger payment. No reward is guaranteed. Check your SAP partner agreement for rules on outside referral income and any conflict with your customer's contract. If your consultancy is the payee, the IRS describes Form W-8BEN-E for foreign entities; our guide to filling out a W-8BEN-E for a consulting firm covers the sections. This is general information, not legal, tax or financial advice. Confirm with your own counsel or tax adviser before acting.

When not to bother

Skip subsidiaries with fewer full-time employees at peak than the baseline, groups where a court or trustee controls assets, records already licensed for AI training, or projects where nobody can say who owns the data. Skip any rollout where you would need to look at records to make the case.

Next step

Register as a partner, then compare the playbook for offshore delivery partners and nearshore software firms. If you also advise on finance, read the fractional CFO guide. Confirm whether non-US residents can join, see how this differs from a customer referral program, and use the referral earnings calculator. Final economics are in the program terms.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Can I take part if my contract with the client forbids using project information?

Check the contract first. If it restricts using project information for other purposes, do not rely on what you learned inside the project. Ask the client's sponsor for explicit permission, or let them apply on their own through a referral link. When in doubt, ask your legal team before registering.

Does the US subsidiary or the German parent decide?

Whichever legal entity owns the records and has authority to license them. On a shared instance that may be the parent, the subsidiary or both. The company's own counsel decides this during review; as the partner you only ask who the authorized sponsor is and make the introduction.

What if the legacy system is being deleted by policy?

Retention and deletion duties come first, and the company's counsel owns them. Raise the question before cutover, because archived systems can qualify if the data still exists, and deleted archives cannot. Never suggest keeping data in breach of a legal hold or a retention schedule.

Can an acquired subsidiary qualify if the group only owns it for a year?

It can, if the data still exists, the company has rights to license it and it meets the baseline. Records from before the acquisition may need the seller's consent or a check of the purchase agreement. Companies that were acquired or wound down can qualify, which is a rights question for their counsel.

Will SourceX contact my client without telling me?

The company applies through the referral form or your referral link, and SourceX qualifies it. Credit goes to the first valid referrer whose introduction leads to a verified company application within the attribution window. Agree with your client how you want to be kept informed, and respect their confidentiality.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment