OCR for insurance documents: what it reads, where it stops and how to automate the rest

OCR in insurance turns scans, faxes and photos of insurance documents into text a computer can read. It reads applications, certificates of insurance, loss runs, claim forms and policies. But it reads the characters, not what they mean. It can't tell a policy number from a claim number, or check a limit against a contract. So insurers, agencies and TPAs add three steps. AI extraction puts each value in its field, and validation checks the values. A person reviews anything the software is unsure about. Checked data then goes into their policy and claims systems.

The first section compares eight tools that insurers shortlist. The rest of the post explains what OCR reads, where it stops and what to automate after it.

OCR and document AI tools for insurance compared

Some tools read and check insurance documents in one platform. Others are cloud APIs that your engineers use to build their own tool. Docsumo is our product. We took facts about the others from each vendor's own site in September 2026. The links are in the sources at the end. For all 12 tools, including which ones split mixed packets and read loss runs, see our list of OCR software for insurance companies.

Our list of claims data extraction tools has each tool's full entry. To compare tools on splitting and labeling alone, see 14 document classification tools.

What is OCR in insurance?

OCR stands for optical character recognition. It's software that finds the text in an image of a page and turns it into characters a computer can search and process. In insurance, it's the first step in reading documents that arrive as scans, faxes, emailed PDFs and phone photos. These are the main document types.

• ACORD applications

  The ACORD 125 commercial insurance application, plus line sections such as the ACORD 126 for general liability and the ACORD 140 for property.

• Certificates of insurance

  Evidence of the coverage a vendor, tenant or borrower holds, to check against what a contract requires. US liability certificates usually come on the ACORD 25; Australia calls them certificates of currency.

• Loss runs

  The insurer's report of claims on a policy. It lists the policy number, coverage period, number of claims, paid losses and the date of each loss. Underwriters read them to judge a risk's claims history.

• Claim forms and loss notices

  ACORD property, auto and liability loss notices, plus the police reports, estimates and invoices behind a claim.

• Health claims and ID cards

  CMS-1500 (professional) and UB-04 (institutional) claim forms, explanation of benefits (EOB) statements, and member ID cards with the member and group numbers. See the claim form guide.

• Policies and declarations

  The declarations page names the insured, the insurer and the agent or broker, and lists each coverage with its limit and premium. Endorsements change the terms.

OCR vs OCR plus AI extraction

OCR's output is text and where it sits on the page. It can't tell which date on an ACORD 125 is the proposed effective date. Nor can it tell whether a limit on a certificate meets the contract. AI extraction uses layout and context to put each value in its field, then checks it.

For the claims side of this comparison, with the fields to pull by claim type, see OCR claims processing.

How to extract data from insurance documents with OCR

Every document goes through the same stages, whether it's a submission, a certificate or a claim. Only the fields and the checks change.

1. CapturePull email, portal uploads, faxes and mail scans into one queue.
2. Clean upStraighten, de-noise and sharpen scans and photos so the characters are clear.
3. Classify and readSort pages by document type, such as application, loss run or claim form, and run OCR, handwriting included.
4. Extract and checkPull named fields and tables, then check them. Dates should fall in range, totals should add up, and values should agree across documents.
5. Review and deliverSend low-confidence fields to a person, then pass the data to your policy, claims or agency management system by API.

OCR use cases in insurance

The same pipeline serves four jobs across the policy lifecycle.

• Submissions and underwriting

  Read ACORD applications, loss runs and statements of values from broker submissions, so underwriters review risks instead of keying them. See ACORD form processing.

• Claims intake

  Turn loss notices, claim forms, estimates and medical bills into claim data, and see what's missing before an adjuster opens the file.

• Policy servicing

  Read declarations pages, endorsements and change requests to keep the policy record in step with the documents.

• COI compliance

  Read certificates of insurance and check limits, dates and additional insured status against each contract. See COI tracking.

For COI compliance, OCR plus AI extraction puts each policy, limit and date on an ACORD 25 in its own field. Each one is then ready to check against the contract.

Challenges of OCR in insurance, and how to handle them

Plan for these five before you pick a tool.

• Scan qualityFaxes, skewed scans and phone photos blur characters. Clean up images before OCR and send low-confidence values to review.
• HandwritingClaim forms and applications are often filled in by hand. Use a tool that reads handwritten text, as Docsumo does, and keep a person on the values it's unsure about.
• Tables across pagesLoss runs, statements of values and itemized bills often run over several pages. Extraction should join each into one table with the headers mapped.
• Layouts that varyLoss runs, declarations pages and medical bills differ from one carrier, broker or provider to the next. ACORD forms also change by edition. Avoid tools that need a template per layout.
• Sensitive dataClaim and health files carry personal and medical information. Ask for SOC 2 Type 2, ISO/IEC 27001 and, for health data, a HIPAA business associate agreement (BAA). Docsumo is SOC 2 Type 2 audited, ISO/IEC 27001:2022 certified and HIPAA compliant, and signs a BAA (security).

How Docsumo handles insurance documents

Docsumo is an intelligent document processing platform. It reads printed and handwritten text and handles any document type, from ACORD forms and certificates to loss runs and claim files. On the Business plan, it classifies mixed packets and splits them into documents. On the Enterprise plan, it checks values across documents and manages each file as a case.

Fields it's unsure about go to your own team, with confidence thresholds set per field. Each value is linked to its line on the page, and reviewers' corrections improve the model. Tables that run across pages are joined into one table, with the headers mapped. Data goes to your policy, claims or agency management system through an API and webhooks. Docsumo isn't a policy or claims system, and it runs in the cloud only.

• 99%99%field-level accuracy across 250+ document types
• 95%+95%+of documents processed straight through, without manual review
• 99%99%accuracy on insurance compliance documents at Arbor

Vertikal RMS uses Docsumo to verify certificates of insurance through ACORD capture, and Arbor uses it on insurance compliance documents.

Which insurance document to automate first

What we'd do. Start with one document type that you receive in large numbers and that a decision depends on. Loss runs for underwriting and loss notices for claims are examples. Automate that type until a person sees only the exceptions. Then add the next one.

OCR turns insurance paperwork into text, not into checked data. Pair it with AI extraction, validation and a review step. Then applications, loss runs, claims and certificates become fields that your underwriting, claims and compliance teams can use. People handle only the exceptions.

Book a demo with a few of your own insurance documents, or start a free trial.

Frequently asked questions