# Referral applications vs unique companies | SourceX

Canonical: https://refer.sourcex.si/guides/the-difference-between-applications-and-companies-referred
Last updated: 2026-11-05

Applications count submissions; companies referred count the businesses a fund actually put in front of SourceX. The two numbers drift apart whenever a company applies twice, a second contact at the same business applies, a trade name and a legal name are logged separately, or subsidiaries apply on their own. Report companies, not applications: run every submission through a deduplication bridge, roll entities up to their group, then split the companies into credited, not credited and pending.

The distinction matters because the program itself counts companies. One partner is credited per company, the reward cap is set per referred company, and a parent company and its subsidiaries count as one company for that cap. A slide that says "23 applications" invites a committee to imagine 23 chances; if those applications came from 14 companies, there were 14 chances at most, and 14 caps.

## What each count measures, and the unit behind it

Name the unit before counting anything. Even official statistics do: the Census Bureau's glossary for its Statistics of U.S. Businesses defines an establishment as a single physical location, notes that it is not necessarily identical with a company, which may consist of several, and defines firms and enterprises as different groupings of establishments under common ownership or control. Three counts of one economy, each correct for its own question.

A referral report needs the same discipline.

| Count | Unit | Question it answers | Where it comes from |
|---|---|---|---|
| Link sends | A message or link the fund sent | How active was the platform team? | The fund's log |
| Applications | One submission at SourceX's application page | How many forms followed our introductions? | The company's confirmation and the portal |
| Unique legal entities | One registered company | How many separate businesses applied? | The bridge below |
| Companies referred | A parent and its subsidiaries together | How many companies did we refer? The headline | The bridge below |
| Credited companies | A company credited to the fund | For how many did our introduction count? | The portal |

**Population.** Every application record the fund can tie to its own introductions, dated within one quarter. **Reporting period.** Read every record on one cutoff date; a company is counted once, in the quarter of its first application, however many submissions follow. Under SourceX's process the company applies itself, so the fund's log holds what the company or the portal confirms, never a form the fund filled in on the company's behalf.

## Five ways one company turns into several applications

1. **Repeat submissions.** An applicant restarts an unfinished form, or applies again after a pause.
2. **Second contacts.** The CEO applies, and so does the CFO who was asked to look into it.
3. **Name pairs.** One record carries the trade name, another the legal name of the same entity.
4. **Subsidiaries.** Two entities in one group each apply, often because different people know about the program.
5. **Two colleagues, one company.** Two people at the fund each sent a link to the same CEO. Within a firm, who should register is settled in [who gets referral credit, the firm or the individual](/questions/who-gets-referral-credit-firm-or-individual).

A sixth situation looks similar but is a credit outcome, not a duplicate in your own log: SourceX already knew the company. The program terms treat any earlier application, relationship or valid introduction as a duplicate, and count any earlier lead, account or email correspondence as a relationship. That company is still one company referred; it is simply not credited to you. The same applies when a partner outside your fund got there first, as [what happens if two partners introduce the same company](/questions/what-happens-if-two-partners-introduce-the-same-company) explains.

## The entity-deduplication reconciliation

The bridge takes the raw application records and removes repetition one rule at a time, so every reduction has a reason a reviewer can check.

**Bridge for one quarter (Illustrative).** Invented records from a fund platform team.

| Step | Rule | Records removed or regrouped | Remaining |
|---|---|---|---|
| 1. Start | Every application record tied to the fund's introductions | None | 23 records |
| 2. Repeat submissions | Same applicant, same entity, applying again; keep the first dated record and attach the rest | 3 | 20 |
| 3. Second contacts | Different people applying for one legal entity | 2 | 18 |
| 4. Name pairs | A trade name and a legal name that resolve to one registration number | 2 | 16 legal entities |
| 5. Group roll-up | Subsidiaries rolled into their parent, one company for the cap | 2 | 14 companies |

Then split the 14 companies by what the portal shows at the cutoff: 9 credited, 3 not credited after duplicate review and 2 pending verification. The fund does not learn whose earlier contact or introduction decided the 3, because partners never receive access to other partners' records or applicant documents.

**Matching keys, strongest first.**

- **Registration number** from the registry where the entity was formed. Same number, same entity.
- **Root web domain.** Probably the same entity, but confirm: groups and brands share domains.
- **Normalized name and location.** A candidate only. A person decides.

Never merge on a person's name, a shared investor or an industry and city alone. Keep every submission attached to its company row, so any merge can be reversed. For the identity register a fund keeps before any outreach, see [how to avoid counting the same company across three networks](/guides/how-to-avoid-counting-the-same-company-across-three-networks); this bridge is the reporting-time check that follows it.

## One row per company, with its submissions attached (Illustrative)

Five of the 14 company rows carry merged records; the other nine companies each sent a single application.

| Company row | Entities | Applications attached | What merged them | Status at cutoff |
|---|---|---|---|---|
| CO-01, 380-person field-services group | 3: parent and two subsidiaries | 4 | 1 repeat, 2 subsidiaries rolled up | Credited |
| CO-02, 210-person freight broker | 1 | 3 | 1 repeat, 1 second contact (the CFO) | Credited |
| CO-03, 150-person claims processor | 1 | 2 | 1 name pair: trade name and legal name | Pending verification |
| CO-04, 95-person engineering consultancy | 1 | 2 | 1 second contact (the COO) | Not credited after duplicate review |
| CO-05, 640-person contact center operator | 1 | 3 | 1 repeat, 1 name pair | Credited |

Read across: 14 of the 23 applications sit behind these 5 companies. The remaining 9 companies split 6 credited, 2 not credited and 1 pending, which brings the totals back to 9, 3 and 2.

**Two cases the bridge cannot settle.** If another partner introduced a sister company of CO-01, or the parent had earlier contact with SourceX, the effect on credit is not settled in the published terms; SourceX decides it in duplicate review, so the row records the group link and waits for the portal. And when a group changes after the quarter, through an acquisition for example, keep the bridge as of its cutoff date and note the change in the next one; after a sale, the acquirer's CEO decides for the business.

## What the quarterly report should say about companies referred

> Q3 (Illustrative): 14 companies referred, made up of 16 legal entities and 23 applications. Of the 14, 9 are credited to us, 3 were not credited after duplicate review and 2 await verification. Applications per company: 23 to 14.

Applications appear once, as a workload line, and the ratio of applications to companies is tracked from quarter to quarter. No benchmark for that ratio exists; a falling ratio usually means introductions that reach the right person the first time. Pending companies stay in the report as pending until the portal moves them. The [explanation for company owners who were referred](/questions/someone-referred-my-company) is worth sending to CEOs who ask why a colleague also applied.

Keep money out of this report. Credit is not a payment: a lead, meeting or signed agreement alone does not earn a payable reward, and a reward exists only after SourceX has paid the company and the payment conditions are met. Multiplying 14 companies, or worse 23 applications, by an assumed payout and annualizing it produces a figure no event supports. The most the count can tell a committee about rewards is a ceiling: one cap per company, for as long as the company is the same company.

## Methods note and where deduplication goes wrong

**Methods note.** The counting units, the credit rule and the one-company-per-group rule for the cap rest on Version 2026-10-22.2, since replaced by version 2026-11-04 of SourceX's program terms and on its who-qualifies page, both read on 2026-10-26; the unit discipline follows the Census Bureau's SUSB glossary. The bridge and every number in it are invented. The method measures how many distinct companies sit behind a fund's application records and how they stand on credit. It does not measure review outcomes after credit, demand for any company's records or any payout, and SourceX has not published application or company counts for this program.

Where it goes wrong:

- **False merges.** Two companies with one trade name in different states are two companies. Merging them carries one company's facts onto the other.
- **Missed merges.** A subsidiary trading under its own brand slips past name matching; ask the CEO about the group structure.
- **Personal data creep.** Applicant names and emails are personal data. The bridge needs the entity, the date and the role of the person who applied, not their inbox.
- **Partial visibility.** Partners do not see other partners' records, so a duplicate outcome comes without its backstory. Record the outcome, not a theory.
- **Small numbers.** At 14 companies, one merge moves the ratio noticeably. Print counts beside any ratio.

## The companies worth an application in the first place

The cleanest bridge starts with fewer, better introductions. Before it ever becomes a row in the bridge, a company worth introducing should show a peak of 50+ full-time employees (no contractors in that count), a documented operating history, rights to license its own records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The CEO authorizes a licensing discussion and signs for the company, so the introduction goes to the CEO, or to someone the CEO has asked to apply, and one person at the fund sends it.

Before the link goes out, keep discovery at metadata level: record types, rough volume, years covered, the system and who runs it. Nobody requests files, samples or logins. What remains for SourceX's review, whether the records match a current program and whether contracts restrict their reuse, is not something a count of applications can predict. Whoever submits must have signed the SourceX Channel Partner Agreement; partners who signed it under the earlier name, Channel Partner Non-Circumvention and Non-Disclosure Agreement, remain bound by that version. How to help a company through the steps after it applies is covered in [supporting a company during information gathering](/guides/how-to-support-a-company-during-information-gathering), and more reporting pages are in [the guides hub](/guides).

## 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.

When one person at your fund owns each CEO relationship and each company will apply once, [set up your partner account](/register), test each company against the [qualification page](/who-qualifies) and study the duplicate rules in the [partner terms](/terms) before the first submission.

Counting companies referred is a reporting job for the platform team; deciding whether SourceX is worth evaluating as an investment is a separate exercise, and the [SourceX investor overview](https://sourcex.si/investors) offers investor materials on request.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.census.gov/programs-surveys/susb/about/glossary.html
- https://sourcex.si/investors
