GPS app for tracking business travel attendance: how to finalise the monthly reconciliation of timesheets (and stay compliant)

It is 5.40 pm on Friday, in the office of your maintenance company in the industrial estate south of Bologna. In front of you, on your desk, is a pile of eight hand-filled timesheets, collected from the eight field technicians who have been out and about this week in Modena, Reggio Emilia, Parma, Cesena and the Riviera. Marco, the senior technician, spent two days at a pharmaceutical client’s site in Imola; on his timesheet, he’s written 07:30 to 17:00, with an hour’s break. But you know that on Wednesday at 14:20 he rang you from the office to ask if it was OK to make a detour to Forlì to pick up a spare part. That extra journey isn’t on the timesheet. Does it count as an hour’s work or as travel time on a business trip? Which client do you charge it to? Luca, the junior, wrote on Thursday ‘journey Cesena → Rimini, 75 minutes’, but Google Maps shows 52 minutes for that stretch. Was it traffic? A stop at a motorway service station? A personal detour? You can’t verify it, but you can’t ignore it either, because at the end of the month the payslip has to balance and the travel allowance under the Metalworkers’ National Collective Agreement must be calculated accurately.

On Monday morning, Marco comes to sit in your office because he sees twelve hours fewer on his payslip than he expected. “I wrote to you that on Wednesday I was at the client’s in Imola until half past six; it was written on the sheet.” You open the sheet: “17:00 end”. Marco swears he wrote “18:30”. Neither of you can remember who’s right. And it’s not just about the twelve hours; it’s the feeling that your company’s time and attendance records are like a handwritten game where, at the end of the month, whoever kept the least accurate record loses. At the same time, your gut tells you that somewhere, amongst this month’s eight technicians and twenty-three clients, hours are being misallocated, forgotten or counted twice – not because anyone is acting in bad faith, but simply because the paperwork can’t keep up with the work.

This is a scenario experienced by every maintenance company, every technical support firm, every network of travelling sales representatives and every installation firm with technicians on the road in Italy. Following the EU Court of Justice ruling C-55/18 of 2019 – the so-called ‘ruling on time recording’ – and the subsequent rulings by the Court of Cassation requiring objective and reliable recording of working hours, the problem is no longer merely operational: it is one of labour law liability. If tomorrow the Labour Inspectorate were to ask for timesheets, handwritten sheets without objective stamps would no longer suffice. And if Marco leaves the company in five years’ time and sues you for unpaid overtime, it is you, as the employer, who will have to prove otherwise. With records that anyone could have altered retrospectively, it becomes a slippery slope.

Why timesheets for business travel don’t work, structurally

The problem with paper timesheets isn’t your technicians’ laziness. It’s the context in which they work. A technician who leaves the warehouse at 06:50 to load the van, travels 95 kilometres to the first customer, works for three hours on a system, sets off again for the second customer, stops for thirty minutes at a motorway service station at midday, in the afternoon deals with an unexpected escalation in a cold store, and returns home at 18:45, has eight or nine different entries to reconstruct, all from memory, on a Sunday evening, with a sheet of paper and a pen on the kitchen table. This lack of precision isn’t a moral failing; it’s only natural. No one can remember exactly, five days on, whether Thursday’s break lasted thirty or forty-five minutes. No one knows exactly what time he left the customer in Imola or what time he arrived at the gate of the customer in Rimini. Figures are rounded off or estimated; when in doubt, one rounds in one’s favour or against oneself, depending on one’s character.

From the company’s point of view, this gives rise to three parallel headaches. The first is the payslip: at the end of the month, someone – usually the accountant or the owner themselves – has to go through the forms, check they’re plausible, cross-reference them with the service reports, calculate travel allowances based on the National Collective Labour Agreement, and tally up expense reimbursements. For each technician, every month, this realistically amounts to between 25 and 45 minutes of pure administrative work: with eight technicians, that’s three to six hours a month during which someone isn’t producing anything, but is simply sorting through paperwork. The second headache is invoicing the client: as the hours per client aren’t broken down in detail, service calls are invoiced at a flat rate, often to your detriment. If Marco, working for the pharmaceutical client in Imola, actually spent fourteen hours rather than the twelve invoiced as a flat rate, you’re effectively giving away two hours at €78 an hour; across twenty-three clients a month, that adds up to a significant sum. The third pain point is internal trust: every technician feels that others’ hours are counted more generously than their own, and these small frustrations build up until they erupt into pay demands.

Added to this is the legal framework. Article 4 of the Workers’ Statute (Law 300/1970, as amended by the Jobs Act) regulates the use of remote monitoring tools and the admissibility of the data collected: the geolocation of employees falls squarely within this framework and requires either a collective agreement with the RSA/RSU trade union representatives or, in the absence of such an agreement, prior authorisation from the Regional Labour Inspectorate. The Court of Cassation has ruled on several occasions regarding the monitoring of attendance whilst on business travel, reiterating that such monitoring is permitted if it serves organisational, productive or safety purposes, but not as a mere surveillance tool. Without an agreement or authorisation, GPS data cannot be used in court. Under the National Collective Labour Agreement for the Metalworking, Commerce and Services sectors, the travel allowance is payable according to precise rules covering kilometres travelled, hours spent away from the workplace, and any reimbursement for meals and accommodation; a handwritten note is an inadequate means of proving that these conditions have been met.

What a GPS app for tracking business travel attendance really needs to do

An app that solves the problem of timesheets for business travel must do four things simultaneously, without turning the technician into a data entry clerk. The first is automatic GPS clocking in and out at the start and end of the day. When Marco arrives at the warehouse at 06:50, he taps ‘Start’ once on the company phone app, and the system saves the timestamp, GPS location and automatically recognises the address: Bologna-Borgo Panigale Warehouse. When setting off for the customer’s premises, no further tap is needed, as the app uses geofencing to recognise the transition from warehouse → journey → customer’s premises. Arrival at the customer’s premises is automatically recorded; on leaving, the job is closed. At the end of the day, on the way home, one final tap on ‘End shift’. Fourteen entries – which used to take twenty minutes of note-taking on a Sunday – are now recorded in real time, are accurate and cannot be altered.

The second feature is geofencing at the customer’s premises. If, for the pharmaceutical customer in Imola, you’ve set a 150-metre perimeter around the factory, the app automatically recognises entry, the start of customer hours, and exit, marking the end. Hours are no longer allocated to the client based on memory, but objectively. If Marco, after his first client, spends twenty minutes at a supplier’s warehouse collecting materials, this is a third, automatically separate record that is not mistakenly invoiced to the pharmaceutical client. The third feature is integration with payroll: at the end of the month, the app exports, for each employee and for each day, the hours worked, travel time, breaks, travel allowances and reimbursement claims, all in a format that your accountant or payroll software (TeamSystem, Zucchetti, ADP) can import directly. What used to take three hours of data validation is now just a single file.

The fourth aspect – and the most critical for an Italian company – is compliance with the GDPR and the Workers’ Statute. A GPS app used whilst on business travel touches on two sensitive areas: the geolocation of an employee and electronic attendance tracking. Both are subject to clear rules. Regarding the GDPR (EU Regulation 679/2016), a legal basis is required (generally Article 6(1)(f) on the grounds of a legitimate interest that overrides the data subject’s interests, or a trade union agreement), transparent information must be provided to the employee, tracking must be limited to working hours (not during breaks, not after the end of the shift), and there must be a limit on the retention period. Under Article 4 of the Statute, a collective agreement with the RSA/RSU is required, or, if the company has no internal trade union representation, authorisation from the Territorial Labour Inspectorate: without one of these two steps, the data cannot be used. In recent years, the Data Protection Authority has fined several companies that had introduced GPS systems without providing a privacy notice and without the correct legal basis, with fines running into five figures.

How to introduce the system without causing a row in the workplace

The most common mistake when introducing a GPS app for staff on business trips is the ‘quick fix’ approach: the owner orders it on Wednesday, and by Monday morning the technicians are expected to have it installed, ‘after all, it’s only for the hours worked’. This approach inevitably leads to conflict – sometimes informal with Marco and Luca, sometimes formal in the form of a complaint to the Data Protection Authority or the trade union. The proper approach involves three steps. First: a Data Protection Impact Assessment (DPIA, pursuant to Article 35 of the GDPR), because the geolocation of employees is considered a high-risk processing operation for the rights and freedoms of data subjects. The DPIA documents the purposes, scope, retention period, recipients and security measures, and serves as your defence should the Data Protection Authority ask for an explanation. Second: a trade union agreement with the RSA/RSU setting out binding terms regarding tracking times, what happens during breaks, how the data is used and how long it is retained. In the absence of internal trade union representation, prior authorisation from the ITL is required; this application must be submitted alongside the other documentation. Thirdly: a written privacy notice to all workers involved, in accordance with Article 13 of the GDPR, in clear Italian, explaining what the app does and what it does not do.

The crux of these three steps is transparency, and, paradoxically, transparency resolves ninety per cent of the resistance within the team. When Marco and Luca realise that the app only tracks their location during working hours, that they can check their own clocking-in records at any time, that there is no tracking after the end of their shift, and that the data is used not to monitor them but to pay them correctly for their hours – and is therefore to their advantage – the tone changes. It goes from “you want to monitor us” to “at last I can prove that on Wednesday I really was there until half past six”. In companies where the transition has been handled properly, after three months the app is so widely accepted that the technicians themselves ring up if their company mobile hasn’t synchronised, because they don’t want to lose any of their own hours. The Data Protection Authority and the Court of Cassation have repeatedly clarified that GPS attendance tracking whilst on business travel is lawful provided the aforementioned conditions are met; the legal framework is in place, it just needs to be followed correctly.

---

The future if you stick to paper timesheets

You’ll continue to lose between three and six hours of administrative work every month verifying the plausibility of handwritten timesheets, plus several hundred euros per technician per year in uninvoiced client hours, because the flat-rate system works against you. At the next inspection by the INPS, the Labour Inspectorate or the Revenue Agency, you will be asked to produce your time records and will present handwritten sheets whose evidential value, following the 2019 EU rulings, is limited. If a technician who has left the company sues you for unpaid overtime, the employment tribunal judge will, when in doubt, side with the claimant, because you are unable to provide objective evidence that the hours claimed were not worked. At the same time, your competitors who are already using digital GPS apps are positioning themselves in the eyes of industrial clients as the most transparent operators, who invoice in a traceable manner, and are winning the big contracts, whilst you are forced to settle for smaller clients with lower profit margins.

The future if you switch to digital GPS tracking

That Monday morning scenario with Marco no longer happens. If he sees twelve hours missing from his payslip, he opens the app himself on his company phone, views the daily reports for the previous four weeks with the GPS stamps, and either finds a genuine error that’s corrected in two minutes, or realises it was a mistake on his part, which is resolved without any argument. As the business owner, at the end of the month you no longer spend three hours deciphering paper records, but simply open the payroll reports, check the plausibility at a glance, export the data to TeamSystem or Zucchetti, and that’s it. On the customer invoicing screen, you can see the actual hours clocked for each customer and each job, with GPS proof, and you can invoice for exactly two and a half hours, rather than rounding up to a flat rate of twelve; for a maintenance company with eight technicians, this easily translates to an extra fifteen to twenty-five thousand euros in profit margin per year. When dealing with the ITL, the INPS or the employment tribunal, you present an unalterable export file documenting who worked when and where; the defence is no longer ‘he said, she said’, but ‘log versus claim’. And within the team, the never-ending issue of hours disappears, because it is no longer up for negotiation.

What you really need to get there

You need an app that runs on a standard company mobile phone, with a geofencing engine that reliably distinguishes between the warehouse, travel and the client’s premises, and which works without constant intervention from a technician – because the technician is on the roof of a cold store, not sitting at a desk. You need payroll reporting broken down into hours worked, travel time, breaks, travel allowances and reimbursements, exportable into Italian payroll formats. You need a native GDPR architecture: tracking only during working hours, self-access for employees, a defined retention period, a documented DPIA, and a facsimile of the trade union agreement pursuant to Article 4 of the Articles of Association. And you need a supplier who supports you beyond the signing of the contract, because the first four weeks with a team of technicians accustomed to working with paper for twenty years will determine the success or failure of the roll-out.

GeoTapp was built precisely for this situation, following discussions with maintenance companies, technical support firms and networks of Italian field technicians who were all too familiar with the monthly ritual of 5.40 pm on Fridays, faced with a pile of paperwork. Automatic GPS clocking in and out at the start and end of the day, geofencing for client sites, separation of hours worked, travel time and breaks, export to TeamSystem / Zucchetti / ADP, GDPR-compliant architecture with a documented DPIA, a facsimile of the trade union agreement pursuant to Article 4, and self-reporting by the employee. See how it works and imagine your next Friday evening in the office, without that pile of handwritten timesheets on your desk.

And what about you? How many hours do you spend each month deciphering handwritten timesheets from your field technicians, cross-checking them and feeding them into the payslip system? And how often does this end up in a row at the start of the month? Write it in the comments – the problem with handwritten timesheets for field staff is more widespread than business owners care to admit, and your contribution will help other colleagues in the same situation.