BOC-3 After an Acquisition, Merger, or Name Change

Buying another carrier, getting bought, or changing your LLC name all touch the BOC-3 in different ways - and getting the answer wrong is one of the easier ways to end up with a SAFER status that says NOT AUTHORIZED when you thought everything was in order. The BOC-3 is keyed to a specific legal entity name and a specific authority number.Anything that changes either of those is a refile trigger; anything that leaves both intact usually isn't. Below is the practical decision tree for the four most common scenarios.

Scenario 1: You Bought the Stock of Another Carrier

In a stock purchase, the legal entity itself doesn't change - the same LLC or corporation continues operating, but the equity is now held by a different person or parent company. Because the BOC-3 is tied to the entity name and the authority number, nothing on the BOC-3 needs to change. What does change: ownership of the corporate parent, which usually triggers an MCS-150 update (FMCSA tracks the contact and address record on the operation), and possibly insurance rebinding. The BOC-3 itself stays as filed. The only edge case is when the seller's blanket provider has gone out of business independently of the deal - in that case you refile to point at an active provider, not because the deal triggered it.

Scenario 2: You Bought the Assets, Operating Under Your Own MC

An asset purchase means you bought the trucks, the customer contracts, sometimes the brand, but not the legal entity. You operate the acquired business under your existing company and authority. Your existing BOC-3 covers everything - you didn't change anything about your authority, just absorbed more revenue. The seller's BOC-3 stays with the seller's entity, which probably winds down or gets sold for parts separately. No refile required on your side.

Scenario 3: You Bought the MC Number Itself

FMCSA does not generally treat an MC number as a transferable asset, but in practice some sales structure themselves around continuing the seller's authority - typically by keeping the seller's LLC alive and changing the membership. Because the legal entity on FMCSA's record stays intact, the existing BOC-3 stays valid for as long as the underlying entity name is unchanged. If the new owner wants to rename the LLC after closing - which is common, especially if rebranding - that triggers Scenario 4 below (a refile sequence we walk through start-to-finish in our LLC vs sole proprietor BOC-3 guide).

The far more common variant is that the new owner intends to operate under their own MC and treats the seller's authority as redundant. In that case the seller's BOC-3 is irrelevant; your own BOC-3 governs.

Scenario 4: Your Legal Name Changed

A legal-name change - for example, an LLC amendment from Apex Hauling LLC to Apex Logistics LLC, or a conversion from sole-proprietor to LLC - is a refile trigger. The BOC-3 has the old name on it; the FMCSA record needs the new name. The canonical sequence is:

1. Update your state filing.File the LLC amendment (or formation, in the case of a sole-prop conversion) with the secretary of state where you're organized.
2. Update MCS-150. File a name change on the carrier's MCS-150 biennial update so FMCSA's SAFER record reflects the new legal name. This usually takes a few business days to propagate.
3. Refile BOC-3 under the new name.Once MCS-150 reflects the change, your blanket process-agent provider files a fresh BOC-3 against the new legal name. The new filing supersedes the prior one in FMCSA's records.

Skipping the MCS-150 update is the most common mistake (alongside the other common BOC-3 filing errors) - some carriers refile BOC-3 first and then update MCS-150, which can produce a temporary mismatch. SAFER occasionally flags the mismatch and downgrades the authority status until the records reconcile.

DBA Changes Are Not Refile Triggers

A “doing business as” (DBA) name is a marketing alias, not a legal entity. If your LLC adds, drops, or changes a DBA, the underlying legal name on FMCSA records is unaffected - and so is your BOC-3. You may want to update SAFER if the DBA appears on your authority listing, but that's an MCS-150 line item, not a BOC-3 issue.

What If You Already Operated Under the Wrong Name?

Sometimes a carrier discovers months after a name change that the BOC-3 still has the old name. The fix is the same: update MCS-150 if not already done, then refile the BOC-3 under the current legal name. There's no separate FMCSA enforcement action against the carrier just for the lag - the rule cares that a current designation exists, not that every prior designation matched in real time. File the corrected BOC-3 and the record reconciles.

Why The MCS-150 Sequence Matters

The reason carriers should update MCS-150 before refiling BOC-3 is timing on FMCSA's side. The BOC-3 acceptance system validates the legal name on the new filing against the legal name on the carrier's active record - which is whatever MCS-150 most recently set. If MCS-150 still has the old name and you submit BOC-3 with the new name, the validator flags a mismatch and rejects. Going in the other order - update MCS-150 first, wait for SAFER to refresh, then file BOC-3 - moves both sides to the new name in the right sequence. The MCS-150 update typically takes a few business days to propagate. Carriers in a hurry sometimes call FMCSA directly to confirm the record has flipped before refiling BOC-3, which avoids burning a rejection cycle.

Mergers Where Two MC Numbers Survive

Some mergers are structured to keep both predecessor authorities alive temporarily - usually because customer contracts are tied to the seller's MC number and the buyer wants to preserve continuity for those contracts. In that case, both MC numbers continue to need their own BOC-3. The acquiring entity files (or already has) a BOC-3 under its own legal name; the acquired entity's BOC-3 stays in force as long as that legal entity is still on the FMCSA record. Eventually one of two things happens: either the acquired entity is wound down and its authority surrendered (BOC-3 falls out with the authority), or the acquiring entity absorbs it via a merger filing that updates the legal name on the surviving authority - which becomes Scenario 4 above and triggers a refile under the merged name.

Authority Reinstatement After an Ownership Gap

Occasionally a carrier's authority lapses during the transition period of a sale - the seller stops paying for insurance, FMCSA revokes authority before the buyer takes over, and the buyer reinstates. If the legal entity name didn't change during that gap, the original BOC-3 is usually still on file and the reinstatement reactivates the existing authority record without needing a new BOC-3. If the buyer also changed the legal name as part of cleanup, that's a refile trigger on top of the reinstatement. Our standalone guide on BOC-3 after authority reinstatement walks through that sequence in detail.

Quick Reference: Refile or Don't?

• Stock purchase, same legal name:Don't refile.
• Asset purchase, your own MC continues:Don't refile.
• You added a new DBA:Don't refile.
• You changed the LLC's legal name: Refile (after MCS-150 update).
• You converted from sole prop to LLC: Refile under the new entity.
• FMCSA issued you a new MC number: Refile against the new authority.
• Your old blanket provider lost FMCSA registration: Refile through a provider with active registration in every state.

Bottom line: A stock purchase or asset deal usually leaves the BOC-3 untouched, but a legal-name change or a new authority number means refile. Update MCS-150 first, then refile BOC-3 under the current legal name. Refile your BOC-3 under the new name for $75 flat.