Match Carrier Legal Names, DBAs and USDOT Records

Match carrier records by the exact USDOT identifier and the legal-name/DBA relationship shown in the source, then preserve any unresolved conflict. Similar names, a shared address or the same telephone number can help you investigate a possible match; they are not enough to merge two carrier entities. Keep the original values and the evidence behind every match.

This guide helps broker operations teams and trucking-service sales teams turn a mixed shortlist into a usable entity record. The output is a documented match, a separate entity or a question requiring clarification. It is not a carrier approval or a list of confirmed buyers.

Know which name you are matching

The legal business name and the doing-business-as name answer different questions. FMCSA's MCS-150 instructions, items 1 and 2 distinguish the entity's legal name from a different trade name it uses. A familiar brand can therefore differ from the legal name on the carrier record without that difference alone establishing an error.

Build your shortlist around three separate fields:

Name supplied: exactly what appeared in the inquiry, export, carrier packet or website.
Recorded legal name and DBA: the names displayed in the source you checked, without silently replacing one with the other.
USDOT identifier: the exact record you resolved, with its source and observation time.

Keep applicable docket identifiers in their own fields, including the prefix. Do not put an MC number into the USDOT column because the digits look plausible. If the supplied identifier does not resolve to the expected business, the discrepancy remains open.

Decide what one row represents

For an operating-carrier shortlist, use one row per resolved USDOT entity. For a sales-account view, you may also need a group or brand record connected to several operating entities. Preserve that relationship separately; do not replace the underlying carrier identifiers with a group name.

FMCSA's guidance on legal-name and business-form changes says USDOT numbers identify specific persons or entities and are not transferable. It also explains that some changes can occur while the legal entity and USDOT number remain the same. That is why neither a new-looking name nor an unchanged name resolves a business transition by itself.

A sales team can manage a parent-company relationship while operations retains separate carrier records. The commercial account owner and the entity responsible for a particular movement may be different. Record both when relevant, with evidence for the relationship.

Resolve each candidate in a repeatable order

1. Preserve the input before cleaning it

Save the supplied name, identifier, source and date in read-only original columns. Create separate search fields for trimmed spaces, consistent capitalization or a common spelling variant. Those transformations make searching easier; they do not prove that two records represent the same entity.

Do not remove LLC, Inc. or a geographic term from the evidence copy. A simplified comparison name may bring two candidates together for review, but the original legal names must still be checked. Correct an obvious transcription error only in a separate resolved field, with a note explaining the evidence.

2. Start from the identifier, or build a small candidate set

Use the supplied USDOT number to open the official SAFER Company Snapshot. If only a name is known, search for candidates and compare their identifiers, legal/DBA names and locations. Do not select the first familiar result simply because its branding resembles the packet.

Our carrier lookup can help locate the record. Treat a directory result as a starting point for the source check. If no candidate can be tied to the supplied business with adequate evidence, label the row unresolved rather than manufacturing a number.

3. Compare names and supporting details field by field

Ask whether the supplied name is the recorded legal name, a displayed DBA, an older name with supporting history, or merely a claimed brand relationship. Compare address and contact information as supporting details, retaining their source dates. An address can be old; a phone can serve several businesses. Agreement strengthens a candidate match but does not settle a contradictory identifier.

For a claimed name change, ask for the evidence that connects the old and current names to the same entity. Do not infer that an acquisition transferred a USDOT number, or decide which registration a restructured business should use. Unclear registration questions belong with FMCSA and the business's responsible adviser.

4. Classify the result without overstating it

Use a small set of explicit outcomes:

Same recorded entity: the identifier and source evidence support the relationship between the supplied and recorded names.
Separate entities: the records resolve to different USDOT identifiers; retain both while any claimed relationship is reviewed.
Possible relationship: shared branding or contact details justify a follow-up, but the connection is not established.
Unresolved conflict: a material identifier or name disagreement prevents a reliable match.

Attach a reason to the outcome. “Same recorded entity because the supplied name appears as the DBA on this USDOT record” is more useful than a numeric confidence score with no explanation.

5. Keep transaction and service checks separate

A successful record match does not authenticate the person using those identifiers. FMCSA's fraud-prevention guidance recommends independently checking contact information and discussing the load through the SAFER-listed number when the supplied number differs. A genuine carrier's details can be misused.

For a load decision, continue with current authority, insurance, service and contact checks, preserving them in a carrier-verification evidence record. For prospecting, move the matched entity into your lead-list qualification workflow. Identity resolution establishes who the row describes; it does not establish demand for your service.

Worked example: three names, two entities, one unresolved relationship

Hypothetical example. Entity A and Entity B are labels, not real carrier identifiers. An equipment-service shortlist contains three rows:

“North Orchard Transport LLC,” tied to Entity A's USDOT record.
“Orchard Express,” tied to the same identifier. The checked record displays it as Entity A's DBA.
“Orchard Logistics Inc.,” tied to Entity B's different identifier and the same office phone.

The first two rows can become one entity entry for this shortlist, with both source rows and the DBA retained. The third stays separate. A common phone creates a relationship question, not permission to combine fleet counts or treat Entity B as already checked.

The research note separates conclusions:

Observed fact: two supplied names map to Entity A's legal-name/DBA fields; Entity B has a different recorded identifier.
Fit hypothesis: both entities might fall within the service team's target segment, subject to equipment and operating-location checks.
Relationship requiring confirmation: the shared phone may reflect a common office or service arrangement; ownership and purchasing responsibility remain unknown.
Confirmed buying need: none. No representative has established a service requirement, timing or decision process.

The useful output is two entity entries and one follow-up question. It is not three qualified leads, and it does not justify assigning one entity's authority or insurance evidence to the other.

Copyable entity-resolution worksheet

Use this block for each candidate match. Keep evidence references in your existing controlled workspace.

Original row reference / input source / date:
Supplied name and identifier:
Resolved USDOT number:
Recorded legal name / DBA:
Applicable docket identifier and prefix:
Source URL / source date / observed time and zone:
Matching details:
Conflicting or missing details:
Relationship evidence, if any:
Outcome: same entity / separate / possible relationship / unresolved
Reason for outcome:
Retained source-row references:
Next check / owner / recheck trigger:

Before accepting the cleaned shortlist, check that every merged row has an evidence-backed reason, every separate entity retains its own identifier, and every unresolved conflict has an owner. Preserve previous observations when a name changes. A current search result should not erase the evidence behind an earlier decision.

Frequently asked questions

Can the legal name differ from the company name on a website?

Yes. The website may use a trade name or brand. Check whether the relationship appears in the official record or can be supported independently. Similar branding alone does not resolve the entity.

Can I merge carriers that share a phone number or address?

Do not merge them on that basis alone. Preserve separate USDOT records and investigate the relationship. A shared contact can reflect a group, dispatcher, common office or outdated information.

Should I remove LLC and Inc. to find duplicate names?

You can use a simplified field to generate review candidates, but retain the original legal names. Name normalization is a search aid, not an automatic merge rule.

What if the USDOT number matches but the name differs?

Record both values and check the legal name, DBA, dates and any documented name history. If the discrepancy remains material, leave the match unresolved. Do not silently overwrite the supplied name or approve the transaction.

Does a business name change always require a new USDOT number?

No blanket rule follows from the name alone. FMCSA distinguishes continuity of the legal entity from changes that may require different registration. Use its current guidance and seek clarification for the actual business change; a shortlist should not make that legal determination.

Is a correctly matched carrier a verified sales opportunity?

It is a better-identified research candidate. Service fit still needs evidence, and a buying opportunity needs confirmation of a real problem, timing and purchasing responsibility. A clean entity record supplies none of those automatically.

By John Hauler, USDOTData's editorial persona. Sources reviewed September 27, 2026. This is a research workflow, not an official FMCSA determination or a claim of personal trucking experience.