Skip to article
HSJGlobal

DBD name troubleshooting

Why DBD Rejects Company Names and How to Correct Them

Identify the reason first, then repair the name pair and filing plan without introducing a new conflict.

By Elara Vance 6-minute read

DBD normally rejects a proposed company name because it is unavailable, prohibited, misleading, incorrectly formed or inconsistent across languages. The right correction depends on the reason. Changing only a spelling may not solve a name that sounds identical to an existing entity; translating only the English form may not solve a Thai-English mismatch; and removing a regulated word may not solve an underlying activity problem.

Treat a rejection as a diagnostic result, not an invitation to submit random alternatives. Preserve the system result, identify the exact category of issue, decide whether the business identity or only the presentation must change, then submit one revised pair that can be used consistently in the incorporation file.

Key takeaways

  • An exact match is not required for a problem: a name that sounds the same or can mislead can also be unacceptable.
  • Government, public-authority, regulated-sector and certain entity-type wording need extra care and sometimes evidence of approval.
  • Thai and English forms must remain aligned in meaning or pronunciation; changing one version in isolation can create a separate refusal reason.
  • Symbols, Roman numerals and specified prohibited wording are not reliable ways to differentiate a name.
  • A corrected name should be tested against the planned business, entity type and incorporation particulars before it is resubmitted.

The main DBD name-rejection categories

The first category is confusing similarity. DBD’s published name rules address names that are the same as, or have the same pronunciation as, an earlier registered partnership or company where that could cause confusion. A name may therefore fail even if the founders changed punctuation, added a generic word or altered a small part of an English spelling.

The second category is restricted or misleading wording. The published rules identify royal and current royal-family references, government and public-authority wording without permission, wording suggesting government or international-organisation ownership, certain regulated business terms, and wording such as “school”, “institute”, “college” or “university” without the relevant approval. The applicable facts and current regulator requirements matter; the name itself cannot create authority to operate a controlled business.

The third category is form and language. DBD’s rule covers names containing symbols or Roman numerals and requires the foreign-language name to match the Thai name in meaning or sound. It also identifies certain entity-related terminology and words that cannot be used under the attached schedules. Consult the DBD’s published name rule and schedules when the problem involves a protected word or close name rather than assuming an automated result explains every legal condition.

Match the correction to the real defect

Use the result notice and the final proposed name pair to decide which of three fixes is needed: a distinction fix, a permission fix or a bilingual-record fix.

DBD company name correction path A rejected name is classified as confusing similarity, controlled wording, or language and form mismatch. Each category has a different correction, followed by a renewed DBD reservation submission. DBD rejects the name Preserve the result and diagnose it Too similar Change the distinctive core Controlled wording Remove it or obtain support Language or form Rebuild the Thai-English pair Resubmit only after the filing record aligns Do not replace one defect with another
The correction should address the exact cause of rejection, not merely make the name look different.

For a similarity problem, change a material part of the name and test the new Thai and English forms for new close matches. For a controlled-word problem, remove the term unless the business genuinely has the current authority support required to use it. For a bilingual mismatch, decide whether the Thai or English form is the true commercial identity and rebuild the other form to match it in meaning or sound.

Do not attempt to solve a substantive issue with typographical camouflage. Adding punctuation, a symbol, a Roman numeral or a generic descriptor often leaves the confusing element untouched. It can also create a new form issue under the published DBD rules.

Fix the cause before you submit a new name

A review can separate an editable name issue from a business, ownership or document condition that needs to be resolved first.

How to avoid a repeated rejection

Before resubmission, run the full screen again: the revised Thai and English names, close DBD record results, controlled words, intended entity suffix and the real business activity. Use the current DBD automatic name-reservation system for the operative submission, rather than relying on a prior draft or an informal interpretation of the rejection.

Also retain one approved version-control record. It should show the rejected version, the specific modification, the Thai and English forms, and the person who may use the new name in the incorporation documents. This prevents an old name from reappearing in a Memorandum of Association, director resolution, overseas document or bank onboarding pack.

Where the revised name contains a word that may be controlled, keep a copy of the applicable authority approval or supporting evidence with the resubmission file. Do not describe a conditional approval as if it were automatic DBD clearance. The right evidence and the right name must reach the correct authority in the right process.

When the name problem is really a business problem

A name that implies finance, education, a government role or another controlled activity may reveal that the company has not yet determined its operating permissions. In that situation, correcting the name alone is not enough. The business needs to decide whether the activity is intended, what approval applies and whether the proposed ownership, capital, documents and timing support that route.

Place the reworked name in the correct registration context by checking it against the Thailand company establishment process . The DBD name decision is only one component of setting up the entity; it cannot approve the activity, secure a licence or validate a foreign-investment path.

If the legal vehicle is a Thai private limited company, ensure the corrected name is carried into the same set of particulars that will be lodged next. Review the private limited registration requirements that follow rather than treating the reservation as the final workstream.

A correction decision before you resubmit

Resubmit when you can point to a clear cause, a material correction, a coherent Thai-English pair and an incorporation file that is ready to use the new result. This is a sound “go” condition for a straightforward availability or language issue.

Stop and escalate the review where the rejected wording relates to a regulated activity, claims a public status, resembles an established entity in the same market, or masks an unresolved business model. A name correction must not create an inaccurate company identity just to move the reservation forward.

Resolve the DBD issue without breaking the filing plan

We can help map a corrected name to the documents and regulatory questions that need to remain aligned in the next submission.

Frequently asked questions

Can I add a number or symbol to make a rejected name different?

Do not assume that this will work. DBD’s published rule addresses symbols and Roman numerals, and the revised name still has to avoid confusing similarity or another separate prohibition.

Does a rejected name mean the company application is rejected?

A name-reservation result and incorporation approval are distinct stages. Correct the name issue and then ensure the remaining incorporation requirements are also ready for filing.

On this page
Chat with an Expert