Common mistakes in mileage reimbursement

— Field Operations Editor

Published: 10/3/2025 • Last reviewed: 6/13/2026 • 5 min read

Avoid the most common mistakes that can delay or invalidate your mileage reimbursement request.

Common mistakes in mileage reimbursement

Why reimbursement mistakes are so expensive

Mileage reimbursement mistakes are rarely intentional, but their cost is real: delayed claims, disallowed amounts, finance rework, and, in the worst case, expense being reclassified as taxable wages during an audit. The good news is that the vast majority of problems concentrate in half a dozen recurring failures. Those who learn to recognize them can prevent almost all the trouble with small process adjustments.

Before detailing each mistake, it helps to align on the basics. If you still have doubts about what is eligible and how the calculation works, review our guide on how mileage reimbursement works. With that foundation, it becomes easier to understand why each mistake below undermines the validity of the claim.

Mistake 1: mixing personal and business trips

The most common error is recording personal travel together with work travel. The home-to-office trip (commuting) is considered personal in practically every jurisdiction and should not enter the reimbursement. Mixing the two inflates the amount and creates a direct audit risk.

The solution is to classify each trip at the source, clearly separating what is business from what is personal. Tools with per-trip classification help, but the cultural rule matters too: no one should record their daily commute as an expense. There are nuances that confuse people: a stop at a client on the way to the office can make part of the trip reimbursable, while personal detours in the middle of a work trip are not. Documenting the real sequence of stops resolves most of these doubts and keeps the entire claim from falling under suspicion.

Mistake 2: estimated distance instead of map distance

Estimating distance from memory almost always results in rounding up. The tax authority expects verifiable distances, based on the real route or a map calculation, not on guesses. Small repeated exaggerations become a pattern that draws attention.

Always use the measured distance — via GPS or route calculation — and record the real origin and destination. This removes subjectivity and makes the number defensible. A good practice is to fix the distance source in the policy: if everyone uses the same route calculation, comparisons between employees are fair and auditors see a consistent criterion. When the distance comes from a system rather than a hand-typed number, the chance of human error drops dramatically.

Mistake 3: logging too late

Recording trips weeks later undermines both memory and the credibility of the record. Many agencies consider that the record should be contemporaneous; entries made more than 30 days later lose strength as substantiation. Detailing the business purpose of each trip reinforces the substance of the expense.[^rfb-substantiation]

Set a short submission deadline — ideally daily or weekly — and automate reminders. The closer to the event, the more reliable the record. Late entries also delay the accounting close and create a cascade effect: finance receives everything at once, with no time to check, and ends up approving claims that should have been questioned. A regular cadence protects both data quality and the company's cash flow.

Mistake 4: missing business purpose

A record without a purpose ("visit to client X to close the contract") is fragile. Distance alone does not prove the trip was for work. The absence of a purpose is one of the first things an auditor questions.

Make the purpose field mandatory and guide the team to write specific descriptions, tying the trip to a concrete client, project, or task. Vague entries such as "work" or "errands" carry almost no evidentiary weight, whereas a clear note linking the trip to a named meeting or delivery is hard to dispute. To understand the tax impact of this, see our material on tax deduction for mileage.

Mistake 5: a frozen per-kilometer rate

Using an outdated rate distorts reimbursement either up or down. Fuel, maintenance, and depreciation costs change, and the rate has to keep up. A rate frozen for years can underpay employees or expose the company to challenges.

Review the rate periodically, document the calculation method, and communicate changes. Keeping the calculation record avoids arguments and demonstrates good faith. An annual review is usually enough, but sharp swings in fuel prices may require interim adjustments. The key is to record the effective date of each rate so every claim is assessed at the correct rate for its period.

Mistake 6: no integrity trail

Editable spreadsheets without history allow silent changes. Without a trail showing when the record was created and whether it was modified, the substantiation loses value. Integration with structured systems — including the export to Clara — preserves that trail and eases accounting reconciliation.

Prefer tools that record the date, time, and author of each entry, and that export data consistently to finance.

Worked example: the cost of mixing commuting into the claim

Consider a month with 1,000 km recorded for reimbursement. In a review, it turns out that 220 km were actually home-to-work travel — that is, personal and non-reimbursable. Let us quantify the damage step by step.

First, the disallowed proportion: 220 km out of 1,000 km represent 22% of the claim that will be denied. With a rate of US$0.70 per mile equivalent, that means US$154.00 of improper reimbursement out of a total of US$700.00.

Second, the tax reclassification. When an amount paid as reimbursement is deemed to be disguised compensation, it can be reclassified as taxable wages. Applying an effective rate of about 27.5%, the US$154.00 generate roughly US$42.35 of additional tax.

Third, the penalty. Fines and interest for underpayment usually add at least 20% on the tax due, or about US$8.47 in this case. Adding improper reimbursement, tax, and penalty, the error of classifying 220 km costs about US$204.82 that month — and the pattern would repeat every month if left uncorrected.

Projected over twelve months, this single classification error exceeds US$2,400.00 per employee a year, not counting the time spent responding to tax queries. When the problem is systemic and hits several drivers, the total becomes a meaningful liability. The central point of the example is simple: correctly separating the 220 km of commuting at the source would have cost nothing, while letting it slide costs dearly and grows over time.

How to build an error-proof process

Prevention combines clear rules and automation. Define a written policy stating what is eligible, the current rate, the submission deadline, and which fields are mandatory. Then use a tool that applies these rules at data entry, blocking incomplete records.

Standardize personal-versus-business classification, require a business purpose on every record, and keep an integrity trail. Finally, review the per-kilometer rate periodically and run a short monthly check focused on exceptions, not on retyping everything. It is worth creating automatic alerts for typical error cases, such as months with mileage well above the average or trips with no purpose filled in. These signals let you fix the claim before payment, not after, when the damage is already done and the correction is more expensive. Treat the monthly review as a habit rather than a fire drill, and assign a clear owner so nothing falls through the cracks.

To close, the six most common mistakes — mixing trips, estimating distance, logging late, omitting purpose, freezing the rate, and keeping no integrity trail — explain most problematic claims. Each of them has a simple, cheap fix compared with the cost of a disallowance or a tax reclassification. With a clear policy, correct classification, and contemporaneous records, reimbursement stops being a source of risk and becomes a predictable, auditable process that protects both the employee and the company over the long run.