# Fund referral terms versioning register | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-archive-the-terms-that-govern-a-fund-s-referrals
Last updated: 2026-11-05

A fund's referrals answer to two rulebooks at once. One is SourceX's: the signed Channel Partner Agreement, its Schedule A, any signed addendum and the program terms version published that day. The other is the fund's own: its participation policy, the list of people allowed to act under it, the disclosure wording it approved and counsel's sign-off. Archive both in one register, label every document with a version, pin each introduction to each version in force that day and to the person who acted, and give the register an owner by role so it outlives whoever started it.

The single partner's version of this job, a sheet that pins referral events to SourceX's terms versions, is set out in [why a partner should save the applicable terms version](/guides/why-a-partner-should-save-the-applicable-terms-version), along with the changelog and the agreement's no-snapshot rule. This page adds what only an institution has: internal rules that change on their own schedule, several people acting under one agreement, and a duty to answer later, after those people have moved on.

## Two rulebooks govern every fund introduction

SourceX's layer is public and dated. Section 11 of the program terms, version 2026-10-22.2, since replaced by version 2026-11-04, lists changes from five versions in October 2026 and sets the rule that matters most for an archive: "Signed agreements are never silently replaced; rates and exceptions in signed agreements are preserved." Section 8 divides the ground: Schedule A's rate, calculation base and cap prevail over the terms, the signed agreement governs confidentiality and contact protection, and the terms govern attribution and rewards. Agreements signed under the earlier title remain in force as signed, under section 9.

The fund's layer is private and changes just as often. A typical one holds:

- **The participation policy.** Whether the fund takes part, through which route and for what purpose.
- **The authorized-person list.** Who may introduce companies under the fund's agreement, from when to when.
- **The approved disclosure wording.** What founders are told about who could be paid.
- **Counsel's sign-off.** Fund counsel's written view, given against the fund's own documents, whose contents never belong in this register.
- **Review minutes.** Each annual decision to continue, change route or wind down.

When a founder, an LP or counsel later asks whether an introduction followed the fund's rules, SourceX's documents cannot answer. They were never meant to. The register exists to put both layers side by side for one introduction on one day.

## Whose register: firm, employee or unpaid

The sample Channel Partner Agreement names the Partner as "[an individual, or entity type and jurisdiction]", so the route decides who holds each half.

| Route | Who signed with SourceX | SourceX half of the record | Fund half of the record |
|---|---|---|---|
| Firm-level | The fund or its management company | The fund | The fund |
| Individual, with fund approval | A partner or employee personally | That person | The fund: approval, policy version, disclosure wording |
| Unpaid | Nobody; companies apply to SourceX themselves | None exists | The fund: the unpaid decision and the wording founders received |

How a firm's account relates to its people's personal accounts is not settled by SourceX's published terms; SourceX decides it. [The entity-recipient matrix](/guides/who-receives-a-reward-when-a-fund-makes-the-introduction) chooses among the routes, and [the unpaid decision record](/guides/when-a-fund-prefers-unpaid-introductions) documents the third.

## The terms-version evidence register

Three parts. Two ledgers name every document version; one table of pins ties each introduction to the versions in force when it was sent.

**Part A, SourceX documents.** One row per version, never overwritten.

| Document | Version label | Date | The fund's copy |
|---|---|---|---|
| Channel Partner Agreement | As printed on the signed copy | From the signing record | The executed file as delivered |
| Schedule A | Part of the signed agreement | Same | Inside the executed file |
| Signed addendum | As printed | Its signature date | The executed file |
| Published program terms | The page's label, for example 2026-10-22.2 | Its published date | A saved copy with address and retrieval date |

**Part B, the fund's own documents.** Same discipline: a version label, a date and a copy.

| Document | Version label | Approved by, on | What changed from the last version |
|---|---|---|---|
| Participation policy | v1, v2 ... | Decision-maker and date | One line |
| Authorized-person list | v1, v2 ... | COO and date | Who was added or removed, with start and end dates |
| Disclosure wording | v1, v2 ... | Approver and date | One line |
| Counsel's sign-off | Counsel's reference | Counsel and date | Scope of the view, not its contents |
| Review minutes | Year | Partners and date | Continue, change route or wind down |

**Part C, the introduction pins.** One row per introduction.

| Field | What to write |
|---|---|
| Introduction reference | The fund's own code, never the company name in an open column |
| Date sent | The timestamp on the introduction record |
| Acting person | Name and role |
| Authorized-list version | The version that listed that person on that date |
| Policy version | The version in force on that date |
| Disclosure version | The wording the founder received |
| Agreement and addendum | Versions in force on that date, from Part A |
| Terms version | The label published on that date, from Part A |
| Pointer | Where the introduction record and SourceX's later notices sit |

Three filing rules keep it trustworthy. Capture documents as delivered, and copy the four facts section 7.9 of the sample says a signing record "must identify": "the Party, authorized signatory, document version and signature date." Store copies read-only in a format meant to last; ISO 19005, the PDF/A family, is titled a file format "for long-term preservation", and in paraphrase its listing says it addresses the static visual appearance of page-based documents. A preserved file shows what a page looked like, not that it was in force, so the pins carry that. And point rather than copy: the introduction record already holds the fields section 3.3 of the sample lists, so the register names where it sits instead of repeating company facts.

**Method note.** Part A applies sections 2, 7, 8, 9, 10 and 11 of SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and sections 1.6, 3.3, 4.4 and 7.9 and Schedule A paragraphs 8 and 9 of the sample Channel Partner Agreement (version 2026-10-19), read on 2026-10-28. Parts B and C are built for this page from common fund records and have not been tested in a dispute or an LP inquiry. The register records which documents were in force; it interprets none of them and judges nothing about whether an introduction should have been made.

## Keeping the register alive when people leave

A register kept by one partner dies with that partner's laptop. Four habits keep it institutional:

1. **Own it by role.** Name the role, usually the COO or the chief compliance officer, and a deputy. The role answers questions; the person rotates.
2. **Close rows at departures.** When someone leaves, end-date their line in the authorized-person list and leave their pins untouched. Their introductions stay theirs in the record. For the live relationships, [the partner offboarding checklist](/guides/how-to-offboard-a-partner-while-preserving-active-company-relationships) keeps each company's next step clear.
3. **Plan for the vehicle ending.** Funds wind down; management companies usually outlive them. Decide with fund counsel which entity keeps the register after a fund vehicle dissolves, and write that decision into Part B.
4. **Restrict access.** Section 1.6 of the sample counts "introduced contact identities, introduction records" as Confidential Information. The register inherits that status.

Retention follows the documents. Under section 9 the agreement runs one year and may end on 30 days' notice; contacts introduced during the term stay protected for six months after it ends, and confidentiality lasts three years. Section 10 keeps rewards already earned payable when their conditions are met, so any reward still waiting holds the register open. What happens to an introduction still in review when the fund exits is not settled by the published terms; SourceX decides, and its answer goes into Part A as its own row.

## Duties the register touches, and what stays out of it

- **Permitted retention.** Section 4.4 of the sample asks each party to return or delete the other's confidential information on request or termination, except "records needed for legal obligations, reward accounting, dispute evidence or routine inaccessible backups." A lean register fits that purpose; one stuffed with company facts strains it.
- **The fund's own recordkeeping.** Whether these papers also fall under the fund adviser's own recordkeeping duties is a question for fund counsel and the chief compliance officer. This page does not answer it.
- **The fund's governing documents.** Counsel reads them; the register records only that counsel did, when and on what scope. Wave 9's [clause-by-clause issue list](/guides/how-to-review-referral-terms-against-fund-documents) shows the SourceX provisions counsel sets beside them.
- **Company records.** None. Fit facts and anything learned about a company stay where they already sit, as [the nine-event decision register](/guides/the-professional-referral-audit-trail-without-excess-client-detail) also insists.
- **Custom terms.** A signed Schedule A or addendum can differ from the published default. File it as that agreement's row only; [the terms segmentation plan](/guides/how-to-keep-custom-terms-from-confusing-standard-partners) explains why one partner's exception must never read as the fund's rule.

## An LP's question two years later (Illustrative)

Illustrative. A composite fund with invented internal versions; only the terms version label is real.

In 2028 an LP asks the fund's COO whether an introduction a departed venture partner made in October 2026 followed the fund's rules. The COO, who joined in 2027, opens the register.

The pin for that introduction reads: sent 15 October 2026; acting person, the venture partner; authorized-person list v2, which listed that partner from 1 October to 31 December 2026; policy v1, approved in September 2026; disclosure wording v1; agreement as signed under its earlier title, no addendum yet; program terms version 2026-10-12. Part B shows counsel's sign-off dated before policy v1 took effect.

The COO answers the LP from those rows in three sentences, without naming the company and without describing anything in the fund's governing documents. Had the question been about a reward rather than the fund's rules, the same rows would go to counsel, and to SourceX under section 7, which asks for "the referral details and supporting evidence". Under Schedule A paragraph 8 SourceX keeps its own dated introduction evidence and attribution decisions; the fund's register is the fund's half of the record, not a substitute for SourceX's.

## Where a version register misleads

- **A saved page proves less than it seems.** It shows what a page said when it was saved, not what someone read on another day.
- **It cannot settle conflicts.** Where two documents read differently, the register shows both. Counsel and SourceX resolve them.
- **SourceX's records decide attribution.** Section 2 decides credit from dated records, and SourceX holds the fuller set.
- **Internal versions drift silently.** A policy edited without a new version number breaks every pin that cites it. Version Part B as strictly as Part A.
- **Personal accounts sit partly outside it.** The SourceX half of an individual route is the individual's.
- **No benchmark exists.** SourceX has not published how funds keep these records or how often version questions arise.

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

Open both ledgers on the day the fund signs: [register as a partner](/register), save the [program terms](/terms) version in force with its retrieval date, and test each company against [who qualifies](/who-qualifies) before anyone writes to its CEO; the yearly check of the whole arrangement is in [the annual partner-program review](/guides/the-annual-review-of-a-fund-s-external-partner-programs), and more fund-side decisions are in the [guides library](/guides).

Keeping the fund's referral records is one task; evaluating SourceX as a possible investment is a separate one, with separate files and people, and anyone at the fund weighing it can request 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/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.iso.org/standard/50655.html
- https://sourcex.si/investors
