DBA (Doing Business As): The Operator's Guide for US Small Businesses

A DBA — "doing business as," also called a fictitious name, trade name, or assumed name — is simply a public registration that lets you operate under a name different from your legal one. It is not a business structure, a tax status, or a liability shield. If you are a sole proprietor named Maria Gomez selling under "Sunrise Cleaning Co.," the DBA is what makes that name legal on signs, invoices, and your bank account. It does not create a separate legal entity — you and the business are still the same person or company in the eyes of the law and the IRS. That distinction is the single most important thing to understand before you file one, open a bank account under it, or use it to apply for funding.

What a DBA is (and what it is not)

A DBA is a name registration filed with a state, county, or city clerk. It puts the public on notice that a specific person or entity is operating under a trade name. That is the entire function: transparency about who is really behind the name.

What a DBA gives you:

• The legal right to market, sign contracts, and invoice under a brand name that isn't your legal name.
• The ability to open a business bank account in the trade name (most banks require the DBA certificate to do this).
• A cleaner, more marketable identity without the cost and paperwork of forming an LLC or corporation.

What a DBA does NOT give you:

• Liability protection. If you're a sole proprietor with a DBA, your personal assets are still fully exposed. Only an LLC or corporation creates that separation.
• A separate tax identity. A DBA files taxes under the owner's SSN or the parent entity's EIN. It is not a taxpayer of its own.
• Exclusive naming rights. A DBA is not a trademark. Someone in the next county could register the same name.
• A new legal entity. This is the misconception that trips up owners at funding time — more on that below.

Who needs a DBA — and who doesn't

You generally need a DBA when the name you operate under is different from your legal name. The rules vary by state, but the pattern is consistent.

Sole proprietors and general partnerships: Your legal business name defaults to your personal name(s). Any brand name beyond that triggers a DBA requirement. "John Smith" needs no DBA; "Smith Plumbing" does.

LLCs and corporations: Your legal name is whatever is on your formation documents. You need a DBA only if you want to operate a brand, product line, or division under a different name — for example, "Coastal Holdings LLC" running a storefront called "The Corner Bakery."

You typically do NOT need a DBA when: you operate strictly under your exact legal name, or your state exempts certain uses (some states let you add a descriptor without filing). Always confirm with your county or Secretary of State — this is a local rule, not a federal one.

How to file a DBA (the practical steps)

Filing is one of the cheapest and fastest administrative tasks in business. It is usually a local matter, and requirements are not uniform, so treat this as a checklist to verify rather than a guarantee.

1. Search name availability. Check your county clerk and Secretary of State databases so you don't duplicate an existing registration. A separate trademark search protects you from a bigger conflict.
2. File with the correct authority. Depending on the state, DBAs are filed at the county clerk, the Secretary of State, or both. Fees for example commonly range from about $10 to $100.
3. Publish if required. Several states (California, Florida, New York, and others) require you to publish the fictitious name in a local newspaper for a set period. Skipping this can invalidate the filing.
4. Renew on schedule. Many DBAs expire — for example every 5 years is common. A lapsed DBA can quietly break your bank account and your ability to enforce contracts.
5. Keep the certificate. Banks, payment processors, and funders will ask for the stamped certificate. Store it with your EIN letter and formation docs.

How a DBA affects business funding

This is where the "not a legal entity" point becomes money. A funder or lender does not lend to a DBA. They lend to the person or entity behind it. When you apply, the DBA is the storefront name; the underwriting attaches to the underlying sole proprietor's SSN or the parent LLC/corporation's EIN.

Practical consequences:

• Your credit and history are the entity's, not the name's. A brand-new DBA on a 10-year-old LLC still carries that LLC's 10-year track record. A DBA on a sole proprietor carries the owner's personal profile.
• Bank statements must match. Revenue-based and MCA funders underwrite on deposits. If your merchant deposits land under the DBA account, the DBA certificate proves that account belongs to your entity. Mismatched names are the most common paperwork snag that stalls approvals.
• A DBA alone does not build "business credit." Sole proprietors who want to separate personal and business liability and credit generally need to form an LLC or corporation and get an EIN — the DBA won't do that on its own.

For a fuller picture of how deposit-based approvals work, see our pillar guide on revenue-based financing and our overview of small business funding options.

Funding options for a business operating under a DBA

Because a DBA is invisible to underwriting on its own, your options are the same ones available to the entity behind it — but the path of least resistance for many main-street operators is revenue-based funding, since it leans on cash flow rather than the pristine credit and long entity age that banks demand.

A revenue-based / MCA marketplace is often the realistic fit when you operate under a DBA as a sole proprietor or young LLC, because approval leans on your bank deposits and monthly revenue rather than your credit score alone. Typical parameters seen across the marketplace, for example:

• Approval driven primarily by consistent bank-deposit volume and revenue trends.
• Minimum funding around $10,000.
• Personal FICO of roughly 500+ considered, since revenue carries the weight.
• Decisions and funding commonly in 24-48 hours.

Nothing here is guaranteed — every file is underwritten on its own deposits and history. What matters for a DBA operator is that the trade-name account statements clearly reconcile to your legal entity, so the reviewer can see the revenue is really yours.

Decision framework: when a DBA works best vs. when to avoid it

A DBA works best when:

• You're a sole proprietor or single-owner operation testing a brand and want a professional name and matching bank account without the cost of forming an entity.
• You already have an LLC or corporation and want to launch a new storefront, product line, or division under its own name while keeping one legal entity.
• You need a bank account and merchant processing in the brand name quickly and cheaply.
• Your risk exposure is low and you're comfortable that liability protection isn't part of the equation yet.

Avoid relying on a DBA alone when:

• You need liability protection — form an LLC or corporation instead; a DBA offers none.
• You want to build business credit separate from your personal credit — that requires an entity and EIN.
• You're taking on employees, significant contracts, or real risk of being sued — an entity is the tool, not a trade name.
• You want exclusive rights to the name — that's a trademark, filed federally with the USPTO, not a county DBA.

The clean rule: use a DBA for branding, use an entity for protection, use a trademark for ownership of the name. They solve three different problems and are often used together.

DBA vs. LLC vs. trademark — a side-by-side example

These three get confused constantly. The table below uses a fictional operator, "Sunrise Cleaning," to show what each tool does. Figures and scenarios are illustrative examples only.

Example takeaway: Maria can file "Sunrise Cleaning" as a DBA under her own name today for branding, later form "Sunrise Cleaning LLC" for protection, and eventually trademark the name if she expands regionally. Each step solves a different problem.