Establishing secure connection…Loading editor…Preparing document…

North Carolina Assumed Name Certificate

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

Overview of the North Carolina Assumed Name Certificate

A North Carolina Assumed Name Certificate (commonly called a DBA or assumed business name filing) registers a trade name used by an individual or entity that differs from its legal name. In North Carolina the certificate is typically completed to notify the public and local government of the name under which a business operates, to enable banking and contracting under that name, and to meet local registration rules. Filing is usually done at the county Register of Deeds or other designated county office and creates a public record tying the assumed name to the legal owner.

Why filing an Assumed Name Certificate matters

Registering an assumed name clarifies who operates the business, helps open bank accounts, supports contract enforcement under the trade name, and reduces the risk of consumer confusion or local noncompliance.

Why filing an Assumed Name Certificate matters

Who typically files this certificate

Filing requirements and consequences vary by county; verify local Register of Deeds rules before submitting.

  • Sole proprietors expanding brand presence without creating an LLC or corporation.
  • Small partnerships or family businesses using a public-facing trade name.
  • Existing LLCs or corporations launching products or divisions under distinct names.

Step-by-step: completing the certificate

Follow these core steps in order to prepare and submit a correct Assumed Name Certificate.

  • 01
    Gather records: Collect legal entity documents and owner ID.
  • 02
    Complete form: Fill fields exactly as instructed.
  • 03
    Sign: Authorized owner signs and dates the form.
  • 04
    Submit: File with the county Register of Deeds and pay fee.

Typical workflow for filing and using the name

This sequence shows how an assumed name moves from registration to operational use.

  • Preparation: Decide name and verify availability.
  • Registration: File certificate with county office.
  • Publication: Complete any local publication or posting if required.
  • Operational use: Open bank accounts; use name on invoices and contracts.

Configuring an online filing or e-submission workflow

Map the steps and fields when preparing an electronic form for submission or signature.

Field Configuration
Assumed Name Field Required text box; validate uniqueness before submission.
Owner Name Field Required; auto-fill from entity profile when available.
Signature Electronic signature field with date stamp and audit trail.
Payment Optional payment field for county fee collection.

Electronic submission and signature requirements

When using any eSignature provider, confirm the county Register of Deeds accepts electronically signed submissions or whether an in-person filing or paper copy is required; maintain a tamper-evident audit trail for recordkeeping.

  • File formats: PDF and DOCX accepted for most uploads
  • Authentication: Email or SMS code verification commonly used
  • Audit trail: Timestamp, IP, and signer details retained

Security and compliance considerations

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Trail: Detailed timestamps and signer metadata retained
ESIGN / UETA: Complies with ESIGN and UETA electronic signature tests
HIPAA: HIPAA-compliant workflows available with a BAA
21 CFR Part 11: Supports FDA-regulated electronic record controls
Certifications: SOC 2 Type II, ISO 27001, PCI DSS

Penalties and risks from incorrect or missing filings

Civil Liability: Misleading consumers can trigger local fines and claims
Contract Issues: Contracts under an unregistered name may be harder to enforce
Tax Exposure: Incorrect filings can trigger withholding or IRS inquiries; see IRC §6721 for reporting penalties
Banking Delays: Banks may refuse accounts without proper public record linkage
Name Conflicts: Failure to research trademarks risks infringement claims
Filing Rejection: Incomplete forms are often returned or voided by county offices

Common mistakes to avoid when preparing the certificate

  • Using an informal or inconsistent trade name across documents causes banking and contract mismatches and confusion.
  • Failing to verify name availability or trademark conflicts can lead to later legal disputes and rebranding costs.
  • Entering incomplete owner or address details may cause the county to reject the filing or delay processing.
  • Assuming electronic signatures are accepted without confirming county policy can lead to invalid filings or required re-submission.

eSignature vendor pricing snapshot for executing the certificate

Comparing vendor starting prices and core capabilities that matter when eSigning or sending the Assumed Name Certificate electronically.

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 by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently asked questions about the North Carolina Assumed Name Certificate

Answers to common questions about filing, signature methods, notarization, and recordkeeping for assumed name registrations.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users