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.

Key Takeaways

  • Identify the party that first introduced the load or document.
  • Write down each legal name, DBA, MC number, USDOT number, email domain, and phone number.
  • Compare the transaction record against official FMCSA records and the documents exchanged.
  • Pause when one party asks you to ignore a mismatch or move communication to a new channel.

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.

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.

How freight fraud shows up in common transaction patterns checklist

  • Identity of every party that introduced the load or document, with the credentials each provided
  • Documents exchanged before pickup, including any revisions and who sent each version
  • Official FMCSA records for each named party, checked at the time of the concern
  • Payment instructions and any changes, with the date and contact associated with each
  • Communications showing who asked for what and when

Patterns that surface in records and contacts

Use the same identifiers across every record. Small differences can be clerical, but they should be resolved before pickup, dispatch, or payment.

If a detail is missing, ask for the missing record rather than filling the gap from memory, an old packet, or a search result.

Patterns that surface in records and contacts checklist

  • Identify the party that first introduced the load or document.
  • Write down each legal name, DBA, MC number, USDOT number, email domain, and phone number.
  • Compare the transaction record against official FMCSA records and the documents exchanged.
  • Pause when one party asks you to ignore a mismatch or move communication to a new channel.

What to capture when a transaction pattern seems off

Save records in their original format when possible. Use one folder named with the load number, lane, date, and parties involved.

If a dispute, identity concern, or theft concern appears later, the timeline is easier to reconstruct when emails, PDFs, screenshots, call notes, and lookup results are grouped together.

What to capture when a transaction pattern seems off checklist

  • Original rate confirmation and every revised version.
  • Broker or carrier packet documents, including W-9, insurance, authority, and agreement records.
  • BOL, POD, seal records, pickup number, delivery confirmation, accessorial approvals, and invoices.
  • Screenshots or saved PDFs of official lookup results with the date checked.
  • Messages showing who requested, approved, or disputed a change.

Questions that separate a mismatch from an innocent gap

Questions should be specific and tied to records. That keeps the conversation professional and avoids unsupported accusations.

If an answer changes the transaction, document the person, date, time, and channel used to confirm it.

Questions that separate a mismatch from an innocent gap checklist

  • Which legal entity is tendering, carrying, paying, or receiving the freight?
  • Which official record supports the MC number, USDOT number, authority, insurance, bond, or trust detail?
  • Who is authorized to approve pickup, rerouting, revised documents, or changed payment instructions?
  • What document proves the current instruction, and who should receive a copy?

What official records establish versus what they leave open

One detail checking out is not the same as authorization confirmed. A correct number, a recognized company name, or a well-formatted document can each appear in a transaction where the communicating party has no connection to the registered entity.

A warning sign is a reason to document and verify, not a finding. Record what prompted the concern and what check it led to — that record determines whether the situation can be addressed if it escalates.

What official records establish versus what they leave open checklist

  • Do not assume a public lookup proves the sender is authorized.
  • Do not assume a document is current because it appears complete.
  • Do not assume a red flag proves wrongdoing by itself.
  • Do not assume a missing detail can wait until after pickup or payment.

When a pattern warrants slowing the transaction

When the file still has gaps, slow the transaction enough to preserve the record and move the question to the right channel.

That may mean a direct call-back, a shipper or receiver confirmation, an internal escalation, an insurer or claims contact, or an official complaint or reporting resource where appropriate.

When a pattern warrants slowing the transaction checklist

  • Record the unresolved mismatch in plain language.
  • Save the official lookup result with the access date.
  • Keep the original communication that created the concern.
  • Use official reporting channels for eligible complaints or cyber-enabled incidents.

Source Notes

Source use for What Is Freight Fraud?

These sources are used as verification and documentation references. They should be checked directly for current status, and they do not certify any private party, document, load, or payment instruction.

FAQ

If I notice a red flag mid-transaction, should I cancel the load?

Not necessarily. Document the concern and try to confirm identity through an independent channel before canceling. Canceling without documenting makes it harder to report or recover later.

Does freight fraud always involve false documents?

Most patterns do — fraud typically requires false identity information, altered documents, or misleading communication. The earliest signal is often a request to move faster than verification allows, or a contact that can't be confirmed through a channel independent of the current transaction.

What's the difference between freight fraud and a contract dispute?

A contract dispute involves disagreement over terms or performance between parties whose identities are established. Fraud involves misrepresentation of identity, authority, or documents — often before any contract is formed. The distinction matters for which official channels and remedies apply.

Source References

  • Broker and Carrier Fraud and Identity Theft Federal Motor Carrier Safety Administration. primary source. Last checked 2026-06-01. FMCSA guidance on broker and carrier fraud, unauthorized USDOT use, suspicious links, SAFER phone comparison, NCCDB, OIG, FTC, and IC3 reporting pointers.
  • Cargo Theft Federal Bureau of Investigation. primary source. Last checked 2026-05-15. FBI overview of cargo theft, including strategic theft trends such as identity theft, fictitious pickup, account takeover, double brokering scams, and fraudulent carriers.