Doing business as (DBA)

A registered trade name different from the entity's legal name.

Definition

Doing Business As (DBA, also called fictitious name or trade name) is a registered alternative name under which an entity does business. Registered at state or county level. Does not create a separate entity; the underlying LLC retains liability.

Context

DBA useful when running multiple brands under one LLC or operating under a name different from the formal LLC name.

Example

A Delaware LLC named Acme Holdings LLC registers DBA Apex Marketing to operate its marketing services brand. Contracts can be signed in either name; liability flows to Acme Holdings LLC.

Common pitfalls

DBA registration is state-specific; multi-state operations may need multiple DBAs.
DBA does not create trademark rights; separate USPTO filing for that.
Some banks require formal DBA registration before accepting transactions in the DBA name.

What a DBA actually changes for a non-resident founder

When you form a Delaware LLC from outside the United States, the name on your Certificate of Formation becomes the legal identity of the business. A doing business as filing sits on top of that legal identity as a public note that says the same entity also trades under a different label. It is helpful to picture the legal name as the passport and the DBA as a nickname that institutions agree to recognize. Nothing about the ownership, the membership interest, or the responsibility of the entity shifts when you add that nickname. The Delaware LLC remains the party that owns assets, signs contracts, and answers for obligations, whether the paperwork shows the formal name or the registered trade name.

For a founder who is building a brand for an English-speaking market while sitting in another country, this distinction matters in practice because it lets you separate the operating brand customers see from the holding name that appears on formation documents. A founder might register an LLC with a plain, forgettable legal name and then run a polished consumer brand under a DBA. The economics, the tax position, and the liability all still route back to the one LLC. A DBA is therefore a naming convenience and a disclosure mechanism rather than a structural change, and treating it as anything more than that tends to create confusion later when banks, payment processors, and tax forms all ask for the legal entity behind the brand.

Delaware specifics versus county and city registration

Delaware handles trade names differently from many states, and that surprises founders who expect a single statewide DBA registry like the one used for forming the LLC. In Delaware, a fictitious name registration for an entity doing business in the state is generally filed at the county level through the Prothonotary in each county where the business operates, rather than through the Division of Corporations that processed your $110 Certificate of Formation. This means the office that created your LLC and the office that records a trade name are not the same, and the two filings live in separate systems with separate fees and forms.

Most non-resident founders never set foot in a Delaware county and run an entirely remote business, so the practical question becomes where the business is considered to operate. A purely online Delaware LLC serving customers worldwide may not have a clear physical operating county inside Delaware at all, which is one reason many remote founders skip a Delaware DBA and instead rely on their legal LLC name for contracts and banking. If you later open a physical presence in another state, the relevant trade name rules will be those of that state or county, not Delaware's. This is general information rather than legal advice, and the exact filing office and requirement depend on where you actually carry on activity, so confirm the local rule for any place you genuinely operate before assuming a Delaware county filing covers you.

Why a single-member foreign-owned LLC rarely needs a DBA at formation

A common early question from non-resident founders is whether they should register a DBA right after forming the LLC. In most cases the answer at formation is no, because the legal LLC name already does everything required to open a bank account, file taxes, and sign agreements. The trade name only becomes useful once there is a real second brand, a customer-facing label that differs from the legal name, or a bank that specifically asks for a registered fictitious name before it will accept deposits under that label. Until one of those triggers appears, a DBA adds paperwork without adding capability.

There is also a timing logic worth understanding. The early steps for a foreign-owned single-member LLC tend to follow a sequence of forming the entity, obtaining a free EIN by filing Form SS-4 which typically takes around 8 to 10 business days when handled by fax or mail for applicants without a US Social Security Number, opening a banking solution, and preparing for the annual Form 5472 with a pro forma 1120. A DBA is not part of that core sequence. Adding one prematurely can complicate the EIN and banking steps because every institution will want to reconcile the trade name against the legal name. The cleaner path is to establish the legal entity and its core accounts first, then layer a DBA on later only when a branding or banking need genuinely calls for it.

Worked example: one LLC running two product brands

Imagine a founder in Lagos who forms a Delaware LLC called Harbor Stack LLC. The plan is to run a paid newsletter under one brand and a small software tool under another, both targeting readers in the United States and Europe. The founder keeps Harbor Stack LLC as the legal entity that holds the bank account, the EIN, and the contracts. For the newsletter the founder uses the brand name Tideline, and for the software the brand name Quaymark. Rather than forming two separate LLCs and paying two separate $300 flat franchise taxes due June 1 each year, the founder can present both brands publicly while keeping a single legal entity underneath.

If a bank or payment processor asks for proof that Harbor Stack LLC is authorized to receive money labeled Tideline or Quaymark, that is the point where a DBA registration in the relevant jurisdiction can help, because it creates a public record linking the brand label to the legal entity. Contracts for either brand are still signed in the name Harbor Stack LLC, optionally noted as Harbor Stack LLC doing business as Tideline. Any liability arising from either brand flows to the one LLC, which is exactly why the founder must weigh whether mixing two unrelated brands under one entity is wise. The DBA gives branding flexibility, but it does not wall the two brands off from each other in terms of risk, and that tradeoff should be considered deliberately.

How a DBA interacts with opening a US business bank account

Banking is where the DBA question becomes concrete for most non-resident founders, because the fintech platforms that serve foreign-owned LLCs each have their own rules about names. Providers commonly used by founders without a US address include Mercury, Wise, Relay, Lili, and Payoneer, and each opens accounts in the legal LLC name tied to the EIN. If you want incoming payments or invoices to display a brand name that differs from the legal LLC name, some platforms allow a trade name or a display name, while others want a formal DBA registration on file before they will accept that label. The exact policy varies by provider and changes over time, so the practical move is to check the current requirement directly with whichever platform you choose.

A frequent point of confusion is expecting a bank account to be opened in the DBA name alone. That generally does not happen, because the account belongs to the legal entity and the EIN belongs to the legal entity. The DBA is at most an attached label, not the account holder. This is why founders are advised to settle on the legal LLC name carefully at formation, since that name will anchor the EIN, the bank account, and every tax filing. A DBA can dress up the customer-facing presentation, but underneath, money still moves through an account owned by the legal Delaware LLC, and reconciling brand names to that legal account is something every founder running multiple labels should plan for.

DBA and the EIN: one number, possibly many names

The Employer Identification Number you obtain by filing Form SS-4 is issued to the legal entity, not to any trade name. A single Delaware LLC has one EIN, and registering one or several DBAs does not generate additional EINs. This is a relief for founders because it means a multi-brand structure built on DBAs keeps a single tax identity, a single set of filings, and a single relationship with the Internal Revenue Service. When a brand under a DBA earns revenue, that revenue belongs to the LLC that holds the EIN, and it is reported through that one entity rather than splintered across separate numbers.

For a non-resident founder who cannot get an EIN online and instead waits the typical 8 to 10 business days after submitting Form SS-4 by fax or mail, this consolidation is useful. You go through the EIN process once for the LLC, and any later DBA simply rides on top of that established number. If a bank or vendor asks for the tax identification number associated with a brand operating under a DBA, the correct answer is the LLC's EIN. Keeping this straight prevents a common mistake where founders assume each brand needs its own tax number. It does not. One legal entity, one EIN, and as many registered trade names as the business genuinely needs, all reporting back through the same return.

DBA, Form 5472, and the foreign-owned LLC reporting duty

A foreign-owned single-member Delaware LLC that is treated as a disregarded entity generally has to file Form 5472 along with a pro forma 1120 to report reportable transactions between the LLC and its foreign owner. The penalty associated with failing to file or filing late is steep at $25,000, which is why this obligation deserves attention regardless of how many brands the LLC runs. Adding a DBA does not change this reporting picture, because the reporting attaches to the legal entity and its foreign owner, not to any individual trade name the entity uses in the market.

It helps to think of the DBA as invisible to the tax form. Form 5472 cares about the relationship between the LLC and its owner and about the transactions that flow between them, such as capital contributions and distributions. Whether the LLC earned its revenue under its legal name or under three different DBAs is not the question the form is asking. That said, running several brands through one entity can make your internal bookkeeping more complex, and clean records that map each brand's activity back to the single LLC make it far easier to prepare an accurate return. This is general information and not tax advice, so a founder with a multi-brand DBA structure and meaningful cross-border transactions should consider professional help to get the 5472 filing right and avoid that $25,000 exposure.

DBA versus forming a separate LLC

Founders weighing how to launch a second brand often face a choice between registering a DBA under the existing LLC or forming a brand new LLC. The two paths have meaningfully different consequences. A DBA keeps everything inside one legal entity, which means one Certificate of Formation, one $300 flat franchise tax due June 1, one EIN, one bank relationship, and one set of annual filings including the Form 5472 obligation. It is the lighter and cheaper route in terms of recurring overhead, and it suits founders who want brand flexibility without multiplying their compliance load.

A separate LLC, by contrast, creates a genuinely distinct legal entity with its own liability boundary, its own franchise tax, its own EIN, and its own filings. The advantage is real separation, so a problem affecting one brand does not automatically reach the assets of the other. The cost is duplicated formation fees, duplicated annual taxes, and duplicated paperwork across both entities. For a non-resident founder running small, low-risk brands that share an audience, a DBA structure under one LLC is often the more efficient choice. For brands with different risk profiles, different investors, or a plan to sell one independently, separate entities usually make more sense. There is no single right answer, only a tradeoff between simplicity and separation that each founder weighs against their own situation.

DBA and trademarks are not the same thing

One of the most persistent misunderstandings is the belief that registering a DBA protects a brand name. It does not. A DBA filing is an administrative record that connects a trade name to a legal entity within a particular jurisdiction. It does not grant exclusive rights to that name, and it does not stop another business elsewhere from using the same or a similar name. Trademark protection is a separate legal mechanism obtained through a filing with the United States Patent and Trademark Office, and that protection rests on use in commerce and on the distinctiveness of the mark rather than on a county trade name record.

For a non-resident founder building a brand intended to grow in the United States, this distinction can be costly to ignore. You might register a DBA, invest in marketing under that name, and then discover that another party holds a federal trademark and can challenge your use. The DBA gives you a public label and helps with banking and disclosure, but it offers no shield against an infringement claim and no power to stop copycats. Founders who care about owning a brand long term generally treat the DBA and the trademark as two distinct projects. The DBA handles the administrative side of operating under a name, while the USPTO filing handles the question of who actually owns the right to that name in the market. Conflating the two leads founders to overestimate what a simple trade name registration buys them.

DBA in contracts, invoices, and signatures

When you operate under a DBA, the way you present the name in legal documents matters for clarity even though the liability outcome is fixed. The cleanest convention is to identify the legal entity and then note the trade name, such as Harbor Stack LLC doing business as Tideline. This makes it unambiguous which legal party is bound by the agreement while still showing the brand the counterparty recognizes. Signing purely under a trade name without any reference to the underlying LLC can create avoidable disputes about who exactly entered the contract, even though the entity remains the responsible party.

Invoices and payment requests follow similar logic. A customer paying an invoice that shows only a brand name may be confused when the bank deposit references the legal LLC name, and a clear mapping between the two reduces support questions and chargebacks. For a non-resident founder relying on platforms like Mercury, Wise, Relay, Lili, or Payoneer, aligning the brand name on invoices with whatever display or trade name the platform supports keeps the customer experience consistent. The underlying truth never changes: the contract obligation and the right to be paid both belong to the legal LLC. The DBA simply governs how the name is displayed, so writing both names where it counts protects you from arguments that the brand and the entity are somehow different parties.

Foreign qualification: when operating elsewhere triggers more filings

A related concept that frequently gets tangled with DBAs is foreign qualification, which is the process of registering a Delaware LLC to do business in another state where it has a real presence. The two are different. Foreign qualification is about the entity gaining authority to operate in a second state, while a DBA is about the entity using a different name. A founder can need one without the other. If your Delaware LLC opens an office or hires staff in another state, that state may require foreign qualification, and within that state you might also need a separate trade name registration if you use a DBA there.

For most non-resident founders running fully remote businesses with no US staff and no US office, foreign qualification often does not arise, because the LLC is not considered to be physically operating in any particular state beyond its Delaware formation. That can change quickly if you establish a tangible footprint somewhere, and the rules vary by state. The practical lesson is that a DBA does not extend your right to operate into a new jurisdiction, and qualifying in a new state does not automatically register your trade name there. Each is its own filing with its own trigger. Founders expanding into a physical US presence should map both questions separately rather than assuming one filing handles both, and should confirm the specific requirements of any state where real activity begins.

BOI reporting and the FinCEN rule for US-formed LLCs

Beneficial ownership information reporting was a major concern for LLC founders, and it sometimes gets mentioned alongside DBA filings as if registering a trade name might create a reporting obligation. It is worth separating these clearly. Under the FinCEN Interim Final Rule of March 26 2025, US-formed LLCs are exempt from beneficial ownership information reporting, which removed a compliance step that had previously worried many domestic and foreign founders forming entities in the United States. A Delaware LLC formed by a non-resident is a US-formed entity for this purpose, so the BOI reporting requirement does not apply in the way it once seemed it might.

Registering a DBA does not reintroduce that obligation, because a trade name is not a new entity and the exemption attaches to how the entity was formed rather than to the names it later uses. Founders should still keep an eye on how rules evolve, since reporting frameworks can shift, and this is general information rather than legal advice. The key point for a multi-brand founder is that adding DBAs to a US-formed Delaware LLC does not generate fresh beneficial ownership filings. The exemption established by the March 26 2025 rule covers the entity, and the trade names operating under it ride along with that status rather than triggering anything separate.

Edge cases that catch founders off guard

Several edge cases tend to surprise founders who treat a DBA as a simple formality. The first is renewal. In some jurisdictions a fictitious name registration expires after a set number of years and must be renewed, and letting it lapse can cause a bank to question transactions under that name. The second is consistency across platforms. If your payment processor shows one trade name, your website shows a slightly different one, and your registration shows a third variation, you create friction that can slow down account reviews and customer trust. Picking one exact spelling and using it everywhere avoids that drift.

A third edge case involves closing or selling a brand. Because a DBA is not a separate entity, you cannot sell the brand by transferring an LLC. Selling a DBA brand means transferring specific assets such as the customer list, the website, and any trademark, then retiring the trade name registration, which is more involved than handing over an entire company. A fourth case is dispute resolution, where a counterparty might argue confusion between the brand and the entity. Clear documentation that the DBA belongs to the named LLC resolves this, but only if you maintained that paper trail. None of these edge cases are unusual, and each becomes easy to manage when you remember that the trade name is a label on a single legal entity rather than a standalone thing.

Common misunderstandings, gathered in one place

It is worth collecting the recurring misconceptions, because most DBA mistakes trace back to a small number of wrong assumptions. The first is that a DBA creates a separate company. It does not, and the underlying LLC keeps full responsibility for everything done under the trade name. The second is that a DBA needs its own EIN or its own tax return. It does not, since the legal entity holds the single EIN and files once. The third is that a DBA protects a brand name. It does not, because that protection comes only from a separate USPTO trademark process. The fourth is that a DBA lets you bank purely under the brand name with no link to the legal entity. In practice accounts belong to the legal LLC tied to the EIN.

The fifth misconception is that a DBA extends your right to operate into new states, which is actually the job of foreign qualification. The sixth is that registering a trade name affects federal reporting such as Form 5472 or beneficial ownership status, when in fact the $25,000 Form 5472 obligation attaches to the entity and its owner, and US-formed LLCs are exempt from beneficial ownership reporting under the FinCEN Interim Final Rule of March 26 2025. The thread running through all of these is the same: a DBA is a name layered on a single legal entity, not a structural, tax, or protective change. A founder who internalizes that one idea will use DBAs effectively and avoid the costly assumptions that lead others astray. This remains general information rather than legal or tax advice, so confirm specifics for your own situation.

Related terms

Foreign qualification

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC