Your legal business name and the name on your sign do not have to be the same — but if they differ, most states require you to register the difference. That registration is called a DBA: “doing business as.” It is one of the simplest filings in business ownership, yet confusion around it causes real problems, from rejected bank applications to unenforceable contracts. Here is what a DBA is, when you need one, and exactly how DBA registration works.
Table of Contents
- What a DBA Is (and Is Not)
- When You Need a DBA
- DBA vs. LLC: The Critical Distinction
- How to Register a DBA: Step by Step
- Costs, Renewals, and Multi-State Issues
- After Filing: Putting the DBA to Work
- Key Takeaways
What a DBA Is (and Is Not)
A DBA — also called a fictitious business name, assumed name, or trade name depending on the state — is a public registration declaring that you are conducting business under a name other than your legal name. If Jane Martinez operates as “Martinez Marketing,” the DBA filing links the two identities in the public record. Its purposes are transparency (customers and creditors can find who is behind the name) and legal permission (many states prohibit enforcing contracts or opening bank accounts under an unregistered name).
What a DBA is not matters more. A DBA creates no legal entity, provides zero liability protection, and confers no tax status. “Martinez Marketing” with a DBA is still Jane Martinez personally — liable for every debt and lawsuit. A DBA also generally provides no exclusive ownership of the name beyond your filing jurisdiction; it is not a trademark. Founders who believe a DBA filing “protects” their brand learn otherwise when a trademark holder sends a cease-and-desist.
Think of the DBA as a name tag, not armor. It tells the world what to call you. Everything substantive — liability, taxes, ownership — comes from your business structure, which is a separate decision made through separate filings.
When You Need a DBA
Sole proprietors need a DBA whenever they operate under any name other than their full legal name. “Jane Martinez, Consultant” using her own name typically needs no filing; “Martinez Marketing” does. Partnerships using a name other than the partners’ surnames generally need one too. These are the classic DBA users — freelancers, independent contractors, and small partnerships branding themselves beyond their personal names.
LLCs and corporations need DBAs in different situations: when operating a division, product line, or location under a name different from the registered entity name. “Blue Ridge Holdings LLC” opening a coffee shop called “Summit Roast” registers “Summit Roast” as a DBA of the LLC. This lets one entity operate multiple brands without forming multiple companies — efficient, provided the bookkeeping keeps each brand’s finances clearly attributed to the entity.
Banks are the practical enforcers. Try opening a business account for an unregistered trade name and the bank will ask for the DBA certificate — no certificate, no account. Landlords, payment processors, and wholesale suppliers often ask too. Even where your state technically exempts your situation, the DBA certificate smooths enough commercial interactions to be worth its modest cost. State small-business portals linked from sba.gov spell out local requirements.
DBA vs. LLC: The Critical Distinction
| Question | DBA | LLC |
|---|---|---|
| Creates a separate legal entity? | No | Yes |
| Limits personal liability? | No | Yes (if maintained properly) |
| Changes how you are taxed? | No | By default no; elections available |
| Typical cost | $10–$100 | $50–$500+ in state fees |
| Ongoing compliance | Periodic renewal | Annual reports, separate finances |
| Right when… | You need a trade name, risk is low | You need liability protection |
The most expensive DBA mistake is treating it as a substitute for an LLC. A consultant with meaningful client exposure, a food business with public-safety risk, or any venture signing leases and hiring workers generally needs the liability shield only an entity provides. The DBA-vs-LLC question is really a risk question: if the business were sued for more than its assets, would your personal savings, home, and future wages be on the line? With only a DBA, the answer is yes.
That said, the two often work together rather than competing. A common, sensible setup is an LLC for protection with one or more DBAs for branding — “Blue Ridge Holdings LLC doing business as Summit Roast.” You get the shield and the sign. Founders weighing startup costs and tax implications should price both filings together; combined, they are still among the cheapest steps in launching.
How to Register a DBA: Step by Step
DBA registration is handled at the state level in some states and the county level in others — this is the single biggest source of confusion, so verify your jurisdiction first. The general process follows the same pattern everywhere:
- Choose the name and check availability. Search your state or county business-name database to avoid duplicates. Then check the USPTO trademark database — a DBA filing will not protect you from infringing an existing federal trademark, and rebranding after launch is painful.
- Confirm where to file. Some states centralize fictitious-name registration with the Secretary of State; others (California and Texas, for example) handle it at the county clerk level in each county where you do business. File in every jurisdiction your rules require.
- Complete the application. You will provide your legal name or entity name, the DBA name, business address, and often a brief description of the business. Entity applicants typically attach proof of good standing.
- Publish notice if required. Several states (notably California, New York, and others) require publishing the DBA in a local newspaper for a set number of weeks and filing proof of publication. Skip this step and the registration may be void.
- Pay the fee and receive your certificate. Fees are modest; the certificate (sometimes called a statement or registration) is your proof for banks and vendors.
Name rules vary: most jurisdictions prohibit names implying you are a bank, insurer, or government agency, and entity-type suffixes (LLC, Inc.) generally cannot appear in a DBA unless the underlying entity carries them. When in doubt, the filing office’s published guidelines — or a quick call — resolve edge cases fast.
Costs, Renewals, and Multi-State Issues
DBA filing fees are among the cheapest in business compliance, typically ranging from around $10 to $100 depending on the state or county — though publication requirements in some states can add a few hundred dollars in newspaper charges. Compared with entity formation costs, the DBA is a rounding error, which is why there is little reason to operate under an unregistered name once you need one.
DBAs expire. Most jurisdictions require renewal every five years (some more or less frequently), and operating on an expired DBA can invalidate contracts signed under the name and complicate banking. Calendar the renewal date when you file — the state will not always remind you. Material changes (new owners, address changes, abandoning the name) typically require amendments or new filings.
Multi-jurisdiction businesses need multi-jurisdiction DBAs. A DBA registered in one county or state provides no rights in another; businesses operating across lines generally register in each. E-commerce sellers with no physical footprint beyond their home base usually need only their home jurisdiction, but anyone with stores, employees, or significant activity elsewhere should check each location’s rules. Federal resources at usa.gov link to state business portals for verification, and interstate commerce rules add context for businesses crossing state lines.
After Filing: Putting the DBA to Work
Once registered, update your commercial identity consistently: business bank accounts, payment processors, invoices, contracts, website, and signage should all use the DBA name exactly as filed. Inconsistent naming (“Summit Roast” here, “Summit Roast LLC” there, “SummitRoast.com” elsewhere) creates the paper-trail gaps that complicate disputes and audits.
Use the DBA on contracts to make them enforceable under the registered name, and keep the certificate with your business records — banks and counterparties will ask for it more often than you expect. If the DBA belongs to an LLC or corporation, maintain the entity’s separateness rigorously: the DBA does not create a new entity, so all income, expenses, and liabilities of the trade name belong to the underlying company and must be accounted for there.
Finally, revisit the trademark question as the brand gains value. A DBA registration is local and weak; a federal trademark is national and strong. When the name becomes an asset worth defending — real revenue, real recognition — the few hundred dollars for a trademark application is the logical next step up the protection ladder.
