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.

Quick links:

Certificates of insurance blog

Insurance template library

API documentation

Schedule a demo

Why ACORD forms break standard OCR

Hundreds of checkboxes, bundled multi-form submissions, and layout shifts between revision years demand more than pattern matching. Sensible combines LLM reasoning with deterministic validation to handle every ACORD variant.

Dense Checkbox Grids

ACORD forms contain hundreds of checkboxes for coverage options, additional insured indicators, and policy conditions. Deterministic rules validate each box state (checked, X-marked, or empty) so downstream systems receive clean boolean values, not guesses.

Bundled Applications

Commercial submissions routinely bundle ACORD 125, 126, 130, and 140 into one PDF. Each form gets identified, split, and extracted individually, preserving the relationship between the application and its supplemental forms.

Version Detection

ACORD revises form layouts every few years, shifting field positions and adding new sections. Version detection happens automatically. The extraction config adapts to the revision without manual intervention.

Fields we extract

Configure your output schema to capture any combination of ACORD fields.

Applicant information

Named insured, mailing address, contact name, phone, email, FEIN, SIC code, business description, years in business

Coverage details

Policy type, effective/expiration dates, limits (each occurrence, general aggregate, products), deductibles, retroactive date, SIR

Supplemental data

Additional insureds, certificate holders, waiver of subrogation, blanket additional insured, prior carrier, loss history


{ /* SenseML: ACORD form extraction */
  "fields": [
    {
      "method": {
        "id": "queryGroup",
        "queries": [
          {
            // Named insured from the applicant section
            "id": "named_insured",
            "description": "named insured, applicant name, first named insured"
          },
          {
            // Policy effective date
            "id": "effective_date",
            "description": "policy effective date, policy period from",
            "type": { "id": "date" }
          },
          {
            // General aggregate limit
            "id": "general_aggregate",
            "description": "general aggregate limit, aggregate",
            "type": { "id": "currency" }
          },
          {
            // Additional insured checkbox
            "id": "additional_insured",
            "description": "additional insured, is additional insured checked",
            "type": {
              "id": "custom",
              "pattern": "true|false|yes|no|checked|unchecked"
            }
          }
          // Additional fields for each occurrence limit, deductible, SIC code, etc.
        ]
      }
    }
  ]
}
ACORD 140

Property Section. Building, location, and coverage detail for commercial property.

ACORD 75

Insurance Binder. Temporary proof of coverage before the policy is issued.

ACORD 126

Commercial General Liability Section. Coverage details for CGL policies.

ACORD 130

Workers Compensation Application. Employee classification and experience modification data.

ACORD 125

Commercial Insurance Application. General information section for commercial submissions.

ACORD 25

Certificate of Liability Insurance. The most common ACORD form used to verify insurance coverage.

Supported ACORD forms

Pre-built configurations for major ACORD forms ship in Sensible's template library. New form numbers or custom revision years can be configured in hours, not weeks.

By form number

ACORD 25, 27, 28, 75, 125, 126, 130, 131, 140, and specialty forms

By use case

Certificates of insurance, commercial applications, workers comp applications, property sections, binders, cancellation notices

Trusted by operations and engineering teams at

Common Questions

Answers about ACORD form numbers, revision year support, and checkbox extraction.

Which ACORD form numbers does Sensible support?

Sensible supports ACORD 23, 24, 25, 27, 28, 45, 75, 101, 125, 126, 127, 130, 131, 140, 304, and 823 with pre-built templates in the configuration library. Multiple revision years are covered for most form numbers.

Can Sensible handle bundled ACORD submissions?

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.

Which ACORD form versions does Sensible support?

Sensible supports any ACORD form number and any revision year. The extraction engine detects the form version automatically and applies the correct field mapping. Custom configurations for specific form versions can be set up quickly.

How does Sensible handle checkboxes on ACORD forms?

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.

Do you support webhooks?

Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.

Does Sensible support human review?

Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.

What security certifications does Sensible have?

Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.

How long is document data retained?

Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.

Is there a free trial?

Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.

How is pricing structured?

Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.

How do I integrate with Sensible?

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.

What file formats does Sensible support?

Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.

How accurate is the extraction?

Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.

How fast is document processing?

Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.

Resources

Documentation Links

Docs: Insurance template quick startDocs: Validation and human reviewDocs: API and delivery options

Related insurance documents

Docs: Insurance template quick startDocs: Validation and human reviewDocs: API and delivery options