The program's own home page says it in one line: a submitted lead, meeting or signed agreement alone does not trigger payment. This page shows why, document by document, so a partner finance manager can tell which signatures move a referral forward and which conditions still decide the cash.
The calculation base and the documents that govern it
Two questions decide any reward: how much, and when. The amount comes from the calculation base, Actual Supplier Payout: compensation actually paid to the company for selected data that reaches Closing and the qualifying completed handoff, under its signed licensing agreement and any Confirmation and amendments. Ranges proposed before signing, data that never closes and money not yet paid are not part of it. The timing comes from section 5 of the program terms, version 2026-11-04.
Several documents touch the same deal, and they rank in a fixed order for your reward:
| Document | Signed by | What it decides for the partner |
|---|---|---|
| Channel Partner Agreement and its Schedule A | You and SourceX | Rate, calculation base, Minimum Transaction, Repeat Window, attribution and payment rules; a signed Schedule A prevails over the public terms |
| Signed addendum | You and SourceX | Overrides a provision only where it expressly says so |
| Public program terms | Published by SourceX | Govern attribution and rewards where no signed document differs |
| Master, Confirmation and amendments | The company and SourceX | The company's own deal, dataset and compensation; never the reward deadline |
| Acquisition Partner's data license | SourceX and the Acquisition Partner | What counts as final written acceptance of the dataset |
One line in section 8 of the terms prevents a common mistake: a company's payment timetable, including a Net 60 clause, never determines when a referral reward is paid.
Six signatures and one notice, and what each leaves open
Read this as a ledger. Every row is a document a partner hears about during a deal, with what it fixes and the condition it leaves open.
| Step | Document | What it fixes | What it leaves open | Status a partner can expect |
|---|---|---|---|---|
| 1 | Your Channel Partner Agreement | Your right to submit introductions; no introduction alone creates a commission | Everything about any company | Nothing to track yet |
| 2 | The company's Master Supplier Licensing Agreement | The framework, signed once after qualification; Day 1 starts an assessment initially up to 30 days | Whether any dataset is ever selected, and its price | Nothing to track yet |
| 3 | The Dataset Deal Confirmation | The exact dataset, payout, rights, processing route and Closing Deadline | Acceptance, Closing and payment | Estimated |
| 4 | SourceX's data license with the Acquisition Partner | Commitment that lets SourceX authorize preparation; positive interest is not yet a purchase | The Acquisition Partner's final written acceptance, meaning unconditional selection of the complete, validated dataset | Estimated |
| 5 | A signed amendment | A changed scope or price, or a part that can be bought separately | A partial handoff counts on its own only if SourceX and you also agree in writing | Estimated, on the amended amount |
| 6 | A renewal or repeat license | A new transaction with the same company | Whether it was first agreed inside your term or the six-month Protection Period, and inside the 12-month Repeat Window that pays 15% | Estimated, or nothing |
| Notice | The Closing Notice (the company signs nothing further) | The company's fee is earned under its signed terms | Cleared funds from the Acquisition Partner, payment of the company, finance approval, your details | Estimated until every condition is met |
The surprise for most finance teams is the last row. The sample Channel Partner Agreement says the company's fee is earned at Closing and is not conditional on the Acquisition Partner paying SourceX, and in the same paragraph that this does not remove the cleared-funds condition for the reward. A company can be paid while your reward is still waiting.
The payment-condition timeline
Two clocks run through one deal, and neither starts at a signature. The attribution clock starts when your introduction is recorded: credit attaches when the company submits a verified application within 90 days of it. The payment clock starts at day 0, the later of two anchor events: the Acquisition Partner's final written acceptance of the complete, validated dataset, and completed handoff of that dataset to the Acquisition Partner. The deadline is day 60.
Illustrative. A 240-person freight forwarder licenses dispatch and exception records. The order of events below is one possible sequence; real deals can differ.
| When | Event | Signature? | Effect on the partner |
|---|---|---|---|
| Introduction recorded | You submit, under a signed Channel Partner Agreement | Yes (earlier) | Attribution clock starts |
| 3 weeks later | The company submits a verified application | No | Credit attaches; inside 90 days |
| Week 6 | Master signed | Yes | Assessment begins |
| Week 11 | Confirmation signed at $160,000 | Yes | A projected $58,000 appears |
| Week 13 | SourceX signs the Acquisition Partner's data license | Yes | Preparation authorized |
| Day minus 14 | Handoff to the Acquisition Partner completed | No | First anchor |
| Day 0 | Acquisition Partner's final written acceptance | No | Later anchor; deadline set at day 60 |
| Day 32 | Acquisition Partner's payment clears to SourceX | No | Condition met |
| Day 41 | The company is paid $160,000 | No | Condition met; base fixed |
| Day 52 | Finance approval, with your tax and payment details already on file | No | Payable by day 60 |
Four signatures appear on that table, and none of them changed the partner's status from Estimated. Each of the conditions behind them did.
Six contracts signed, six different results (Illustrative)
Every row has at least one signed agreement. Generic companies and invented amounts; none of this forecasts what any company is paid.
| Case | What was signed | Amount the company was actually paid | Partner's amount | Deciding term |
|---|---|---|---|---|
| A. On time | Confirmation at $160,000 | $160,000 by day 41 | $58,000 by day 60 | Terms, section 5 |
| B. Never closed | Confirmation at $90,000 | $0; data declined at the Closing Deadline | $0 | Data that never closes is excluded (section 4); the amount also sits below the USD 100,000 Minimum Transaction |
| C. Closed, buyer funds late | Confirmation at $240,000 | $240,000 by day 50 | $62,000, paid soon after the day-75 funds clear | No new 60-day period (Schedule A 5.3) |
| D. Paid in two parts | Confirmation at $300,000 | $150,000, then $150,000 | $57,500, then $7,500 | The USD 50,000 element with the first part that meets every condition, the 5% element in proportion as each part is paid (Schedule A 5.4) |
| E. Renewal signed too late | Renewal at $120,000, first agreed eight months after the partner's agreement ended | $120,000 | $0 | Repeat transactions after the Protection Period (Schedule A 6) |
| F. Already known to SourceX | Confirmation at $150,000 | $150,000 | $0 to this partner | Earlier lead, account or email makes it a duplicate (section 3) |
Two refinements. In case C, the company is paid on day 50 because its fee does not wait for the Acquisition Partner, but the deadline passes on day 60 with the cleared-funds condition still open; the reward follows when the funds clear on day 75. In case E, the same company's renewal would have counted if it had been agreed within six months of the agreement ending, at 15% of its payout as a repeat inside the 12-month Repeat Window. Agreed later, it earns nothing unless you and SourceX agree otherwise in writing, so note your agreement's end date beside every company likely to renew.
A seventh signature can also be worth less than the first: a second Confirmation with the same company pays 15% of its payout and nothing more, because the USD 50,000 floor applies once per referred company and does not return on a repeat, renewal or amendment; first agreed more than 12 months after the first qualifying Closing, it falls outside the Repeat Window. Longer sequences are worked through in the renewal and repeat guide and the ledger for rewards paid in parts.
One more timing trap sits outside the table. A company that invoices a few days after Closing is due its payment within 60 calendar days of that valid invoice, so its payment date can land after your day 60. That does not move your deadline, because the company's timetable never sets it. It does delay payment, because payment of the company is itself a condition: the reward follows once the company is paid.
Sort every referral into payable, waiting, projected or zero
At any reporting date, put each referral in exactly one bucket, using the portal's statuses on the rewards page.
| Bucket | Test | Cases above, on day 70 |
|---|---|---|
| Paid or payable | Both anchors reached and every condition met | A at $58,000; D's first part at $57,500 |
| Accrued, conditions open | The company has been paid, and something on SourceX's or your side is outstanding | C at $62,000, waiting on cleared funds |
| Projected only | Signed, not yet paid to the company | D's second part at $7,500 |
| Zero | Not closed, outside the protection period or Repeat Window, a duplicate, or below the Minimum Transaction | B, E, F |
On those numbers, $115,500 is payable or paid, $62,000 is waiting on one condition, and $7,500 is projected. Only the first belongs in a cash forecast as money to expect. SourceX does not publish how often Confirmations reach Closing, so applying a success rate to the projected bucket means inventing one; carry projections at face value with their stage instead. If a company's compensation is later cut, the reward is reduced in proportion, so keep each record open until the reward shows Paid. The two-gate guide separates credit questions from payment questions, and the stage-to-cash reconciliation shows the same buckets across a fund's whole portfolio.
Four facts to confirm in writing before a signature reaches your forecast
- Your own paper. Whether you signed a Schedule A or addendum that differs from the default rate, base, floor or Minimum Transaction.
- Your agreement's dates. The Channel Partner Agreement runs for one year, renews only with fresh signatures, and protects introductions for six months after it ends. Note both dates beside every referral that could renew.
- Partial deliveries. Whether SourceX has agreed in writing to treat a separately selectable part as its own qualifying handoff.
- Your details. Tax and payment details on file before day 0, so the only open conditions are ones you cannot control. The 60-day deadline guide shows what happens when they arrive late, and the payable-reward explainer lists every condition in order.
Before any of this matters, the company has to fit: 50 or more full-time employees at peak, contractors excluded, years of documented records, rights to license them and a CEO who wants the conversation.
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.
If you know a company whose CEO wants the conversation, register for a partner link with your tax and payment details already complete, check the company against who qualifies, and keep section 5 of the program terms beside your forecast so that no signature is counted as cash.