Automate loss run processing
Unstract reads each prior carrier's loss runs as they arrive, ties every policy year to the carrier's totals, and posts the loss summary to the submission in your AMS, rater or policy system.
Trusted by insurance teams around the globe
Loss runs arrive in every carrier's own layout
A renewal needs five years of claims history, and each prior carrier sends its loss run report on its own schedule and in its own format. Someone retypes every claim into a spreadsheet, adds up each year and chases the carrier that hasn't replied.
Three carriers, three loss run layouts for the same account
Claims retyped line by line while the renewal date gets closer
A scanned loss run with the valuation date half covered
A policy year that nobody notices is missing until the quote
Loss runs that trickle in from each carrier over a week
Each loss run has to be keyed, added up and checked against the carrier's totals before an underwriter can price the account.
Unstract reads every loss run as it arrives, puts the claims from all carriers into one table, ties each year to the carrier's totals and posts the loss summary to the submission. A person sees only the account with a missing year or a total that doesn't tie.
From each carrier's loss run to the submission record, without the keying
Five steps, run on their own for every account. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up the loss runs wherever they land
Loss runs are requested from each prior carrier and come back as PDFs, by email, through a carrier portal or forwarded by the insured, usually five years per policy. Each one is picked up where it arrives and tied to the account and the submission it belongs to.
Every loss run for an account lands in one record, whichever carrier or channel sent it.
Read every loss run, then pull each claim on it
LLMWhisperer reads each loss run as text with its table layout kept, so the claim rows stay in their columns on a crooked scan. Document Studio then extracts the policy period, the carrier, the valuation date and every claim: date of loss, cause, status, and the paid, reserved and incurred amounts.
One set of field definitions runs on every carrier's loss run, whatever its columns are called.
Turn every carrier's layout into one loss table
Each carrier names its columns, lines and claim statuses differently. Every loss run is mapped into one table, with policy years, lines of business and statuses on the same codes, so a closed claim from one carrier reads the same as a closed claim from another.
The table is built per account, so five years from three carriers read as one claims history.
Check it against the carrier's totals before anyone touches it
Each year's claims are added up and tied to the totals the carrier printed. The years requested are compared with the years received, and any valuation date older than 90 days is flagged. An account that passes keeps moving. One that fails stops in a review screen with the carrier, the year and the gap side by side.
A total that doesn't tie, a missing year or a stale valuation date goes to an underwriting assistant. Every other account keeps moving.
Post the loss summary to the submission your team works from
The loss summary by year, with claim frequency, severity and large losses, goes to the submission record in your AMS, rater or policy system: an underwriting workbench such as Guidewire PolicyCenter or Duck Creek Policy, or a rating spreadsheet in Excel or Google Sheets. The loss runs stay attached, with each figure traceable to its page.
The underwriter opens a summary that already adds up, instead of five PDFs and a blank spreadsheet.
Watch it tie the loss runs from your last renewal.
Bring the loss runs behind one account, every carrier's layout included. We run them live and show each claim, each year's total and anything that doesn't tie.
Every loss run and the paperwork that comes with it
Documents
- Carrier loss runs
- ACORD forms
- Statements of no loss
- Large loss detail reports
- Experience modification worksheets
- Schedules of values
- Broker and insured loss summaries
- Carrier supplemental applications
- Prior policy declarations pages
- Loss run request letters
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Running on one book of renewals first
Nobody on your side writes code, and nothing changes overnight. Loss run processing is set up on loss runs from your own carriers and proven on one book of renewals before it goes further.
Book a consultation
We go through the loss runs behind a few recent renewals together: which carriers send them, how, and what your team checks before a submission goes to an underwriter.
Set up on your own loss runs
The fields, the year-by-year tie-out, the valuation date rule and the connection to your workbench or rating sheet are set up on the loss runs your carriers actually send.
Pilot on one book, then widen it
One book of renewals runs live within days. When the summaries hold, the other books follow, with the same checks.
Built for the teams that put a submission together
Loss runs from every prior carrier summarized for the renewal, with the missing year chased before the submission goes to market.
Five years of claims history tied out on every submission, so the account is triaged against appetite on numbers that add up.
A loss summary on the submission record before the file is assigned, with large losses and open reserves already pulled out for the underwriter.
Losses by year and cause on one summary, so the insured's risk team sees where claims come from before the renewal meeting.
Loss summaries that add up, before the underwriter opens the file
Built for paperwork that shows an account's claims history
A loss run lists every claim an account has had, what each one cost and what is still reserved, often with claimant names and injury details. In a competing broker's hands, it shows exactly how the renewal will price.
- Encrypted in transit and at rest.
- Loss runs are never used to train models.
- Access by role, account and carrier, with every review and correction recorded against the submission.
- Retention you set: processed loss runs are deleted on the schedule you choose.
- Self-hosted deployment for carriers and MGAs whose controls keep claims history inside their own environment.
What underwriting and placement teams want to know
A loss run is the prior carrier's record of every claim on a policy: date of loss, cause, status, and the paid, reserved and incurred amounts, as of a valuation date. Underwriters price an account on its claims history, so a submission usually carries five years of loss runs from every carrier that wrote the account in that time.
Define the fields once, not per carrier. LLMWhisperer reads each loss run with its table layout kept, Document Studio extracts the same fields from every carrier's version, and each layout is mapped into one table with policy years, lines and claim statuses on shared codes.
Generic OCR returns text, and someone still has to find the claims, add them up and check them. Loss run automation needs three things in a row: a read that keeps the table layout, extraction that pulls the same fields from every carrier's version, and checks that tie each year to the carrier's totals. Unstract does all three, and the same approach reads a schedule of values into one table of locations.
Look for one that reads the loss run report as a table rather than as loose text, keeps every claim row with its date and cause, and shows where on the page each figure came from. Unstract does that, then sums each year and flags large losses, so the review starts on the claims that matter instead of on retyping.
Yes. Each policy year's claims are added up and compared with the totals on the carrier's loss run, the years received are compared with the years requested, and valuation dates older than 90 days are flagged. An account that fails any of these stops with the reason attached.
The account stops in a review screen that shows the carrier, the year and the gap. An underwriting assistant requests the missing year or a fresh loss run, notes a year with no coverage, or confirms it, and the decision is recorded against the submission. Every other account keeps moving.
To the submission record in your AMS, rater or policy system, such as Guidewire PolicyCenter or Duck Creek Policy, or to a rating spreadsheet in Excel or Google Sheets. Flow posts the summary by year, with frequency, severity and large losses, as part of the run.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Loss runs are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosted deployment keeps claims history inside your own environment.
Unstract sets it up with you in a consultation, on the loss runs your carriers actually send and the checks your team already makes. One book of renewals is usually live within days, and the rest follow once the summaries hold.
Bring the loss runs from your last five renewals
Every carrier's layout, the scanned ones included. You watch each account tie out year by year, and every held account shows the missing year or the total that didn't tie.