Conveyance reimbursement repays an employee for approved work travel under the company’s policy. A useful claim explains the trip, the eligible distance, the applicable rate and the reviewer’s decision. A total amount without those details is difficult to check.

For a field team using bikes or cars, distance-based claims can be organised with a simple calculation and a consistent review process. The examples below use illustrative company rates, rather than a universal reimbursement rate.

How do you calculate a conveyance reimbursement claim?

For a distance-based company policy, multiply the eligible kilometres by the applicable company rate per kilometre. Add separately approved trip expenses only when the policy allows them, and account for any advance already paid.

A bike rate and a car rate may differ. The business should identify which rate applies to a trip and when that rate became effective. Do not substitute a public internet rate for the rate agreed under your company policy.

A conveyance allowance is different from a trip claim

A fixed allowance is a different arrangement from reimbursement based on individual trips or expenses. Before calculating anything, establish which arrangement your business uses. A fixed monthly amount should not silently be treated as a per-kilometre claim, and the same travel should not be submitted twice through different processes.

This guide covers the review of trip claims; confirm the applicable payment arrangement in your company policy.

What information belongs in a travel claim?

Recorded distance and eligible distance can differ

A route record helps provide context, but it is not automatically the reimbursable distance. A company policy may treat commuting, personal detours or particular journey segments differently. Agree those rules before employees submit claims.

Also distinguish a route estimate from odometer readings and location-derived travel history. They answer related questions but can differ. Missing updates or an unusual route need a review with the employee; they are not, by themselves, a reason to assume the claim is false.

Ask the selected app to demonstrate how it presents claimed distance, recorded travel and supporting readings. NexaSync’s expense and conveyance workflow supports this review alongside configurable vehicle reimbursement rates.

A worked example of a changed approval amount

Suppose an employee submits 86 km at the illustrative company rate of ₹5/km: ₹430. After reviewing the trip with the employee, the manager confirms 72 km as eligible business travel under the agreed policy. The distance-based approved amount is ₹360.

The useful review record retains the 86 km submitted, the 72 km approved, the applied rate and a specific explanation for the difference. It should also distinguish any separately approved parking or toll amount. Do not silently replace the submitted amount without context.

If the parties disagree about eligibility or distance, follow the company’s review process. Keep the issue visible until someone owns the next decision.

A five-step claim review workflow

1. Employee submits: record the work purpose, trip details, eligible distance and evidence required by policy.
2. Reviewer checks: verify the date, vehicle category, rate and any duplicate or pending claim.
3. Clarify differences: compare the submitted trip with available records and ask the employee for context where needed.
4. Record the decision: keep the approved amount and an explanation with the supporting information.
5. Reconcile the outcome: follow the company’s payment process and distinguish an approved claim from a payment already completed.

Approval is not the same as money reaching an employee’s bank account. Confirm how the approved report moves into your company’s payment process rather than assuming a tracking app pays reimbursements automatically.

Agree the rules before the first claim

• Which work journeys are eligible and how commuting or personal segments are handled.
• Vehicle categories, effective rates and the person authorised to change them.
• Evidence needed for distance, tolls, parking and other allowed costs.
• Submission and review deadlines, with a route for disputed claims.
• How advances, duplicate submissions and approved-but-unpaid claims are reconciled.

Keep the process proportionate. Ask for the evidence needed to resolve the claim rather than requiring several unrelated screenshots for every routine trip.

What to check in conveyance reimbursement software

Evaluate one ordinary trip, one claim with missing information and one decision where the approved amount differs. Confirm who can review the claim and what the employee can see afterwards. Check whether exports include the information your finance team needs.

NexaSync connects claim review with the field team’s recorded working day. Review the expense workflow and current Pro plan capabilities; expense review is a Pro capability rather than part of the basic Free plan.

For the wider evaluation, combine this example with a useful client visit report and the five-day pilot checklist. The salesman tracking app guide explains how managers can review attendance, locations and visit outcomes together.

Common questions

What per-kilometre rate should we use?

Use the applicable company policy and vehicle category. The ₹5/km examples in this guide are illustrative; they are not a universal or government-mandated reimbursement rate.

Can an employee claim both fuel receipts and a kilometre amount?

That depends on the company’s approved arrangement. Define what the kilometre rate covers and avoid reimbursing the same cost twice. Resolve uncertainty before the claim is submitted.

Does GPS history automatically approve a claim?

No. It can provide context for a review. Eligibility, the applied rate, missing information and the approval decision still need to follow the company process.

Does approving a claim mean it has been paid?

No. Keep the approval outcome separate from the payment and reconciliation process, and confirm how your business communicates each status.