Commission Agreement Template for SaaS: Free & Editable

You've probably been here already. A partner sends you a customer, the customer picks an annual plan, then upgrades mid-cycle, asks for a refund, or churns before renewal. Suddenly the “simple” commission deal you tracked in a spreadsheet isn't simple at all.

That's where most SaaS teams get into trouble. They launch an affiliate or referral program fast, promise a percentage, and assume they'll sort out the details later. Later is when finance asks what counts as earned revenue, support asks who owns disputed referrals, and the partner asks why this month's payout is lower than last month's.

A solid commission agreement template fixes that before it becomes a relationship problem. In SaaS, this isn't just legal housekeeping. It's how you define recurring revenue logic, payout triggers, refund handling, attribution windows, and what happens when software data and human expectations don't match.

Why Your SaaS Needs a Rock-Solid Commission Agreement

A partner sends you a deal in January. By March, the customer has switched plans, applied a discount, missed a payment, and asked support for a credit. By April, the partner wants to know why their commission report no longer matches the number they expected.

That situation is normal in SaaS. The problem is not the edge case itself. The problem is running the program without written rules for how commission is earned, tracked, adjusted, and paid.

A commission agreement matters because subscription revenue keeps changing after the initial sale. In a one-time transaction, the payout question is usually simple. In SaaS, a single referral can create months of follow-up decisions around renewals, upgrades, downgrades, failed charges, refunds, and churn. If the contract only states a percentage, finance has to fill in the rest later. That usually means inconsistent decisions, partner frustration, and extra legal review after the relationship is already under pressure.

Informal programs break under recurring revenue

A spreadsheet can carry a small partner program for a while. It stops working once billing logic gets more complicated than “closed deal times rate.”

The weak points show up fast:

• Commission trigger is undefined: Is the payout based on signup, first collected payment, activation, or the end of the refund period?
• Attribution rules are incomplete: If an affiliate link assisted the deal but sales closed it, which channel gets credit?
• Revenue adjustments are missing: How do refunds, chargebacks, credits, taxes, and discounts affect the commission base?
• Post-termination payments are unclear: Does the partner keep earning on existing accounts, and if so, for how long?
• System records do not control disputes: If your app, Stripe, and CRM disagree, which record governs the payout?

Those are not drafting details. They are operating rules.

Teams that treat affiliate and referral partnerships as a real acquisition channel need agreements that match how the business bills and reports revenue. If you are still deciding whether this channel fits your growth model, this overview of why affiliate marketing is a useful growth channel gives the business context. Once you launch, the agreement has to do more than sound formal. It has to hold up when software events and partner expectations stop lining up.

Clear terms make the program easier to run

Good partners care about rate, but experienced partners care just as much about definitions. They want to know what counts as a qualified referral, when a commission becomes payable, what can reduce it, and how disputes get resolved. Serious operators ask these questions early because they have already seen messy programs before.

This is also where SaaS teams save real time. A clear agreement reduces custom exceptions, shortens payout reviews, and gives support, finance, and partnerships one shared rulebook. It also makes your affiliate software easier to configure because the contract tells you what the platform should enforce.

For the legal drafting itself, Kons Law's guide to business contracts for professionals is a useful reference. The commercial terms still need to be specific to your pricing model, billing system, and partner motion.

Friendly relationships help. Clear agreements keep those relationships intact when money gets complicated.

Your Free Commission Agreement Template

Start with a template you can edit, not a generic PDF that locks you into someone else's assumptions. For a working base document, use this affiliate agreement template. It gives you a practical starting point for defining parties, commission mechanics, payment terms, and termination language.

If you want a broader legal drafting refresher before editing the template, Kons Law's guide to business contracts for professionals is worth keeping open in another tab. It's helpful for founders who know the commercial deal but need a cleaner way to express it in contract language.

Base template text

Use this as a starting draft and customize it to match your pricing model, billing system, and partner type.

Commission Agreement

This Commission Agreement is entered into by and between [Company Name] and [Partner Name] as of [Effective Date].

1. Appointment
Company appoints Partner on a non-exclusive basis to promote and refer prospective customers for Company's products or services.

2. Commission Structure
Partner will earn commission as described in Schedule A. Schedule A must define the commission basis, qualifying events, exclusions, and payout timing.

3. Qualified Transactions
Commission is payable only on transactions that meet Company's qualification rules, including valid attribution, successful payment collection, and compliance with program policies.

4. Payment Terms
Company will issue commission payments on the schedule stated in Schedule A, subject to any applicable holding period for refunds, chargebacks, or verification.

5. Taxes and Status
Partner is responsible for its own taxes unless applicable law requires otherwise. Partner acts as an independent contractor and not as an employee, agent, or joint venturer of Company.

6. Confidentiality
Partner will protect Company confidential information and use it only for purposes of this agreement.

7. Term and Termination
This agreement begins on the Effective Date and continues until terminated by either party under the notice terms stated herein.

8. Post-Termination Rights
Any post-termination commission rights must be expressly stated in Schedule A. If not stated, no ongoing commission accrues after termination.

9. Disputes
The parties will follow the dispute procedure stated in this agreement and the governing law clause.

10. Entire Agreement
This agreement and attached schedules form the full understanding between the parties.

Don't treat the template as final

A template is only the shell. The core work sits in the schedule that defines commission logic. That's where you specify recurring versus one-time payouts, whether discounts reduce commissionable revenue, how refunds are handled, and what evidence controls attribution.

If your product sells subscriptions, annual prepay plans, add-ons, or usage-based upgrades, generic wording won't be enough. You need language that mirrors how your billing system behaves.

Core Clauses Explained for Every Commission Agreement

A partner sends five customers in month one. Your dashboard shows five conversions, Stripe shows four successful payments, one customer cancels inside the refund window, and finance asks a simple question: what do we owe?

That answer should come from the agreement, not from a Slack thread.

A usable commission agreement template translates your program rules into terms that legal, finance, and partner managers can all apply the same way. In SaaS, that means the clauses must match how attribution, billing, renewals, and reversals work inside your systems.

Parties and scope

What it is: The clause that names the parties and defines the relationship.

Avoidable complications often begin with discrepancies. If the agreement names an individual but payments go to a registered business, you create tax and documentation problems. If you call someone a referral partner but the agreement gives them reseller authority, you create commercial and legal confusion.

Spell out three things clearly:

• Legal identity: Full legal name of the company and the partner entity.
• Program role: Affiliate, referral partner, reseller, independent contractor, or agent.
• Permitted conduct: What channels and methods are allowed, restricted, or banned.

For SaaS programs, this clause should also state whether the partner can use paid search on branded terms, coupon sites, email promotions, or sub-affiliate networks. Those are not minor marketing details. They directly affect attribution quality, margin, and brand risk.

Commission basis and earning trigger

What it is: The clause that defines what gets commissioned and the event that creates commission eligibility.

This is the financial engine of the agreement. If the language is loose, every disputed payout will start here.

Define the commission basis in concrete terms. Use net subscription revenue, gross contract value, flat fees per qualified account, or another metric that finance can verify from system records. Then define the earning trigger with the same level of precision. Contract signature, first successful payment, completion of onboarding, or some other event.

In SaaS, "earned" and "payable" should usually be separate. A partner may earn credit when a referred account becomes a paying customer, but payment may not go out until funds clear, fraud checks pass, and the refund window closes.

A practical test helps. If your finance lead and your affiliate manager would calculate different numbers from the same clause, the wording is not finished.

Payment timing and adjustments

What it is: The clause that governs when payment happens and what can change the amount.

This section should answer routine payout questions before they turn into support tickets. State the payout cadence, payment method, currency, minimum threshold, and whether fees or taxes reduce the amount sent.

Then deal with adjustments directly. SaaS programs see a steady stream of events that affect commissionable revenue:

• Refunds
• Chargebacks
• Discounts and promo credits
• Partial payments
• Failed renewals
• Downgrades
• Canceled annual plans with prorated returns

If you may need to reverse or offset commissions after one of those events, document the logic for recovering commissions in plain language. A short definition of commission reversal and recovery terms helps, but the agreement still needs the exact rule. State whether the amount is netted from future payouts, invoiced back, or adjusted only within a defined time period.

This clause should also identify the source of truth. In practice, that is usually your billing platform and partner tracking software, not a partner spreadsheet.

Term, termination, and post-termination effects

What it is: The clause that explains when the agreement starts, how it can end, and what happens to open or existing accounts.

Generic templates often stop at notice periods. That is not enough for subscription businesses. The expensive question is what happens to customers the partner already referred.

Write this part with real operating scenarios in mind. If a partner is terminated for fraud, you probably do not want ongoing commission rights. If a good partner leaves voluntarily, you may choose to continue paying on existing accounts for a limited period. Both outcomes are defensible. Problems start when the agreement says nothing.

The cleanest approach is to state the rule for each category:

Issue	Weak wording	Better clause
Existing referred accounts	“Commissions end at termination”	State whether existing customers continue to generate commission, and for how long
Material breach	“Company may terminate immediately”	Define the conduct that counts as breach
Notice	“Reasonable notice”	State the notice method and exact number of days
Pending payouts	Not addressed	Explain whether approved but unpaid commissions are still paid
Surviving obligations	Not addressed	List confidentiality, payment reconciliation, audit rights, and dispute provisions that continue

This is one place where trade-offs matter. A generous post-termination tail can help recruit strong partners. It also creates a long payment obligation that finance has to track.

Confidentiality, contractor status, and disputes

What it is: The legal framework around the money terms.

Partners often get access to conversion data, pricing, roadmap details, and internal reporting through your partner portal. Confidentiality terms should cover that information and limit how it can be used.

Independent contractor language matters for a different reason. You want the agreement to reflect the actual relationship. The company does not control working hours, employment benefits, or day-to-day supervision. The partner is responsible for its own taxes and business operations unless local law says otherwise.

Dispute language should be practical, not theatrical. State the governing law, venue or arbitration process, notice requirements, and any deadline for raising payout disputes. In partner programs, a simple rule works well: require disputes to be raised within a defined period after the payout statement is issued, and identify the records that control if numbers do not match.

Plain language wins here. If a clause sounds polished but no one on your ops team can apply it, it will fail the first time a partner challenges a payout.

Advanced Commission Structures for SaaS and Affiliates

A partner sends you ten paying customers in January. By March, two have upgraded, one has churned, one has come back on a different plan, and finance is asking whether the recruiter above that partner still gets an override. If your commission agreement only says "20% per sale," your software, your ops team, and your partner will all read that sentence differently.

That is the problem with generic templates. They are built for one-time transactions. SaaS programs run on recurring revenue, billing events, churn, attribution windows, and partner data flowing through tracking software.

The agreement has to match how commissions are calculated in your CRM, billing system, and affiliate platform. If the contract says one thing and the system pays another, you have created a dispute by design.

Recurring revenue needs precise boundaries

Recurring commission models can be excellent for SaaS because they push partners toward customers who stay, expand, and pay on time. They also create more edge cases than almost any other structure.

Spell out whether commission applies to:

• Initial subscription only
• Every renewal
• Renewals for a fixed period
• Upgrades and seat expansions
• Add-ons but not services
• Net revenue after credits and discounts

The phrase that causes the most trouble is "lifetime recurring commission." In practice, "lifetime" can mean the customer relationship, the subscription term, the partner relationship, or the life of the program itself. A good agreement removes that ambiguity and ties payout to a defined revenue event, usually collected subscription revenue, for a stated period.

That trade-off matters. Broad recurring rights help recruit ambitious affiliates. They also increase payout liability, reconciliation work, and the odds of arguments when a customer downgrades or returns after churn.

Tiered and performance-based models need trigger logic

Tiered rates work well when you want to reward stronger partners without raising commission for everyone. But the trigger cannot be vague. The contract should say exactly what moves a partner from one tier to the next and when that status takes effect.

Here's a useful walkthrough before you go deeper into setup details, especially if you're building a networked partner model with multi-tier commission structures for affiliate programs.

Use metrics your systems can verify. Common examples include cumulative collected revenue, number of active paying accounts, retained customers after a hold period, or contract value above a stated threshold. If the system cannot measure it cleanly, do not turn it into an automatic payment right.

The same rule applies to bonuses. A clause that promises extra commission for "high-quality customers" is asking for a dispute. Define quality using hard criteria such as retained subscription months, payment status, plan type, or expansion revenue within a set period.

If an incentive cannot be audited from CRM, billing, or affiliate data, it should not appear in the agreement as an automatic entitlement.

Multi-tier payouts create upstream risk

Multi-tier models add another layer of exposure because one customer event can trigger payouts to more than one partner. That structure can drive program growth, but only if the agreement answers the operational questions upfront.

Start with the trigger chain:

• What event places a partner under an upstream sponsor
• When does the upstream commission begin
• Which transactions qualify for the override
• Whether refunds, chargebacks, and fraud reversals flow through every level
• Whether the upstream payout survives suspension or termination of the downstream partner

These points sound technical because they are technical. In SaaS, the payment logic often sits inside partner software while the legal obligation sits inside the agreement. Those two pieces need to line up. Otherwise you end up manually fixing payouts, making one-off exceptions, and teaching partners to challenge every statement.

The best advanced commission structures are not the most creative ones. They are the ones your team can calculate, audit, and defend without rewriting the rules every quarter.

Putting It All Together Filled Agreement Examples

The easiest way to test a commission agreement template is to fill it with realistic language and see whether someone outside the growth team can understand it.

Example one with simple recurring commission

A straightforward SaaS affiliate setup might use language like this:

Commission Rate
Partner will earn a recurring commission equal to 20% of collected subscription revenue from each Qualified Customer referred by Partner.

Qualified Customer
A Qualified Customer is a new customer not previously in Company's sales pipeline or customer database, who purchases through Partner's tracked referral link and completes a successful payment.

Payment Timing
Commissions are payable monthly for transactions collected in the prior payout cycle, after any applicable refund hold.

Exclusions
No commission is payable on taxes, credits, refunds, chargebacks, implementation services, or non-subscription fees.

This works because every important term is anchored to something observable. “Collected subscription revenue” is much better than “sales revenue.” “New customer” is better than “customer.” Exclusions are in the clause itself, not buried in email.

Example two with annual plans and a clawback window

Now take a more complex structure for a SaaS company selling annual plans through affiliates and strategic partners:

Commission Structure
Partner will earn commission on annual subscription plans based on collected net subscription revenue.
Tier 1 applies to standard qualified sales. Tier 2 applies once Partner reaches the threshold stated in Schedule A.
Company may pay additional performance bonuses where the conditions in Schedule A are satisfied.

Hold and Reversal
Commission on annual plans is not payable until the holding period in Schedule A expires. If a customer receives a refund, chargeback, billing reversal, or account credit tied to the qualifying transaction, Company may reduce future payouts by the related commission amount.

Attribution
Attribution will be based on Company's recorded referral and billing data. In the event of conflicting records, Company's system data will govern unless Partner provides contrary written evidence.

This language does three useful things. It separates qualification from payout. It makes reversals explicit. It defines which system controls in a dispute.

What good examples have in common

Good agreement language usually has these traits:

• It names the data source: billing data, referral tracking, CRM record, or signed order.
• It distinguishes earned from payable: those are not always the same thing.
• It handles failure modes: refunds, duplicate accounts, disputed attribution, and terminations.

If your filled example still requires a verbal explanation, keep editing.

Navigating Legal and Tax Compliance

A partner closes a deal, the customer pays, and finance is ready to issue commission. Then the problems start. The payee name does not match the signed entity. No tax form is on file. The partner wants payout to a different country than the one in the contract. What looked like a routine payment turns into a legal and accounting exception.

That is why the agreement needs to do more than describe a percentage. In SaaS, it also has to match how your billing system, partner platform, and finance process work. Recurring revenue creates edge cases that generic legal forms often miss, especially around renewals, reversals, tax treatment, and partner access to customer data.

Contractor versus employee classification

Calling someone an affiliate, reseller, or partner does not settle classification. Regulators look at the working relationship. If your team controls the person's hours, reviews day-to-day activity, requires specific methods, or folds them into normal operations, contractor language in the contract will not save you.

The agreement should state independent contractor status clearly. Your operating model has to support that position too. I have seen SaaS teams create avoidable risk by treating top-performing partners like part-time employees while still paying them as contractors. That usually becomes expensive when tax withholding, benefits, or labor rules get reviewed later.

For Australian readers, EndureGo's explanation of ATO rules for personal services income is a practical reference when contractor classification starts affecting tax treatment.

Tax forms, invoices, and cross-border payouts

Cross-border programs break when basic paperwork is vague. Your agreement should say who handles taxes, whether the partner must submit invoices, what documents are required before first payout, and whether the company can hold payment until those items are complete.

A few details matter more than founders expect:

• Tax documentation: define what must be collected before any payout is approved.
• Invoice rules: state whether invoices are required, what they must include, and when they are due.
• Indirect taxes: clarify how VAT, GST, sales tax, or similar charges are handled.
• Currency and transfer fees: say which party absorbs conversion spreads, bank charges, or payout platform fees.
• Payee verification: require the legal entity name, tax details, and payout account to match.

This is not paperwork for its own sake. It prevents disputes, failed payouts, and messy quarter-end reconciliations.

Privacy, marketing conduct, and data access

SaaS partner programs often expose more data than companies realize. A dashboard may show account status, plan type, renewal timing, coupon use, or referral events. Even when that data looks harmless, it can create privacy obligations if a person can be identified directly or indirectly.

The agreement should spell out what partners may collect, what they may see, and what they are prohibited from storing or sharing. If partners run paid ads, use tracking links, build landing pages, or capture leads, assign responsibility for compliance with privacy, consent, and advertising rules. If they only receive aggregate reporting, say that plainly. If they never get customer-level personal data, write that down too.

Generic forms often skip this part. In SaaS, that is a mistake. Your actual risk sits in the software workflow as much as in the legal language.

Keep legal terms aligned with recurring revenue mechanics

Recurring commissions create tax and compliance questions that one-time sales models do not. Revenue can churn. Payments can fail on renewal. Credits may be issued months after the original sale. If your agreement is vague on when commission is earned versus when it is payable, finance has to improvise.

State the trigger with precision. Use the billing event your systems can verify. Then tie payout timing, reversals, and recordkeeping to that event. That makes legal review easier because counsel can assess a real operating model instead of cleaning up loose commercial terms after the program is live.

Managing Payouts and Program Operations

Month-end is where weak commission agreements break. An affiliate expects payment on every signup in the dashboard. Finance only wants to pay on cash collected. Support is stuck explaining why two numbers that looked identical all month suddenly diverged. In SaaS, that gap usually comes from one problem. The contract, billing system, and partner-facing reporting were never aligned closely enough.

The operational job is simple to describe and hard to execute. Every commission rule in the agreement needs a matching system event, approval step, and payout record. If one part is vague, the disputes show up later around renewals, failed charges, downgrades, refunds, and duplicate accounts.

Build operations around a clear payment trigger

Start with the event that makes commission payable. Use something your team can verify in the billing stack, not a soft milestone like form completion or trial signup unless the program is intentionally paying for those actions.

For SaaS, the cleanest trigger is usually a successful collected payment after any hold period you set for refunds or fraud review. That could be a Stripe charge captured successfully, a settled Paddle payment, or another confirmed billing event your finance team can audit. The point is consistency. If the agreement says commission is earned on collected revenue, the dashboard cannot show unqualified earnings at checkout and expect partners to interpret the fine print correctly.

A workable payout flow usually looks like this:

1. Capture attribution at signup through referral links, partner IDs, or approved coupon codes.
2. Confirm the billable event in the payment system.
3. Apply program rules for refunds, credits, chargebacks, self-referrals, fraud flags, and duplicate accounts.
4. Lock the approved commission amount for the payout cycle.
5. Send payment and a supporting statement so the partner can reconcile each line item.

Use tools that match the agreement

Manual payouts can work early on. They fail once volume increases or when recurring revenue creates too many edge cases to track in a spreadsheet. The issue is not speed alone. It is auditability.

Your team needs a ledger that answers basic questions without debate. Which customer triggered the commission. Which plan counted. Whether the payment cleared. Whether a later refund reversed it. Whether the account renewed under the original attribution window. If a partner has to ask finance for all of that, the program is already too opaque.

Useful program infrastructure includes:

• Billing integrations that expose the exact payment status used to approve commissions
• Partner reporting that separates pending, approved, reversed, and paid amounts
• Exportable payout records for finance and tax documentation
• Exception queues for refunds, disputed charges, plan changes, and suspected abuse

Refgrow is one example of software used for embedded SaaS referral and affiliate operations. The brand matters less than the setup. Choose tooling that applies the same attribution, approval, and reversal logic described in the agreement.

Give partners enough visibility to reduce disputes

Partners do not need every internal finance detail. They do need enough visibility to understand why they were paid, why something is still pending, and why a commission was reversed. In practice, that means clear status labels, payment history, and transaction-level explanations for exceptions.

This reduces support load, but the bigger benefit is trust. Affiliate relationships tend to break on confusion before they break on economics. If the contract says one thing, the dashboard suggests another, and the remittance file says something else again, the partner will assume the program is being managed inconsistently.

The best operating standard is straightforward. The agreement defines the rule. The software applies the rule. The payout report shows the result. When those three match, recurring commissions are manageable even as the program grows.

Commission Program Pre-Launch Checklist

Before launch, run one final pass. Most bad commission programs don't fail because the strategy was wrong. They fail because the setup was incomplete.

Use this checklist:

• Finalize the agreement draft: Confirm commission basis, earning trigger, payout timing, exclusions, and termination effects are explicit.
• Get legal review: Especially if you have cross-border partners, recurring commissions, or multi-tier logic.
• Match system behavior to contract terms: Make sure your billing and affiliate tools calculate commissions the same way the agreement describes them.
• Set payout operations: Decide cadence, payment rail, approval owner, and reconciliation process.
• Prepare partner onboarding: Give affiliates a short explanation of attribution, payout timing, prohibited conduct, and where they can see performance data.
• Test edge cases: Run sample scenarios for refunds, annual plans, discounts, duplicate referrals, and post-termination accounts.

If you can't answer “what happens” for each edge case before launch, a partner will ask after launch.

Frequently Asked Questions About Commission Agreements

A typical SaaS dispute starts the same way. A partner expects commission on an account that upgraded, churned, then returned six months later, and the agreement never said whether that revenue still counts.

That is why FAQ-level questions matter. In affiliate and referral programs, small drafting gaps turn into payment disputes, margin leakage, and partner distrust.

Can you change a commission agreement after it's signed

Usually yes, if the agreement says how changes are made. The clean approach is a written amendment, updated schedule, or new program terms that require clear acceptance.

In SaaS, this matters most when you change payout rates, attribution windows, or eligibility rules. If the contract allows unilateral updates, use that power carefully. It may be legally permitted in some cases, but it can still damage partner retention if the change cuts expected earnings.

What's the difference between a referral program and an affiliate program

Referral programs usually involve customers, users, or close industry contacts making occasional introductions. Affiliate programs usually involve publishers, creators, agencies, or other partners promoting repeatedly and expecting formal tracking, reporting, and payout workflows.

The difference is operational, not just marketing. Referral terms can stay fairly simple if the relationship is low volume. Affiliate terms usually need tighter language around attribution, spam rules, brand use, coupon abuse, and software-based tracking because those programs create more edge cases.

Do you always need a written agreement

No law forces every commission relationship into a signed contract. That said, running a SaaS program without written terms is asking for disputes.

Recurring billing creates questions a verbal agreement will not answer cleanly. What happens after a downgrade? Does a refund claw back prior earnings? Does commission continue after termination for customers referred before the end date? Written terms keep those questions from becoming finance problems later.

When should you ask a lawyer to review it

Get legal review before launch if the program includes recurring commissions, cross-border partners, multi-tier payouts, performance bonuses, regulated industries, or any setup where a contractor could start looking like an employee.

I also recommend legal review when partners get access to customer data, admin access, or co-selling rights. At that point, the agreement is doing more than defining payout. It is allocating risk.

A starting template saves time only if it matches how your billing system, CRM, and partner software function. As noted earlier, Refgrow helps SaaS companies run embedded affiliate and referral programs with in-app tracking, automated commission workflows, and partner-facing dashboards.