What is an ACORD 126 used for?
It is the Commercial General Liability section of the ACORD application set. Agencies submit it with the ACORD 125 (the commercial application core) so carriers can rate GL coverage: limits, classifications, exposures, deductibles, and the underwriting questions specific to liability.
Does ACORD 126 automation require a carrier API?
No. Extraction reads the form itself, and delivery uses whatever the carrier offers — an API where one exists, deterministic portal automation where it doesn’t. No carrier approval is needed to stop retyping your own application data.
How does automated GL class code mapping work across carriers?
The pipeline reads the class codes and operation descriptions from your 126, then maps them per carrier — because carriers genuinely differ in their code systems. Mapping rules are explicit and reviewable, so a wrong-code surprise becomes a mapping fix, not a recurring mystery.
Can it handle multi-location GL schedules?
Yes. Per-location classifications, varying limits by location, and location-specific exposures are extracted as structured schedule data and placed into each portal’s location screens — the exact part humans hate most.
What about scanned or faxed 126s?
Scans are the normal case, not the exception. OCR runs with per-field confidence scores; anything below threshold routes to quick human review instead of flowing into a carrier submission wrong.