# Supplier and partner payout accounting | SourceX

Canonical: https://refer.sourcex.si/guides/why-company-payouts-and-partner-rewards-need-separate-ledgers
Last updated: 2026-11-05

Because they are two separate SourceX obligations owed to two different parties. The company's payout is owed under its signed Dataset Deal Confirmation, invoiced after Closing and due within 60 calendar days of a valid invoice. Your reward is owed under the Channel Partner Agreement: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on the company's first qualifying transaction and 15% on repeats agreed within 12 months, payable only after further conditions, including SourceX's receipt of cleared funds. One rule links the two ledgers. Timing, the base, the once-per-company floor and reductions pull them apart, and only separate ledgers show where.

A partner that books the company's figures as if they were its own will report rewards too early, apply the once-per-company floor to transactions it does not cover, and end up holding confidential numbers it has no reason to hold.

## Two obligations side by side: who owes, who is owed and when

Ledger A is the company's payout, kept by SourceX and the company. Ledger B is your reward, which only you should keep on your side.

| Point | Ledger A: company payout | Ledger B: partner reward |
|---|---|---|
| Owed by | SourceX | SourceX |
| Owed to | The referred company | The partner named in the signed agreement |
| Governing document | The company's Master agreement and Dataset Deal Confirmation | The Channel Partner Agreement and Schedule A, then the program terms |
| Falls due | After Closing, on the company's valid invoice | After acceptance, handoff, cleared funds to SourceX, payment of the company, finance approval and your details |
| Clock | 60 calendar days after SourceX receives a valid invoice, unless signed otherwise | 60 calendar days after final written acceptance or completed handoff, whichever is later; a late condition defers it without a new period |
| Waits for the buyer to pay SourceX? | No, unless the company signed a different arrangement | Yes; cleared funds are a condition |
| Ceiling or floor | Whatever the Confirmation fixes | No ceiling; a USD 50,000 element applies once per company or corporate group, on its first qualifying transaction |
| Who sees the detail | The company and SourceX | You, through statuses, reference codes and redacted calculations |

The buyer-payment row explains most surprises. Schedule A says the supplier Fee is earned at Closing and is not conditional on an Acquisition Partner paying SourceX unless the supplier signed a different arrangement, and that this does not remove the cleared-funds condition for the reward. Ledger A can therefore show the company paid while Ledger B is still waiting. Neither ledger is wrong.

## The single rule that connects them, and what stays outside it

One rule links the two ledgers: **Ledger B's total for a company equals the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on its first qualifying transaction, plus 15% of Actual Supplier Payout on each further qualifying transaction first agreed within 12 months of that first Closing.** A transaction below the USD 100,000 Minimum Transaction adds nothing unless SourceX agrees in writing. Each reward line accrues as each installment reaches the company: the USD 50,000 element with the first installment that meets every condition, the percentage elements proportionately.

What counts as Actual Supplier Payout is narrower than "money SourceX sent the company":

- **Inside the base:** compensation actually paid for selected data that reached Closing and the qualifying completed handoff, under the company's signed agreement, Confirmation and any amendments.
- **Outside it:** separately itemized taxes and expense reimbursements, the reward itself and the Acquisition Partner's full transaction price. SourceX's own fees are outside it too, and Schedule A adds that a change to SourceX's price or fee does not change the reward base by itself.
- **Not yet in it:** indicative ranges, data that has not closed and amounts the company has not been paid.

Movements in Ledger A carry through to Ledger B in only one direction. When Ledger A shows the company's payout cut or reversed, Ledger B recomputes that transaction's reward on the reduced Actual Supplier Payout, using the same formula: the percentage element falls with the base, and any excess already paid is adjusted. A buyer refund that leaves the company's payout untouched changes nothing in either ledger.

Nothing ever nets between them. SourceX pays the reward as a payment of its own and never takes it from the company's agreed compensation, which is why Ledger A carries no "partner fee" line and Ledger B no "company share". If you signed a Schedule A or addendum with a different rate, base or floor, write it at the top of Ledger B; it prevails over the website terms.

## The two-ledger reconciliation diagram, row by row

The diagram on this page draws the two ledgers as lanes on one timeline. Ledger A runs along the top: Closing, the company's invoice, then each installment as SourceX pays it, with the cumulative total beneath. Ledger B runs underneath: each Ledger A payment drops a line into it on the 2026 formula, the line waits at a gate until SourceX has cleared funds and finance approval, and the lane keeps growing with Ledger A, because there is no ceiling; only the USD 50,000 element appears once, with the first installment.

Illustrative: one invented company, one first qualifying transaction paid in two installments and two later reductions.

| Step | Ledger A event, as SourceX reports it | Ledger A cumulative | Ledger B effect | Ledger B status |
|---|---|---|---|---|
| 1 | Closing; the company invoices SourceX | $0 | Nothing accrues yet | None |
| 2 | Installment 1 paid to the company in month 2 | $240,000 | $62,000 accrues: the USD 50,000 element plus 5% of $240,000 | Waiting on cleared funds and approval |
| 3 | SourceX receives cleared funds in month 4; finance approves | $240,000 | $62,000 approved, then paid | Paid |
| 4 | Installment 2 paid to the company | $480,000 | $12,000 accrues, 5% of the installment; Ledger B stands at $74,000 | Approved, then paid |
| 5 | Company's amount cut by $80,000 | $400,000 | Recomputed at $70,000, so $4,000 is adjusted | Offset against later amounts or recovered |
| 6 | Cut by a further $40,000 | $360,000 | Recomputed at $68,000, so a further $2,000 is adjusted | Offset against later amounts or recovered |

Step 4 is where the formula shows its shape. 15% of $480,000 would be $72,000; USD 50,000 plus 5% is $74,000, so the floor line still wins and Ledger B stands at $74,000. A further qualifying transaction the company first agrees within 12 months of this Closing would add 15% of its own Actual Supplier Payout, with no second USD 50,000 element and no ceiling. Step 5 shows why the reduction rule matters: an $80,000 cut in Ledger A moves Ledger B by only $4,000, because the USD 50,000 element does not shrink with the base. Step 6 repeats the recalculation, and SourceX must give an explanation and supporting calculation for each adjustment. The [installment ledger template](/guides/installment-referral-reward-ledger) covers the installment split in more detail, and the [payout reversal examples](/guides/supplier-payout-reversal-referral-reward) show a cut and a buyer refund side by side.

## Four places the ledgers legitimately part (Illustrative)

Each line below is a case where Ledger A and Ledger B show different numbers and both are correct.

| Divergence | Ledger A shows | Ledger B shows | Governing term |
|---|---|---|---|
| Timing | Paid in month 2, on the company's invoice | Paid in month 4, after cleared funds | Terms section 5; Schedule A paragraph 5.5 |
| Base | USD 100,000 sent, of which $10,000 is itemized expense reimbursement | Nothing: the $90,000 base is below the USD 100,000 Minimum Transaction unless SourceX agreed in writing | Terms section 4: taxes and reimbursements excluded; Minimum Transaction |
| Repeat Window | A second transaction of $240,000, first agreed within 12 months of the first Closing | $36,000 on that transaction, not $62,000: the USD 50,000 element applied only to the first | Terms section 4: the floor once per company; repeats at 15% |
| Reductions | Cut from $480,000 to $400,000 | Down $4,000, from $74,000 to $70,000 | Terms section 6, applied to that transaction's Actual Supplier Payout |

Two further cases leave both ledgers empty, which is also worth recording. A Confirmation that never reaches Closing creates no payment to the company and no reward; a signed document is not a ledger event. And a late condition on the reward side, such as cleared funds arriving after the 60-day deadline, changes nothing in Ledger A: the reward is paid promptly once the condition is met, and no new 60-day period begins.

## What belongs in your books, and what stays in the company's

Ledger B should be built only from what SourceX gives you. The agreement says partners receive the information reasonably needed to understand their own referral and reward, through reference codes, status information and redacted calculations, and that SourceX need not reveal Acquisition Partner names, contracts, prices or its margin.

| Keep in Ledger B | Leave out of Ledger B |
|---|---|
| Reference code and installment number | The company's invoices and bank details |
| Cumulative reward per company or group, with the USD 50,000 element marked once | The company's Confirmation price or licensing terms |
| Status with its date: Estimated, Eligible, Approved, Processing, Paid | The Acquisition Partner's identity or contract |
| Approved amount, paid date and amount received | Any figure you only know from the company itself |
| SourceX's explanation for each reduction or offset | Estimates presented as receivables |

The hard case is the partner who also advises the company: its accountant, fractional CFO or managed-service provider. You may see the company's side of Ledger A in your client work. Keep two files. The client engagement file holds what the client shares with you as its adviser; Ledger B holds what SourceX tells you as a partner, and it is never filled from the client file. SourceX's own home page tells licensed professionals to check their rules on referral fees, and that is a question for your professional body, not for the ledger. Never suggest to the client that your reward reduces its payout; it does not. The difference between the two flows is also explained for companies in [referral reward versus company licensing proceeds](/guides/how-to-distinguish-a-referral-reward-from-the-company-licensing-proceeds).

Corporate groups get one row. The once-per-company floor sees a parent and its subsidiaries as one company, so however many group entities license, the USD 50,000 element appears on that row once and later qualifying transactions in the group earn 15%; the [subsidiary floor page](/guides/subsidiary-referral-reward-cap) works through group cases.

## Month-end checks that keep Ledger B honest

Run six checks per company before closing the month.

1. **Formula.** Every first-transaction line equals the greater of $50,000 plus 5% and 15% of the amount SourceX has reported as paid on that transaction, and every repeat line equals 15% of it.
2. **Floor once.** The USD 50,000 element appears at most once per company or group, on its first qualifying transaction, unless your signed Schedule A says otherwise.
3. **Bank tie-out.** Every Paid line matches a receipt, and any gap between approved and received has a reason written beside it.
4. **Estimates off the books.** Every Estimated line stays out of receivables and is labeled not yet earned.
5. **Reductions documented.** Every adjustment carries SourceX's explanation and supporting calculation.
6. **Open conditions named.** Every line that is accrued but unpaid says which condition it waits on.

In management reporting, show three numbers per company: paid, payable (Approved or Processing) and estimated. Never fold the third into the first two. If a check fails, rebuild the figure before you query it; the payment rails and paperwork that sit behind the final step are covered in [how referral partners get paid](/questions/how-do-referral-partners-get-paid).

## 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 your firm is about to make its first introduction, open Ledger B before you do: [register](/register) in the name you want paid, check the company against [who qualifies](/who-qualifies), and write the [program terms](/terms) version at the top of the ledger. Related finance guides are in the [guides index](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/rewards
- https://refer.sourcex.si/