The usual story runs like this. A co-investing fund's partner submits an introduction from their partner account, naming the entity on the fund's own paperwork: a holding company, the vehicle both funds invested through, or the group's best-known brand. You, the ecosystem lead at the other fund, notice when the operating company's CEO mentions an email from SourceX that used the wrong name. Nothing is broken yet. It becomes a problem only if it is fixed in the wrong way.
Five ways an introduction lands on the wrong entity
The entity matters because almost everything SourceX checks belongs to one specific company: the full-time headcount at its peak, the records its employees created, the rights it holds and the CEO who can say yes. SourceX's screening guidance defines the operating entity as the legal entity whose employees created the records and that holds them today, and says it is not the fund, a holding vehicle or a brand name.
| Mistake | Illustrative example | What it breaks | Who fixes it |
|---|---|---|---|
| A holding company or investment vehicle named instead of the operating company | A holding company with four staff above a 210-person field services business | Fit is measured on an entity with almost no staff or records | The submitter, once the operating company's CEO confirms |
| A brand or trade name with no legal entity behind it | The name on the trucks rather than on the contracts | The record names nobody SourceX can review | The submitter |
| A sister company in the same group | The group's software unit instead of its services unit | Records and the internal sponsor differ; the group still counts as one referred company | The submitter, with the group CEO |
| A different company with a similar name or domain | Two logistics firms with near-identical names in different states | SourceX may contact, or find a duplicate at, the wrong company | The submitter, the same day |
| A pre-acquisition name for a company that now sits inside an acquirer | The founder's company, bought last year | The acquirer's CEO now decides for it | The submitter, after the acquirer's CEO confirms |
The last row is the one most often mistaken for a typo. Once a company is acquired, the acquirer's CEO decides for it, so correcting the name also means asking a different person for permission.
Map the chain and the permission before anyone writes
Four parties are involved, and only one of them can fix the record.
| Party | Role | What it may do |
|---|---|---|
| The co-investor's partner who submitted | Partner of record for this introduction | Send the correction from the same partner account, with the CEO's confirmation |
| You, at the other fund | Noticed the error; not a party to the record | Tell the submitter privately, and help find the right entity name if asked |
| The CEO of the intended company | Decides whether the company talks to SourceX at all | Confirm the right entity and say whether they want the conversation |
| SourceX | Holds the dated records and decides credit | Review the corrected record, including any duplicate question |
One check comes before any correction: did the intended company's CEO actually agree to the introduction? If the co-investor named the holding company because nobody had asked the operating company's CEO, this is not a naming problem. It is an introduction the decision-maker never knew about, which SourceX's screening guidance treats as usually not a fit. Stop, and let the CEO decide whether there should be any introduction at all.
To settle which entity is meant, start with the CEO, who can name the company that employs the staff and holds the records; the guide to finding a company's legal entity name covers registry lookups, and which entity owns the data in a group covers holding structures. Where the entities involved have a Legal Entity Identifier, GLEIF's Level 2 data shows each one's direct and ultimate accounting consolidating parents, and the whole LEI data pool can be searched free of charge without registering. Many mid-size private companies have no LEI, and GLEIF records reporting exceptions where no parent is given, so treat it as a cross-check, never the answer.
The entity correction handoff template
Ten fields on one page, filled before the correction is sent. The examples are Illustrative, and the placeholders HoldCo and OpCo stand for a holding company and the operating company beneath it.
| # | Field | Filled by | Example (Illustrative) |
|---|---|---|---|
| 1 | The original record, copied unchanged: entity named, web domain, date sent, submitter | The submitter, from their own submission | HoldCo, HoldCo's domain, day 1, Fund B's partner |
| 2 | The intended entity: exact legal name, place of formation, web domain | The intended company's CEO | OpCo, its state of incorporation, OpCo's domain |
| 3 | How the two relate: parent and subsidiary, sister companies, successor after a deal, or unrelated | The CEO, cross-checked against a registry or LEI data where available | OpCo is wholly owned by HoldCo |
| 4 | Who confirmed the difference, and when | The CEO, by email | OpCo's CEO, day 6 |
| 5 | That the CEO knows about the introduction and wants the conversation | The CEO's own words | "Yes, I am happy to talk to SourceX" |
| 6 | Fit facts for the intended entity: full-time headcount at peak with contractors left out, the year its own records start, any client-owned material | The CEO | Peak of 210 full-time in 2025; service records since 2011 |
| 7 | Earlier contact: whether the intended entity, or anyone in its group, has applied to, held an account with or written to SourceX | The CEO | None, to the CEO's knowledge |
| 8 | Who sends the correction: the original submitter, from the same partner account | The submitter | Fund B's partner, day 8 |
| 9 | What stays the same: one contact for the founder, and no files, samples or logins changing hands | Both funds | The founder deals with Fund B's partner only |
| 10 | What is left to SourceX: the date it attaches to the corrected record, and any duplicate question in the group | Nobody outside SourceX | Recorded as open |
Method note. The fields mirror what SourceX's partner agreement sample says every introduction record must identify (the company, its domain, the partner, the opportunity, the method and timestamps), with fields added for the relationship between the two entities, the CEO's consent and earlier contact. Sources were SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned Channel Partner Agreement sample, SourceX's screening guidance and GLEIF's Level 2 page, all read on 2026-10-27. Nobody has published how often entity errors happen in investor introductions or how SourceX has resolved them, and the template assumes no outcome.
Why the original record stays visible
Correct by adding, never by overwriting. SourceX decides attribution from dated records, and its partner agreement says a dispute must not erase original evidence, so the most useful correction sits beside the first record with its own date and an explanation that a reviewer can follow. A record that was quietly changed reads as less reliable than one that admits a mistake.
Three things stay outside anyone's control at your end:
- The date. The published terms do not say whether a corrected entity inherits the original introduction's date. Credit still needs the company's verified application within 90 days of a recorded introduction, so behave as though the correction buys no extra time.
- The group's history. If the holding company named by mistake has its own past with SourceX, nobody outside SourceX can say whether that past follows the subsidiary. The terms address groups only for the once-per-company floor, and SourceX rules on the rest when it examines the record for duplicates.
- Earlier contact at the intended company. Any earlier application, account, lead or email exchange between OpCo and SourceX makes it a duplicate that is not credited, however tidy the correction.
The once-per-company floor is the one settled group rule. A parent and every subsidiary count as one referred company, so HoldCo and OpCo share a single first qualifying transaction with its USD 50,000 floor, whatever the record ends up saying; later transactions in the group within the Repeat Window pay 15%.
Keep one accountable introducer
The co-investor who submitted stays the owner of the introduction, and the correction goes out from the same partner account. Taking it over feels efficient and does the most damage: a second record from your fund points at the same group, the terms credit only one partner per company, and SourceX's partner agreement requires competing claims to be recorded and resolved in good faith on dated evidence. The founder, meanwhile, hears from two funds about one idea. How SourceX weighs two records for one company is covered in when two partners refer the same company, and ways to avoid the collision upstream in preventing duplicate claims.
If the submitter will not correct the record, or has left their fund, tell the CEO plainly what happened. The CEO can choose how to proceed, including applying directly, and SourceX decides what any of it means for credit.
Status and compensation, settled before the next message
Agree two things with the submitter when you raise the error.
Status. You will hear little, and that is by design. Partners receive generic stages or reference codes about their own referrals, and the terms keep every partner out of other partners' records. Ask the submitter to pass on only what OpCo's CEO is happy for you to know, typically that the correction was sent and, later, that the matter has closed.
Compensation. Spotting the error earns your fund nothing from SourceX, and the correction should not become the occasion for an informal share. Illustrative: if SourceX later paid OpCo USD 100,000 under its signed agreement on a first qualifying transaction and the original submitter was credited, the reward would be USD 55,000 (the greater of USD 50,000 plus 5% and 15%), paid by SourceX to that partner, with nothing for the fund that noticed the wrong name.
A correction worked through (Illustrative)
Illustrative. Two funds co-own HoldCo, which owns OpCo, a 210-person field services company with full-time headcount that peaked in 2025. On day 1, Fund B's partner submits an introduction naming HoldCo, because that is the name on the funds' share records. On day 3, OpCo's CEO mentions to Fund A's platform lead that an email referred to HoldCo, which has four employees and holds no operating records. Fund A's lead calls Fund B's partner the same afternoon and sends the blank template. On day 6, OpCo's CEO confirms by email that OpCo is the intended company, that OpCo wants the conversation and that, to the CEO's knowledge, nobody in the group has dealt with SourceX. On day 8, Fund B's partner sends the correction from the same partner account, with fields 1 to 10 attached. Fund A sends nothing to SourceX, and OpCo submits its own application the following week.
Where the correction can still fail
- The CEO never agreed. If field 5 cannot be filled honestly, the correction is the wrong tool; the introduction should not exist yet.
- Duplicates. Earlier contact anywhere SourceX treats as relevant can leave the corrected record uncredited, and the published terms do not settle every group case.
- The clock. A correction made late in the 90-day window leaves little time for a verified application.
- Structure. Records sometimes sit in a shared-services entity or were moved in an acquisition; acquisition-led growth and the referral entity shows how deals relocate them.
- Demand. A correct record is still only the start: SourceX assesses relevance to its current data needs in review, and a well-identified company can be declined.
A measurable next step. For one year, log every co-investor introduction your platform team hears about and mark the ones that named the wrong entity, with the mistake type from the first table. If holding-company errors dominate, add a one-line entity check to your fund's co-investment notes; the venture platform overview shows where introductions fit in a platform team's work.
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 own fund introduces anyone, open a partner account, confirm which legal entity employs the staff against the screening criteria and read how dated records decide credit in the program terms; more coordination guides sit in the guides section.
A wrong entity on a referral is a coordination problem between funds; whether SourceX is a sound investment is a separate question, and anyone weighing it can request investor materials through the SourceX investor overview.
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.