Skip to content
SortSpoke Logo

SortSpoke for ACORD Forms

Transform ACORD Forms Processing with Human-Guided AI

Extract data from ACORD forms — ACORD 125, 126, 130, 140 and more — into structured, source-traceable fields your underwriters verify before anything reaches your systems.

  • Fast and accurate document intake
  • AI-powered data extraction and enrichment
  • Simple, powerful, and transparent AI
INSURED NameACME Holdings, Corp. FEIN82-3461125 POLICY Policy #PC-208411-A Effective2026-06-01 Term12 months COVERAGE Limit$2,000,000 Premium$42,118 Deductible$5,000 99% HIGH 85% MEDIUM 62% LOW

Parser or Filler

ACORD form parser and filler: what SortSpoke does, and what it doesn't

An ACORD form is a standardised insurance form published by ACORD, the industry's global standards body. Carriers, MGAs, and brokers use them so the same submission data is captured the same way everywhere — the ACORD 125 for the commercial applicant, the ACORD 126 for general liability, the ACORD 140 for property.

The commercial set carries one more alongside those three: ACORD 130 — Workers compensation application — class codes, payroll, experience modifier.

ACORD stands for the Association for Cooperative Operations Research and Development. Standardising the form is not the same as standardising the submission: brokers fill the same form differently, carriers modify it, revisions accumulate, and much of it arrives scanned or photographed. That gap between a standard form and non-standard data is the problem this page is about.

"Parser and filler" gets used for two different jobs.

Two Different Jobs

Parsing and filling are not the same job

SortSpoke does one of them, and it is worth being exact about which — because picking the wrong tool for the other one wastes a quarter.

Parsing: reading a filled ACORD form

  • This is SortSpoke Point it at a completed ACORD 125, 126, 130, 140 or any carrier-specific variation of them, and it returns structured fields — applicant, FEIN, mailing address, nature of business, premises, prior carrier, limits, classification codes — each one traceable back to the spot on the page it came from.
  • Handles scanned, photographed, and digitally filled forms Including the marked-up versions brokers actually send.
  • Reads carrier-modified and older revisions of the same form Without a new model per variant.
  • Your underwriters review flagged fields Nothing lands in a system of record unverified.

Filling: putting the data somewhere

  • SortSpoke fills your systems, not PDFs Parsed fields go out through the API into your policy admin, rating, or underwriting workbench, so nobody re-keys a submission that has already been read once.
  • Structured output via API into any downstream system Delivered in the shape the receiving system expects.
  • Field mapping you can adjust without an IT ticket Underwriting operations owns the mapping, not a release train.
  • Full traceability from ACORD form to system of record Every delivered value can be traced back to the page it came from, for audit.
  • A PDF tool that types text into blank ACORD forms is a different product category That is not what this is.

How to eliminate manual ACORD form data entry

  1. 1

    Define the target fields first, not the forms

    Start from the fields your rating or policy system requires. Teams that start from the form end up extracting hundreds of fields nobody consumes.

  2. 2

    Map to the forms brokers actually submit

    A commercial submission is usually an ACORD 125 with a 126 for liability and a 140 for property, and the same field appears in different places across them. Map once per field, across the set.

  3. 3

    Keep a reviewer on the extracted values

    Every extracted value should be traceable to the place it came from in the source PDF, so the reviewer verifies rather than re-reads. This is the step that decides whether downstream teams trust the data.

  4. 4

    Deliver into the system of record automatically

    The saving only materializes if the verified record lands in the policy or underwriting system without a second keying step.

Eliminating manual ACORD data entry takes four steps: define the fields your systems actually need, map them to the ACORD forms brokers really send, route the extracted values through a reviewer who checks each one against the source document, and push the verified record into the policy or underwriting system through an API. SortSpoke covers all four in one project.

Automated ACORD form processing scales with program count, not just document count: a larger MGA runs several programs, each with its own required fields and its own carrier reporting format, so the mapping is per program rather than one-size-fits-all. See submission intake for MGAs for how that plays out across a book.

Where do fillable ACORD forms come from?

SortSpoke's form guides carry blank fillable copies of the most common commercial forms, each with its edition date: the ACORD 125, ACORD 126 and ACORD 140. To confirm the edition your carrier accepts, use one of three sources:

  • ACORD directly — via acord.org, under ACORD's own membership and forms programs.
  • Your agency or policy management system — most AMS and policy admin platforms ship licensed ACORD forms as a built-in feature.
  • The carrier or MGA you are submitting to — they routinely supply the exact revision they want back.

The bottleneck is rarely the blank form. Underwriting teams do not lose their week finding an ACORD 125 — they lose it turning hundreds of completed ones, in a dozen formats, into data they can price against. That is the job on this page.

Sample commercial insurance application with synthetic data — not an ACORD form — showing the fields SortSpoke extracts
Synthetic sample. Fictional carrier, insured, and amounts — this is not an ACORD form, it is our own layout carrying the same field categories. See SortSpoke extract a form like this

Certificates

Proof of coverage is not a submission form

An ACORD 25 is the standard Certificate of Liability Insurance form: one page summarising the liability coverage a business already has, issued by the insured's agent or broker as evidence of that coverage, as of the date the certificate was issued, for a third party such as a client, a landlord or a general contractor.

That makes it a different document from the application forms above — a certificate arrives from a vendor or subcontractor and gets checked against a requirement, while an ACORD 125, 126 or 140 arrives from a broker and gets underwritten. To see one read field by field, the free certificate extractor returns every field on a certificate you already have. For a section-by-section walk through the document, read what an ACORD certificate of insurance does and does not prove.

The commercial ACORD form family

A commercial submission is usually an ACORD 125 with a 126 for liability and a 140 for property, and the same field can appear in different places across them — see how the ACORD 125, 126 and 140 differ. The ACORD 25 is the outlier in this set: it reports coverage already bound rather than requesting new coverage.

FormWhat it isWhen you see itWho fills itWhat SortSpoke does
ACORD 25Certificate of Liability Insurance — a one-page summary of the coverage already in force.When a vendor, subcontractor or tenant has to prove coverage to whoever required it.The insured's agent or broker, who issues it to the certificate holder.The free extractor on this site returns every field on a certificate you upload.
ACORD 125Commercial insurance application — applicant, FEIN, locations, nature of business, prior carriers.At the front of almost every commercial submission.The agent or broker, from information the applicant provides; the applicant signs it.Reads completed applications and returns each field with a confidence score and a link back to where it sat on the page.
ACORD 126Commercial general liability section — exposures, limits, classification codes.Attached to an ACORD 125 whenever general liability is requested.The agent or broker, alongside the application.Extracts limits, classification codes and exposures for a reviewer to check before they reach rating.
ACORD 140Property section — building values, construction, protection, occupancy.Attached to an ACORD 125 whenever property coverage is requested.The agent or broker, alongside the application.Extracts building values, construction and protection details location by location.

ACORD Forms Questions

An ACORD form is a standardised insurance form published by ACORD, the industry’s global standards body, so that submission data is captured the same way across carriers, MGAs, and brokers. The most common commercial ones are the ACORD 125 (applicant), ACORD 126 (general liability), ACORD 140 (property), and ACORD 130 (workers compensation).

From ACORD directly, from your agency or policy management system, or from the carrier or MGA you are submitting to. SortSpoke’s ACORD 125, ACORD 126 and ACORD 140 guides also include a blank fillable PDF and a filled sample, with the edition date shown — ask the carrier which edition it accepts.

SortSpoke processes the commercial ACORD forms covered on this page — the ACORD 25, 125, 126, 130 and 140 — along with other standard ACORD forms. The system also handles the custom versions and variations of these forms that carriers or agencies use, adapting to format differences.

No — SortSpoke can run straight through on high-confidence fields if you configure it that way. However, we always recommend keeping a human in the loop for critical underwriting data to ensure maximum accuracy and compliance, especially for complex submissions or high-value policies.

Unlike black-box AI or traditional OCR, SortSpoke puts underwriters in control of the extraction process. AI handles the initial data extraction from ACORD forms, but underwriters validate results and provide feedback that improves the system in real-time. This approach delivers speed without giving up verifiability: every field is checkable against the source form, and accuracy is governed by thresholds you set rather than promised by us.

Yes, we provide structured data outputs via API that can be consumed and ingested into any downstream system, eliminating manual data re-entry and ensuring consistency across your tech stack.

Most customers are up and running with SortSpoke's ACORD forms processing within 2-4 weeks. Unlike traditional solutions that require extensive setup and configuration, SortSpoke works with ACORD forms out of the box and learns from your team's feedback to continuously improve accuracy.

Go Deeper

More ACORD Resources

See How SortSpoke Turns ACORD Forms Into Verified Data

After submitting, you'll choose your preferred demo time — no pressure, pick a slot that fits your schedule.

Get a Demo