Commercial auto (the Business Auto Policy) is a high-severity commercial line. Here is how the line is structured, how fleet schedules and MVRs are managed, and what a BAP policy administration platform must support.
Commercial auto insurance — the Business Auto Policy (BAP) — covers vehicles owned, leased, hired, or non-owned by a commercial insured. It is a high-severity line with fleet scheduling, driver MVR pulls, and state-by-state financial-responsibility filings that differ from personal auto.
This page is a reference for commercial auto carriers, MGAs, TPAs, and program administrators evaluating a policy administration platform for their BAP book.
Personal auto policies exclude most commercial use. Vehicles titled to a business, vehicles used to deliver goods or people for a fee, and vehicles shared among employees almost always belong on a BAP.
For the platform, that means commercial auto product configuration has to enforce business-entity policyholders, named-driver schedules, cargo and radius-of-operation factors, and commercial-specific rating codes — none of which sit cleanly on a personal auto product.
Standard BAP includes liability (BI / PD), physical damage (collision / comprehensive on scheduled units), UM/UIM, medical payments, and optional coverages for trailer interchange, cargo, and rental reimbursement.
Commercial-specific endorsements include Hired Auto (short-term rented or leased vehicles), Non-Owned Auto (employee personal vehicles used for business errands), and HNOA as a combined endorsement. The platform's forms library has to version and state-file each.
BAP policies schedule each vehicle (VIN, garaging, primary use, radius, cargo) and each listed driver. At quote and renewal, the platform pulls motor vehicle records on listed drivers to surcharge or decline based on violations and at-fault losses.
Mercury's configurable underwriting workflow, API-first architecture, and field-level validation handle scheduled units at scale, MVR service integration, and driver-level surcharging inside the rating engine.
Commercial auto telematics is more widely adopted than personal telematics because the fleet owner already manages the vehicles and pays the premium. Carriers and MGAs use telematics feeds to adjust rating, manage loss control, and reduce severity on the fleet.
Mercury supports driver-behavior telematics ingest and factor application inside the rating engine, letting a commercial auto program ship as a product configuration rather than a custom build.
Commercial auto branches into rideshare, last-mile delivery, and motor-carrier / long-haul trucking, each with its own rating plan and regulatory filings (federal financial-responsibility filings for motor carriers, state-specific delivery endorsements, rideshare coverage gaps).
Program administrators and MGAs use Mercury's configurable rating, forms library, and multi-carrier MGA quoting to launch specialty commercial auto programs quickly rather than carrying custom code per program.
Does Mercury handle fleet scheduling at scale?
Yes. Mercury's configurable underwriting workflow and API-first architecture handle large vehicle schedules, scheduled driver lists, and MVR service integration for BAP policies. Rating and validation operate at the scheduled-unit level.
Can Mercury support multi-carrier commercial auto MGA programs?
Yes. Mercury supports multi-carrier MGA quoting for commercial auto, where one agent workflow fronts multiple carriers' paper, each with its own filed rates, rules, and forms.
Does Mercury ingest commercial telematics?
Mercury supports driver-behavior telematics ingest and factor application inside the rating engine, suitable for commercial auto and fleet programs as well as personal UBI.