What happens if a referred company applies through a different channel?
If a company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) you've introduced to SourceX later applies through a different channel, the program's attribution rules come into play. The general principle is that the first valid referral within the attribution window gets credit once the company completes its verified application. Once credit is locked, subsequent introductions or applications from different channels for the same company do not override the initial attribution.
How attribution works
When you refer a company, your referral is typically associated with that company within SourceX's system. If the company then independently contacts SourceX or uses another partner's link, the system performs a check to see if an existing referral is already on file. If your introduction was the first valid one within the 90-day attribution window, it receives the credit.
Duplicate review
Situations where a company is introduced by multiple parties, or is already in discussion with SourceX, trigger a duplicate review process. This process assesses the timing and validity of each introduction. Key factors include:
- Existing relationships: If SourceX already had an application, relationship or earlier valid introduction with the company before your introduction, it is not credited to you. Under section 3 of the terms, a relationship includes any earlier lead, account or email correspondence, however it began.
- Competing introductions: If another partner's valid introduction of the same company came first within the 90-day attribution window, that introduction receives the credit.
Why this process exists
The duplicate review and attribution rules are designed to ensure fairness and prevent multiple partners from claiming credit for the same opportunity. It protects the integrity of the referral program by clearly defining how eligibility is determined in complex scenarios.
Ensuring your referral is tracked
To maximize the chances of your referral being properly attributed, encourage the company to use your specific referral link or ensure they mention your introduction if they contact SourceX directly. You can monitor the status of your referrals through your partner dashboard.
For more details on what makes a referral eligible and the full terms, please consult the FAQ and the program terms.
Rewards on a company's first qualifying transaction are calculated as the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, and repeats within the Repeat Window pay 15%. A lead, meeting or signed agreement alone does not trigger payment. See the program terms.
A different domain on the application is a matching problem, not a new rule. SourceX decides credit from dated records, and it goes to whichever valid introduction of a new company came first inside the 90-day attribution window, once that company files a verified application. The domain matters twice. Your introduction record names one, so the applicant must be traceable to the same legal entity, and section 3 counts any earlier email between SourceX and the company, from whichever domain it came, as an existing relationship.
The sections below add the domain case to the channel rules above: what a second domain can mean, how to rebuild the dates, an evidence sheet that ties each domain to an entity, three contrasting cases and the short note to send when review opens.
Two questions a second domain raises, and which one the partner can answer
Is the applicant the company you introduced? This is an identity question, and public evidence can usually settle it. The partner agreement requires every introduction record to identify the company, its domain, the partner, the opportunity, the introduction method and timestamps. When the application arrives from another domain, SourceX has two domains to reconcile, and a partner who already tied both to one registered entity saves that step.
Did SourceX already know the company under any domain? This one is not yours to answer. In the terms, a relationship means any earlier lead, account or email correspondence the company has had with SourceX, however it began, and SourceX checks its own records before inviting an introduced company. A company that wrote to SourceX last spring from its old brand domain was already known, even if your introduction used the new one. What you can do is ask the CEO, before you introduce, under which names and domains the company might have been in touch.
Keep the two apart. Identity evidence shows the names match; it never proves priority, and the first valid introduction still governs when two partners or an earlier contact are involved.
Rebuild the timeline across every domain the company uses
Put every dated event on one line, whatever domain it came from. Days are counted from your recorded introduction, because Schedule A of the agreement credits a verified application within 90 days of it.
| Day | Event | Domain it carries | Who holds the record |
|---|---|---|---|
| Before 0 | Any earlier lead, account or email between SourceX and the company | Any domain or name the company has used | SourceX; the CEO may remember |
| 0 | Your written introduction: portal submission, tracked application or email | The domain you recorded | You and SourceX |
| Variable | The company changes its brand, email system or group structure | Old and new domains | Public: the company's site and registry |
| Variable | The CEO replies or forwards from another address | The other domain, or webmail | You |
| Application day | The company submits its application | The domain it applied from | SourceX; ask the CEO for the date |
| Application day minus day 0 | The day count | Not applicable | Your arithmetic, against 90 |
Two rows decide most cases: the first, which only SourceX can fill in completely, and the last. The rest of the timeline only connects them.
The domain-to-legal-entity evidence sheet
One row per domain you see. The aim is a public link from each domain to one registered entity, written down before anyone asks.
| Domain you see | What it can mean | Public evidence that ties it to an entity | What to record | Who settles it |
|---|---|---|---|---|
| New brand domain after a rebrand | Same company, new name or brand | The new site's legal pages naming the registered company; a registry entry with an unchanged number | Both domains, the switch date and the registry number | You can show it; SourceX matches it |
| Country-code or regional domain | A branch of the same company, or a separate subsidiary | The regional site's legal notice naming its operator and registration number | Whether that operator is the entity you introduced | SourceX, when the operator is a different entity |
| Parent or holding-company domain | The group applied, or a group executive wrote for the subsidiary | The parent's site or filings listing the subsidiary | Both entities, and which one employs the staff and holds the records | SourceX in duplicate review; the once-per-company floor is settled |
| Acquirer's domain after a sale | The business now sits inside the buyer | A public announcement naming both companies | The entity that holds the records today, and its CEO | SourceX, with the company |
| Personal webmail | Nothing about the company | None: a webmail address identifies a person, not an entity | The writer's role and the company they named | The company, by confirming from its own domain |
| An adviser's or agency's domain | A third party writing for the company | The adviser's own site and the company's confirmation | That the company itself applies | The company and SourceX |
| Look-alike domain | A different company with a similar name | A different registration number or jurisdiction | Nothing: your introduction does not cover it | The public registry |
Registration lookups rarely close a row. ICANN made RDAP the authoritative source for generic top-level domain registration data on 28 January 2025, replacing WHOIS, and its lookup service sends requests for nonpublic registration data to the Registration Data Request Service or the sponsoring registrar. The registrant you can see may therefore not name the company at all. The company's own legal pages and its registry entry are better evidence, and how to find a company's legal entity name shows where to look. For a name change between introduction and application, the rebrand evidence packet has the matching forms; for a sale, read whether referral credit survives an acquisition.
On groups, be precise about what is decided. The terms do not mention parents, subsidiaries or affiliates for credit. Whether a parent's earlier contact with SourceX, or another partner's introduction of a sister company, affects your credit is decided by SourceX in duplicate review. The reward floor is settled: a parent and its subsidiaries are one company for that purpose, so the USD 50,000 floor applies once, to the group's first qualifying transaction, and later group transactions within the Repeat Window pay 15% with no cap.
Three domains, three outcomes (Illustrative)
Illustrative cases with generic companies; the facts are invented and nothing here describes a real referral.
Case A: a rebrand domain. You introduce the CEO of a 160-person freight audit firm on day 0, recorded with its old domain. On day 18 the firm moves its website and email to a new brand; its registered name and number stay the same. On day 44 the CEO applies from the new domain. The governing terms are section 2 of the program terms and section 3.3 of the agreement: a dated written introduction naming the company and its domain, and a verified application inside 90 days. The new site's legal page names the same registered company, so the link is public. Nothing in the terms makes the domain change itself relevant to credit; the open question, as always, is whether SourceX's records show earlier contact under either domain.
Case B: a group domain with an earlier email. About five months before your introduction, the CFO of a parent group exchanged emails with SourceX from the parent's domain about a different subsidiary. On day 0 you introduce the CEO of a 210-person German subsidiary, recorded with its own country-code domain, and it applies on day 26. Section 3 counts earlier email correspondence with "the company"; whether the parent's emails count against this subsidiary is not settled in the terms, so SourceX decides it in duplicate review. Record both entities and the CEO's account of the earlier contact, and promise the CEO nothing about credit. The money side is settled, so the arithmetic is safe to show:
| Entity (Illustrative) | Actual Supplier Payout | How the reward is worked out | Reward |
|---|---|---|---|
| German subsidiary | USD 250,000 | First qualifying transaction: greater of USD 50,000 plus 5% and 15% | USD 62,500 |
| Parent, licensing within 12 months | USD 250,000 | Repeat in the Repeat Window: 15%, the floor is not applied again | USD 37,500 |
| Group total | USD 500,000 | No cap | USD 100,000 |
Case C: webmail after the window. You introduce the CEO of a 95-person claims administrator on day 0. The CEO forwards your note to a personal webmail account while traveling and applies from it on day 97, naming the company. The identity link is easy: the CEO confirms from the company domain. The clock is not. Under Schedule A the verified application has to come within 90 days of the recorded introduction, and the terms are explicit that ongoing contact protection leaves the window where it was. Linking the domains cannot reopen it.
What to send when review opens, and what to keep back
Send nothing unless SourceX asks or a duplicate review opens; disputes go to hello@sourcex.si under section 7 of the terms. When you do write, five lines are enough:
- The legal name and registry number of the entity you introduced, with the date you checked.
- The domain on your introduction record and the domain on the application, each with the public page that ties it to that entity.
- The timestamp and method of your written introduction.
- The day count from introduction to application.
- The CEO's own one-sentence account of any earlier contact with SourceX, under any name or domain.
Keep back message headers, forwarded company correspondence, mailbox screenshots, the company's mail-server or DNS records and anything about another partner. SourceX holds most of the dated record already, and partners never receive access to other partners' records, so a longer packet adds risk without adding evidence. The difference between a written introduction and a link click is set out in written introduction vs referral link attribution, and the clock itself in what an attribution window is. If two partners are involved, what happens when two partners introduce the same company applies after identity is settled.
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.
Before your next introduction, write the company's legal name and every domain it uses into one row, then request a partner link, confirm the company meets who qualifies and have sections 2 and 3 of the program terms to hand. More attribution guides are in the guides.