Guide
How to Handle a COI With Wrong Named Insured
By Keelstar Team · Updated July 11, 2026
The short answer
When a COI lists the wrong named insured, stop work authorization until the broker reissues the certificate with the legal entity that matches your contract and W-9. Named insured errors are among the most common certificate deficiencies — DBAs on invoices while the policy covers a parent LLC, former company names after mergers, or individual names instead of corporate entities. Contact the vendor's broker directly with your contract party name and request a corrected ACORD 25. Do not accept handwritten edits on the certificate PDF. If the mismatch reveals the vendor is performing work under an uninsured entity, escalate to risk management and legal before allowing continued access. Document the deficiency, correction request date, and revised certificate receipt.
How named insured mismatches happen
Brokers sometimes pull certificates from outdated account records. Vendors operating under trade names confuse AP and risk reviewers. Subcontractors newly formed as LLCs may still have certificates under the owner's personal name. Construction tiers amplify the problem when lower-tier subs change entities mid-project without notifying upstream parties.
Compare three sources
Cross-check the named insured against your executed contract, vendor master record, and W-9 legal name. All three should reconcile — or you should have documented why they differ, such as a parent-subsidiary guarantee arrangement.
- Contract counterparty legal name
- W-9 line 1 legal name
- ACORD 25 named insured box
- Invoice header if DBA is used operationally
Immediate steps when insured is wrong
Mark the certificate deficient. Notify the vendor and copy their broker with the correct legal name. Suspend site access or PO release until a corrected certificate arrives. Do not store the deficient certificate as 'approved with exception' without risk management sign-off.
Working with brokers on corrections
Brokers reissue certificates quickly when given the contract entity name and policyholder account details. Provide the vendor's policy number if known and your certificate holder address. Most corrections turnaround in one to two business days — faster than disputing a denied claim later.
Entity structure red flags
If the performing entity differs from the insured entity — for example, work performed by 'ABC Plumbing LLC' but insured shows 'John Smith' — ask whether a legal relationship exists and whether coverage follows. Uninsured shell arrangements create liability exposure for general contractors and property owners.
Prevent repeat mismatches at onboarding
Collect legal entity name in your vendor intake form and pass it to COI request templates. Auto-compare incoming certificate insured names to vendor master data. Flag fuzzy matches for human review before approval.
Frequently asked questions
- Is a DBA on the certificate acceptable if it differs from the legal name?
- The named insured should be the legal entity covered by the policy — often the LLC or corporation. DBAs may appear in the description of operations but should not replace the insured name unless the policy explicitly covers the DBA as an insured.
- Can we white-out and correct the named insured on a COI?
- No. Request a reissued certificate from the broker. Hand-edited certificates fail audits and may not reflect actual policy records.
- What if the vendor recently changed their company name?
- Request an updated certificate reflecting the new legal entity and confirm the underlying policies were endorsed for the name change. Contracts, W-9s, and COIs should align on the current legal name.
- Does named insured mismatch void all coverage?
- Potentially — if the entity performing work is not the insured on the policy, their insurer may deny claims. Treat mismatch as a critical deficiency, not a clerical typo.
Related guides
Put this into a monitored workflow
COI Tracker handles this continuously — with reminders and an audit trail.