A DBA is not a company: what the filing actually buys you
Fictitious names open bank accounts and satisfy licensors, but they do not shield anything
Contents 5 sections
DBA is a public notice that a person or a company is using a name other than its legal one. That is the entire legal content of the filing. It does not form an entity, it does not change how the IRS taxes you, and it does not put a wall between your business creditors and your house.
Founders confuse this constantly, because "doing business as" sounds like it must be doing something structural. It is not. What a DBA actually buys is narrower and, once you understand it, usually still worth the $10 to $100 you pay for it.
What a DBA filing is, in statute
California calls it a fictitious business name, Texas calls it an assumed name, New York calls it a certificate of assumed name, Florida calls it a fictitious name registration. The mechanics differ; the legal nature is the same.
In California, Business and Professions Code § 17900 et seq. governs. Any person or partnership transacting business under a name that does not include the surname of every owner, or that suggests additional owners, must file a Fictitious Business Name Statement with the county clerk in the county of the principal place of business. The statement is public, published once a week for four consecutive weeks in a newspaper of general circulation in the county, and expires after five years. Filing fees are set county by county and typically run $26 to $60 for the first name, with publication adding $30 to $150 depending on which paper you use.
Texas splits the job between two offices. Under Chapter 71 of the Business and Commerce Code, an incorporated or registered entity (an LLC, a corporation, an LP) files its assumed name certificate with the Texas Secretary of State, currently $25. An unincorporated person or general partnership files with the county clerk in each county where the business maintains premises, at a fee the county sets (usually around $15 to $25). The certificate is good for ten years.
New York's General Business Law § 130 requires every person conducting business under a name other than their own, and every partnership other than a limited partnership, to file a certificate of assumed name with the county clerk where business is conducted. Corporations and LLCs file their § 130 certificates with the Department of State instead, at $25 plus a county-by-county surcharge that can push the total past $100 for multi-county operations in New York City.
Florida Statutes § 865.09, the Fictitious Name Act, requires registration with the Division of Corporations before a person or entity engages in business under a fictitious name. The filing fee is $50. Florida also requires that the fictitious name be advertised at least once in a newspaper of general circulation in the county where the principal place of business is located, before the registration is accepted. Registration is good for five years and renews for $50.
Across the four largest state economies, the all-in cost of a DBA runs from roughly $10 at a small Texas county clerk to around $200 in a California county that requires paid publication in a high-circulation paper. Nowhere does it cost what forming an LLC costs. Nowhere does it do what forming an LLC does.
The three things it actually buys you
A correctly filed DBA gives you three practical things, and you should file one if you need any of them.
The first is a bank account in the business name. Banks apply customer-identification rules that require documentary evidence of any name on an account that is not the account holder's legal name. For a sole proprietor who wants checks made out to "Northside Plumbing" to clear, the filed DBA is the document the bank wants to see. Without it, the bank either refuses the account or opens it in the legal name and tells the customer to endorse every check twice.
The second is compliance with state and local licensing. Many occupational licenses, seller's-permit registrations, and city business-tax certificates ask for both the legal name and every trade name under which the licensee operates. The California CDTFA reseller's permit application asks for fictitious business names. New York City's Department of Consumer and Worker Protection requires assumed-name registration before issuing most of its licenses. Without the DBA, the application does not move.
The third is trademark evidence. When the USPTO examines a use-based trademark application, the specimen of use (invoices, a website, packaging) sits better in the record if there is a corresponding DBA registration showing the applicant has publicly adopted the name. A DBA is not a trademark and confers no exclusive rights, but it is useful corroborating evidence when the examining attorney asks.
Those are the benefits. Read them carefully, because they are all administrative and none of them is a shield.
What a DBA does not do
A DBA does not create a legal entity. A sole proprietor who files a fictitious business name is still a sole proprietor. A partnership that files an assumed name is still a partnership. The filing adds a name; it does not add a legal person.
Because it does not create an entity, it does not create limited liability. This is where founders get hurt. A plumber operating as "Northside Plumbing" under a county DBA is personally liable for every invoice, every judgment, and every slip-and-fall at every job site, to the full extent of her personal assets. The DBA is not a corporate veil. It is a name tag.
Even the corporate veil, when one exists, is thinner than founders think. In Walkovszky v. Carlton, 18 N.Y.2d 414 (1966), a taxi passenger sued a cab operator who had divided his fleet across ten corporations, each owning two cabs and each carrying the statutory minimum of insurance. The New York Court of Appeals held that the corporate form would be respected where used for a legitimate business purpose, and that piercing required a showing that the corporation was used to commit a fraud or to perpetrate a wrong on the plaintiff. The opinion reaffirmed the veil, but the lesson for a founder reading it sixty years later is the one you want to internalize: the veil exists only for entities, and only when the entity is operated as one. A DBA on a sole proprietorship has no veil to pierce.
A DBA also does not change federal tax treatment. A sole-proprietor DBA files Schedule C under the owner's SSN. A partnership DBA files Form 1065 under the partnership's EIN. An LLC operating under a DBA files whatever the LLC was going to file anyway. The DBA is invisible to the IRS.
The same is true under the Corporate Transparency Act, enacted as part of the FY2021 National Defense Authorization Act and awaiting final FinCEN rulemaking. A "reporting company" is defined at 31 U.S.C. § 5336(a)(11)(A) as a corporation, LLC, or other similar entity created by filing a document with a secretary of state or similar office, or formed abroad and registered to do business in the United States. A sole proprietor under a DBA is not created by a state filing of that kind; a county fictitious-name certificate is a name registration, not an entity formation. The sole prop therefore will not be a reporting company under the plain text, and no beneficial-ownership report will be owed for the DBA when the rule lands. (If the same sole prop later forms an LLC, the LLC is the reporting company and the DBA is irrelevant to that analysis.)
When to file one, and when to form instead
The useful test is to ask what problem the filing solves. If the problem is that the bank will not open the account, the license office will not issue the permit, or the trademark examiner wants evidence of use, a DBA solves it for under $100. If the problem is that a customer could sue the business and reach the owner's house, no DBA filed in any county in the United States will solve it. The tool for that problem is an LLC or a corporation, which costs more, takes longer, and, when operated properly, does what the name tag cannot.
The trap is spending $50 on a fictitious-name filing and believing the business has been "set up." The county clerk is not in the business of advising you. The filing will be accepted, the receipt stamped, and the owner will walk out with the same personal liability she walked in with, plus a certificate.
File the DBA when you need one of the three things it does. Form an entity when you need the thing it does not.
Sources
- Cal. Bus. & Prof. Code § 17900 et seq. (Fictitious Business Names), https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?division=7.&chapter=5.&lawCode=BPC
- Tex. Bus. & Com. Code Ch. 71 (Assumed Business or Professional Name), https://statutes.capitol.texas.gov/Docs/BC/htm/BC.71.htm
- Texas Secretary of State, "Assumed Name Certificate (Form 503)" fee schedule, https://www.sos.state.tx.us/corp/assumedname.shtml
- N.Y. Gen. Bus. Law § 130 (Certificate of Conducting Business Under Assumed Name), https://www.nysenate.gov/legislation/laws/GBS/130
- Fla. Stat. § 865.09 (Fictitious Name Act), http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0800-0899/0865/Sections/0865.09.html
- Florida Department of State, Division of Corporations, "Fictitious Name Registration," https://dos.myflorida.com/sunbiz/start-business/efile/fl-fictitious-name-registration/
- Walkovszky v. Carlton, 18 N.Y.2d 414 (N.Y. 1966), https://law.justia.com/cases/new-york/court-of-appeals/1966/18-n-y-2d-414-0.html
- 31 U.S.C. § 5336 (Beneficial Ownership Information Reporting Requirements), https://www.govinfo.gov/app/details/USCODE-2021-title31/USCODE-2021-title31-subtitleIV-chap53-subchapII-sec5336
- USPTO, Trademark Manual of Examining Procedure § 904 (Specimens), https://tmep.uspto.gov/RDMS/TMEP/current#/current/TMEP-900d1e1.html