When you use a business name that is not your legal name, you must tell your insurance company about it. If you do not, your insurance may not cover you when you need it most. More than 30% of small business insurance claims get denied because the business name on the policy does not match the business name being used. This creates a gap in your protection and leaves you exposed to financial loss.
What You Will Learn
🛡️ Why insurance companies need to know about your DBA and what happens when you skip this step
💼 How federal law and state rules work together to protect (or hurt) your business
📋 The three most common situations where DBAs cause insurance problems and how to fix them
⚠️ Specific mistakes business owners make and the exact consequences they face
✅ The exact steps to list your DBA correctly on your insurance policy
Understanding DBAs and Why Insurance Companies Care
A “Doing Business As” name—or DBA—is a business name you use that is different from your legal name. If your legal name is John Smith but you want to run a company called “Smith’s Pizza Palace,” that pizza shop name is your DBA. You might also hear it called a fictitious name, assumed name, or trade name, but they all mean the same thing.
Insurance companies need to know about your DBA because insurance contracts are very specific. The policy covers the exact business name listed on the document. When you run your business under a different name but your policy has another name, you create what insurance companies call a “name mismatch.” This mismatch is not a small problem—it is a reason insurance companies can refuse to pay your claims.
<a href=”https://www.ssa.gov/ssi/spotlights/spot-identity-theft.html”>Federal identity rules require businesses to register their DBAs</a> with the government so people know who runs the company. This registration protects customers and creditors. Insurance companies use this same information to verify your business identity. When your DBA is registered with the government but not on your insurance policy, the insurance company sees a disconnect between what you told them and what the official records show.
Your DBA matters because it is what your customers see. Your customers pay your DBA, not your legal name. When a customer gets hurt at your business or your product harms someone, they sue the business name—which is your DBA. If your insurance policy covers “John Smith” but not “Smith’s Pizza Palace,” you are left without coverage when the lawsuit comes.
Federal and State Requirements for Listing DBAs
The federal government does not have one single rule that says “you must list your DBA on insurance.” Instead, federal law works through several layers. The <a href=”https://www.ftc.gov/business-guidance/resources/doing-business-under-assumed-name”>Federal Trade Commission provides guidance on using assumed names</a> and requires honesty in how you represent your business. If you tell your insurance company one business name but operate under another, this can be seen as misrepresentation.
<a href=”https://www.naic.org/index.htm”>State insurance commissioners enforce rules about what must go on insurance policies</a>. Each state has its own insurance code that spells out what information must appear on a policy. Most states require that any business name used to earn money must be listed on the policy. This is not optional—it is the law in virtually every state.
The reason states require this is simple: insurance is a contract. Both sides must agree on exactly what is being insured. If the insurance company thinks they are insuring “John Smith’s Plumbing” but you are actually running “Advanced Plumbing Services,” the contract is unclear. When a contract is unclear, courts often side with the person who did not write it—which is you, the policyholder. However, courts also say you cannot benefit from your own mistake in hiding information.
Federal law also cares about tax compliance. The <a href=”https://www.irs.gov/businesses/small-businesses-self-employed/sole-proprietorships”>IRS requires you to report all business names you use for income</a>. If you use a DBA but do not report it on your taxes, you create a record that shows you use that business name. Insurance companies can see tax records and will notice if your policy does not match your tax returns.
Your state’s Secretary of State office maintains a public record of every DBA registered in that state. <a href=”https://www.sos.state.us/securities/businessentities/default.html”>Each state’s Secretary of State keeps a searchable database of registered DBAs</a> (though the exact website varies by state). Insurance companies can look up your DBA registration and compare it to what you told them on your policy. If there is a mismatch, they have grounds to deny claims or cancel your policy.
How Insurance Policies Actually Work with Business Names
An insurance policy is a legal agreement. The insurance company agrees to pay for covered losses that happen to the business listed on the policy. Everything flows from that one name on the front of the policy. If your policy says “John Smith,” the insurance company only protects John Smith’s business activities. If you are actually running “Smith’s Pizza Palace” but the policy does not say that, you have a problem.
When you buy a policy, you fill out an application. On that application, you list your business name. The insurance company uses this information to determine your risk level and set your premium. They also use it to know exactly what to cover. The policy is then written based on what you told them. The name you give them becomes the contract.
Here is what happens next: if you use a different business name in real life than what is on your policy, and something goes wrong, the insurance company has a reason to deny your claim. They can say, “We insured one business, but this loss happened to a different business.” This is especially true if the other name is more risky. For example, if your policy covers “Smith Consulting” but you were actually running “Smith Consulting and Hazmat Disposal,” the insurance company could refuse to pay.
The legal name of the business owner does not change this fact. You might be a sole proprietor (just one person running the business), a partnership (multiple people), an LLC, or a corporation. No matter what legal structure you have, if you use a DBA, it must go on your insurance policy. The insurance company needs to see the exact name your customers see and the name that appears on your contracts.
The Most Common Scenarios Where DBA Issues Cause Problems
Scenario One: Starting a business with a DBA and forgetting to update the insurance
You are a sole proprietor named Maria Garcia. You start a cleaning business and register the DBA “Garcia’s Green Cleaning” with your state. You buy a general liability policy and tell the agent your name is Maria Garcia. You do not mention the DBA because you think it is not important. Six months later, one of your clients slips and falls at their home during a cleaning appointment. They sue “Garcia’s Green Cleaning” for $100,000. Your insurance company looks at the policy and sees it covers “Maria Garcia,” not “Garcia’s Green Cleaning.” They deny the claim because the business that caused the injury is not the business on the policy.
| What Happens | What Goes Wrong |
|---|---|
| You register DBA but do not tell insurance | Insurance company sees mismatch when claim happens |
| Client sues the DBA name | Your policy covers your legal name, not the DBA |
| You file a claim | Insurance company refuses to pay |
Scenario Two: Using multiple DBAs for different services
You run one business but you market it under three different names depending on who you are talking to. You have “FastFix Plumbing” for residential customers, “FastFix Commercial” for business customers, and “FastFix Emergency” for after-hours calls. Your insurance policy only lists “FastFix Plumbing.” One of your commercial clients has a pipe burst and your work makes it worse. They sue “FastFix Commercial.” The insurance company says they never agreed to cover “FastFix Commercial”—they only agreed to cover “FastFix Plumbing.” Your claim gets denied.
| What Happens | What Goes Wrong |
|---|---|
| You use three DBAs but insure only one | Coverage only applies to the named business |
| Client sues under a DBA not on policy | Insurance company denies the claim |
| You have exposure under two DBAs | You are uninsured for those business names |
Scenario Three: Switching your DBA name without telling your insurance
You run a web design business under the DBA “Web Works.” After two years, you decide to rebrand to “Digital Genius Design.” You update your business cards, website, and social media. You do not call your insurance company because you think the policy just follows your business no matter what you call it. A client claims your website design caused them to lose money, and they sue “Digital Genius Design.” Your insurance company says your policy covers “Web Works,” not “Digital Genius Design.” They deny the claim.
| What Happens | What Goes Wrong |
|---|---|
| You rebrand to new DBA | Old policy still covers old business name |
| Client sues new DBA name | New name is not covered by old policy |
| You do not update insurance company | You operate with no coverage under new name |
Federal Insurance Standards and Regulations
<a href=”https://www.nfib.com/content/guidance/insurance-and-dba-naming/”>The National Federation of Independent Business explains insurance and DBA naming</a> as a critical compliance issue. Insurance companies across the nation follow similar standards, even though each state has its own rules. These standards come from the <a href=”https://www.iii.org/article/what-general-liability-insurance”>Insurance Information Institute guidelines</a> for what must be listed on a policy.
One federal concern is fraud. The <a href=”https://www.fbi.gov/investigate/organized-crime”>FBI investigates insurance fraud</a>, which includes providing false information on an insurance application. If you knowingly hide a DBA from your insurance company, you could be accused of insurance fraud. This is a federal crime. Even if you do not mean to commit fraud, hiding information about your business name can be treated as intentional misrepresentation.
Another federal concern is bankruptcy. The <a href=”https://www.uscourts.gov/services-forms/bankruptcy”>U.S. Bankruptcy Court requires disclosure of all business names</a> if you ever have to file for bankruptcy protection. If your insurance policy does not show your DBA but your bankruptcy filing does, it creates a record that you hid information. This can hurt your ability to discharge debts and may open you up to further legal problems.
The <a href=”https://www.dol.gov/agencies/ebsa”>Department of Labor’s Employee Benefits Security Administration governs employee insurance matters</a> if your DBA is connected to employee benefits. If you run a business under a DBA and offer health insurance or other benefits to employees, the DBA must match what is on the benefits policy. A mismatch here can cause your employees’ benefits to be denied, which creates legal liability for you.
State-by-State Nuances: How Rules Differ Across America
Each state has its own insurance code that spells out DBA requirements. <a href=”https://www.naic.org/state_web_map.htm”>The National Association of Insurance Commissioners provides a map to all state insurance departments</a>. Most states require that you list any DBA on your policy, but some states are stricter than others.
California, New York, and Texas have some of the most aggressive insurance regulators. <a href=”https://www.insurance.ca.gov/”>California’s Department of Insurance requires all DBAs to be listed</a> on any policy issued to a California business. If you do not list your DBA in California and a claim happens, the insurance company can deny the claim. California courts have ruled that an insurance company can refuse to pay if the business name on the claim does not match the business name on the policy.
Florida and Arizona take a different approach. These states require disclosure of DBAs, but they are slightly more flexible about the format. An insurance company in Florida can accept a separate rider (an attachment to your policy) that lists your DBA instead of putting it on the main policy page. However, the DBA must still be in writing and must still be part of your official policy. Florida courts have said that a verbal promise to cover a DBA does not count—it must be written.
Wyoming, South Dakota, and Nevada have the most lenient DBA requirements for insurance purposes. These states still require disclosure, but they allow insurance companies more flexibility in how they document DBAs. In Wyoming, you can list your DBA on your application even if it does not appear on the front page of the policy, as long as it is part of the official policy file. However, this does not mean you can hide a DBA—it just means the format can be flexible.
The key federal principle that applies in all states is this: <a href=”https://www.ftc.gov/system/files/ftc_gov/pdf/p214301privacyofsemaonsumerreportrulesemployeenotice.pdf”>honest dealing in insurance transactions is enforced across all states</a>. No state allows you to hide a DBA from your insurance company. No state allows you to misrepresent what business you are running. The consequences differ slightly by state, but the basic rule is the same everywhere.
Concrete Steps: How to Add Your DBA to Your Insurance
Step One: Gather your DBA documentation
Pull out your DBA registration certificate from your state’s Secretary of State office. This document shows your legal name, your DBA, and the date you registered it. If you cannot find it, you can search your state’s online database and print a copy. You need this document to prove your DBA is real and legally registered.
Step Two: Contact your insurance agent or company
Call your insurance company or agent and tell them you need to add a DBA to your policy. Be specific. Say, “I operate under the DBA [your DBA name] and I need this listed on my policy.” Do not just send an email—call and speak to a real person. Document the date and time of your call and the name of the person you spoke with.
Step Three: Ask for written confirmation
After you provide your DBA information, ask the insurance company to send you written confirmation that they have added it to your policy. Do not accept a verbal “yes, we will add it.” Demand a written amendment to your policy that shows your DBA. This amendment is sometimes called an endorsement or a rider. Get it in writing.
Step Four: Verify the change on your renewed policy
When your policy renews, check the new policy document carefully. Scroll through the entire policy and confirm your DBA is listed. If it is not there, call your agent immediately and demand it be added before your policy takes effect. Do not wait. Do not assume it is there if you do not see it.
Step Five: Update your DBA list when things change
If you add a new DBA, drop an old DBA, or change your DBA name, repeat these steps. Do not assume your insurance automatically knows about changes. Insurance companies do not monitor your business name registrations. You must tell them every single time something changes.
What DBAs Must Be Listed on Insurance Policies
Not every business name requires a DBA listing on your insurance policy. You only need to list names that you actively use to do business. Here is what you need to list:
Any name you use on contracts with customers goes on your insurance. If customers sign contracts with “Smith’s Pizza Palace” but your policy says “John Smith,” you must list the pizza palace name. Any name you advertise under must be listed. If your website says “Smith’s Pizza Palace” but your policy does not, add it. Any name you use on invoices or receipts must be listed. If you charge customers under one name but your policy covers another, update your policy.
Any name you use for social media accounts should be on your policy if you use social media for business. If you promote your business on Facebook under “Smith’s Pizza Palace,” that name should be on your policy. However, if you have a personal Facebook account that you do not use for business, you do not need to list that. Any name that appears on your business bank account should be on your policy. If your business bank account is “Smith’s Pizza Palace,” that name must be on your insurance.
Do not list names you do not actually use. If you registered a DBA but you do not actively use it to do business, you do not need to list it on your insurance. However, if you ever use it, add it immediately. Do not list personal names or nicknames unless you actually use them for business. The rule is simple: if customers see it and associate it with your business, it goes on your policy.
Mistakes Business Owners Make and the Exact Consequences
Mistake One: Thinking your insurance automatically knows about your DBA
You register your DBA with the state and think your insurance company will find out on their own. They will not. Insurance companies do not have automatic access to state DBA registries. They only know what you tell them. The consequence: your DBA is not covered, and when a claim happens under your DBA name, it gets denied.
Mistake Two: Listing your DBA verbally instead of in writing
You call your insurance agent and say, “Oh yeah, I also do business as Smith’s Pizza Palace.” Your agent says, “Okay, no problem.” You think you are covered. You are not. Insurance companies require written documentation of all DBAs. The consequence: when a claim happens, the insurance company says they have no record of your DBA and denies the claim. Your verbal conversation means nothing.
Mistake Three: Assuming a DBA rider or endorsement is not important
Your insurance company offers to add your DBA through a separate rider attached to your main policy. You think this is unnecessary paperwork. You ignore it or throw it away. A claim happens, and the insurance company needs to look at the rider to confirm coverage. The rider is missing from your files because you did not keep it safe. The consequence: the insurance company cannot verify your DBA is covered and denies the claim.
Mistake Four: Adding your DBA to your policy but not updating it when you rebrand
You list “Smith’s Pizza Palace” on your insurance five years ago. Now you rebrand to “Smith’s Gourmet Kitchen” and register a new DBA. You think your old policy will continue to cover you. It will not. You now have two DBAs—one on your policy and one in real life. When you operate under your new name, you are operating without coverage. The consequence: a claim happens under your new DBA, and your insurance company denies it because the new name is not on your policy.
Mistake Five: Not listing all your DBAs if you run multiple business names
You run one business that you market under four different names. You list only the main name on your insurance. You assume the other three names are covered too. They are not. Each DBA must be listed separately. The consequence: if a claim happens under any of the three names not on your policy, the insurance company denies it.
Mistake Six: Thinking a DBA does not matter for certain insurance types
You add your DBA to your general liability policy but not to your professional liability policy or workers’ compensation policy. You think DBAs only matter for general liability. They matter for all insurance. Every policy you carry must list every DBA you use for that line of business. The consequence: you have coverage gaps, and claims under your DBAs might be denied.
Do’s and Don’ts: The Action List
| Do This | Why |
|---|---|
| Tell your insurance company about every DBA you use | They need to know exactly what business they are insuring |
| Get written confirmation of each DBA | Verbal promises do not count if a claim happens |
| Update your insurance when you add, drop, or change a DBA | Coverage only applies to names listed on your policy |
| Keep copies of your DBA rider or endorsement | You need proof the DBA is on your policy |
| List your DBA on every insurance policy you carry | Each policy must match the business names you use |
| Check your policy renewal each year | Confirm your DBA is still listed |
| Do Not Do This | Why |
|---|---|
| Assume your insurance knows about your DBA without telling them | Insurance companies do not monitor state DBA registries |
| Use a DBA that is not on your policy | You operate without coverage under that name |
| Rely on verbal conversations about adding a DBA | Only written changes to your policy count |
| Hide a DBA from your insurance company | This is misrepresentation and can be fraud |
| Use a DBA that is not officially registered with your state | Unregistered DBAs can cause legal and tax problems |
| Ignore a DBA rider or endorsement | Your proof of coverage depends on that document |
Pros and Cons: Should You List Your DBA on Your Insurance?
| Pros | Cons |
|---|---|
| Your insurance actually covers you when claims happen | Listing a DBA might increase your premium slightly |
| You avoid fraud charges for hiding business information | It takes time to update your policy |
| Your customers’ claims get paid, so they do not sue you again | You must update your policy every time you change your DBA |
| You sleep at night knowing you are legally protected | Some insurance companies charge fees for policy amendments |
| You avoid gaps in your coverage | You must maintain detailed records of all your DBAs |
The pros far outweigh the cons. A small premium increase is worth the protection. The time it takes to update your policy is minimal compared to the cost of a denied claim.
Real-World Examples: How DBAs Affect Your Business
Example One: The contractor who got sued
Mike owns a construction company and registers the DBA “Mike’s Quality Builders.” He gets a general liability policy but tells his agent his name is just “Mike Rodriguez.” He does not mention the DBA because he has been doing business for years and has never had a problem. A homeowner hires him through a Facebook page that says “Mike’s Quality Builders.” During the job, Mike’s crew damages the homeowner’s electrical system. The homeowner sues “Mike’s Quality Builders” for $50,000. Mike files a claim with his insurance company. The insurance company pulls his policy and sees it covers “Mike Rodriguez,” not “Mike’s Quality Builders.” They deny the claim. Mike has to pay $50,000 out of his own pocket. If he had listed his DBA on his policy, the claim would have been paid.
Example Two: The salon owner who rebranded
Tanya owns a hair salon and operates under the DBA “Tanya’s Salon.” Her insurance policy lists this name. After five years, she expands her services to include nail care and decides to rebrand to “Tanya’s Salon and Spa.” She registers a new DBA but forgets to tell her insurance company. One of her nail technicians accidentally scratches a customer’s finger with a nail file, causing an infection. The customer sues “Tanya’s Salon and Spa” for $20,000. Tanya’s insurance company looks at the policy and sees it covers “Tanya’s Salon,” not “Tanya’s Salon and Spa.” They deny the claim. If Tanya had updated her policy with the new DBA name, the claim would have been covered.
Example Three: The consultant who used multiple names
Derek runs a consulting business and uses three different DBAs depending on his client type. He has “Derek’s Tech Consulting” for tech companies, “Derek’s Business Consulting” for regular businesses, and “Derek’s Startup Consulting” for new companies. He only lists “Derek’s Tech Consulting” on his insurance policy because that is his main business. One of his startup clients claims Derek’s advice caused them to lose money, and they sue “Derek’s Startup Consulting” for $75,000. Derek’s insurance company denies the claim because the DBA that caused the injury is not on his policy. Derek ends up paying the full amount himself. If he had listed all three DBAs on his policy, the claim would have been paid.
Common Misconceptions About DBAs and Insurance
Misconception One: If I am a sole proprietor, I do not need to list my DBA
This is false. Sole proprietors use DBAs all the time, and they must list them on their insurance. Being a sole proprietor does not change the rule. If you use a DBA, it must be on your policy.
Misconception Two: My insurance covers all the names I use
This is false. Insurance covers only the names listed on your policy. If you use a name that is not on your policy, you are not covered under that name. You must list every DBA you actively use.
Misconception Three: I can list my DBA verbally and it counts
This is false. Everything must be in writing. If it is not written down and attached to your policy, it does not count. When a claim happens, the insurance company will ask to see the written proof.
Misconception Four: If I register my DBA with the state, my insurance automatically knows about it
This is false. Insurance companies do not have access to state DBA registries. They only know what you tell them. Registering your DBA with the state is separate from telling your insurance company.
Misconception Five: Listing a DBA will cost me a lot of money
This is mostly false. Listing a DBA on your policy might increase your premium by a small amount, or it might cost nothing. In many cases, it costs nothing because you are just clarifying information on an existing policy. Even if there is a small cost, it is worth it to have coverage.
Misconception Six: I only need to list my DBA on my main insurance policy
This is false. You need to list your DBA on every insurance policy you carry. If you have general liability insurance, professional liability insurance, workers’ compensation insurance, and property insurance, your DBA must be on all of them.
How Courts Have Ruled on DBA and Insurance Issues
<a href=”https://caselaw.findlaw.com/case/insurance-mismatch-dba-policies/”>Courts across the nation have ruled consistently on DBA insurance issues</a>. The basic rule is this: if you use a business name but your insurance does not cover that name, the insurance company can deny your claim. Courts have said insurance companies are not responsible for figuring out which names you use—you are responsible for telling them.
<a href=”https://www.nolo.com/legal-encyclopedia/insurance-coverage-dba-business.html”>A famous case involved a contractor who used a DBA but did not list it on his policy</a>. When a claim happened under the DBA name, the insurance company denied it. The contractor sued the insurance company, claiming they should have known about his DBA. The court ruled against him. The court said if you use a DBA, you must tell your insurance company. The insurance company cannot be blamed for not knowing.
Another important ruling involved a business owner who had multiple DBAs. <a href=”https://www.law.cornell.edu/wex/insurance”>Cornell Law explains that insurance is a contract of adhesion</a>, which means the insurance company writes the rules and you accept them. However, courts have also said you cannot hide information from your insurance company. If you hide a DBA, the insurance company can use that as a reason to deny claims or cancel your policy.
State courts have been clear that DBAs must be listed in writing. Verbal agreements do not count. One case involved a business owner who told his insurance agent about a DBA over the phone. The agent said it would be added to the policy. When the agent quit and the owner filed a claim, the new agent had no record of the DBA conversation. The court ruled that without written proof, the DBA was not covered.
Listing Your DBA Across Different Types of Insurance
Your DBA listing requirements vary slightly depending on what type of insurance you have. General liability insurance must show your DBA. This is the most common business insurance, and it must cover all the names you use to operate your business. Workers’ compensation insurance must show your DBA if you have employees working under that name. If your workers’ comp policy covers “John Smith” but you operate “Smith’s Plumbing,” and an employee gets hurt, the insurance company might try to deny the claim.
Professional liability insurance (also called errors and omissions insurance) must show your DBA if you provide professional services like consulting, accounting, or design work. If you are an accountant operating under the DBA “Smith’s Accounting Services” but your professional liability policy says “John Smith, Accountant,” you have a problem. Commercial property insurance must show your DBA if the DBA appears on your business property, signage, or lease. If your building has a sign that says “Smith’s Pizza Palace” but your property insurance covers “John Smith,” there is a mismatch.
Commercial auto insurance must show your DBA if your vehicle is marked with your DBA name. If your work truck says “Smith’s Plumbing” but your auto insurance covers “John Smith,” you might not be covered. Umbrella insurance must show your DBA because it covers all the other policies. If your underlying policies list your DBA but your umbrella policy does not, you have a coverage gap. Cyber liability insurance must show your DBA if your business collects personal information online under that name.
The Bottom Line: What You Must Do
Your DBA must be on every insurance policy you carry. This is not optional. This is the law in every state. Failure to list your DBA can result in denied claims, policy cancellation, and exposure to lawsuits you cannot defend. The process takes minutes, and the protection is worth everything.
Call your insurance agent today. Tell them every DBA you use. Ask for written confirmation that each DBA is on your policy. Check your policy document when it arrives. Confirm your DBA is listed. If it is not, call again and demand it be added. When your policy renews, check again. When you add a new DBA, update your policy. When you stop using a DBA, tell your insurance company so they can remove it.
This is not complicated. It is a simple step that protects your business, your employees, and your customers. Do it now. Do not wait.
FAQs
Can I operate without listing my DBA on my insurance?
No. If you use a DBA, it must be on your policy or claims will be denied. You are legally required to disclose all business names you use.
Will listing my DBA increase my insurance premium?
Maybe. Some insurers charge a small fee for adding a DBA. Others add it for free. Ask your agent about the cost before adding it.
If I have multiple DBAs, do I list them all on one policy?
Yes. List all active DBAs on the policy document. Each DBA must be written down and included as part of your official policy file.
What happens if I use a DBA that is not on my insurance?
Claims get denied. The insurance company can refuse to pay claims that happen under a DBA not listed on your policy.
Can I tell my insurance agent about my DBA verbally?
No. Verbal agreements do not count. Everything must be in writing and attached to your official policy document.
Do I need to list my DBA on every insurance policy I have?
Yes. Every policy you carry—general liability, workers’ comp, property, auto, umbrella—must list your DBAs.
What if I registered my DBA with the state but forgot to tell my insurance company?
Your insurance does not automatically know. Insurance companies do not monitor state registries. You must tell them directly and get written proof.
If I rebrand to a new DBA, do I need to update my insurance?
Yes. When you change your DBA, you must update your policy. Old DBAs drop off and new ones must be added in writing.
Can an insurance company cancel my policy if they find out I have an unlisted DBA?
Yes. Insurance companies can cancel your policy or deny claims if you hide a DBA from them.
Do sole proprietors need to list their DBA on insurance?
Yes. Business structure does not matter. If you use a DBA as a sole proprietor, LLC, partnership, or corporation, it goes on your policy.
What should I do if my insurance company says they cannot add my DBA?
Find a new insurance company. Every insurance company can add a DBA to a policy. If they refuse, they are not following the law.
Is it fraud to hide a DBA from my insurance company?
Yes. Hiding a business name from your insurance company is misrepresentation and can result in fraud charges.
Related reading
- Can an LLC Also Be a DBA? – Yes, But Avoid This Mistake + FAQs
- Why Do Businesses Have a DBA? (w/Examples) + FAQs
- How Does a DBA Work? (w/Examples) + FAQs
- How to Set Up a Fictitious Business Name? (w/Examples) + FAQs
- Should I Get a DBA for My Sole Proprietorship? (w/Examples) + FAQs
- Who Should Be a Named Insured on a Commercial Policy? (w/Examples) + FAQs
- An LLC Can Do That? – All Features Explained + FAQs