Fictitious Name (an Assumed Business Name): What It Is and How It Affects Funding

A fictitious name — also called an assumed business name, a DBA ("doing business as"), or a trade name — is any name a business operates under that is different from the owner's legal personal name or the legal name registered with the state. If Maria Gonzalez runs a shop as "Sunrise Cafe" without forming a company under that name, "Sunrise Cafe" is her fictitious name. Registering it does not create a new legal entity, give you liability protection, or change your taxes; it simply puts the public on notice about who is behind the brand and lets you legally invoice, sign contracts, and open a bank account under that name. From a funding standpoint, the fictitious name matters for one practical reason: it is usually the name that shows up on your merchant deposits and bank statements, and revenue-based underwriters read those statements to make a decision.

Fictitious name vs. legal name: the distinction that trips owners up

Every business has a legal name. For a sole proprietor, the legal name is the owner's own name (John Smith). For an LLC or corporation, it is the exact name on the formation documents filed with the Secretary of State (Smith Ventures LLC). A fictitious name is anything the business uses in the marketplace that is not that legal name.

• Sole proprietor: John Smith operating as "Smith's Lawn Care" needs a DBA because "Smith's Lawn Care" is not his legal name.
• LLC: Smith Ventures LLC selling under the brand "QuickClean" needs a DBA because the brand differs from the registered entity name.
• No DBA needed: Smith Ventures LLC invoicing as "Smith Ventures LLC" — the name it operates under already matches the legal name.

The key idea: a DBA is a mask over an existing person or entity, not a separate business. Liability, taxes, and debts still run to the underlying owner or company."

When you are legally required to register an assumed name

Most states require you to register a fictitious name before you use it in commerce, though the office and terminology vary — some file at the county clerk, others at the Secretary of State. Common triggers:

• You are a sole proprietor or partnership using any name other than the owners' surnames.
• You are an LLC or corporation marketing, invoicing, or banking under a brand different from your registered entity name.
• Your bank requires a filed DBA certificate to open a business deposit account in the trade name.
• You want to run several storefronts or brands under one legal entity — each distinct brand typically needs its own assumed-name filing.

Penalties for skipping registration range from fines to being unable to enforce a contract in court. Filing is inexpensive and usually renews on a multi-year cycle. Check your specific state and county office, because requirements are not uniform nationwide.

What a fictitious name does NOT give you

This is where owners most often get burned. A DBA is administrative, not protective. It does not:

• Create liability protection. A sole proprietor with a DBA is still personally liable for business debts. If you want a liability shield, you form an LLC or corporation — a separate step.
• Change your taxes. Income still flows to the same tax return under the same EIN or SSN.
• Give you trademark rights. Registering a DBA in your county does not stop a business three states away from using the same name. Trademark is a separate federal process.
• Make you a new borrower. When you apply for funding, underwriters look through the DBA to the real owner or entity behind it.

If liability protection is your actual goal, see our pillar on choosing a business structure for funding before you file anything.

How a fictitious name affects business funding approvals

Here is the underwriter's-desk reality. When you apply to a bank or an SBA lender, mismatched names create friction: the legal entity on the application must line up with the entity on tax returns, the operating agreement, and the bank account. A DBA that isn't documented can stall a file for weeks.

Revenue-based and MCA marketplace funders read the situation differently. They approve primarily on bank deposits and revenue trends rather than on paperwork perfection or credit score. What they care about is that the deposits landing in the account are clearly yours and clearly consistent. A clean, registered DBA that matches your merchant statements actually helps here — it ties the money coming in to the business applying for funding. The name on your deposits should tell one coherent story.

Typical profile for a revenue-based approval: minimum around $10,000 in funding, personal FICO 500+, decisions in roughly 24-48 hours, with the review driven by cash flow. Nothing here is ever guaranteed — approval always depends on the deposits underwriting actually sees.

Decision framework: when a DBA helps or hurts your funding path

Use this as a quick self-check before you file or apply.

A fictitious name works best when

• Your brand name differs from your legal name and you need to bank and invoice under the brand.
• You run multiple storefronts or product lines under one entity and want each to deposit under its own recognizable name.
• You are rebranding but keeping the same legal entity, EIN, and bank history intact.
• You want your merchant statements to match your public-facing brand so revenue-based underwriting reads cleanly.

Think twice / avoid relying on a DBA when

• You actually need liability protection — form an entity instead; a DBA does nothing here.
• Your deposits are split across a personal account and the DBA account, muddying the revenue picture underwriters need.
• You just opened the DBA bank account yesterday — most revenue-based funders want to see a few months of deposit history in the account you're applying with.
• You expect a DBA to shield you from an existing business debt. It won't; the debt follows the underlying owner.

Example: how the name on deposits shapes a revenue-based review

The figures below are for example only, to illustrate how underwriters read deposit consistency — not a quote or an offer.

Notice the pattern: the amount of revenue matters, but so does whether the deposits clearly belong to the applying business. A registered fictitious name that matches the deposit account removes doubt. Cash flow that is easy to trace is cash flow that is easy to approve.

Practical steps: filing a fictitious name the funding-ready way

1. Confirm the name is available. Search your state/county assumed-name database and, ideally, a federal trademark search to avoid conflicts.
2. File with the correct office. County clerk or Secretary of State, depending on your state. Keep the stamped certificate.
3. Publish if required. Some states require a newspaper notice of the assumed name.
4. Open or update your business bank account in the DBA name using the certificate. This is the account whose deposits underwriting will read.
5. Run all revenue through that account. Consistent, single-channel deposits are the single biggest thing you control before applying for revenue-based funding.
6. Keep records aligned — the DBA, the legal entity, the EIN, and the deposit account should all point to the same story.

When your deposit history is clean and consistent, a revenue-based marketplace can move fast. For how underwriters weigh those deposits against credit, see our pillar on how revenue-based financing works.