How to reconcile manual introductions with portal activity: a monthly worksheet that gives every company one of seven match states, keeps each original record exactly as it was and leaves overlapping claims to SourceX

Short answer

Once a month, line up two lists: the introductions your people made by hand (emails, calls later confirmed in writing, meeting notes) and what the partner portal shows (submissions, link visits, stages). Match them on the company, never on a person or a click, and give each company one of seven match states with one action. A link visit without a written introduction is not an introduction, and a spoken one needs written confirmation. Never back-date, delete or resubmit to make the lists agree: SourceX decides credit from dated records and settles overlaps in its duplicate review.

Visual briefFull-size diagram
Two rows of company chips on one October timeline, your log above and the portal below. R1 on 6 October and R7 on 22 October appear in both rows and are joined by green lines marked tied. R2 sits only in your log, flagged S3 consent only, and R3 is flagged S4 spoken only; R5 sits only in the portal, flagged S6 portal only. A third row of twelve scattered dots is labeled visits, no company named, S5, and a footer reads overlaps: SourceX decides.
Illustrative October worksheet from the example on this page; dates in UTC.

This worksheet compares where introductions are recorded. Matching the portal's stages and reward statuses to a CRM is a different job, set out in mapping SourceX statuses to a fund's CRM. Deciding whether two records describe one legal entity is the job of the entity-brand matching rule.

Why the two lists drift apart

Your firm's list grows wherever your people work: an email to a CEO, a call after a board meeting, a note from a conference. The portal's list grows from a narrower set of events. SourceX's partner home page says that when a company opens your link, the visit is recorded, and that attribution is locked when the company submits its application. Its partner privacy page says referral link visits are recorded with a first-party identifier, and it offers visitors a referral preference with two settings: persistent, or this visit only. A CEO who opened your link may therefore leave no lasting trace in the portal, while a colleague who forwarded the link around may leave a dozen visits that name nobody.

SourceX's partner agreement says which records count. An introduction has to be recorded in writing, through an authenticated portal submission, a tracked verified application, an email or a mutually acknowledged introduction log, and an oral introduction must be confirmed in writing before its protection attaches (section 1.2). Both lists therefore hold valid written records, and both hold noise.

RecordWhere it livesIs it one of the agreement's written forms?What it cannot tell you
Portal submissionThe portalYes: an authenticated portal submissionWhether the CEO agreed; that pointer lives in your file
Email introducing the company to SourceXYour sent mailYes: an emailWhether SourceX has matched it to an application
Email to the CEO only, with your linkYour sent mailIt is your dated evidence that you raised SourceX and the CEO agreed; how SourceX weighs it is SourceX's decisionWhether the CEO ever used the link
Call or meetingYour notesNot until confirmed in writingAnything, until then
Link visitThe portalNo: the terms say an earlier link click alone does not decide creditWho opened it, or for which company
The company's applicationSourceXA tracked verified application, held by SourceXYou see only your own referral's stage

What the worksheet may hold

One row per company, built from pointers rather than content:

  • the company's legal name and web domain, as the CEO confirmed them;
  • the manual record: what it was (email to SourceX, email to the CEO, call), who made it and a reference to where it is stored;
  • the portal record: its reference and the timestamp the portal shows;
  • a pointer to the CEO's written agreement;
  • every timestamp twice, once as recorded with its offset and once converted to UTC;
  • the match state, the action, its owner and a date.

The worksheet never holds email bodies, company records, the company's application details or anything about other partners. The terms say partners never receive access to other partners' records or to applicant documents (section 7), so there is nothing of theirs to record anyway.

The timestamp rule comes from RFC 3339, the IETF specification for timestamps on the internet. It gives every time it expresses a stated offset from UTC, treats a local time with no offset as unacceptable for internet use, and uses the example that 18:50:00-04:00 is the same instant as 22:50:00Z (our paraphrase). An email stamped 18:50 at UTC-4 and a portal entry stamped 22:58 UTC were eight minutes apart, not four hours. Write the original with its offset, add the UTC conversion in its own column, and never overwrite the first with the second.

The activity reconciliation worksheet

Each company gets exactly one state. The last column matters as much as the action.

StateWhat you seeWhat it meansActionNever
S1 TiedYour written record and a portal submission name the same companyTwo records of one introductionNote both timestamps in UTC and keep bothDelete the one that looks redundant
S2 Emailed, not in the portalAn email introduced the company to SourceX; the portal shows nothingA written form exists on your sideKeep the email as the record; if the company later applies and the portal still shows nothing, raise it with SourceX and attach the emailResubmit it so the portal looks complete
S3 Consent onlyYou emailed the CEO with your link; nothing reached SourceXThe CEO agreed, but SourceX has no introduction yetIf the CEO still wants it, submit now; the submission carries today's dateBack-date it or describe it as made earlier
S4 Spoken onlyA call or meeting, with no written recordNothing is protected yetConfirm with the CEO in writing, then submitTreat call notes as an introduction
S5 Visits onlyLink visits with no company namedActivity, not an introductionCount visits on their own lineCall visits referrals or leads
S6 Portal onlyA submission your log does not holdA colleague submitted without logging it, or someone submitted without the CEOFind the submitter and add the CEO's agreement pointer; if there is none, escalateWithdraw or edit it quietly
S7 Two claimsTwo colleagues, or your firm and another partner, on one companyA possible overlapKeep every record as made; inside the firm, name one owner from now on; across firms, SourceX decides in duplicate reviewAsk the CEO to choose a partner, or delete a record

Three rules sit under every state.

  1. Records are added to, never edited. The partner agreement says competing claims are reviewed against dated evidence and that a dispute must not erase original evidence (section 3.3). A worksheet that tidies history destroys the thing SourceX would read.
  2. The portal does not rewrite the agreement. The same agreement says a dashboard edit, an unanswered message or a one-time exception does not amend it (section 7.7). If a portal entry you recorded last month now shows a different company or date, write down both versions and raise it with SourceX, attaching your dated record.
  3. Credit is not a column. The worksheet records which records exist. Whether one of them earns credit depends on SourceX's own records, including any earlier contact between the company and SourceX, which no partner can see. Only one partner is credited per company. The page on the evidence to include in an attribution question covers what to send if you ever need to ask.

Who works the worksheet, and when

WhoDoes whatBy when
Each colleague who introduces companiesLists their manual records for the month, with pointers and offsetsThird working day of the month
The operations leadPulls the portal side, assigns one state per company and assigns actionsFifth working day
The colleague named on each actionCarries it out: a written confirmation, a submission dated today, an agreement pointer foundWithin the month
SourceXDecides credit and overlapping claims from dated recordsNever on your timetable

Four findings go straight to the operations lead: an S6 submission with no CEO agreement behind it, an S7 claim involving another firm, a portal record that changed after you recorded it, and any request from a colleague to back-date anything. The lead's first question is always the same: what does the original record say, and where is it?

October's worksheet, run on 27 October (Illustrative)

Illustrative. Generic companies, invented records, no outcome implied. Times are converted to UTC.

RefCompanyManual recordPortal recordStateAction taken
R1A 210-person freight brokerEmail introducing it to SourceX, 6 Oct 14:40Submission, 6 Oct 14:52S1Both kept
R2A 95-person dental laboratory groupEmail to the CEO with the link, 9 OctNoneS3CEO reconfirmed in writing; submitted 27 Oct, dated 27 Oct
R3A 300-person staffing firmCall notes, 13 OctNoneS4Written confirmation asked of the CEO
R4None namedNone12 link visitsS5Counted on their own line
R5A 160-person engineering firmNoneSubmission, 15 Oct 09:05S6Submitter found; the CEO's agreement email added to the file
R6A 400-person logistics companyEmail to SourceX by one colleague, 20 OctSubmission by another colleague, 21 OctS7, inside the firmBoth kept; one colleague now owns the relationship
R7A 120-person claims administratorEmail to SourceX sent 18:50 at UTC-4 on 22 Oct, which is 22:50 UTCSubmission, 22 Oct 22:58S1Both kept, eight minutes apart

Six companies and one line of visits. Nothing was deleted, nothing was dated earlier than the day it happened, and no row carries a guess about credit. One fit note belongs outside the worksheet: the R3 staffing firm's size is measured on its own full-time staff, not the workers it places with clients, and that is for the CEO to describe and SourceX to review.

Closing rows and keeping the trail

A row closes when its action is done and nothing new has arrived for a full month: S1 and S2 rows stay open until the company applies or the 90-day window from the recorded introduction ends, S5 lines close every month, and an S7 row stays open until SourceX has said whatever it is going to say. Keep closed rows with your reward records; the partner agreement allows records needed for reward accounting and dispute evidence to be kept after other material is returned or deleted. How long beyond that is your firm's retention policy.

Limits of a two-list reconciliation

  • SourceX's records stay unseen. You cannot see earlier applications, accounts or correspondence between SourceX and a company, and section 3 of the terms makes any of them decisive.
  • Visits fade. A visitor who chose the this-visit-only setting may leave nothing for the portal to show later. Your written record matters more than the visit count.
  • The portal decides its own screens. What the dashboard lists, and in what form, is set by SourceX; the partner portal explainer treats the portal as the authority on what it shows. Build the worksheet around whatever your dashboard lets you list.
  • No benchmark. Nobody has published how often manual and portal records disagree in partner firms. Count S3, S4 and S6 rows each month; a rising S6 count usually means people are submitting without logging.

How a single click relates to a credited company is followed step by step in link click versus attributed company, what each record proves when an email and a click disagree is laid out in written introduction versus referral link, and the partner's stages are on how it works. More operating guides are in the guides library.

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.

Run your first worksheet only after everyone who introduces companies has registered as a partner and signed the agreement, check each S3 and S4 company against who qualifies before anyone submits, and keep the program terms version beside every timestamp.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should we resubmit a manual introduction through the portal so the two lists match?

Only where no introduction reached SourceX yet and the CEO still wants one, and then the submission carries today's date. Never present it as made earlier. Where an email already introduced the company to SourceX, keep that email as the record; a fresh submission adds a later date, not an earlier one.

Do link visits belong on the worksheet?

Count them on their own line, never in the company list. A visit records that a browser opened your link; it names no company, and the terms say an earlier link click alone does not decide credit.

Two colleagues introduced the same company. Which record do we delete?

Neither. Keep both exactly as they were made, name one colleague to own the relationship from now on, and let SourceX read the dated records if credit is ever in question. Deleting a record removes evidence the partner agreement says a dispute must not erase.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/privacy
  4. refer.sourcex.si
  5. rfc-editor.org/rfc/rfc3339.html

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment