Why a partner should save the applicable terms version when the agreement needs no snapshot: a recordkeeping sheet that pins each referral event to the text in force that day

Short answer

Save versions because every question about credit or a reward is answered by a dated document, and those documents change. The published terms have been revised repeatedly since 12 October 2026, most recently on 4 November 2026, while the Channel Partner Agreement you signed changes only through a writing both sides sign. You do not need a website snapshot for the agreement to work; its own Schedule A says none is required. You need a log that records which agreement you signed, which terms version was live at each referral event and any signed addendum.

Visual briefFull-size diagram
A swimlane timeline from 12 to 26 October 2026: the published terms lane changes from version 2026-10-12 to 2026-10-19, 2026-10-21 and 2026-10-22.2, the signed agreement lane stays flat from 15 October, and the Illustrative introduction on 16 October and application on 24 October each point up to a different terms version.
Illustrative partner and dates; the version sequence follows the changelog in section 11 of the published terms.

That distinction saves effort. A partner who screenshots every page every week builds a pile nobody can search. A partner who writes one row per event, with the version stamp and the date, can answer the only question that matters when something is disputed: which words governed this, on that day?

Your agreement needs no snapshot; your questions do

The sample Channel Partner Agreement defines its Program Terms as the rules in Schedule A, which form part of the signed agreement, and says no separate website snapshot or attachment is incorporated. Schedule A repeats it: website updates, calculator changes and dashboard edits do not change the agreement, and no separate website terms snapshot is required. Your protection does not depend on a copy of a web page.

Questions still do. The website terms say they govern attribution and rewards, they carry the changelog that explains which changes reach earlier referrals, and they are where most partners read the rules before acting. When you ask SourceX about a decision, the useful message quotes the sentence you relied on and names the version it came from. Without the version, you are quoting a page that may have changed since.

Three documents that change in three different ways

DocumentWho can change itHow a change happensWhat it decidesWhat to keep
Published program terms at /termsSourceXA new version with a new stamp; section 11 lists what changedAttribution and rewards, subject to what you signedThe version stamp, the date you read it and a full-page PDF
Signed Channel Partner Agreement and Schedule ABoth parties togetherA writing signed by both; it renews only with fresh acceptance and signaturesRate and calculation base; confidentiality and contact protectionThe signed copy and its signing record, which names the document version and signature date
Signed addendumBoth parties togetherSignatureOnly the provisions it expressly identifiesThe signed addendum, word for word

On rate and calculation base the documents agree: section 8 of the terms says a signed Schedule A prevails over the website terms. Beyond those two items they use different words. The website terms say they govern attribution and rewards, while the sample agreement says it and Schedule A prevail over inconsistent website program terms and that Schedule A holds the complete rules for attribution. If your question sits in that space, quote both texts with their versions and ask; do not pick the one you prefer.

Fit criteria move too. SourceX's screening page says criteria follow each program and can change, and that a screen is valid on the date it was made. A company still needs 50 or more full-time employees at peak, years of records it created itself, rights to license them and a CEO who authorizes the discussion; whether its records match current demand stays unknown until SourceX reviews it. Date every screening note for the same reason you date a terms version.

What the published changelog already settles

Section 11 of the terms does part of the work for you. It says signed agreements are never silently replaced and that rates and exceptions in signed agreements are preserved, then lists each change.

VersionWhat section 11 says changedDoes it say the change reaches earlier referrals?
2026-10-12The section 4 reward calculation, since superseded by the 2026-11-04 versionYes: it applies to all referrals, including those submitted earlier
2026-10-19The agreement partners sign becomes the Channel Partner Agreement (version 2026-10-19)Agreements under the earlier title remain in force as signed (section 9)
2026-10-21Section 3 states what counts as an existing relationship with SourceXNot stated
2026-10-22Section 5 states the payment deadline and conditions in Schedule A's words; section 9 links an unsigned sample of the agreementNot stated
2026-10-22.2Section 4 defines Actual Supplier Payout in the words of Schedule ANot stated
2026-11-04Section 4 becomes the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, with 15% on repeats first agreed within 12 months and a USD 100,000 Minimum TransactionRead the entry's own words and quote them with your event dates

Saving a version does not freeze the old text where the changelog says a change applies to everyone, as the 2026-10-12 entry does. What the saved version gives you is the ability to see which rows of this table touch your referral, and to ask about the ones marked "not stated" with dates in hand.

Pin five referral events to five dates

Five events decide most questions, and each one should carry the version live on its date:

  1. Agreement signed. The terms require it before you submit introductions, so this date comes first.
  2. Introduction recorded. From this date the company has 90 days to submit the verified application that earns credit, a clock that runs apart from contact protection, as attribution versus contact protection explains.
  3. Verified application. Attribution locks when the application is submitted.
  4. Acceptance and handoff. Section 5 of the terms puts the payment deadline at "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."
  5. Reward paid or recalculated. Reductions follow section 6 and come with SourceX's explanation and calculation.

If two partners' introductions collide, these dates are what two partners introducing the same company turns on. The journey from submission to recorded payment is mapped in follow a data referral to recorded payment.

The terms-version recordkeeping sheet

One row per event, kept in a spreadsheet or a notes file beside the saved PDFs. Write each version stamp in full, revision suffix included; the Illustrative example below shortens the first one to "2026-10-12 revision" because the changelog does not show which revision was live on a given day.

EventDate (Illustrative)Agreement in forceTerms version liveSigned addendumCopy keptWhat the row lets you check
Agreement signed15 Oct 2026Channel Partner Non-Circumvention and Non-Disclosure Agreement, as signed2026-10-12 revisionNoneSigned PDF and signing recordSection 9: it remains in force as signed
Company screened15 Oct 2026Same2026-10-12 revisionNoneDated screening noteCriteria as of that date
Introduction recorded16 Oct 2026Same2026-10-12 revisionNoneExported email and portal entryDay 0 of 90
Verified application24 Oct 2026Same2026-10-22.2NoneThe company's note of its dateSection 3's relationship wording, added from 2026-10-21
Addendum adopting current textNot yet signedEarlier agreement until signedRecord on the dayOffered under section 9Signed addendum once it existsThe provisions it expressly changes
Acceptance, handoff, paymentNot yetRecord on the dayRecord on the dayRecord on the daySourceX's explanation and calculationSection 5 deadline; section 6 reductions

Row four is the reason the sheet exists. The introduction happened under one version and the application under another, and the section 3 wording on existing relationships arrived in between. The changelog does not say which text decides whether this company was new. A partner with this sheet can ask that question in two sentences; a partner without it is reconstructing dates from memory.

Four partners, four governing texts (Illustrative)

Partner (Illustrative)What they signedThe question that came upText that governsWhat they needed to have kept
Partner 1The agreement under its earlier title, 14 Oct 2026Does it still apply after the rename?Terms section 9: it remains in force as signed, and an addendum is offeredThe signed copy, and the addendum if they sign it
Partner 2Channel Partner Agreement version 2026-10-19 with the standard Schedule A, 23 Oct 2026Does the website or Schedule A set the rate?Terms section 8 and agreement 7.2: the signed Schedule A prevails on rate and calculation baseThe signed copy and its signing record
Partner 3The same agreement plus a signed addendumDoes the addendum change attribution?Agreement 7.2: an addendum overrides only provisions it expressly identifiesThe addendum's exact wording
Partner 4The same agreement; a reward was later recalculatedWas the reduction applied correctly?Terms section 6 and Schedule A paragraph 7The terms version in force, SourceX's calculation and the payment records

Partner 4's arithmetic, Illustrative: an Actual Supplier Payout of $240,000 produces a reward of USD 62,000, because USD 50,000 plus 5% beats 15% at that size. If the payout is later reduced to $200,000, the reward is recalculated to USD 60,000 and the USD 2,000 difference is adjusted. Had the payout been $500,000, the reward would be USD 75,000, and a reduction to $440,000 would bring it to USD 72,000: the USD 50,000 element stays with the first qualifying transaction and only the 5% element moves. Checking either result means knowing which formula applied and whether this was the company's first qualifying transaction or a repeat within the Repeat Window, which is what the sheet records.

A copy you can still read in two years

Keep each copy complete and reproducible. Where a U.S. law requires a contract to be retained, federal e-signature law accepts an electronic record that accurately reflects the information and stays accessible, in a form that can be accurately reproduced later by transmission, printing or otherwise. Nothing in the program asks you to meet that statute, but it is a sound test for your own folder:

  • the full terms page saved as a PDF with the version stamp visible, not a cropped screenshot;
  • the signed agreement as delivered, with the signing record that names the document version and signature date, which the sample agreement requires;
  • any addendum, signed, kept with the agreement it changes;
  • a calculator screenshot only as a note, since the terms call portal and calculator estimates projections, not promises.

Partners who compare several programs face the same versioning problem across each of them; refreshing a program comparison when terms change sets out that routine, and the referral terms explained reads an earlier version clause by clause.

Asking a version question with the least paper

Send hello@sourcex.si five items: the agreement's title, version and signature date; the terms version or versions involved, with the dates you relied on them; the sentence or sentences you are relying on, quoted; the event dates from your sheet; and the question in one line. If you are giving formal notice under the agreement rather than asking, the sample agreement says email notice takes effect on acknowledged receipt and an automated send event is not acknowledgment, so keep the reply with the sheet. More attachments rarely help. A quoted sentence with a version stamp usually does. More attribution guides are in the guides hub.

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.

Start the sheet on the day you sign: register as a partner, save the signed agreement with its signing record, note the version stamp on the program terms, and date your first screening note against who qualifies.

  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

If no snapshot is required, why keep one at all?

Because a question is answered by quoting words, and the words on the website change. The saved copy shows what you read and when; it does not override your signed agreement, and it does not need to for the log to be useful.

Does a new version of the website terms change an agreement I already signed?

Not by itself. The terms say signed agreements are never silently replaced, and the sample agreement says website updates, calculator changes and dashboard edits do not change it. Changes need a writing both sides sign; some changelog entries, such as the reward calculation from version 2026-10-12, say they reach earlier referrals.

Which version decides a question that falls between an introduction and an application?

The changelog does not say for most entries. Quote both versions, give the event dates and ask SourceX in writing; do not assume the earlier or the later text wins.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si
  4. refer.sourcex.si/who-qualifies
  5. uscode.house.gov/us/usc/t15/s7001

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