10 Red Flags in Time and Attendance Software Demos (and What to Ask Instead)
Vendor demos skip the edge cases that break payroll. Here are 10 warning signs in time and attendance software, from hard-coded overtime to biometrics with no lawful basis, and the test to run on each before you sign.
The Demo Shows the Happy Path, and Your Payroll Lives Off It
A scripted demo of time and attendance software shows the cases that go smoothly: a nine-to-five employee clocks in, the timesheet totals up, a manager approves it. Your real risk sits elsewhere. It's the night shift that crosses midnight, the warehouse with no signal, the overtime premium that changes on public holidays, and the fingerprint reader your works council or data-protection regulator never approved.
Each red flag below comes with a question or hands-on test. Send the tests to vendors before the second meeting and ask them to run your scenarios live in a sandbox. If a vendor won't, you've learned something too.
Red Flag: Overtime Rules That Need a Services Ticket to Change
If the presenter says overtime is "configured by our implementation team," find out what that means. Often it's a hard-coded rule set you can't edit without paying for professional services. That fails the first time a collective agreement or a law changes.
Overtime rules vary widely by country. Brazil requires a premium of at least 50%, and many collective agreements set more for Sundays and holidays; hour-bank (banco de horas) arrangements are also permitted. India's Factories Act generally requires double the ordinary rate for covered workers, and state shop-and-establishment laws add their own thresholds. Gulf states set statutory premiums that often differ for night work. In the EU, the Working Time Directive caps average weekly hours, while premiums come from national law and sector agreements. Verify current figures locally.
What to ask instead: "Show me an admin building a new overtime rule while we watch: daily and weekly thresholds, a holiday multiplier and an averaging period." A real overtime rules engine supports effective dates, so last month's timesheets still calculate under last month's rules.
Red Flag: Every Example Uses the Vendor's Tidy Sample Company
Sample data is built to look clean. Your schedules aren't. Before the demo, send five real (anonymized) scenarios and ask the vendor to run them live:
- A shift running from 22:00 to 06:00 that crosses a daylight-saving change
- A split shift with an unpaid break the employee forgot to punch
- Ramadan reduced hours, which many Gulf jurisdictions require for private-sector staff
- An employee who works across two sites with different pay rates in one week
- A public holiday that lands on a rest day
If the answer for two or more is "we'd handle that with a manual adjustment," you'll be fixing them by hand every pay period.
Red Flag: No Straight Answer on Offline Clocking
Ask what happens when the network drops. If the vendor changes the subject, expect trouble. Construction sites, field-service vans, basements and rural plants all lose connectivity, and an employee time tracking app that simply refuses the punch leaves you with paper notes and pay disputes.
Test it: turn on airplane mode or unplug the terminal, record three punches, then reconnect. Check that the punches sync with their original timestamps, that duplicates get flagged, and that the record shows each punch was captured offline. Ask, too, how long a device can stay offline before it stops accepting punches.
Red Flags: Biometrics With No Lawful Basis, and No Way Around Them
Fingerprint and face terminals stop buddy punching. They also involve some of the most sensitive data you'll hold. Two warning signs recur: the vendor treats employee consent as enough, and the system has no non-biometric option.
Under the GDPR, biometric data used to identify a person is special-category data, and European regulators have repeatedly said consent is rarely freely given in employment. Several have penalized employers over biometric time clocks. Brazil's LGPD treats biometrics as sensitive data. India's DPDP Act requires notice and a valid purpose. Gulf countries have national data-protection laws, and free zones such as DIFC and ADGM run their own regimes. In some US states, Illinois among them, employers face direct lawsuits over biometrics.
What to ask instead:
- Is the template stored on the device, on the employee's card, or in your vendor's cloud? On-device or on-card storage is the lower-risk design.
- Do you keep raw images or only irreversible templates?
- Can we offer a PIN, badge or QR alternative to each employee without extra licensing?
- How are templates deleted when someone leaves, and can you show us the deletion log?
Before buying hardware, have qualified data-protection counsel review biometric time clock privacy in each country you operate in. In many jurisdictions that means a formal impact assessment.
Red Flag: GPS Tracking That's Either Always On or Off
Geofencing keeps remote clock-ins honest. A system that tracks location continuously, including on breaks or after the shift ends, is a proportionality problem under the GDPR and a trust problem anywhere. Some European countries also have right-to-disconnect rules that make constant tracking harder to justify.
Ask for: location captured only at the moment of the punch, a geofence radius set per site, and a clear on-screen notice for the employee. Confirm you can switch location off entirely for particular roles or countries.
Red Flag: "We Export a CSV to Your Payroll"
This is where these projects most often go wrong. A generic CSV can mean your payroll team remaps columns every cycle, earnings codes don't match, and retro corrections vanish.
Run a parallel pay period. Give the vendor one real period of punches for 20 to 50 employees. Have them push it into your payroll system, whether a global provider or a local engine, then reconcile against what you actually paid. Ask whether the integration is a maintained API connector or a file template, who fixes it when payroll changes its format, and how a timesheet edited after approval shows up in the next run. Any variance you can't explain is a reason to stop.
Red Flags: Silent Edits and Vague Answers on Where Data Lives
Ask a manager in the demo to change a punch, then pull up the record. If it doesn't show the original time, who changed it, when, and why, that's a compliance gap. In 2019 the EU's top court held that member states must require employers to keep an objective, reliable and accessible system for recording daily working time, and national rules have followed. Brazil's electronic time-recording regulations set technical standards for recording systems. In many countries, labor inspectors will ask for exactly this trail.
The tenth flag is a hand-wave about hosting. "It's in the cloud" tells you nothing. Ask for hosting regions, the sub-processor list, how cross-border transfers are handled, and retention settings per country. Some countries, including India and Saudi Arabia, and parts of the EU public sector, apply localization or transfer rules that can rule a vendor out.
Red Flag: A Per-Employee Price That Hides Everything Else
A low per-employee-per-month headline often leaves out terminals, integrations and multi-country setup. Get a three-year total cost of ownership in writing. Typical 2026 market ranges are below; they vary by contract, region and headcount, so confirm with each vendor.
| Cost line | Typical 2026 range (USD) | What drives it up |
|---|---|---|
| Time and attendance only | $2–$8 per employee per month | Multiple pay rules, minimum seat counts |
| Full workforce management software (scheduling, forecasting) | $6–$15 per employee per month | Demand forecasting, labor budgeting modules |
| Biometric or badge terminals | $300–$1,500 per unit | Outdoor-rated hardware, face recognition, local support |
| Implementation | $0–$5,000 single site; $10,000–$50,000+ multi-country | Custom rules, payroll connectors, data migration |
Hypothetical example: a 120-person company across three sites pays $5 per employee per month ($21,600 over 36 months), buys six terminals at $800 each ($4,800) and pays $8,000 for setup. That's about $34,400 over three years, and roughly a third of it isn't subscription. Your next step: turn the tests above into a scorecard, send it to your shortlist, and drop any vendor that fails the parallel payroll run or the biometric review. No discount makes up for either.
Quick answers
Should a small company use biometric time clocks at all?
Often not. For a team under about 50 people, PIN, badge or geofenced mobile clock-ins usually stop most buddy punching without the legal exposure of biometrics. If you do choose biometrics, use on-device template storage plus an alternative method, and get a data-protection professional to review it in each country first.
How long should a time and attendance software trial last?
Long enough to cover at least one full pay cycle, plus a period that includes a public holiday or a shift-pattern change. For most companies that's four to six weeks. A two-week trial on sample data rarely surfaces export or overtime problems.
Can one system handle overtime rules for several countries?
Many international platforms can, but quality varies a lot. Check that rules are set per legal entity or location, carry effective dates, and can be edited by your admins. Have a local payroll or employment advisor confirm the rule set for each country before go-live.
Written by the Poolgrid HQ editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.