Extract ACORD forms to structured JSON
ACORD forms pack dozens of fields into dense checkbox grids and multi-section layouts across standardized applications, certificates, and binders. Every revision shifts field positions. Sensible converts any ACORD form into consistent JSON for submission processing and compliance tracking.
Why ACORD forms break standard OCR
Checkboxes, bundled applications, and legacy versions challenge general-purpose parsers.
ACORD forms contain hundreds of checkboxes for coverage options. Sensible validates each box state with deterministic rules.
Submissions often bundle ACORD 125, 126, 130, and 140 in one PDF. Sensible splits and extracts each form individually.
ACORD revises layouts every few years, shifting field positions. Sensible detects the revision and applies the correct field map.
Fields we extract
Extract any data you need from ACORD forms into your desired output schema
Named insured, mailing address, contact name, phone, email, FEIN, SIC code, business description, years in business
Policy type, effective/expiration dates, limits (each occurrence, general aggregate, products), deductibles, retroactive date, SIR
Additional insureds, certificate holders, waiver of subrogation, blanket additional insured, prior carrier, loss history
Property Section. Building, location, and coverage detail for commercial property.
Insurance Binder. Temporary proof of coverage before the policy is issued.
Commercial General Liability Section. Coverage details for CGL policies.
Workers Compensation Application. Employee classification and experience modification data.
Commercial Insurance Application. General information section for commercial submissions.
Certificate of Liability Insurance. The most common ACORD form used to verify insurance coverage.
Supported ACORD forms
Sensible processes all major ACORD form types used in commercial and personal lines, many available in Sensible's template library. Any ACORD version can be configured in hours.
ACORD 25, 27, 28, 75, 125, 126, 130, 131, 140, and specialty forms
Certificates of insurance, commercial applications, workers comp applications, property sections, binders, cancellation notices
Common Questions
Specific details about our ACORD extraction engine.
Sensible supports ACORD 25, 27, 28, 75, 125, 126, 130, 131, 140, and others. Pre-built templates are available in the configuration library.
Yes. Commercial submissions often combine ACORD 125, 126, 130, and 140 in one PDF. Sensible identifies each form within the bundle and extracts them individually.
Sensible handles multiple ACORD revision years including 2010, 2014, and 2016 versions. The extraction engine detects the form version and applies the correct field mapping.
Sensible accurately detects checked, unchecked, and X-marked boxes across the form. Fields like Additional Insured, Waiver of Subrogation, and coverage indicators are returned as boolean values.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.