Revenue Sharing Agreement Template

In plain language: Identifies both parties by their full legal names and entity types, and briefly states the commercial purpose of the agreement.

Common mistake: Using trade names or brand names instead of registered legal entity names — this creates ambiguity about which entity is bound and can complicate enforcement.

In plain language: Precisely defines what counts as 'revenue' for sharing purposes — gross or net, which products or channels are included, and which deductions are permitted before calculating each party's share.

Common mistake: Defining revenue as 'gross revenue' without specifying permitted deductions — one party assumes refunds reduce the base while the other does not, generating disputes with every payment cycle.

In plain language: States each party's exact percentage entitlement, any tiered thresholds that change the split as revenue scales, and how the formula applies to each revenue category.

Common mistake: Using a single flat percentage without clarifying whether it applies to all revenue categories or only specific product lines, leading to under- or over-payment when multiple revenue streams exist.

In plain language: Sets out how often payments are made, the deadline after each period closes, the currency, and the accepted payment methods.

Common mistake: Failing to specify a payment deadline tied to a defined period-close date — 'promptly' and 'within a reasonable time' are routinely interpreted differently and invite late-payment disputes.

In plain language: Requires the paying party to provide regular revenue statements in a defined format and to maintain supporting records for a minimum period.

Common mistake: No reporting requirement at all — without contractual statements, the receiving party has no way to verify payments and cannot trigger audit rights effectively.

In plain language: Grants the receiving party the right to inspect the paying party's books and records to verify revenue figures, and specifies the audit process, notice requirements, and cost allocation.

Common mistake: Granting unlimited audit frequency without notice requirements — this exposes the paying party to disruptive, repeated audits and can destroy the commercial relationship.

In plain language: States the initial duration of the agreement, any automatic renewal terms, and the conditions and notice period under which either party may terminate — with or without cause.

Common mistake: Auto-renewal clauses with notice periods shorter than the payment cycle — a party can become locked into another full year before realizing the renewal window has closed.

In plain language: Clarifies that each party retains ownership of its pre-existing IP, governs any jointly developed assets, and requires both parties to keep financial terms and proprietary data confidential.

Common mistake: No confidentiality clause in a revenue-sharing deal — sharing payment data and revenue figures without protection exposes sensitive commercial terms to competitors or the market.

In plain language: Each party warrants it has authority to enter the agreement and that its contributions don't infringe third-party rights; the indemnification clause allocates liability for breaches of those warranties.

Common mistake: One-sided indemnification covering only the paying party's liability — if the revenue source infringes a third party's IP, both parties may face claims and the allocation of that risk should be explicit.

In plain language: Specifies which jurisdiction's law governs the agreement and whether disputes go to arbitration, mediation, or litigation — and in which venue.

Common mistake: Choosing a governing law with no connection to either party's location or the revenue-generating activity — courts in some jurisdictions will apply local law regardless, making the clause ineffective.

A revenue sharing agreement is a contract between two or more parties that defines how income generated by a specific product, channel, or initiative is calculated and divided. It covers the revenue definition, each party's percentage entitlement, payment timing, reporting obligations, audit rights, and term. It is used in partnerships, affiliate arrangements, content licensing, reseller deals, and co-developed product launches.

A revenue sharing agreement splits gross or net income before operating costs are deducted. A profit sharing agreement splits what remains after all agreed costs — salaries, overhead, marketing — have been subtracted. Revenue sharing is simpler to calculate and audit because it depends on fewer variables, but it means the paying party absorbs all operating costs before the split. Profit sharing is fairer when both parties contribute ongoing costs, but disputes over allowable deductions are more common.

Yes — a revenue sharing agreement is generally enforceable as a contract when it is signed by authorized representatives of both parties, contains clear terms for the revenue definition and payment obligations, and is supported by consideration (each party giving something of value). As with any commercial contract, enforceability depends on the jurisdiction and whether the terms meet local contract-law requirements. Consider having a lawyer review the agreement before signing, particularly for high-value or cross-border arrangements.

At minimum: parties and their legal entity names, a precise definition of shared revenue with permitted deductions, the sharing percentage or formula, payment schedule and currency, reporting requirements, audit rights with notice and frequency limits, IP ownership and confidentiality terms, term and termination conditions including cure periods, and governing law. Missing the revenue definition or audit rights are the two omissions most likely to generate disputes.

The percentage is negotiated based on each party's contribution — capital, technology, distribution reach, or customer relationships. Common structures include a flat split (e.g., 70/30), a tiered split that increases the receiving party's share as cumulative revenue crosses defined thresholds, or a sliding scale tied to performance metrics like conversion rate or customer lifetime value. There is no universal standard; the split should reflect the relative value each party provides to the deal.

Yes, if the agreement includes a termination clause — which it should. Most agreements permit termination for material breach after a defined cure period (typically 15–30 days), and may include a convenience termination right with advance notice (typically 30–90 days). Agreements without any termination provision can be difficult to exit before the fixed term expires, particularly if revenue underperforms. Always include a minimum-revenue threshold that triggers an exit right if the deal is not generating meaningful income.

Audit rights give the receiving party the contractual ability to inspect the paying party's books and records to verify that reported revenue figures are accurate. Without them, the receiving party must accept the paying party's statements at face value with no recourse if figures are understated. Best practice is to limit audits to once per year with 30 days' advance notice, and to shift the audit cost to the paying party if an underpayment exceeding 5% is confirmed.

Notarization is not required for a revenue sharing agreement to be enforceable in most jurisdictions. A signed agreement between authorized representatives is typically sufficient. However, if the agreement forms part of a larger transaction involving real property or certain regulated industries, notarization or additional formalities may be required. Using timestamped e-signatures and retaining the executed copy in a secure document vault is sufficient for most commercial arrangements.

Tax treatment varies by jurisdiction and the nature of the arrangement. In the US, revenue share payments to domestic parties are typically reportable on Form 1099-MISC if they exceed $600 annually. Cross-border payments may be subject to withholding tax under bilateral tax treaties. In the UK and EU, VAT implications depend on whether the payment constitutes consideration for a supply of services. Both parties should confirm the applicable tax treatment with an accountant before the first payment is made.