Insurance document automation for claims: the 8 best data extraction tools in 2026

For claims operations teams at carriers, MGAs and TPAs. Eight tools that turn claim documents into data, and what each one reads and costs. You'll also see how the data reaches Guidewire, Duck Creek or your own claims system.

An umbrella over stacked blocks beside a claim document and a file folder, with a green check above

Key takeaways

  • Insurance document automation reads claim documents such as loss notices, ACORD forms, repair estimates and CMS-1500 bills. It hands checked data to the claims system. The adjuster still makes the decisions.
  • Eight tools are worth a shortlist for claims data extraction in 2026: Docsumo, Hyperscience, ABBYY Vantage, Affinda, Indico Data, Bevaya (formerly Roots Automation), Sensible and Amazon Textract.
  • Only three name a core claims system on their own sites. Hyperscience, Indico Data and Bevaya list Guidewire and Duck Creek, while the rest, Docsumo included, hand data over through an API and webhooks.
  • Three publish prices: Bevaya from $4,000 per AI agent a month, Sensible from $449 a month (both billed annually) and Amazon Textract per page. Docsumo offers a free 14-day trial for up to 1,000 pages.
  • Pilot on your own claim files, because faxed estimates, handwritten loss notices and long medical bills are where tools differ.
On this page
  1. Where document automation sits in a claim
  2. Claims data extraction: what to pull from each document
  3. How claim documents become claim data
  4. The 8 best claims data extraction tools
  5. Claims data extraction tools compared
  6. Where the data lands: core claims systems
  7. How to choose claims data extraction software
  8. What to test in a pilot
  9. If claim files still wait for someone to key them
  10. Frequently asked questions

Insurance document automation software reads claim documents and turns them into checked data for the claims system. Claim documents include loss notices, ACORD forms, repair estimates and CMS-1500 medical bills. For claims data extraction, the tools worth a shortlist in 2026 include Docsumo, Hyperscience, ABBYY Vantage and Affinda. Indico Data, Bevaya, Sensible and Amazon Textract are on the shortlist too. All eight tools work in front of a core claims system such as Guidewire ClaimCenter or Duck Creek Claims. The core system runs the claim from intake to closure.

Vendor details below come from each vendor's own website, checked in September 2026. Links are in the sources at the end.

What are you fixing?

For claim documents keyed by hand
Docsumo (our product) reads and checks loss notices, ACORD forms, estimates and medical bills, then sends the data to your claims system.
For mixed claim packets that need sorting
Docsumo splits each emailed or scanned packet into its documents and labels each one by the types you name. It works with no training set, on the Business plan. Documents it can't classify wait as Unclassified for a person to assign. See document classification software.
For FNOL intake into Guidewire or Duck Creek
Indico Data or Bevaya, which both name connectors for those systems.
For capture on your own servers
Docsumo runs in the cloud only. Look at Hyperscience or ABBYY Vantage, which can run on-premises.
For medical bills through an API
Docsumo reads CMS-1500 and UB-04 bills and returns each field through its API and webhooks. It signs a BAA, and your reviewers check the fields it's unsure about. Sensible and Affinda also read CMS-1500 and UB-04 forms.
For intake your engineers build on AWS
Docsumo if you'd rather not build packet splitting and review screens. It splits mixed claim packets on its Business plan, and your team checks uncertain fields in Docsumo. Files go in and data comes out through its API and webhooks. To build everything yourself, use Amazon Textract, priced per page.

Where document automation sits in a claim

Claims software comes in three kinds. Core claims systems run the claim itself, from assignment to payment. Claims AI tools help handlers with decisions such as triage and coverage. Insurance document automation sits in front of both and turns what the claimant, the shop and the provider send into data. This post ranks that third kind, the tools that read claim documents, and then shows where the core systems fit.

Five-layer claims stack: first notice of loss, document intake and extraction (Docsumo), claims AI, core system, payments
Docsumo works at layer 2, turning claim documents into data. It doesn't set reserves or pay claims.

Claims data extraction: what to pull from each document

Every claim document has a handful of fields the claims system needs and one or two checks worth running before anyone opens the file. These are the ones claims teams ask for most.

DocumentFields to extractCheck before it reaches the claims system
Loss notice (ACORD 1, 2 or 3, or your FNOL form)Policy number, insured, date, time and location of loss, cause, description, estimated lossThe date of loss falls inside the policy period
Police reportReport number, date and location, parties, vehicles and plates, narrativeDate and location match the loss notice
Repair estimateShop, parts and labor lines, labor hours and rates, tax, totalThe lines add up to the total
Adjuster reportClaim number, inspection date, coverage notes, reserve recommendation, narrative sectionsClaim number and dates match the file
CMS-1500Insured's ID (box 1a), patient (box 2), diagnosis codes (box 21), service lines with CPT or HCPCS codes, units and charges (box 24), total charge (box 28)Line charges add up to the total, and the member ID matches the card
UB-04Type of bill, statement period, revenue codes, HCPCS codes, units, charges, principal diagnosisLines add up to total charges, and service dates fall inside the statement period
EOBPayer, claim number, billed, allowed and paid amounts, patient responsibility, adjustment reason codesBilled, allowed, paid and patient amounts reconcile line by line
Demand letterClaimant, attorney, amount demanded, injuries, treatment dates, response deadlineThe deadline is captured and routed to the handler

Here's a property loss notice being read, with the handwritten parts included.

Policy
FieldExtracted valueConfidence
Policy numberQHM-5561204
Line of businessHomeowners (HO-3)
Policy period2026-03-01 to 2027-03-01
A homeowners loss notice from Quillmere Mutual, policy QHM-5561204: a burst supply line on 09/14/2026, inside the policy period, with a handwritten $18,400 estimate.

The medical bills have more boxes and more ways to go wrong. Our guide to health insurance claim form extraction walks through them field by field.

How claim documents become claim data

  • Loss notices
  • Repair estimates
  • Medical bills
  • Police reports
Insurance document automation
  1. 01Classify and split
  2. 02Extract
  3. 03Validate
  4. 04Route exceptions
Claims system
How claim documents become claim data

Take an auto claim that arrives as one email. A single PDF holds an ACORD 2 loss notice, a police report, two body-shop estimates and a set of photos. The first job is splitting that PDF into its documents and labeling each one, because an estimate and a police report need different fields. We compare 14 document classification tools for this step.

Then each document is read. The estimate lines are added up against their totals, and the date on the police report is compared with the date of loss. The file reaches the claims system as data. A person sees only what failed, such as a total that doesn't add up or two dates that disagree.

That hand-off is where most teams lose time today, so it's the part the tools below are built for. Our walkthrough of claims automation covers the rest of the claim, and there's more on OCR for claims intake.

The 8 best claims data extraction tools

Docsumo is our product, so we've put it first and said plainly what it doesn't do. The others are grouped by what they're built for.

Document automation platforms

1. Docsumo

Document automationOur product
Docsumo is an intelligent document processing (IDP) platform. For insurance claims, it splits and classifies incoming packets and reads loss notices, ACORD forms, estimates and medical bills. It sends only low-confidence fields to a reviewer. It isn't a claims system, so it doesn't set reserves or pay claims.
Reads
Any claim document type, handwritten text included; covers 250+ document types
Claims systems
API and webhooks into your claims system or data warehouse
Deployment
Cloud only; SOC 2 Type 2, ISO 27001, HIPAA and GDPR, with SSO and role-based access (security)
Pricing
A free 14-day trial for up to 1,000 pages; Business and Enterprise plans are quoted. Classification and splitting start on Business; cross-document validation and case management are on Enterprise
Best fitMid-sized and enterprise carriers and MGAs automating intake in front of the claims system they already run
  • 99%field-level accuracy across 250+ document types
  • 95%+of documents processed straight through, without manual review
  • 99%accuracy on insurance compliance documents at Arbor
  • 3,000+hours saved a month at Arbor

2. Hyperscience

Document automation
Hyperscience's Hypercell platform reads claim forms, medical records, damage and inspection reports and invoices, and sends exceptions to people for review. Its claims page describes email intake, classification and extraction. It also covers case collation and business-rule validation.
Reads
Claim forms, medical records, damage and inspection reports, invoices; pre-built models for ACORD forms, EOBs and health insurance cards; handwriting, faxes and phone photos
Claims systems
Guidewire, Duck Creek and Vertafore AMS360, as named on its insurance pages; API-first
Deployment
SaaS, on-premises, private tenant or air-gapped; FedRAMP High authorized
Pricing
Not published; volume-based
Watch for
The insurance customers it names are large, such as QBE and Canada Life, so ask how it prices a smaller rollout
Best fitInsurers and government programs that need on-premises, air-gapped or FedRAMP High deployment. See Docsumo vs Hyperscience.

3. ABBYY Vantage

Document automation
ABBYY's claims page leads with Vantage, its IDP platform, for first notice of loss and claim assessment. Pre-trained skills in its Marketplace include the ACORD 2 automobile loss notice and automobile accident reports, and ABBYY still sells FlexiCapture alongside it.
Reads
FNOL documents, ACORD 2 auto loss notices, auto accident reports and vehicle titles as pre-trained skills; handwriting, barcodes and checkboxes
Claims systems
None named; its FAQ says it connects to claims management, RPA and BPM tools; REST API
Deployment
ABBYY Cloud (US, Europe or Australia), or on-premises and private cloud on Azure
Pricing
Not published
Watch for
The claims page doesn't describe how people review extracted fields
Best fitInsurers that need on-premises capture or already run ABBYY. See Docsumo vs ABBYY FlexiCapture.

4. Affinda

Document automation
Affinda sells a general document AI platform with a claims use case. A natural-language agent sets up extraction, and a review screen comes built in.
Reads
Claim forms, ACORD forms, invoices, receipts, medical reports, repair estimates, loss adjuster reports, and CMS-1500 and UB-04 health claims
Claims systems
None named; REST API, webhooks and client libraries, plus Salesforce and Dynamics 365
Deployment
Multi-tenant or single-tenant SaaS, your own VPC, or self-hosted; on-premises is a paid add-on
Pricing
Per-page credits with no dollar prices published; a 2-week trial with 200 credits
Watch for
HIPAA support is a paid add-on, and exceptions route on failed validation rules rather than on confidence scores
Best fitClaims teams that want one tool for many document types, health claims included

Insurance intake and AI agents

5. Indico Data

Insurance intake
Indico Data calls itself an intake and orchestration platform for insurance operations. It reads first notice of loss packets as they arrive and passes the data on with a confidence score and an audit trail.
Reads
FNOL and loss notices from emails, PDFs, ACORD forms, photos and call summaries. Its older claims page adds loss runs, statements of values, spreadsheets and handwriting
Claims systems
Guidewire, Duck Creek and Salesforce, plus Snowflake, SQL and RPA tools; REST and GraphQL APIs
Deployment
Single-tenant on AWS, or hosted by the customer
Pricing
Not published; custom, based on submissions a year and users
Watch for
Medical bills and repair estimates aren't named on its pages, and its focus is commercial and specialty insurance
Best fitCommercial and specialty carriers and MGAs that want FNOL intake wired into Guidewire or Duck Creek

6. Bevaya (formerly Roots Automation)

Insurance AI agents
Roots Automation renamed itself Bevaya in May 2026. It sells AI agents for insurance work, built on its own InsurGPT model, including agents for FNOL setup, medical bills, legal demands and claim indexing.
Reads
ACORD, FROI, CMS-1500 and UB-04 forms, demand letters, photos and handwritten reports; medical bills with CPT, ICD-10 and HCPCS codes, and EOBs
Claims systems
Guidewire ClaimCenter (a Guidewire-validated indexing accelerator), InsuranceSuite, Duck Creek and Salesforce; HTTP API
Deployment
SaaS only, hosted mainly on Azure in US data centers
Pricing
From $4,000 per AI agent a month, billed annually, with usage counted in credits (setting up one FNOL uses 60)
Watch for
Each claims task, such as FNOL, medical bills or legal demands, is its own agent and is priced per agent
Best fitCarriers, TPAs and MGAs on Guidewire that want claims tasks handed to agents

Developer APIs

7. Sensible

Developer API
Sensible is a developer-first extraction API. Engineers configure extraction in SenseML, its open configuration language, and get validated JSON with the source location of every field.
Reads
Pre-built configurations for CMS-1500 and UB-04. ACORD claims forms, state first reports of injury, workers' comp and auto injury forms configured on request; EOBs and loss runs
Claims systems
None named; REST API, Python and Node SDKs, webhooks and Zapier
Deployment
SaaS on AWS, with custom data residency on Enterprise
Pricing
Growth $449 and Scale $1,349 a month, billed annually; Enterprise quoted; 14-day trial
Watch for
Only the CMS-1500 and UB-04 configurations are pre-built, and the HIPAA BAA comes with the Enterprise plan
Best fitEngineering teams building claims intake that want a review queue included

8. Amazon Textract

Developer API
AWS's API for text, handwriting, forms, tables and signatures in scanned documents. Your engineers build the claims workflow around it.
Reads
Text, forms and tables; invoices and receipts through AnalyzeExpense; handwriting in English only
Claims systems
None; you build the hand-off
Deployment
AWS cloud
Pricing
$1.50 per 1,000 pages for text and $50 per 1,000 for forms (published, US West); a 3-month free tier for new AWS customers
Watch for
Classification of mixed packets, review screens and routing are yours to build, and AWS's A2I human review service is closed to new customers
Best fitEngineering teams building their own intake pipeline on AWS. See Docsumo vs Amazon Textract.

Claims data extraction tools compared

Facts as published on each vendor's site in September 2026.

ToolClaim documentsClaims systemsDeploymentPricing
Document automation platforms4 tools
DocsumoOur productCarriers and MGAs, mid-sized to enterpriseLoss noticesACORD formsEstimatesMedical billsHandwritingAPI, webhooksCloudFree trial; quoted plans
HyperscienceOn-premises or FedRAMP HighClaim formsACORD formsEOBsMedical recordsHandwritingGuidewire, Duck Creek, AMS360SaaS, on-premises, air-gappedNot published
ABBYY VantageInsurers already on ABBYYFNOLACORD 2Accident reportsHandwritingNot namedCloud, on-premisesNot published
AffindaMany document types in one toolClaim formsACORD formsEstimatesCMS-1500UB-04Not named; APISaaS, VPC, self-hostedPer-page credits; trial
Insurance intake and AI agents2 tools
Indico DataCommercial and specialty carriersFNOLACORD formsEmailsPhotosGuidewire, Duck Creek, SalesforceSingle-tenant AWS, self-hostedNot published
BevayaCarriers and TPAs on GuidewireACORDFROICMS-1500UB-04Demand lettersGuidewire ClaimCenter, Duck Creek, SalesforceSaaSFrom $4,000 per agent a month
Developer APIs2 tools
SensibleEngineering teamsCMS-1500UB-04EOBsLoss runsNot named; APISaaS on AWSFrom $449 a month
Amazon TextractEngineering teams on AWSTextFormsTablesInvoicesBuild your ownAWSPer page

Where the data lands: core claims systems

Guidewire ClaimCenter and Duck Creek Claims don't read claim documents. They're where the extracted data ends up, and they're what most searches for claims automation software turn up, so here's how they fit.

Guidewire ClaimCenter

Core claims system
Guidewire's claims system for P&C insurers covers the claim from intake to closure. AI guidance for handlers comes from ProNavigator, which Guidewire agreed to buy in October 2025.
Takes in
Digital intake tied to policy search; APIs and Guidewire Marketplace integrations
Deployment
Guidewire Cloud
Pricing
Not published
Best fitP&C carriers replacing or modernizing their core claims system

Duck Creek Claims

Core claims system
Duck Creek's cloud-native claims system connects natively to Duck Creek Policy and Billing. Vista Equity Partners has owned Duck Creek since 2023.
Takes in
2,600+ APIs across the platform
Deployment
SaaS (Duck Creek OnDemand)
Pricing
Not published
Best fitP&C carriers that want a SaaS core system configured by the business

Hyperscience, Indico Data and Bevaya name connectors for these systems on their own sites. Docsumo and the other tools send JSON through an API or webhooks, and your team or integrator maps it to the claims system's intake. Ask each vendor which fields it maps without custom work and who maintains the mapping when the claims system changes.

How to choose claims data extraction software

Start with the claim documents you receive most, by line of business, and rule out any tool whose own site doesn't name them. A workers' comp team living on FROIs and medical bills needs a different shortlist from a property team drowning in contractor estimates.

Then decide who owns the integration. Named Guidewire or Duck Creek connectors save integration work if you run those systems, which is the case for Hyperscience, Indico Data and Bevaya. An API-first tool asks more of your engineers but fits any claims system, older ones included. Medical data adds one more question, which is who stores it, where, and whether the vendor signs a BAA before you send a single bill.

Our take. Judge claims intake by the whole file, not by how well a tool reads one page. A perfectly read loss notice doesn't help much if the estimate, the police report and the policy disagree. So the checks between documents decide how many files reach an adjuster clean. On Docsumo those cross-document checks are part of the Enterprise plan.

What to test in a pilot

Clean samples make every tool look good. Pilot on a couple of hundred real claim files, score classification and extraction separately, and include the documents your team struggles with.

  • Itemized medical billsCMS-1500 and UB-04 forms from many providers, with codes and modifiers on every line.
  • Faxed repair estimatesDegraded images where every line item and total still has to be read right.
  • Adjuster reportsA structured header over narrative sections that hold much of the detail.
  • Explanations of benefitsPayer-specific layouts, with remark codes for each adjustment.
  • Edge casesDuplicate submissions, missing fields and totals that don't match their lines.
  • The review queueWhat a reviewer sees, and whether corrections improve the model.

If claim files still wait for someone to key them

Shortlist by the job. For FNOL intake wired into Guidewire or Duck Creek, look at Indico Data or Bevaya. For capture on your own servers, Hyperscience or ABBYY Vantage. For CMS-1500 and UB-04 bills through an API, Sensible, and for many claim document types in one general tool, Affinda. For a pipeline your engineers own on AWS, Amazon Textract.

If you want claim packets read and checked in front of the claims system you already run, that's where Docsumo fits. Your own team clears the exceptions. The same approach reads underwriting submissions too, from ACORD 125 applications to loss runs.

Book a demo and bring a few of your own claim files, or start a free trial.

Frequently asked questions

What software do insurance companies use to process claims?

Most use three kinds together. A core claims system such as Guidewire ClaimCenter or Duck Creek Claims runs the claim. Insurance document automation such as Docsumo, Hyperscience or Indico Data turns claim documents into data. Claims AI helps with decisions such as triage and coverage. The document layer feeds the other two.

How do you automate insurance claims processing?

Start where claims wait, which for most teams is intake. Documents arrive by email or portal, get classified and split, and have their fields extracted and checked. Only the exceptions reach a person before the data goes to the claims system. Adjusters keep the coverage, liability and settlement decisions.

Is a general document AI tool or an insurance-specific platform better for claims?

Insurance-specific platforms such as Indico Data and Bevaya come with claims workflows and named Guidewire or Duck Creek connectors. General platforms such as Docsumo, Affinda and ABBYY Vantage read claim documents alongside the rest of your paperwork and connect through an API. If your engineers already own the claims-system integration, the connectors matter less than how each tool reads your documents. So test both kinds on real files.

Which claim documents can extraction software read?

Loss notices and FNOL forms, ACORD loss notices, police reports, repair estimates, adjuster reports, demand letters, CMS-1500 and UB-04 medical bills, and EOBs. Coverage differs by tool, so check that each one names the documents you receive most, and test the handwritten and faxed ones. Our guide to health insurance claim form extraction covers the medical bills box by box.

Will claims extraction software work with Guidewire, Duck Creek or an older claims system?

Hyperscience, Indico Data and Bevaya name Guidewire and Duck Creek connectors on their own sites. Docsumo and the other tools send extracted data as JSON through an API or webhooks. Your team or integrator maps it to the claims system's intake. An older system without an intake API usually takes the data through the integration layer you already run.

What is the best API for document extraction and splitting in insurance?

It depends on who builds the workflow. Amazon Textract and Sensible are APIs your engineers build around, and both publish prices. Docsumo, our product, returns extracted fields through an API and webhooks. It splits and classifies mixed claim packets on its Business plan. It sends low-confidence fields to a reviewer.

Is insurance document automation the same as document management or delivery software?

No. Document management software stores and organizes files, and document delivery software creates and sends outgoing documents such as policies and notices. Insurance document automation reads incoming documents, such as loss notices, applications and bills, and turns them into data.

See Docsumo read your own documents

Bring a few real samples. We'll show the fields extracted, the checks that ran and what a reviewer would see.