A long packet feels thorough and often reads as uncertain. A short one that puts six dates in order and asks a precise question is easier to review, and it is the kind of record the program's own documents say decisions are made from.
Most of the evidence is already on SourceX's side
The terms say SourceX checks its own records before inviting an introduced company and decides attribution from dated records, including written introduction evidence, existing applications and preexisting relationships. The sample Channel Partner Agreement adds that SourceX keeps dated introduction evidence and attribution decisions, and maintains records sufficient to explain an attribution decision. Your job is not to rebuild SourceX's file. It is to supply what that file may lack and to frame the question.
| Evidence | Who holds it | What to do with it |
|---|---|---|
| Your portal submission and its timestamp | SourceX, and you through your dashboard | Cite the date; no need to re-send it |
| The link visit | SourceX, which records it when the company opens your link | Mention it; a click alone does not decide credit |
| The company's application and its date | SourceX and the company | Ask the company for the date and the name it used |
| An introduction email sent outside the portal | You | Attach it, exported with its full header |
| Written confirmation of an introduction made in person or by phone | You | Attach it; the written date is the one that counts |
| The company's account of earlier contact with SourceX | The company | Include its short statement, in its words |
| Another partner's messages or records | Not you | Never include them |
| The company's data, exports or screenshots of its systems | The company | Never include them |
Line the dates up in one column
Before writing anything, put every date on one list, earliest first: the day you signed the partner agreement, which the terms require before any introduction; your written introduction, with time and time zone; the link visit, if your dashboard shows one; the day the company submitted its application; and the number of days between introduction and application. The sample agreement measures the window as 90 days from the recorded introduction to a verified application.
Take email timestamps from the message itself, not from an inbox list. In Gmail, Google's help center says opening the message and choosing More, then Show original, opens the full header in a new window, ready to copy. Microsoft's support page says new Outlook and Outlook on the web show it under More actions, View, View message details, and classic Outlook for Windows under File, Properties, in the Internet headers box; it describes headers as listing details such as the sender and the mail servers a message passed through. Export the original message rather than forwarding it, so the date in the file is the one from the day you sent it. The sample agreement also says a dispute must not erase original evidence, so leave the original where it is.
The minimal evidence submission template
Seven fields, one page. Fill every field or write "not known"; do not leave one out silently.
| Field | What to write | Example (Illustrative) | Leave out |
|---|---|---|---|
| 1. The question | One sentence naming the decision you want | Is my 4 Aug 2026 email the first valid introduction of this company? | Arguments about fairness or effort |
| 2. The company | Legal name, any trading name, web domain, registration number if known | A 220-person regional freight broker, named as in its registry entry | Staff names beyond the CEO's role |
| 3. Your agreement | Title, version and signature date | Channel Partner Agreement, version 2026-10-19, signed 1 Aug 2026 | The whole document |
| 4. Your written introduction | Date, time with time zone, channel, recipient's role | 4 Aug 2026, 09:12 UTC-5, email to the CEO with the partner link | Forwarded copies |
| 5. The application | Date and name used, as the company reports them | Applied 21 Aug 2026 under its legal name | The application's contents |
| 6. Earlier contact | The company's statement on whether it applied, held an account or corresponded with SourceX before | None, per the CEO's email of 25 Aug 2026 | Your guesses about SourceX's records |
| 7. Attachments | At most three, each named | Introduction email with header; the CEO's statement | Anything not listed in fields 1 to 6 |
Field 6 matters more than partners expect. Under the terms, a relationship exists if, before your introduction, SourceX had the company as a lead or an account or exchanged email correspondence with it, however that began, and a company with such history is not credited to a later partner. The company knows its own history; you usually do not. If the date or spelling of the company's name is the issue rather than credit, correcting a mistyped company name has a narrower request, and a question about which terms version applied belongs with saving the applicable terms version.
Never attach these, however helpful they look
- Company records of any kind: data samples, exports, system screenshots, inventories. The sample agreement gives a partner no authority to share a supplier's inventory, records, raw data or personal information.
- Another partner's correspondence, even if the company forwarded it to you.
- Personal details beyond names and roles the question needs.
- Long email chains when the first message proves the date.
Keeping it small is not only courtesy. The European Union's General Data Protection Regulation writes the same idea into law as data minimisation: personal data must be adequate, relevant and limited to what is necessary for the purpose. In a 2025 judgment the Court of Justice found the systematic collection of a title from every customer buying train tickets online disproportionate, because it could have been limited to the customers who actually needed it. A partner packet is a much smaller thing, but the test transfers: if a page does not help decide the question in field 1, it does not go in.
Credit and fit are decided separately
Attribution evidence settles who would be credited if a reward ever exists. It does not show the company fits. The company still needs 50 or more full-time employees at peak (contractors excluded), years of records it created itself, the rights to license them and a CEO who authorizes the discussion, and a lead, meeting or signature alone does not trigger payment. Partners stay at metadata level throughout, describing record types, rough volumes, years, systems and owners. Whether those records match current demand and what a license would cover remain unknown until SourceX reviews the company.
Three questions, three packets (Illustrative)
Illustrative: invented companies and dates, showing how the published text reads rather than real outcomes.
Case 1, an introduction at a dinner. On 3 September 2026 you introduce yourself and SourceX to the CEO of a 160-person facilities services company over dinner. Another partner submits the company through the portal on 15 September. You send your first written confirmation to the CEO on 25 September, and on 30 September the company applies through the other partner's link. The packet: your 25 September email with its header, plus one honest line about the 3 September dinner. Governing text: the sample agreement's rule that oral introductions must be confirmed in writing before protection attaches, and section 2 of the terms on the first valid introduction. On a plain reading the earliest written introduction is the other partner's 15 September submission; SourceX decides, and the packet should not pretend otherwise.
Case 2, the company was already talking to SourceX. In May 2026 a 300-person medical billing company's CFO emailed SourceX about licensing. On 9 September you introduce the CEO, and the company applies on 19 September. The packet: the CEO's statement, in field 6, that the CFO wrote in May. Governing text: section 3 of the terms. On a plain reading no partner is credited, because the company was not new. A complete packet sometimes ends the question, and that saves everyone time; checking for an existing SourceX relationship covers the questions to ask before introducing.
Case 3, a late application. You email the CEO of a 210-person engineering firm on 1 July 2026, and the firm applies on 12 October 2026, 103 days later. The packet: the email header and the application date. Governing text: the sample agreement's 90 days from the recorded introduction, and the terms' statement that the window does not extend because contact protection under the agreement continues. On a plain reading the application falls outside the window. Asking costs a few minutes, but no extra attachment changes the arithmetic.
When two partners' claims collide head on, two partners referring the same company walks through the evidence checks, and rebrand attribution evidence handles a company whose name changed along the way. The record-keeping habits that make a packet easy to assemble are in how to prove a referral.
Where the packet goes and what comes back
Start in your dashboard: SourceX's contact page sends questions about an existing referral or reward there, and status updates appear there. If the status does not answer it, send the packet to hello@sourcex.si; the terms ask for the referral details and supporting evidence, and say SourceX reviews the case and communicates its decision. Expect information about your own referral, such as status and reference codes, and nothing about anyone else's: partners never receive access to other partners' records, applicant documents or confidential buyer information. If the question becomes a formal dispute under the signed agreement, the sample agreement starts with 30 days of good-faith written notice and discussion. More attribution topics 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.
The cheapest evidence is created before anyone asks for it: register as a partner and sign first, confirm the company against who qualifies, send a dated written introduction to the CEO, and keep the program terms section on attribution beside your log.