What Is Freight Fraud?

How this comes up in practice

A freight transaction that ended in a cargo loss came down to a gap no one checked: the carrier assigned on the rate confirmation and the driver who arrived at the dock both had paperwork that looked consistent with the load. The shipper released the freight because the pickup number matched and the driver knew the delivery address. What the shipper didn't verify — because there was no established protocol for it — was whether the carrier named on the rate confirmation had any knowledge of this load. A call to the carrier's SAFER-listed number, made before release, would have revealed that they didn't. The pickup number had been obtained through a compromised email account; the driver had no connection to the carrier. The paperwork was internally consistent; the authorization wasn't there. That gap — between records that look right and authorization that hasn't been confirmed — is the thread running through freight fraud patterns, regardless of whether the presenting party is impersonating a broker, a carrier, or both.

How official guidance frames the freight fraud problem

FMCSA's guidance on broker and carrier fraud identifies several overlapping categories: unauthorized USDOT number use, broker impersonation, fictitious pickups, double brokering without shipper consent, and identity theft affecting legitimate carriers and brokers. In practice these patterns often appear together in the same transaction — a fictitious pickup may involve a stolen USDOT number and a broker impersonation simultaneously. For adjacent verification steps, compare this with Carrier Identity Theft Explained, and How to Report Freight Fraud.

What connects these patterns is misrepresentation at a point where the affected party had no obvious reason to suspect it. The carrier, broker, or shipper typically has all the information they would normally rely on — the documents look right, the numbers check out, the communication is professional. Standard verification catches the problem; verification that stops one step short of the independent contact or official record comparison doesn't.

This guide focuses on document-level and contact-level verification because that's where the misrepresentations surface. An official FMCSA record that doesn't match the document in hand, or a contact that can't be confirmed through a channel the presenting party didn't introduce, is the signal that the transaction needs a slower look.

How freight fraud shows up in common transaction patterns

Freight fraud shows up differently depending on which side of a transaction you're on. A carrier may receive a convincing load offer that leads to an unpaid or stolen shipment. A broker may release a carrier packet only to find the documents belonged to a legitimate company with no involvement in the load. A shipper may pay an invoice while freight was picked up by someone with no authorization for that load. What connects these patterns is misrepresentation — a name, number, document, or instruction that wasn't what it appeared to be. FMCSA has issued formal fraud alerts addressing identity theft, double brokering, fictitious pickup, and payment redirection as documented patterns in U.S. trucking, and the FBI Internet Crime Complaint Center (IC3) processes freight-related business email compromise reports as part of its annual BEC tracking.

The most practical first response to a suspected fraud pattern is to slow down, pull the original documents, and compare what was communicated against what official records show. This guide introduces the most common patterns and the records most useful for that comparison.

Patterns that surface in records and contacts

Start with the identity trail: the first message, the company name used there, and the MC or USDOT number that later appears in documents. In this guide, that starts with fraud patterns that use false identities, incomplete documents, or rushed contact changes.

A pattern becomes easier to evaluate when each name, number, domain, and phone number is tied to the moment it entered the file. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

What to capture when a transaction pattern seems off

For what is freight fraud, the useful record is usually the one that shows where fraud patterns that use false identities, incomplete documents, or rushed contact changes first entered the file.

That record is stronger when it sits beside the dated lookup, the original message, and a note from the party connected to the transaction. It is weaker when it has been renamed, cropped, forwarded without headers, or separated from the transaction timeline.

Questions that separate a mismatch from an innocent gap

Hold the booking, dispatch, pickup, or payment decision when the file depends on a new contact path, revised document, missing official record, or mismatch that no one has explained.

The pause should be narrow and written down: the field that does not line up, the source used to check it, and the person or channel that must answer before the work continues.

What official records establish versus what they leave open

For basic fraud-pattern review, preserve the earliest version of each document before later corrections blur the timeline. In this guide, that starts with fraud patterns that use false identities, incomplete documents, or rushed contact changes.

Keep the documents beside the message thread that introduced them, because the sequence often matters more than a single mismatch. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When a pattern warrants slowing the transaction

Ask questions that separate an operational mistake from an identity concern without accusing a party too early. In this guide, that starts with fraud patterns that use false identities, incomplete documents, or rushed contact changes.

Good answers point to a record, a known contact, or a dated confirmation rather than a general assurance. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Further context on fraud recognition

Fraud basics are most useful when they slow down conclusions. A familiar brand, correct MC number, or polished packet can still be used by an unauthorized sender. In this guide, that starts with fraud patterns that use false identities, incomplete documents, or rushed contact changes.

The safer habit is to write down the gap and the check it triggered, then decide whether the records resolved it. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When to escalate the concern

Escalation begins when the file still has an identity gap after ordinary confirmation steps. In this guide, that starts with fraud patterns that use false identities, incomplete documents, or rushed contact changes.

Move the issue to an internal lead, known company contact, insurer, law-enforcement contact, or official reporting channel based on what the records show. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ