How to connect an attendance machine to payroll software
Every attendance machine has to hand its punches to the software that pays people. There are four ways to do it. They differ in cost, in the effort they take every month and in how often payroll ends up wrong.
What actually has to move
A punch is small: a user ID, a date and time, a direction (in or out) and the terminal it came from. Payroll wants something different: hours per employee per day, with shifts, overtime and leave applied. Something has to turn the first into the second. In most setups the HR or payroll software does that work, as long as it receives every punch, once, with the right employee ID and the right time.
The four methods below are four ways of moving punches from the machine to that software.
1. Export a file and import it
Someone downloads punches from the machine (on a USB stick or through its desktop software), tidies them in Excel and imports the file into payroll. It costs nothing and works with any software that accepts an import.
It also depends entirely on one person, happens late (weekly or monthly), and introduces errors at every step: missed punches, duplicate rows, a column in the wrong date format. With several sites it is one file per site. Fine for one small office with monthly payroll; painful beyond that.
2. Use the machine maker's desktop software
Most terminal brands ship attendance software that runs on a PC, pulls punches from the machines over the local network, calculates reports and exports them for payroll. It is cheap and works without internet.
The PC must stay switched on and backed up, each site usually needs its own installation, and the last step is still an export and an import. When the PC fails, attendance history can go with it.
3. Have a custom integration built
A dealer or developer writes a program that reads punches from the machines (through the maker's SDK or database) and sends them to the HR system's API. It can be tailored exactly to your rules.
It is also tied to one brand, one firmware and one version of your HR software. When any of them changes, it breaks, and often only its author knows how to fix it. Ask who maintains it, and for how long, before paying for one.
4. Use a cloud gateway with ready-made integrations
The terminals send each punch over the internet to a cloud service, a biometric gateway, which delivers it to your HR or payroll software through a ready-made integration. It works across sites and brands, needs no PC, and retries failed deliveries instead of losing them.
It costs a yearly licence per terminal, needs an internet connection at each site (terminals buffer punches when it drops), and depends on the gateway supporting your software. Check that before anything else. Older machines that cannot send over the internet can still join through a small connector on site; see keeping the machines you have.
The four ways side by side
| Export and import | Maker's desktop software | Custom integration | Cloud gateway | |
|---|---|---|---|---|
| Setup cost | None | Low | High | Low to medium |
| Monthly effort | High | Medium | Low, until it breaks | Low |
| Punches reach payroll | Weekly or monthly | When someone exports | Near real time | Within about a minute |
| Several sites | One file per site | One PC per site | Possible, at extra cost | Built in |
| Mixed terminal brands | Yes, by hand | Usually one brand | Usually one brand | Yes |
| When something fails | Noticed at payroll | Noticed at payroll | Often silent | Retried and reported |
Before go-live: match the employee IDs
The single most common reason punches go missing in payroll is an ID mismatch: the terminal knows a person as user 1047, the HR system knows them as EMP-0193. Pick one ID scheme and set every terminal's user ID to the ID your HR software uses for that person (or the field it matches on, such as a badge ID or an employee number). Test with three people before you enrol everyone.
Punches or shifts?
Some software wants every punch and works out hours itself; examples are Zoho People, ERPNext, BambooHR and QuickBooks Time. Others want a finished shift or timesheet with a start and an end, such as Deputy and Business Central. When software wants shifts, something has to pair each check-in with its check-out. Two cases decide whether that pairing is good:
- Night shifts: a 22:00 to 06:00 shift should become one shift on the day it started, not two half days.
- Missing check-outs: a forgotten punch should leave a visible gap for a manager to fix, not a 40-hour shift.
A go-live checklist
- Match employee IDs on every terminal and in the HR software.
- Set every terminal's clock and time zone; a terminal running ten minutes slow shifts everyone's hours.
- Run the old method and the new one side by side for one pay period and compare totals per person.
- Check a night shift, a missed punch and a terminal that was offline for a while.
- Decide who fixes missed punches, and where: in the HR software, not on the terminal.
- Write down how a leaver is removed from every terminal.
Common problems and their causes
| What you see | Usual cause | Fix |
|---|---|---|
| Employee not found | Terminal user ID differs from the HR ID | Align IDs before go-live |
| Hours shifted by a fixed amount | Wrong time zone or terminal clock | Set the time zone; sync the clock |
| Two punches seconds apart | People punching twice to be sure | Let the software ignore repeats within a minute or two |
| Night shift split into two days | Pairing by calendar day | Pair within a shift boundary, book to the start day |
| Punches missing for a site | Terminal offline or unplugged | Use terminals that buffer and a service that reports gaps |
Connecting punches is what Cams does
Cams connects terminals of 90+ brands to 70+ HR, payroll, ERP and school systems through its cloud, with retries and a console that shows every delivery.