Employer Liability for a Personal Vehicle: Who's Actually on the Hook?

This post explains coverage mechanics in general terms. It is not legal or insurance advice, and coverage outcomes depend on your specific policy wording, insurer, and jurisdiction — confirm anything specific to your company with your broker or coverage counsel.

Employer liability for a personal vehicle used at work is the question most HR and ops managers only think about after an accident, not before. If an employee gets into an accident while driving their own car for a work errand, most assume one of two things: either "that's between them and their insurance" or "our business insurance covers it." Neither is reliably true, and the gap between those two assumptions is exactly where the exposure lives.

The two policies behind employer liability for a personal vehicle

There are two separate coverages in play, and they do different jobs. The employee's own personal auto policy — assuming they declared business use on it — is the first responder: it covers their own liability and their own vehicle and injury, up to their policy limits. The employer's non-owned auto liability coverage (in Canada, this is typically an OPCF 27B endorsement; in the US, a similar non-owned/hired auto endorsement) covers the company's liability exposure specifically — not the employee's own losses — and normally only kicks in as an excess layer, after the employee's personal limits are exhausted.

A mileage reimbursement rate — CRA or IRS — is a separate thing entirely. It compensates the employee's running costs, including a notional insurance line item baked into the rate. It does not respond to a claim. Treating the reimbursement rate as a form of coverage is the most common misunderstanding in this whole picture.

Where the exposure actually shows up

The real risk sits in two places: an employee who didn't declare business use on their personal policy (many don't, often without realizing they should), and a company that doesn't carry non-owned liability coverage at all. When both of those are true at once, there's no policy responding anywhere in the chain for a third-party claim — the company ends up self-insuring the exposure out of pocket, or contesting it, with nothing behind it. Declared use plus employer coverage is the version of this that resolves cleanly, with each policy doing the job it's designed for.

The part that no insurance policy — from either side — will ever cover

Regardless of which of the above applies, there's a set of costs that no coverage responds to in any scenario: regulatory fines, criminal negligence penalties, and tax or payroll penalties are uninsurable in every jurisdiction, as a matter of public policy. So is the multi-year premium escalation that typically follows a claim. This is a meaningful share of the total exposure a company is actually carrying — which is why the useful move isn't better insurance, it's preventing the underlying gap (an undeclared policy, a missing endorsement, an expired license nobody caught) from existing in the first place.

That's the same audit-trail idea an independent reviewer landed on when testing Fuelshine's compliance approach: The Expenses Doctor's review praised the AI validation layer for flagging anomalies — missing business purpose, off-hours trips, distance mismatches — before a claim reaches a manager's desk. That's not insurance, and it doesn't change what a policy covers. But a documented, audit-ready record of who was driving, when, and why is exactly the kind of thing that matters if a liability question ever actually comes up — and it's cheaper to have built before you need it than to reconstruct after.

Not sure where your own policy gaps are? Get your free 60-second Fuelshine audit → Takes about 60 seconds · no credit card, no sales call.

A thank-you to The Expenses Doctor

Thanks to The Expenses Doctor for the independent look at Fuelshine's AI validation layer — the audit-trail point this post builds on came from their unpaid, unaffiliated testing, not from us describing our own product.

FAQ

If an employee crashes their own car on a work errand, does the company's insurance automatically cover it? Not automatically. The employee's personal auto policy (with business use declared) responds first. The employer's non-owned liability coverage, if the company carries it, typically applies only as an excess layer on top of that — and only covers the company's own liability exposure, never the employee's own vehicle damage or injury.

Does the CRA or IRS mileage rate include insurance coverage? No. The mileage rate compensates the employee's vehicle running costs, including a notional insurance line item in the calculation — but it is not an insurance product and does not respond to a claim.

What happens if an employee never declared business use on their personal policy? Their insurer may deny the claim, in whole or in part, depending on the specific policy wording and jurisdiction. If that happens, the employer's non-owned liability coverage — if it exists — stops being an excess backstop and becomes the primary responder for third-party liability, a larger and faster exposure for the company than the declared-use scenario.

What costs are never covered by any insurance policy in this picture? Regulatory fines, criminal negligence penalties, and tax or payroll penalties are uninsurable everywhere, and post-claim premium escalation isn't a coverage question at all. These sit outside the entire insurance picture regardless of which policies are in place.