The problem with travel claims
A field officer visits 15 centres in a day across three villages. At month-end they write a claim. The branch manager can't verify it, so either everyone is paid a flat amount (unfair to the officers who ride the most) or every claim is a negotiation.
Pay for distance actually travelled
When the attendance app records location during work hours, the day's route is known. Add up the distance between points and you have the kilometres travelled — from check-in to check-out, no form to fill.
A worked example, with a rate you choose:
| Value | |
|---|---|
| Average distance per working day | 38.2 km |
| Working days in the month | 24 |
| Kilometres for the month | 916.8 km |
| Rate (two-wheeler, your policy) | ₹3.00 / km |
| Travel pay | ₹2,750.40 |
Rules that keep it fair
- Count only working hours. Tracking starts at check-in and stops at check-out; the ride home isn't company travel.
- Set the rate by vehicle — two-wheeler and four-wheeler rates differ — and write it into the travel policy.
- Look at outliers before paying. A day at three times the usual distance is worth a question, not an automatic payout or an automatic cut.
- Be open about tracking. Tell staff when location is recorded and why; it protects them as much as the company.
Tie it to targets and collections
Distance on its own doesn't tell you whether the visits were useful. Put the live map next to monthly targets and collections — entered by one person and approved by another (maker-checker) — and you see both the effort and the result.
How KYE HR does it
KYE HR shows field staff on a live map during work hours, turns kilometres travelled into travel pay, and tracks monthly targets and collections with maker-checker approval — in the same login as attendance and payroll. See field teams → · KYE HR for NBFCs and MFIs →