# Mixed eligible and ineligible groups, mapped | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-handle-a-mixed-eligible-and-ineligible-corporate-group
Last updated: 2026-11-04

Handle a mixed group by drawing one line, not by forming one opinion of the group. Each operating entity goes inside if it passes the published facts (50+ full-time employees at peak, several years of its own records, rights to license them, an eligible location), outside if it fails one, and open if a fact is unknown. Run the same line through shared systems and record libraries, introduce only the inside entity by name, and tell the group in writing what is left out.

The partition protects two things at once. It keeps a weak entity from riding into a review on the strength of a strong sibling, and it keeps a strong entity from being held back because the group also owns a consumer app or a small spinout. Funding status settles neither. The entity a fund invested in can be the one that falls outside the line, while an unfunded operating company two boxes away on the chart passes every test.

## Which entity operates, and who controls it on the date you check?

The entity on the map is the legal company whose employees created the records and whose systems hold them; its controller is whoever can direct it on the day you write the date down. A pure holding company, a shared-services company or a brand name is rarely the entity to introduce.

Start with a dated, public view of the chart where one exists. The LEI system's Level 2 data records each registered entity's direct parent, defined as the lowest-level company that consolidates it in its financial statements, and its ultimate parent at the top of the chain. The child entity reports that relationship, and a reporting exception is filed instead when it has no parent, when the parent has no LEI, or when it opts out for exceptional reasons. Treat it as a starting point with two limits: consolidation describes the accounts, not who can decide a licensing discussion, and an exception or missing record tells you nothing about the group's real shape. Confirm the rest with the group's own dated entity chart.

Two names go on every row before anything else: the entity's own CEO, who authorizes a licensing discussion for that entity and signs for it, and the person in your network who can ask that CEO and be heard. A group CEO, CFO or board can sponsor the introduction or hold internal consent rights, but the authorizer is the CEO of the entity that would license. The [subsidiary approval path](/guides/why-a-subsidiary-introduction-needs-a-different-approval-path) walks through groups where those roles sit far apart.

## The entity-level referral partition map

Illustrative. A fictional family-owned property services group, generic entities, invented facts and dates. The fund holds a minority stake in one entity: the analytics spinout. Every cell is metadata the group's finance or operations lead can answer without opening a record.

| Item | Layer | Side of the line | Published test that places it | Wording in the introduction note |
|---|---|---|---|---|
| U.S. residential property-management operator | Operating entity | Inside | 310 full-time employees at peak; work orders, vendor dispatch and inspection reports since 2009 in its own system; U.S. | Named as the only company introduced |
| Group ERP, operator's company code | Shared system | Inside, by company code | Records the operator's own staff created | "Its records in the group ERP, identified by its company code" |
| Group ERP, Mexican subsidiary's company code | Shared system | Outside | Same tenant, but those records are about 60% English | Covered by "no other group entity is part of this introduction" |
| Group procedures library | Shared records | Open | Written by the parent's operations team for every subsidiary; which entity holds the rights is unclear | "One question about group-written procedures goes to SourceX first" |
| Mexican facilities-maintenance subsidiary | Operating entity | Outside today | 140 full-time employees and records since 2015, but about 60% English | Not named |
| Resident app company | Operating entity | Outside | Its records are residents' personal data | Not named |
| Analytics spinout, the fund's portfolio company | Operating entity | Outside | 34 full-time employees at peak, founded 2023, product data held in customers' accounts | Not named |
| Parent holding company | Owner | Not a licensor | Holds shares; 9 people in group finance | Any group consent is handled inside the group |

**The rejected case.** The analytics spinout is the row most likely to be pushed through, because it is the one the fund knows best. It fails three ways today: below 50 full-time employees at peak, too short a history, and records that belong to its customers rather than to it. A warm board seat cures none of these. It stays outside the line with a dated note of what would change the answer: full-time headcount passing 50 and several years of records the spinout itself controls.

**Method note.** Each row applies the published criteria (who qualifies and the program terms, Version 2026-11-04, both checked 2026-11-04) and the owner's rule that a parent and its subsidiaries count as one referred company for the reward floor. The map records structure and screening facts only. It does not measure demand for any entity's records, record quality, contract restrictions or payout, all of which SourceX assesses in its own review, and no acceptance rates for partitioned groups have been published.

## Where the line runs through a shared system

A group can run one system while each company in it keeps its own records, so the partition has to continue below the entity row. Four rules keep it clean:

1. **The line follows whoever created the records, not where they are stored.** A group ERP, CRM or document store can sit inside and outside at once.
2. **Describe the inside portion by an entity identifier** the group already uses: company code, business unit, tenant, mailbox domain or project prefix.
3. **Prove the split with metadata, never samples.** System name, entity identifier, span of years and a rough record count are enough at this stage. Partners never ask for exports, files or logins, and never handle a record.
4. **If a store cannot be split by identifier,** such as one shared inbox serving three companies, mark it open and let SourceX's review decide what, if anything, can be separated.

Group-written material deserves its own row. Procedures a parent's central team wrote for every subsidiary may belong to the parent, to whichever entity paid for them or to nobody clearly, and only a rights review settles that. Listing them as an open question costs nothing; folding them into the inside entity's description invites a correction later.

## Program fit, English share and record history on each side

Run three checks per entity, not per group, because each can differ inside one family of companies.

- **Program fit.** SourceX applies the criteria of the specific program, not one universal minimum, so a subsidiary that falls outside one program today may fit another program later. Date every outside row, so a later recheck has something to compare against.
- **English share.** 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. In a cross-border group the test runs entity by entity: the Mexican subsidiary above fails it today even though its U.S. sibling has no language question at all.
- **Record history.** Count years of records the entity holds now. An entity bought into the group last year may have left its older archive with the seller, which is the subject of [whether an acquired company can license its historical data](/questions/can-an-acquired-company-license-its-historical-data). Headcount is counted on the entity's own full-time employees at peak, contractors excluded; where staff sit in a shared-services company, give both numbers rather than adding them together.

## Saying no to part of a group without saying yes to the rest

The note to the group carries the partition in plain words. Name the inside entity, state that no other group entity is part of the introduction, and list the open question. Then choose words for each row that cannot be heard as a verdict SourceX never gave.

| Row type | Say | Never say |
|---|---|---|
| Inside | "We think the operator matches the published criteria; SourceX makes its own decision in review" | "The group qualifies" |
| Open | "One question about group-written procedures goes to SourceX before anyone counts them in" | "Send everything and let SourceX sort it out" |
| Outside on English share | "The subsidiary does not meet the published English rule today; we have noted the date" | "SourceX turned it down" |
| Outside on size and history | "The spinout is below the size and history tests today, which says nothing about the business" | "Your turn will come" |
| Outside on consumer data | "Personal consumer data is usually not a fit, so the app company is not included" | "Anonymize it and we will add it" |

SourceX has reviewed none of the outside rows, so no sentence should imply it has. One question the map cannot settle is credit across the group: whether earlier contact between SourceX and the parent, or another partner's introduction of a sister company, affects credit for the entity you introduce. The terms do not address parents, subsidiaries or affiliates on that point, so SourceX decides it in duplicate review; note any group-level contact you know of and let the review weigh it. Whoever submits the introduction must first sign the SourceX Channel Partner Agreement. For the narrower question of whether several entities of one group can each be introduced, see [introducing multiple companies from the same corporate group](/questions/can-i-introduce-several-companies-from-the-same-corporate-group); for screening a holding company's operating businesses before anything is promoted, see the [holding company program page](/for/holding-company-referral-program).

## One floor for the whole group

For the reward, the parent and every subsidiary are treated as one referred company: the USD 50,000 floor applies once, to the group's first qualifying transaction, however many entities license and however many agreements they sign, and no cap applies after it. Partitioning therefore changes what is introduced, never the formula applied to it.

Illustrative arithmetic, not a forecast or a quote. If SourceX paid the operator $160,000 for a first license, the reward would be the greater of USD 50,000 plus 5% ($58,000) and 15% ($24,000), so $58,000. If a second license for the same operator were first agreed within 12 months of that first Closing and paid $300,000, it would pay 15%, or $45,000, with no cap on the total. Should the Mexican subsidiary fit a different program and license inside that same 12-month Repeat Window, its transaction would also pay 15% of its Actual Supplier Payout, but the USD 50,000 floor would not apply again, because the group has already used it. The [subsidiary reward guide](/guides/subsidiary-referral-reward-cap) works through a group's payments in order.

## Where the partition map can be wrong

- **Ownership records lag.** Level 2 data depends on the child entity reporting its parents, and exceptions stand in for missing relationships; a group that sold or merged an entity recently may not show it yet.
- **Programs change.** Criteria differ by program in size, history, geography, language and data category, so an outside row can move inside later, and an inside row can stop matching current needs.
- **Rights sit below metadata.** Customer contracts, employee privacy and third-party terms can limit an inside entity's records, and only SourceX's rights review settles them.
- **Shared stores resist splitting.** Some records cannot be separated by any identifier; those stay open, and some may never be licensable.
- **Demand is untested.** Relevance to current data needs is checked in review, and a clean partition does not establish it.

## 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 the partition map leaves one entity clearly inside the line and its CEO wants the conversation, [register for a partner link](/register), check that entity against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the introduction note goes out; more group cases sit in [guides](/guides).

Partitioning a group for an introduction is referral work, and judging whether SourceX itself merits an investment is a separate decision; investor materials are available on request through the [SourceX investor overview](https://sourcex.si/investors).

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.gleif.org/en/lei-data/access-and-use-lei-data/level-2-data-who-owns-whom
- https://sourcex.si/investors
