If you work in roofing or insurance restoration, you've heard the word Xactimate thrown around constantly. But what actually is a Xactimate ESX file — and why does it matter for getting paid on insurance claims?
This guide breaks it down from the ground up: no jargon, no fluff — just the practical knowledge you need to understand the ESX format, how it fits into the claims workflow, and how tools like ESXPress are changing the game for contractors who don't want to spend hours manually entering line items.
What Is Xactimate?
Xactimate is the industry-standard estimating platform used by insurance carriers, adjusters, and restoration contractors to price property claims. Owned by Verisk, it's the de facto tool for roofing, water mitigation, fire restoration, and virtually every type of property damage claim in the United States.
When an adjuster writes an estimate — or when a contractor supplements one — they use Xactimate's pricing database, which contains over 20,000 base line-item codes (called SEL codes; ESXPress's 18,054 catalog counts SEL entries including activity variants) with region-specific material and labor pricing updated monthly.
What Is an ESX File?
An ESX file is Xactimate's native file format — specifically, the ESX (Estimate Solution XML) format used since Xactimate version 28. It replaced the older .esx binary format with a compressed XML structure that can be imported, exported, and shared between Xactimate users.
Key facts about ESX files:
- Format: Xactimate's native project-file format
- Contains: Every line item, quantity, price, depreciation, overhead, and profit calculation
- Portable: Can be emailed between adjusters, contractors, and supplementers
- Region-aware: Pricing is tied to a specific price list (e.g., the current Tulsa list)
- Required by: Most major insurance carriers for claim settlement
Key Insight: An ESX file is not just a spreadsheet — it's a structured project file that Xactimate uses to verify every line item against its pricing database. Getting the format right is critical for a supplement to be accepted.
Why ESX Files Matter for Roofing Contractors
Here's the reality of insurance restoration: if you can't produce a clean, code-accurate ESX file, you're leaving money on the table. Adjusters work in Xactimate. Carriers approve estimates in Xactimate. When you submit a supplement in the same format the adjuster uses, you're speaking their language — and that dramatically increases approval rates.
Contractors who master the ESX workflow typically see:
- Faster supplement approvals — a clean, code-accurate file doesn't bounce back for corrections
- Fewer line-item disputes because codes match the carrier's price list
- Higher claim values by including every codeable item
- Professional credibility with adjusters and desk reviewers
The Old Way vs. The New Way
Traditional Manual Entry
- Receive carrier's estimate PDF (often 30-60 pages)
- Manually open Xactimate and create a new project
- Set the correct price list and tax jurisdiction
- Enter every line item by hand — searching each SEL code
- Input quantities, adjust depreciation, calculate O&P
- Export as ESX and email to the adjuster
Time: 3–6 hours per estimate. Error-prone. Tedious.
ESXPress Automated Conversion
- Upload the carrier's estimate PDF
- AI extracts line items, maps SEL codes, and matches pricing
- Review the parsed data (typically minutes)
- Use AI Copilot to add missing line items in natural language
- Export a ready-to-import ESX file
Time: Under 2 minutes. Accurate. Repeatable.
ESX File Structure — Under the Hood
For the technically curious, a valid ESX file contains:
- Document structure: Required sections (
PROJECT_INFO,CLAIM_INFO,SALESTAXES,EMBEDDED_PL) in Xactimate's expected order - Required fields per line item:
itemId,calc(calculation type, usuallyqtyfor quantity-based), SEL code, description, quantity, unit price, and tax status - Metadata: Price list ID, tax jurisdiction, claim number, and estimate-level overhead/profit percentages
Missing a single required field — like itemId — will cause Xactimate to reject the entire file on import. This is why automated tools with format validation are essential for reliable conversion.
Common ESX Mistakes That Get Supplements Rejected
- Wrong price list: Using an outdated or wrong-region price list
- Missing itemId: Every line item requires a unique identifier
- Malformed project structure: Sections missing or out of order
- Tax jurisdiction mismatch: Not matching the claim location
- Missing required line items: Like O&P (overhead and profit) when applicable
- Invalid SEL codes: Codes that don't exist in the target price list
Frequently Asked Questions
Can I open an ESX file without Xactimate?
No — ESX files require Xactimate desktop (version 28+) to open natively. However, tools like ESXPress can generate valid ESX files without Xactimate installed, which you then send to the adjuster or open in your own copy of Xactimate.
What's the difference between ESX and PDF estimates?
A PDF is a static document — it shows line items but can't be imported into Xactimate. An ESX file is the live, editable estimate format that Xactimate understands. Converting PDF to ESX is the bridge between carrier paperwork and actionable supplement data.
How long does it take to learn Xactimate?
Most contractors spend dozens of hours becoming proficient — often 40 or more — and that's just for basic estimate entry. Supplement building, macros, and advanced reporting take much longer. Tools like ESXPress dramatically reduce the learning curve by automating the most time-consuming parts.
Does every insurance carrier accept ESX files?
Virtually all major carriers in the US use Xactimate as their primary estimating platform — State Farm, Allstate, Liberty Mutual, Travelers, USAA, and dozens more. If the adjuster uses Xactimate (and most do), they can import your ESX file.
The Bottom Line
An ESX file is the currency of insurance restoration. Whether you're a contractor supplementing a claim, a public adjuster building an estimate, or an independent adjuster settling losses — fluency in the ESX format directly impacts your bottom line.
ESXPress was built to give contractors that fluency without the 80-hour learning curve. Upload a PDF, get an ESX. It's that simple.
Start your free 14-day trial — card required, no charge until it ends →