# Referral reward payment periods: a tracker | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-receives-several-payments-in-different-periods
Last updated: 2026-11-05

Each payment SourceX makes to the introduced company adds its own slice of reward in the period that payment is made: on the company's first qualifying transaction the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and 15% on each further transaction first agreed within 12 months of the first Closing. The slice becomes payable once the program's conditions are met, and a payment that lands after the 60-day deadline is paid promptly when its conditions are met, with no fresh 60 days. Track four dates for every payment, assign each to a period, and keep accrued, received and adjusted amounts in separate columns.

A finance manager closing quarters needs more than the arithmetic of a single payment. The question here is where each amount sits in time: which quarter it accrued in, which quarter the cash arrived in, which quarter a reduction adjusted it, and what to show while it is between those points. The company's side of the same payments, including how proceeds reach a fund, is covered in [who receives portfolio company license proceeds](/questions/who-receives-proceeds-from-a-portfolio-company-license).

## Why one company can be paid in several periods

SourceX usually pays a company a one-time fee for a dataset, so a single deal is often a single payment. Several payments arise in four ordinary ways:

- **A second deal.** A returning company reuses its Master and signs a new Dataset Deal Confirmation for another dataset.
- **Payments set by the agreement.** Some agreements set recurring deliveries, each paid as the agreement states, and the terms expressly contemplate supplier compensation paid in installments.
- **Repeat licenses and renewals.** These count for the partner only if first agreed within 12 months of the company's first qualifying Closing, the Repeat Window, and each must still meet the USD 100,000 Minimum Transaction on its own.
- **A separately selectable lot.** A partial handoff counts as its own qualifying event only if SourceX and the partner expressly agree in writing.

None of these is capped, but the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and does not return on a repeat, renewal or amendment. A parent company and its subsidiaries count as one company for that floor, so a group that licenses through several entities belongs on one tracker.

## The dates that place each payment in a period

The terms give each payment four dates that matter to a partner, and each can fall in a different quarter.

| Date | What sets it | Effect on the tracker |
|---|---|---|
| Company paid | The company's own signed terms, typically within 60 days of a valid invoice after Closing | The reward slice accrues in this period: the first-transaction formula, or 15% on a repeat, in proportion to the installment |
| Day 0 | The later of the Acquisition Partner's final written acceptance and completed handoff of the complete, validated dataset | Starts the payment clock for that transaction |
| Deadline | Day 0 plus 60 calendar days | The reward is due by then if every condition is met; if not, promptly once they are, with no new 60-day period |
| Reward received | Cleared buyer funds, payment of the company, finance approval and the partner's payment and tax details | Cash moves from accrued to received in this period |

One line in section 8 of the [program terms](/terms) keeps the columns honest: the company's payment timetable never determines when a reward is paid. It determines when the slice accrues, because the reward is calculated on money the company has actually received.

## The period-by-period tracking example

Illustrative. A 260-person title and escrow services company was introduced by a partner whose Channel Partner Agreement was signed in February of Year 1. Deal 1 closed in October of Year 1, so the company's Repeat Window for further transactions runs to October of Year 2. Over three years the company is paid five times. Deal 2 was agreed in January of Year 2, inside the window. The assumptions about how its fees are split are invented for the example.

First, the dates for each payment:

| Payment | Company paid | Day 0 | Deadline | Reward received | Quarter accrued, then received |
|---|---|---|---|---|---|
| Deal 1, one-time fee of $180,000 | Dec 28, Year 1 | Nov 20, Year 1 | Jan 19, Year 2 | Jan 14, Year 2 | Q4 Year 1, then Q1 Year 2 |
| Deal 2, first of two $60,000 parts | Apr 8, Year 2 | Mar 3, Year 2 | May 2, Year 2 | Apr 28, Year 2 | Q2 Year 2, same quarter |
| Deal 2, second part | Sep 29, Year 2 | Mar 3, Year 2 | May 2, Year 2, already passed | Oct 13, Year 2 | Q3 Year 2, then Q4 Year 2 |
| Deal 3, repeat license agreed in July of Year 2, $160,000 | Mar 20, Year 3 | Feb 2, Year 3 | Apr 3, Year 3 | Apr 1, Year 3 | Q1 Year 3, then Q2 Year 3 |
| Deal 4, renewal first agreed in November of Year 2, $90,000 | Aug 20, Year 3 | Not tracked | Not tracked | Nothing | No accrual |

Then the tracker itself, one row per quarter, the view a finance manager closes each period:

| Quarter | Paid to the company | Accrued this quarter | Received this quarter | Accrued, not yet received | Cumulative reward | Note |
|---|---|---|---|---|---|---|
| Q4 Year 1 | $180,000 | $59,000 | $0 | $59,000 | $59,000 | USD 50,000 plus 5% of $180,000; finance approval still open at year-end |
| Q1 Year 2 | $0 | $0 | $59,000 | $0 | $59,000 | Received before the Jan 19 deadline |
| Q2 Year 2 | $60,000 | $9,000 | $9,000 | $0 | $68,000 | First part of deal 2, 15% of the installment |
| Q3 Year 2 | $60,000 | $9,000 | $0 | $9,000 | $77,000 | Paid to the company after its deadline |
| Q4 Year 2 | $0 | $0 | $9,000 | $0 | $77,000 | Paid promptly; no new 60 days |
| Q1 Year 3 | $160,000 | $24,000 | $0 | $24,000 | $101,000 | 15% of $160,000; no floor on a repeat |
| Q2 Year 3 | $0 | $0 | $24,000 | $0 | $101,000 | Received before the Apr 3 deadline |
| Q3 Year 3 | $90,000 | −$2,000 | −$2,000 | $0 | $99,000 | Deal 4 earns nothing; a $40,000 reduction on deal 1 takes $2,000 off its reward, settled this quarter |
| Total | $550,000 | $99,000 | $99,000 | $0 | $99,000 | Every accrued dollar received |

The company was paid $550,000 across five payments before the reduction on deal 1; the partner's total is $99,000 under the default terms, with no cap to stop it. None of this touches the company's money: SourceX funds the reward separately.

## Delayed, reduced and zero: what each contrast teaches

**Delayed across a quarter line.** Deal 2's second part was paid to the company on September 29, months after deal 2's deadline of May 2. The terms do not restart the clock; the slice is due promptly once its conditions are met. In the tracker it accrues in Q3 and arrives in Q4, so the Q3 close shows $9,000 accrued and not yet received, with the open condition named beside it.

**A repeat at 15%, without the floor.** Deal 3 produced $24,000, 15% of $160,000; the USD 50,000 floor had already been used on deal 1 and does not return on a repeat. Deal 3 qualified at all because it was first agreed in July of Year 2, inside the Repeat Window; acceptance and handoff months later do not change that.

**Zero, and a reduction that counts.** Deal 4 was first agreed in November of Year 2, after the Repeat Window closed, and its $90,000 sits below the USD 100,000 Minimum Transaction, so it creates no reward unless SourceX and the partner agree otherwise in writing. Separately, the $40,000 reduction on deal 1 in Q3 Year 3 does change the reward: deal 1's Actual Supplier Payout falls from $180,000 to $140,000, USD 50,000 plus 5% of which is $57,000, so $2,000 of the $59,000 already paid is adjusted. A reduction that lawfully lowers what the company kept lowers the reward in proportion; one that does not leaves it alone.

Payment-by-payment arithmetic on one sheet, without the period view, is in the [installment reward ledger](/guides/installment-referral-reward-ledger), and repeats and renewals across parallel licenses are worked through in the [renewal scenarios](/guides/data-referral-renewal-cap).

## Five checks before closing a period

1. **Every accrued slice has a dated payment behind it.** A Confirmation, an invoice or a scheduled installment adds nothing until the company is actually paid.
2. **The floor is counted once per company group**, not per entity or per agreement, and never again on a repeat, renewal or amendment unless a signed Schedule A says otherwise. The [subsidiaries guide](/guides/how-to-handle-multiple-subsidiaries-in-referral-attribution) covers group structures.
3. **Every accrued-not-received amount names its open condition**: cleared buyer funds, payment of the company, finance approval or your own details.
4. **Adjustments are booked in the period you are told about them**, with SourceX's explanation and supporting calculation attached. An overpaid reward may be offset against later rewards or recovered where the law permits, so a "received" figure can still move. Whether to restate a closed period is your accountant's call; the [reversal examples](/guides/supplier-payout-reversal-referral-reward) show what changes the base and what does not.
5. **Zero rows stay visible with their reason.** Deal 4 belongs on the tracker so that nobody books it later from memory. The note on [rewards from repeat business](/questions/referral-fee-on-repeat-business) is the place to check before counting a renewal.

## Which tax year a cross-year slice belongs to

Deal 1 accrued in December of Year 1 and arrived in January of Year 2. IRS Publication 538 says that under the cash method a taxpayer includes income actually or constructively received during the tax year, and that under an accrual method income is generally reported in the year it is earned. A cash-method partner therefore looks at the January receipt; an accrual-method firm has to ask its adviser when its right to the reward was fixed, given that finance approval and other conditions were still open at year-end. This page describes the timing only; it is general information, not tax advice. For setting money aside when a slice arrives with nothing withheld, see [estimated taxes on referral income](/questions/estimated-taxes-on-referral-income).

## What stays uncertain until a payment lands

A tracker built this way is deliberately backward-looking. Projected payments, such as the second part of a deal before it is paid, belong in a separate forecast with their expected quarter and no accrual. SourceX does not publish typical times between Confirmation, acceptance and payment, and the conditions in section 5 can move a slice from one quarter to the next without anything going wrong. The [rewards page](/rewards) lists the statuses a partner sees for each slice, from Estimated to Paid.

The introduction behind all of this still had to fit: a company with 50 or more full-time employees at peak, contractors excluded, years of documented records, rights to license them and a CEO who wanted the conversation.

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

If a company you know could license more than one dataset over time, [register for a partner link](/register), confirm the company against [who qualifies](/who-qualifies), and keep sections 4, 5 and 8 of the [program terms](/terms) beside the tracker so each payment lands in the right period.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://www.irs.gov/publications/p538
