W-9, COI and authority: the three documents that stall onboarding

A carrier passes every call, the rate is agreed, and then onboarding sits untouched for days because one document doesn't match another. This happens more often than it should, and it's almost always the same three items: the W-9, the certificate of insurance, and proof of operating authority. None of these are exotic requests. They just have to be correct, current, and consistent with each other, and that last part is where most delays come from.

The W-9: a name-matching problem, not a tax problem

The W-9 confirms the legal name and tax ID a broker will use to pay a carrier and report payments to the IRS. The stall usually isn't about the form itself, it's about mismatches: the business name on the W-9 doesn't match the name on the MC authority, or the entity listed isn't the one that actually holds the authority. A carrier operating under a DBA needs to make sure the legal name, not the trade name, is what appears on the form. Brokers cross-check this against FMCSA records, so a small discrepancy here can hold up an otherwise clean file.

The COI: coverage that has to match the load, not just exist

A certificate of insurance shows that a carrier has auto liability and cargo coverage in force. The common failure point is that the certificate is outdated, doesn't list the broker as certificate holder, or shows cargo limits too low for the freight being hauled. Insurance requirements vary by broker and by commodity, so a certificate that satisfied one shipper may not satisfy the next. The safest habit is to keep a current COI on file and request an updated one at renewal, rather than waiting until a load is already booked.

Authority: active status, not just having a number

Operating authority means a carrier is registered with FMCSA and authorized to haul for-hire freight in interstate commerce. The number itself isn't proof of anything if the authority is inactive, revoked, or under a different name than the one on the paperwork. Brokers check authority status against live FMCSA data before dispatch, because a carrier's status can change between one load and the next. This is standard vetting, not a sign of distrust, and it protects both sides if something goes wrong later.

Why the same document trips up different carriers

Onboarding requirements aren't standardized across brokers, so a document set that clears one broker's file can still get flagged elsewhere. Some of this is broker-specific policy, and some of it is just diligence about keeping records current. The practical fix is the same either way:

• Keep the legal name identical across the W-9, MC authority, and insurance certificate.
• Renew the COI before it expires, not after a broker asks for it.
• Confirm authority status directly with FMCSA if it's been a while since the last check.

Ellys runs an invite-only carrier network and checks authority against live FMCSA data before dispatch, then continues monitoring status afterward, so a carrier's file doesn't go stale between loads. This isn't unusual practice, but it does mean paperwork that's already consistent moves through onboarding without the back-and-forth described above.

Carriers who want to see what a clean onboarding file looks like, and get set up before the next load comes up, can start at /carriers.