# Reconcile a referral reward to the supplier basis | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-reconcile-a-reward-with-the-supplier-payment-basis
Last updated: 2026-11-04

Recompute the reward from the supplier payment basis SourceX states, not from the deposit you received. Entitlement to date is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on the company's first qualifying transaction, plus 15% of each further qualifying transaction first agreed within 12 months of the first Closing, unless a signed Schedule A says otherwise. Subtract what you have already received, and the result is what should be due once every payment condition clears. Any difference from the cash that arrived gets a reason code: timing, floor or minimum, exclusion, reduction or offset, signed exception, partial handoff, bank or unexplained.

A finance manager reconciling a referral reward has three records that should agree: what SourceX says it paid the referred company, what the formula says you are owed, and what reached your bank. When they disagree, the fault is usually in the middle record, your own recomputation, and the most common errors are using the company's gross payment, counting the USD 50,000 floor again on a repeat transaction and treating each event as if it stood alone.

## What you reconcile against, and what you will never see

The referred company's invoices, Confirmation and bank records are its own confidential documents, and a partner never asks for them. The basis you reconcile against is the one SourceX states for your referral. The partner agreement says SourceX keeps records sufficient to explain a reward calculation or reversal, and that you receive the information reasonably needed to understand your own referral and reward: reference codes, status information and redacted calculations.

| Record | Issued by | What it tells you | What it leaves out |
|---|---|---|---|
| Reference code | SourceX | Which referral and transaction a line belongs to | The Acquisition Partner's identity |
| Redacted calculation | SourceX | The qualifying basis behind your reward, whether the transaction is the company's first or a repeat, any reduction and its reason | The supplier's invoice, contract terms and SourceX's margin |
| Reward status | SourceX | Estimated, Eligible, Approved, Processing or Paid | Why a condition is still open, unless you ask |
| Your bank record | Your bank | The amount and date actually received | Anything about the basis |
| Your signed agreement | You and SourceX | The rate, floor, minimum and base that apply to you | Anything about the company |

"Supplier payment" means something else on another part of this site: the [supplier-to-first-payment packet](/guides/chain-supplier-to-first-payment) describes a company's own accounts payable records as a possible dataset. Here the supplier is the company you referred, and the payment is what SourceX pays it for its data.

## Recompute from the top every time

The base is Actual Supplier Payout: compensation actually paid to the referred company for selected data that reaches Closing and the qualifying completed handoff. Separately itemized taxes and expense reimbursements, SourceX's fees, the Acquisition Partner's full price and your own reward are excluded, and so are ranges, unclosed data and unpaid amounts. The governing conditions then decide when an amount is payable: the Acquisition Partner's acceptance, its payment received by SourceX in cleared funds, SourceX paying the company, SourceX finance approval, and your payment and tax details.

The reconciliation uses one formula, applied to the running total each time anything changes:

1. **Cumulative basis** = every qualifying payment to the company so far, less any reduction or reversal.
2. **Entitlement to date** = the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on the company's first qualifying transaction, plus 15% of the basis of each further qualifying transaction first agreed within 12 months of the first Closing.
3. **Due** = entitlement to date less everything you have already received for that company.

A negative "due" means an overpayment, which the agreement lets SourceX offset against later rewards or recover where the law permits. The method needs no special handling for the floor, because it belongs to the first qualifying transaction and is counted once per company; none for reductions, because they lower the basis of the transaction they touch and the reward with it; and none for offsets, because a later entitlement simply nets against what was already paid. A payment below the USD 100,000 Minimum Transaction adds nothing unless SourceX agreed otherwise in writing. A parent company and its subsidiaries are one referred company for the floor, so a group's payments sit on one sheet.

## The supplier-payout reward reconciliation sheet

One sheet per referred company or group, one row per supplier payment or reduction, with each remittance recorded on the row it settles.

| Column | What goes in | Where it comes from |
|---|---|---|
| A. Reference code | SourceX's code for the referral or transaction | SourceX |
| B. Event and date | Supplier payment, reduction or reversal, with its date | SourceX's status and calculation |
| C. Basis of this event | Qualifying amount after exclusions; negative for a reduction | Redacted calculation |
| D. Cumulative basis | Previous D plus C | Formula |
| E. Entitlement to date | the greater of $50,000 plus 5% and 15% of the first qualifying transaction's basis, plus 15% of each later qualifying transaction in the Repeat Window | Formula, at your signed rate and floor |
| F. Received before this row | Sum of earlier deposits for this company | Your bank record |
| G. Due | E less F | Formula |
| H. Received for this row | The deposit, with its date | Your bank record |
| I. Variance | H less G | Formula |
| J. Reason code | One code per variance, from the list below | Your judgment, then SourceX's answer |
| K. Open item | The condition still pending, and who clears it | Status |

**Reason codes.**

| Code | What it means | Whose record explains it |
|---|---|---|
| T, timing | A payment condition is still open: cleared funds, finance approval, or your own payment and tax details | SourceX's status; your profile |
| C, floor or minimum | The USD 50,000 floor was expected again on a repeat transaction, or a payment below the USD 100,000 Minimum Transaction was counted | The formula |
| X, exclusion | An itemized tax or reimbursement was in your basis but not in SourceX's | The redacted calculation |
| R, reduction or offset | The company's payout was reduced, and the excess was offset or recovered | SourceX's explanation and supporting calculation |
| S, signed exception | Your Schedule A or an addendum sets a different rate, base, floor or minimum | Your signed agreement |
| P, partial handoff | A partial delivery was not agreed in writing as a separate qualifying handoff | The written agreement, or its absence |
| B, bank | Bank charges or currency conversion after the money left SourceX | Your bank |
| U, unexplained | None of the above | Ask SourceX with the reference code |

Only T is expected to clear on its own. C, X and S mean your expectation was wrong; R means the basis changed; B is a cost on your side; U is a question for SourceX. The [installment ledger](/guides/installment-referral-reward-ledger) tracks how each installment accrues; this sheet tests what you were actually paid against it.

## One company, five events, two years (Illustrative)

Illustrative. A 340-person facilities maintenance contractor licenses work order and inspection records. Invented amounts and dates; no real company, quote or completed deal. The second and third transactions were each first agreed within 12 months of the first Closing, inside the Repeat Window.

| Event | Basis of event | Cumulative basis | Entitlement to date | Received before | Due | Received | Code |
|---|---|---|---|---|---|---|---|
| 1. First qualifying transaction paid, Feb 12 | $120,000 | $120,000 | $56,000 | $0 | $56,000 | $56,000 on May 8 | T until May 8 |
| 2. Second transaction paid, Jun 10 | $160,000 | $280,000 | $80,000 | $56,000 | $24,000 | $24,000 on Jul 30 | X against a $26,400 expectation |
| 3. Third transaction paid, Oct 6 | $180,000 | $460,000 | $107,000 | $80,000 | $27,000 | $27,000 on Dec 18 | C against a $59,000 expectation; T for the late date |
| 4. Reduction on the third, Jan 20 of year 2 | minus $60,000 | $400,000 | $98,000 | $107,000 | minus $9,000 | $0 | R, $9,000 overpaid |
| 5. Renewal payment, Apr 14 of year 2 | $80,000, below the minimum | $400,000 | $98,000 | $107,000 | minus $9,000 | $0 | C, nothing qualifies; R, offset still open |

**Event 1, delayed.** For almost three months the reward sat at code T: the company had been paid, but SourceX was still waiting on the Acquisition Partner's payment in cleared funds. No variance, only time. The $56,000 is the greater of USD 50,000 plus 5% of $120,000 and 15% of it.

**Event 2, an exclusion.** The company received $176,000, of which $16,000 was an itemized reimbursement for archive retrieval. A partner who multiplied the gross figure by 15% expected $26,400 and saw $24,000. The variance is real, but the error is in the partner's sheet, not in SourceX's.

**Event 3, the floor and a late date.** A partner who applied the USD 50,000 floor again expected $59,000 on the third transaction, but the floor belongs to a company's first qualifying transaction alone; a repeat inside the Repeat Window pays 15%, here $27,000, so the $32,000 variance against that expectation takes code C. The remittance also came after the deadline because the partner firm had changed its legal entity and its new tax form was missing. The terms give no new 60-day period; the reward was paid promptly once the form arrived.

**Event 4, a reduction.** Part of the third dataset was reversed and that transaction's payout fell by $60,000, to $120,000. Its reward falls to $18,000, entitlement to date to $98,000 against $107,000 received, so $9,000 is overpaid. SourceX explains a reduction with a supporting calculation, and may offset the excess against later rewards or recover it where the law permits.

**Event 5, a zero.** The company is paid $80,000 under a renewal agreed during the partner agreement's term. The payment is below the USD 100,000 Minimum Transaction, so unless SourceX agreed otherwise in writing it adds nothing: the cumulative basis stays at $400,000, entitlement at $98,000, and the partner has already received $107,000, so nothing is due and the $9,000 stays open for offset. The company was paid and the remittance is zero, which is correct. Had SourceX recovered the $9,000 in cash in February instead, "received before" would read $98,000 and this row would show $0 due with nothing open. Either route ends at $98,000 for the company. [Supplier payout reversal versus buyer refund](/guides/supplier-payout-reversal-referral-reward) explains why a refund to the buyer alone would have changed none of this.

## Close the month: payable amounts and what is not yet earned

1. **Match every deposit to a reference code.** A deposit without one is not reconciled, however familiar the amount.
2. **Recompute D, E and G for each company with any event this month.** Use your signed rate, floor and minimum.
3. **Code every non-zero variance.** Leave nothing blank; U is an answer.
4. **List open items.** Every T row names its condition and who clears it. Your own payment and tax details are the one item you can clear today.
5. **Separate three totals.** Received this month; due but held by a named condition; and amounts based on compensation not yet paid to the company, which are not earned and stay out of income.

Keep SourceX's redacted calculation with the deposit it explains. The IRS notes that business transactions generate supporting documents, such as invoices, receipts and deposit slips, which contain the information you need to record in your books; a reward's calculation is that document for a referral deposit. How you book the income is a matter for your accountant. For unexplained differences, the terms provide a dispute route: send the referral details and your evidence, and SourceX reviews and communicates its decision. The [rewards policy explainer](/resources/rewards-policy-explainer) and [how referral partners get paid](/questions/how-do-referral-partners-get-paid) cover the statuses and payment methods; [payout calculation examples](/resources/payout-calculation-examples) and [how referral rewards are calculated](/proof/how-referral-rewards-are-calculated) work more arithmetic.

## Before any of this: a company that fits

The sheet only fills if a company fits. That means 50+ full-time employees at peak with contractors excluded, years of records it created itself, the rights to license them and a CEO who wants the conversation and can sign for the company. 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. Partners describe records at metadata level, sign the SourceX Channel Partner Agreement before submitting an introduction, and never collect the company's records or payment documents. What only SourceX's review can settle, whether the records match current demand and what rights cover them, is also why the basis column starts empty. More finance guides sit in [the guides hub](/guides).

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

When your sheet is ready to receive its first row and a CEO wants the conversation, [sign up for a partner link](/register), confirm the company's fit facts on [who qualifies](/who-qualifies) and write the [program terms](/terms) version on the sheet's first line.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/rewards
- https://www.irs.gov/businesses/small-businesses-self-employed/what-kind-of-records-should-i-keep
