One scope at a time works right up until Monday. Then four adjusters send through forty carrier scopes, half of them over 100 lines, and the week is spent re-keying instead of building. Batch conversion is the answer to that pile, but only if the tool can actually take the volume. Two numbers decide whether it can: how many files you can push at once, and how many lines each file is allowed to carry.
Here is how batch conversion works, where the line cap bites, what a week of scopes costs on a per-conversion plan, and how to keep the batch clean as it goes out.
What batch conversion actually means
The shape is the same PDF to ESX converter you would use for one scope, pointed at many.
- Bulk upload. Drop a stack of carrier PDFs into the dashboard instead of one at a time.
- Parallel processing. The files convert at the same time, so a batch moves in roughly the time one conversion takes rather than the sum of all of them.
- A review queue. Converted estimates land in a queue so a reviewer can work through them in a deliberate order instead of by memory.
- Batch export. The finished .esx files download together, or push to your Xactimate directory.
- An API for the steady flow. If scopes arrive in an inbox or a shared drive, the REST API can convert each one as it lands, so the batch is really a pipeline.
For the full enterprise picture, including white-label and team accounts, see the batch PDF to ESX enterprise guide.
The line cap is the number that decides throughput
The cap is where a batch either flows or hits a wall. Every ESXPress plan converts scopes of 1,000+ line items per file in a single pass. There is no per-line surcharge at any tier, so a 900 line scope costs the same as a 90 line one, and a long scope converts whole instead of being silently cut down. That last part matters more than it sounds. A silent truncation is a scope that looks finished and is missing lines, which is exactly the kind of gap you find weeks later on a job you have already started.
Not every tool works this way. Some meter by the line item and charge overage above a capped allowance, which means the same heavy week costs more depending on how large each scope happens to be, not just how many there are. ClaimsFlow's published rate (claimsflow.io) was $0.35 per line item with 150 free line items as of 2026-09-24, a per-line model to weigh against a flat per-conversion price. Their rates change, so check their page before you budget from it, and the side-by-side sits on ClaimsFlow vs ESXPress.
What a week of scopes costs
On a flat per-conversion plan, the cost scales with the count, not the size of each file. Our published tiers run 25 conversions for $179, 75 for $479, 100 for $599, 250 for $1,450, 500 for $2,750, 1,000 for $5,250, and 2,500 for $12,500, which lands at a $5.00 per file floor at the top tier. Past your monthly cap, conversions pause rather than billing you for surprise overage, and one-off credit packs ($29 for 1 file, $99 for 5, $175 for 10, or $375 for 25) cover a spike without locking you into a higher plan. The free plan includes 5 conversions a month with no card.
The full breakdown, including how flat per-conversion pricing compares with per-line meters, is in what PDF to Xactimate conversion costs, and the current rates are on the pricing page.
Keep the batch clean as it goes out
Volume makes review the bottleneck, so it pays to make review easy.
- Validate before you file. Run each finished .esx through the free ESX validator so a structural problem is caught on your side of the handoff.
- Read the flagged lines first. Lines the conversion could not ground kept the carrier's price and are marked. Those are the ones that need a human eye, and they are the ones that tend to grow a supplement.
- Work the queue in one sitting. Reviewing a batch together keeps the decisions consistent across the week instead of drifting claim by claim.
One more thing a batch exposes: the omissions. A single scope missing drip edge is easy to shrug off. Forty scopes missing the same line is a pattern you can fix once, and the completeness check that runs on each dashboard conversion is what surfaces it. That is the difference the whole workflow is built around: while competitors convert what is already on the PDF, ESXPress also identifies and restores what the carrier omitted.
Start with next week
Upload a batch, let it convert in parallel, and review from the queue. Start free with 5 conversions a month and no card, then size the plan to your volume. Start a batch, or compare the PDF to ESX tools first if you are still choosing.