Skip to content
⚠️ Staging environment, test only, not production
Sign In
Supplements9 min read

The Xactimate Reprice Trap: When an Old Price List Owes You a Supplement

Xactimate reprices a file against the list on the machine that opens it. Here is why an old carrier price list can owe you a supplement, and how to catch it.

Review required: AI-generated output requires professional review, verify every line item, price, and total before submission.

Chaz Jaco

Co-Founder & Software Architect, ESXPress

You send a converted scope to a client, they open it in Xactimate, and the total that comes back is not the total that left your desk. Or you open a file someone sent you and the numbers move before you touch a thing. The question that follows is always the same: why did the total change?

The answer is usually not a bug and not a bad conversion. Xactimate prices every file against the price list loaded on the machine that opens it. That is how the platform works, and once you can see which lines moved, the change stops being a mystery and becomes a supplement line.

Here is the mechanism, the one error that moves more single lines than any other, and a pre-import workflow that surfaces all of it before you submit.

What reprice actually means

A Xactimate estimate is line items, quantities, codes, and notes. The prices are not locked into the file the way most people assume. When the file opens, Xactimate prices each line from the list loaded on that machine, for that region, for that price month.

So two people can open the same file on two machines in two regions and see two different totals before anyone edits anything. The file carries the record. The receiver's list does the pricing.

That is the idea behind keeping the printed price on every line in a converted file. The price you saw on the carrier's PDF stays attached to the line as a reference, and Xactimate prices it again against your list. When the two differ, the difference is information, not noise.

When the delta is a legitimate supplement line

Price lists move with the market and by region. A scope the carrier priced on an older price month can come back higher today for no reason other than the list moved. When the work is still ahead of you, that gap is a supplement conversation.

The pattern is simple. Date the list the carrier used. Reprice the same scope on your list. Compare the two line by line. Where a line moved and the work has not been done yet, you have a documented supplement line with a reason attached: the scope was priced on an edition that no longer reflects current costs.

Key Insight: Do not argue with the total. Argue with the line. A total that moved is a headline. The line behind it is what a reviewer can act on, and a line only moves when you attach the reason it should. Repricing hands you the list of lines that already moved on their own.

Date the carrier's price list before you submit

Every Xactimate estimate carries a price-list identity: a region and an edition, often called the price month. On a carrier's PDF you will find it near the estimate header or on the summary. The exact label varies with the product and version that produced the file, so look for the region and the date rather than one fixed heading.

Write it down as the first line of your supplement narrative. Something as plain as "priced on [region] [month]" tells the reviewer exactly which list your comparison is built on. That puts the conversation on the document instead of on a memory of a phone call.

Where that edition differs from the one you have loaded, expect movement when the file opens. The conversion did not fail. Two price lists disagreed, and now you can name them.

The activity-code mismatch, the biggest single-line error

Line items carry an activity code. Install means material and labor. Removal means labor only: you take the old material off, and you do not buy and install anything new. Add covers a smaller addition to an existing line.

The most common reprice error on a file that was converted, re-keyed, or assembled by hand is a removal priced as an install, or a line that should have been a removal left as a full install. It is one line, and because install lines carry material, that one line can move a total hard.

Before you submit, sort the file and read the activity on every large line. Anything that says remove, tear out, or detach should be a removal activity. Anything going back on the roof should be an install. Check the biggest labor lines first, because the cost of the mistake lives there.

The catch-all code trap

Xactimate has catch-all and miscellaneous classes. When a scope uses one, Xactimate prices that line itself on import, from its own list, and the figure that comes back can land far from what the file carried.

This is the failure mode behind files that reprice to several times their original figure. The line looked harmless in the scope. On import, the platform did what a catch-all class tells it to do, and the total followed.

ESXPress does not emit catch-all codes. It keeps the printed price from the carrier's PDF on the line and flags anything it cannot match to a real code, so an unresolved line shows up in a review list instead of hiding inside a number. You see the line that needs a decision, and you make it.

A pre-import workflow that catches all of this

  1. Date the price list on the carrier scope. Region and edition, written down.
  2. Convert the PDF to ESX with the printed price kept on each line.
  3. Read the review list. Unresolved lines are flagged there, not guessed at.
  4. Run a reprice check to see which lines your list prices differently.
  5. Compare the totals item by item: replacement cost, overhead and profit, tax, depreciation, and the net figure. Name every line that moved.
  6. Fix the activity codes and the catch-alls, then submit.

Steps two and four are the ones people skip, and they are the ones that turn a mystery into a list.

Why line by line beats eyeballing

A total that moved tells you nothing about which line moved. Comparing a PDF against an estimate by eye means you cannot reconcile quantity by quantity, and the line you miss is usually the expensive one. Get both sides onto the same structure first, then compare.

Convert the carrier scope PDF to a Xactimate ESX file so the comparison is line for line, with the printed price kept on every line and anything unverifiable flagged for review. Start on the free plan: five conversions a month, no card required.

To go deeper on the mechanism, read why Xactimate reprices an estimate and the repricing explainer. To see which lines your own list prices differently, run the reprice check. If you build supplements from satellite scopes, the satellite supplement guide covers the carry-over items that go missing before the file ever opens, and the complete PDF to Xactimate guide walks the full conversion.

This post was drafted with AI assistance and reviewed for accuracy.

Xactimate is a registered trademark of Verisk Analytics, Inc. ESXPress is independent and not affiliated with or endorsed by Verisk/Xactware.

#xactimate reprice#roofing supplements#price list#insurance claims#carrier scopes#activity codes

Frequently Asked Questions

Why did Xactimate change my total when I imported the file?
Xactimate prices every line against the price list loaded on the machine that opens the file. If that list differs from the prices the file carried, the total moves. This is expected platform behavior on every import, not a conversion error, and it is why a converted file keeps the printed price on each line as a reference.
Can an old price list turn into a supplement?
Yes, when the work has not been done yet. If the carrier priced the scope on an older price month and the same scope prices higher on your current list, the difference on each affected line is a documented supplement item. Date the carrier's list, reprice the scope, and compare line by line.
Where do I find the price list date on a carrier estimate?
The estimate carries a price-list identity near its header or summary: a region and an edition, often called the price month. The exact label varies by the product and version that produced the PDF, so look for the region and the date rather than one fixed heading, and record both in your supplement narrative.
What is the most common reprice error on a scope?
A removal priced as an install. Removal activity is labor only, while install activity carries material and labor, so a line coded as the wrong activity can move a total on its own. Sort the file and check the activity code on every large labor line before you submit.
What is a catch-all code, and why does it reprice a file?
Catch-all and miscellaneous classes (the 9500 and 9501 family) tell Xactimate to price the line itself on import from its own list. A scope that uses them can reprice far from its original figure. ESXPress does not emit catch-all codes; it keeps the printed price and flags anything it cannot match to a real code.
Does converting a PDF to ESX stop Xactimate from repricing?
No, and it should not. Xactimate still prices the file on import. What conversion gives you is a line-for-line structure, the printed price on every line, and a review list of unresolved codes, so you can see exactly which lines moved and why.

Ready to convert PDFs to ESX in minutes, not hours?

Start free, no card required, 5 free conversions included. Upgrade to a paid plan for a 14-day trial (card required, no charge until it ends). First conversion in about two minutes.