# Corporate referral compliance review: 24 questions | SourceX

Canonical: https://refer.sourcex.si/guides/what-corporate-compliance-teams-need-to-review-in-a-referral-program
Last updated: 2026-11-05

Compliance needs to clear four things before anyone at the corporate records a SourceX introduction: who the partner is and who signs for it, whether anyone may accept the reward, what information may travel to SourceX, and what anyone may say about SourceX, the corporate and the company. SourceX's published terms and its sample Channel Partner Agreement answer most program questions. Your own policies answer the employee questions, counsel answers the rest, and none of them decides for the operating company: its CEO does.

Approve a dated document set, not "the program". The terms page carries Version 2026-11-04, published 4 Nov 2026, and links an unsigned sample of the Channel Partner Agreement with the standard reward terms. Section 11 says "Signed agreements are never silently replaced," and section 9 says the agreement lasts a year and "renews only with fresh acceptance and signatures." An approval naming both versions and lapsing on the anniversary cannot drift out of date unnoticed.

## Three seats a compliance reviewer keeps apart

One request can put the corporate in three capacities at once. The corporate seat is the would-be partner: the venture unit, or the employee who would register. The vendor seat is any commercial tie with the company: procurement buys from it, a sales team sells to it or an operations team hosts its systems. The company seat belongs to the operating company, where only the CEO can agree to a licensing discussion. Compliance clears the first, restricts the second, and in the third checks only that the CEO's agreement exists before anything is recorded. Large partner programs draw a similar line around contact details: Microsoft's Partner Center guidance on co-sell opportunities tells partners, in our paraphrase, to get a customer's consent before handing Microsoft that customer's contact information, because Microsoft can use it to reach the customer directly.

| Seat | What compliance reviews | What it cannot clear | Pattern to watch for |
|---|---|---|---|
| Corporate: the venture unit or one named employee | Whether the corporate or a person may join, sign and accept a reward | The company's records, fit or interest | An employee registering personally to collect a reward the entity may not take |
| Vendor: procurement, an account team, a hosting team | Whether a tender, renewal or dispute is open, and whether the asker influences it | Permission to ask | The buyer or account owner on a live deal making the ask |
| Company: the operating company | That its CEO agreed in writing before any record was made | Whether to proceed or what to license | A CTO's enthusiasm logged as the company's yes |

## The 24-question policy review pack

Each question names who can answer it and, where SourceX has published something, what the text says. SourceX's own documents settle 14 of the 24. Six turn on your policies, three need counsel's reading even where SourceX has published the clause, and one is open: the published terms are silent on a partner who declines its reward, so that question goes to SourceX in writing before anyone submits. The fourteen bind SourceX and its partner and say nothing about whether your employer lets you take part; the other ten are where corporate approvals usually stall.

Two figures make the money rows concrete. Illustrative: if SourceX's actual payout to a referred company came to $400,000 on its first qualifying transaction, the reward would be $70,000, USD 50,000 plus 5%, because that is more than 15% of the payout. If that payout were later cut to $300,000, the reward would be recalculated on the reduced total and fall to $65,000, with any excess already paid adjusted. A buyer refund that leaves the company's payout untouched changes nothing.

The signature comes first in time: a partner signs the SourceX Channel Partner Agreement before submitting any introduction, and anyone who signed it under its earlier title, the Channel Partner Non-Circumvention and Non-Disclosure Agreement, stays bound by that signed text.

| # | Question | Who answers | What the published text says |
|---|---|---|---|
| A1 | Who registers as partner: the entity, one named employee or nobody? | Your policy | The sample agreement's partner line reads "[JURISDICTION AND ENTITY TYPE, OR INDIVIDUAL]" |
| A2 | Who may sign for the entity? | Your signing-authority policy | Section 7.9: the signing record names the party, signatory, document version and date |
| A3 | Does signing make the corporate SourceX's agent or legal partner? | Sample agreement, section 7.1 | Independent contractors; the partner cannot commit SourceX to prices, licenses or payouts; "Participation creates no partnership or employment relationship." |
| A4 | Does the agreement restrict the corporate's other business? | Counsel | Section 2.4: "It creates no blanket non-compete, employment restriction, exclusivity over a contact's unrelated business, or prohibition on lawful competition." |
| A5 | How long does it bind, and what survives? | Terms, section 9 | One year, 30 days' notice; six months of contact protection; three years of confidentiality, longer for trade secrets |
| A6 | Which law and forum govern a dispute? | Counsel | Terms section 12: Delaware law; JAMS arbitration seated in Wilmington |
| B1 | May the corporate or an employee accept money from an outside company for an introduction? | Your policy | Nothing: SourceX's documents do not reach an employer's rules |
| B2 | What is the reward based on, and who funds it? | Terms, section 4 | On a company's first qualifying transaction, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap and a USD 100,000 Minimum Transaction; 15% on each further qualifying transaction first agreed within the twelve-month Repeat Window; paid separately by SourceX and never deducted from the company's agreed compensation |
| B3 | When does it become payable? | Terms, section 5 | Within 60 calendar days of whichever comes second: the Acquisition Partner signing off on the full validated dataset in writing as final, or that dataset's handoff finishing; every listed condition must also be met, and "payment must also be lawful" |
| B4 | Can a paid reward change later? | Terms, section 6, with the program's reduction rule | A cut to the company's payout means recalculation on the reduced cumulative payout; a buyer refund alone does not |
| B5 | Does the person who could be paid also influence a purchase, renewal, investment or dispute with the company? | Your conflicts policy | Nothing: this is the vendor seat |
| B6 | How will the company's CEO learn who could be paid? | Your policy | No wording prescribed; tell the CEO before asking for a yes |
| B7 | What if policy allows the introduction but bars the reward? | Open: ask SourceX in writing | The published terms do not deal with a partner who turns a reward down |
| C1 | What may the corporate tell SourceX about a company? | Sample agreement, sections 4.2 and 4.4 | "no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems"; no dataset copies without separate written authorization |
| C2 | May the CEO's name and email reach SourceX before the CEO agrees? | Your privacy policy | SourceX's screening page lists introductions made without the decision maker's knowledge among poor fits |
| C3 | Did any fact arrive through a board seat, diligence, a supply contract or an NDA? | Counsel | Nothing: SourceX cannot judge your confidentiality duties |
| C4 | What will the corporate hear back? | Sample agreement, section 4.6; terms, section 7 | Generic stages or reference codes for its own referral; never other partners' records, applicant documents or confidential buyer information |
| D1 | May the corporate call SourceX its partner in public? | Sample agreement, section 4.5 | Not without written authorization |
| D2 | Which claims must no message make? | Sample agreement, section 4.6; SourceX's application page | No telling a company that an estimate, interest, a signature or an upload assures a purchase or reward; "Applying doesn't guarantee an offer or payment." |
| E1 | Which document wins when two disagree? | Terms, section 8; sample agreement, section 7.2 | A signed Schedule A prevails on the reward formula, base, Minimum Transaction, Repeat Window and any cap; website updates and dashboard edits do not amend a signed agreement |
| E2 | What must each introduction record show? | Sample agreement, section 3.3 | Company, domain, partner, opportunity, introduction method and timestamps |
| E3 | What if the company already knows SourceX, or another partner knows it too? | Terms, sections 2 and 3 | Earlier leads, accounts or email correspondence make it a duplicate; one partner is credited, and SourceX settles overlaps in duplicate review |
| E4 | Who decides when the company is being acquired, or sits in a group? | SourceX's screening page and program rules | The target's CEO until closing, the acquirer's CEO after; whether a company and its corporate group count as one company for the once-per-company USD 50,000 floor is for SourceX to decide |
| E5 | What happens to earned rewards if the corporate leaves? | Terms, section 10 | They stay payable once their conditions are met, unless they arose from fraud or a breach |

## The approval memo compliance signs

A sign-off reads best as a one-page memo with fixed fields. It approves the corporate's participation and its conditions, never a company: that answer belongs to each company's CEO, and the order in which both sides' approvals clear is set out in [the two approval paths](/guides/a-corporate-venture-referral-needs-two-approval-paths). If a request keeps bouncing between the innovation side and legal before a memo can be drafted, the [handoff diagnostic for innovation and legal teams](/guides/the-hidden-friction-between-innovation-and-legal-teams) finds the missing fact.

1. **Documents approved.** Terms Version 2026-11-04 and the agreement version the linked sample carries, with the date each was read.
2. **Partner of record.** The entity, one named employee or nobody, and why.
3. **Signer.** The role that holds authority to bind the partner.
4. **Scope.** The named relationships covered and who may make each ask.
5. **Wording.** The approved first message to a CEO, naming who could be paid; logos and labels go through the [co-branding audit](/guides/how-to-avoid-suggesting-a-corporate-partner-endorses-sourcex).
6. **Conditions.** No ask during an open tender, renewal, dispute or acquisition talk; the CEO's written yes before anything is recorded; nothing from a board seat, diligence or a contract in any message.
7. **Open items.** Each unanswered question with an owner and a date, B7 included.
8. **Expiry.** The agreement's first anniversary or the next terms version, whichever comes first.

## A narrow first approval, and the events that reopen it

Approve three named companies for 90 days, not the whole network. At day 45, read the log: asks made, CEOs who agreed, any message that left the approved wording, any request for records or logins, any complaint from a company or an account team. Stop early if a CEO says the commercial relationship shaped the answer. SourceX has not published how long corporate approvals take or how often CEOs agree; your log produces those figures, and none are published here. Reopen the memo when the facts under it move:

- **A new terms version.** Read the change log in section 11 and decide whether it touches anything the memo relied on.
- **The anniversary.** Renewal needs fresh signatures, so it needs a fresh look.
- **A commercial event.** A tender, renewal or dispute moves that company out of scope until it ends.
- **A change of ownership.** The target's CEO decides until closing; if the corporate itself is the buyer, what its deal team learned stays inside the deal, as the [corporate development page](/for/corporate-development-data-licensing-referral) explains.
- **A new signer or relationship owner.** Authority does not move with a job title.
- **Your own policy.** Outside-compensation rules change too; the [board member conflict-of-interest question](/questions/board-member-conflict-of-interest-referral-fee) shows one variant.

## Where a review pack can mislead

- **It is dated.** It reflects documents read on 2026-10-27, with the money rows brought up to terms Version 2026-11-04 on 2026-11-04, and SourceX may publish new versions.
- **SourceX's documents bind two parties.** The operating company's duties to its own customers are worked out between the company and SourceX in its rights review, never by the corporate's compliance team.
- **A clean review is not a fit.** Programs differ, and whether a company's records match one is decided in SourceX's review; a company that misses one program may suit another later.
- **Pressure does not show on paper.** A CEO who depends on the corporate as customer or investor may agree to please it, which is why the pilot asks CEOs how the request felt.
- **It is not legal advice.** The counsel rows are questions for your lawyers, not conclusions about how any law applies.

**Method note.** The pack applies SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement (version 2026-10-19), the screening page and the application page, all read on 2026-10-27, to questions a corporate compliance team typically asks before joining an outside program; the money rows (B2, B4, E1, E4) and the version references were brought up to terms Version 2026-11-04 on 2026-11-04. Microsoft's guidance appears only as an outside comparison. Each question has one primary answerer, and a question counts toward SourceX's 14 only when SourceX's own text settles it. Demand, record quality, payouts and approval times are not assessed.

## 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 memo is signed and a CEO has agreed in writing, [register the partner of record](/register), check the company against the screening facts on [who qualifies](/who-qualifies) and file the version of the [program terms](/terms) you approved alongside the memo.

Clearing a referral program and reviewing SourceX as a possible investment belong in separate files; for the second, the [SourceX investor overview](https://sourcex.si/investors) takes requests for investor materials.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/apply
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
- https://sourcex.si/investors
