Establishing secure connection…Loading editor…Preparing document…

Subscription Payment Share Agreement

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

Subscription Payment Share Agreement

Effective Date:

Parties

        

        

Recitals

This Subscription Payment Share Agreement (the "Agreement") is entered into by and between the Primary Party and the Secondary Party identified above. The Parties agree to share the costs, responsibilities, and payment obligations for one or more paid subscriptions to services or software as described below, subject to the terms and conditions set forth in this Agreement.

Subscription Items (Itemized)

Description Billing Cycle Total Amount Share (%) Share Amount Payor

Subtotal:

Tax:

Total:

Payment Allocation and Procedures

1. Allocation. Each subscription listed above shall be allocated between the Parties in the percentages set forth in the corresponding Share (%) field. The Party designated as Payor for a subscription shall be responsible for remitting the full payment to the vendor or platform when the subscription is billed. The non-paying Party shall reimburse its allocated share to the Payor pursuant to the reimbursement procedure below.

2. Reimbursement Procedure. Within days of receipt of proof of payment, the non-paying Party shall reimburse the Payor by the agreed method. Proof of payment shall include an invoice, receipt, or account billing statement. Failure to reimburse within the stated period constitutes a breach under this Agreement.

        

3. Late Payment and Interest. Any reimbursement not received by the Payor within the time specified above shall accrue interest at the rate of percent per month (or the maximum permitted by law, if less). The defaulting Party shall also be responsible for reasonable collection costs, including attorneys' fees.

Default, Remedies, and Suspension

If a Party fails to reimburse an owed share after written demand and a cure period of days, the non-defaulting Party may (a) suspend any shared subscription if permitted by the vendor, (b) terminate this Agreement with respect to future subscriptions upon thirty (30) days' written notice, and (c) pursue any remedies available at law or equity.

Termination and Cancellation

Either Party may terminate this Agreement with thirty (30) days' written notice to the other Party. Termination shall not relieve either Party of obligations accrued prior to the effective date of termination, including reimbursement of unpaid shares and any unpaid interest or collection costs.

Confidentiality

The Parties agree that billing information, account credentials, and any commercially sensitive terms provided by one Party to the other in connection with this Agreement shall be treated as Confidential Information and shall not be disclosed to third parties except as necessary to enforce this Agreement or as required by law.

Representations, Indemnity, and Limitation of Liability

Each Party represents that it has full authority to enter into this Agreement. Each Party shall indemnify and hold harmless the other Party from and against any third-party claims arising from that Party's breach of payment obligations, negligence, or willful misconduct. Except for willful misconduct or gross negligence, neither Party shall be liable for incidental or consequential damages in excess of the total sums paid under this Agreement in the prior six (6) months.

Dispute Resolution and Governing Law

The Parties shall attempt in good faith to resolve any dispute arising out of or relating to this Agreement by negotiation. If unresolved within thirty (30) days, disputes shall be resolved by binding arbitration in the State of under the rules of the chosen arbitral forum. Judgment on the award may be entered in any court of competent jurisdiction.

Notices

All notices required or permitted under this Agreement shall be in writing and shall be deemed given when delivered personally, sent by certified mail, or sent by email to the addresses provided in the Parties section. Notice to Primary Party:

Notice to Secondary Party:

Amendment; Assignment

This Agreement may be amended only by a written instrument signed by both Parties. Neither Party may assign its rights or obligations hereunder without the prior written consent of the other Party, except to a successor in interest by merger or sale of substantially all assets.

Miscellaneous

If any provision of this Agreement is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. This Agreement constitutes the entire agreement between the Parties with respect to the subject matter hereof.

Primary Party:

By:

Date:

Secondary Party:

By:

Date:

Enter text✕

What a Subscription Payment Share Agreement Is

A Subscription Payment Share Agreement is a written contract that defines how recurring subscription revenue is divided among participating parties. It sets the percentage splits, payment schedule, invoicing and reconciliation processes, reporting obligations, dispute-resolution steps, and tax-related responsibilities. The agreement typically specifies timing for remittances, procedures for refunds or chargebacks, audit rights, termination provisions, confidentiality, and which jurisdiction’s law governs interpretation. Parties often attach payment schedules and sample reports as exhibits so amounts can be verified against gateway or processor records.

Why this Agreement Matters and How It Stands Up Legally

A clear Subscription Payment Share Agreement reduces disputes, ensures consistent remittance timing, and assigns tax and reporting duties; properly executed it creates enforceable obligations under general contract law. Electronic execution is acceptable across most U.S. transactions under the ESIGN Act (15 U.S.C. ch. 96, 2000) and state UETA statutes, provided intent, consent, attribution, and record retention requirements are met.

Why this Agreement Matters and How It Stands Up Legally

Typical Parties and When They Use This Agreement

The agreement is used when multiple parties share revenue from subscription-based services and need documented allocation, reporting, and payment processes.

  • SaaS vendors sharing revenue with resellers or channel partners, where commission splits and timing must be fixed.
  • Payment processors or gateways that settle fees to multiple recipients and need reconciliation terms.
  • Content platforms and marketplaces that distribute subscription proceeds among creators and the platform.

Use this agreement at onboarding, when adding partners, or whenever revenue-sharing mechanics change materially.

Step-by-step: How to complete and execute the agreement

Follow these steps for a correct, auditable signature workflow for a Subscription Payment Share Agreement.

  • 01
    Prepare document: Draft revenue split, schedules, and exhibits; include tax and audit clauses.
  • 02
    Insert fields: Add name, date, percentage, bank/payment fields, and initial boxes where needed.
  • 03
    Assign signers: Define each party’s signer and set authentication level (email, SMS, or higher).
  • 04
    Send and complete: Distribute for signature and capture the audit trail after all parties sign.

Configuring an online signing workflow for shared payments

Common settings ensure signatures, authentication, and payment fields behave consistently across signers.

Field Configuration
Signature Order Sequential or parallel signer flow
Authentication Email link, SMS code, or KBA where required
Payment Field Embed processor token or reference ID
Audit Trail Enable IP, timestamp, and action logs

Where to send and how execution typically flows

A typical routing sends the agreement to each party in the order required, gathers signatures, and delivers executed copies for bookkeeping.

  • Upload document: Store original in PDF or DOCX format
  • Place fields: Add signature, date, and payment data fields
  • Distribute: Send to signers or generate signing links
  • Archive: Save executed PDF with audit trail

Delivery options and technical requirements

Choose a distribution method that preserves the audit trail and supports your chosen authentication level.

  • Integrations: Salesforce, NetSuite, Microsoft 365 supported
  • File formats: PDF and DOCX are standard
  • Authentication: Email, SMS, or advanced options

Ensure the chosen platform stores tamper-evident records and supports the retention timeframe required by law and internal policy.

Time-sensitive dates to track in the agreement

Track each milestone so remittances and reporting occur on schedule and tax filings remain accurate.

Remittance Due Date:

Specify exact day each period for payment remittance

Monthly Reconciliation:

Set a monthly close and dispute window (e.g., 30 days)

1099 Reporting:

Report payments subject to IRS Form 1099 by Jan 31

Notice for Termination:

Define notice period for contract termination

Audit Response Time:

Require document production within a defined number of days

Common preparation mistakes to avoid

  • Leaving payment formulas vague or referencing undefined terms can lead to inconsistent remittances and disputes over what constitutes gross versus net revenue.
  • Failing to require supporting transaction detail or access to processor reports prevents effective reconciliation and increases audit friction between parties.
  • Using inconsistent party names or incorrect tax IDs risks backup withholding, incorrect 1099 reporting, and potential IRS penalties for the payer.
  • Not specifying chargeback or refund handling (who bears cost and timing for reversals) frequently causes post-termination financial disputes.

Penalties and practical risks if the agreement is incorrect

1099 Penalties: 1099 late penalties (IRC §6721)
Backup Withholding: 24% backup withholding risk
Payment Disputes: Loss of revenue and litigation costs
Contract Breach: Damages and injunctive relief exposure
Data Privacy: HIPAA or state privacy fines
Recordkeeping Failures: Regulatory audit penalties

Security and compliance data points to include

Encryption: AES-256 at rest
In transit: TLS 1.2/1.3
Certifications: SOC 2 Type II
Privacy: GDPR and CCPA compliant
Healthcare: HIPAA (BAA required)
FDA/Digital: 21 CFR Part 11 support

Principal clauses that should be in every agreement

Include clear, enforceable clauses that govern how money flows, how disputes are resolved, and who bears tax or compliance responsibilities.

Revenue Split

Define exact percentages, rounding rules, and whether splits are on gross or net revenue, including examples of calculations.

Payment Timing

Specify due dates, business day computation, cutoff times, and interest or fees for late remittance.

Reporting

Require periodic statements with transaction-level details, agreed formats, and reconciliation procedures for disputes.

Audit Rights

Grant limited audit access to transaction logs and processor reports with confidentiality protections and timing limits.

Tax Allocation

State which party is responsible for tax reporting and indemnify for incorrect 1099 or withholding treatment.

Termination

List termination triggers, wind-down payment procedures, and treatment of pre-paid or in-flight subscriptions.

Supporting documents you should attach

Attachments provide the operational detail necessary to enforce payment flows and perform reconciliations without additional negotiation.

Executed Agreement

Final signed PDF with audit trail preserved for accounting and legal records.

Payment Schedule

Exhibit listing billing cycles, remittance days, and any tiered splits or thresholds.

Processor Reports

Sample transaction and settlement reports from payment gateways to support reconciliation.

Tax Forms

W-9 or foreign equivalent for each payee to avoid backup withholding issues.

Real-world examples and how they were structured

Two representative examples show how different organizations define splits and control reporting to reduce disputes.

Optica Ventures LLC

Optica used a fixed percentage split with monthly reconciliations and sample reports attached

  • The COO emphasized ease of use
  • The structure required processor-level reports and a 30-day dispute window to prevent recurring payment disagreements.

Martin Properties

A small property-technology provider split subscription revenue with a channel partner on a tiered basis

  • The founder noted mobile signing helped speed onboarding
  • The agreement included automated remittance by the processor and explicit chargeback handling to protect both parties.

Who typically has authority to sign

Authorized Signer

The person legally authorized to bind the organization—often a CEO, CFO, or delegated officer. Confirm delegation with a board resolution or an officer certification where internal policy requires it.

Finance Representative

A finance or treasury representative may be authorized for operational sign-off on remittance schedules and account details; major commercial terms normally still require an officer-level signature.

Pricing and feature comparison for e-signature solutions

Pricing and feature availability vary by vendor and plan. signNow appears first in the comparison below and entries reflect published plan starting prices and known feature distinctions.

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 vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently asked questions about Subscription Payment Share Agreements

Answers to common questions about execution, e-sign validity, notarization, amendments, and recordkeeping for subscription share agreements.


Need help? Contact support

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