Is an electronic signature legally binding?

Yes, under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally legally equivalent to handwritten signatures if intent, consent, attribution, and retention requirements are met.

Do I need a notary for a SaaS Addendum?

Typically no; addenda are commercial agreements that rarely require notarization. If a specific state or ancillary document requires notarization, follow that statutory requirement.

What makes an e-signature evidentiary?

A complete audit trail showing signer identity, timestamps, and authentication steps provides the attribution and integrity courts rely on for enforceability.

How do I handle HIPAA obligations?

Attach a HIPAA Business Associate Agreement when PHI is processed; ensure the vendor provides necessary technical safeguards and a signed BAA to allocate responsibilities.

Can a counterparty claim lack of consent?

Include consumer disclosure where required and capture consent logs; ESIGN requires disclosure for consumer-facing electronic records of rights to paper alternatives.

How should I store executed addenda?

Store signed copies in a secure contract repository with tamper-evident storage, access controls, and retention metadata aligned with regulatory obligations.

Electronic Signature
Templates
Miscellaneous
Software as a Service Addendum

Software as a Service Addendum

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

Software as a Service Addendum

This Software as a Service Addendum (the Addendum) is entered into as of by and between the parties identified below and governs the provision of cloud-based software and related services under the underlying agreement referenced below.

Parties and Reference

Service Provider Service Provider Address Client Client Address

Reference Agreement: The parties are bound by a preexisting agreement (the Agreement). The Agreement effective date is and this Addendum supplements and modifies the Agreement as set forth herein.

WHEREAS

WHEREAS, Service Provider operates and maintains a cloud-hosted software platform for delivery of software functionality described as (the Services); and

WHEREAS, Client desires to receive the Services and any ancillary support, and the parties desire to set forth additional terms and operational details regarding such Services.

NOW, THEREFORE, in consideration of the mutual covenants and promises contained herein, the parties agree as follows.

Scope of Services

Description of Services

Service Provider shall provide the Services described above and maintain the underlying infrastructure, platform, and application availability necessary for Client to access and use the Services in accordance with the service levels set forth below and any mutually agreed statement of work.

Uptime Commitment Support Response Target

Payment Terms

Client shall pay Service Provider the fees for the Services as set forth below. All fees are payable in U.S. Dollars unless otherwise agreed in writing. Fees do not include taxes, duties, or other governmental charges for which Client is responsible.

Subscription Fee Amount Billing Schedule First Billing Date Payment Method Late Fee

Invoices are due within thirty (30) days of receipt unless otherwise stated. Overdue amounts shall accrue interest at the rate set forth above and Service Provider may suspend access to the Services for nonpayment following at least ten (10) days' written notice. Client shall be liable for reasonable costs of collection, including attorneys' fees.

Term and Termination

The term of this Addendum shall commence on and shall continue until unless earlier terminated in accordance with this Addendum.

Notice Period for Termination Without Cause (days)

Either party may terminate this Addendum for material breach by the other party if the breaching party fails to cure such breach within thirty (30) days after receipt of written notice. Termination shall be without prejudice to any other rights or remedies available at law or in equity.

Upon expiration or termination, Client shall pay all outstanding fees due through the effective date of termination. Service Provider shall, at Client's written request made within days, return Client Data in a commonly used electronic format and thereafter securely delete Client Data in Service Provider's possession in accordance with the Data Security provisions below.

Confidentiality

"Confidential Information" means non-public information disclosed by one party to the other that is designated confidential or that reasonably should be understood to be confidential. The receiving party shall: (a) use Confidential Information solely to perform its obligations under this Addendum; (b) restrict disclosure to employees, contractors, and agents with a need to know and who are bound by confidentiality obligations at least as restrictive as those herein; and (c) take reasonable measures to protect Confidential Information from unauthorized disclosure. Confidential Information does not include information that is publicly known without breach, known prior to disclosure, or independently developed without use of the disclosing party's Confidential Information.

Confidentiality Duration (years)

Data Security and Privacy

Service Provider shall maintain administrative, physical, and technical safeguards appropriate to the nature of the Client Data to protect against unauthorized access, disclosure, alteration, and destruction. Service Provider will notify Client without undue delay upon becoming aware of a confirmed security incident affecting Client Data and will cooperate in mitigation and remediation. Client remains responsible for the accuracy of Client Data and for obtaining any consents required for processing.

Data Return or Deletion Period (days)

Intellectual Property

As between the parties, Service Provider retains all right, title, and interest in and to the Services, platform, software, and any derivatives, improvements, or enhancements thereto, including all intellectual property rights. Service Provider grants Client a non-exclusive, non-transferable, revocable license to access and use the Services during the term solely for Client's internal business operations. Client retains all right, title, and interest in and to Client Data.

Warranties; Limitation of Liability

Service Provider warrants that it will provide the Services materially in accordance with the Scope of Services. EXCEPT AS EXPRESSLY SET FORTH IN THIS ADDENDUM, THE SERVICES ARE PROVIDED "AS IS" AND SERVICE PROVIDER DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

NEITHER PARTY SHALL BE LIABLE FOR INDIRECT, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES. SERVICE PROVIDER'S AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THIS ADDENDUM SHALL NOT EXCEED THE FEES PAID BY CLIENT TO SERVICE PROVIDER UNDER THIS ADDENDUM IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY.

Governing Law

This Addendum shall be governed by and construed in accordance with the laws of the state of without regard to its conflict of laws principles.

Entire Agreement; Amendment

This Addendum, together with the Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings. Any amendment or modification of this Addendum must be in writing and signed by authorized representatives of both parties.

Survival

Provisions that by their nature should survive expiration or termination of this Addendum shall so survive, including but not limited to Payment Terms, Confidentiality, Intellectual Property, and Limitation of Liability.

Service Provider:

By:

Date:

Client:

By:

Date:

What a Software as a Service Addendum Is and when it applies

A Software as a Service Addendum is a contract attachment that defines how a cloud-hosted software provider will deliver, secure, and support its service for a customer. It clarifies service levels, data handling, privacy and security obligations, uptime commitments, incident response, and allocation of responsibilities between vendor and customer. The addendum typically augments a master services agreement or subscription agreement and governs operational details such as backups, compliance certifications, access controls, and vendor subcontracting.

Why including a SaaS Addendum matters for risk and clarity

A properly drafted addendum reduces ambiguity about uptime, data protection, and liability, helping both parties understand operational obligations and regulatory responsibilities under laws like ESIGN and UETA.

Who prepares and who signs a Software as a Service Addendum

The addendum is used by legal, procurement, security, and vendor operations teams to document technical and compliance commitments.

Vendor legal and operations teams — Draft the addendum and confirm technical commitments and subcontractor relationships.
Customer procurement and security reviewers — Validate SLAs, data handling procedures, and any industry-specific addenda such as HIPAA BAAs.
Finance and contract administrators — Confirm billing, termination, and change-order terms for alignment with purchasing rules.

Final signatures are typically executed by authorized signatories on both sides, often the vendor signatory and a customer procurement officer or authorized contract signatory.

How to complete and execute the addendum in practice

Follow a simple workflow that collects required data, secures internal approvals, then routes for signature and final storage.

01

Prepare draft: Assemble clauses and any industry addenda for legal review.
02

Internal approvals: Get sign-offs from security, procurement, and finance as required.
03

Route to counterparty: Send to the other party for review and signature.
04

Execute and archive: Capture final signatures, store with master agreement, and record retention metadata.

Setting up an online workflow for the Addendum

Configure a reusable template and signing workflow to reduce errors and speed execution across multiple customers.

Field	Configuration
Template	Create a locked template for standard terms and variable fields.
Signer authentication	Select email verification, SMS code, or stronger methods for high-risk agreements.
Conditional fields	Use conditional logic to show clauses only when applicable to a customer type.
Retention	Set automatic archival and export policies to preserve signed records.

Where to send, store, and manage completed addenda

A clear destination policy ensures that executed addenda are discoverable and available for audits, renewals, and incident response.

Contract repository: Store the signed addendum alongside the master services agreement in the contract system.
Vendor CMDB: Record service details and contacts in the configuration management database for operational use.
Security evidence store: Keep compliance artifacts, certifications, and BAAs together for audit readiness.
Email to stakeholders: Send final signed copy to legal, procurement, and the assigned account manager.

Sharing and signing options for the Addendum

Choose a delivery method that preserves integrity, provides an audit trail, and meets any regulatory authentication requirements.

Integrations: Support for Salesforce, NetSuite, Microsoft 365, Google Workspace, and CLM platforms.
File formats: PDF and DOCX support with preserved fields and audit metadata.
Authentication: Options include email, SMS, knowledge-based, and advanced signer authentication.

Use a channel that records signer attribution and timestamps while aligning with internal policies for retention and access control.

Core clauses and provisions to include in a professional addendum

A well-structured addendum covers operational commitments, data protection, compliance, liability limits, and procedural details so each party knows expectations and remedies.

License scope

Define permitted users, restrictions, and any reserved rights; include usage metrics and audit rights where applicable.

Service levels

Quantify uptime, maintenance windows, measurement method, remedies, and credits for unmet thresholds.

Data security

Enumerate technical and organizational controls, encryption at rest and in transit, and breach notification timelines.

Subprocessors

List categories of subprocessors, notice and objection process, and contractual flow-down requirements.

Compliance addenda

Attach industry-specific addenda such as HIPAA BAA or FERPA protections when applicable.

Termination and exit

State termination rights, data return or destruction procedures, and assistance for data migration on exit.

Key security and compliance elements to document

Encryption in transit: TLS 1.2/1.3

Encryption at rest: AES-256

Certifications: SOC 2 Type II

Privacy laws: GDPR compliance

Healthcare: HIPAA with BAA

Regulated records: 21 CFR Part 11 support

Common notice periods, effective dates, and timing to track

Track the effective date and contractual notice windows carefully to avoid missed renewals, late terminations, or unplanned auto-renewals.

Effective date:

MM/DD/YYYY format; determines start of obligations

Renewal notice:

Typical range: 30–90 days before renewal

Termination notice:

Contract should specify required notice period for termination

SLA credit claim window:

Often 30–90 days to submit an SLA claim

Data retrieval window:

Specify time for data export after termination

Common mistakes to avoid when preparing the addendum

Leaving SLA metrics vague rather than defining measurement and credit methodology.
Failing to identify data residency, which can create compliance gaps for cross-border data flows.
Omitting subprocessors or failing to require contractual flow-down to third parties.
Using ambiguous termination and exit language that leaves data return responsibilities unclear.

Potential legal and operational risks from an incomplete addendum

Regulatory fines: HIPAA exposure — 45 CFR §164.530(j)

Tax or reporting risk: Incorrect documentation can trigger IRS scrutiny

Operational downtime: Undefined SLAs increase outage impact

Data loss: Insufficient backup obligations

Liability gaps: Missing indemnity or limitation clauses

Enforceability: Lack of clear signature/consent evidence

Real-world examples of electronic execution in enterprise environments

These examples show how organizations used an eSignature platform to streamline contract execution while preserving compliance and auditability.

Optica Ventures LLC

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

Quick adoption across deal teams accelerated closing cycles.
Using a template-based workflow reduced manual errors and allowed consistent capture of required signature and approval metadata for audit purposes.

Xerox

airSlate SignNow provides us with the flexibility needed to get the right signatures on the right documents, in the right formats, based on our integration with NetSuite.

Integration supported automated routing of signed addenda.
That integration reduced processing time by removing manual handoffs and ensured each signed addendum was correctly linked to customer accounts.

Practical tips to ensure accurate and enforceable addenda

Adopt these practical controls to reduce mistakes, support compliance, and make execution repeatable across accounts.

Use a standardized template

Maintain a canonical template with locked core clauses and configurable fields to ensure consistency and speed reviews.

Confirm signer authority

Require signatory name, title, and entity confirmation; cross-check against corporate records to avoid challenges.

Include measurable SLAs

Define precise measurement windows, monitoring methods, and remedy mechanics for service level failures.

Keep an audit trail

Ensure every execution includes timestamps, IP addresses, and signer authentication logs for enforceability.

eSignature solution pricing comparison for signing SaaS Addenda

Compare common vendor starting prices and capability flags relevant to executing and storing signed addenda; signNow is listed first for parity in comparisons.

	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
Envelope Cap	No cap	100 envelopes/user/year limit	Varies	Varies	Varies

Frequently asked questions about executing a SaaS Addendum

Answers to common questions about enforceability, signatures, and recordkeeping for addenda executed electronically.

Need help? Contact support

Is an electronic signature legally binding?
Yes, under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally legally equivalent to handwritten signatures if intent, consent, attribution, and retention requirements are met.
Do I need a notary for a SaaS Addendum?
Typically no; addenda are commercial agreements that rarely require notarization. If a specific state or ancillary document requires notarization, follow that statutory requirement.
What makes an e-signature evidentiary?
A complete audit trail showing signer identity, timestamps, and authentication steps provides the attribution and integrity courts rely on for enforceability.
How do I handle HIPAA obligations?
Attach a HIPAA Business Associate Agreement when PHI is processed; ensure the vendor provides necessary technical safeguards and a signed BAA to allocate responsibilities.
Can a counterparty claim lack of consent?
Include consumer disclosure where required and capture consent logs; ESIGN requires disclosure for consumer-facing electronic records of rights to paper alternatives.
How should I store executed addenda?
Store signed copies in a secure contract repository with tamper-evident storage, access controls, and retention metadata aligned with regulatory obligations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now