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. FBI IC3 annual reports note that business email compromise — a category that includes freight-specific payment redirection fraud — consistently ranks among the highest-loss cybercrime categories by dollar amount, and IC3 staff have specifically cited organized document submissions as more actionable than incomplete reports.

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

Official-resource pages are entry points, not substitutes for checking the live source. In this guide, that starts with which records to preserve before using official complaint or reporting portals.

Record the exact URL, lookup date, and field you relied on so later reviewers can see what the source showed at the time. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

What to preserve before and after each submission

For how to report freight fraud, the useful record is usually the one that shows where which records to preserve before using official complaint or reporting portals first entered the file.

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

Questions that match the incident type to the right reporting channel

Hold the lookup, complaint, or reporting 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 an official report accomplishes versus what it can't guarantee

When using official channels, preserve both the source page and the transaction records that made the lookup necessary. In this guide, that starts with which records to preserve before using official complaint or reporting portals.

For reporting portals, keep confirmation numbers and copies of what was submitted. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When the documentation file is ready to file across multiple channels

Official-source questions should match the incident type to the right record or reporting channel. In this guide, that starts with which records to preserve before using official complaint or reporting portals.

If a source has limits, note those limits rather than stretching the record beyond what it can show. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Further reporting channel context

Official records can lag, omit context, or show only a narrow regulatory fact. In this guide, that starts with which records to preserve before using official complaint or reporting portals.

Use official resources as evidence of what the source says, not as certification that a private transaction is ready to rely on. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When to use this channel versus another

Escalate when the official source points to a complaint path, reporting portal, or professional channel outside this site's scope. In this guide, that starts with which records to preserve before using official complaint or reporting portals.

Keep the source result with the transaction file so the next step is based on dated records. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ