How to Review a Revenue Sharing Agreement: a Clause-by-Clause Checklist

How do you review a revenue sharing agreement before you sign? Begin with the one definition that drives the whole deal: what counts as "revenue", and is the share taken from gross revenue or from net? Almost every dispute in a revenue sharing agreement comes from a loose revenue definition, or from a long list of deductions that quietly shrinks the base before your percentage is applied. So before you look at the percentage, pin down the number the percentage is multiplied by. A revenue sharing agreement is a contract where two or more parties agree to split the revenue from a product, service, venture or asset, rather than paying a fixed fee. It is common in partnerships, distribution, content and platform deals, joint ventures and affiliate-style arrangements. Reviewing one well means checking the revenue definition, the share, the deductions, how and when you get paid, your right to see the numbers, and what happens when the deal ends. This article is general guidance, not legal advice. Revenue sharing engages contract, tax and sometimes partnership law, which vary by jurisdiction, so have a qualified professional review one before you rely on it. ## The clause-by-clause review checklist 1. How is "revenue" defined? Is it gross receipts, or net of specified items? This is the base your percentage applies to, so it matters more than the percentage itself. Watch for broad phrases like "net revenue as determined by the Company".

2. What deductions are allowed before the split? List them: taxes, refunds, chargebacks, platform fees, discounts, cost of goods, marketing. Each deduction reduces your share. Insist the deductions be specific and capped, not open-ended.
3. What is the share, and is it fixed or tiered? Is it a flat percentage, or does it change with volume, time or milestones? Make sure the tiers and triggers are unambiguous.
4. When is revenue recognised? Is your share earned when the customer is invoiced, when they pay, or when the money clears? Recognition on payment, net of refunds, protects you from paying out on revenue that never arrives.
5. How and when are you paid? What is the calculation period (monthly, quarterly), the payment deadline after period end, the currency, and any minimum payout threshold? Long delays and high thresholds hold back your money.
6. Do you have audit and reporting rights? Will you receive a regular statement showing how your share was calculated, and can you audit the other party's records if you doubt the figures? Without an audit right, you have to take the numbers on trust.
7. Is there a minimum guarantee or a cap? Is there a floor (a minimum you receive regardless of revenue) or a ceiling (a cap on what you can earn)? Each shifts risk between the parties.
8. Exclusivity and scope. Does the deal tie you exclusively to this party, and is the revenue clearly limited to the defined product, territory or channel? Revenue from outside the defined scope should be excluded cleanly, in both directions.
9. Who owns the IP and the customer relationship? In content and product deals, confirm who owns the underlying intellectual property and the customer data, separately from the revenue split.
10. Term, termination and tail payments. How long does it run, how can it end, and do you keep receiving a share on revenue from customers or sales originated during the term after it ends? Tail rights can be worth more than the headline percentage.
11. Tax treatment. Who bears GST, and how is tax deducted at source (TDS) handled? Revenue sharing is not the same as a profit-sharing partnership, and getting the tax characterisation wrong is costly.
12. Dispute resolution and governing law. Which law governs, and how are disputes resolved? A clear audit-and-dispute path matters because revenue sharing disputes are usually about numbers. ## Red flags in a revenue sharing agreement - "Net revenue" is used but never fully defined, or is left to one party to determine.

• Deductions before the split are open-ended, so the base can be shrunk at will.
• You have no right to a regular statement and no right to audit the figures.
• Your share is recognised on invoicing but is not reversed when the customer refunds or does not pay.
• Payment is delayed far beyond the period end, or a high minimum threshold holds your money back.
• The term ends with no tail payment on revenue you originated.
• The tax treatment, especially GST and TDS, is left unaddressed.
• Exclusivity binds you, but revenue outside the defined scope is still swept in against you. ## How to protect your position The strongest protections are a tight revenue definition, a short and capped list of deductions, recognition on payment net of refunds, a regular statement as of right, and an audit right you can actually use (ideally with the other side paying the audit cost if an error above a threshold is found). If you originate customers or sales, negotiate a tail. And settle the tax treatment, GST and TDS, in the agreement rather than leaving it to argument later. Last verified October 2026. ## A note on jurisdiction In India a revenue sharing agreement is a contract under the Indian Contract Act, 1872. Two tax points matter. Goods and services tax (GST) can apply to the supply underlying the revenue, and the agreement should say who bears it and how it is invoiced. Tax deducted at source (TDS) under the Income-tax Act, 1961 may apply to payments between the parties, depending on how the arrangement is characterised, so the mechanism for deduction and credit should be clear. <!-- [VERIFY: applicable GST treatment and TDS section for the specific arrangement] --> A revenue sharing arrangement can also, depending on its terms, look like a partnership, which carries different legal and tax consequences, so the agreement should state clearly that it is not a partnership if that is the intention. In the UK, US, Ireland, Singapore and Australia the tax and characterisation rules differ, so treat "varies by jurisdiction" as the default and take local advice. Last verified October 2026. ## Where a contract workspace helps Reviewing a revenue sharing agreement is mostly tracing how a number is built: the revenue definition, the deductions, the recognition point and the reporting that lets you check it. The risk is rarely in one clause; it is in how the definition, the deductions and the audit right combine. What helps is keeping the review, the editing and the reporting-and-payment tracking for revenue sharing agreements in one AI workspace tuned to your deals, so how your share is calculated, and where the definition leaves you exposed, stays visible. Adira is built for that kind of work.