Is an AKA Statement legally binding?

Yes. When signed and executed with intent, an electronic or paper AKA statement can be binding under the ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA where adopted; ensure signer intent, consent, attribution, and retention are satisfied.

Can I e-sign this document?

Yes. Electronic signatures meeting ESIGN/UETA evidentiary standards are acceptable for most private transactions; certain narrow exceptions like wills or court filings remain excluded.

Do I need a notary or witnesses?

Not typically for vendor or bank use, but some recipients or state laws may request notarization or witnesses. Check recipient requirements and state-specific rules before skipping notarization.

How do I correct a mistake after signing?

Prepare an amended statement referencing the original, have the authorized signer execute and date it, and distribute to all prior recipients to replace the earlier version.

Who should sign the statement?

An authorized representative with corporate authority (owner, officer, or designated agent) should sign; include title and contact information to establish authority.

How long should I keep the signed statement?

Follow applicable retention guidance: at least 3 years for tax records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)), and longer where industry rules apply.

Electronic Signature
Templates
Miscellaneous
Business AKA Statement

Business AKA Statement

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

BUSINESS AKA STATEMENT

Business Legal Name:

Assumed / Trade Name(s) Principal Business Address

County or Jurisdiction of Filing: Effective Date of Assumed Name:

WHEREAS

WHEREAS, the registrant whose legal name appears above is engaged in lawful business activity within the stated jurisdiction and wishes to conduct business under one or more assumed names to distinguish certain lines of trade and to identify services offered to the public; and

WHEREAS, the registrant declares that the assumed name(s) listed in this statement are not adopted for the purpose of evading creditors or avoiding legal obligations and that no name included herein infringes upon the registered trade name or trademark rights of any third party of which the registrant has actual knowledge; and

WHEREAS, the registrant elects to file this statement to provide public notice of the assumed name(s) under which the registrant will carry on business and to comply with applicable local filing requirements;

STATEMENT OF ASSUMED NAME

The registrant hereby certifies, under penalty of perjury, that the information contained in this Business AKA Statement is true and correct. The registrant will conduct business under the following assumed name(s) at the principal address listed above for the following general business purpose(s):

Business Purpose

ENTITY TYPE

Indicate legal form of registrant (check all that apply):

Sole Proprietorship Partnership Corporation Limited Liability Company (LLC) Other:

SCOPE OF WORK

Describe the specific business activities that will be performed under the assumed name(s). Include goods, services, sales channels, and any operational limitations or specialties.

PAYMENT TERMS

The registrant acknowledges any fees, charges, or consideration related to use of the assumed name as agreed between parties or imposed by the filing jurisdiction. Specify fee arrangement below if applicable:

Fee / Amount Payment Schedule Late Payment / Delinquency

TERM AND TERMINATION

This Business AKA Statement shall be effective as of the date stated above and shall remain in effect until terminated in accordance with the provisions below or as required by applicable law.

Commencement Date: Termination Date (if any):

Notice Period for Voluntary Termination

CONFIDENTIALITY

The registrant acknowledges that certain records, lists, or other business information associated with the use of the assumed name may be confidential. Except as required by law or a competent judicial or administrative authority, such confidential information shall not be disclosed by any party without the prior written consent of the registrant.

By checking the box below, the signatory affirms understanding of and agreement to the confidentiality undertaking set forth above.

I acknowledge and agree to the Confidentiality clause.

GOVERNING LAW

This Business AKA Statement shall be governed by and construed in accordance with the laws of the jurisdiction in which it is filed. Any dispute arising under or relating to this statement shall be resolved in the courts of that jurisdiction.

Governing Jurisdiction

ENTIRE AGREEMENT

This Business AKA Statement, together with any attachments, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings and agreements, whether written or oral. Any amendment or modification must be in writing and signed by an authorized signatory of the registrant.

CERTIFICATION AND ACKNOWLEDGMENT

I certify, under penalty of perjury, that the information provided in this Business AKA Statement is true and correct to the best of my knowledge, and that I am authorized to execute this document on behalf of the registrant named herein.

Registrant / Business

Printed Name:

By:

Date:

Title / Capacity:

Filing Agent / Authorized Representative

Printed Name:

By:

Date:

Title / Capacity:

What a Business AKA Statement Is and when it’s used

A Business AKA Statement documents an entity's alternative trade names, commonly known as "doing business as" (DBA) or AKA names, alongside core identifying information. Typical contents include the legal entity name, DBA/AKA names, taxpayer identification number, principal address, authorized signer, and effective date. The form is used to confirm identity for vendors, banks, payers, licensing agencies, and internal records, and it helps align contract, payroll, and tax records. It can be a standalone sworn statement or an attachment to vendor onboarding and formation filings for recordkeeping and compliance.

Why a clear Business AKA Statement matters

A precise Business AKA Statement reduces payment and tax matching errors, supports vendor onboarding, and documents trade name use for regulatory or licensing reviews.

Typical users and recipients of an AKA statement

Organizations that prepare or request Business AKA Statements range across operations, compliance, and finance teams.

Small business owners setting up DBAs or vendor accounts
Accounts payable and vendor management teams verifying payee identity
Compliance or legal teams documenting trade name use for licensing

Recipients commonly keep the statement with vendor files, tax records, or licensing documentation to ensure consistent identity matching.

Representative signers and requestors

Owner / CEO

An owner or chief executive typically signs to attest to the accuracy of the business's legal name and DBAs. This signer must be authorized and may be asked for ID to corroborate identity.

Finance Lead

Accounts payable or finance officers request and retain AKA statements to ensure vendor payments and tax reporting match the correct taxpayer identification information and bank account details.

Core elements included in a professional Business AKA Statement

A complete statement presents consistent, verifiable data fields and a clear attestation from an authorized signer to avoid downstream mismatches.

Legal Entity

The company's registered legal name exactly as on formation documents or the most recent amendment; mismatch risks payment or tax reporting errors.

AKA / DBA Names

List each trade name or alias used in commerce, with start dates and, where applicable, jurisdiction of registration to support vendor and licensing checks.

Taxpayer ID

Provide EIN or SSN (for sole proprietors) in the format required by payers to prevent backup withholding and ensure correct 1099/W-9 processing.

Principal Address

Full street address, city, state, and ZIP; P.O. boxes alone are insufficient for legal service or certain vendor onboarding processes.

Authorized Signer

Name, title, and contact of the person attesting to the statement; include identification method or notarization if required by the requester.

Effective Date

The date the AKA began or the statement was executed; this establishes when the trade name became operational for recordkeeping.

Step-by-step: completing and issuing the statement

Follow these steps to prepare a clear, verifiable Business AKA Statement for internal or third-party use.

01

Gather documents: Collect formation, DBA registration, and EIN records for verification.
02

Complete fields: Enter entity name, AKAs, tax ID, address, signer, and effective date.
03

Authenticate signer: Obtain authorized signature; notarize if requested by recipient.
04

Distribute copy: Send to payer, bank, or vendor and retain a signed file for records.

Typical processing flow when deploying an AKA statement

Common routing: prepare, verify, sign, and file. Below are the main handoffs and required checks.

Prepare Document: Populate fields and attach supporting formation or DBA registrations.
Verify Identity: Match legal name and EIN against official records or ID.
Sign and Notarize: Authorized signer executes; notarize if the requester requires it.
Record Retention: Store signed copy in secure records and provide recipient with a certified PDF.

Digital workflow settings for online completion and repeat use

Configure your electronic template to enforce consistency, required fields, and signer authentication.

Field	Configuration
Legal Name	Required, read-only for template reuse
DBA Lines	Repeatable field set with start date
Tax ID	Masked input with validation rule
Signature	Required with signer name and date stamp

Digital submission and format considerations

Ensure the chosen workflow records timestamps and signer attribution to satisfy ESIGN/UETA evidentiary requirements when questioned.

Integrations: Connectors for NetSuite, Salesforce, Google Workspace
Formats: PDF/A, DOCX, and flattened signed PDF output
Authentication: Email, SMS code, or stronger ID verification

Comparing eSignature vendors for executing Business AKA Statements

Vendor feature and pricing comparison. signNow is listed first. Use vendor sites for plan details and to confirm availability of specific enterprise features.

	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
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Security and compliance controls to protect AKA statements

Encryption: AES-256 at rest, TLS 1.2/1.3

Audit Trail: Comprehensive timestamped activity log

Access Controls: Role-based permissions and SSO

HIPAA BAA: BAA available for covered health data

21 CFR Part 11: Compliant for FDA-regulated records

Certifications: SOC 2 Type II and ISO 27001

Key legal and financial risks to avoid

Incorrect TIN: Backup withholding risk

Late Reporting: IRC §6721 penalties

Unsatisfied Auth: Payment delays and contract disputes

HIPAA Violation: Civil monetary penalties possible

Notarization Missing: Recipient may reject document

Record Retention: Noncompliance with audit rules

Common preparation errors to avoid

Entering trade names that do not match filed DBA registrations, which leads to vendor or bank rejections and onboarding delays.
Failing to provide the correct EIN or mixing personal SSN for a separate legal entity, which can trigger backup withholding.
Omitting effective dates or signer titles, creating uncertainty about when the trade name became effective or who has authority.
Skipping notarization when the recipient explicitly requires it, causing repeated requests and slower payment cycles.

Timing considerations and response expectations

There is no universal filing deadline for an AKA statement; timing depends on recipient requests and related regulatory cycles.

Provide on Request:

Supply an AKA statement when a payer or bank requests it to complete vendor setup

Before Payments:

Deliver prior to first payment to avoid delays or backup withholding

Tax Reporting:

Align statement updates with annual tax filings and 1099 data collection

Registration Deadlines:

File DBA registrations per local rules before representing the name commercially

Update Frequency:

Update statements within 30 days of material changes when practicable

Key milestones from preparation to retention

A simple milestone sequence for completing, distributing, and retaining an AKA statement.

01

Draft and Verify

Prepare the statement and verify entity and DBA documentation

02

Signer Authorization

Confirm authority and obtain signature or notarization as required

03

Deliver to Recipient

Send signed copy to payer, bank, or licensing agency

04

Archive Securely

Store signed document per retention policy and regulatory requirements

Frequently asked questions about Business AKA Statements

Answers to common questions about legality, notarization, electronic signatures, and correcting errors when preparing an AKA statement.

Need help? Contact support

Is an AKA Statement legally binding?
Yes. When signed and executed with intent, an electronic or paper AKA statement can be binding under the ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA where adopted; ensure signer intent, consent, attribution, and retention are satisfied.
Can I e-sign this document?
Yes. Electronic signatures meeting ESIGN/UETA evidentiary standards are acceptable for most private transactions; certain narrow exceptions like wills or court filings remain excluded.
Do I need a notary or witnesses?
Not typically for vendor or bank use, but some recipients or state laws may request notarization or witnesses. Check recipient requirements and state-specific rules before skipping notarization.
How do I correct a mistake after signing?
Prepare an amended statement referencing the original, have the authorized signer execute and date it, and distribute to all prior recipients to replace the earlier version.
Who should sign the statement?
An authorized representative with corporate authority (owner, officer, or designated agent) should sign; include title and contact information to establish authority.
How long should I keep the signed statement?
Follow applicable retention guidance: at least 3 years for tax records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)), and longer where industry rules apply.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now