How to Report Freight Fraud

How this comes up in practice

The most actionable fraud reports are filed with a complete document set assembled before opening the form, not immediately after discovering a problem. IC3 asks for communication records showing how a cyber-enabled incident was initiated — email headers, domain information, the message sequence. NCCDB asks for specific records supporting an FMCSA-jurisdictional complaint. Each reporting channel is designed to work with a specific kind of documentation. Organizing the transaction file — rate confirmation, carrier packet, communications, official lookup records, payment instructions, and any changes to those instructions — before filing produces a report the receiving agency has enough information to act on. A file that takes an hour to assemble is more useful than a report filed immediately with incomplete records.

What makes a fraud report actionable versus informational

A fraud report filed immediately after discovering a problem, without organized documentation, creates an informational record — it tells the receiving agency that something happened. A report filed with email headers, official lookup screenshots, and a complete transaction file gives investigators data they can act on. The difference between the two is the document preparation that happens before the filing form is opened. For adjacent verification steps, compare this with FMCSA NCCDB Complaint Guide, FTC / FBI IC3 / OIG Reporting Checklist, and What to Do After Cargo Theft.

The reporting channels in this guide serve different purposes. NCCDB handles FMCSA-jurisdictional matters. IC3 handles cyber-enabled crimes. FTC handles consumer fraud patterns. DOT OIG handles allegations involving DOT programs. Filing with the wrong channel doesn't mean the report is useless, but it does mean the agency receiving it may lack the authority to act on the specific incident type.

The document preparation that makes reporting effective is the same preparation that makes every other follow-up step viable — insurance claims, legal review, bond claims. Building the file once, before any process begins, is more efficient than assembling different documents for each channel in sequence.

Organizing documentation before using official reporting channels

Reporting freight fraud through official channels starts with documentation, not with a complaint form. The records preserved before filing — rate confirmations, carrier packets, email headers, BOLs, PODs, payment instructions, official lookup screenshots — are what give a report enough substance to be useful. Filing without organized documentation typically results in a report that can't be acted on.

Different reporting channels serve different purposes, and choosing the right one depends on what actually happened. NCCDB handles eligible FMCSA-jurisdictional matters. IC3 handles cyber-enabled incidents including email fraud and account takeovers. FTC handles consumer fraud patterns. DOT OIG handles allegations involving DOT programs, federal funds, or FMCSA-regulated entities in a federal context.

Records to organize before filing with any reporting channel

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 before and after each submission

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 match the incident type to the right reporting channel

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 an official report accomplishes versus what it can't guarantee

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 documentation file is ready to file across multiple channels

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