# Referral record closure after SourceX review | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-close-a-referral-record-after-sourcex-review
Last updated: 2026-11-04

Close a referral record only when SourceX has recorded an outcome you can point to: a reward that reads Paid, a duplicate-review decision, a reward canceled as ineligible, a deal that did not close or a reduction with SourceX's calculation. Copy that outcome as SourceX worded it, with the date and the place you read it. Then keep the introduction evidence, the CEO's permission and any reward statements, and remove everything else. Your own theory about why it ended, or about who was first, never enters the record.

Two neighboring questions have their own pages. Whether a quiet record has closed at all is settled by [the stalled-versus-closed rules](/guides/the-difference-between-a-stalled-referral-and-a-closed-one), and a CEO's no is stored, without its reasons, in [a decline record](/guides/how-to-record-a-company-s-decline-without-keeping-its-private-reasons). This page starts after SourceX has said something about your referral, and covers the operations lead's last two jobs on it: writing the reason and pruning the file.

## Four closing lines that record a guess instead of an outcome

The mistakes below look harmless on the day and mislead a year later, when someone at the firm meets the same company again. All four are Illustrative.

| What the record said | What SourceX had recorded | Why the guess fails |
|---|---|---|
| "Lost to another partner" | Not credited after duplicate review | Partners never receive access to other partners' records (terms, section 7), so "another partner" is a theory; earlier contact between the company and SourceX itself is just as possible |
| "We were first: the CEO clicked our link on day 2" | Not credited after duplicate review | The terms decide attribution from dated records and say an earlier link click alone does not decide credit (section 2) |
| "Dead, the CEO went quiet" | Estimated, unchanged | Silence is not an outcome; with no SourceX outcome on file, this checklist does not apply yet |
| "Done, reward paid" | Paid | Paid closes the record but not the arithmetic: reductions recalculate the reward, and further qualifying transactions agreed within the Repeat Window can add to it, with no cap |

## What a closed record keeps, and what leaves it

A closed record has two layers: the introduction as it was made, and SourceX's outcome as SourceX recorded it. The first layer is fixed by the unsigned sample of the Channel Partner Agreement, which says each introduction record identifies the company, domain, partner, opportunity, introduction method and timestamps (section 3.3). The second layer is copied, never composed.

The authoritative history sits with SourceX, not with you. Schedule A of the same agreement says SourceX retains dated introduction evidence, attribution decisions, supplier payout calculations and payment status, and that a partner may request an explanation of its own reward (paragraph 8). Your copy therefore only needs what lets you understand your own referral and, if it comes to that, contest a decision with evidence. Everything beyond that is material to prune.

## The closure reason and retention checklist

The checklist has two parts. Part A turns SourceX's outcome into one of six codes. Part B decides, item by item, what stays in the file.

**Part A: closure reasons.** Use a code only when the evidence column exists. Quote SourceX's label or message exactly and add the date you read it and where.

| Code | SourceX's recorded outcome | Evidence to cite | Write | Never write |
|---|---|---|---|---|
| X1 | The reward reads Paid and the money arrived | Dashboard label, payment statement, bank receipt | Paid, the amount, the date received, adjustable | Final |
| X2 | Not credited after duplicate review | The label or SourceX's message | SourceX's words, quoted | Who you think was credited, or why |
| X3 | Reward canceled because the referral was ineligible | The label or SourceX's message | SourceX's words, quoted | Your theory about fit or demand |
| X4 | No deal | A stage or message from SourceX showing the deal ended | SourceX's words and the date | Anything taken from the company's own notice |
| X5 | Reward reduced or reversed | SourceX's explanation and supporting calculation | The recalculated figure and its date | A figure you worked out yourself |
| X6 | Outcome disputed | Your dispute message and SourceX's reply | Closed on SourceX's outcome of that date, dispute open | Reopened, before SourceX changes its decision |

Notes on four codes. **X1:** a later cut to the company's payout reduces the reward proportionately: a first qualifying transaction is recalculated as the greater of $50,000 plus 5% and 15% of the reduced Actual Supplier Payout, and a repeat within the Repeat Window as 15% of its reduced payout. **X4:** SourceX's company process page says a company whose deal does not close receives a no-deal notice and its declined data is deleted. That notice belongs to the company; never ask the CEO to forward it. **X5:** Schedule A says SourceX must provide an explanation and supporting calculation for a reduction (paragraph 7), so a reduction without one is a question for SourceX, not a blank for you to fill. **X6:** the disputed code keeps SourceX's outcome as the closing line and puts your disagreement beside it, never in place of it.

**Part B: what stays in the file.**

| Item | Keep, hold or remove | Why | Look again when |
|---|---|---|---|
| Introduction record: company, domain, partner, opportunity, method, timestamps | Keep | Agreement section 3.3 names these fields, and a dispute must not erase original evidence | Your firm's retention policy says so |
| The CEO's written yes | Keep | It shows the introduction was authorized | With the introduction record |
| SourceX's outcome as recorded | Keep | It is the closing reason | With the introduction record |
| Payment statements, remittances, tax and payment messages | Keep | Section 4.4 lets a partner retain records needed for reward accounting | Under your finance retention policy |
| Dispute file | Hold while the dispute runs | Original evidence must survive a dispute (section 3.3) | When SourceX communicates its decision |
| Other confidential information from SourceX | Return or delete when asked or at termination | Section 4.4 excepts only what legal duties, reward accounting, dispute evidence or routine backups need | On request, or when the agreement ends |
| Anything from the company's records that reached you | Remove now and tell the CEO it is gone | Section 4.4 bars keeping supplier dataset copies without separate written authorization | Immediately |
| Guesses, opinions, the CEO's private reasons | Never kept | None of them is an outcome | Not applicable |
| Free-text notes | Prune to what supports a code | Notes outlive the people who wrote them | At closure |

This page sets no retention period; your firm's policy and its legal obligations decide that. The agreement adds two limits of its own: retained material stays confidential and may be used only for the purpose it was kept for (section 4.4), and confidentiality survives for three years after the agreement ends, longer for trade secrets (section 5.3).

## Credit is SourceX's call, made from dated records

Only one partner can be credited for a company, and SourceX makes that call. Under section 2 of the terms, the earliest valid introduction of a company that is new to SourceX earns the credit if that company files a verified application within the 90-day window, and the decision rests on dated records such as written introduction evidence, existing applications and preexisting relationships. Section 3 sets the duplicate rule wide: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." When several partners know one company, SourceX settles the overlap in duplicate review.

Some questions the terms do not answer at all, for example whether an earlier conversation SourceX had with a parent company, or another partner's introduction of a sister company, changes the outcome for yours. SourceX settles those in duplicate review too, and a closing line should never anticipate how. For the reward floor the position is settled: a company and its corporate group count as one referred company, so the USD 50,000 floor applies once, to the first qualifying transaction, and repeats pay 15% with no cap.

If you disagree, section 7 of the terms asks you to contact SourceX with the referral details and supporting evidence; SourceX reviews the dispute and communicates its decision. Bring the introduction record, the CEO's dated written yes and the written introduction itself, not a click log, and see [what to include in an attribution question](/guides/the-evidence-to-include-in-an-attribution-question). For disputes arising from the agreement, it sets thirty days of good-faith written notice and discussion before arbitration (section 7.4). While any of this runs, the record carries X6.

## Four records closed in November (Illustrative)

Illustrative. Generic companies and invented dates and amounts; nothing here describes a real referral.

| Record | What SourceX recorded | Code | Closing line | Removed at closure |
|---|---|---|---|---|
| A | Statement: USD 200,000 Actual Supplier Payout, reward Paid at USD 60,000 | X1 | Paid, USD 60,000, received 12 Nov, adjustable | A forecast tab a partner had kept |
| B | Not credited after duplicate review, read on 14 Nov | X2 | SourceX's label quoted, read 14 Nov in the partner dashboard | A note saying "beaten by another partner" |
| C | Reward canceled, referral ineligible, read on 20 Nov | X3 | SourceX's label quoted, read 20 Nov | An email thread guessing why |
| D | Stage showing the deal ended, read on 25 Nov | X4 | SourceX's stage words quoted, read 25 Nov | A forwarded copy of the company's no-deal notice, deleted and the CEO told |

Record B is the one firms argue with. Its relationship owner remembered the CEO clicking the firm's link on day 2, but the firm's earliest written introduction was an email on day 9, and a click alone decides nothing. The partner of record reviewed what the firm held, found nothing earlier than day 9, and closed the record on SourceX's words without a dispute. Had the firm held an earlier dated introduction, it would have sent that once under section 7 and coded the record X6.

## Who signs off a closure, and when it goes up a level

| Role | Does | Takes it further when |
|---|---|---|
| Operations lead | Reads the outcome, applies a code, works through Part B | The label is one nobody at the firm has seen before |
| Relationship owner | Confirms nothing on their side contradicts the record, and sends the CEO at most a short note that the file is closed | The CEO asks what SourceX decided: point the CEO to SourceX and relay nothing |
| Partner of record | Handles disputes and questions about the firm's own reward | A reduction arrives without a calculation, or Paid shows with no money received |

The partner of record is whoever signed the Channel Partner Agreement before submitting. If your CRM closes deals for you, check two of its habits. HubSpot, for example, sets a deal's close date to the current date when the deal moves into a closed stage, unless that automation is switched off, and lets you customize the options of its Closed lost reason property (HubSpot's knowledge base, paraphrased). Add a separate field for the date of SourceX's outcome, because the close date records when someone moved the deal, and replace the lost-reason options with the six codes so no free-text guess fits.

## Reopening a closed record without rewriting it

A closed line is never edited. A new dated event adds a line beneath it:

- **SourceX changes an outcome after a dispute.** Add the new outcome with its date; the X6 line stays as history.
- **A further qualifying transaction.** Under the 2026 terms, a further qualifying transaction with the company first agreed within 12 months of the first qualifying Closing (the Repeat Window) pays 15% of its Actual Supplier Payout, with no cap. The USD 50,000 floor applied once, to the first qualifying transaction, and does not return for a repeat, renewal or amendment.
- **A reduction after Paid.** Add SourceX's recalculated figure and its calculation reference under X5.
- **A new decider.** If the company is acquired, its own CEO decides until closing and the acquirer's CEO afterward. That changes whom you would talk to next time, not the code on the old line.

## What the checklist cannot see

- **Generic stages.** Partners follow their own referral through generic stages or reference codes, and SourceX need not reveal Acquisition Partner names, contracts, prices or margin (agreement, section 4.6). A code describes what SourceX showed you, not the whole deal.
- **Lag.** A company can know its outcome before your dashboard shows one. Wait for SourceX's label instead of closing on what you heard.
- **No published frequencies.** SourceX has not published how often each outcome occurs, so a count of your own codes describes your book, not the program.
- **Reasons behind a decision.** The [status glossary](/resources/referral-status-glossary) explains the labels, [why a company referral was declined](/guides/how-to-understand-why-a-company-referral-was-declined) covers what a partner can and cannot learn, and [attribution versus payment eligibility](/guides/the-difference-between-attribution-eligibility-and-payment-eligibility) separates the two tests a referral faces. More operating guides sit in the [guides library](/guides), and reward rules on the [rewards page](/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 your closed records are clean, the next introduction starts from firmer ground: [register as a partner](/register) if your firm has not yet signed the Channel Partner Agreement, check new companies against [who qualifies](/who-qualifies), and keep the version of the [program terms](/terms) your closing codes rely on.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://refer.sourcex.si/resources/referral-status-glossary
- https://sourcex.si/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://knowledge.hubspot.com/properties/hubspots-default-deal-properties
