Connecting a ZKTeco fingerprint device to payroll: complete guide
A fingerprint device only saves time when its punches reach payroll without a USB stick. This guide covers the three ways to connect a ZKTeco device, the setup steps from network settings to month close, and the problems you are most likely to meet.
Most companies in Jordan already have a ZKTeco fingerprint or face device at the door. The device records punches well. The work starts afterwards: getting those punches off the device, matching them to employees and shifts, turning them into lateness and overtime, and closing the payroll month without retyping anything.
This guide walks through that chain end to end. It uses Aspirations as the example because that is the system we know, but the questions apply to any fingerprint attendance system. Menu names differ slightly between models and firmware versions, so treat the paths below as typical, not exact.
Three ways punches can leave the device
- Cloud push (ADMS): the device itself sends punches to a server over the internet. On ZKTeco devices this is the Cloud Server Setting, and it works with firmware that supports ADMS (Push 2.x). Punches arrive in real time.
- Local bridge: a small program on an office PC reads devices on the local network over the ZK protocol (port 4370) every 2 minutes and uploads over HTTPS with a site token. It is read-only and never clears the device. This suits older devices without ADMS, or networks that block outbound traffic from devices.
- File import: upload the 1_attlog.dat file from a USB stick, or a CSV or Excel export from ZKTime or ZKBioTime. Errors are previewed and the file is saved all or nothing. This suits historical data or a branch with no network.
You can mix them: head office on cloud push, a warehouse through the bridge, last year's records by file. Duplicates are removed, so a punch that arrives through two routes is counted once.
Which devices work
Aspirations is designed for ZKTeco devices whose firmware supports ADMS, for example K40 and K50 Pro, MB160, MB360 and MB460, SpeedFace-V5L, ProFace X, iClock, uFace and SilkBio, and for ZK-compatible devices such as Granding, ESSL, Timmy and Anviz in ZK mode. Devices on newer Push 3.x firmware connect through their legacy ADMS mode or through the local bridge. Firmware differs between batches, so we confirm your exact model and firmware during setup, before you rely on it.
Step 1: device network settings
Before anything else, the device needs a working network connection. On the device, open Menu, then Comm., then Ethernet (or Network). Give it a fixed IP address on your office network, or make sure your router always gives it the same address, and set the gateway and DNS so it can reach the internet. For the local bridge, the PC running it must be on the same network and able to reach the device on port 4370.
Step 2: add the device and set the ADMS server
- In Aspirations, add the device with its serial number, found under the device's system information, and choose its branch and work location.
- On the device, go to Menu, then Comm., then Cloud Server Setting.
- Choose ADMS as the server mode and enter the server address and port we give you.
- Restart the device. Its status turns online in the devices screen and new punches start to appear.
On its first connection, a device usually sends the punches already stored in its memory. Punches already received through another route are skipped as duplicates.
Step 3: map device user IDs to employee numbers
The device knows people only by a user number (PIN). Fingerprint and face templates never leave the device; the system receives only the user number and the time. Each PIN must therefore match an employee:
- The device PIN is matched to the employee number automatically, including simple variations such as leading zeros.
- Any punch without a match waits on a screen where HR assigns it to the right employee. Earlier punches from that PIN are then attributed and the days recalculated.
- Optionally, send employee names and numbers to ADMS devices, so new staff do not need to be typed on each device.
The simplest rule is to use the employee number as the device PIN everywhere, on every device in every branch.
Step 4: shifts, rosters and grace
A punch only means something when it is compared with the shift the employee was supposed to work. Build shift templates with a start, an end, a break and a grace period (10 minutes by default), then weekly rosters from those templates. Night shifts that end the next morning are counted as one working day. Weekend days are set per company; the default is Friday and Saturday.
Choose how punches pair up: first and last punch of the day, or in/out pairs for split shifts and breaks. Repeat punches within 2 minutes are ignored.
Step 5: lateness, early leave and overtime rules
- Lateness is the time between the shift start and the check-in, beyond the grace period.
- Early leave is the time between the check-out and the shift end, beyond the grace period.
- Overtime is the time worked after the shift end once it exceeds the grace period. Work on a rest day counts as overtime.
- Absence is a scheduled day with no punch and no approved leave. It is flagged for HR, not deducted automatically.
Jordan's Labour Law sets overtime at no less than 125% of normal pay on working days and 150% on weekly rest days and holidays. The default multiplier in payroll is 1.25 and HR can edit it. To check an amount, use the overtime calculator, and see our guide to overtime and public-holiday pay in Jordan for the hourly-rate conventions.
Step 6: corrections workflow
Forgotten punches happen. An employee who forgot to punch requests a correction from self-service, with the time and a reason. HR approves it, optionally through your approval rules, and nobody can approve their own request. When HR edits attendance directly, a reason is required and the change history is kept. Field staff can check in from their phone browser with a geofence, which complements devices rather than replacing them.
Step 7: close the payroll month
- Review the board for missing punches and unmatched PINs, and clear them.
- Apply the month: lateness, early-leave and overtime minutes are written to payroll input.
- Review the input in payroll, decide any absence deductions, and approve.
Once payroll for a month is approved, that month's attendance is locked, so a late recalculation does not quietly change salaries that have already been paid.
Troubleshooting
Wrong times or punches on the wrong day
The device sends its local time without a time zone, so its clock must be right. Set the date, time and time zone on the device, and set the device's time zone in the system if it differs from the company's. A punch dated before 2015, which usually means a clock that was never set, is rejected. Check the clock again after a power cut.
Duplicate punches
Employees often punch twice to be sure. Repeat punches within 2 minutes are ignored, and the same punch arriving through two routes, or the same file uploaded twice, is skipped. If you still see odd pairs, check whether the pairing rule (first and last, or in/out pairs) matches how the shift works.
Device offline
A device on cloud push stores its logs when the internet drops and resends them when it reconnects. If a device has been silent for more than 30 minutes (configurable), you get an alert. With the local bridge, missed records are read on the next cycle. If a device stays offline, check its network settings, the server address and port, and whether a firewall blocks it.
Punches that do not appear for one person
This is almost always an unmatched PIN: the employee was enrolled on the device with a different number. Assign it once from the unmatched screen, and the earlier punches follow.
If you are comparing systems before you connect anything, our checklist on how to choose payroll and HR software in Jordan covers what to ask about devices.
