Extract the policyholder, policy number, loss date and type, estimated loss, assigned adjuster, and claim status from a first notice of loss (FNOL) PDF.
The full guide: First notice of loss (FNOL) opens the claim file
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
A first notice of loss is the initial report that OPENS a claim. The extractor reads the claim or FNOL number and report date, the policyholder name, policy number, contact email, and phone, the loss date, the loss location address, the loss type (enum), and the loss description.
The preliminary estimated loss amount and currency, the coverage type, the policy limit, the deductible, and the general aggregate limit, the assigned adjuster or handler (assignee name and email), the insurer name and NAIC number, the producer name, and the claim status (open, acknowledged, pending, in review, approved, denied, or closed).
Yes. The damaged items table returns each item number, description, value, damage extent, and estimated repair cost; a claim coverages table returns each coverage type, limit, deductible, and coverage status; and a documents submitted table returns each document type, date, description, and submission date.
An FNOL is the earliest intake — the first report of an incident that opens the claim with a preliminary estimate and an assigned adjuster. A claim filing is the later, formal itemized submission carrying beneficiary and payment details. For that formal submission, use the claim filing extractor.
PDF only, up to 10MB and 100 pages. The notice is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Redact the policyholder contact details where you can.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for underwriting and claims teams, or the extraction API if you are building it in.