# Multinational referral language coverage | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-screen-language-coverage-across-a-multinational-group
Last updated: 2026-11-05

Screen language one entity at a time, never for the group as a whole, and from the company's answers rather than its records. For each entity that holds records, write down its country, the languages its records are kept in as the company reports them, and which half of SourceX's published rule applies. U.S., Canadian and EU companies face no English share in that rule; in the other markets it names, at least 70% of the data must be in English; any other country is a question for SourceX. The CEO of the company that holds the records decides.

This guide is for platform and portfolio teams at funds whose companies run subsidiaries, branches and service centers in several countries.

## Location picks the rule; the records supply the answer

In a group, location and language come apart twice over: each entity has its own country, and each entity's records have their own languages. Where the group is run from answers neither. The first fact decides which half of SourceX's rule applies; the second, reported by the company, decides whether a stated condition looks met; and whether anything is licensable at all waits for SourceX's rights review with the company's counsel.

The rule itself, as SourceX publishes it: 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.

For the first half of that sentence, SourceX's FAQ answers the language question directly: "Yes, for companies in the U.S., Canada and the EU: multilingual and non-English data can be valuable, so tell us the languages involved." So a German or French subsidiary is not screened out by language, but its languages still have to be stated. An EU address tells you little on its own: the EU's official site lists 24 official languages, English among them (our paraphrase of a search excerpt). SourceX's screening page adds that its current data needs differ in company size, operating history, geography, language and data category.

For the second half, the share is a property of the data. SourceX's own article on language audits says it confirms the share "on the dataset actually offered rather than on the company's country or working language". A group-wide policy that "we work in English" is therefore not an answer either.

Where the partner sits plays no part in this screen. The terms ask partners for an approved account, a signed SourceX Channel Partner Agreement before any introduction and, in section 5, the payment and tax details a payment needs, adding that "payment must also be lawful." We found no list of partner countries in them; how a reward is taxed where you live is for your own adviser.

## The entity-and-language matrix

One row per entity that holds records the company might describe. Fill it from public facts and the relationship holder's answers; the language column comes only from the company.

Illustrative. A generic 1,100-person software and services group; figures are what its teams might report, not measurements.

| Entity and the records it holds | Country | Part of the published rule | Languages, as the company reports them | What you can say now | Who answers next |
|---|---|---|---|---|---|
| 1. U.S. parent: product, sales and finance records | U.S. | First half; no English share set | 98% English, company estimate | Location is covered; size, history, rights and the CEO decide the rest | The parent's CEO |
| 2. Irish subsidiary: support tickets for European customers | Ireland, EU | First half | 55% English, 30% German, 15% French, company estimate | Covered; name all three languages to SourceX | The subsidiary's CEO |
| 3. Indian subsidiary: implementation and support records | India | Second half; at least 70% English | 96% English, from the company's own count across years and teams | The condition looks met on the company's count; SourceX confirms on what is offered | The subsidiary's CEO |
| 4. Mexican subsidiary: Spanish-language customer service | Mexico, Latin America | Second half; at least 70% English | 20% English, 80% Spanish, company estimate | The condition is not met on the company's own count | The subsidiary's CEO, who decides what the company describes |
| 5. Japan branch of the parent: sales notes made in Tokyo | Parent in the U.S.; records made in Japan | Not settled | Japanese and English, mix not reported | Nothing about fit; ask SourceX first | SourceX |

Row 5 is the explicit unknown worth keeping. The published sentence speaks of where a company is. It says nothing about records a U.S. company's branch created in a country the sentence does not name, so the honest entry is a question, not a guess in either direction.

## Reading the matrix without blending the rows

- **Rows do not average.** SourceX's sentence does not say whether figures from different entities may be combined. Rows 3 and 4 do not merge into one middling figure; they are two separate answers.
- **Say only the "say now" column.** "The group qualifies" appears nowhere in the matrix, and never should in an email.
- **Unknown is not a fail.** It is a question for the company or for SourceX, with a date beside it.
- **The decider follows the records.** The CEO of the company that holds the records decides whether it talks to SourceX: the subsidiary's CEO for rows 2 to 4, the parent's for rows 1 and 5. If the group was acquired, the acquirer's CEO decides; before closing, the target's CEO does.
- **One cap, unsettled credit.** However many entities license, a company and its corporate group share one reward cap. Whether an introduction of one entity affects credit for a sister entity is not settled by any published rule; SourceX decides it from dated records in duplicate review.

## Who fills each cell, and who never touches the records

The partner fills the country and rule columns from public facts and conversation. The company's own team counts and reports the languages; the inventory arithmetic is set out in the [English-language eligibility guide](/guides/english-language-data-referral-eligibility), and the evidence note that records how a figure was reached is in [stating data language without guessing from headquarters](/guides/how-to-state-data-language-without-guessing-from-headquarters). SourceX measures the dataset actually offered.

Nobody in a fund samples, reads, exports or reviews a portfolio company's records to fill this matrix, and nobody collects records for SourceX. If a figure is missing, the cell says "not reported" until the company supplies it. For sorting a single entity into its location group before any language question, use [checking language coverage before suggesting global fit](/guides/check-language-coverage-before-suggesting-global-fit).

## Questions the matrix hands on

| Question | Who answers it |
|---|---|
| Can an entity in a country the published sentence does not name take part? | SourceX |
| Are the records the company's to license? | SourceX's rights review, with the company's counsel |
| Do privacy or data-transfer rules affect where records can go? | The company's counsel; SourceX's FAQ asks companies to say where their data comes from so it can flag extra review |
| How is a partner's reward taxed in the partner's country? | The partner's own tax adviser |
| Which entity applies, and whose introduction is credited? | SourceX, from its dated records |

This page gives no legal or tax advice. Its job is to keep each question attached to the person who owns it.

## What each entity row turns into

Every row ends in one of three entries, each dated:

- **Introduce.** The relationship holder asks the CEO of the records-holding company, the CEO wants the conversation, and the partner who submits has signed the Channel Partner Agreement. The company then applies itself. Credit, if any, goes to the first valid introduction of a company new to SourceX, decided from dated records rather than a link click, and only one partner is credited per company.
- **Hold.** A named question is waiting on SourceX or on the company's own count.
- **No fit.** The failing fact, the date and what would change it, such as row 4 on the company's own count. A no-fit row is never shared outside the team.

None of this replaces the size and history checks: a full-time workforce that has topped 50 at some point, with contractors left out of the count, and years of records the company produced on its own. The [company fit checker](/tools/company-fit-checker) gives a preliminary, non-binding screen, and [global partners referring companies](/guides/global-partners-referring-us-businesses) keeps partner and company location apart.

**Method note.** The matrix applies SourceX's geography sentence and screening page, its FAQ and language-audit article, and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-27, with the EU's list of official languages as context. It records what a company reports and which published condition applies; it does not measure language, record quality, rights or demand. SourceX has published no figures on how multinational groups fare in review.

## What could make this screen wrong

- **Programs move.** SourceX says its data needs differ by language among other things, so a row correct today can change. Date every row and screen again when the criteria change.
- **The threshold has no published unit.** The sentence gives 90% but not whether records, words or messages are counted; the company should state its unit, and SourceX's measure is the one that counts.
- **Group treatment is unpublished.** How SourceX reads a group spanning both halves of the sentence, or a branch abroad, is decided in its review.
- **Company counts can be wrong.** A self-reported share is an estimate until SourceX measures the dataset offered.
- **Regions are not lists.** Latin America is named as a region; confirm a borderline country with SourceX.
- **Language is not demand.** A covered location and a clear language picture say nothing about whether a current program wants the records.

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

Once a row reads "introduce" and that entity's CEO wants the conversation, [create your partner account](/register), recheck the entity against [SourceX's screening page](/who-qualifies) and keep the [referral terms](/terms) open while you draft the introduction.

Screening a portfolio group for a referral is separate from deciding whether SourceX itself is a sound investment; for that second question, investor materials can be requested 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/who-qualifies
- https://sourcex.si/faq
- https://sourcex.si/insights/dataset-language-coverage-validation
- https://european-union.europa.eu/principles-countries-history/languages_en
- https://refer.sourcex.si/terms
- https://sourcex.si/investors