How do affiliate commissions work with per-seat SaaS pricing?
Short answer: Decide whether an affiliate earns on the initial subscription, eligible seat expansion, renewals, or all three. Calculate commission on eligible collected amounts, not simply changes to the number of users. An added seat is normally an expansion of an existing customer relationship, not another customer acquisition.
Stripe documents a per-seat model through a subscription item's quantity. Paddle Billing allows quantity changes and proration choices. Neither billing event determines your affiliate contract automatically.
Choose the commission policy
| Policy | Eligible event | Risk to control |
|---|---|---|
| First-payment bounty | First qualifying paid transaction | A second seat purchase must not create another customer bounty |
| Expansion commission | Collected incremental seat charge | Do not pay on the same proration twice |
| Recurring share | Each eligible paid renewal during the agreed term | Refunds, duration limits and reduced quantities |
| Hybrid | One bounty plus specified expansion revenue | Keep separate ledger categories and caps |
Publish the commission duration, eligible product lines, refund treatment, exclusions and expansion rules in partner terms. Verify that the chosen tracking platform supports invoice-level quantity changes; recurring-commission support does not necessarily include seat proration.
Worked example: five seats added mid-cycle
Suppose a SaaS customer already pays for 10 seats at $20 each per month. Fifteen days into a hypothetical 30-day billing cycle, the customer increases to 15 seats. Under a simple half-month proration, the incremental charge is 5 × $20 × 15/30 = $50 before tax, discount and rounding. If the contract makes seat expansion eligible for a 15% commission, the incremental commission is $7.50 after successful collection.
The next full monthly invoice is 15 × $20 = $300. Under a 15% recurring-revenue-share policy the eligible commission could be $45. Under an initial-sale-only bounty it is $0. These examples illustrate different contractual models, not a vendor's default payout behavior. Use actual settled invoice amounts: billing processors can prorate differently depending on timing and configuration.
Keep invoice-line keys and partner ownership together
A robust ledger stores merchant customer ID, subscription ID, invoice ID, line ID, quantity, price ID, partner attribution ID, policy version and payout state. Use the invoice line plus commission policy version as an idempotency key. When webhook retries arrive, update the original record rather than creating another commission.
- Record the approved referring partner when the first paid account qualifies.
- On successful collection, identify seat-related line items and exclude noncommissionable products and taxes.
- Apply the approved rate to the eligible collected net amount; do not treat every quantity change as a second referral.
- Mark the commission pending during the published approval period.
- On refund or credit note, create a traceable negative adjustment linked to the original line.
- Reconcile total payable commission to the merchant's retained revenue.
Review our multiple-subscription attribution guide for accounts with more than one contract, and Stripe plan-change attribution for changes to the plan itself.
Handle downgrades, annual billing and credits
A reduction in seats might affect future renewals without reversing a valid historical payment. If the merchant returns part of an already commissioned charge, calculate an adjustment under the written terms. Annual prepayment should use a defined acquisition or revenue-recognition rule rather than mechanically paying a fresh bounty per seat. A negotiated free seat is not collected revenue.
For enterprise contracts, store the approved commission base and exception reason. Avoid relying on estimated seat counts or CRM contract value when the program promises payment-based commissions. Separate partner-sourced account attribution from the financial amount eligible for commission.
Implementation acceptance checklist
- One initial customer purchase creates no more than one acquisition reward.
- A seat increase creates the correct incremental charge and, only when eligible, a separate commission.
- Webhook replay never doubles payouts.
- Seat decreases, refunds and disputed payments reconcile against prior entries.
- Partner reports show the billing period, approval state and eventual payout.
- Consent and financial-record handling match your disclosed policies.
Frequently asked questions
Is an added seat a new referral?
Usually not. It is expansion revenue, which may have its own commission rule.
Should commission use list price or net collected revenue?
Use the definition in the program agreement. Net eligible collected revenue is often easier to reconcile to actual payment activity.
Can prorations create a negative commission?
Yes, if a refund or credit reverses previously commissioned revenue and the agreement permits adjustments.
Sources and editorial disclosure
Official documentation checked 2 November 2026: Stripe per-seat pricing, Paddle quantity and proration, and Stripe subscription webhooks. Calculations and commission policies are illustrative, not claimed vendor defaults. SaaSAlways has not independently tested a merchant account.