ACORD 130 Pitfalls: Where Submissions Go Wrong Before They Reach a Carrier

The ACORD 130 is the workers' compensation application that nearly every submission in the country is built on. Brokers fill it out, PEOs read it, carriers underwrite from it, and everyone has seen enough of them to stop reading carefully. That is the problem. The places where the form is incomplete or inconsistent are the places where a carrier underwriter either sends it back or quietly prices in the uncertainty.

This post walks through the form section by section. The descriptions below follow the ACORD 130 edition in common circulation, which runs to roughly a dozen sections and twenty-four yes-or-no general information questions. Editions vary; check the form in front of you.

Applicant and policy information: the entity has to match everything else

The first section asks for the applicant's legal name and any DBA, mailing address, entity type, FEIN, years in business, NAICS or SIC code, and contact details.

The pitfall is mismatch. The name on the ACORD is "ABC Landscape Inc," the loss runs say "ABC Landscaping and Maintenance," the dec page says "ABC Landscape Inc dba Green Horizon," and the census came from a payroll export under the owner's name. Each of those might be the same entity, or the loss runs might belong to a predecessor that was dissolved and reformed, which matters enormously for experience rating. An underwriter who cannot reconcile the entities will either ask, which costs days, or assume the worst.

Years in business is the other quiet problem. A corporation two years old whose loss runs go back five is either a reorganized predecessor or a mistake, and either way it is a question. For PEOs, the FEIN is what payroll will be keyed to, and a wrong FEIN propagates into everything downstream.

The policy information section asks for the proposed effective and expiration dates, submission status, billing preferences, audit frequency, and any deductible or retrospective plan. The coverage section asks for the Part One states, Part Two employer's liability limits, Part Three other-states coverage, and additional coverages like USL&H or voluntary compensation.

The common omission is Part Three. A business with employees who travel or work in a state other than the one listed, which the general questions ask about separately, needs other-states coverage, and an application that lists one state in Part One and nothing in Part Three while answering "yes" to out-of-state travel is internally inconsistent. Employer's liability limits are frequently left at the form's defaults when the applicant's contracts require higher limits, which surfaces at certificate time rather than application time.

Locations and individuals: where payroll actually lives

The locations section asks for every location with address, county, and state. The individuals section asks for owners, partners, officers, and relatives, with their ownership percentage, duties, include-or-exclude status, class code, and payroll.

Missing locations are the most common omission on the entire form. A business with a yard and an office lists the office. The rating section that follows is organized by location, so a missing location means missing payroll, and missing payroll means a quote that will be corrected at audit. Carriers know this and price it in.

The individuals section fails in the other direction: it is filled out, but the include-or-exclude elections do not agree with the payroll in the rating section. An officer excluded on the ACORD whose salary sits in the class code payroll is an error that affects premium directly.

Rating information: class, payroll, and location, all three

The rating section is a worksheet by state and location: class code and description, number of full-time and part-time employees, estimated annual payroll, and the rating factors that apply, including the experience modification.

Three things go wrong routinely. Payroll is copied from last year's audit without adjustment for growth. Class codes are copied from the expiring policy without anyone asking whether operations changed. And the experience mod field is either blank, or filled in from memory, or filled in with the mod from two years ago.

The mod field deserves special attention. The carrier will verify it against the bureau, and a mismatch between the ACORD and the worksheet is a credibility problem for the whole submission. If the bureau has not yet published the mod for the proposed effective date, say so rather than guessing.

For a PEO, this section is also where the census has to agree with the application. If the census shows 85 employees and the rating section shows 60, something is wrong, and the carrier will find it.

Prior carrier information and loss history: the five-year table

The form asks for five years of prior carrier history: year, carrier and policy number, annual premium, mod, number of claims, amount paid, and reserves. Loss runs are attached separately.

This is the section that most often arrives half-empty, and it is the section carriers care about most. Two years filled in out of five is a question about the other three. A carrier listed for a year with no corresponding loss run is a question. Claim counts and paid amounts that do not match the attached loss runs, which happens when the table was filled from an older run or from memory, are a question with an uncomfortable answer.

The right discipline is to build this table from the loss runs rather than before them. Every year gets a carrier, every carrier gets a run, and the figures on the table are the figures on the run at its valuation date. Where there is a gap, say why: self-insured, no employees, prior entity. An unexplained gap is read as a hidden year.

Nature of business, the general questions, and signatures

The nature of business section is a narrative description of operations, products, duties, and subcontracting. The general information section is twenty-four yes-or-no questions covering, among other things, aircraft and watercraft, hazardous materials, work underground or at height, work over water, subcontractors and whether certificates are obtained, a written safety program, group transportation, employee age ranges, seasonal and volunteer labor, out-of-state travel, post-offer physicals, prior declinations or cancellations, employee leasing, work performed at home, tax liens or bankruptcies, and unpaid workers' comp premium.

The pitfalls here are two kinds. The first is the reflexive "no." An applicant answering twenty-four questions in a row tends to answer no to all of them, and the "no" to "is a written safety program in operation" or "does the applicant lease employees to or from other employers" is sometimes untrue. The leasing question in particular matters for PEO submissions, since a client joining a PEO is by definition entering a leasing or co-employment arrangement, and the answer and the remarks should reflect that.

The second is the "yes" with no explanation. Every "yes" is supposed to be explained in the remarks section, and an unexplained "yes" to the hazardous materials or prior-cancellation question is a submission that will come back.

The nature of business description has its own failure mode: it is one word. "Landscaping." A carrier underwriter wants to know whether that means mowing, irrigation, tree work, or hardscape with heavy equipment, because those are different class codes and hazards. When the description and the class codes disagree, the class codes are usually wrong.

The form carries signature lines for the applicant and the producer, with dates, and a fraud warning with state-specific language. For a quote, a signed application is often not required; for binding, it is.

The pitfalls are mundane: an application dated after the proposed effective date, the producer's signature on the applicant's line, a signed version that was later edited. None are fatal at quoting, but each becomes a problem the day a claim is disputed and the carrier pulls the file.

What a carrier does with an incomplete application

An incomplete or inconsistent ACORD 130 does not usually get declined outright. It gets one of three treatments, and none of them are good for the broker or the PEO.

It gets sent back with questions, which costs a week. It gets quoted with conservative assumptions, which means a higher rate or a larger deposit than a complete application would have earned. Or it gets quoted as submitted, and the discrepancies surface at audit as an additional premium bill and an unhappy client a year after the sale.

For a PEO the mechanism is the same with one difference: the PEO is presenting the client to the carrier that underwrites its entire book, and an inconsistent application makes the PEO look careless to the one party it cannot afford to look careless to.

Most of the pitfalls above are inconsistencies between documents: the ACORD against the loss runs, the census, the dec page, and itself. A human reviewer catches these by reading all four side by side, which is slow and happens less often than anyone admits.

InboxIQ in HALO IQ parses the ACORD 130 along with the loss runs, census, and dec page that arrive with it, and because the data from each lands in structured fields on the same deal, the inconsistencies become visible rather than buried. A payroll total on the application that does not match the census, a prior carrier on the five-year table with no loss run attached, a mod on the rating section that disagrees with the worksheet: these are the things a submission review should surface first, and the point of parsing the application rather than filing it is to surface them before a carrier does.