Engineer payroll from verified data: timesheets, mileage and overtime

Most engineer payroll runs on a timesheet filled in on Friday from memory. Nobody is lying on purpose. Memory is just a poor record of a week spent between six sites and two wholesalers.

The cost is not only overpayment. When the time on a job is wrong, the cost of that job is wrong, and every quote priced from it is wrong too.

This guide explains how to build timesheets from data you already collect, and how to do it in a way engineers accept.

Step 1: Write down your pay rules first #

Before you touch any data, write down how time is paid. For example:

• When the paid day starts and ends
• Whether travel from home to the first job is paid, and at what rate
• Overtime thresholds and rates
• Callout and out of hours rates
• How breaks are treated

Get this agreed and in writing before anything else. Automating a rule nobody agrees on only produces arguments faster.

A note on travel time: for workers with no fixed base, time spent travelling to the first job and from the last job can count as working time under the Working Time Regulations. Whether it must be paid, and at what rate, depends on the employment contract and minimum wage rules. Take employment advice if you are unsure.

Step 2: Decide your sources of truth #

You need two sources that confirm each other:

• Vehicle data from a tracker or telematics system: where the van was, when it arrived, when it left
• Job status from the engineer's app: when they started and finished each job

When both agree, the time is verified. When they disagree, it is an exception for a person to review.

Step 3: Tell your engineers before you switch anything on #

Location data about an employee is personal data under UK GDPR. The Information Commissioner's Office has published guidance on monitoring workers, and it expects employers to:

• Tell workers clearly what is tracked, when, and why
• Have a lawful basis and a specific purpose
• Carry out a data protection impact assessment before monitoring starts
• Avoid tracking outside working hours where a vehicle has private use

Present it to engineers as what it is: the end of weekly timesheets and mileage claims, and protection for them when a customer disputes attendance. Let them see their own data.

Step 4: Build the timesheet automatically #

For each engineer and day, the system should produce a draft timesheet showing:

• Start and finish of the working day
• Time on site per job
• Travel time between jobs
• Stops that are not linked to a job

The engineer reviews and confirms their own draft. That takes two minutes instead of twenty.

Step 5: Review exceptions, not every line #

Set rules that flag an entry for review, for example:

• On-site time differs from the job status by more than 15 minutes
• A gap of more than 30 minutes between jobs with no travel to explain it
• A stop at an address that is not a job or a known supplier
• Overtime above the normal weekly level

The office reviews only the flagged items. An engineer can add a reason to any exception before it is decided.

Step 6: Handle mileage correctly #

How mileage is treated depends on the vehicle.

Company vans. Business mileage is not reimbursed per mile, but verified mileage lets you check fuel card spend and private use.

Engineers' own vehicles. HMRC approved mileage allowance payments apply. For cars and vans, the rate has been 45p per mile for the first 10,000 business miles in a tax year and 25p after that. Check the current rates on GOV.UK before relying on them.

Either way, calculate mileage from the actual route to the job postcode, not from a claim.

Step 7: Feed real cost back into quoting #

Once time is verified, you know the true labour cost of every job. Compare it with what was quoted. This is the input that makes the labour units in your quoting accurate, and it is the main reason to do any of this.

Checklist #

• Pay rules written down and agreed
• Vehicle data and job status both captured
• Engineers told what is tracked and why
• Data protection impact assessment completed
• Private use handled outside working hours
• Draft timesheets generated and confirmed by engineers
• Exception rules set, with a route for engineers to explain
• Mileage treated correctly for company and own vehicles
• Verified labour cost compared with quotes

This guide is practical guidance, not legal or tax advice.

How Vero does this #

Vero combines vehicle telematics with job status to produce a draft timesheet for every engineer every day. Mileage is calculated to the job postcode. The office sees only the exceptions, and verified labour cost flows back into quoting.