# Mixed-language company summary: a template | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-handle-a-mixed-language-company-summary
Last updated: 2026-11-04

Write your summary of the company in one language, the language of the person who will read it, and tag every line with the language of the source behind it: the company's website, a public register entry, the CEO's own words on a call. Keep names, job titles and figures exactly as the company gives them. The languages you happened to read never stand in for the language of the company's records. That line belongs to the company, and you never open a record to fill it.

This page covers your own text. Translating your message for a CEO, the brief that travels with a submission and the company's own note on record language have their own guides: [when translation is needed](/guides/when-translation-is-needed-before-a-company-can-evaluate-the-opportunity), [the brief for an English-operating international company](/guides/the-introduction-brief-for-an-english-operating-international-company) and [stating data language without guessing from headquarters](/guides/how-to-state-data-language-without-guessing-from-headquarters).

## Three languages sit behind every cross-border summary

A summary built from mixed sources involves three different languages, and most errors come from letting one of them stand in for another.

| Language | What it describes | Who knows it | Where it goes in your summary |
|---|---|---|---|
| Source language | Whatever you read or heard: website, register extract, press release, the CEO on a call | You, from your notes | A tag on every line |
| Summary language | The single language your summary is written in | You choose it, for its reader | The header, stated once |
| Record language | The language of the records the company might license | Only the company | One line, in the company's words, or "not yet stated" |

Only the third matters to SourceX's location rule, and it is the one you see least. Who-qualifies states that rule in one sentence: "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." How a company works out its English share is explained in the [English-language eligibility guide](/guides/english-language-data-referral-eligibility); this page adds no other country or language rule.

Keep three location facts apart too: where you are based, where each operating entity is, and which entity holds the records. Your own location is a separate question, set out in [partner location versus supplier eligibility](/guides/the-difference-between-partner-location-and-supplier-eligibility).

## How mixed sources bend a summary

Four distortions creep in when one summary is written from sources in several languages.

- **A rendered claim becomes your claim.** A sentence carried over from the company's marketing page, without a tag, reads as something you verified.
- **A name or title shifts.** A translated legal name can point at a different entity, and calling a local job title "CEO" because it sounds senior can name the wrong person. The CEO decides under SourceX's program, so keep the company's own title and note who confirmed that this person holds the CEO role.
- **A figure changes size.** In 2003 the General Conference on Weights and Measures resolved that the decimal marker may be either the point or the comma on the line (paraphrase). A headcount printed "1.200" in one source and "1,200" in another is the same staff, but a reader used to the other convention can take the first as 1.2. Write counts without separators, such as 1200, and keep the source's form in the tag.
- **Fluent prose implies English records.** A polished English summary of a half-English website invites the reader to assume English records. No website tells you that.

## The language distribution summary template

Three parts: a header naming your summary language and listing every source by language, the tagged summary lines, and a closing count of how much of the summary rests on each source language. The count describes your sources, never the company's records.

**Part A, the header.**

| Field | What you write |
|---|---|
| Summary language | One language, named once |
| Written by | Your name, firm and country, and the date of this version |
| Sources | One row per source: what it is, its language tag, who produced it, the date you saw it |
| Rendering | Who rendered material from other languages, and whether the CEO has read this version |

Use short standard language tags such as "es", "de" or "pt" rather than labels of your own. W3C's guidance on choosing a language tag advises keeping the tag as short as possible and adding a region or script part only when it distinguishes something that matters in context (paraphrase).

**Part B, the summary lines.**

| Line | What it holds | Tag | Rule |
|---|---|---|---|
| 1. Company | Legal entity name exactly as registered, a Latin-script form beside it if the name uses another script, and any trading name | Source tag | Never translate an entity name |
| 2. Where it operates | The country of each operating entity | Source tag | One country per entity |
| 3. What it does | Two sentences in your own words | "Partner wording" | No pasted marketing copy |
| 4. Size | Full-time headcount at peak as the company states it, contractors left out | "Company statement" with date | Number written without separators |
| 5. Decider | The CEO's name as the CEO writes it, the company's own title for the role, and who confirmed it | Source tag | Nobody but the CEO is listed as deciding |
| 6. Why it may fit | Your reason, in your words | "Partner view" | Never "qualifies" or "eligible" |
| 7. Record language | The company's words with a date, or "not yet stated" | "Company statement" | Never inferred from lines 1 to 6 |
| 8. Open questions | What only the company or SourceX can answer | None | Questions, not guesses |

For lines 1 and 5, W3C's article on personal names suggests that when an application needs a name in both its native script and a Latin-script form, the two are kept as separate items (paraphrase): the person's or the register's form first, the Latin form beside it, never in its place. When you quote the CEO from a call held in another language, give the original words and your rendering, marked as yours, and never polish a quote into English that says more than the CEO said.

**Part C, the closing count.** Give each line one primary source tag, then count. The foot line, shown in the example below, reveals at a glance how much you rendered from a language the company may not have checked. If most lines rest on your own renderings and the CEO has not read the result, the summary is not ready to send.

## A Mexican logistics company, summarized from Spanish and English (Illustrative)

Illustrative: a generic company, invented facts, no outcome implied.

A platform manager at a London fund knows the CEO of a cross-border trucking and customs firm in northern Mexico through a co-investor. Three sources feed the summary: the company's website, with long Spanish pages and shorter English ones; its public commercial register entry, in Spanish; and a thirty-minute call with the CEO in Spanish, a colleague interpreting.

| Line | Entry | Primary tag |
|---|---|---|
| 1. Company | Legal name as the register prints it, legal form included; the trading name from the English pages beside it | es, register, 2026-10-20 |
| 2. Where it operates | Operating entity in Mexico; a sales office in Texas listed on the English pages, entity not confirmed | en, website, 2026-10-20 |
| 3. What it does | Trucking and customs brokerage for manufacturers that ship across the border | Partner wording |
| 4. Size | Website: "más de 300 colaboradores", rendered by the partner as "more than 300 staff"; full-time headcount at peak not yet stated | es, website; company statement pending |
| 5. Decider | The CEO, under the company's own title for the role, confirmed on the call as the person who holds the CEO role | es, call, 2026-10-21 |
| 6. Why it may fit | Twelve years of shipment exception and customs-hold notes, as the CEO described them | es, call; partner view |
| 7. Record language | Not yet stated. The CEO remarked that correspondence with U.S. customers is in English; a remark, not a count | Company statement pending |
| 8. Open questions | Whether the Texas office is a separate entity; how the English condition reads for the records the company would offer; peak full-time headcount | For the company and SourceX |

Closing count: primary source es: 4 lines; en: 1; partner wording: 1; company statements: 0 of 2; open: 1.

What the count showed: four of eight lines rest on Spanish material a colleague rendered, and nobody at the company has read the English. The website's word for staff does not say whether contractors are included, so line 4 waits for the company, and the CEO's remark about U.S. customers never becomes a percentage. The CEO reads the summary before it goes anywhere, in English with each Spanish source beside its line or in a Spanish version checked as the translation guide describes. Mexico sits in the Latin America part of the published sentence, so the English condition is the one that matters; how it applies to these records is for the company to state and SourceX to decide.

## Who settles what the summary leaves open

| Open question | Who answers it | What your summary says meanwhile |
|---|---|---|
| Record language and English share | The company, counted its own way; SourceX on how its condition applies | "Not yet stated" |
| Whether each entity's location is covered | SourceX, against the published sentence | The entity and its country, nothing more |
| The exact legal name and which entity holds the records | The CEO; the public register for the name | The register's form, tagged |
| Contract limits on reusing the records | The company's counsel | Nothing |
| Tax or payment questions about any reward | Your own adviser | Nothing; see [routing tax questions out of the intro call](/guides/how-to-route-international-tax-questions-out-of-the-intro-call) |

You give no legal or tax view on any of these; the summary records who was asked and when.

## What the finished summary leads to

A tagged summary ends in one of three places.

- **It travels with an introduction.** The CEO has read it, calls it fair and wants the conversation; you have signed the SourceX Channel Partner Agreement; the company applies itself. The summary joins your dated record. One partner is credited per company, from dated evidence, and a link click alone settles nothing; a company SourceX already knew is not credited, and if several people at your fund know the CEO, SourceX settles the overlap in duplicate review.
- **It records a no-fit.** The company's own statement fails a published fact, for example a CEO who says full-time headcount never reached 50. Write the fact, the date and what would change it; SourceX notes that a company missing one program's bar may suit another later.
- **It waits.** Lines 4 and 7 stay open, and the questions go back through whoever holds the CEO relationship.

The summary never touches the company's payout: the terms say the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation" (section 4). By default it is the greater of $50,000 plus 5% and 15% of what SourceX actually pays, with no cap for the company and its whole group.

## When tagging every line misleads

- **A tag is not evidence.** It records where you read something, not that the thing is true or current.
- **The CEO's reading is not acceptance.** A CEO who confirms your summary is fair has approved your wording, not a licensing outcome; SourceX's review decides fit.
- **Rendering quality varies.** A machine rendering pasted into line 3 carries errors no tag reveals; have someone fluent check meaning.
- **Programs move.** SourceX says its requirements follow its current data needs, so a summary is valid on the date in its header.
- **One-language companies need no tags.** The header alone is enough.

**Methods note.** The template applies SourceX's who-qualifies page and program terms as read on 2026-10-27, W3C guidance on language tags and personal names, and the 2003 CGPM resolution on number notation. It measures nothing about the company's records, demand or rights; the closing count describes your sources only. The worked example is invented.

## 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 your summary is tagged, the CEO has read it and wants the conversation, [register as a partner](/register), set the summary beside [who qualifies](/who-qualifies) one last time and confirm the [program terms](/terms) you are submitting under.

Writing a careful company summary is referral work; judging SourceX as a possible investment is a different exercise, and readers doing that can ask for materials 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://refer.sourcex.si/terms
- https://www.w3.org/International/questions/qa-choosing-language-tags
- https://www.w3.org/International/questions/qa-personal-names
- https://www.bipm.org/en/committees/cg/cgpm/22-2003/resolution-10
- https://sourcex.si/investors
