Does showing the payment sequence reduce partner confusion? A two-layout comprehension test that sets SourceX's payment conditions in their real order beside the same sentences in the terms' own order, asks partners to place five status updates, and counts every reader who turns the order into a timetable

Short answer

Nobody knows yet, so test it. An ordered display of SourceX's published payment conditions should help partners place a status update, such as a signed agreement or an accepted dataset, at the right point and see which two events start the 60-day deadline. It can also backfire if the order reads as a timetable or as one strict chain. Compare two layouts of identical sentences, score five placement tasks, and count every partner who infers a date the terms never give.

Visual briefFull-size diagram
Three ordered steps, credit, company signs, and Closing with handoff, lead to a clock box reading the 60-day deadline starts at the later of acceptance and handoff, then to a box of five conditions met in any order, cleared funds to SourceX, company paid, finance approval, your payment and tax details, and lawful to pay, and finally to reward paid; a note says a condition still open at the deadline is paid once met with no new 60 days.
Layout B of the test, drawn from terms sections 2, 4 and 5 (Version 2026-10-22.2). An order, not a timetable.

What partners misread about the payment trigger, item by item, is the subject of the payment-trigger knowledge survey. This page tests one change to the material itself: putting the conditions in order.

The sequence the terms describe, and where it stops being a chain

Read terms sections 2, 4, 5 and 8 together and three different kinds of statement appear. Only the first kind is a sequence.

Ordered steps.

  1. Credit. "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application" (section 2). Credit is not payment.
  2. The company signs with SourceX. "A lead, meeting or signed agreement alone does not earn a payable reward" (section 5).
  3. Closing and handoff. There is no Actual Supplier Payout to base a reward on until selected data reaches Closing and the qualifying completed handoff and the company is actually paid (section 4).

One clock. The deadline is "60 calendar days after the later of" two events (section 5): the Acquisition Partner accepting the full, validated dataset in writing, and the dataset's handoff to it being completed. Either event can come first; the later one starts the clock.

Conditions in no fixed order. Payment also requires Acquisition Partner acceptance, its payment received by SourceX in cleared funds, payment of the underlying supplier compensation, SourceX finance approval, the partner's payment and tax details, and that payment is lawful (section 5). If one is still open at the deadline, "the reward is paid promptly once it is satisfied; no new 60-day period begins."

A second clock that is not the reward's. After Closing the company invoices SourceX, and its payment falls due within 60 calendar days of a valid invoice unless other terms are signed (SourceX's how-it-works page). Section 8 is explicit: "a supplier's payment timetable, including any Net 60 clause, never determines when referral rewards are paid." Two 60-day periods start from different events, and paying the company is itself one of the reward's conditions.

The amount sits apart from all of this: by default the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap, paid separately and never deducted from what the company receives (section 4).

Why order could help, and how it could hurt

Plain-language guidance favors order for processes. Digital.gov's guidance on organizing information says, in paraphrase, to set out a process in the sequence the reader and the organization follow, as a numbered list, with general information first and exceptions and conditions later. The U.S. Web Design System's process list guidance adds that such a list should run three to ten steps and that content without a clear logical order belongs in an unordered list (paraphrase). Applied honestly, that means the three ordered steps can be numbered, while the conditions must not be.

The same layout can mislead three ways:

  • A line reads as a timetable. Evenly spaced steps suggest even gaps, and the terms give no gaps at all.
  • A chain implies an order the terms do not set. Numbering the conditions would tell partners that finance approval follows the company's payment, which section 5 does not say.
  • The two clocks merge. A partner who sees "60 days" twice may decide the reward follows the company's invoice period.

Two layouts, identical sentences

ElementLayout A, terms orderLayout B, sequence
SentencesThe quoted and paraphrased sentences above, in the order sections 2, 4, 5 and 8 print themThe same sentences, nothing added or removed
ArrangementContinuous paragraphsThree numbered steps, a clock box, an unnumbered conditions box, then the open-condition rule and the company's invoice clock, each in its own box
HeadingsSection numbersWords taken from the terms only
Durations shownThe 60-day rule onlyThe 60-day rule only
Shared line"The order shows what must happen first, not when."The same line
Version stampTerms Version 2026-10-22.2, since replaced by version 2026-11-04The same stamp

Both layouts are shown in the same place, such as the onboarding email, and both run within a few words of each other in length.

The payment-stage comprehension test

Each task shows one status update. The partner answers three parts: where the referral stands, whether the 60-day deadline has started, and whether a reward is payable now. "Not sure" is allowed on every part.

TaskStatus updateWhere it standsDeadline started?Payable now?Settled by
T1"The company has signed its agreement with SourceX."Step 2NoNoSection 5
T2"The Acquisition Partner has given final written acceptance; handoff is still under way."Clock boxNo; the later event has not happenedNoSection 5
T3"Handoff was completed today; acceptance came ten days ago. The company has sent its invoice."Conditions boxYes, from todayNo; the company has not been paidSection 5
T4"The deadline passed with one condition open; it was met this morning."Conditions boxIt has already runYes, promptly, with no new 60-day periodSection 5
T5"The company's agreement gives SourceX 60 days to pay its invoice."Outside the reward sequenceNot this clockNoSection 8

Scoring. All three parts right is a full answer; the right place with a wrong clock or payable part is partial; the wrong place is a miss; "not sure" is tallied in a column of its own, never merged with wrong answers.

The timetable guard. One open question closes the test: "From what you read, roughly how long after the company signs would a reward be paid?" Two coders sort each answer into one code without knowing the layout:

CodeThe answer...
G0Says no date can be given, or that it depends on conditions being met
G1Gives a number of days, weeks or months after signing
G2Counts 60 days from signing, the application or the company's invoice
G3Anything else, kept verbatim with identifying details removed

Measures. Primary: the share of partners in each layout with at least four of five tasks fully right. Guard: the share coded G1 or G2. Descriptive: over the following 60 days, payment-timing questions each partner sends the partner manager, coded the same way.

  • Unit. A partner who has signed the SourceX Channel Partner Agreement or is completing onboarding.
  • Allocation. A random draw per partner, recorded before launch.
  • Conditions. One sitting, alone, within a day of reading the layout; no lookups during the test.
  • Afterward. Every partner sees the full key with section numbers, whatever their layout.
  • Use of answers. Never to rank partners or limit who may refer.
  • Floor. 20 partners per layout before any comparison; fewer means counts only. That floor is this page's choice, not a statistical standard.

Pause triggers, and the rule for switching layouts

Written and dated before launch:

  1. SourceX publishes a new terms version. Stop, re-key both layouts and all tasks to the new text, and restart the count.
  2. A partner reports that either layout promised a date or a payment. Pause both and check every sentence against the terms.
  3. Layout B draws three more G1 or G2 answers than Layout A at any point. Pause B and review its boxes and spacing.

Layout B replaces Layout A only if its share of partners with four of five tasks fully right beats A by a margin written down before launch, its G1 and G2 answers are no more common, and no single task does worse in B by that margin. Anything else keeps Layout A, or sends a revised B back for another round.

One partner's answers (Illustrative)

Illustrative. An invented partner in Layout B scores T1, T3 and T4 in full, gets partial credit on T2 (thought acceptance alone started the deadline) and misses T5 (thought the company's invoice period set the reward date). The open answer, "about 60 days after the company is paid", is coded G2. One partner decides nothing. If T5 misses and G2 codes cluster in Layout B across the group, the company's invoice clock is sitting too close to the sequence and needs more separation.

Missing, unsure and unfinished answers

Partners who open the test and stop count as started, not finished, in both layouts. "Not sure" answers are reported beside right and wrong ones. Because allocation is random, a difference between layouts can be read as caused by the layout, for this group at this time; differences by role or months since signing are description only.

How much a small gap can tell you

With 20 or so partners per layout, a gap of one or two people means nothing; say so, and publish the result even if Layout B loses. Change the box where misses cluster rather than redesigning the whole layout. For partners who still equate signing with payment, measuring whether partners misunderstand the payment trigger is the follow-up reading, and dashboard estimates are tested separately in testing a referral calculator without anchoring on the maximum.

Where this test can mislead

  • A quiz is not a conversation. Placing a status correctly does not prove a partner will describe it correctly to a CEO.
  • The terms move. Every task is keyed to Version 2026-10-22.2, since replaced by version 2026-11-04.
  • Diagrams travel without their boxes. A cropped sequence that loses the conditions box teaches the chain the test was built to avoid.
  • Volunteers read carefully. Partners who finish an optional test may be the most attentive ones.
  • Signed documents can differ. A signed Schedule A or addendum prevails on its own points (section 8), so the test covers the default terms only.

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 your partners can place a status update without inventing a date, create a partner account, confirm each company against who qualifies and keep the program terms as the text every layout is checked against.

  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 the sequence show typical durations between steps so partners can plan?

No. The terms give one dated rule, the 60-day deadline after the later of acceptance and handoff, and nothing else that a partner could plan on. Any other duration in the layout would be a timetable SourceX has not published.

Which 60 days is the reward deadline?

The one in terms section 5: 60 calendar days after the later of the Acquisition Partner's final written acceptance and completed handoff. The company's own invoice period is a separate clock, and section 8 says a supplier's payment timetable never decides when rewards are paid.

What if a partner has a signed Schedule A with different terms?

The test covers the default published terms only. Section 8 lets a signed Schedule A or addendum prevail on its own points, so a partner with one should read the sequence against that document.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/how-it-works
  3. digital.gov/guides/plain-language/principles/organize
  4. designsystem.digital.gov/components/process-list

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