Establishing secure connection…Loading editor…Preparing document…

Revenue Sharing Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

REVENUE SHARING AGREEMENT

This Revenue Sharing Agreement (this “Agreement”), dated as of (the “Effective Date”) is entered into by and among , a German Aktiengesellschaft (“DBAG”), and , a Delaware limited liability company (“Affiliate” and together with DBAG, the “Parties”).

RECITALS

WHEREAS, DBAG is a stock corporation organized under the laws of Germany and is engaged in a wide range of banking and other financial activities;

WHEREAS, DBAG conducts some of its business activities through its New York Branch (“DBNY”) and other of its business activities through corporate subsidiaries organized under the laws of various States of the United States;

WHEREAS, Taunus Corporation, a Delaware corporation (“Taunus”), is the ultimate United States parent company of substantially all of DBAG’s United States subsidiaries (together with Taunus, the “Taunus Group”);

WHEREAS, Taunus is a bank holding company within the meaning of the U.S. Bank Holding Company Act of 1956, as amended, and is subject to regulatory oversight by the United States Federal Reserve System and the New York State Banking Department;

WHEREAS, certain regulatory developments pursuant to the “Basel II” rules would require Taunus to change the method with which it reports bank regulatory capital;

WHEREAS, certain regulatory developments pursuant to the proposed “Basel III” rules will affect the way regulators will measure a bank’s capital, which developments will require DBAG to take certain actions with respect to its United States banking operations conducted through DBNY;

WHEREAS, the Collins Amendment to the Dodd-Frank Wall Street Reform and Consumer Protection Act (“Dodd-Frank”) will require Taunus to take certain actions with respect to its ownership of DBAG’s United States banking chain in order to avoid certain adverse regulatory capital consequences;

WHEREAS, certain actions required to be taken by DBAG as a result of Dodd-Frank could result in further adverse affects to DBAG as a result of other bank regulatory developments;

WHEREAS, DBAG has concluded that certain of the adverse consequences resulting from compliance with Dodd-Frank and other regulatory developments would be mitigated by entering into transactions with Affiliate that would result in a tax grouping of DBNY and the Taunus Group as a single taxpayer for United States federal income tax and state and local tax purposes;

WHEREAS, DBAG has concluded that managing the DBNY business through a Regional Executive Committee would be advantageous for both business and regulatory purposes.

WHEREAS, the Parties are entering into this Agreement for the purpose of establishing their sharing of net profits and net losses with respect to, and in relation to their interests in, the business of DBNY; and

WHEREAS, simultaneously with the execution of this Agreement, the Parties have entered into the Operating Agreement (defined below), setting forth certain rights and obligations of DBAG and Affiliate with respect to the business of DBNY;

NOW, THEREFORE, in consideration of the mutual covenants and obligations set forth in this Agreement, the parties hereby agree as follows:

SECTION 1. Definitions. Capitalized terms not otherwise defined herein have the meaning set forth in this Section 1.

“Additional Investment Amount” has the meaning set forth in section 2(b).

“Affiliate Share” means Affiliate’s two (2) percentage interest in the Net Profits and Net Losses of DBNY.

“Assets” and “Liabilities” means the assets and liabilities of DBNY as reflected on the books and records established and maintained by DBAG for DBNY as of the Effective Date, including the assets and liabilities of the Consolidated Group. The Assets and Liabilities as of the Effective Date are set forth on the balance sheet and attached hereto as Exhibit B.

“Board” has the meaning set forth in the Operating Agreement.

“Cap” means eleven and one-half percent (11.5%) of the Investment Amount.

“Effective Date” means for all purposes December 31, 2011.

“Investment Amount” means at any time, the amount of Affiliate’s capital investment in DBNY, calculated as follows: the USD $385 million contributed by Affiliate to DBNY as set forth in section 2(a), increased by any and all Additional Investment Amounts described in section 2(b), and reduced, but not below zero, by any and all distributions from DBNY to Affiliate described in sections 3(b) and 3(d).

SECTION 2. Revenue Sharing.

(a) The Parties hereby agree that in exchange for the contribution by Affiliate of the Investment Amount to DBNY, and subject to the terms of this Agreement, Affiliate is hereby granted for each year during the Term an interest in the Net Profits equal to the Distribution Amount and an interest in Net Losses equal to the Loss Participation attributable to the business activities of DBNY from the Effective Date until the Termination Date, as more fully set forth below.

(b) In the event there is an increase during any year in Branch Equity, then Affiliate will contribute to DBNY an amount that is equal to the Affiliate Share multiplied by such increase (the “Additional Investment Amount”).

(c) The interest of Affiliate in the Net Losses of DBNY is not intended to and does not subject Affiliate to a share of the Net Losses of DBNY that, in the aggregate for all such Loss Years, exceed an amount equal to the Investment Amount (the “Loss Limitation Amount”).

(d) The parties hereby acknowledge that the interest in Net Profits and Net Losses acquired by Affiliate pursuant to this Section 2 does not represent an interest of a creditor in the assets of DBNY and that such interest is subordinate in all respects to all of the creditors of DBNY.

SECTION 3. Payments and Distributions.

(a) Affiliate will be entitled to receive, for any Profit Year, payments and distributions from DBNY equal to the Distribution Amount with respect to its interest in the Net Profits of DBNY for such year.

(b) Affiliate and DBAG each will be entitled to receive their respective pro rata shares of any Return of Capital in any year during which DBNY receives Dividends.

(c) On the Termination Date, Affiliate will be entitled to receive a payment from DBNY in an amount equal to the Liquidation Rights (the “Termination Payment”), plus the current year Profit Based Distribution, if any.

(d) In the event there is a decrease during a year in Branch Equity, then to the extent that the Liquidation Rights exceed zero, DBNY will distribute to Affiliate within sixty (60) days of such calculation an amount equal to the Excess Distribution for that year.

SECTION 4. Term. This Agreement will remain in effect until the Termination Date.

SECTION 5. Tax Treatment. The parties intend and agree that as a result of the transactions effected by this Agreement and the Operating Agreement DBNY will constitute a “business entity” for purposes of Treasury Regulation § 301.7701-1 et seq.

SECTION 6. No Agency Relationship. This Agreement does not purport to, and the Parties agree that it does not, establish an agency relationship between DBNY and Affiliate.

SECTION 7. Modifications and Waivers. No supplement, modification, waiver, or termination of this Agreement or any provision hereof shall be binding unless executed in writing by all parties hereto.

SECTION 8. Consent to Jurisdiction. By execution hereof, each party hereby consents to the non-exclusive jurisdiction of the courts of the State of New York with respect to any matter or action arising out of or in connection with this Agreement.

SECTION 9. Governing Law. Pursuant to N.Y. Gen. Oblig. Law § 5-1401, the Parties agree that this Agreement shall be governed by the laws of the State of New York.

SECTION 10. Binding Effect. The provisions of this Agreement shall survive closing of the assignments and shall be binding upon and inure to the benefit of the respective successors and permitted assigns of the parties to this Agreement.

SECTION 11. Transferability. The rights and obligations of each of the Parties under this Agreement may be transferred or assigned only upon written consent of each other Party.

SECTION 12. Execution of Counterparts. This Agreement may be executed in any number of counterparts, each of which when so executed and delivered shall be deemed an original.

SECTION 13. Further Assurances. Each party will do such acts, and execute and deliver to any other party such additional documents or instruments as may be reasonably requested.

SECTION 14. Entire Agreement. This Agreement (including the Exhibits) constitutes the entire agreement among the parties with respect to the subject matter hereof.

SIGNATURE PAGE FOLLOWS

IN WITNESS WHEREOF, the parties hereto have executed this Agreement as of the date first-above stated.

DEUTSCHE BANK AG

Name:

Title:

Name:

Title:

DEUTSCHE BANK FINANCIAL LLC

Name:

Title:

Name:

Title:

EXHIBIT A

OPERATING AGREEMENT

This Operating Agreement is incorporated by reference and accompanies the Revenue Sharing Agreement.

EXHIBIT B

ASSETS AND LIABILITIES

DBNY Branch Including Consolidated Group

Combined Balance Sheet

December 31, 2011

(in US GAAP, thousands USD)

Total Assets

Total Liabilities

Total Shareholders' Equity

Total Minority Interest

Total Equity

Total Liabilities and Equity

Enter text✕

What a Revenue Sharing Agreement Is and When It’s Used

A Revenue Sharing Agreement is a contract that sets out how income from a joint activity will be divided among parties. It defines eligible revenue streams, calculation methods, payment timing, reporting obligations, and audit rights. Common uses include partnerships between content creators and platforms, distribution deals, affiliate arrangements, and joint ventures. Clear definitions and measurable metrics reduce disputes. This template is designed for U.S. transactions and can be executed on paper or electronically where ESIGN and UETA permit enforceability.

Why a Clear Revenue Sharing Agreement Matters

A well-drafted agreement aligns expectations, protects revenue entitlements, and provides remedies for breaches. It reduces ambiguity about what counts as revenue, how costs are allocated, and how reconciliations occur. Including reporting and audit provisions helps verify payments and limits downstream disputes.

Why a Clear Revenue Sharing Agreement Matters

Who Typically Signs or Manages These Agreements

Revenue sharing agreements are used by businesses of varying size when two or more parties will receive a portion of revenue from a shared activity. Below are common roles involved.

  • Platform Operators — Product or partnership teams that collect revenue and remit shares according to contract terms.
  • Content Creators & Affiliates — Individuals or small businesses receiving a percentage of sales or ad revenue.
  • Legal & Finance Teams — Review revenue definitions, tax implications, and reporting controls.

Parties should confirm signer authority and include corporate sign-off or an authorized representative to avoid later disputes.

Core Clauses to Include in a Professional Revenue Sharing Agreement

A complete agreement includes a clear revenue definition, split formula, payment mechanics, audit and reporting rights, term and termination language, and dispute resolution. Precise drafting reduces interpretive risk and eases ongoing administration.

Revenue Definition

Define gross vs net revenue, allowed deductions, refunds, chargebacks, and the timeframe for recognizing revenue to avoid ambiguity.

Split Formula

Specify percentages or fixed amounts, tiered rates, thresholds, and any adjustments tied to performance metrics or costs.

Payment Terms

State payment frequency, method, currency, late fees, interest, and bank details or payment platform information.

Reporting & Audit

Require periodic statements, supporting data, and inspection rights; set confidentiality boundaries for shared financial data.

Term & Termination

Set the effective date, initial term, renewal conditions, and consequences of termination including final accounting.

Dispute Resolution

Choose governing law, venue, and whether disputes go to mediation or arbitration to limit litigation costs and delay.

Step-by-Step: How to Complete the Agreement

Follow a consistent completion order to reduce omissions and ensure all parties can review material terms before signing.

  • 01
    Prepare Parties: Confirm legal names and authorized signers for each party.
  • 02
    Define Revenue: List and describe each revenue stream and allowable deductions.
  • 03
    Set Mechanics: Specify split percentages, payment timing, and delivery method.
  • 04
    Review, Sign, Distribute: Circulate final draft to legal and finance, then execute and record signatures.

Options to Configure an Online Signing Workflow

Configure electronic workflows to capture signatures, enforce signing order, and collect authentication evidence suitable for recordkeeping and compliance.

Field Configuration
Template Create a reusable template with fixed fields for parties, effective date, and payment terms.
Routing Order Set sequential or parallel signing depending on required approvals.
Authentication Choose email link, SMS code, or stronger methods like identity verification for higher-value agreements.
Reminders Enable automated reminders and final signed-copies distribution to all parties.

Typical Signing Flow for Electronic Execution

A standard online signing flow captures signer identity, timestamps, and provides a tamper-evident final PDF plus an audit trail for record retention.

  • Upload Document: Sender uploads the agreement and maps required fields.
  • Assign Signers: Add signer emails and specify signing order if needed.
  • Signer Authentication: Signers verify identity via email link, SMS code, or stronger checks.
  • Completion & Audit: Signed PDF and detailed audit trail are generated and distributed.

Technical Considerations for eSigning Revenue Sharing Agreements

Choose an eSignature platform that captures intent, consent, attribution, and preserves a reproducible record consistent with ESIGN/UETA.

  • Authentication: Supports email, SMS, and optional identity verification for higher-value contracts.
  • Audit Trail: Records IP, timestamps, and signer actions for evidentiary purposes.
  • Document Formats: Accepts PDF and DOCX and produces tamper-evident signed output.

For sensitive or HIPAA-related financial arrangements, ensure the platform supports appropriate security and, if required, a Business Associate Agreement.

Essential Information to Collect and Protect

Parties: Full legal names
Tax IDs: TIN or EIN
Bank Details: Account and routing for payouts
Payment Terms: Schedule and methods
Reporting Data: Metrics and supporting statements
Confidentiality: NDA scope and data handling

Key Risks and Potential Consequences of Errors

Unenforceability: Vague terms can lead to non-enforceability
Tax Exposure: Incorrect TINs may trigger backup withholding
Late Payment Liability: Interest and damages for missed remittances
Breach Claims: Contractual damages and injunctive relief
Data Breach: Privacy violations and regulatory fines
Audit Findings: Reconciliation mismatches can trigger disputes

Common Drafting and Setup Mistakes to Avoid

  • Imprecise revenue definitions lead to recurring disputes over what revenue is shareable and who bears refunds or chargebacks.
  • Failing to define timing and cutoffs for revenue recognition causes mismatches in period reporting and delayed reconciliation.
  • Omitting audit rights or proof requirements limits the ability to verify calculations and may prevent recovery of underpayments.
  • Using verbal agreements or unsigned spreadsheets creates enforceability problems; always execute a written, signed agreement.

Practical Tips for Clear, Enforceable Revenue Sharing Terms

Adopt uniform reporting formats, require supporting detail for reconciliations, and include mechanisms for periodic true-ups and dispute resolution.

Use Clear Definitions
Define all key terms such as 'Gross Revenue', 'Net Revenue', 'Chargebacks', and 'Adjustments' with examples to reduce interpretive disputes.
Require Supporting Data
Mandate standardized reports and file formats for reconciliations; require transaction-level detail on an agreed schedule to enable audits.
Limit Deductions
Specify which expenses the revenue share absorbs; establish the deduction order to avoid surprise netting.
Plan for Termination
Describe final accounting, final payment timing, and survival of payment and confidentiality clauses after termination.

Real-World Examples of Platform and Partner Revenue Agreements

These examples show how organizations use electronic execution and clear clauses to manage revenue sharing at scale.

Optica Ventures (Brian Fitzgibbons)

Optica used a standard agreement to streamline partner payouts and reporting.

  • The interface simplified partner onboarding and approvals.
  • The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

Martin Properties (Tim Martin)

A property management firm executed revenue splits with vendors and tenants electronically.

  • Remote signing sped reconciliations and reduced paper handling.
  • I can process and execute all of these documents online with 100% compliance and built-in security.

Comparison: Common eSignature Options for Executing Revenue Sharing Agreements

Below is a high-level pricing and capability comparison of eSignature vendors often used to execute agreements; signNow is listed first per vendor convention.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Key Dates and Timeframes to Track

Track payment cycles, reporting deadlines, and any tax filing dates tied to revenue distributions to avoid late fees and penalties.

Effective Date:

Date when obligations begin; use MM/DD/YYYY and base payment cycles from this date.

Payment Cycle:

Monthly or quarterly dates for payments and reconciliations, e.g., 30 days after month-end.

Reporting Deadline:

Dates for delivering supporting statements, e.g., within 15 business days after period close.

Tax Filings:

Collect TINs early; 1099-NEC recipient deadline is Jan 31 each year.

Renewal Notice:

Lead time for renewals or termination notice, commonly 30–90 days prior to term end.

Frequently Asked Questions about Revenue Sharing Agreements

Answers to common execution, enforcement, and eSigning questions encountered when creating revenue sharing agreements.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users