Are electronic signatures acceptable?

Yes. Electronic signatures meet federal ESIGN Act and most state UETA laws when intent, consent, attribution, and record retention are satisfied. Exceptions exist for wills, certain court orders, and other statutorily excluded categories.

Do I need notarization?

Not always. Notarization or Remote Online Notarization is required only when state law or the parties demand it for particular instruments. If notarization is required, confirm the state-specific RON rules and identity-proofing procedures with the notary.

Who must sign the form?

An authorized corporate officer or person with delegated authority should sign. Verify internal corporate resolutions or powers of attorney that grant signing authority to avoid challenges to enforceability; record the signer's title and date.

How do I correct errors after signing?

Minor typographic errors typically require an executed amendment or corrected counterpart signed by all parties. Material changes should be handled through a formal amendment that references the original agreement and is signed by authorized representatives.

Can I use remote notarization?

Remote Online Notarization is available in most states but not universally. Confirm the state's RON statute and procedural requirements before relying on RON, and retain session recordings and notary logs per state rules.

How should I submit and store executed copies?

Use an eSignature platform that provides an immutable audit trail, timestamps, and secure PDF storage. Ensure parties consent to electronic records and maintain an archived copy with metadata and access controls for compliance and audits.

Electronic Signature
Templates
Miscellaneous
Business Interconnection Form

Business Interconnection Form

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

BUSINESS INTERCONNECTION AGREEMENT

Parties

Interconnecting Party (Company A):

Interconnection Provider (Company B):

WHEREAS

WHEREAS, Company A operates commercial business operations and requires interconnection services to exchange data, access network infrastructure and provide services to its customers; and

WHEREAS, Company B owns, operates and maintains interconnection facilities and network infrastructure and is willing to provide interconnection services to Company A on the terms and conditions set forth in this Agreement; and

WHEREAS, the parties desire to document the scope, technical responsibilities, payment terms and liabilities associated with the interconnection of their respective systems and facilities.

Scope of Work

Detailed Scope of Interconnection

Technical and Operational Information

Interconnection Location / Service Address Primary Technical Contact Estimated Capacity and Technical Specs Maintenance Window and Planned Downtime

Payment Terms

Amount Payable:

Payment Schedule

Invoicing Frequency:

Late Payment Fee:

Billing Contact

Term and Termination

Term Commencement Date:

Term Expiration Date:

Either party may terminate this Agreement for convenience upon days' prior written notice. Termination for material breach may occur immediately if the breaching party fails to cure within a commercially reasonable period following written notice.

Confidentiality

Each party shall keep confidential all proprietary, technical and commercial information disclosed in connection with this Agreement and shall not disclose such information except to those employees, contractors or advisors who have a need to know and who are bound by obligations of confidentiality no less protective than those set forth herein. Confidential information shall not include information that is (i) publicly known through no fault of the receiving party, (ii) lawfully obtained from a third party, or (iii) independently developed without reference to the disclosing party's confidential information.

Additional Confidentiality Terms (if any)

Insurance, Liability and Indemnity

Each party shall maintain insurance appropriate to its operations, including commercial general liability and professional liability coverage. Neither party shall be liable to the other for incidental, consequential or punitive damages except to the extent caused by gross negligence or willful misconduct. Each party shall indemnify, defend and hold harmless the other from third-party claims arising from the indemnifying party's negligence or breach of this Agreement.

Notices

Notice Address for Company A Notice Address for Company B

Governing Law

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

Entire Agreement; Assignment

This Agreement, including all schedules and attachments executed by the parties, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior discussions, proposals and understandings. Neither party may assign or transfer this Agreement without the prior written consent of the other party, except to a successor in interest by merger, sale of substantially all assets, or corporate reorganization.

Amendments

No amendment, modification or waiver of any provision of this Agreement shall be effective unless in writing and signed by authorized representatives of both parties.

Acknowledgments

The undersigned representatives certify that they are authorized to execute this Agreement on behalf of their respective parties and that the information provided in this Business Interconnection Agreement is true and complete to the best of their knowledge.

Company A — Printed Name:

By:

Date:

Company B — Printed Name:

By:

Date:

What a Business Interconnection Form Is and When It Applies

Business Interconnection Form is a standardized contract-like document used by two or more businesses to define operational, technical, and legal connections between entities. It records party identities, authorized contacts, data exchange points, responsibilities, security controls, service levels, billing arrangements, and termination conditions. Organizations use it to authorize system access, integrate APIs, set incident-response expectations, and document agreed operational workflows. The form often includes technical exhibits and can be executed electronically when parties consent to electronic records and signatures under applicable U.S. law.

Why this form matters for reliable integrations

Provides a single, auditable record of access rights, responsibilities, and technical requirements to reduce disputes, streamline onboarding, and support compliance with electronic-signature frameworks while aligning legal and operational expectations.

Typical parties and roles that complete this form

Common users and roles that complete this form include authorized representatives of businesses, technical leads, legal counsel, procurement, and vendor account managers.

IT/Integration Leads responsible for mapping data flows, access controls, and technical requirements.
Legal or compliance officers who confirm contract language and privacy or security obligations.
Procurement or vendor managers who oversee service terms, billing, and termination clauses.

Use the form when formalizing intercompany access, API connections, data sharing agreements, or vendor integrations requiring documented authority.

Who can sign and who prepares the form

Authorized Signer

An authorized signer is an officer or person with board-delegated authority to bind the company. Confirm corporate resolution or power-of-attorney documentation before signing to ensure enforceability and prevent internal challenges to the agreement.

Technical Lead

The technical lead is responsible for detailing integration endpoints, security controls, and operational contacts. They supply diagrams, test plans, and change-management expectations so contractual commitments align with engineering capabilities and reduce post-execution disputes or failed integrations.

Key information fields commonly required

Party Name: Full legal business name

Authorized Contact: Name, title, phone, and email

Data Types: Data categories to be shared

Access Rights: Read/write/modify permissions and limits

Security Controls: Encryption, authentication, logging required

Effective Date: Enter as MM/DD/YYYY date format

Principal risks and consequences of errors

Contract Void Risk: Signature errors may invalidate agreement

Data Breach Liability: Third-party breach fines and remediation costs

Regulatory Penalties: HIPAA or state penalties possible

Operational Downtime: Integration outages and service disruption costs

Tax Withholding: Incorrect billing may trigger withholding rules

Notary Noncompliance: Missing notarization can delay enforcement

Common preparation mistakes to avoid

Failing to specify exact data elements and formats leads to misconfigured integrations, repeated change orders, and unexpected operational outages during onboarding.
Using informal signatories without documented authority causes internal disputes or claims that the agreement was not validly executed.
Not aligning technical diagrams with contractual schedules results in mismatched expectations and additional negotiation or remediation work after project start.
Neglecting to require encryption, logging, or role-based access in the form creates compliance gaps and increases audit findings.

Step-by-step: completing the Business Interconnection Form

Follow these steps in order to prepare, review, and execute the form with minimal rework and clear accountability.

01

Draft: Populate parties, scope, and exhibits
02

Technical Review: Validate endpoints, schemas, and access rules
03

Legal Review: Confirm indemnities, SLAs, and termination
04

Sign & Archive: Collect signatures, notarize if required, then store

How routing and signature flow typically works

Routing and execution flow shows where to file, who approves, and how signatures and attachments move between parties.

Prepare Document: Create form and attach technical exhibits
Assign Signers: Add authorized contacts and signature order
Authenticate: Use email link, SMS code, or KBA
Complete Audit: System captures timestamp, IP, and activity log

Essential sections to include in a professional form

Essential sections of a Business Interconnection Form establish contacts, technical details, security terms, service levels, billing, and change control to align legal and operational expectations.

Parties

Identify each legal entity, including DBA names, jurisdiction of formation, taxpayer identification if required, and the authorized signer with title and current contact information for notices.

Scope

Describe the systems, APIs, data sets, and business processes covered. Define allowed uses, exclusions, performance expectations, and any limits on data retention or transfer.

Security

Specify required security controls such as encryption in transit and at rest, access controls, incident reporting timelines, pen testing requirements, and audit log retention.

Service Levels

Define uptime commitments, maintenance windows, notification periods for outages, remedies for missed SLAs, and escalation contacts for operational incidents.

Billing

Set invoicing frequency, accepted payment methods, dispute resolution for charges, late fee calculation, and responsibility for taxes or duties.

Termination

List termination rights, data return or destruction procedures, transition support obligations, and survival of confidentiality or indemnity clauses.

Configuring an online workflow for completion

Configure an online workflow that assigns roles, enforces required fields, and routes executed copies to designated archives automatically.

Field	Configuration
Signer Order	Sequential or parallel signing
Required Fields	Make name, signature, date mandatory
Authentication	Select email, SMS, or KBA
Archive	Auto-save PDF to cloud storage

Platform and integration requirements to consider

Ensure the signing platform supports PDF, DOCX, and API integration, plus role-based access and audit logs for compliance.

Formats: PDF, DOCX, XLSX supported
Integrations: Salesforce, NetSuite, Google Workspace
Security: TLS 1.2/1.3, AES-256 at rest

Typical timelines and processing expectations

Typical timelines include internal review, technical validation, signature routing, notarization, and final archive delivery depending on parties and state rules.

Submission Timing:

Provide upon request or before project start

Internal Review:

Allow 3–10 business days for legal and technical review

Signature Turnaround:

Electronic signing often completes within 24–72 hours

Notarization Window:

Notary scheduling adds 1–5 business days

Final Delivery:

Executed copy delivered to all parties and archives

Key milestones from intake through archive

Milestones show intake to archive stages and who performs each step in sequence for audit and compliance tracking.

01

Intake

Submit completed draft and attachments for intake review

02

Technical Validation

Confirm API endpoints, field mappings, and test credentials

03

Legal Approval

Legal reviews clauses, indemnities, and termination rights

04

Execution & Archive

Signatures collected, notarization if required, then archive copy saved

How this form differs from related agreement types

Compare a Business Interconnection Form to related agreements to decide which fits your needs and when to use each document.

Criteria	Business Interconnection Form	Data Sharing Agreement
Purpose	operational integration	data-sharing terms
Typical Elements	technical, security, slas	data use, consent, audit
When to use	api access, vendor integrations	sensitive data transfers only
Notarization	sometimes required	rarely required

Pricing and feature snapshot for eSignature platforms

Pricing and feature comparison among common eSignature vendors to consider for executing the Business Interconnection Form.

	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	Varies	Varies	Varies	Varies
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	Varies	Varies	Varies

Frequently asked questions about completing and signing the form

Answers to frequent questions about completing, signing, and storing the Business Interconnection Form, including electronic signature validity and authentication options.

Need help? Contact support

Are electronic signatures acceptable?
Yes. Electronic signatures meet federal ESIGN Act and most state UETA laws when intent, consent, attribution, and record retention are satisfied. Exceptions exist for wills, certain court orders, and other statutorily excluded categories.
Do I need notarization?
Not always. Notarization or Remote Online Notarization is required only when state law or the parties demand it for particular instruments. If notarization is required, confirm the state-specific RON rules and identity-proofing procedures with the notary.
Who must sign the form?
An authorized corporate officer or person with delegated authority should sign. Verify internal corporate resolutions or powers of attorney that grant signing authority to avoid challenges to enforceability; record the signer's title and date.
How do I correct errors after signing?
Minor typographic errors typically require an executed amendment or corrected counterpart signed by all parties. Material changes should be handled through a formal amendment that references the original agreement and is signed by authorized representatives.
Can I use remote notarization?
Remote Online Notarization is available in most states but not universally. Confirm the state's RON statute and procedural requirements before relying on RON, and retain session recordings and notary logs per state rules.
How should I submit and store executed copies?
Use an eSignature platform that provides an immutable audit trail, timestamps, and secure PDF storage. Ensure parties consent to electronic records and maintain an archived copy with metadata and access controls for compliance and audits.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now