Mileage Claims in a Staff App: Which Distance and Which Rate Are You Approving?

A mileage claim needs an approved journey quantity and a defined reimbursement rate, not just a photograph of a fuel receipt. Before commissioning an expenses app, decide how the employee explains the journey, which distance is eligible and which version of the rate applies. Otherwise a plausible total can conceal an unsupported claim.

This is software planning, not a statement of tax allowances or an employee's legal entitlement. Have the actual eligibility rules, rates, evidence requirements and accounting treatment reviewed for your organisation and jurisdiction. Do not copy a number from a software demonstration into your reimbursement policy.

Distinguish a journey claim from vehicle spending

Fuel bought, distance travelled and distance approved for reimbursement are different records. A company vehicle's odometer history does not automatically identify an employee's eligible business journey. Likewise, a fuel receipt describes a purchase, not the distance to reimburse.

For a hypothetical service team, a useful claim might identify the employee, journey date, business purpose and the distance submitted with its unit. Decide whether you need origin and destination, a reference to the visit, or another reviewed supporting record. Collect only what the approved process needs; continuous location tracking is not a prerequisite proposed by this guide.

Keep the employee's submitted distance separate from any reviewer adjustment. If a journey contains a private detour or another excluded portion, the application should explain the accepted quantity rather than silently replacing the original claim.

Treat the rate as policy data, not an anonymous price

The official Odoo 19 expense-entry guide illustrates quantity-based expenses: a configured category supplies a unit price, and entering a quantity updates the total. Its mileage example uses miles and a category-specific price per mile. That is an illustration of configuration and multiplication, not an official reimbursement allowance for your business.

In your specification, attach the unit to both the distance and the rate. A rate per mile must not be applied to an unlabelled kilometre quantity. If conversion is needed, agree the conversion and rounding rules and retain the submitted unit for review.

Ask who maintains the approved rates and how changes take effect. Does the journey date choose the rate, or does another reviewed rule apply? A later category-price edit should not silently change the meaning of an already approved claim. Request a retained rate or policy-version reference and an explicit correction path. These are proposed controls, not features verified by the cited Odoo page.

Make adjustments explainable

Show the submitted quantity, accepted quantity, applicable rate and resulting claim amount together. Distinguish an incomplete journey description from an ineligible claim. Name the person who can resolve each case and let the employee see what information is missing.

Decide how corrections affect approval. Changing a distance or the applicable rate after approval may require renewed review under your policy. Keep the original decision understandable rather than presenting today's recalculation as the amount previously authorised.

A mileage calculation is not proof of payment. Reuse the separate submission, review and settlement states described in staff expense claims. Do not build a second reimbursement route simply because mileage has its own entry screen.

Accept a policy example, not just a calculator

Include a labelled distance, the wrong distance unit, an adjusted journey, a missing business purpose and a rate change between journey and submission in your demonstration. Correct an approved historical claim and inspect both its current amount and decision history. Use fictional people and journeys.

Write the expected outcomes into your acceptance criteria, after checking the policy with the responsible adviser. The deliverable is a traceable journey-to-claim calculation connected to the existing expenses process, not a dashboard that confidently multiplies two unexplained numbers.

Source boundary

Odoo 19: Log expenses, read on 26 October 2026, supports the quantity, category unit-price and calculated-total example. Journey evidence, effective-date rules, rate history, reviewer adjustments and unit validation above are commissioning requirements to implement and test separately. No jurisdiction-specific rate or tax outcome is asserted.