Two programs can both advertise 30% commission and still pay wildly different amounts for the same customer. One pays 30% of the invoice total. The other pays 30% of the pre-tax amount that landed in the bank after a coupon. On a $99 annual plan with a 30% discount and 20% VAT, those two numbers are $24.94 and $20.79. Multiply by a few hundred orders and the gap is a salary.
The percentage is the number everyone negotiates. The base is the number almost nobody writes down, and it decides the actual payout. This guide is about the base: what gross and net mean on a real order, what Polar, Stripe, and Paddle each hand you, and a default you can put in your terms without needing to explain it twice.
TL;DR
- The commission basis is the amount the percentage gets multiplied by, and it deserves its own line in your program terms.
- The defensible default is the pre-tax amount you actually collected, after discounts, before refunds: commission = rate times pre-tax subtotal.
- Applying the rate to the gross total pays affiliates a cut of sales tax or VAT you only pass through, so you lose money on every taxable order.
- Every provider reports a different field (Polar
net_amount, Stripeamount_total, Paddledetails.totals.subtotal), so normalize to a pre-tax base before multiplying. - Store the base and the rate next to each conversion, because six months later the only thing that settles a dispute is the number you saved.
What commission basis actually means
A commission has three parts, and programs usually publish only two. There is the rate (30%), the attribution rule (which affiliate owns the customer, for how long), and the basis (what amount the rate applies to). The third one is where trust goes to die, because it is invisible on the pricing page and only shows up when an affiliate compares their payout to a customer invoice.
It matters because orders are not single numbers. An order has a list price, a discount, a tax line, sometimes a credit, and later maybe a partial refund. Pick any two of those and you get a different payout from the same sale. A basis is simply a decision about which point in that sequence you consider to be "the revenue".
There is no universal right answer, but there are wrong ones. Paying commission on money you never keep is wrong in a way that compounds quietly, month after month, and it is the mistake I see most often when someone says their affiliate costs "do not match the invoice". If you are still deciding the rate itself, the right affiliate commission rate for SaaS covers how to size it against margin; this post assumes the rate is already set and asks what it multiplies.
The four numbers on every order
Take a single annual order and write down every number it passes through.
| Line on the order | Example | What it represents | Belongs in the base? |
|---|---|---|---|
| List price | $99.00 | Published price before any deal | No |
| Discount (30%) | -$29.70 | Margin the affiliate already gave away | No |
| Subtotal after discount | $69.30 | What your product actually sold for | Yes |
| Tax or VAT (20%) | +$13.86 | Collected for a tax authority, not for you | No |
| Total charged | $83.16 | What the card was charged | No |
| Refund (later) | -$83.16 | Money returned, commission must follow | Reverses the base |
| Commission base | $69.30 | The one number the rate applies to | This is the answer |
Read the table as a filtering exercise: you are looking for the line that represents value your business keeps. That line is almost always the subtotal after discount and before tax. Everything above it is someone else's money or someone else's margin, and everything below it is a reversal.
Gross means the total charged. Net usually means the total minus tax, which is the subtotal. The confusion starts because some tools say net when they mean something else entirely, which is the next two sections.
Tax is not your revenue
Sales tax, VAT, and GST are pass-through money. You collect them, you hold them, and then you send them to an authority. In a merchant-of-record setup like Paddle, you never really hold them at all: Paddle calculates and remits tax as the seller, and pays you the remainder.
Paying commission on the gross total means paying an affiliate a cut of that pass-through. At a 30% rate and 20% VAT, the affiliate earns 6% of the order value on money that was never yours. On a $83.16 order that is $4.15 per sale handed out for nothing, and it grows with both the tax rate and the rate you pay.
The same logic runs backwards on refunds. If a customer gets a full refund, tax goes back too, and a commission computed on gross will overpay by the tax slice even after a "full" clawback that used the wrong base.
This is also why tax paperwork and commission paperwork should agree. If your 1099-NEC or W-8BEN reporting is built from the same conversion rows as your payouts, a tax-inclusive base inflates reported income and makes year-end reconciliation harder than it needs to be. Affiliate tax forms without the headache covers the reporting side.
Discounts: pay on what the customer paid
Discounts are the other half of the base question, and they are less controversial once you say them out loud: an affiliate who hands out a 30% coupon has already spent 30% of your margin to make the sale. Charging the commission to the list price spends the commission budget on margin that no longer exists.
Run the numbers on the same $99 annual plan. Paying 30% of the list price is $29.70. Paying 30% of the $69.30 actually collected is $20.79. The second number is a 30% commission; the first is an effective 42.9% of revenue, which is a completely different deal from the one on your affiliate page.
There is one legitimate reason to use list price: commission that stays stable when a discount changes, which makes forecasting easier and avoids arguments about whether a coupon was "the affiliate's". That convenience has a real price, and it should be a deliberate choice written in the terms, not an accident of which field your provider sends first.
Stacked discounts are where this gets ugly. A launch code plus an affiliate code plus an annual discount can take a $99 plan to $40. If your base is list price, you pay $29.70 on $40 of revenue and lose money on the customer. If you change your pricing or promo structure often, read changing prices without breaking affiliate commissions before promising a fixed base.
What each provider actually sends you
This is the part that decides whether your base is right in practice, because you can only multiply the number you receive. The three main providers describe a sale in three different vocabularies.
| Provider | Amount field | Tax | Discounts | Practical note |
|---|---|---|---|---|
| Polar | order.net_amount |
Excluded | Excluded | Preferred field; falls back to amount_total, then subtotal_amount |
| Stripe | Checkout amount_total, invoice amount_paid |
May include automatic tax | Excluded | Check billing_reason on renewals so the first invoice is not counted twice |
| Paddle | details.totals.subtotal |
Excluded | Excluded | Minor units sent as strings, convert before dividing |
| Generic webhook | Whatever the merchant sends | Unknown | Unknown | Merchant's job to send a pre-tax figure |
Polar is the easiest of the three to get right: net_amount is already the pre-tax, post-discount figure, which is exactly the base described above. Stripe is the one that trips people up, because amount_total on a Checkout Session is what the customer was charged, and with automatic tax enabled that includes tax. Paddle sits in the middle: the subtotal is pre-tax and post-discount, and because Paddle is the merchant of record, it is also the number that corresponds to what you are actually paid.
If your payouts never quite match the provider dashboard, the mismatch is usually one of these fields plus a rounding rule. Why affiliate commissions do not match Stripe goes deeper on the reconciliation side; here the point is narrower: normalize to a pre-tax amount before you multiply, and write down which field you normalized from.
Three meanings of net, and why the confusion is expensive
The word net is doing too much work in this conversation, and a basis described as "net" is not always the same basis twice.
Net of tax is a point-in-time figure: subtotal on this order, before tax. This is the one you want.
Net of refunds is a running figure: revenue kept after returns. It changes retroactively when a refund lands, so a commission computed on it will differ depending on the day you compute it.
Net revenue, in the accounting sense, is revenue minus returns, allowances, and discounts. It is a period concept for reporting, not a per-order concept for payouts.
Programs that say "we pay on net revenue" without picking one of these end up with affiliates and finance computing two different numbers from the same data, both defensible, neither matching. Pick net of tax and say so explicitly: "the pre-tax amount charged for the order, after discounts, excluding refunded amounts". That sentence resolves 90% of future arguments.
The remaining 10% are attribution questions rather than basis questions, such as whether a renewal belongs to the original affiliate. That split, owner versus amount, is the same split that makes plan changes tricky, and affiliate commissions on upgrades and downgrades covers the valuation side when the amount itself moves.
A base you can defend in one formula
The whole policy fits in a line:
commission = floor(pre_tax_amount_charged * rate / 100)
Pre-tax, after discount, in cents, rounded down to the cent. Rounding down matters more than it sounds: rounding up across thousands of orders is a small persistent overpay, and every payout system that disagrees with you will disagree in the same direction.
Apply it to the worked example. Annual plan at $99, a 30% coupon, and 20% VAT, paying a 30% rate:
- On list price: 9900 cents times 30% = $29.70 per order, which is $29.70 paid on $69.30 of revenue.
- On gross total: 8316 cents times 30% = $24.94 per order, $4.15 of which is commission on tax.
- On pre-tax subtotal: 6930 cents times 30% = $20.79 per order, and the math survives a discount change without anyone renegotiating.
Across 100 orders like that, the gross basis costs $415 more than the pre-tax basis, and the list-price basis costs $891 more. Neither is a rounding error. Both are invisible in a dashboard that only shows totals.

Refunds, chargebacks, and events that arrive out of order
Whatever base you pick, reversal has to use the same base. A refund of $83.16 on a gross-based commission reverses $24.94; on a pre-tax base it reverses $20.79 and the tax slice never entered the ledger. Mixing bases between the charge and the reversal leaves a residue on every refunded order.
Timing is the second trap. Webhooks are retried and reordered, so a refund event can arrive before the sale it refers to. Any system that can only reverse an existing commission will silently fail to reverse that one, and the affiliate keeps a commission on a sale that was refunded. A minimal fix is a tombstone: record the refunded order id when the sale has not landed yet, and reconcile when it does. When the refund beats the sale walks through that failure and what the fix looks like in code.
Idempotency is the third. Order events get retried, and without a uniqueness rule keyed on the provider's order id you will occasionally pay two commissions for one order. Cheap to add at the start, painful to unwind after a bad month.
Partial refunds deserve a sentence of their own: reverse the commission on the refunded amount only, not the whole order, and use the same pre-tax proportion. A 50% refund on a $83.16 order should reverse 50% of $20.79, not 50% of $24.94.
Writing the basis into your program terms
A basis only protects you if it is published. Five lines cover it:
- The base: pre-tax amount charged after discounts, excluding tax, shipping, and refunded amounts.
- The rate: the percentage, plus whether per-affiliate overrides exist and override the default.
- The rounding rule: down to the cent, per conversion.
- The reversal rule: refunds and chargebacks reverse commission on the refunded amount, using the same base.
- The change policy: what happens when you change the base, and which conversions the change applies to.
That is small enough to paste into an existing program terms page rather than commissioning a new one. The affiliate program terms template has a full structure if you need one, and the basis clause drops into it as written.
Changing the basis later is the awkward case. Tightening from gross to pre-tax is a pay cut for every affiliate, even though you are correcting an error. Applying it only to conversions after a dated announcement, with 30 days of notice and a note in your changelog, keeps the change defensible. Retroactive recalculation of already-paid commissions is how programs lose their best affiliates in a single afternoon.
Auditing a year of commissions in one afternoon
You do not need to rebuild anything to find out whether your base is right. Pull 20 orders from the provider dashboard, at random, across months.
Recompute each one by hand from the provider's own numbers: subtotal, discount, tax, total. Compare to the stored conversion. Then look for four patterns.
- Stored amount is larger than the provider subtotal: you are paying on tax or on list price.
- Stored amount matches the pre-refund total on refunded orders: reversals are not firing.
- Two conversions with the same provider order id: missing idempotency.
- A conversion with no matching invoice: hand-recorded sale, or a webhook that fired on a pending payment.
Twenty orders is enough to see whether the basis is pre-tax or not, because the error is systematic rather than random: every taxable order carries it. If a full export is more your speed, the CSV route covers the same ground at once; in Sled that is the Export CSV button on the conversions page, which hits the same rows the dashboard reads, amount column included.

FAQ
Should affiliate commission be calculated before or after tax?
Before tax. Tax is collected on behalf of an authority and never becomes your revenue, so paying a percentage of it means paying commission on money you pass through. Use the pre-tax subtotal, after discounts, and state that in your terms so nobody has to guess.
What is the difference between gross and net commission for affiliates?
Gross commission applies the rate to the full amount charged, including tax. Net commission applies it to the pre-tax amount after discounts. On a $83.16 order with $13.86 of tax at a 30% rate, the difference is $4.15 per order, and it accumulates on every taxable sale.
Do affiliates get commission on discounted sales?
Yes, on the discounted amount, unless your terms say otherwise. An affiliate coupon already reduces your margin, so paying commission on the list price means paying on revenue you never collected. If you want list-price commission for simplicity, publish it as a deliberate policy rather than letting it happen by default.
How do Polar, Stripe, and Paddle report the amount to use?
Polar sends net_amount, which is already pre-tax and post-discount. Paddle sends details.totals.subtotal, pre-tax and post-discount, in minor units as strings. Stripe sends amount_total on Checkout Sessions and amount_paid on invoices, both of which can include automatic tax, so subtract the tax component before applying your rate.
The basis is one line in your terms and a decision in your webhook handler, and it is the difference between a program that reconciles and one that argues. Sled stores the amount it used for every conversion and shows the rate next to it, so the base is a stored fact rather than a reconstruction; start a free trial and check the first order yourself, or read why affiliate commissions do not match Stripe first.