Can the CoS & S32 be e-signed?

Yes. Under the ESIGN Act (15 U.S.C. §7001) and state UETA laws, electronic signatures are generally enforceable if intent, consent, attribution, and record retention are present.

Is notarization required?

Not always. Some filings or deeds require notarization; verify the target agency or county recorder. If a notary is required, consider Remote Online Notarization where allowed.

Are witness signatures necessary?

Witness requirements vary by state and by document type. For certain deeds or powers of attorney, two witnesses may be required; consult state law before execution.

How should I store the executed document?

Retain the final signed PDF with its audit trail in a secure repository, maintain backups, and follow retention rules applicable to your industry and jurisdiction.

What authentication level is recommended?

For routine approvals, email plus access code may suffice. For regulatory, healthcare, or high-value transactions, require stronger authentication such as SSO, SMS code, or certificate-based verification.

Can I update the document after signing?

Yes, but treat post-signature changes as amendments: create a new amendment document, obtain fresh approvals, and preserve both original and amendment records for auditability.

Electronic Signature
Templates
Miscellaneous
Business Document CoS & S32

Business Document CoS & S32

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

Business Document CoS & S32

This General Business Agreement ("Agreement") is entered into effective as of by and between:

Party A Name:

Party A Address

Party B Name:

Party B Address

Recitals

WHEREAS, Party A is engaged in the business activity described above and requires services, deliverables and compliance documentation, including a Certificate of Service (CoS) evidencing receipt and performance of obligations; and

WHEREAS, Party B represents that it possesses the expertise, personnel and authority to perform the services and to comply with Section 32 obligations set forth in this Agreement; and

WHEREAS, the parties desire to set forth their mutual understandings, responsibilities, payment terms, confidentiality obligations and dispute resolution provisions in writing.

Scope of Work

Description of Services and Deliverables (describe specific tasks, milestones and acceptance criteria):

Attachments and Supporting Materials: indicate if Certificate of Service (CoS) or other exhibits will be provided upon completion:

Certificate of Service (CoS) to be attached upon delivery Section 32 compliance exhibit to be provided

Payment Terms

Total Contract Amount Payment Schedule and Milestones Late Payment Fee Late Fee Grace Period (days)

Term and Termination

Term Commencement Date: Term Expiration Date:

Notice Period for Termination without Cause (days)

Either party may terminate this Agreement for material breach if the breaching party fails to cure such breach within the notice period specified above. Termination shall be without prejudice to any accrued rights or remedies.

Confidentiality

Each party shall maintain in strict confidence all non-public information disclosed by the other party that is identified as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). Confidential Information does not include information that is: (a) publicly available through no fault of the receiving party; (b) already lawfully known to the receiving party at the time of disclosure; or (c) lawfully obtained from a third party entitled to disclose it. The receiving party shall not use Confidential Information except as necessary to perform its obligations under this Agreement.

Confidentiality Duration (years)

Section 32 Compliance

The parties acknowledge obligations described as Section 32 obligations, which require specific certifications, recordkeeping and reporting as set forth in this Agreement. Party B shall perform any inspections, testing and certification required under Section 32 and shall deliver an executed Section 32 compliance exhibit together with the Certificate of Service upon completion of the services. Failure to meet Section 32 requirements shall constitute a material breach.

Notices

Notices required under this Agreement shall be in writing and delivered to the addresses set forth below or to such other address as either party may designate by written notice to the other.

Notice Address for Party A Notice Address for Party B

Governing Law; Dispute Resolution

This Agreement shall be governed by and construed in accordance with the laws of without regard to conflict of laws principles. The parties shall first attempt to resolve disputes through good faith negotiation; if unresolved, disputes shall be resolved by binding arbitration in the jurisdiction named above unless otherwise agreed in writing.

Indemnification

Each party shall indemnify and hold harmless the other party from and against any third-party claims, liabilities, damages and expenses arising from the indemnifying party's breach of this Agreement, negligence or willful misconduct, subject to the indemnified party's compliance with claim notice and mitigation obligations.

Entire Agreement

This Agreement, including any exhibits, attachments and the Certificate of Service, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. No amendment 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 remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the prior written consent of the other, except to an affiliate or in connection with a sale of substantially all of its assets.

Party A:

By:

Date:

Party B:

By:

Date:

What the Business Document CoS & S32 Is and When it Applies

The Business Document CoS & S32 is a structured corporate document used to record a business-level certificate of service, approval, or compliance action and an associated S32 schedule or signature appendix. It identifies the parties, describes the transaction or notice, sets an effective date, attaches exhibits or schedules, and collects required authorizing signatures. Organizations use it for internal approvals, external notices, contract attachments, or regulatory filings where a formal certificate and a compact signature appendix are required to evidence delivery and acceptance.

Why the CoS & S32 Matters for Corporate Records

Using a consistent CoS & S32 clarifies who delivered notices or approvals, creates an auditable record of timing and parties, and reduces disputes over service and authorization. Proper completion supports corporate governance, regulatory compliance, and defensible recordkeeping.

Who Typically Completes or Signs This Document

Accurate signatory selection and role validation reduce legal risk and speed processing when filing, serving, or recording the document with third parties.

Corporate Legal Teams and Counsel responsible for compliance and formal notices, ensuring accuracy and attachment of required exhibits.
Operations and Contract Managers who execute approvals, record service dates, and coordinate signatory routing across departments.
External Agents and Vendors authorized to accept service or provide certified delivery on the company’s behalf.

Step-by-Step: Completing and Circulating the CoS & S32

Follow a consistent sequence to prepare, approve, and distribute the document to maintain chain-of-custody and evidentiary value.

01

Prepare Document: Populate parties, effective date, and S32 appendix references.
02

Attach Exhibits: Add schedules, exhibits, and supporting delivery proof.
03

Authorize Signers: Confirm authorized individuals and obtain signatures in proper order.
04

Record and Distribute: Save final copy, log delivery, and send to recipients.

Where the CoS & S32 Goes After Signing

Routing depends on purpose: internal retention, external service, regulatory filing, or contract counterpart delivery. Each destination has different record and proof needs.

Internal Records: Store executed original in contract repository with index metadata.
Counterparty Delivery: Send signed copy to the other party and keep proof of receipt.
Regulatory Filing: File with the appropriate agency or attach to a submission package.
Legal Hold: Preserve in compliance with litigation hold instructions when required.

How to Configure an Online CoS & S32 Workflow

Design the workflow to collect information, route for approvals, and capture a tamper-evident record of delivery and signature.

Field	Configuration
Signature Order	Set sequential or parallel routing per approval hierarchy.
Authentication	Require email plus SMS code or stronger ID verification for high-risk signers.
Conditional Fields	Show S32-related fields only when the appendix is required.
Audit Trail	Enable full event logging (timestamps, IP, actions).

Technical Considerations for eSigning and eSubmission

Ensure your chosen stack preserves a reproducible record and supports export to archival systems for compliance and eDiscovery.

Integrations: Connectors for CRM, ERP, cloud storage, and project systems reduce manual uploads.
File Formats: Use PDF or DOCX formats; ensure signed PDF preserves audit metadata.
Authentication: Support for SMS, KBA, SSO, or certificate-based verification as needed.

Security and Compliance Essentials for CoS & S32 Records

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Audit Trails: Immutable timestamped event logs for each action

Certifications: SOC 2 Type II and ISO 27001 recognized

HIPAA Support: BAA available where protected health data exists

21 CFR Part 11: Controls available to meet FDA-regulated record needs

Accessibility: WCAG 2.0 Level AA compliance for users

Core Sections to Include in a Professional CoS & S32

A complete CoS & S32 contains standardized sections so recipients and recordkeepers can quickly verify authority, timing, and attached exhibits.

Parties

Full legal names, contact details, and organizational role for each entity. Avoid DBAs where legal identity matters and include state of formation for companies.

Certificate of Service

A clear statement of how and when the document or notice was served, including method, date, and delivery tracking identifiers when available.

S32 Appendix

A concise schedule or signature appendix referencing specific exhibits or clauses. Include version numbers and attachment filenames for unambiguous reference.

Authority and Title

Signatory names, official titles, and a statement confirming their authority to sign on behalf of the listed party; reference any POA if used.

Effective and Delivery Dates

Separate fields for effective date and service date; both are commonly used to trigger obligations or notice windows.

Exhibit Index

A listed index of attachments, with page counts and brief descriptions to simplify review and preserve evidentiary context.

Best Practices for Accurate, Efficient Completion

Follow routine checks and process controls to reduce rework, support audits, and shorten turnaround times for signature collection.

Standardize Templates

Use a single approved template to avoid missing clauses, inconsistent headings, or incorrect appendix references that create disputes.

Validate Signers

Confirm signatory authority before circulation and log role and approval limits to prevent unauthorised agreements.

Use Conditional Logic

Show only relevant S32 fields when required. Conditional fields reduce signer confusion and lower error rates.

Preserve Proof

Retain delivery confirmations, tracking numbers, and the platform audit trail to support compliance or dispute resolution.

Common Mistakes to Avoid When Preparing CoS & S32

Using an informal name or DBA instead of the legal entity name causing mismatch with public filings or tax records.
Failing to attach the exact S32 appendix referenced, leaving the document ambiguous during review or enforcement.
Collecting initials instead of full signatures when the document requires formal authorization, weakening enforceability.
Omitting service details (method, tracking number, or recipient) that are necessary to prove timely delivery.

Risks and Legal Consequences of Inaccurate or Late Submission

Contract Disputes: Missing or incorrect service evidence can lead to contested notice windows and breach claims

Regulatory Penalties: Failure to file required notices may trigger agency fines or enforcement

Tax Withholding: Incorrect payee identity can cause backup withholding under IRS rules

I-9 Exposure: Employment form errors risk fines ranging widely per violation

Evidence Loss: Absent audit trail, proving delivery or consent becomes costly and uncertain

Contract Invalidity: Unauthorised signatures or improper witnessing may render the document void

Key Dates and Timing Considerations

Track effective dates, service deadlines, and filing windows. Some related regulatory deadlines follow fixed schedules and must be observed.

Effective Date:

The date obligations begin; enter as MM/DD/YYYY.

Signature Deadline:

Set a clear signing cutoff to avoid uncertainty about acceptance.

Filing Window:

If filing with an agency, confirm that submission aligns with their published deadlines.

Tax Reporting:

When related to tax forms, remember Form 1099-NEC recipient deadline is Jan 31.

Record Retention Start:

Retention periods typically begin on the document creation or filing date.

Real-World Examples of CoS & S32 Usage

Practical examples show how organizations reduce turnaround and maintain compliance when using a standard CoS & S32 template.

Optica Ventures — COO

Optica standardized its certificate and appendix to reduce review time by centralizing attachments.

This avoided version conflicts across deals.
The team reports faster approvals and fewer follow-up requests because each S32 referenced a single, auditable exhibit location.

Martin Properties — Founder

Martin Properties digitized its CoS & S32 to collect remote approvals across offices.

Mobile signing allowed onsite confirmations.
As a result, closings proceeded without in-person signings and the company retained a complete timestamped record for audits.

Who Has Authority to Sign the CoS & S32

Corporate Officer — CFO

A chief officer with delegated signing authority signs financial certifications and service statements. Document an internal resolution or delegated authority to support the officer’s signature in disputes.

Authorized Agent — Contract Manager

Designated managers may sign operational certificates when granted written authority; the signing record should reference the delegation document and the agent’s title.

Comparing eSignature Vendors for CoS & S32 Workflows

Pricing and feature availability vary by vendor and plan. The table below shows starting price and selected feature availability across common providers.

	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 trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	Varies
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 the Business Document CoS & S32

Answers to common questions about valid signatures, notarization, retention, and digital completion processes for this document.

Need help? Contact support

Can the CoS & S32 be e-signed?
Yes. Under the ESIGN Act (15 U.S.C. §7001) and state UETA laws, electronic signatures are generally enforceable if intent, consent, attribution, and record retention are present.
Is notarization required?
Not always. Some filings or deeds require notarization; verify the target agency or county recorder. If a notary is required, consider Remote Online Notarization where allowed.
Are witness signatures necessary?
Witness requirements vary by state and by document type. For certain deeds or powers of attorney, two witnesses may be required; consult state law before execution.
How should I store the executed document?
Retain the final signed PDF with its audit trail in a secure repository, maintain backups, and follow retention rules applicable to your industry and jurisdiction.
What authentication level is recommended?
For routine approvals, email plus access code may suffice. For regulatory, healthcare, or high-value transactions, require stronger authentication such as SSO, SMS code, or certificate-based verification.
Can I update the document after signing?
Yes, but treat post-signature changes as amendments: create a new amendment document, obtain fresh approvals, and preserve both original and amendment records for auditability.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now