The partner terms summary should point to the governing agreement: a summary-versus-contract mapping table that names, for each line of a program-at-a-glance box, the signed document that decides it for the person reading and the link label that takes them there

Short answer

A program summary on a partner's website describes the arrangement; it never governs it. Each line should name the document that decides it for the person reading, and link there with a label saying what they will find. For a partner, the signed Channel Partner Agreement and its Schedule A prevail over the website terms on rate, base and cap. For a company, its own signed agreements with SourceX decide its payout and timing; the partner terms do not govern its payment. Conditions that change a money claim stay next to the claim, not behind the link.

Visual briefFull-size diagram
Five summary lines on the left linked to governing documents on the right: reward rate and cap to the signed Schedule A, credit to the program terms, the company's payment to the company's own agreements and confidentiality to the signed partner agreement, while the line paid within 60 days splits in orange into two documents.
The mapping method on this page. The summary lines are generic examples, not quotes from any partner's website.

This guide is for the compliance or communications lead whose firm publishes a "SourceX at a glance" box, FAQ answer or handout. Keeping such pages current is covered in the page-to-terms audit worksheet, and a clause-by-clause reading in the referral terms explained. The question here comes first: which document stands behind each line, for which reader, and how the summary says so.

Two contracts, two readers, one box

Company CEOs read a partner summary to decide whether to talk to SourceX, and their money is governed by their own agreements with SourceX. Other professionals read it to decide whether to become partners, and once they sign, the Channel Partner Agreement governs their reward. Your staff read it and repeat it. One sentence can be right for one reader and wrong for another.

Payment timing is the clearest case. For a partner, section 5 of the terms says: "The payment deadline is 60 calendar days after the later of (a) the Acquisition Partner's final written acceptance of the complete, validated dataset for the qualifying transaction and (b) completed handoff of that complete, validated and approved dataset to that Acquisition Partner." For a company, SourceX's process page says that after Closing the company invoices, and that "Payment is due within 60 calendar days after SourceX receives a valid invoice, unless different terms are signed." Section 8 of the terms keeps the two apart: "a supplier's payment timetable, including any Net 60 clause, never determines when referral rewards are paid." A summary line reading "paid within 60 days" fuses two clocks, two triggers and two contracts into one promise that neither document makes.

Money works the same way. The company's payout is fixed in its signed Dataset Deal Confirmation, and SourceX's process page calls any earlier estimate indicative. The partner's reward is calculated on what SourceX actually pays the company and, in the words of section 4, "is paid separately by SourceX and is never deducted from the supplier's agreed compensation," so a company receives the same amount with or without a partner. Three facts, three sources, kept apart.

What SourceX's documents say about their own order

The documents rank themselves, which makes the mapping possible. Section 8 of the terms says the reward formula, calculation base, Minimum Transaction, Repeat Window and any cap "in a signed Channel Partner Agreement's Schedule A prevail over these terms," that the signed agreement "governs confidentiality, contact protection and its remedies," and that "These terms govern attribution and rewards." It also says signed supplier and buyer agreements govern their own transactions. Section 12 adds that "Where a signed referral agreement sets its own governing law or dispute process, that agreement controls."

The sample agreement linked from section 9 of the terms points the same way from its side. Section 1.1 defines the Program Terms as Schedule A and says "No separate website snapshot or attachment is incorporated." Section 7.2 says the agreement and Schedule A prevail over inconsistent website program terms, and section 7.7 says a website update does not amend the agreement. Section 7.1 closes off a word summaries often use: "Participation creates no partnership or employment relationship."

A partner summary therefore sits on three layers: the partner's own signed agreement and any addendum, the program terms page, and the company's agreements with SourceX, which a partner never sees. Nothing in the terms says how partners should summarize them; the pointer method below is this guide's recommendation, not a SourceX rule.

The summary-versus-contract mapping table

One row per line a program summary typically contains. Fill a copy for your own box, adding a column for your exact wording.

Summary lineReader it affectsDocument that decides it for that readerPointer label that works
Reward rate and capPartnersThe partner's signed Schedule A; terms section 4 states the default"Reward: default in program terms section 4; your signed Schedule A governs"
What the reward is calculated onPartnersActual Supplier Payout, defined in terms section 4 and Schedule A paragraph 3"How Actual Supplier Payout is defined (terms, section 4)"
The company's payment does not changeCompaniesTerms section 4 for the reward; the company's own Dataset Deal Confirmation for its payout"Why a reward never reduces the company's payment (terms, section 4)"
When a reward is paidPartnersTerms section 5 and Schedule A paragraph 5"When a reward becomes payable (terms, section 5)"
When the company is paidCompaniesThe company's own signed terms; SourceX's process page describes the usual invoice timing"How SourceX pays companies (SourceX's process page)"
Who gets creditPartnersTerms section 2 and Schedule A paragraph 2"How credit is decided (terms, section 2)"
Confidentiality and contact protectionPartnersThe signed Channel Partner Agreement, sections 4 and 5 in the sample"Confidentiality: your signed partner agreement"
Which companies may be a fit, and who decidesCompanies and partnersSourceX's screening page; terms section 1 for size"Which companies may be a fit (who qualifies)"
License and exclusivity termsCompaniesThe company's own Dataset Deal Confirmation, which is not publishedNo summary line; say these are agreed between the company and SourceX
Disputes and governing lawPartnersTerms section 12, unless a signed agreement sets its own"Disputes: terms section 12 and your signed agreement"
Changes to the programPartnersTerms section 11 for new versions; sample section 7.7 for signed agreements"Checked against terms version 2026-10-22.2, since replaced by version 2026-11-04 on [date]"
Naming SourceX as your partnerThe publicSample agreement section 4.5: written authorization firstNo line until SourceX authorizes it in writing

Two rows deserve their exact wording on the page itself rather than a paraphrase. The fit row is safest as SourceX's own location sentence: 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. Add the size rule (50 or more full-time employees at peak, contractors excluded) and the screening page's own caution: may be a fit, SourceX decides after review. The reward row is safest as the offer block, pasted unedited, because it carries its own conditions.

Method note. The table was built on 2026-10-28 from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned sample Channel Partner Agreement (version 2026-10-19), SourceX's screening page (updated 2026-10-27) and its process page for companies. Each row asks which document the published texts themselves say decides the point, for the reader it affects. A partner's signed copy governs where it differs from the sample, and no company's deal documents were seen.

Pointers that work, and labels that hide

The FTC's .com Disclosures guidance offers the clearest published test for a summary's links. In paraphrase: a disclosure that is an integral part of a claim should not be placed behind a hyperlink but next to the claim, a link that leads to further information should be labeled so readers can tell its importance, nature and relevance, and vague labels such as "details," "disclaimer" or "fine print" are likely inadequate. Whether that guidance reaches your page is a question for your own counsel; it describes good pointing either way.

Applied to a terms summary, three things stay in the box beside the claim they qualify: the offer block with its conditions, the fact that a reward never reduces the company's payment, and the line that SourceX decides after review. Definitions, full payment conditions and the dispute process can sit behind links whose labels say where they go.

Label that hidesLabel that points
"Terms apply""Program terms, version 2026-10-22.2, since replaced by version 2026-11-04: section 5 sets when a reward is paid"
"Details""How SourceX decides which introduction gets credit (terms, section 2)"
"Learn more""Which companies may be a fit, on SourceX's screening page"
"Fine print""Your signed partner agreement governs if it differs from this summary"

One summary box rewritten line by line (Illustrative)

Illustrative. An invented 25-person accounting firm publishes a six-line "SourceX at a glance" box on its client resources page. Its third line reads "Clients and referrers paid within 60 days of the deal."

Traced to its sources, that line fails four ways. Evidence: no document says it. Scope: it covers two readers whose money runs on different contracts. Timing: the partner's clock starts at the later of final written acceptance and completed handoff, not at "the deal," and section 5 says "A lead, meeting or signed agreement alone does not earn a payable reward"; the company's clock starts when SourceX receives a valid invoice after Closing, unless its signed terms differ. Permission: the box also names SourceX as the firm's partner, which waits for written authorization under section 4.5. The firm split the line in two, each half pointing at its own document.

Line in the old boxProblemRewritten line
"Our partnership agreement with SourceX"Sample section 7.1: no partnership is created; section 4.5: public identification needs written authorization"We have signed SourceX's Channel Partner Agreement," published after SourceX's written OK
"Protected by our NDA with SourceX"Old title; confidentiality is governed by the signed Channel Partner Agreement"Confidentiality is governed by our signed partner agreement," with a link to the sample
"Clients and referrers paid within 60 days of the deal"Two clocks fused, wrong triggerTwo lines, one per reader, each linked to its own source
"Clients keep 100% of their payout"Right in substance, unsourced"SourceX pays any reward separately; terms section 4 says it is never deducted from the company's agreed compensation"
"Standard license terms for every company"Describes company deal terms, which are agreed in each company's own Dataset Deal Confirmation and not publishedLine removed
"Terms apply"A label that says nothing"Program terms, version 2026-10-22.2, since replaced by version 2026-11-04," with the date checked

After the box goes live

Keep three things with the published box: the terms version and date checked, SourceX's authorization if the box names it as your partner, and the old wording of any changed line. Recheck when the terms version changes; the audit worksheet runs that check line by line, and saving the applicable terms version covers the private record of which version governed each of your own introductions. If a summary line was wrong, correct it with a dated note and send the correction to anyone who received the old version directly. Money lines beyond the offer block go through the payout claim checklist before they go anywhere.

What a summary can never settle

  • Your own signed terms. If your Schedule A or an addendum differs from the default, the summary still describes the published program, and the offer block tells readers a signed Schedule A can differ.
  • The company's deal. A partner never sees a company's Dataset Deal Confirmation and should describe it only in SourceX's published words.
  • Questions the terms leave open. How a firm's account relates to its people's personal accounts, or what happens when a partner declines a reward, is not settled in the published terms; SourceX decides, and a summary should say so rather than invent a rule.
  • Fund and firm documents. These may add rules; reviewing referral terms against fund documents sets the issues out for counsel.
  • Legal effect. This page is not legal advice, and whether any guidance on disclosures applies to your summary is for your own counsel.

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 every line in your box names its document, register as a partner if you have not yet signed, point the fit line at who qualifies, and stamp the box with the version of the program terms you checked. More partner guides are in the guides hub.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can our summary just say the terms apply and link to them?

A link alone hides the conditions that change a money claim. Keep the offer block, with its own conditions, beside any reward line, and use the link for the detail behind it, labeled with what the reader will find there.

Our signed Schedule A differs from the default. Should the summary show our rate?

Ask SourceX before publishing anything about your own terms. A public summary describes the published program; the offer block already tells readers that a signed Schedule A can differ.

Should the summary describe what the company signs with SourceX?

Only in SourceX's own published words: a Master Supplier Licensing Agreement once, and a Dataset Deal Confirmation for each deal. The terms of any company's deal are between that company and SourceX, so a partner summary never describes them.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. sourcex.si/how-it-works
  4. refer.sourcex.si/who-qualifies
  5. ftc.gov/sites/default/files/attachments/press-releas…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment