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!
Overview of the North Carolina Assumed Name Certificate
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.
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
-
01Gather records: Collect legal entity documents and owner ID.
-
02Complete form: Fill fields exactly as instructed.
-
03Sign: Authorized owner signs and dates the form.
-
04Submit: File with the county Register of Deeds and pay fee.
Typical workflow for filing and using the name
-
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
| 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
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
| 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
-
What is an Assumed Name Certificate?
It is a public filing that registers a trade name used by a person or business owner. The certificate links the trade name to the legal owner and creates a county-level public record for banking and contracting purposes.
-
Where do I file in North Carolina?
Most filings are completed at the county Register of Deeds where the business operates; some counties provide online submission. Confirm the specific county office for procedures and accepted payment methods.
-
Can the form be signed electronically?
Electronic signatures are generally valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, but acceptance of electronic filings by county offices varies; check with the county Register of Deeds before relying on e-submission.
-
Is notarization required?
Notarization is not universally required for all assumed name filings; requirements depend on state and county practice. Confirm local rules because some counties request notarized signatures for recordability.
-
How do I change or cancel a filing?
To amend or cancel, file the county's correction or cancellation form following the county's instructions. Keep copies of both original and cancellation filings for records and bank requirements.
-
How long should I retain the records?
Retain the original filing and supporting documents for the active term plus several years afterward; federal and industry rules apply, for example, IRS records are generally kept three years under IRC §6501(a).
be ready to get more
Join over 28 million airSlate SignNow users