Can a vendor sign the Code electronically?

Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states. Verify exceptions such as wills or specific court filings that remain excluded.

Do you need notarization for the Code?

Generally no for internal compliance policies, but notarization may be required by state law for certain attestations or if the contract specifically demands it; check state requirements.

What level of authentication is recommended?

Use email plus OTP or higher-assurance methods for sensitive vendor relationships. Stronger authentication reduces repudiation risk and supports auditability in regulated industries.

How long should signed Codes be retained?

Retain for the contract term plus regulatory minimums. Follow IRS guidance for tax records (IRC §6501(a)) and HIPAA retention (45 CFR §164.530(j)) where applicable.

Are scanned signatures acceptable?

Scanned signatures can be acceptable if the signing event includes an audit trail that demonstrates signer intent, attribution and record retention consistent with ESIGN requirements.

What happens if a vendor falsifies information?

Contract remedies may include corrective action, penalties, suspension, or termination. Investigate promptly and document findings to support enforcement actions.

Electronic Signature
Templates
Miscellaneous
Vendor Compliance Code of Conduct

Vendor Compliance Code of Conduct

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

VENDOR COMPLIANCE CODE OF CONDUCT

This Vendor Compliance Code of Conduct ("Code") is entered into by and between Company Name: and Vendor Name: effective as of Effective Date:

WHEREAS

WHEREAS, Company Name requires that all vendors, suppliers and service providers conduct business in a lawful, ethical and socially responsible manner; and

WHEREAS, Vendor Name acknowledges and agrees to comply with the standards and commitments set forth in this Code when performing any work or supplying any goods or services to Company Name.

WHEREAS, this Code is incorporated into applicable purchasing, master services and supplier agreements between the parties and establishes minimum compliance obligations intended to protect Company Name, its employees, customers and reputation.

SCOPE OF WORK

Scope of Obligations (describe activities, goods or services covered)

STANDARDS OF CONDUCT

Vendor shall at all times comply with applicable law, exercise reasonable due diligence, and adhere to the following mandatory standards:

- Anti‑Corruption and Anti‑Bribery: Vendor shall not offer, promise, pay or authorize any bribe, kickback or other improper payment to obtain or retain business. Vendor shall maintain adequate controls to prevent corruption.

- Labor and Human Rights: Vendor shall prohibit forced labor, child labor and human trafficking; provide legally required wages and benefits; and respect the right to humane working hours and freedom of association.

- Health, Safety and Environment: Vendor shall maintain safe working conditions, comply with environmental laws, and take reasonable steps to minimize environmental impact.

- Data Protection and Confidentiality: Vendor shall protect Company data and personal information in accordance with applicable privacy laws and the confidentiality obligations in this Code.

COMPLIANCE CHECKLIST

Please indicate the areas the Vendor affirms compliance with by checking each applicable box:

Anti‑Corruption and Anti‑Bribery

Labor, Human Rights and Fair Wages

Health, Safety and Environmental Protection

Data Protection and Confidentiality

MONITORING, AUDITS AND REPORTING

Vendor shall maintain accurate records demonstrating compliance with this Code. Company reserves the right to conduct reasonable audits and inspections of Vendor facilities and records, subject to advance notice of days, except where shorter notice is required for urgent compliance concerns.

Vendor shall promptly report any actual or suspected violations of this Code to Company and shall cooperate in any investigation. Vendor shall not retaliate against any individual who reports concerns in good faith.

PAYMENT TERMS

Contract Amount Payment Schedule Late Payment Fee

If payment due under this Code and any incorporated agreements is not made within days of the due date, interest shall accrue at or the maximum rate permitted by law, whichever is lower.

TERM AND TERMINATION

This Code commences on Start Date: and continues until End Date: unless earlier terminated in accordance with this section.

Either party may terminate for convenience upon written notice to the other party provided at least days prior to the effective termination date. Either party may terminate immediately for material breach that is not cured within days after written notice of the breach.

CONFIDENTIALITY

Each party shall maintain in confidence all non‑public information disclosed by the other party in connection with this Code and any incorporated agreements ("Confidential Information"). Confidential Information shall not include information that is or becomes publicly known through no breach by the receiving party, is rightfully received from a third party without restriction, or is independently developed. The receiving party shall use Confidential Information only for purposes of performing its obligations and shall return or destroy Confidential Information upon request.

GOVERNING LAW

This Code shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. The parties agree that disputes arising under this Code shall be resolved as set forth in any controlling master supply or services agreement; absent such agreement, disputes shall be resolved exclusively in the courts located in the governing state.

ENTIRE AGREEMENT

This Code, together with any referenced purchase orders, master agreements or written attachments expressly incorporated herein, constitutes the entire understanding between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, representations and understandings. No amendment to this Code is effective unless made in writing and signed by authorized representatives of both parties.

VENDOR CERTIFICATION

By signing below, Vendor certifies that it has read, understood and will comply with the terms of this Vendor Compliance Code of Conduct. Vendor further certifies that all information provided in connection with this Code is true and accurate to the best of Vendor's knowledge.

Primary Vendor Contact Name Primary Vendor Contact Title Primary Vendor Contact Email Primary Vendor Contact Phone

Company Representative:

By:

Date:

Vendor Representative:

By:

Date:

What the Vendor Compliance Code of Conduct is and why it matters

A Vendor Compliance Code of Conduct is a formal policy document that sets behavioral, legal and operational standards vendors must follow when supplying goods or services. It defines compliance expectations for labor practices, data protection, conflict of interest disclosure, anti-bribery behavior, quality controls and reporting obligations. Organizations use the Code to manage risk, standardize vendor onboarding and create objective grounds for audits, corrective action and contract termination. The document becomes part of procurement records and helps demonstrate oversight during regulatory or customer inquiries.

Why include a Vendor Compliance Code of Conduct in your procurement process

A clear Code reduces legal and reputational risk by setting objective vendor obligations, streamlining audits, and creating contractual remedies for noncompliance. It centralizes compliance expectations so contracting, procurement and legal teams evaluate vendors consistently across the supply chain.

Typical teams and roles that complete or enforce the Code

The Vendor Compliance Code of Conduct is used across procurement, legal and compliance functions as part of vendor onboarding, renewal, and audit workflows.

Procurement and sourcing teams — collect completed Codes to validate vendor readiness before awarding contracts and to maintain a central compliance register.
Compliance and risk officers — review vendor responses, verify certifications, and track remediation actions against organizational standards.
Vendors and supplier administrators — complete the Code, attest to policies, and supply supporting documents such as certifications and corrective plans.

Maintaining signed Codes in procurement records supports consistent vendor oversight and provides documentary proof for audits, customer inquiries, and regulatory reviews.

Core sections to include in a professional Vendor Compliance Code of Conduct

A practical Code is concise, actionable, and organized so vendors can attest to specific items quickly while giving your team clear verification criteria.

Policy Scope

Define which vendors, tiers and contract types the Code applies to; include geographic or product-specific exceptions and how the Code dovetails with contract terms and SOWs.

Conduct Standards

List required behaviors and prohibitions—anti-bribery, fair labor, human trafficking prevention, environmental safeguards—and cite any accepted industry standards or certifications.

Data Protection

Specify handling of personal and sensitive data, encryption expectations, breach notification timelines, and obligations under HIPAA or other sector rules where applicable.

Reporting & Audit

Describe self-attestation, supporting documentation (certificates, inspection reports), audit rights, required notice periods and on-site inspection processes.

Remediation & Sanctions

Explain how noncompliance is addressed: corrective action plans, temporary suspension, monetary offsets, or termination rights consistent with contract language.

Signatures & Acknowledgement

Provide a clear signature block, effective date, authorized signatory name and title, and a statement confirming truthfulness under penalty of contract remedies.

Essential fields to collect on the Code

Vendor Legal Name: Exact registered name

Tax ID / EIN: TIN or EIN for tax validation

Primary Contact: Name, email, phone

Scope of Services: Short service description

Certifications: List active certificates

Authorized Signatory: Name, title, signature

Step-by-step process to complete the Vendor Compliance Code of Conduct

Follow these sequential steps to gather, verify and record a completed Code from a vendor.

01

Gather information: Collect vendor name, EIN, contact and scope of work.
02

Populate template: Fill required fields and attach supporting certifications.
03

Assign signers: Designate vendor signatory and internal approvers.
04

Archive record: Store signed Code in the procurement repository.

Configuring the online workflow for the Code

Standardize routing, authentication and retention settings so completed Codes follow a predictable approval path and are stored securely.

Field	Configuration
Signature Type	eSignature \| Digital signature optional
Authentication Method	Email link \| SMS OTP where higher assurance needed
Routing Order	Vendor -> Procurement -> Legal -> Compliance
Retention Policy	Retain signed copy in repository per records schedule

Where to send or file a completed Code

Establish a single source of truth for completed Codes so teams can retrieve validated records quickly during audits and renewals.

Vendor Portal: Primary submission channel with version control
Procurement System: Attach to vendor master record and contract
Shared Repository: Secure file storage with access controls
Compliance Inbox: Email for exceptions and remediation tracking

Digital signing and distribution considerations

Use an eSignature-enabled workflow that supports authentication, audit trails and secure storage to maintain evidentiary value for signed Codes.

Authentication: Email links, SMS OTP, or higher assurance methods
Audit Trail: Capture timestamp, IP, and signer actions
Supported Formats: PDF, Word DOCX, and PDF/A for archiving

Choose integrations that connect to procurement, document repositories and ERPs; ensure any eSignature provider supports HIPAA BAA if handling protected health information.

Key deadlines and processing expectations

Define explicit deadlines for vendor return, internal review and remediation so noncompliance can be detected and addressed promptly.

Vendor Response Time:

Typically return the completed Code within 10 business days of request

Annual Recertification:

Require yearly confirmation or sooner if material changes occur

Audit Response Window:

Provide documentation within five business days of an audit request

Effective Date:

Code becomes effective on the signer’s date of signature

Remediation Deadline:

Vendors must propose corrective action within 30 days of a finding

Typical processing milestones from issue to enforcement

A staged timeline clarifies responsibilities and escalation points from issuance through enforcement of the Code.

01

Issue Code

Procurement issues Code to vendor and logs request

02

Vendor Return

Vendor completes fields and attaches certifications

03

Internal Review

Compliance and legal review responses and documents

04

Enforcement

Implement remediation, suspension or contract remedies

Common mistakes to avoid when preparing the Code

Sending a generic document without specifying scope or the contracts it applies to, which creates ambiguity during audits and enforcement.
Failing to require or verify supporting certifications and expiry dates, causing gaps in the vendor's asserted compliance status.
Accepting scanned signatures without preserving an auditable event, which can weaken evidentiary value during disputes or regulatory reviews.
Not tracking version history or effective dates, leading to confusion about which Code applied at a particular contract milestone.

Penalties and risks if the Code is incomplete or incorrect

Contract Termination: Possible immediate termination

Monetary Fines: Fines or offsets under contract

Supply Disruption: Suspension of deliveries or services

Regulatory Liability: Exposure to enforcement actions

Reputational Harm: Customer or public trust loss

Withholding Payment: Payments paused until remediation

How the Vendor Compliance Code of Conduct compares with related documents

Use this table to distinguish the Code from similar supplier documents so teams select the right instrument for governance and contracting.

Document Type Comparison	Code of Conduct	Ethics Policy	Vendor Contract	Vendor Questionnaire
Legal Bindingness	often contractual	policy only	contractual	informational
Typical Use	ongoing compliance	internal standards	transaction terms	pre-award vetting
Signature Required				sometimes
Auditability	high	low	high	medium

Comparing eSignature vendors for executing the Vendor Compliance Code of Conduct

This pricing and capability snapshot highlights common commercial plans and essential features for running vendor Code workflows. Vendor columns list widely known starting prices and basic feature availability.

	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	Varies	Varies	Limited trial	Limited trial
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 executing and enforcing the Vendor Compliance Code of Conduct

Answers to common practical and legal questions about signing, authentication, storage and enforceability for vendor Codes.

Need help? Contact support

Can a vendor sign the Code electronically?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states. Verify exceptions such as wills or specific court filings that remain excluded.
Do you need notarization for the Code?
Generally no for internal compliance policies, but notarization may be required by state law for certain attestations or if the contract specifically demands it; check state requirements.
What level of authentication is recommended?
Use email plus OTP or higher-assurance methods for sensitive vendor relationships. Stronger authentication reduces repudiation risk and supports auditability in regulated industries.
How long should signed Codes be retained?
Retain for the contract term plus regulatory minimums. Follow IRS guidance for tax records (IRC §6501(a)) and HIPAA retention (45 CFR §164.530(j)) where applicable.
Are scanned signatures acceptable?
Scanned signatures can be acceptable if the signing event includes an audit trail that demonstrates signer intent, attribution and record retention consistent with ESIGN requirements.
What happens if a vendor falsifies information?
Contract remedies may include corrective action, penalties, suspension, or termination. Investigate promptly and document findings to support enforcement actions.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now