Can DB135 be signed electronically?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally valid if intent, consent, attribution, and retention are satisfied.

Do I need a notary for DB135?

Not usually. Notarization depends on the document purpose and state rules. Certain filings or conveyances may require notarization or witnesses to be valid.

How should I retain executed DB135?

Retain an immutable PDF with audit trail metadata. Follow IRS, HIPAA, or other applicable retention rules; for tax records keep at least three years from filing.

What authentication is sufficient?

Email link or SMS code often suffices for business agreements; use stronger KBA, 2FA, or PKI where higher assurance or regulatory controls are required.

What if signer name doesn’t match records?

Mismatched names can trigger backup withholding or payment holds. Use legal entity names and verify TINs before executing to avoid tax reporting issues.

How to correct an executed DB135?

Execute an amendment or replacement document signed by all parties. Avoid handwritten interlineations; use an addendum referencing the original agreement and effective date.

Electronic Signature
Templates
Miscellaneous
Business Document DB135

Business Document DB135

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

BUSINESS DOCUMENT DB135 — GENERAL BUSINESS AGREEMENT

This General Business Agreement (the "Agreement") is entered into as of between Client Name: and Service Provider Name: .

Client Primary Address Service Provider Primary Address

RECITALS

WHEREAS, Client desires to retain Service Provider to perform the services described in this Agreement and Service Provider has the skill and capacity to provide such services under the terms set forth herein;

WHEREAS, Service Provider represents that it is duly authorized and able to perform the services and will comply with all applicable laws, regulations, and professional standards in performing services for Client;

WHEREAS, the parties desire to set forth in writing their respective rights and obligations with respect to the services and payment therefor.

SCOPE OF WORK

Service Provider shall perform the services described below and such additional tasks as the parties may agree in writing. The services shall be performed in a professional and workmanlike manner consistent with industry standards.

Detailed Scope of Work (describe deliverables, milestones, and acceptance criteria)

PAYMENT TERMS

Client shall pay Service Provider for the services described above in accordance with the schedule and rates set forth below. All amounts are stated in U.S. dollars unless otherwise specified.

Total Contract Amount Payment Schedule Invoices and Payment Method Late Payment Fee

TERM AND TERMINATION

This Agreement shall commence on and shall continue until unless earlier terminated in accordance with this section.

Notice Period for Termination Without Cause (number of days)

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure the breach within the notice period specified above following written notice. Upon termination, Service Provider shall deliver any completed work and Client shall pay for services performed through the effective date of termination.

CONFIDENTIALITY

Each party acknowledges that during the term of this Agreement it may receive Confidential Information of the other party. "Confidential Information" means non-public information disclosed in any form that is designated as confidential or that, by its nature, should reasonably be understood to be confidential.

The receiving party shall (a) hold Confidential Information in strict confidence, (b) not disclose Confidential Information to any third party except as expressly permitted in this Agreement, and (c) use Confidential Information solely to perform its obligations under this Agreement. The obligations of confidentiality shall survive termination for a period of years, except for trade secrets which shall remain protected for so long as they qualify as trade secrets under applicable law.

REPRESENTATIONS, WARRANTIES AND LIMITATIONS

Each party represents and warrants that it has authority to enter into this Agreement and that its performance will not violate any agreement with any third party. Service Provider warrants that services will be performed in a professional manner consistent with industry standards. EXCEPT FOR THE EXPRESS WARRANTIES SET FORTH HEREIN, NEITHER PARTY MAKES ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Neither party shall be liable to the other for consequential, incidental, special, or punitive damages except for liability arising from willful misconduct or gross negligence. The parties' aggregate liability for any claim arising under this Agreement shall not exceed the total amounts paid or payable by Client to Service Provider under this Agreement during the twelve (12) months preceding the claim.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction of without regard to principles of conflicts of law. Any dispute arising out of or relating to this Agreement shall be resolved in the courts of that jurisdiction.

ENTIRE AGREEMENT

This Agreement, including any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, and communications, whether written or oral. No amendment or modification of this Agreement shall be effective unless in writing and signed by authorized representatives of both parties.

MISCELLANEOUS

If any provision of this Agreement is held invalid or unenforceable, the remainder of the Agreement will remain in full force and effect. The parties are independent contractors and nothing in this Agreement will be construed to create a partnership, joint venture, or employer-employee relationship. Notices required by this Agreement shall be delivered to the addresses set forth above.

Client

Printed Name:

By:

Date:

Service Provider

Printed Name:

By:

Date:

What the Business Document DB135 Is and when it applies

Business Document DB135 is a standardized corporate agreement template commonly used to record business-level decisions, formalize vendor or client arrangements, and capture essential transactional terms. It consolidates party identification, effective dates, scope of services or goods, compensation or consideration, and signature blocks into a single record suitable for internal tracking, external execution, and regulatory retention. The form is designed for both printed and electronic completion and is often incorporated into larger workflows that include approvals, notarization where required, and archival for compliance and audit purposes.

Why Business Document DB135 matters for corporate recordkeeping

DB135 centralizes key contractual elements so organizations maintain consistent terms, clear execution evidence, and a reliable audit trail. Using a single, well-structured template reduces ambiguity, speeds approvals, and supports regulatory retention obligations across tax, employment, and industry-specific rules.

Core sections to include in a professional DB135

A complete DB135 includes clearly labeled sections that define parties, scope, timing, monetary terms, signatures, and attachments. Each element should be precise to reduce downstream disputes and to support eSignature verification and record retention.

Parties

Legal entity names and contact details for every party, including entity type and authorized signer details, to ensure enforceability and accurate service.

Effective Date

The start date for obligations and rights, entered as MM/DD/YYYY; this date controls performance windows and statute of limitations calculations.

Scope

A concise description of goods or services and measurable deliverables so performance can be verified and invoicing matched against contract terms.

Consideration

Clear monetary amounts, payment terms, and invoicing schedule; avoid vague phrases like 'reasonable sum' to reduce payment disputes.

Signatures

Named signatories, title blocks, signature dates, and any witness or notary fields required for legal effect in the governing jurisdiction.

Attachments

Exhibits, SOWs, insurance certificates, and schedules referenced in the agreement so the document is self-contained and audit-ready.

Stepwise process to complete and execute DB135

Follow these steps in order to prepare DB135 for signature and retention; adjust for any company-specific approvals or notarization requirements.

01

Prepare: Populate all fields and attach exhibits; confirm party names and amounts.
02

Review: Legal and finance validate terms, payment schedule, and governing law.
03

Sign: Obtain signatures, witness, or notarization as required by jurisdiction.
04

Archive: Store executed copy with audit trail and retention metadata.

Typical online workflow settings for DB135

Sample configuration options reflect common eSignature and routing needs for DB135; adapt values to internal approval chains and authentication requirements.

Field	Configuration
Authentication	Email link, SMS code, or 2FA depending on signer risk
Signature Type	Allow typed, drawn, or PKI-based signatures where required
Routing	Sequential approvals with conditional routing for exceptions
Retention	Automatic archival to document store with PDF/A output

How to share and submit DB135 electronically

Use secure eDelivery and file formats that preserve content and audit logs when circulating DB135 for signature.

Integrations: Salesforce, NetSuite, Google Workspace common
File formats: PDF, DOCX, and PDF/A supported
Authentication: Email, SMS code, or advanced 2FA options

Typical eSubmission flow for DB135

A streamlined eSubmission captures signatures, records an audit trail, and routes the executed document to archive systems and involved stakeholders.

Upload: Sender uploads final DB135 to platform
Place Fields: Add signature, date, and conditional fields
Send: Invite signers by email or create a signing link
Complete: Signer authenticates, signs, and receives executed copy

Common timing checkpoints for DB135 processing

DB135 workflows typically include internal review, signature deadlines, filing where required, and retention start dates; these checkpoints support timely compliance and vendor payment cycles.

Internal Review Due:

Allow 3–5 business days for legal and finance review

Signature Deadline:

Set a firm date for signer execution, often 7–14 days

State Filing:

If filing required, follow the state's submission deadline

Invoice Matching:

Match invoices to executed DB135 before payment

Retention Start:

Retention begins on effective date or signing date

Key milestones from draft to archived record

Track each milestone to ensure contract enforceability, timely payments, and compliance with retention obligations.

01

Draft Completion

Document finalized and exhibits attached for review

02

Approvals

Legal and finance confirm terms and risk mitigation

03

Execution

Signatures obtained, with notarization if required

04

Archival

Executed PDF stored with audit trail and metadata

Common preparation errors to avoid with DB135

Leaving party names informal or abbreviated, which delays verification and may trigger re-execution.
Incomplete payment terms or vague consideration language that leads to billing disputes and late payments.
Forgetting jurisdiction or governing law that leaves ambiguity over dispute resolution and applicable statutes.
Skipping required witness or notary steps when a jurisdiction mandates them, causing enforceability challenges.

Consequences of incorrect or incomplete DB135 entries

Tax Reporting Risk: IRC §6501 exposure; incorrect data can affect returns

1099 Penalties: IRC §6721: $60–$330 per incorrect or late form

I-9 Violations: 8 CFR §274a.2 penalties: $281–$2,789 per violation

Notarization Defect: Missing notarization can void filings in some states

Data Privacy Breach: HIPAA or state law exposure where PHI is mishandled

Contract Dispute: Ambiguities increase litigation risk and remediation costs

Security and compliance attributes relevant to DB135 records

In Transit: TLS 1.2/1.3

At Rest: AES-256 encryption

Audit Trail: Detailed timestamps and IP logs

HIPAA: BAA required for PHI

Regulatory: ESIGN and UETA compliant

Certifications: SOC 2 Type II and ISO 27001

Real-world examples showing DB135 in practice

Two concise examples show common DB135 outcomes in firms that adopted electronic execution and standardized templates.

Optica Ventures (COO)

Optica standardized execution with a shared template to reduce review cycles.

This cut negotiation time for standard vendor terms.
Brian Fitzgibbons described the interface as simple and easy-to-use, noting it improved customer interactions and reduced back-and-forth on signature logistics while preserving compliance evidence.

Martin Properties (Founder)

A small real estate firm used DB135 templates for vendor and tenant agreements.

Templates ensured consistent clauses and faster closing.
Tim Martin said he was able to process and execute documents online with compliance and security, enabling mobile and offline signing without in-person delays.

How DB135 differs from a standard commercial contract

This high-level comparison highlights common distinctions between DB135 and a general form of commercial contract to aid selection and drafting decisions.

Criteria	DB135	Standard Contract
Notarization	rare	possible
Witnesses	typically none	varies by state
Typical Use	operational agreements	wide commercial use
Tax Reporting	may require tins	depends on transaction

Representative eSignature vendor pricing and capability snapshot

Vendor pricing and feature availability vary by plan and billing cadence; signNow is presented first for direct comparison across common criteria.

	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

Frequently asked questions and solutions for DB135

Answers to common execution and compliance questions for DB135, covering signature validity, notarization, retention, and electronic submission.

Need help? Contact support

Can DB135 be signed electronically?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally valid if intent, consent, attribution, and retention are satisfied.
Do I need a notary for DB135?
Not usually. Notarization depends on the document purpose and state rules. Certain filings or conveyances may require notarization or witnesses to be valid.
How should I retain executed DB135?
Retain an immutable PDF with audit trail metadata. Follow IRS, HIPAA, or other applicable retention rules; for tax records keep at least three years from filing.
What authentication is sufficient?
Email link or SMS code often suffices for business agreements; use stronger KBA, 2FA, or PKI where higher assurance or regulatory controls are required.
What if signer name doesn’t match records?
Mismatched names can trigger backup withholding or payment holds. Use legal entity names and verify TINs before executing to avoid tax reporting issues.
How to correct an executed DB135?
Execute an amendment or replacement document signed by all parties. Avoid handwritten interlineations; use an addendum referencing the original agreement and effective date.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now