What if my BOC-3 is rejected by FMCSA?
BOC-3 rejection is rare but real. The FMCSA L&I system rejects filings that name an unregistered process agent, that have a USDOT/MC mismatch, or that are submitted by an entity without a Form BOC-91 on file. The rejection notice arrives via email; the fix is to correct the underlying issue and resubmit through a registered process-agent provider with current BOC-91 standing.
The most common rejection reason is a process-agent provider whose Form BOC-91 has lapsed. Form BOC-91 is the upstream registration the provider files with FMCSA establishing that they are a registered process agent. The BOC-91 has to be current at the moment the BOC-3 is submitted; if it has expired or been revoked, every BOC-3 filed under that BOC-91 is rejected. Carriers caught in this situation switch to a different provider whose BOC-91 is current.
The second-most-common rejection reason is a USDOT/MC mismatch. The Form BOC-3 has fields for USDOT number and MC docket number; if the two don't match what the FMCSA L&I system has on file (because the MC was issued under a different USDOT, or because the carrier transposed digits at submission), the system rejects. The fix is to verify the USDOT-MC pairing in SAFER and resubmit with corrected data.
A less common rejection is a name mismatch — the legal name on Form BOC-3 has to match the legal name on file with FMCSA exactly. A carrier doing business as a DBA may need to update its USDOT registration via Form MCS-150 first, then refile the BOC-3 with the corrected legal name. The order matters: BOC-3 cannot pre-stage a name change that hasn't been processed by FMCSA yet.
Once the underlying issue is corrected, resubmission is electronic and typically clears within 2-24 hours. The original rejection does not penalize the carrier — there is no fee for rejected filings, and there is no FMCSA-side adverse action beyond the operating-authority impact of running without a current BOC-3 (which only matters during the 21-day vetting window for new authority or after a revocation event).