ACORD form data extraction uses AI to read completed ACORD 25, 28, and 125 forms and return their contents as structured JSON, CSV, or Excel. It replaces manual re-keying of policy numbers, limits, dates, checkboxes, and certificate holder details. The right approach differs by form: a dense limits grid on the ACORD 25, lender and loss-payee context on the ACORD 28, and multi-row tables on the ACORD 125. Tools like PerfectParser handle the reading side so downstream systems receive verified data.
ACORD forms are standardized, but getting their data into your systems usually isn’t. A certificate of insurance arrives as a scanned PDF. Someone opens it beside the agency management system (AMS) and retypes the limits, policy numbers, and holder details one field at a time.
This guide explains how ACORD form data extraction works with AI. It covers what to expect from the three most common forms (ACORD 25, 28, and 125), how to validate the output, and how to test a tool on your own documents.
What Is ACORD Form Data Extraction?
ACORD form data extraction is the process of reading a completed ACORD form and returning its contents as structured fields instead of a flat image. A purpose-built ACORD parser handles four key operations:
- Identifies the form type: Distinguishes between ACORD 25 certificates of liability, ACORD 28 property evidence, ACORD 125 applications, and attached endorsements or schedules.
- Locates each field and section: Maps visual bounding boxes to semantic field definitions across producers, insurers, coverages, limits, and certificate holders.
- Reads values and checkbox states: Classifies binary tick marks (
OCCURvs.CLAIMS-MADE,ADDL INSD,SUBR WVD) while parsing handwritten or printed alphanumeric values. - Outputs structured data: Emits clean JSON, CSV, or Excel ready for ingestion into AMS360, Applied Epic, Salesforce, or underwriting pipelines.
Why Manual ACORD Data Entry Is a Bottleneck
If you want to reduce manual ACORD form data entry, start by seeing where the time goes. For each form, an agency specialist typically:
- Opens the PDF and identifies the form and edition.
- Re-keys the insured, policy numbers, dates, and limits into the AMS.
- Checks each box by eye (occurrence vs. claims-made, additional insured, subrogation waived).
- Copies the certificate holder or mortgagee details.
- Double-checks everything, because a transposed digit can flow into an active coverage record.
Three real costs add up quickly:
- Labor costs: Minutes per form, multiplied across hundreds or thousands of certificates every month.
- Transposition errors: A wrong digit in a policy number or limit can trigger compliance disputes or delayed loan closings.
- Intake turnaround delay: Documents sit in a queue while tenants, vendors, lenders, and brokers wait for verification. For commercial agencies, certificate processing is part of a larger intake challenge explored in our guide to commercial broker insurance data capture.
How to Extract an ACORD 25 Certificate of Insurance
The ACORD 25 (Certificate of Liability Insurance) is one of the highest-volume documents in commercial insurance. Because it is largely a dense matrix, accurate extraction depends on keeping every limit tied to its exact coverage row.
Why it's hard: The same limit label (e.g., "$1,000,000") can appear under general liability, auto, and umbrella sections. Furthermore, the ADDL INSD and SUBR WVD checkboxes sit on a narrow row separated from the policy number they modify. PerfectParser uses vision-based spatial awareness to lock every limit and checkbox to its corresponding coverage line.
ACORD 28 Data Extraction: Evidence of Commercial Property Insurance
The ACORD 28 is issued when a lender, mortgagee, or loss payee requires evidence of commercial property coverage. Unlike the liability-focused ACORD 25, the ACORD 28 is organized around the physical property location and interested parties.
Why it's hard: The same address structure appears multiple times (named insured address, physical property location, and mortgagee billing address). Contextual parsing is required to ensure loan numbers and loss-payable clauses map to the correct financing record. Because ACORD 28 forms summarize complex commercial assets, cross-referencing extracted limits with an AI insurance policy schedule parser ensures property sub-limits align with master policies.
ACORD 125 Commercial Application OCR
The ACORD 125 is the core applicant cover sheet for commercial submissions. As the front page of a multi-line insurance submission, it is the most information-dense of the three forms.
General contractors and developers who manage high-volume subcontractor applications can coordinate certificate validation directly with their construction AP automation to unblock lien waivers and payment applications.
ACORD 25 vs. 28 vs. 125 at a Glance
The Hard Parts: Checkboxes, Grids, and Scans
Checkbox State Detection
A checkbox is not text, so simple text-only OCR engines either omit it completely or misinterpret a cross as an X. An AI document parser classifies checkboxes into three distinct states: checked, unchecked, or uncertain. On an ACORD 25, correctly distinguishing OCCUR from CLAIMS-MADE or confirming whether SUBR WVD is selected prevents substantial coverage verification errors.
Dense Multi-Box Grids
Limits and deductible amounts are packed into tight cells. If vertical row boundaries shift, a $2,000,000 general aggregate can accidentally be read as the per-occurrence limit. Layout-aware vision models examine row geometry and label headers simultaneously to ensure values land in the right schema slot.
Fillable PDFs vs. Scans
Not every ACORD document requires the same processing path:
- Fillable digital PDFs: Contain digital form fields (AcroForms) that allow deterministic field-level reading.
- Scanned, faxed, or photographed PDFs: Require visual layout parsing, deskewing, and intelligent character recognition.
A production pipeline should automatically route clean digital documents through instant extraction and apply multi-modal vision models to degraded scans.
Form Editions
ACORD updates form revisions periodically (e.g., ACORD 25 edition 2016/03 vs. earlier revisions). Coordinate-based zonal OCR breaks whenever a carrier uses an alternate edition or custom margins. Vision models parse relative semantics, ensuring consistent output regardless of edition variations.
AI Solution for ACORD Form Data Entry: The Architecture
An enterprise ACORD data extraction pipeline operates across seven automated stages:
- Ingest: Files arrive via REST API, SFTP, shared inbox, or batch file upload.
- Classify: AI classifies whether the incoming PDF is an ACORD 25, ACORD 28, ACORD 125, or an attached policy schedule.
- Parse Layout: Spatial analysis detects grid headers, column separators, and checkbox clusters.
- Extract: Field values, checkboxes, and line items are mapped into a standardized JSON schema.
- Validate: Automated business rules run cross-field consistency checks (e.g., aggregate ≥ occurrence).
- Human Review: Low-confidence fields or validation discrepancies are flagged for side-by-side operator review.
- Deliver: Clean data is delivered via webhooks or API directly into AMS360, Applied Epic, or your custom database.
Sample JSON Output and API Workflow
Here is an illustrative output schema from an ACORD 25 extraction:
{
"form_type": "ACORD_25",
"edition_date": "2016/03",
"producer": {
"name": "Beacon Risk Partners",
"contact": "Jane Doe",
"phone": "555-0199"
},
"insured": {
"name": "Apex Contracting LLC",
"address": "450 Industrial Parkway, Austin, TX 78701"
},
"certificate_holder": {
"name": "Midwest Development Corp",
"address": "1200 Commerce St, Dallas, TX 75201"
},
"coverages": {
"general_liability": {
"insurer_letter": "A",
"policy_number": "GL-889102-01",
"effective_date": "2026-03-01",
"expiration_date": "2027-03-01",
"basis": "occurrence",
"additional_insured": true,
"subrogation_waived": true,
"limits": {
"each_occurrence": 1000000,
"damage_to_rented_premises": 300000,
"med_exp": 10000,
"personal_adv_injury": 1000000,
"general_aggregate": 2000000,
"products_comp_op_aggregate": 2000000
}
},
"workers_compensation": {
"insurer_letter": "B",
"policy_number": "WC-449102-09",
"effective_date": "2026-03-01",
"expiration_date": "2027-03-01",
"statutory_limits": true,
"limits": {
"el_each_accident": 1000000,
"el_disease_ea_employee": 1000000,
"el_disease_policy_limit": 1000000
}
}
}
}
Submitting an ACORD document through the PerfectParser REST API is straightforward:
import requests
url = "https://api.perfectparser.com/v1/extractions/start"
headers = {"X-API-Key": "YOUR_API_KEY"}
with open("acord25_certificate.pdf", "rb") as f:
response = requests.post(
url,
headers=headers,
files={"file": f},
data={"parser_id": "acord-forms-v1"}
)
job = response.json()
print("Job submitted:", job["job_id"])
Validation Rules That Catch Real Errors
Extraction without validation merely accelerates errors. A production-ready pipeline applies these validation rules:
ACORD 25
- Chronology: Effective date must precede expiration date.
- Limit Logic: General aggregate must be greater than or equal to the each-occurrence limit.
- Completeness: Policy number must be present for every checked coverage row.
- Holder Validation: Certificate holder name and address must match the contracting counterparty.
- Endorsement Flags: Ensure
ADDL INSDandSUBR WVDmatch contractually required endorsements. For vendor onboarding and subcontractor management, compliance teams frequently pair certificate intake with contract data extraction to verify that certificate limits satisfy underlying master services agreements (MSAs).
ACORD 28
- Location Matching: Property location address must match portfolio assets on file.
- Interest Verification: Additional interest name and loan/mortgage account number must reconcile with lending systems.
- Term Coverage: Policy dates must cover the entire financing or escrow period.
ACORD 125
- FEIN Validation: Federal Employer Identification Number must follow standard 9-digit format (
XX-XXXXXXX). - Location Completeness: Every premises row must have a street, city, state, and ZIP.
- Loss Reconciliation: Prior loss amounts must be numeric and dated.
What Extraction Does Not Do
To maintain compliance and sound risk governance, understand where automated extraction stops:
- It does not issue or alter certificates: It reads incoming documents; it does not generate binder certificates or modify coverage terms.
- It does not verify carrier solvency: It extracts the insurer name and NAIC code as printed, but does not assess A.M. Best ratings.
- It does not replace coverage verification: An ACORD certificate is legally informational and does not alter the underlying policy. Critical risks should be cross-referenced with policy declarations.
How to Measure ROI
Calculate your team's baseline manual data entry expense:
Annual Cost = Forms per Year × (Minutes per Form ÷ 60) × Loaded Hourly Rate
For example, processing 1,000 certificates a month (12,000 annually) at 15 minutes per form represents 3,000 hours. At a $35/hour loaded labor cost, that equals $105,000 annually in repetitive keying. Automating 80% to 90% of this intake frees up operational capacity for client onboarding and underwriting analysis.
Automate ACORD Form Data Extraction with AI
Extract fields, limits, checkboxes, and certificate holder details from ACORD 25, 28, and 125 forms directly into JSON, Excel, or your AMS. 20 free pages included.
Start Extracting ACORD Forms Free →
