Broker Fraud vs Carrier Fraud

How this comes up in practice

A carrier accepts a load through a rate confirmation that lists a real, active broker MC number. The load moves, delivers, and is invoiced. Two weeks later, when payment is overdue, the carrier searches the MC number in L&I and finds it belongs to a company that is unaware of the load. The email address on the rate confirmation, on close inspection, used a domain registered two weeks before the booking. The carrier moved a legitimate load in good faith; the actual broker never tendered it. Both accounts are correct. What the situation created was a carrier who needs to establish the chain of events for any claim they file — and who needs to separate the broker-side documentation from the delivery documentation in order to use either. Organizing records that show who introduced the load, through what channel, and using which credentials is the work that makes the file usable for claims, reporting, or legal review, regardless of whether the fraud was primarily broker-side, carrier-side, or both.

Why the fraud type determines what you document first

Broker fraud and carrier fraud produce different documentation priorities because they implicate different records. When the concern is broker-side — someone tendering loads without valid authority or impersonating an established broker — the records that matter are broker authority status in L&I, the domain and contact path that introduced the load, and any changes to payment instructions. When the concern is carrier-side — someone presenting a carrier's credentials without authorization — the records that matter are the SAFER contact for that carrier, the packet documents and how they arrived, and whether carrier management can confirm the dispatcher and the load. For adjacent verification steps, compare this with Fake Broker vs Fake Carrier, How to Verify a Freight Broker, and How to Verify a Motor Carrier.

The two can overlap in the same transaction. A fictitious pickup frequently involves someone who impersonated a broker to get the load tendered, then impersonated a carrier to arrange pickup. In that case, the documentation task covers both sides: the broker identity evidence and the carrier authorization evidence are each needed for reporting and for any claims process that follows.

The guide covers both patterns because the comparison is operational. Freight fraud reporting channels differ by the type of conduct involved — NCCDB handles FMCSA-jurisdictional matters, IC3 handles cyber-enabled elements. Organizing the records with the fraud type in mind, rather than treating all suspected fraud the same way, puts the file in the right shape for whichever channels apply.

Distinguishing broker misrepresentation from carrier misrepresentation

Broker fraud and carrier fraud often look similar in the moment — someone is misrepresenting who they are and what they can do. The distinction matters for documentation and reporting because the relevant records, authority types, and complaint channels differ by role.

Broker fraud typically involves someone tendering loads without valid broker authority or misrepresenting payment terms, company identity, or affiliation. Carrier fraud typically involves someone using a carrier's name, USDOT number, or packet documents without that carrier's authorization, or picking up freight under false pretenses. Both can happen in the same transaction, involving a fraudster who impersonates both roles in sequence.

Records that separate broker authority from carrier operating status

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.

What to preserve when the type of misrepresentation is unclear

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.

Questions that clarify which party's credentials need verification

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.

What a real MC number or USDOT number leaves open about the sender

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.

When the fraud type determines which reporting channel applies

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.

Source Notes

FAQ