Use caseAuto insurance

Auto claim documents cross-checked

Report, estimate, appraisal, invoice: four documents that should agree. The adjuster rereads the same plate and amounts, and odd lines slip by.

Every document is read field by field on arrivalThe documents are checked against each otherThe adjuster settles each gap and sets the amount

Actions on this case file
The assistantConsistency check

The plate matches on all four documents. The invoice is $183.15 above the approved amount, and the VIN differs on its last character.

source · 4 documents on the case file
The verdict on the documents

A gap between two documents · both values shown, with their page

01

The problem

The whole thing in one move

Helen, an auto adjuster in Dallas, has four documents on claim SI-26-07734 and twenty more claims waiting behind it. What separates the documents is a few characters: one wrong digit in a VIN, one part added after the appraisal. Read in a row on a busy day, the line that differs looks like the others, and the shop gets paid for a part nobody approved.

Here the comparison runs as each document lands. The AI extracts the fields of each one, applies the consistency rules the claims team wrote, and shows every gap with both values and their page. Helen starts from the differences, checks them in the documents, and sets the amount to pay.

Invoice F-2026-1460.pdfViewer
The last document in. The shop's invoice, read the morning it arrives and set against the three documents already on the claim.
Invoice against appraisalAI console
One line too many. The invoice set against the approved repairs, with the sensor nobody approved.

Each of these screens exists somewhere in a claims office today. The difference is the order: each document is read once, the documents are checked against each other, and the adjuster settles what differs before anything is paid. The steps follow claim SI-26-07734 through its four documents and one corrected invoice.

02

Each document, read on its own

Before any comparison, each document is typed and its fields are extracted with their page.

Step 1Intake

Four documents, each in its slot

Daniel Mercer's car was hit at an intersection in Dallas on October 14. Over four weeks his claim has received the police accident report, the estimate from Delgado Auto Body, the report of the appraiser Paula Hughes, and this morning the final invoice. Each one is filed in its named slot on the case, so it carries its type.

Accident reportShop estimateAppraisal reportFinal invoice
Claim SI-26-07734 · DocumentsCase management
A document filed in its slot gets its type and opens in the viewer.
The last document starts the checkWhen the invoice fills the last slot, the process runs the comparison. Nobody has to remember to launch it.
Step 2AI check

The accident report gives the vehicle and the facts

The AI extracts the fields the comparison needs from the accident report: the plate and policy of each vehicle, the contributing factor recorded, the point of impact. For vehicle A, Mr. Mercer's car, it reads plate LKT-4182 and an impact on the front right.

Accident report.pdfViewer
Each extracted field keeps the page it was read on.
The facts are written onceThe plate, the policy and the impact zone are fields on the case. The next documents are checked against them.
Step 3AI check

Estimate and appraisal become line items

The estimate and the appraisal use different layouts. The AI extracts both into the same lines: each part with its reference and price, labor with hours and rate, paint, totals. The appraiser approved the bumper, the right headlight and the fender, with 6.5 hours of bodywork.

Appraisal HE-26-3381.pdfViewer
Up to fifty values per document, each one tied to its line on the page.
Two layouts, one set of linesThe shop's format and the appraiser's format no longer matter. What is compared is the part, the hours and the price.
03

The documents, checked against each other

The claims team wrote the consistency rules in plain language. Each one names the documents and the field it compares, and two of them stop on this claim.

Step 4AI check

Ten rules run when the invoice arrives

The rules check that all four documents describe the same car, that the repaired parts fit the impact, and that the invoice stays within what the appraiser approved.

Same plate and VIN on every document?Do the parts match the impact zone?Is the invoice within the approved amount?

The result is written onto the case: a status and the reasoning in plain words. Here the status is Attention required, with two gaps.

Consistency checkAI console
A rule never decides which value is right. It shows both, with their source.
The adjuster opens the file on its gapsHelen does not reread four documents to find two lines. The two lines are named before she starts.
Step 5Viewer

The VIN gap is checked in the documents

Helen, the adjuster, searches for the VIN in the appraisal report: it is printed with a 7 at the end. The invoice and the registration card in the customer folder both end in 1. It is the same car, and the appraisal has a typo.

She leaves a note on the appraisal page and marks the rule as reviewed.

Appraisal HE-26-3381.pdfViewer
The note stays on the document, visible to whoever opens it next.
A doubt is cleared with its reasonThe next reader sees why the rule was cleared, and by whom. Nobody has to ask Helen again.
Step 6Assistant

The invoice has a line the appraiser did not approve

Every part on the invoice matches the appraisal, except one: a front parking sensor for $183.15, in neither the estimate nor the report. Helen asks the assistant whether the report mentions the sensor.

Appraisal HE-26-3381.pdfViewer
The answer cites the page, so the adjuster checks it in one click.
Worth counting: how many invoice lines get paid each month because nobody had time to set them against the appraisal?
The extra line is found before paymentTwenty dollars or two hundred, the line is named with its amount. The adjuster decides what to do with it.
04

The adjuster settles

The comparison has done its part. What to pay, and what to ask, stays with Helen.

Step 7Assistant

One message to the shop, the appraiser copied

Helen asks the assistant for a message to Delgado Auto Body. The draft names the line, the amount and the page of the report. She adds that a supplemental appraisal is possible if the sensor failed after the inspection, and sends it.

Claim SI-26-07734Case management
The message and its sources are filed in the case history.
The shop hears about it the same morningThe question goes out with the page that backs it. The shop answers on facts, and the claim does not stall.
Step 8AI check

The corrected invoice passes every rule

Two days later Delgado Auto Body sends a corrected invoice without the sensor. It is filed as a new version of the invoice, read, and the ten rules run again. The status moves to Complete.

SettlementCase management
The amount is the adjuster's field. The check only says the documents agree.
Helen approves on documents that agreeShe sets the amount, minus the deductible, and approves. The first invoice stays on the case as an earlier version.
Step 9Settings

The rule learns its reference document

Each month Brett, the claims administrator, reads the reasons adjusters gave when they cleared a rule. VIN gaps were almost always cleared against the registration card. He adds one sentence to the VIN rule: compare with the registration card first, and name the document that differs.

Rule: same VIN on every documentAI console
The rule is plain language, changed without a release of the application.
The next VIN gap points to its culpritHandlers no longer look for which document is wrong. The rule says it, and they check.
05

The verdicts

Ten rules give each claim one result: the documents agree, two of them differ, or a rule fails outright. Helen's next move depends on which.

Complete

The documents agree

Same car, parts that fit the impact, an invoice within what was approved. The check records all three on the claim in one line.

After that: the adjuster checks, sets the amount and approves.
Attention required

Two documents differ

A character in a VIN, a line on the invoice. The check shows both values and the page of each.

After that: the adjuster clears the gap or asks the shop; the check runs again on the new document.
Not eligible

A rule fails, and you know which

A plate that belongs to another car, repairs on a zone the report says was not hit. The AI lists what passes first.

After that: a letter drafted from the file, reviewed and signed by the adjuster.
What the AI leaves to you

It sets no amount. It pays no shop. It decides no gap is a typo. Across the nine steps on this page, every gap is settled by the adjuster, with her name and her reason on the case.

The AI extracts, compares and drafts. The rules are written by the claims team, in plain language, and they change when the team sees a better one.

06

Time back

These come from claim SI-26-07734 alone. Your document set and the rules your team writes will move them.

0 linesretyped to compare the documents. Parts, hours and amounts are extracted from each one.
10 rulesrun on every invoice the moment it arrives, the same way on a quiet day and a busy one.
1 linestopped before payment: the parking sensor nobody approved, found with its page.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Why these numbers hold

Zero wasted readingProductivityThe comparison runs before the adjuster opens the file. She reads the gaps first.
Zero silent gapsProcess reliabilityEach difference is named with both values and its source. A cleared gap keeps its reason.
Decision supportA person decidesAnswers cite their page. The amount and the approval stay with the adjuster.
07

Who it helps

An adjuster, a claims administrator and an architect will each look at this from their own desk. This is what they find.

Business operations

Claims adjusters

Four times the same facts, and the line that differs hides in the fourth.

  • The file opens on its gaps, before page one.
  • Each gap shows both values and their page.
  • Answers about a document cite where they come from.
  • The message to the shop is drafted with the right line and amount.
Administration

Claims administrators

The checks live in people's heads, and every adjuster runs them a little differently.

  • The consistency rules are written down, in plain language.
  • Brett edits a rule, and the next invoice runs on it.
  • The reasons adjusters give tell you which rule to sharpen.
  • Every check run stays in the case history, dated.
IT and architecture

CIOs and architects

Each new check used to mean a new script on a new server.

  • The check is a step in the claim process.
  • The appraiser's and the shop's documents arrive through the API.
  • Each AI call leaves a log line: question, answer, model.
  • Hosted in your data center or in the cloud.

A good first step

With one pair of documents. Set the invoice against the appraisal on your auto claims, with three rules. A month of real claims shows whether the rules catch what your adjusters catch.

The accident report and the estimate join the same check afterwards, with rules your team adds one at a time.

Let's talk

Check your own claim documents

Bring a few anonymized claim folders with their appraisals and invoices. We will run the same comparison on them and look at the gaps with your team.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.