A DBA registers a name, not a business — three things people get wrong

Depending on which state you are in, the same filing is called a fictitious business name statement, an assumed name certificate, a trade name registration or a DBA. The vocabulary is state vocabulary. The mechanism is identical everywhere it exists: you are trading under a name that does not say who you are, and the state wants the connection written down where anyone can find it.

What actually triggers the obligation

The trigger is not "having a business name". It is trading under a name that hides the owner. California's definition at Business and Professions Code section 17900 is the clearest version: for an individual, a fictitious business name is one that does not include the individual's surname, or one that suggests additional owners. For a corporation it is any name other than the one in its articles of incorporation; for an LLC, any name other than the one on file with the Secretary of State.

So Janet Johnson trading as Johnson Jewelry generally has nothing to file. Janet Johnson trading as Janet Jewelry does. And an LLC formed as Northgate Consulting LLC that puts "Northgate Studio" on its invoices has crossed the same line, because the invoice name is not the registered name.

There is a limit on what the name may say. California section 17910.5 bars a fictitious business name containing "Corporation", "Corp.", "Incorporated" or "Inc." unless the registrant is a corporation, and "Limited Liability Company", "LLC" or "LC" unless it is an LLC; the county clerk must refuse the filing. A sole proprietor cannot become Widget Inc. by paying a filing fee.

Why the filing cannot create a liability shield

Courts state this flatly. In Pinkerton's, Inc. v. Superior Court, a 1996 California Court of Appeal decision, the court held that "use of a fictitious business name does not create a separate legal entity" — and applied it to defeat a default judgment taken against the trading name after the corporation behind it had already appeared and been dismissed. The trade name was not a party capable of defaulting, because it was not anybody.

That cuts both ways, and the second direction is the one that costs money. A sole proprietor who files a DBA has done nothing to their exposure: the business debts are still their debts, and the only route to a shield is forming an entity, which is a different filing with a different consequence — see LLC versus corporation. An LLC that files three DBAs still has one shield across all three, and a claim arising under any of them reaches the same pool of assets.

The filing gives you almost no rights in the name

This is the second belief, and the statutes contradict it in plain terms. Florida Statutes section 865.09(8) says registration "is for public notice only, and does not give rise to a presumption of the registrant's rights to own or use the name registered, nor does it affect trademark, service mark, trade name, or corporate or other business entity name rights previously acquired by others in the same or a similar name" — and adds that registration "does not reserve a fictitious name against future use".

The administrators say the same thing in their own words. The Texas Secretary of State warns that filing an assumed name "does not prevent anyone else from filing the same assumed name". Pennsylvania's Department of State states there are "no ownership rights to a fictitious name". A Georgia superior court clerk's office puts it in capitals: it should not be assumed that registration secures or protects the use of the name exclusively.

Rights in a name come from somewhere else. Under the Lanham Act, 15 U.S.C. § 1125(a) gives a civil action against confusing use to anyone damaged by it, registered or not — the right grows out of use in commerce. Federal registration adds what a county index cannot: § 1072 makes registration on the principal register constructive notice of the claim of ownership, nationwide.

So a DBA filing is not a clearance search, and it is no defence against someone with prior trademark rights. If the name matters, run a trademark clearance search before the signage is printed, not after a cease and desist arrives.

The real sanction is the courthouse door

Ask what happens if you never file and most answers reach for a fine. Fines exist and are mostly trivial. The provision that actually bites is the one that suspends your ability to sue. California Business and Professions Code section 17918 is the clean example: "No person transacting business under a fictitious business name contrary to the provisions of this chapter, or his assignee, may maintain any action upon or on account of any contract made, or transaction had, in the fictitious business name in any court of this state until the fictitious business name statement has been executed, filed, and published as required by this chapter."

Read that as a small business owner with an unpaid invoice. The customer has not paid; you go to file in small claims; the defence is not that the work was bad but that you never filed a piece of county paperwork. Texas section 71.201 adds a sting on top — a court may award the other side the expenses, including attorney's fees, of locating and serving a defendant who did not file.

Why most people file anyway: the bank

The statutory consequence is the important one. The reason the filing actually gets done is duller. Banks will not open an account, or deposit a cheque, in a name they cannot tie to a customer of record. Wells Fargo's account-opening requirements state the rule and the trigger together: if the business name does not include the legal last name of the owner, the bank needs an original or certified document such as a fictitious name certificate or certificate of assumed name. Janet Jewelry needs one; Johnson Jewelry does not.

That is the statute's surname test, arrived at independently by a bank, and it is why a filing that grants no rights is nonetheless effectively compulsory. The Small Business Administration is blunt about the trade: a DBA "doesn't provide legal protection by itself", but most states require it and it is what lets you bank under the name.

Where it is filed, published and renewed — none of it is uniform

Treat everything in this section as a prompt to check your own state rather than a rule. The differences are real and structural, not cosmetic.

County or state

California files at the county clerk; Florida once, statewide, with the Division of Corporations; Georgia with the clerk of the superior court. Texas and New York both split it by entity type — county clerk for sole proprietors and general partnerships, the state for registered entities, a division Texas completed when House Bill 3609 removed the county requirement for those entities in September 2019. And Kansas has no such filing at all: its Secretary of State notes that the name reservation form "does not register an assumed, fictitious, trade, or DBA (doing business as) name", and offers no substitute.

Publication, in the states that still require it

Several states still make you buy a newspaper notice, and the shape of it varies. Georgia wants the county legal organ, once a week for two weeks. Florida wants the intention to register advertised at least once. Pennsylvania requires it only where an individual is a party to the registration — 19 Pa. Code § 17.208 calls for a single notice in two county newspapers, one of them the legal newspaper, with the proofs kept rather than filed. California's version, and the deadlines around it, are on the axis below.

Renewal diverges as much as everything else. Florida also runs five years; a Texas certificate may state a term of up to ten; New York's section 130 certificates carry no expiry at all. None of it is guessable from another state.

The foreign-qualification case, where a DBA is not optional

One situation reverses the usual logic. When an out-of-state entity qualifies in a new state and its legal name is already taken there, it cannot simply proceed. Texas is explicit: where the legal name is unavailable, "the entity must register in Texas under an assumed name (d/b/a)" and file an assumed name certificate with the Secretary of State. Here the DBA is not branding but the condition of being allowed to operate — and it is the name that will carry service of process.

Does a DBA need its own EIN?

No, and the reason is the same one running through the whole page: a DBA is not a taxpayer because it is not a person. The IRS states that a business entity should have only one EIN. It also confirms the practical corollaries — a sole proprietor needs no new EIN to change a business name or location, or to own multiple businesses, and neither does a corporation or a partnership changing its name.

Two things follow. The bank account opened under the trading name is still the entity's account, on the entity's EIN. And a Form W-9 given to a client should carry the legal name on the tax line with the DBA on the business-name line, never the DBA alone — a mismatch between the name and the TIN is what generates backup-withholding notices later.

How to sign a contract when you trade under a DBA

Here the abstraction becomes visible. If the trading name is not a legal person, a contract signed in that name alone has an identity gap at the top of it, and the counterparty who wants out will find it. Pinkerton's is the demonstration in reverse: a judgment against a trade name was worthless because there was nobody there to bind.

The fix is one line of drafting and costs nothing. Name the legal person, then attach the trading name to it: Northgate Consulting LLC d/b/a Northgate Studio. That single formulation satisfies the statute, discloses the principal, and gives the reader a party they can sue and be sued by.

The same discipline applies downstream. An invoice that names only the trade name is the document you will be trying to enforce, and an NDA signed by a trading name binds nobody in particular. Where an LLC is the entity, its operating agreement is the place the trading names should be recorded, so the paperwork and the signage agree.

What the filing is actually for

Read the three misconceptions together and one design shows through. These are consumer-protection statutes. Their object is that a person dealt with by a name can find out who stands behind it — which is why Florida calls registration "public notice only", and why the sanction is aimed precisely at whoever wanted the anonymity: you may be sued in the name you chose, but you may not sue in it until you have said who you are.

So it is cheap to do and wrong in only one direction. It buys a bank account, a clean route to court, and disclosure the law would otherwise force on you awkwardly. It buys no protection from creditors and no claim on the name. For the first, form an entity and keep the formalities that make it hold; for the second, the register you need is the USPTO's.