Cut 12% of Fleet Cost: Reconcile Mileage Logs 2026

A plumbing contractor with eight trucks gets a stack of fuel-card statements at the end of each month, a separate export from the GPS tracker, and a third pile of paper mileage sheets the techs may or may not have filled out. Reconciling them — matching every fuel purchase to a vehicle, a driver, and a logged trip — is a tedious afternoon in a spreadsheet that the office manager dreads, so it gets done late, incompletely, or not at all. The result: fuel bought on a Sunday near a tech's house never gets questioned, and thousands of dollars in legitimate mileage deductions go unclaimed because the logs were never clean enough for the accountant to trust.

This is a workflow recipe for automating that reconciliation. Fuel-and-mileage reconciliation is the process of matching each fuel-card transaction and each logged trip to a specific vehicle and job, then flagging the charges that do not line up. Done by hand it is error-prone and slow; automated, it runs nightly, catches anomalies the day they happen, and produces an IRS-defensible mileage log as a byproduct. This is a bottom-of-funnel guide — you have the fleet, the fuel cards, and the tracking; here is the step-by-step recipe to wire them together, plus where US Tech Automations does the matching concretely.

Key Takeaways

• The pain is three disconnected data sources — fuel-card statements, GPS/telematics logs, and trip records — reconciled by hand, so waste and missed deductions hide in the gaps.

• The recipe matches every fuel transaction to a vehicle and a logged trip automatically, flags mismatches (off-hours fills, no-trip purchases), and outputs a clean mileage log.

• Homeowners using ANGI for service requests: 7.5M (2024) according to ANGI's Annual Report (2024) — demand is high, margins are thin, and uncontrolled fleet cost is exactly where home-services profit leaks.

• Numeric tables below quantify typical fleet-cost leakage, the deduction value of clean mileage logs, and a per-truck ROI estimate.

• US Tech Automations runs the match nightly: it ingests the fuel-card feed and telematics data, reconciles them, and routes flagged anomalies to the owner for review.

Why manual reconciliation leaks money

Fleet is one of the largest controllable costs in a home-services business, and reconciliation is the control. Without it, three kinds of money disappear: fuel waste, unclaimed deductions, and the labor spent matching spreadsheets.

US business mileage IRS deduction rate: 70 cents per mile (2025) according to the IRS Standard Mileage Rates (2025). A service van running 25,000 business miles a year represents $17,500 in deductible expense — but only if the mileage log is contemporaneous and defensible. A log reconstructed from memory at tax time is exactly what the IRS disallows, so sloppy reconciliation does not just risk an audit, it forfeits the deduction.

Fuel waste is the second leak. Fuel can represent up to 60% of total fleet operating cost according to the U.S. Department of Energy's Alternative Fuels Data Center (2023) — and personal use, off-route detours, and outright fuel-card misuse are invisible until someone matches each fill to a logged trip. The matching is the audit; skip it and the leak runs indefinitely.

The numeric majority here is the point: each row is a dollar figure you can recover, and they stack. Across an eight-truck fleet the recoverable total runs well into five figures a year.

Who this is for

This recipe is for home-services businesses — HVAC, plumbing, electrical, landscaping, pest control — running roughly 5 to 50 service vehicles with fuel cards (WEX, Fuelman, Fleetcor) and some form of GPS or telematics (Samsara, Verizon Connect, Motive). If your office reconciles fuel and mileage in a spreadsheet, or not at all, and you suspect waste or know you are leaving deductions on the table, this is for you.

Red flags — skip this if: you run fewer than 3 vehicles where a quick monthly glance suffices, you have no fuel cards or GPS tracking (no data to reconcile), or you reimburse personal vehicles instead of operating a fleet. Without both a fuel-transaction feed and a trip/mileage source, there is nothing to match.

The recipe: step by step

Here is the reconciliation workflow, broken into the steps the automation runs. Each step is a discrete check; together they turn three raw feeds into a clean log and an anomaly list.

The five-step recipe is the spine of the workflow. Steps 1 and 2 are pure data work that automation does instantly and humans do slowly; steps 3 through 5 are where the value lands — the flags that catch waste and the log that captures the deduction.

A common variant: route serious anomalies (a fuel purchase 80 miles from any job, repeated weekend fills) the same way you would route warranty claims to the service desk — into a tracked queue with an owner and a due date, not a one-off email that gets buried. Teams that already reconcile subcontractor invoices against jobs will recognize the same match-flag-route pattern.

The recipe runs on a daily cadence rather than monthly for a reason: a fuel anomaly is far easier to resolve the morning after it happens than four weeks later when the tech barely remembers the day. A same-day flag — "this $68 fill on Saturday has no matching trip" — gets a quick, honest answer; the same question a month later gets a shrug. Catching it fresh is half the deterrent value, because techs quickly learn that off-book fuel use is noticed within a day, not buried in a quarterly review nobody reads.

Inside the nightly match: feeds, rules, flags

This is the concrete execution. US Tech Automations connects to your fuel-card provider's transaction feed and your telematics platform's trip API. Each night it pulls the day's fuel transactions and GPS trips, then matches every fill to a vehicle by card number and to the nearest logged trip by timestamp and location — the step the office manager does by eye across two spreadsheets, run automatically in seconds against the full day.

When a transaction does not match — a fill at 9 p.m. on a Saturday, a purchase with no corresponding trip, or a tank that holds more gallons than the vehicle's capacity — US Tech Automations flags it and routes it to the owner with the transaction details, the vehicle, the driver, and the surrounding trip history attached, so the review starts with evidence rather than suspicion. The matched trips, meanwhile, accumulate into a contemporaneous mileage log that exports clean to the accountant at year-end. The same engine can pull double duty and reconcile parts inventory against job usage, since both are the same match-and-flag pattern over different feeds.

A worked example

Take a 12-truck HVAC company using WEX fuel cards and Samsara telematics, averaging 22,000 business miles per truck per year. Before automating, the office manager spent about 6 hours a month reconciling fuel statements against GPS exports and gave up on building a clean mileage log entirely, so the company claimed deductions on only an estimated 60% of its actual business miles. They wired a nightly workflow to the Samsara trip.completed event and the WEX transaction export: it matched 96% of fills automatically, flagged 11 anomalies in the first month (including $740 in weekend fuel purchases near one tech's home), and produced a complete log covering all 264,000 fleet miles. The recovered deduction on the previously unclaimed 40% of miles — roughly 105,600 miles at the 70-cent rate — represented over $73,000 in additional deductible expense, on top of the fuel waste the flags surfaced and the 6 monthly hours returned to the office.

ROI per truck

The recipe pays for itself at small fleet sizes because the recoverable categories stack per vehicle. Multiply the per-truck recovery by your fleet count and compare to a one-time setup measured in days.

The numeric-majority ROI table is the BOFU case in one view. Even the conservative end of the range — a mid-five-figure annual recovery on a dozen trucks — dwarfs the configuration cost, and the deduction value alone usually covers it.

The labor recovery is easy to undervalue but real. Service businesses lose 21 days a year per employee to manual data entry according to Smartsheet's automation research (2017), and reconciliation is exactly that kind of repetitive matching work. Handing it to a nightly automated job returns those hours to the office manager for revenue work — scheduling, dispatching, customer follow-up — that actually grows the business.

Setting your anomaly thresholds

The reconciliation is only as good as the flags, and the flags are only useful if they are tuned to your fleet. Set them too loose and real waste slips through; too tight and the owner drowns in false positives and stops reviewing the queue. The thresholds below are sensible starting points to adjust against your first month of data.

Idling can consume 0.5-1 gallon of fuel per hour with the engine running according to the U.S. Department of Energy's Argonne National Laboratory (2015), which is why an excessive miles-to-fuel mismatch is a legitimate flag — a truck burning fuel without logging miles is often idling on the clock. The thresholds turn that physics into a routable alert.

The numeric-majority threshold table is what you hand to whoever owns the review queue. Start here, watch the false-positive rate for two weeks, and tighten the bands until the flags are almost all real. A queue the owner trusts is a queue the owner actually works.

The flagged items should land in a tracked queue with an owner, the same way a smart shop handles any exception — not as an email that scrolls away. Teams that already track permit applications per project will recognize the discipline: every exception gets an owner and a resolution, or it does not get resolved.

When NOT to use US Tech Automations

If you run two or three trucks, an owner who glances at the fuel statements each month will catch most problems for free — the automation's setup is not worth recovering a few hours a quarter. If you do not operate fuel cards or any GPS/telematics, there is no transaction feed and no trip data to reconcile; you would be automating a process you do not yet have, and the right first step is adopting fuel cards and tracking, not a reconciliation tool. And if your accountant already builds a clean mileage log from a single integrated fleet platform, a separate reconciliation workflow may be redundant — check whether your existing tool already matches fuel to trips before adding another. Honest take: this recipe earns its keep on fleets of five-plus trucks with separate fuel and tracking data and real waste; below that, simpler habits win.

FAQ

What does fuel-and-mileage reconciliation actually match?

It matches every fuel-card transaction to a specific vehicle and to the nearest logged trip by time and location, then checks the mileage-to-fuel ratio for plausibility. The output is a list of matched, clean records and a queue of anomalies — fills with no trip, off-hours purchases, or impossible MPG.

How does automating this recover tax deductions?

The IRS requires a contemporaneous, defensible mileage log to claim the standard mileage deduction — 70 cents per mile in 2025. Automated reconciliation builds that log from your trip data as it happens, so you can claim deductions on all your business miles instead of the fraction you can defend at tax time.

What data sources do I need?

A fuel-card transaction feed (WEX, Fuelman, Fleetcor) and a GPS or telematics source (Samsara, Verizon Connect, Motive). The automation matches the two; without both, there is nothing to reconcile. If you have only one, start by adding the other.

How does it catch fuel theft or personal use?

By flagging fills that do not match a logged business trip — purchases at odd hours, near a driver's home, or with no corresponding GPS trip — and by checking that gallons purchased are plausible for the vehicle and miles driven. These anomalies are invisible in a manual monthly glance and obvious to a nightly automated match.

How long does setup take?

For a fleet on standard fuel cards and a major telematics platform, connecting the feeds and configuring the match rules is typically a few days of setup, after which the reconciliation runs nightly without intervention. The main effort is mapping vehicles to cards and confirming the anomaly thresholds.

Does this replace my telematics platform?

No. Your telematics platform tracks the vehicles and your fuel card records the purchases; the automation sits on top and reconciles the two into a clean log and an anomaly queue. It complements those tools rather than replacing them.

Getting started

If your trucks are running and your fuel and mileage data live in separate, un-reconciled piles, you are almost certainly leaking deductions and fuel cost you cannot see. The recipe is straightforward: ingest both feeds, match every fill to a trip, flag the mismatches, and let a clean log accrue. See how US Tech Automations runs the nightly match and routes anomalies on the agentic workflows platform, and review pricing to plan your fleet rollout.