This mileage reimbursement calculator multiplies miles by a per mile rate. The default path uses 120 miles and rate 0.67. The product is 120 × 0.67 = 80.4.
The math is intentionally simple so expense worksheets stay easy to audit. Employer handbooks and tax rules may set different rates or caps. Confirm those rules separately. For trip distance context when you have start and end points in planning tools, keep miles labeled clearly before you multiply by rate here.
How the formula works
Reimbursement = miles × rate. Miles is the distance claimed. Rate is the amount paid per mile. There is no fuel log, no depreciation schedule, and no tax table inside this product.
Worked example
Enter 120 for miles and 0.67 for rate. Compute 120 × 0.67 = 80.4. That is the reimbursement amount shown for the default case. Raise miles to 200 at the same rate and the product becomes 134.
| Input | Value |
|---|---|
| Miles | 120 |
| Rate per mile | 0.67 |
| Product | 120 × 0.67 |
| Reimbursement | 80.4 |
How to use the fields
- Miles is the distance you are claiming for reimbursement.
- Rate is the agreed dollars per mile value (for example 0.67).
Why rate format matters
People sometimes type 67 when they mean 67 cents. This tool expects a decimal dollar rate such as 0.67. Entering 67 would inflate the product by a factor of 100 and produce an unrealistic claim total.
Sanity check with a short trip: 10 miles at 0.67 should be 6.7. If the result looks like hundreds of dollars for a short errand, inspect the rate decimal first.
Common mistakes
- Entering cents as a whole number instead of a decimal rate
- Mixing round trip and one way miles without labeling which was used
- Assuming the product equals actual fuel receipts
- Omitting the rate beside the dollar total when filing a claim
Linear scaling habits
Doubling miles doubles the payout at a fixed rate. Doubling the rate doubles the payout at fixed miles. That linearity makes classroom checks easy: hold one input, change the other, and confirm the ratio.
Ask learners to predict 60 miles at 0.67 before clicking. Half the miles should return half of 80.4, which is 40.2.
Reporting for expense packets
Write “120 miles × 0.67 = 80.4” rather than a bare 80.4. Auditors need both inputs. Add trip purpose and date in the same note so the product can be traced to a real journey.
If a policy uses a different rate by vehicle class, run separate lines instead of blending rates into one opaque total.
Classroom drills
Fix miles at 120 and compare rates 0.50, 0.67, and 0.70. Expect 60, 80.4, and 84. Then fix rate at 0.67 and compare 50, 120, and 200 miles.
Have students compute the product by hand first. The calculator becomes a verification step, which is the right habit for expense math.
Policy context without overclaiming
Organizations publish rates that change over time. This page does not assert a current legal rate. It only multiplies the miles and rate you enter. When policy text updates, change the rate field and recompute.
Personal tax treatment of mileage is a separate question. Keep reimbursement arithmetic here and seek tax guidance elsewhere when filing rules matter.
Round trip labeling
A 60 mile one way trip is 120 miles round trip if both legs are claimed. State one way or round trip beside the miles field so teammates do not double count later.
When multiple stops appear on one day, sum the driven segments first, then multiply once by the rate.
Multi day trip packets
For a week of travel, either sum all miles into one line or keep one line per day with the same rate. Both approaches multiply the same way. Separate lines make audits easier when destinations differ.
If two rates apply in one period, never blend them into a fake average without showing the split. Run each block on its own miles × rate product, then add the dollar totals.
Limitations
No map routing, no fuel price model, and no tax or employer policy engine. Output is miles × rate only.
For related unit and percent checks while you plan materials, try the unit converter or the percentage calculator.