Montgomery County DBA search — how to look up a fictitious business name (OH)
A fictitious business name (DBA) filed in Montgomery County, Ohio gives you a person’s name · the one signing the lease or the equipment contract · but not their entity status or credit history. For underwriters, that distinction matters. A DBA filing is public record, easy to look up, and tells you who operates under an assumed name. It does not tell you whether that person is a sole proprietor, an LLC, or a corporation. Without that entity type, you cannot assess liability structure or file a UCC lien properly.
What a Montgomery County DBA filing actually contains
A fictitious business name registration in Montgomery County shows:
· The assumed name (the “doing business as” name) · The true legal name of the owner or entity filing it · The business address and mailing address · The filing date and expiration date · The signature and oath of the filer
That is the substance. It does not include ownership percentages, member or officer names, tax ID, or business classification. If an LLC with three members files a DBA under one member’s name, the county record shows only that member’s signature · not the full membership structure. For credit underwriting, you need more than a DBA to build a complete picture.
How to search Montgomery County DBA records
The Montgomery County Recorder’s Office (Dayton, Ohio) maintains a searchable database of assumed name filings. You can access this through the county’s official online system. Search by the DBA name, the owner’s legal name, or the filing date. Results return the current status (active, expired, or abandoned) and basic filing information.
Most DBA searches are fast. You get a PDF or printed record within minutes. The record is public and costs little to obtain. If you need certified copies, the county charges a small fee and can mail them within days. For routine credit underwriting, a basic search is usually sufficient.
A DBA is not an entity type
This is where many underwriters stumble. A DBA is a registration of a name, not a legal entity. If you see “Jane Smith DBA Smith Plumbing” in a Montgomery County filing, Jane Smith is the entity · either a sole proprietor, or the authorized signatory of an LLC or corporation. The DBA does not tell you which.
This matters for UCC filings. If you take a security interest in equipment, you must file the UCC against the correct legal entity name. Filing against “Smith Plumbing” alone is not enough · you need to know whether the debtor is “Jane Smith, sole proprietor” or “Smith Plumbing LLC” or “Smith Plumbing Inc.” The Montgomery County DBA record does not give you that. You have to look elsewhere · the Secretary of State (for entities registered in Ohio) or the county auditor (for sole proprietorships).
Why you need both a DBA search and an entity search
A applicant tells you: “I do business as Premier Equipment Services in Dayton.” You search Montgomery County for the DBA. You find it · filed by Robert Chen, active, address matches his credit application.
Now you need to know: Is Robert Chen a sole proprietor? Or does he own this business through an LLC? If it is an LLC, is the LLC registered with the Ohio Secretary of State? If so, is Robert the only member, or is there outside capital?
The DBA search alone does not answer these. You must search the Ohio Secretary of State’s business registry for an LLC or corporation named “Premier Equipment Services” or “Chen Premier Services” or similar. If the entity is registered, you will see the members, managers, registered agent, and status. If it is not registered, Robert Chen is operating as a sole proprietor under an assumed name · which is legal, but changes your liability and lien-filing strategy.
DBA expiration and renewal flags
Montgomery County DBA filings expire. The registration term varies, but an expired DBA means the filer is no longer legally authorized to use that assumed name. If your applicant’s DBA is expired and they have not renewed it, they are operating without a current assumed name registration.
This is not automatically a deal-killer. Many small operators let DBAs lapse because they do not realize the filing has expired, or because they intend to wind down the business. But an expired DBA is a red flag. Ask the applicant: Are you still using this name? Why has the registration lapsed? How long has it been expired? If the DBA expired six months ago and they are still accepting contracts under that name, they are in technical violation of Ohio law.
Check the filing and expiration dates carefully. If you are looking at a new applicant, the DBA should be current and active.
The underwriting risk
The real risk is incomplete verification. You look up a DBA, confirm the owner’s name, and assume you have verified the business. You have not. You have verified that one person registered one name with the county. You have not verified:
· Whether that person controls an LLC or corporation · Whether there are other owners or members · Whether the entity has a tax ID or credit history · Whether the entity is in good standing with the state · Whether there are UCC liens or tax liens against the entity
For a $50,000 equipment lease, a DBA search is a start. For a $500,000 line of credit, it is a first step, not a final answer.
Bottom line
A Montgomery County DBA search is fast and public. It tells you who filed an assumed name and when. It does not tell you the legal entity type, ownership structure, or entity status. Always pair a DBA search with a Secretary of State entity search and a UCC/lien search to build a complete credit file. If you are cross-checking applications across multiple states, doing this manually is tedious · one county here, another state’s registry there, scattered county filings for liens. A unified verification tool that pulls DBA records, state entity data, and lien filings into one report saves time and reduces the chance you miss a flag.