Catch inflated mileage claims before you sign off on them

If you do the books for a plumbing outfit, an HVAC company, an electrician, or any business that sends people out to jobsites, you already know the monthly ritual. A pile of mileage claims lands in your inbox — a technician drove to three jobs, a stop at the supply house, back to the shop — and you're expected to approve reimbursement based on numbers you have no easy way to check.

Most bookkeepers handle this one of two ways. Either you trust the numbers because checking them properly would take longer than the job itself, or you spot-check a handful by hand — opening a map, typing in the start address, typing in the end address, reading off a distance, closing the tab, and doing it again for the next claim. Neither option is great. The first one means you're occasionally signing off on numbers that are wrong, sometimes by a little, sometimes by a lot. The second one eats twenty or thirty minutes a week doing something that feels like it should be simpler than it is.

The actual cost of not checking

Mileage reimbursement is one of those line items that looks small until you add it up. A technician who rounds up "about 40 miles" to a flat 50 every time, across a dozen jobs a month, across a handful of technicians, across a year, is not a rounding error anymore. It's real money leaving the business, and it's money you approved.

It isn't always dishonesty, either. Plenty of overstated claims are just guesswork — someone doesn't remember the exact route, so they estimate high "to be safe." Some are address mix-ups: a technician logs the wrong jobsite, or writes down an address that's close but not exact, and the distance calculation is off before anyone even starts driving. Either way, the business is footing the bill for numbers nobody actually verified.

And when you do try to verify a claim by hand, the process itself is slow enough that you can only really do it for the ones that look suspicious. That means the small, steady overstatements — the ones that never look dramatic enough to flag — sail through every single month.

What a quick address check actually gives you

Here's the shift: instead of checking claims one at a time by typing addresses into a map, you take the whole month's list of jobsite addresses — every start point, every stop, every end point — and turn it into a spreadsheet with the exact location of each one attached. Once every address has a precise location next to it, spotting a claim that doesn't add up becomes something you can see at a glance rather than something you have to go hunting for.

If a technician claims 62 miles for a job that pins two streets over from the shop, you'll notice immediately. If someone logged a jobsite address that's slightly wrong — a transposed digit, a missing apartment number, a town name that doesn't match the ZIP code — that shows up too, because it either won't return a location at all or it'll return one that's clearly nowhere near where the job was actually done. Either way, you've caught something worth a follow-up question before the reimbursement goes out, not after.

This isn't about building a fancy mileage-auditing system. It's about turning "I have no easy way to check this" into "I can glance at a map and tell in ten seconds." That's the whole value.

How it works

You don't need any technical background for this, and you don't need your clients' technicians to change how they log jobs. This runs entirely on your end, on the spreadsheet you already collect.

Step 1: Export your list of jobsite addresses

Pull the month's mileage claims into one spreadsheet — one row per trip, with the starting address and the destination address in their own columns. If your bookkeeping software already exports this, use that. If it's a manual log, a plain spreadsheet works fine.

Step 2: Upload the file

Sign in to your account and upload the spreadsheet. You're not writing anything or configuring anything technical — you're picking the file, the way you'd attach it to an email.

Step 3: Let it process

The service reads every address in your file and works out its exact location — latitude and longitude, plus a cleaned-up version of the address itself. For a typical month of jobsite trips, this takes minutes, not hours, and there's nothing for you to do while it runs.

Step 4: Download your results

You get back the same spreadsheet you uploaded, with the exact location added for every address, plus a note on any address that couldn't be matched cleanly — which is often your first clue that something was logged wrong.

Step 5: Spot-check the outliers

Sort or scan for the claims where the locations don't match what was reported, or where the flagged addresses need a second look. This is the two-minute step that used to take twenty. You're not manually mapping every trip anymore — you're reviewing a short list that the process has already narrowed down for you.

What it costs

CSV2GEO's Lite plan is $19 a month and covers up to 21,000 US addresses. For a bookkeeper handling mileage and jobsite checks across even a dozen field-service clients, that's more headroom than you'll likely use in a month — most small field-service operations submit a few hundred jobsite addresses at most, even with several technicians running multiple jobs a day. The plan is a subscription you can cancel anytime, and subscribing works out to about 30% cheaper per address than paying one-off, which matters if this becomes a recurring part of your monthly close.

You could bill this back to clients as part of a monthly reconciliation service, or simply absorb it as a tool that makes your own job faster and your sign-off more defensible. Either way, $19 a month is a modest price for not having to guess whether a mileage claim is real.

Frequently Asked Questions

It's fair to wonder whether this is worth adding to your monthly routine, especially if you're not naturally a "software" person. Here's what usually comes up.

Is this hard to set up if I'm not techy at all? No. If you can attach a file to an email, you can use this. There's no software to install and nothing to configure — you upload a spreadsheet and you get one back.

What happens if an address is messy, incomplete, or just wrong? You'll see it flagged in the results rather than silently guessed at. A jobsite address with a typo, a missing unit number, or an inconsistent town name either won't match cleanly or will come back looking off — and that's exactly the kind of thing worth a quick follow-up question to the technician who logged it.

Do I need to understand mileage or routing software to use this? No. This isn't a routing tool and it doesn't calculate driving distance for you. What it gives you is the exact location of each address, which is the piece of information you need to sanity-check a claim yourself — either by eye on a map or with a simple distance comparison in your spreadsheet.

Can I cancel if I only need this for a couple of months? Yes. It's a month-to-month subscription with no lock-in. If tax season or a particular client audit is the only reason you need it, use it for those months and cancel afterward.

Is client data safe if I'm uploading addresses that include job details? The file you upload only needs addresses to work — you can strip out anything else (client names, invoice numbers, job notes) before uploading if you'd rather keep the file to the minimum needed. Only include what you're comfortable sending.

What if I only have a handful of mileage claims to check each month? Then this is barely a dent in your monthly plan allowance. The Lite plan's 21,000-address limit is built for far higher volume than a typical bookkeeping caseload — you're not paying for capacity you'll never touch, you're paying for the ability to check whenever you need to.

Will this catch every case of overstated mileage? It catches the clear ones — jobs where the claimed distance and the actual location obviously don't line up, and addresses that were logged incorrectly. It's a sanity check, not a forensic audit. But most overstated claims aren't subtle once you can actually see where the job was.

The real point

You're not trying to catch anyone out. Most of the time, a mileage discrepancy is a rounding habit or a typo, not fraud. But right now you have almost no efficient way to tell the difference between an honest estimate and a real problem, so everything gets approved on trust. A monthly address check doesn't change how your clients' technicians work. It just gives you, the person actually responsible for signing off on the number, something concrete to look at before you do.

For $19 a month, that's a cheap way to stop guessing.

Related Articles

• Quoting jobs by real driving distance, not guesswork
• Mapping a service radius that keeps crews on schedule
• Handling addresses that won't geocode
• Offering address cleanup as a recurring client service
• The real cost of running your own geocoder

---

*I.A. / CSV2GEO Creator*