How to report delayed referrals without calling them lost: active, paused and closed statuses that change only on a dated event

Short answer

Report a delayed referral as active or paused, never lost, until a dated event closes it: a declined application, a CEO who says no, a duplicate finding, a no-deal notice or an attribution window that ended without a verified application. Before the application, delay has a hard limit, because credit needs a verified application within 90 days of the recorded introduction. After it, review, buyer acceptance and payment can take months without changing attribution. Count every case still open at the cutoff as open, with its age.

Visual briefFull-size diagram
A timeline of five Illustrative introductions against a shaded 90-day attribution window and a cutoff line: two cases close on dated events, one pauses before its application and closes when the window ends, one pauses after credit and runs past the cutoff, and one stays active past the cutoff.
Illustrative cases. The 90-day window comes from the program terms and Channel Partner Agreement Schedule A; statuses follow the definitions on this page.

This page is for the fund COO or platform analyst whose quarterly report has a "lost" column that keeps filling with companies nobody has actually lost. It gives the status definitions, the evidence that moves a case between them, and the arithmetic for showing open cases honestly. Which gate a case has cleared, attribution, eligibility or payment, is explained in the difference between attribution, eligibility and payment eligibility; this page is about reporting the cases still moving between those gates.

Two clocks, and only one of them can close a case early

The attribution clock starts at the recorded introduction. Schedule A of the Channel Partner Agreement credits the first valid introduction of a new company when that company submits a verified application within 90 days of the recorded introduction, and the program terms add that the window does not extend because contact protection under the agreement continues. A delay here is not neutral. A CEO who asks for "a few months" before applying can let the window run out.

Everything after the application runs on separate clocks. The Agreement says supplier assessment, exclusive holds, acceptance review and Closing deadlines do not extend attribution or create a longer reward entitlement. Once a company is credited, a slow review delays cash; it does not move credit. The payment deadline itself falls 60 calendar days after two events have both happened, counted from whichever came later: the handoff being completed, or the Acquisition Partner putting its final written acceptance of the complete, validated dataset on record. If a condition such as cleared funds is still outstanding at that deadline, the reward is paid promptly once it is met, and no new 60-day period begins.

So the same three months of silence mean different things at different stages. Before the application, they can end the case. After it, they are a wait. The guide to attribution and contact protection draws the two clocks side by side.

Stages, population and the cutoff for a delay report

  • Population. Unique companies introduced in writing, with the CEO's knowledge, in a stated period. One row per company; a parent and its subsidiaries share one row because they share one reward cap.
  • Cutoff. The date at which every status is read. Each status carries the date of the evidence behind it.
  • Age. Days from the recorded introduction to the cutoff, shown for every case that is not closed.
  • Visibility. After credit, the fund sees generic stages or reference codes, not buyer names or prices. Statuses use what the fund can see and say so.

Active, paused and closed: the status definitions

CodeStatusEnters on (dated evidence)Leaves onClock to watch
A1Active: introduced, window openWritten introduction recordCredited application, or day 90Attribution: show the window's end date
A2Active: credited, in reviewVerified application creditedAgreement stage, hold or declineNone for credit
A3Active: supplier agreement stagePortal stage shows an agreementAcceptance and handoff, or a no-deal noticeNone for credit
A4Active: accepted, payment pendingAcceptance and handoff recordedReward paid, or a condition flaggedPayment: 60 days after the later of acceptance and handoff
P1Paused: company asked to wait, before applyingThe CEO's written requestApplication inside the window, or day 90Attribution keeps running
P2Paused: review waiting on current data needsSourceX's written note or portal statusReview resumes, or a declineReview date you set
P3Paused: company-side hold after creditThe company's email (migration, counsel review, ownership change)Company resumes, or withdrawsReview date you set
P4Paused: payment condition outstandingSourceX's explanation of the missing conditionCondition met and reward paidPaid promptly once met
C1Closed: paid, no open transactionBank receipt matched to SourceX's calculationReopens only for a new transactionNone
C2Closed: window ended without a verified applicationIntroduction date plus 90 days, no creditSourceX decides any later applicationNone
C3Closed: reviewed as a duplicatePortal statusNot reopened by the fundNone
C4Closed: declined in reviewPortal status or SourceX's noteA later program may fit; log a new caseNone
C5Closed: CEO declined or withdrewThe CEO's emailOnly a new, permissioned conversationNone
C6Closed: no dealA no-deal notice or an expired unclosed dealA new transactionNone

Five rules make the table work:

  1. "Lost" is not a status. A case is active, paused or closed.
  2. Closing needs a record. Every C code points to a dated document. A feeling that the company has gone quiet is not one.
  3. Pausing needs an owner and a date. Every P code names who follows up and when, usually within 45 days, and a P1 case shows the window's end date in the same cell.
  4. Time alone moves only one case. Statuses change when evidence changes. The single exception is the attribution window, which closes by the calendar.
  5. Paused cases stay in the denominator. Dropping them makes every rate look better than it is.

On C2: SourceX checks its own records and decides credit from dated evidence. If the company applies after the window, do not report it as credited, and do not assume a fresh introduction resets the clock. Ask SourceX and record its answer. On C4: requirements change with current data needs, and missing one program's criteria today does not rule a company out of another program later. That is a new case with a new date, not a revived old one; the guide to keeping an introduction warm while demand is paused covers the relationship side.

Open cases are censored observations, not failures

Reliability engineers met this problem decades ago. NIST's Engineering Statistics Handbook describes a test that stops at a fixed time: some units have failed, and the rest survived the whole test. Their failure times lie to the right of the cutoff and are simply missing, which the handbook calls right censoring. Nobody counts a surviving unit as a failure.

An open referral at a cutoff is the same kind of observation. The report knows it lasted at least this many days, not how it ends. Two practical rules follow. Never compute an average time to payment from closed cases alone, because the slowest cases are exactly the ones still open. And print the age of each open case beside any time-based figure, so the reader can see how much of the story is still unwritten.

Ten companies at two cutoffs (Illustrative)

Illustrative. Generic companies, invented dates, no real outcomes. All ten were introduced in writing, with the CEO's knowledge, between April and June 2026.

Company (Illustrative)IntroducedStatus at 30 JuneStatus at 30 SeptemberEvidence for the change
210-person freight broker8 AprA2 credited, in reviewA3 agreement stagePortal stage
140-person claims administrator15 AprA3 agreement stageA4 accepted, payment pendingAcceptance and handoff recorded
95-person engineering firm22 AprP1 asked to wait, window ends 21 JulC2 window endedNo application by 21 Jul
320-person staffing firm2 MayC3 duplicateC3 duplicatePortal status, 20 May
160-person software company9 MayA2 credited, in reviewP3 company-side holdCEO's email: CRM migration until January
600-person logistics operator20 MayA2 credited, in reviewP2 waiting on current data needsSourceX's note
75-person accounting firm3 JunA1 window open, ends 1 SepA2 credited, in reviewApplication credited 12 Aug
250-person contact center10 JunA1 window open, ends 8 SepC5 CEO withdrewCEO's email, 30 Jul
130-person insurance agency17 JunA1 window open, ends 15 SepA2 credited, in reviewApplication credited 2 Sep
480-person property manager24 JunA1 window open, ends 22 SepC4 declined in reviewPortal status, 25 Sep

At 30 June, the old report's rule ("no application, or no movement for 30 days, means lost") would have shown 6 of 10 lost: the four companies still inside their windows, the one that asked to wait and the duplicate. Under these definitions the same date reads 8 active, 1 paused and 1 closed. By 30 September, three of the six "lost" companies had been credited, though one was then declined in review. The staffing firm, incidentally, is counted on its own full-time staff only; placed workers on assignment at clients do not count toward the 50.

Rolling open cases forward so none disappear

MovementCompanies
Open (active or paused) at 30 June9
Closed in the quarter: window ended, CEO withdrew, declined in review3
New introductions in the quarter0
Open at 30 September6
Closed since introduction, in total4

Nine open, three closed, six open: the arithmetic has to work every quarter. Add the open and closed lines for the cohort and the result must equal the ten companies introduced. If it does not, a case was dropped or double counted.

The quarterly note: learning, not a reward forecast

The note for this cohort says: 10 companies introduced; 7 credited so far, one of them later declined in review; 4 closed with a dated reason each; 6 open, of which 2 are paused with named owners and review dates; the oldest open case is 175 days old. Reward cash received in the quarter: $0. One company has acceptance and handoff recorded, so its payment clock is running.

What the note leaves out is as deliberate as what it includes. It gives no estimated value for open cases, because the program terms call portal and calculator estimates projections, not promises. It does not annualize anything. And it does not describe paused companies as likely or unlikely to close, because nothing in the record supports either.

Ways a status report still misleads

  • Endless pauses. A P code renewed three times is a decision nobody has made. Escalate it to the relationship owner.
  • Agreement expiry. The Channel Partner Agreement runs one year and renews only with fresh signatures. If a pause could outlast it, put the renewal date on the case and ask SourceX in writing how a long-paused case is treated at expiry, rather than assuming.
  • Partner-side visibility. A2, A3 and A4 rely on generic stages; the fund cannot verify what it cannot see.
  • Small cohorts. Ten companies support counts, not rates. SourceX has not published conversion rates or typical durations to compare against.
  • Demand shifts. A P2 case can sit idle for reasons unrelated to the company or the introduction.

Methods note. The fourteen codes and five rules are this page's own, built on the attribution, duplicate and payment provisions of program terms version 2026-10-22.2, since replaced by version 2026-11-04 and the Channel Partner Agreement sample version 2026-10-19, and on NIST's description of right censoring, checked 2026-10-26. They classify cases; they do not predict outcomes, measure record quality or estimate any company's compensation.

Fit facts that make a delay worth waiting out

A delay is only worth tracking for a company that could fit. Before anyone is introduced, check the published facts: at least 50 full-time employees at the company's peak, a figure contractors do not count toward; an operating history with documents behind it; the right to license its own records; and a CEO who authorizes the discussion. 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. Funding status decides nothing. Whoever submits the introduction must already have signed the SourceX Channel Partner Agreement; a partner whose copy carries the older name, "Channel Partner Non-Circumvention and Non-Disclosure Agreement", is held to that copy exactly as signed.

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.

Before your next introduction, register for a partner link so the 90-day clock starts from a dated record, check the company against who qualifies, and read the attribution and payment sections of the program terms.

A fund weighing SourceX as a possible investment, rather than reporting its own introductions, should start from the SourceX investor overview and request materials there.

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.

  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

If a CEO asks us to wait until next quarter, is the introduction safe?

Not automatically. Credit needs a verified application within 90 days of the recorded introduction, and that window does not stretch because the CEO asked for time. Record the window's end date on the case, tell the CEO it exists, and treat an application after it as a question SourceX decides from dated records.

Does a long SourceX review put attribution at risk?

No. Once the verified application is credited, review, supplier agreement, acceptance and Closing run on separate clocks that do not extend or shorten attribution. A slow review delays cash; it does not move credit.

When should a paused case be closed?

Only when a dated event closes it: the window ends without an application, a duplicate finding, a decline, a withdrawal or a no-deal notice. A pause that keeps getting renewed should be escalated to the relationship owner, not quietly relabeled as lost.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. itl.nist.gov/div898/handbook/apr/section1/apr131.htm
  4. refer.sourcex.si/who-qualifies
  5. sourcex.si/investors

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