Sign in Talk to our team
Use case · Insurance claims

Insurance claim extraction. Hours, not weeks.

FNOL forms, medical bills, repair estimates, police reports — claim packages arrive as multi-document bundles, each with its own format. fluex extracts and normalizes every supporting document into a single claim schema in under five seconds per document, ready to trigger straight-through processing or route to a claims handler.

Book a demo API reference

Why claim packages stall

A typical auto-claim package contains a FNOL form, a police report, repair estimates from one or two body shops, photos with damage descriptions, and possibly medical bills. A property claim might include the FNOL, a contractor estimate, photos, and a public adjuster's report. Each document type has a different format; manual handling means a claim sits in a queue for days. OCR-based parsers handle structured forms but break on free-text reports and unusual estimate formats.

How fluex does it

fluex parses each document type with a specialized schema and merges them into a single claim record. FNOL forms produce structured incident data. Repair estimates produce line items, parts, and totals. Medical bills produce CPT codes, charges, and provider info. Police reports produce parties, citations, and narrative sections. The merged claim record is then ready for straight-through processing rules (auto-approve, refer to handler, refer to SIU).

Sample extraction output

claim_typeAuto — collision
claim_numberAC-2026-04-0188
incident_date2026-04-18
claimantRobert M. Taylor
policy_numberPOL-1029384
vehicle_regABC-1234 (NY)
documentsFNOL, police report, 2× repair estimates, 6 photos
repair_estimate_lowUS$ 8,420.00 (Acme Auto Body)
repair_estimate_highUS$ 9,180.00 (City Collision)
estimated_lossUS$ 8,800.00
coverage_check✓ Comprehensive — confirmed
fault_indicatorAt-fault: third party
stp_eligible✓ — within auto-approve threshold
confidence0.96 → straight-through processing

What you get out of the box

Multi-document claims

FNOL, police reports, medical bills, repair estimates, photos with annotations — merged into one claim record.

Line-item parts & labor

Repair estimates parsed to part numbers, labor hours, and totals — ready for negotiation or comparison.

Medical bill normalization

CPT codes, ICD codes, charges, allowed amounts, provider info — normalized across hospital, clinic, and provider invoices.

Straight-through-processing flags

Configurable auto-approval rules (loss threshold, fraud score, document completeness) trigger STP or route to a handler.

Integration patterns

fluex integrates with major claims systems (Guidewire, Duck Creek, Insurity, Sapiens) via REST + webhook. The async API handles 50-document claim packages in under 90 seconds end-to-end and pushes the normalized claim record into your loss-adjustment workflow.

Compliance & trust

Claim documents include PII, medical info, and accident-scene data. fluex retains them encrypted at rest with per-tenant keys; HIPAA BAA is available on Enterprise for medical-bill workflows. Configurable retention from 0 to the statutory 7-10 years many insurance regulators require. See our trust page for the full posture: encryption, tenant isolation, sub-processors, GDPR DPA, CCPA, SOC 2 Type II in progress, and HIPAA BAA on Enterprise.

Get started

Pay-per-page pricing means you can start an evaluation today without an annual commit. Most teams ship their first claim-document extraction into production within a week.