DBA ownership belongs to whoever registered the fictitious name. A DBA (short for “doing business as”) is a trade name, not a legal entity, so it can’t own itself and it can’t own anything else. If you filed the paperwork as a sole proprietor, you personally own the DBA. If an LLC or corporation filed it, that entity owns it through its existing legal structure. Every right, obligation, and liability attached to the name runs directly to the registrant.
Who the Registrant Is Depends on How You Filed
A sole proprietor who files a fictitious business name is personally the owner. An LLC or corporation that files one remains the owner through its existing legal structure. The DBA itself owns nothing, holds no rights, and can’t act on its own behalf. It’s a nickname for a person or business that already exists.
The practical result: a DBA can’t sign a contract, own property, open a bank account, or appear in court as a party. The registrant does all of those things. When someone sues a business operating under a trade name, they’re really suing the person or entity behind it. Courts have consistently held that a fictitious business name has no legal existence independent of its registrant.
What Owning a DBA Means for Your Personal Liability
This is where owners get hurt. Registering a DBA does not create a liability barrier of any kind. If you’re a sole proprietor and someone sues your DBA business, they’re suing you. Your house, your car, and your personal bank accounts are all reachable, because there’s no separate entity between you and the claim.
When an LLC registers a DBA, the LLC’s existing liability protection carries forward. But the protection comes from the LLC structure, not from the DBA filing. The DBA is just a name the LLC uses in the market. Strip away the LLC, and the DBA standing alone protects nothing. People who register a DBA thinking it gives them the same protection as forming an LLC are making a mistake that can cost them everything they own.
Every asset the registrant holds is potentially exposed to business debts. A sole proprietor operating under a DBA has no legal shield between personal savings and a business lawsuit. The DBA didn’t create a new entity, so there’s no new entity to absorb the hit.
Owning the Filing Is Not Owning the Name
Registering a DBA does not give you exclusive rights to that name. The filing exists to create a public record linking a trade name to its owner, so customers and regulators know who they’re dealing with. It doesn’t stop another business in a different county or state from using the same name.
Trademark protection is a separate system entirely. The U.S. Patent and Trademark Office notes that “using a business name doesn’t necessarily qualify as trademark use,” and that registering a business name at the state or local level does not create trademark rights.1United States Patent and Trademark Office. Trademark Process A trademark protects a brand as a source identifier for specific goods or services. A DBA filing tells the county or state who you are.
Using a name in commerce can build common law trademark rights over time, but those rights are limited to the geographic area where you actually do business. Broader protection requires federal trademark registration through the USPTO. Filing a DBA and filing a trademark serve completely different purposes, and having one does not create or substitute for the other. So the ownership a DBA gives you is ownership of a public disclosure, not ownership of a brand.
Taxes Follow the Owner, Not the DBA
Because the DBA isn’t a separate entity, it isn’t a separate taxpayer either. The IRS doesn’t recognize a DBA as a taxable entity. If you’re a sole proprietor, you report all business income and expenses on Schedule C (Form 1040), regardless of what name you operate under.2Internal Revenue Service. About Schedule C (Form 1040), Profit or Loss from Business (Sole Proprietorship) Line C of that form asks for your business name, which is where your DBA goes. If an LLC or corporation registered the DBA, the entity keeps filing under its existing tax structure.
You also don’t need a new Employer Identification Number just because you registered a DBA. The IRS is explicit: you don’t need a new EIN if you simply change your business name or location.3Internal Revenue Service. When to Get a New EIN Sole proprietors who have no employees can continue using their Social Security number for tax purposes. An existing EIN carries over.
Sole proprietors owe self-employment tax on net business earnings, covering Social Security and Medicare. The self-employment tax rate is 15.3%, split between 12.4% for Social Security and 2.9% for Medicare.4Internal Revenue Service. Self-Employment Tax (Social Security and Medicare Taxes) Registering a DBA doesn’t change that obligation or create any new deductions. The business income flows through to your personal return the same way it always did.
Banking Under a Name You Own
A DBA can’t hold a bank account, but its owner can open one in the trade name. Most banks require a fictitious name certificate or assumed name certificate before they’ll open an account under a DBA. Wells Fargo, for example, requires a fictitious name certificate or statement for sole proprietors whose business name doesn’t include their legal last name, and lists similar documentation requirements for partnerships and other entities.5Wells Fargo. How to Open A Business Bank Account: What You Need Beyond the DBA certificate, expect to bring your personal identification, your EIN or Social Security number, and the bank’s minimum opening deposit.
Keeping business funds in a dedicated account under your DBA name isn’t legally required for sole proprietors, but it protects you. Mixing personal and business funds makes tax reporting harder, and if you later form an LLC, commingled accounts are exactly the kind of evidence a court uses to “pierce the veil” and strip away liability protection.
Transferring or Ending DBA Ownership
Because ownership is tied to the registrant, it doesn’t move on its own. When a business is sold, the DBA doesn’t automatically transfer to the new owner. The buyer needs to file a fresh DBA registration linking the trade name to their own legal identity. The seller should file an abandonment or withdrawal to sever their connection to the name. In asset purchase agreements, a DBA and its associated goodwill are typically listed among the transferred intangible assets, but the regulatory filing is a separate step the buyer must complete independently.
If both parties skip this paperwork, the public record still shows the original owner as the person behind the business. That creates liability exposure for the seller and legal standing problems for the buyer.
When you stop using a DBA, file a statement of abandonment or formal withdrawal with the same office where you originally registered. This filing severs the public link between you and the trade name. Without it, you remain on record as the person responsible for any activity conducted under that name, even if you stopped operating years ago. If someone else starts using the name, or if old obligations surface, the public record still points to you. The filing is inexpensive and usually takes just a few minutes, but people forget about it all the time. Treat it like canceling an insurance policy: you wouldn’t stop paying premiums and assume the policy disappears on its own.