A carrier contact change is a reason to reconcile records, especially before a new shipment. Compare the new phone, email domain, address, and named contact with a saved prior record and current official registration information. A change is not proof of fraud: companies relocate, change dispatch providers, add staff, and update registrations.
Find the carrier’s public registration record in HaulFacts lookup before comparing it with your own prior vendor file. The two records can have different update dates.
Identify what changed and when
Separate the federal record date, your own last-approved snapshot, and the date a person contacted you. These dates answer different questions. An MCS-150 date does not establish when a particular phone number or address changed; that needs field history or saved before-and-after records. A phone changed in your vendor file today may have been a legitimate federal update weeks ago; an official record may also lag a valid business change.
Make a compact before-and-after note. Include the field, old value, new value, source, observed date, and any explanation received. Avoid overwriting the old value without preserving the evidence that triggered review.
Verify through an independent path
Use a known phone number from an official profile or a trusted prior contact, rather than replying to the new email or calling only the new number. Ask the company to confirm the booking contact and the changed detail. Compare legal name, USDOT, MC identifier where relevant, and the load-specific contacts.
For example, a carrier that has hauled before emails from a new domain and asks for a wire change. A calm response is to call the number already on file or listed in the official record, confirm the request with an authorized person, and document the result. The new domain is a discrepancy to resolve, not a conclusion about the carrier.
What FMCSA cautions about identity theft
FMCSA warns that legitimate carriers can be victims of identity theft and recommends independently verifying contact information and documents. This is why a matching USDOT number alone does not authenticate a transaction. Verify carrier identity has a broader booking workflow.
If official registration details appear inaccurate, the carrier can use FMCSA’s update processes. A third party should retain the source and direct relevant data-quality questions to the appropriate process rather than publishing an allegation.
Escalate the mismatch, not the label
An organization might require a second reviewer for recent changes to bank details, contact domain, pickup instructions, or carrier identity. That can be a prudent control. Describe the action as “identity verification pending” or “contact change under review,” not “fraud suspected,” unless independently supported facts and your process justify a different conclusion.
Make the result time-bound. A phone change confirmed today may still be rechecked before a later high-value tender if the transaction or company policy calls for it.
Use shared carrier addresses to investigate common public fields carefully and read a carrier profile to keep identity, authority, safety, and insurance evidence separate.