Can a counter be signed electronically?

Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and state UETA statutes, subject to statutory exceptions and any needed notarization or witness requirements.

When is notarization required?

Notarization is required when a jurisdiction or registry specifically requires an acknowledgement for recordability, and some deeds or filings will still need a notarized signature for recording.

What authentication is advisable?

Use authentication commensurate with risk: email link for low-risk counters, SMS or knowledge-based authentication for sensitive transactions, and multi-factor or advanced signer verification for high-value matters.

How long must I keep execution records?

Retain signed counters per applicable standards: at least three years for tax records (IRC §6501(a)), six years for HIPAA-related materials (45 CFR §164.530(j)), and longer where state law or industry regulation requires it.

What if a signer’s name does not match records?

Mismatched names can create enforceability questions; correct legal names should be used and any known variations explained in an attestation or corporate capacity statement.

How do I amend an already-signed counter?

Create a clear written amendment or restatement signed by authorized parties. For material changes, obtain fresh signatures rather than relying on implied consent to preserve enforceability.

Counter Agreement SHA

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

COUNTER AGREEMENT SHA

This Counter Agreement SHA (the Agreement) is entered into as of Effective Date: by and between:

Party A Name: Address:

Party B Name: Address:

RECITALS

WHEREAS, Party A and Party B previously entered into a shareholding agreement and related transaction documents (the Original SHA) and wish to amend certain terms by mutual agreement; and

WHEREAS, the parties desire to document their counterproposal, specifying revised obligations, payment terms and confidentiality obligations to govern their relationship going forward.

NOW, THEREFORE, in consideration of the mutual covenants set forth herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. SCOPE OF WORK

1.1 Services: Party A shall perform, and Party B shall accept, the services and deliverables as described below. The parties acknowledge that this Scope of Work amends any conflicting provisions of the Original SHA to the extent expressly stated in this Agreement.

Detailed Scope of Work

2. PAYMENT TERMS

2.1 Consideration: In full consideration for performance of the Scope of Work, Party B shall pay Party A the amounts and on the schedule set forth below. All payments shall be made in lawful currency and in immediately available funds.

Total Amount Payable Payment Schedule Late Payment Fee

If any payment is not received by the due date, interest shall accrue at the lesser of (i) the rate of or (ii) the maximum rate permitted by applicable law. In addition, the non-defaulting party may suspend performance after providing days' written notice to cure.

Invoicing Instructions

3. TERM AND TERMINATION

3.1 Term: This Agreement shall commence on the Start Date: and shall continue until the End Date: unless earlier terminated as provided herein.

3.2 Termination for Convenience: Either party may terminate this Agreement for convenience upon providing written notice at least days prior to the effective date of termination.

3.3 Termination for Cause: Either party may terminate immediately upon written notice if the other party materially breaches any obligation under this Agreement and fails to cure such breach within days after receipt of written notice specifying the breach.

4. CONFIDENTIALITY

4.1 Definition: "Confidential Information" means all non-public information disclosed by one party to the other, whether in written, oral or electronic form, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure.

4.2 Obligations: Receiving party shall (a) hold Confidential Information in confidence using at least the same degree of care it uses to protect its own confidential information, but no less than reasonable care; (b) use Confidential Information only to perform its obligations under this Agreement; and (c) not disclose Confidential Information to any third party except to employees, contractors or advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those in this Agreement.

4.3 Exceptions: Confidential Information does not include information that: (a) is or becomes publicly available through no wrongful act of the receiving party; (b) is rightfully received from a third party without restriction; (c) was known to the receiving party prior to disclosure; or (d) is independently developed by the receiving party without use of the disclosing party's Confidential Information.

5. GOVERNING LAW; DISPUTE RESOLUTION

5.1 Governing Law: This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws principles.

5.2 Venue: The parties submit to the exclusive jurisdiction of the state and federal courts located in the county and state specified by the governing law clause for any action arising out of or relating to this Agreement, and waive any objection to venue or inconvenient forum.

6. MISCELLANEOUS

6.1 Entire Agreement: This Agreement, together with any exhibits or schedules expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written.

6.2 Amendments: No amendment or waiver of any provision of this Agreement shall be effective unless in writing and signed by both parties.

6.3 Assignment: Neither party may assign or transfer its rights or obligations under this Agreement without the prior written consent of the other party, except to an affiliate or in connection with a merger or sale of substantially all of its assets, provided the assignee assumes the assigning party's obligations in writing.

6.4 Severability: If any provision of this Agreement is held to be invalid or unenforceable, such provision shall be severed and the remainder of this Agreement shall remain in full force and effect.

6.5 Notices: Any notice required or permitted under this Agreement shall be in writing and delivered by hand, certified mail, or overnight courier to the addresses set forth above or to such other address as a party may designate by notice in accordance with this Section.

REPRESENTATIONS AND COVENANTS

Each party represents and warrants that it has the full right, power and authority to enter into and perform this Agreement and that the execution and delivery of this Agreement and the performance of its obligations hereunder have been duly authorized.

Party A

Printed Name:

By:

Date:

Party B

Printed Name:

By:

Date:

What a Counter Agreement SHA Is and When It’s Used

A Counter Agreement SHA is a formal written response that modifies, amends, or objects to a proposed Shareholders' Agreement (SHA). It typically restates key provisions, proposes alternative terms, and identifies items that remain unresolved between the parties. The document functions as a negotiated counterpart to the original SHA, documenting concessions, conditions precedent, and timing for execution. In many transactions it serves both as a negotiation record and, once signed by all parties, as an operative contractual instrument that can alter governance, transfer restrictions, vesting schedules, or buyout provisions.

Why a Counter Agreement SHA Matters

A clear counter agreement protects negotiating parties by documenting proposed changes, preserving bargaining positions, and creating a paper trail that supports later enforcement. Well-drafted counters reduce ambiguity in shareholder rights and timing while clarifying conditions precedent and execution mechanics under ESIGN and state electronic transaction laws.

Who Typically Prepares and Signs a Counter Agreement SHA

Parties on both sides of a financing, acquisition, or internal restructuring commonly prepare counters to preserve negotiation positions and document material changes.

Lead investors and their counsel reviewing governance and protective provisions.
Founders or executive leadership negotiating vesting, transfer restrictions, or buyout rights.
Corporate general counsel or outside counsel finalizing enforceability and signature authority.

Counsel, corporate officers, and authorized shareholders usually review and approve the counter before execution to ensure authority and compliance.

Representative Signers and Their Roles

General Counsel

General counsel typically reviews the counter for corporate authority, statutory compliance, and alignment with existing charter and bylaws, then certifies that signers have corporate authorization to bind the entity.

Founder / CEO

Founders or the CEO often negotiate commercial terms, confirm the business intent of changes, and execute the counter on behalf of the company when board or shareholder approvals are already satisfied or delegated.

Essential Elements to Include in a Professional Counter Agreement SHA

A complete counter should be organized, reference the original SHA precisely, and clearly state which clauses are replaced, added, or removed to avoid ambiguity during execution and enforcement.

Reference to original

Identify the original SHA by date and parties, then state that the counter modifies specified sections rather than superseding the entire agreement unless expressly stated.

Redlined provisions

Present changed language using tracked changes or side-by-side clauses so each replacement term is unambiguous for counterparties and for later court or arbitration review.

Effective date

Specify the effective date for modified provisions and whether the counter is conditional on other approvals, funding, or corporate actions to avoid disputed commencement questions.

Signature blocks

Include clear signature blocks for each party with printed name, title, corporate authority statement, and execution date to confirm who is legally bound.

Conditions precedent

List any required approvals, regulatory clearances, or third-party consents that must occur before the counter becomes operative to avoid premature obligations.

Integration clause

State how the counter interacts with the original SHA, whether it amends specific sections or supersedes prior inconsistent language, to reduce interpretive disputes.

Step-by-Step: Preparing and Executing a Counter Agreement SHA

Follow these sequential steps to prepare a defensible counter and complete execution in line with company governance and applicable e-signature rules.

01

Draft the counter: Identify changed clauses and draft precise replacement language for each item.
02

Internal review: Obtain board or authorized officer review to confirm authority and compliance with corporate documents.
03

Share with counterparty: Deliver a clean and a redlined version to counterparties and request confirmation of receipt.
04

Execute and retain: Have authorized signers sign, notarize if required, and securely retain copies with audit trail metadata.

Typical Digital Workflow Settings for Counters

Configure the signing workflow to match negotiation sequencing, authentication needs, and retention requirements before sending the counter for signature.

Field	Configuration
Authentication method	Email link, SMS code, or advanced authentication depending on transaction sensitivity
Field types	Signature, date, initials, and conditional text fields for variable clauses
Routing order	Sequential or parallel signer order configured to match negotiated execution sequence
Retention policy	Preserve signed copy and audit trail for jurisdictional retention requirements

How Electronic Execution and Exchange Usually Works

A reproducible e-signing flow reduces friction and creates evidence of intent, attribution, and retention required under ESIGN and UETA.

Upload document: Sender uploads the counter draft and configures fields.
Assign signers: Add signer emails, roles, and signing order.
Authenticate signer: Signer verifies identity via link, SMS, or KBA where required.
Capture audit trail: System records timestamps, IP, and actions for legal defensibility.

Technical and Platform Considerations for Electronic Counters

Choose a platform that supports the authentication level, audit trail, and export formats your transaction requires.

Formats supported: PDF, DOCX, HTML
Integrations: Salesforce, NetSuite, Google Workspace
Advanced auth: SMS, KBA, SSO options

Ensure the platform can produce a tamper-evident signed PDF with a complete audit trail and allows secure storage to meet record-retention obligations.

Common Timing and Deadline Considerations

Track explicit response windows, effective dates, and any filing or notarization timing so parties meet negotiated and legal deadlines.

Negotiation response window:

Typical request to respond within 7–14 days of receipt

Effective date:

State whether effective on signature or a specified MM/DD/YYYY

Notary/RON session:

Schedule within 30 days of final signature when notarization is required

Post-execution filing:

File any required notices with registries promptly per local rules

Record retention start:

Retention runs from execution date or last effective amendment

Key Milestones from Draft to Recorded Agreement

A typical milestone sequence helps project-manage the counter from draft to executed and stored record.

01

Draft Complete

All replacement clauses drafted and internal approvals obtained.

02

Counterparty Review

Counterparty reads and proposes any additional edits or acceptances.

03

Execution

Authorized signers sign and notarize if required.

04

Store and File

Signed copy archived and any registries or corporate records updated.

Comparison: Electronic Signature vs Wet-Ink Notarized Execution

Understand how an electronically signed counter compares with traditional notarized wet-ink execution for enforceability and recording.

Criteria	Electronic Signature	Wet-Ink Notarized
Legal status	yes (esign)
Remote notarization	depends on state
Witness required	varies by state	often required
Recordability	accepted by many registries	universally accepted

eSignature Pricing and Feature Comparison

Vendor pricing and core features vary. The table shows starting prices and common feature presence to guide platform selection for document execution.

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

Real-World Examples of Counters and Execution Outcomes

These examples illustrate how organizations used counters to document negotiated changes and complete execution with secure electronic workflows.

Optica Ventures

Optica negotiated investor protections and minority transfer limits

Used clear redlines to speed agreement review
The team executed the counter electronically, retained an audit trail, and avoided follow-up disputes by documenting each concession and approval path.

Martin Properties

A property firm used a counter to amend transfer restrictions

They required notarization for recordable clauses
Execution combined in-person notarization with an electronic audit trail so both recording and corporate records were satisfied.

Common Preparation Errors to Avoid

Failing to identify the exact clause being amended, which creates interpretive gaps and litigation risk.
Using vague language for conditions precedent, causing disputes over whether obligations became effective.
Permitting unauthorized signers to execute, which can render the counter unenforceable against the entity.
Neglecting to preserve an audit trail or electronic certificate that proves intent and attribution.

Key Legal Risks If the Counter Is Incorrect or Incomplete

Unenforceability: Missing authority or improper signatures can void the agreement

Statutory exceptions: Certain transaction types remain excluded from ESIGN/UETA

Filing penalties: Late or incorrect regulatory filings may trigger fines

Tax exposure: Misstated financial terms can create reporting liabilities

Privacy breaches: Improper handling of protected data risks HIPAA or state penalties

Evidence gaps: No audit trail weakens ability to prove intent or execution

Practical Document Features to Include Before Sending

Include these practical items to streamline review, execution, and downstream recordkeeping for the counter.

Templates

Use standardized redline templates that preserve revision history and clearly label amended clauses so reviewers can compare versions quickly.

Audit trail

Ensure the signing platform records timestamps, IP addresses, and signer authentication to support attribution and retention obligations.

Export options

Allow signed PDFs and native DOCX exports so legal teams can archive both final and editable copies of the executed counter.

Version control

Maintain a version log that lists drafts, review dates, and who provided material edits during negotiation stages.

Frequently Asked Questions About Counter Agreement SHA Execution

Answers address common process, validity, and retention concerns when preparing or electronically signing a counter agreement.

Need help? Contact support

Can a counter be signed electronically?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and state UETA statutes, subject to statutory exceptions and any needed notarization or witness requirements.
When is notarization required?
Notarization is required when a jurisdiction or registry specifically requires an acknowledgement for recordability, and some deeds or filings will still need a notarized signature for recording.
What authentication is advisable?
Use authentication commensurate with risk: email link for low-risk counters, SMS or knowledge-based authentication for sensitive transactions, and multi-factor or advanced signer verification for high-value matters.
How long must I keep execution records?
Retain signed counters per applicable standards: at least three years for tax records (IRC §6501(a)), six years for HIPAA-related materials (45 CFR §164.530(j)), and longer where state law or industry regulation requires it.
What if a signer’s name does not match records?
Mismatched names can create enforceability questions; correct legal names should be used and any known variations explained in an attestation or corporate capacity statement.
How do I amend an already-signed counter?
Create a clear written amendment or restatement signed by authorized parties. For material changes, obtain fresh signatures rather than relying on implied consent to preserve enforceability.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now