Can this be e-signed?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. Confirm no statutory exception applies, and obtain any required consumer disclosures.

When is notarization required?

Most revenue sharing addenda do not require notarization, but state or institutional policies may require it for certain attachments. Check the governing state and the primary agreement.

If the addendum involves student educational records, FERPA restrictions may apply. Include data use limits and ensure any vendor handling student records complies with FERPA.

Which tax forms are involved?

Tax consequences depend on payee status. Collect W-9s for U.S. payees and plan for 1099 reporting; missing TINs may trigger backup withholding at 24%.

How do I amend an executed addendum?

Execute a written amendment signed by authorized representatives of all parties or replace the addendum with a new signed agreement per the amendment clause.

How long to retain records?

Retain financial and tax records at least 3 years (IRC §6501(a)), longer for audit or state-specific requirements; keep signed addenda for the active term plus several years.

Electronic Signature
Templates
Education
Education Revenue Sharing Addendum

Education Revenue Sharing Addendum

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

EDUCATION REVENUE SHARING ADDENDUM

This Education Revenue Sharing Addendum (the Addendum) is entered into by and between: Institution Name: and Partner Name: Effective Date: . This Addendum amends the underlying Agreement between the parties and sets forth terms for sharing revenue derived from educational programs, courses, or services identified herein.

RECITALS

WHEREAS, Institution operates educational programs and provides instruction, enrollment, and related services; and WHEREAS, Partner refers or delivers students, marketing, or other qualifying services to Institution in exchange for a portion of revenue attributable to enrolled students or program fees; the parties agree to the revenue sharing arrangement set forth below.

DEFINITIONS

For purposes of this Addendum, the following definitions apply:

"Program" means the educational offering identified as:

"Eligible Revenue" means gross tuition, enrollment fees, and directly related program fees collected by Institution from students attributed to Partner under the attribution rules below, excluding amounts listed as Excluded Revenue.

REVENUE SHARING TERMS

Revenue Share Percentage to Partner: of Eligible Revenue.

Revenue Basis: Gross Revenue Net Revenue (after specified adjustments)

Eligible Revenue — detailed description Excluded Revenue (examples and clarifications)

ATTRIBUTION AND ELIGIBILITY

Students eligible for Revenue Share are those enrolled in the Program and attributed to Partner pursuant to the parties' attribution method:

Associated Student / Cohort Details (if applicable)

PAYMENT, REPORTING, AND AUDIT

Reporting Frequency: Monthly Quarterly Annual

Payment Due: Payments are due within days of Institution's delivery of the periodic revenue report. Payments shall be accompanied by a statement showing calculations and supporting enrollment data.

Report Format and Required Data

Audit Rights: Partner shall have the right, not more than once per calendar year and upon reasonable notice, to audit Institution records reasonably necessary to verify payments. Institution shall retain records for a period of .

TERM AND TERMINATION

Term: This Addendum commences on the Effective Date and continues for a period of unless earlier terminated as provided herein.

Termination for Cause: Either party may terminate for material breach upon cure period following written notice. Termination shall not relieve Institution of obligations to remit amounts due for Eligible Revenue earned prior to termination.

CONFIDENTIALITY AND DATA

The parties shall maintain the confidentiality of student data and commercially sensitive revenue information in accordance with applicable privacy laws and the confidentiality obligations in the underlying Agreement. Neither party shall disclose the other's confidential information except as required by law.

TAXES, COMPLIANCE, AND INDEMNIFICATION

Tax Treatment: Each party is responsible for its own taxes arising from payments received under this Addendum. Institution shall provide documentation of amounts paid to Partner as required under tax law; Partner shall be responsible for reporting income and paying taxes.

Indemnification: Each party shall indemnify, defend and hold the other harmless from third-party claims arising out of its breach of this Addendum or gross negligence in performance.

NOTICES

Institution Notice Address Institution Contact Person Partner Notice Address Partner Contact Person

MISCELLANEOUS

Assignment: Neither party may assign this Addendum without the prior written consent of the other, except that either party may assign to an affiliate or in connection with a merger or sale of substantially all its assets.

Governing Law: This Addendum shall be governed by the laws of the State of without regard to conflict of laws principles.

Additional Terms or Notes

Institution Printed Name:

By:

Date:

Partner Printed Name:

By:

Date:

What the Education Revenue Sharing Addendum Is

The Education Revenue Sharing Addendum is a contract amendment that defines how revenue derived from an educational program, product, or service will be shared between the educational institution and one or more partners. It clarifies revenue split percentages, payment schedules, reporting obligations, audit rights, and termination triggers while operating as part of a primary agreement such as a license, services contract, or partnership agreement. The addendum also allocates responsibility for tax reporting, compliance with education privacy laws like FERPA, and any required disclosures to stakeholders.

Why a Clear Addendum Matters

A well-drafted Education Revenue Sharing Addendum reduces disputes by documenting payment mechanics, timelines, and reporting formats; it supports regulatory compliance, enables auditability, and preserves the parties’ financial and reputational interests.

Who Typically Uses This Addendum

Parties across education and vendor ecosystems use this addendum to formalize revenue arrangements and compliance responsibilities.

Higher education institutions and their licensing teams managing course, content, or technology revenue sharing agreements.
School districts and charter networks contracting with curriculum or platform vendors for shared-revenue programs.
EdTech companies and content providers defining payout terms, reporting cadence, and data access rights.

The document suits any arrangement where money is divided among educational entities and partners and where tax, privacy, or audit obligations must be explicit.

Core Elements to Include in the Addendum

A comprehensive addendum addresses parties, revenue formulas, timing and mechanics of payments, reporting and audit rights, compliance obligations, and termination or amendment procedures.

Parties

Identify each contracting entity with full legal name, business type, and contact details to ensure correct attribution and invoicing.

Revenue Split

Specify percentage allocations, rounding rules, treatment of discounts/refunds, and whether gross or net revenue is the basis for calculations.

Payment Schedule

Define frequency (monthly, quarterly), payment method, remittance instructions, and timelines for reconciliation and correction of errors.

Reporting Requirements

List report contents, file formats, delivery method, deadlines, and responsible parties for each reporting period.

Audit Rights

Allow periodic audits, define scope, notice period, access limits, and cost allocation if discrepancies are found.

Termination & Remedies

State termination triggers, cure periods, outstanding payment treatment, and post-termination reconciliation procedures.

Step-by-Step: Completing the Addendum

Follow these sequential steps to prepare, review, and execute an Education Revenue Sharing Addendum efficiently and with compliance in mind.

01

Gather Documents: Collect the primary agreement, tax IDs, and prior reports for reference.
02

Fill Core Fields: Enter parties, revenue basis, split percentages, and schedule.
03

Legal & Tax Review: Have counsel review tax implications and FERPA or other privacy impacts.
04

Execute & Archive: Obtain signatures, distribute executed copies, and store per retention rules.

Configuring an Online Workflow for the Addendum

Set up an e-sign and reporting workflow that matches the addendum’s fields and authentication needs before sharing for signature.

Field \| Configuration	Role \| Required \| Format
Signature Fields	Place signer, date, and title fields; mark required for all parties.
Authentication	Use email plus SMS code or stronger MFA for each signer.
Conditional Fields	Show payment or tax fields only when applicable to a party.
Notifications	Enable automated receipts and routing confirmations for records.

Typical Execution Flow for Digital Completion

An efficient digital workflow reduces turnaround time: upload the addendum, map fields, authenticate signers, collect signatures, and capture an audit trail.

Upload Document: Import the finalized addendum as PDF or DOCX.
Place Fields: Add signature, date, and required data fields for each party.
Authenticate Signers: Choose email link, SMS, or KBA based on risk.
Complete & Archive: Collect signed copies and store a tamper-evident record.

Technical and Integration Considerations

Select an eSignature platform that supports required authentication, audit trails, and your document formats before sending the addendum for signature.

Integrations: Salesforce, NetSuite, Google Workspace, Box and similar systems for automated storage.
Formats: Accept PDF and DOCX; ensure the platform preserves signatures for downstream reporting.
Authentication: Support for SMS codes, SSO, and advanced signer verification.

Confirm the platform can produce an auditable certificate of completion and that data exports align with your accounting and reporting systems.

Security and Compliance Essentials

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest.

Certification: SOC 2 Type II and ISO 27001 certified.

HIPAA Support: BAA available where PHI is involved.

eSign Law: Compliant with ESIGN and UETA.

21 CFR: Supports 21 CFR Part 11 for regulated records.

Audit Trail: Detailed timestamps, IP, and action logs.

Principal Risks If the Addendum Is Incorrect

Incorrect Tax Reporting: May trigger IRC §6721 penalties.

Backup Withholding: Missing TINs can trigger 24% withholding.

FERPA Noncompliance: Improper data sharing risks loss of compliance.

Payment Disputes: Vague terms increase litigation likelihood.

Data Breach Exposure: Insufficient controls may trigger notification laws.

Invalid Signatures: Improper execution risks unenforceability.

Common Preparation Pitfalls to Avoid

Unclear revenue definitions that omit refunds, discounts, or chargebacks and cause calculation disputes.
Inconsistent reporting formats between parties that delay reconciliation and increase accounting workload.
Failing to secure W-9s or tax IDs for payees, which can trigger backup withholding obligations.
Overlooking privacy obligations such as FERPA, leading to improper sharing of student data with vendors.

Typical Deadlines and Timing Expectations

Establish clear deadlines for reporting, reconciliation, payments, and annual disclosures so all parties can plan accounting and compliance activities.

Reporting Frequency:

Monthly reports due by the 15th of the following month.

Quarterly Reconciliation:

Reconcile quarterly within 30 days after quarter close.

Payment Remittance:

Remit payments within 45 days of report approval.

Annual Statement:

Provide annual financial summary within 60 days after fiscal year end.

Tax Recipient Deadline:

Issue 1099s or equivalent by Jan 31 where applicable.

How This Addendum Compares to Similar Documents

A quick comparison clarifies when to use an addendum versus separate agreements and what each option typically requires.

Criteria	Addendum	Standalone Agreement
Use Case	modify existing contract	new, independent deal
Complexity	lower	higher
Notarization	rare	possible
Tax Reporting	same as original contract	requires standalone payer designation

eSignature Pricing Snapshot for Executing Addenda

Compare common eSignature vendors and pricing tiers to evaluate cost and compliance capabilities when executing Education Revenue Sharing Addenda.

	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	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/yr	Varies	Varies	Varies

Frequently Asked Questions and Troubleshooting

Answers to common legal, technical, and administrative questions encountered when preparing or executing an Education Revenue Sharing Addendum.

Need help? Contact support

Can this be e-signed?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. Confirm no statutory exception applies, and obtain any required consumer disclosures.
When is notarization required?
Most revenue sharing addenda do not require notarization, but state or institutional policies may require it for certain attachments. Check the governing state and the primary agreement.
Does FERPA apply?
If the addendum involves student educational records, FERPA restrictions may apply. Include data use limits and ensure any vendor handling student records complies with FERPA.
Which tax forms are involved?
Tax consequences depend on payee status. Collect W-9s for U.S. payees and plan for 1099 reporting; missing TINs may trigger backup withholding at 24%.
How do I amend an executed addendum?
Execute a written amendment signed by authorized representatives of all parties or replace the addendum with a new signed agreement per the amendment clause.
How long to retain records?
Retain financial and tax records at least 3 years (IRC §6501(a)), longer for audit or state-specific requirements; keep signed addenda for the active term plus several years.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now