# Passing a referral reward to the company | SourceX

Canonical: https://refer.sourcex.si/guides/what-if-the-fund-wants-to-pass-the-reward-to-the-company
Last updated: 2026-11-05

SourceX's published terms pay any reward to the credited partner, separately from the company, and the company receives the same payout whether or not a partner is credited. The terms say nothing about handing a reward on. Whether SourceX would ever pay someone other than the partner is its decision, and what a fund does with money it receives is for fund counsel and the fund's tax adviser. So write the wish down as an exception request before anyone tells a founder that money will reach the company.

This page gives no legal or tax advice and describes no fund's partnership agreement, side letters, Form ADV or compliance manual.

## What the company already receives, and why that reframes the wish

The idea usually starts from a belief that the reward comes out of the founder's pocket. It does not. Section 4 of the terms reads: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." SourceX funds the reward from its own share, so the company's payout is fixed by the company's own signed agreement with SourceX and does not move when a partner appears or disappears.

Illustrative, in symbols only. Suppose SourceX pays the company P under its signed deal records. On the company's first qualifying transaction the credited partner's reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, where P is that payout; further qualifying transactions first agreed within 12 months of the first Closing pay 15% of theirs, and the USD 50,000 floor applies once to the company and its whole corporate group. If no partner is credited, the company still receives P. Nothing the fund does with its reward changes P.

So passing the reward on would repair no loss, because there is none. It would be a fresh transfer from whoever signed to a company the fund may partly own: a decision about the fund's own money, for the people who advise the fund.

## Three wishes inside "pass it to the company"

One phrase covers three requests, each answered by a different person.

| The wish | What the fund pictures | What SourceX's published documents say | Who answers the open part |
|---|---|---|---|
| 1. SourceX pays the company instead | The reward goes straight from SourceX to the company | The terms pay the credited partner and name no other payee; section 8 says only an expressly agreed, signed addendum overrides a provision | SourceX, in writing; assume nothing until it replies |
| 2. The fund receives it, then hands it over | The fund is paid and forwards the money | The terms stop at payment to the partner and are silent on anything after it | Fund counsel on the fund's documents; the fund's tax adviser on treatment |
| 3. The fund declines, so the company gets more | Declining enlarges the company's payout | The terms do not provide for declining a reward, and the company's compensation is set by its own signed agreement | SourceX decides how a declined reward is handled; ask in writing |
| 4. Nobody at the fund takes part | The company applies on its own | No partner, so no reward; the company's payout is untouched | The fund's own participation policy |

Row 4 needs no exception at all, so a fund whose only aim is never to profit at a founder's expense can stop there. Unpaid routes are compared in [when a fund prefers unpaid introductions](/guides/when-a-fund-prefers-unpaid-introductions); this page is for the fund that still wants the money to end up with the company.

## Name the asker, the signer, the payee and the intended beneficiary

Redirection adds a fourth name to the usual three.

- **The asker** knows the CEO and raises SourceX: a platform lead, a deal partner, an operating partner.
- **The signer** is the Partner on the Channel Partner Agreement, signed before any introduction is submitted. The sample agreement names the Partner as "an individual, or entity type and jurisdiction", so a fund entity or one person can take that seat. Choosing between them is covered in [who receives a reward when a fund makes the introduction](/guides/who-receives-a-reward-when-a-fund-makes-the-introduction).
- **The payee** is whoever SourceX pays: the credited partner, and only one partner can be credited for a company (section 2). Section 5 lists the partner's required payment and tax details among the payment conditions.
- **The intended beneficiary** is the company. SourceX's documents never name it in connection with the reward.

The fourth name is the hard one, because the company's CEO also decides whether the company talks to SourceX at all. Promised extra money becomes part of a decision that should rest on the company's records, rights and interest, so the request below asks how and when the company would learn of the plan.

## The written exception request template

One page, filled in by the person who wants the exception and decided by whoever the fund's policy names. The form keeps every answer the fund cannot give itself as a question with an owner.

| Field | What the requester writes | Who checks it |
|---|---|---|
| 1. Requester | Name, role and whether they would be the asker, the signer or both | COO |
| 2. Company | Its name and how the relationship arose, with nothing taken from board materials | COO |
| 3. Default route | What the fund's participation policy already says: firm signs, a named person signs with approval, unpaid, or no part | Compliance |
| 4. Exception sought | Wish 1, 2 or 3 from the table above, in one sentence | Compliance |
| 5. Reason | One of: the company is thought to pay for the reward; a conflict worry; the founder asked; a gift to the company; other, stated | COO |
| 6. Terms read | Sections 4, 5 and 8 of the terms, the version number and the date read | Requester |
| 7. Question to SourceX | The message below, the date sent and the date and text of the reply | Requester, then compliance |
| 8. Questions for counsel and tax | Listed, never answered on this form: what the fund's documents say about money from third parties connected to portfolio companies, and how a transfer to the company would be treated | Fund counsel; the fund's tax adviser |
| 9. What the CEO hears | Who could be paid, who says it, when, and confirmation that no onward payment is offered as a reason to proceed | Compliance |
| 10. Decision | Exception approved, refused, or withdrawn because field 5 was a misunderstanding; approver and date | The approver the policy names |
| 11. Review | Reopen on a new terms version, a change of signer, or a change in the fund's holding in the company | COO |

Field 5 does most of the work. A belief that the company pays for the reward is answered by section 4, and the request is withdrawn with a note; a conflict worry goes on to counsel, who may prefer row 4; a founder's request makes field 9 the one to get right.

**Model question to SourceX for field 7.** "We are [entity, type and jurisdiction], registered as a partner [or intending to register]. We are considering asking that any reward connected to [company] be [paid to the company / declined]. Version 2026-10-22.2, since replaced by version 2026-11-04 of your terms does not address this. Please tell us in writing whether you would agree to such an arrangement and, if so, in what signed form. We will promise the company nothing until we have your reply."

Section 8 of the terms gives that power to one document only: "An expressly agreed, signed addendum may override the relevant provisions." Until a signed document says otherwise, the terms as published apply, however warm a reply sounds.

**Method note.** The template's fields come from SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and the unsigned sample agreement (version 2026-10-19), read on 2026-10-28, together with the four names above. Field 8 holds questions, not findings: nothing here reads any fund's documents or states a tax result. The form has not been tested with funds, and SourceX has published no figures on how often funds ask to redirect a reward.

## Duties, outside roles and potential conflicts the exception touches

- **The fund owns part of the company.** A transfer from a fund entity to a portfolio company moves money between parties already tied by an investment; which entity gives, and on what authority, is for counsel.
- **A board seat.** It gives the fund no authority to open a licensing discussion; the CEO does that. What a partner learns from board materials may prompt one question to that company's CEO and goes no further, including into field 2.
- **A person who signed personally.** An operating partner or employee who wants to hand on their own reward needs their own adviser, and possibly the firm's approval for the transfer too.
- **An LP-owned company.** Money sent to a business one of the fund's LPs owns raises relationship questions the platform team cannot see; counsel hears it before field 4 is written.

When two hats meet in one person, the boundary between referral work and investing work is drawn in [separating a company referral from an investment introduction](/guides/separate-a-company-referral-from-an-investment-introduction).

## Two exception requests, two endings (Illustrative)

Illustrative. Generic funds and companies, invented facts, no outcome implied.

**Withdrawn at field 5.** A seed fund's platform lead asks to pass any reward to a 160-person logistics software company, believing the company pays for it. The COO shows her section 4 and the request is withdrawn that day. The default route stands: the management company signs, and the CEO hears that the fund could be paid and that the company's payout is unaffected.

**Sent to SourceX and counsel.** A growth fund wants any reward connected to a 400-person claims processor it controls to go to that company. Field 7 goes to SourceX; field 8 goes to fund counsel and the tax adviser. While both are open, nobody mentions the idea to the CEO. The fund then chooses row 4: the CEO applies on the company's own initiative, nobody registers, and the record notes the replies by date without describing them.

Either way, the file keeps the form, SourceX's reply, the date of counsel's conclusion and the exact words the CEO heard; wording that note is covered in [disclosing a referral incentive to a portfolio founder](/guides/how-to-disclose-a-referral-incentive-to-a-portfolio-founder).

## Company fit is the same on every route

No wish changes whether the company could suit a SourceX program. SourceX screens on five things: at least 50 people on the full-time payroll when the company was at its largest, with contractors set aside; a multi-year history of records the business produced on its own; the legal room to license that material; a CEO who agrees to talk; and a match with a current program. 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.

The fund never collects records, samples or logins; the CEO describes the company. If the company is acquired, the acquirer's CEO decides for it, and before closing the target's CEO does. A parent and its subsidiaries count as one referred company, so the USD 50,000 floor applies once across the group. Demand, rights and license scope stay unknown until SourceX reviews the company.

## Risks and limits of an exception request

- **SourceX may say no.** The terms provide for one payee, and nothing on this page suggests SourceX will agree to another.
- **The fund's documents may close the door.** A transfer could be barred or need approvals the platform team cannot grant. Without counsel's reading, treat row 4 or the default route as the answer.
- **Tax treatment is unknown here.** Only the fund's and the company's own advisers can assess a receive-then-transfer route.
- **The promise can distort the decision.** Extra money offered to a decider invites the question whether the company would have talked to SourceX without it.
- **No reward is certain.** Section 5 says "A lead, meeting or signed agreement alone does not earn a payable reward," so an exception may never have money to act on. The fund-side questions counsel asks first are collected in [the questions fund counsel will ask about referral economics](/guides/the-questions-fund-counsel-will-ask-about-referral-economics), and whether to take part at all in [should a venture fund accept data referral rewards](/guides/should-a-venture-fund-accept-data-referral-rewards).

## 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 the exception request is decided and the CEO wants the conversation, the chosen signer can [register](/register), compare what the CEO describes with [who qualifies](/who-qualifies) and file the version of the [program terms](/terms) it read beside the form.

Deciding what happens to a referral reward is a separate matter from weighing SourceX as an investment; anyone looking at the second 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://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
