A DBA is not a legal entity. “Doing business as” is an alias — a registered trade name attached to a person or company that already exists in the eyes of the law. It creates no new business, no separate legal “person,” and no liability shield of its own. Whoever stands behind the name, whether that’s you as a sole proprietor or an LLC you’ve already formed, is still the party doing the business.
That distinction sounds technical, but it drives nearly every practical question people ask about DBAs: who gets sued, who owes the taxes, whose assets are on the line, and whether registering a trade name “sets up a business.” The short answer to that last one is no. It gives your business a name. It doesn’t give it a legal existence.
What a DBA Actually Is
When a state issues articles of incorporation or an LLC certificate of formation, it creates a new legal person. That new person can own property, sign contracts in its own name, sue, be sued, and carry its own debts separately from the humans who own it. A DBA does none of this. It’s a registration that tells the public one thing: this trade name belongs to this particular owner.
Courts treat the name accordingly. A trade name has no standing to sue or be sued on its own, because there’s nothing there to sue. Any lawsuit touching the business has to name the actual person or entity behind the DBA. If you sign a contract using your trade name, every obligation in that contract runs to you personally, or to whichever company registered the name. The DBA is a label on the door. The business inside the door is still whoever walked in.
Liability Under a DBA
Because registering a DBA creates nothing new, it protects nothing. A sole proprietor operating under a trade name carries the same unlimited personal liability as a sole proprietor using their own legal name. If the business is sued or runs up debt it can’t pay, creditors can reach the owner’s personal bank accounts, home equity, and other assets. There is no corporate veil to pierce, because no corporate structure exists.
The picture shifts, but not by much, when an LLC or corporation files a DBA. Those entities already have liability protection built in through their formation. A DBA added on top doesn’t weaken that protection, but it doesn’t strengthen it either. The trade name is just a second label for the same entity. If the LLC’s protections fail for other reasons, such as commingled funds, fraud, or undercapitalization, the DBA won’t save anyone.
This is the trap most new business owners fall into. They pick a catchy name, file the DBA, open a bank account, and assume they’ve “started a company” in the legal sense. They haven’t. If a liability wall between the business and your personal finances matters to you, forming an LLC or corporation is the step that builds that wall. A DBA alone doesn’t.
DBA vs. LLC or Corporation
Most people asking whether a DBA is a legal entity are really deciding between a DBA, a formal entity, or both. The differences come down to a few points:
- Legal existence. An LLC or corporation is a separate legal person recognized by the state. A DBA has no independent existence apart from its owner.
- Liability. LLC members and corporate shareholders generally aren’t personally liable for business debts beyond what they put in. A sole proprietor with a DBA has unlimited personal liability.
- Taxes. An LLC can elect how it’s taxed. A DBA has zero effect on tax status; income flows through exactly as it would without the trade name.
- Cost and complexity. DBA registration is cheap and usually a single filing. Forming an entity involves higher fees, governing documents, and ongoing compliance like annual reports.
- Using both. Many LLCs and corporations file one or more DBAs to run divisions or product lines under different names while keeping everything under one legal umbrella. The entity does the legal work; the DBA does the branding.
If you want a professional name and are comfortable accepting personal liability, a DBA by itself is enough. If you want the liability barrier, form an entity first. You can always layer a DBA on top of it later.
Taxes Under a DBA
The IRS does not recognize a DBA as a separate taxpayer. Every dollar earned under the trade name is reported on the owner’s existing return. Sole proprietors report business profit or loss on Schedule C of Form 1040.1Internal Revenue Service. About Schedule C (Form 1040), Profit or Loss from Business (Sole Proprietorship) For an LLC or corporation using a DBA, the trade name changes nothing about how the entity files.
Sole proprietors can use their Social Security number as their taxpayer ID, though many prefer an Employer Identification Number to keep their SSN off invoices and vendor forms. The IRS requires an EIN if you hire employees or file certain excise returns, but any sole proprietor can apply at no cost.2Internal Revenue Service. Get an Employer Identification Number Getting an EIN doesn’t convert the DBA into a separate taxable entity. And adding or changing a DBA on an existing EIN doesn’t require a new one.3Internal Revenue Service. When to Get a New EIN
The same logic shows up on Form W-9. Your legal name goes on line 1 and the DBA goes on line 2, and the taxpayer identification number must match the legal name on line 1, not the trade name. A mismatch can trigger backup withholding on your payments.4Internal Revenue Service. Form W-9 Request for Taxpayer Identification Number and Certification The pattern is consistent across every tax context: the DBA is cosmetic, and the legal owner is the real taxpayer.
When You Have to Register and What Happens If You Don’t
Although a DBA creates no entity, registering one isn’t optional in most situations. The general rule across states is that if you conduct business under any name that doesn’t clearly identify the legal owner, you have to file. For sole proprietors, any name other than your legal surname typically triggers the requirement. For LLCs and corporations, operating under any name other than the one on the formation documents triggers it. If you’re registered in one state but doing business in another, the second state may require its own DBA filing even if you’ve registered at home.
Skipping registration can cost more than the filing fee you avoided. Several states bar businesses from filing or maintaining lawsuits on contracts made under an unregistered trade name until the business complies with the statute. You can usually fix the problem by registering late, but the delay in a case where you’re trying to collect on an unpaid invoice can be expensive on its own. Other possible consequences include civil penalties, inability to open a business bank account under the trade name, and in some states treatment as a deceptive trade practice. The filing itself is cheap and routine, which is why most owners who understand what a DBA is, and what it isn’t, treat registration as a basic housekeeping step rather than a strategic choice.