How do I add or remove a signer?

Edit the routing in your sender platform before sending: add the signer email, assign the signing role, and reorder signers as needed. Resend the updated envelope to ensure all parties receive the latest version and audit trail.

Is an e-signature legally binding?

Yes, if it meets the ESIGN Act criteria: the signer intends to sign, consents to an electronic record, the signature can be attributed, and the record is reproducible. State UETA laws also apply for intrastate transactions.

When is notarization required?

Notarization is required when statute or the form specifies it; requirements vary by state and document type. For remote notarization, confirm the state's RON rules and identity-proofing obligations before proceeding.

What happens if a TIN is wrong?

An incorrect TIN can trigger backup withholding at 24% and produce IRS penalties for incorrect reporting. Correct the form promptly and provide an updated, signed record to avoid continued withholding.

Can the client withdraw consent to electronic records?

Yes. For consumer-facing financial or healthcare records, provide a clear ESIGN consumer disclosure and a method to withdraw consent; maintain a record of withdrawal per ESIGN requirements.

Which plan supports bulk sending and API access?

Bulk send is available on higher tiers and some premium plans; API and site-license usage-levels are plan-dependent. Check your vendor plan details for bulk send and developer API access.

Electronic Signature
Templates
Miscellaneous
Client Supplemental Forms

Client Supplemental Forms

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

CLIENT SUPPLEMENTAL FORMS

This Client Supplemental Forms (the Agreement) is entered into as of by and between Service Provider Name: (Service Provider) and Client Name: .

WHEREAS

WHEREAS, Client engages Service Provider to provide the services and supplemental deliverables described in this Agreement and any attached schedules; and

WHEREAS, the parties desire to set forth supplemental terms, client-specific requirements, and administrative details that will govern the relationship and the performance of services under the primary agreement between the parties.

NOW, THEREFORE, in consideration of the mutual covenants contained herein, the parties agree to the supplemental terms set forth below.

SCOPE OF WORK

The Service Provider shall perform the following supplemental services and provide the supplemental deliverables in addition to those described in the primary agreement:

Detailed description of supplemental services

CLIENT-SPECIFIC REQUIREMENTS

List of client policies, standards, or tools required for performance Client primary contact (name, title) Client billing contact (name, email, phone)

PAYMENT TERMS

Compensation for the supplemental services shall be as follows:

Total supplemental fee Payment schedule and milestones

Late payment shall accrue interest at: after a grace period of .

TERM AND TERMINATION

The supplemental services described herein shall commence on and shall terminate on unless earlier terminated in accordance with this Agreement.

Either party may terminate this supplemental agreement for convenience upon days' prior written notice. Termination for cause may be effected immediately upon written notice for material breach that is not cured within .

CONFIDENTIALITY

Each party shall keep confidential and shall not disclose to any third party any Confidential Information disclosed by the other party except as expressly permitted herein. Confidential Information means non-public information disclosed in connection with the supplemental services that is marked confidential or that by its nature should reasonably be understood to be confidential.

The receiving party shall use the same degree of care to protect Confidential Information as it uses to protect its own confidential information but no less than reasonable care. Confidentiality obligations survive termination for a period of years, except with respect to trade secrets, for which protection shall continue as long as such information qualifies as a trade secret under applicable law.

Exceptions to confidentiality (if any)

DATA HANDLING AND PRIVACY

Will Service Provider process personal data or sensitive information on behalf of Client? Yes No

If yes, describe data categories, security measures, and retention

INSURANCE AND INDEMNITY

Service Provider shall maintain insurance as required by the primary agreement and as follows for the supplemental services: general liability minimum ; professional liability minimum .

Indemnity scope (describe)

ACCEPTANCE OF DELIVERABLES

Client shall have days from delivery of each deliverable to inspect and either accept or provide written objections specifying any deficiencies. Absent timely written objections, deliverables shall be deemed accepted.

AMENDMENT

Any amendment to this supplemental agreement must be in writing and signed by authorized representatives of both parties. No oral modification shall be binding.

GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by the laws of the State of without regard to its conflict of laws principles. The parties shall first attempt to resolve disputes through good faith negotiation; if unresolved within days, disputes shall be resolved by the dispute resolution mechanism specified in the primary agreement.

ENTIRE AGREEMENT

This Agreement, together with the primary agreement and any exhibits or schedules attached hereto, constitutes the entire agreement between the parties with respect to the supplemental services and supersedes all prior and contemporaneous understandings, proposals or agreements, written or oral, relating to the subject matter hereof.

NOTICES

Service Provider notice address Client notice address

REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that it has the full power and authority to enter into this Agreement and that its performance will not violate any other agreement to which it is a party. Service Provider further warrants that supplemental services will be performed in a professional and workmanlike manner consistent with industry standards.

Additional representations or exceptions

Service Provider Name:

By:

Date:

Client Name:

By:

Date:

What Client Supplemental Forms Are and when they apply

Client Supplemental Forms are attachments that collect client-specific details not captured by primary contracts, intake records, or standard onboarding forms. They commonly document alternate contacts, billing preferences, compliance attestations, special authorizations, industry-specific disclosures, or supplemental technical data required to complete a service or regulatory filing. Organizations use these forms to reduce follow-up questions, centralize nonstandard information, and create a consistent record for operational processing. When included in digital workflows, the forms preserve an audit trail and make downstream approvals, billing, and verification more reliable and reproducible.

Why these supplemental forms matter for compliance and operations

Client Supplemental Forms reduce ambiguity by capturing specific data points that affect billing, regulatory compliance, and service delivery. They create an auditable record for consent and acknowledgements and lower manual rework by ensuring critical information is collected at the point of intake.

Which teams typically prepare or complete Client Supplemental Forms

Typical users include the teams that manage onboarding, compliance, billing, and account administration across public and private organizations.

Client services teams responsible for onboarding and maintaining accurate contacts, preferences, and delivery instructions.
Compliance and legal teams documenting disclosures, consent language, and industry-specific attestations required for regulation.
Finance and billing teams collecting payment instructions, tax identifiers, and invoicing preferences to avoid payment delays.

Centralizing supplemental data reduces manual reconciliation, supports audit trails, and shortens time-to-service for downstream teams.

Stepwise process to complete and submit a Client Supplemental Form

Follow these sequential steps to prepare, verify, and send the form for signature and final processing.

01

Prepare: Gather supporting documents and required identifiers before populating fields.
02

Complete Fields: Enter each value exactly per the fillable fields guide above.
03

Review: Verify names, dates, and TINs; check for required initials and attachments.
04

Submit: Send to all signers using the agreed routing and retain the audit trail.

Where completed Client Supplemental Forms are routed

Common destinations and submission channels for completed forms, depending on organizational workflow and recordkeeping rules.

Client Portal: Upload for attachment to the client record in the portal.
Email to Team: Send certified copies to internal teams for manual processing.
CRM Attachment: Store as a CRM document tied to the account or opportunity.
Third-party Filing: Transmit to external registries or compliance systems when required.

Common digital workflow settings for online completion

Configure these settings to control authentication, notifications, conditional logic, and storage for supplemental forms.

Field	Configuration
Authentication	Email link \| SMS code \| KBA
Notifications	Email on view, sign, complete
Conditional Fields	Show or hide fields based on prior answers
Storage Location	CRM \| Document repository \| Cloud archive

Technical requirements and integrations for eSubmission

Ensure your platform supports secure e-signatures, common file formats, and the integrations required by downstream systems.

Browser Support: Modern TLS 1.2/1.3 browsers
File Formats: PDF, DOCX, XLSX supported
Integrations: Salesforce, NetSuite, Google Workspace

Align integration choices with retention and audit requirements, and confirm that chosen systems support required authentication levels and export formats.

Typical timelines and expected processing windows

Timelines below reflect common internal service-level expectations; adjust them to match regulatory or tax deadlines where applicable.

Request Timing:

Issue during initial onboarding or when a change occurs

Client Response Window:

Return within 7–14 business days to avoid delays

Internal Processing:

Allow 2–5 business days for review and attachment

Escalation:

Escalate after 15 business days without response

Tax Reporting Impact:

Deliver required tax data before reporting deadlines

Key milestones in the supplemental form lifecycle

Numbered milestones show the sequential stages from issue to archived record for the Client Supplemental Form.

01

Issue Form

Sender generates and routes the form to required signers.

02

Complete by Client

Client supplies data and signs within the agreed window.

03

Internal Review

Team verifies inputs, attachments, and signatures for completeness.

04

Archive Record

Final signed document stored with audit trail and metadata.

Common mistakes to avoid when preparing supplemental forms

Submitting incomplete or missing TINs which can trigger backup withholding and delay payments.
Using inconsistent names between the form and government IDs that prevent identity verification and notarization.
Failing to attach required supporting documents such as authorizations or industry-specific certificates.
Forgetting to date signatures or using initials where a full signature is required, invalidating acceptance.

Risks and penalties associated with incorrect supplemental forms

Backup Withholding: 24% withheld

1099 Penalty: $60 to $330 per form

Intentional Disregard: $660+ per form

I-9 Violations: $281–$2,789 per violation

Contract Risk: Enforcement disputes possible

Operational Delay: Service or payment hold

Comparing eSignature vendor pricing and basic capabilities

Basic pricing and capability differences among common eSignature vendors; signNow is shown first for column alignment and comparison.

	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	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Real examples showing how organizations use supplemental forms

Short case examples illustrate practical ways supplemental forms reduce friction and document required client information.

Tech Data — Internal service speed

Tech Data standardized supplemental attachments to centralize customer instructions and accelerate revenue recognition.

The new workflow reduced manual handoffs for approvals.
As a result, internal response times shortened and signed records were available directly in the customer account for billing and audit purposes.

Fertility Centers of Illinois — Compliance

The clinic used supplemental forms to collect patient-specific authorizations and consents.

The approach ensured consistent collection of clinical disclosures.
Completed forms provided auditable evidence of consent and reduced repeated intake questions during follow-up visits.

Security and compliance features to preserve form integrity

Encryption in Transit: TLS 1.2/1.3

Encryption at Rest: AES-256

HIPAA Support: BAA available

Audit Trail: Timestamps and IP logs

Certifications: SOC 2 Type II

Regulatory Coverage: ESIGN, UETA, 21 CFR Part 11

Frequently asked questions about completing and submitting Client Supplemental Forms

Common questions and concise answers to resolve processing issues, authentication problems, and legal concerns when using supplemental forms.

Need help? Contact support

How do I add or remove a signer?
Edit the routing in your sender platform before sending: add the signer email, assign the signing role, and reorder signers as needed. Resend the updated envelope to ensure all parties receive the latest version and audit trail.
Is an e-signature legally binding?
Yes, if it meets the ESIGN Act criteria: the signer intends to sign, consents to an electronic record, the signature can be attributed, and the record is reproducible. State UETA laws also apply for intrastate transactions.
When is notarization required?
Notarization is required when statute or the form specifies it; requirements vary by state and document type. For remote notarization, confirm the state's RON rules and identity-proofing obligations before proceeding.
What happens if a TIN is wrong?
An incorrect TIN can trigger backup withholding at 24% and produce IRS penalties for incorrect reporting. Correct the form promptly and provide an updated, signed record to avoid continued withholding.
Can the client withdraw consent to electronic records?
Yes. For consumer-facing financial or healthcare records, provide a clear ESIGN consumer disclosure and a method to withdraw consent; maintain a record of withdrawal per ESIGN requirements.
Which plan supports bulk sending and API access?
Bulk send is available on higher tiers and some premium plans; API and site-license usage-levels are plan-dependent. Check your vendor plan details for bulk send and developer API access.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now