Comprehensive attendance software for ZKTeco devices: what actually connects, and what's sold as integration.

Walk into any small Indian shop or factory with a biometric door reader and there's a 70%+ chance it's a ZKTeco — K40, F18, F22, MB360, MB10. The brand is everywhere (psst — even most eSSL devices are rebranded ZKTeco). The cloud software story, however, is a mess.

Owners get sold "ZKTeco integration" by so-called "Attendance Management" vendors that, in practice, means "you USB-export attendance once a month and email it to us." That isn't integration. That's email.

I'm going to walk through what comprehensive attendance software for ZKTeco devices actually has to do — handle real-time punch capture, multi-device sync, payroll, and Shop & Establishment Act–ready reports. And I'll list the Indian attendance software providers that actually do it.

Key takeaways

What "comprehensive integration" actually means

Comprehensive attendance software for ZKTeco devices is software that pulls real-time punch data from one or more ZKTeco biometric machines via the ADMS push protocol (or SDK pull), deduplicates and reconciles employee records, handles offline buffering, and feeds the data into payroll and statutory compliance reports — without a USB drive, a vendor visit, or a Windows PC running ZKTime in the back office.

That definition rules out five things commonly sold as "integration":

• Manual USB export (the default ZKTime workflow)
• One-machine-at-a-time integration only
• Read-only sync with no two-way employee provisioning
• Static-IP / same-network requirement to reach the device
• Attendance-only outputs with no payroll or Shop Act register

That isn't integration. That's email.

If your shortlisted attendance software does any of those, it isn't comprehensive — it's just a viewer.

The 3 ways biometric data reaches the cloud

There are exactly three connection methods. Knowing which one a vendor uses tells you everything.

1. ADMS / Push protocol. ZKTeco's own protocol pushes punch logs to a configured cloud URL the moment a punch happens. Set it up once on the device (Menu → Comm → ADMS / Cloud Server) and every punch flows in real time. Works behind NAT (Network Address Translation, if you're not a geek like me). No public IP needed. This is the right fit for 95% of small businesses.

2. SDK / pull integration. The software vendor's server polls the device on schedule via ZKTeco's SDK (Windows or Linux libraries). Higher friction — needs a static IP and open ports — but gives two-way sync, so you can provision a new employee in the cloud and have the fingerprint template flow down to the device.

3. Manual export (USB / ZKTime). ZKTeco's own desktop software workflow. Plug in a USB, copy the day's logs, import. Don't accept this in 2026.

ZKTeco ADMS vs SDK: the technical difference, in plain words

Most shop owners hear "ADMS" or "SDK" thrown around by vendors and nod politely without knowing what either means. Here's the plain-English version.

ADMS (Automatic Data Master System) is a push protocol. Think of the device as the one making the phone call. You give it a number to dial — the cloud server URL — and the moment someone punches in, the device dials out and delivers the punch. The cloud doesn't need to know where the device is. It doesn't need to be able to reach it. Punches work over any home router, a mobile hotspot, even office WiFi behind a firewall. As long as the device can get to the internet, it can get to the cloud.

The SDK is a pull protocol. Now the cloud server is the one making the call. It dials into the device, reads its memory, hangs up. For that to work the device has to have a public address the server can find — a static IP, a port-forwarded router, or a VPN. The SDK can do more powerful things, like provisioning fingerprint templates from the cloud and clearing logs remotely. But for a shop owner with one biometric machine and a domestic Jio Fiber connection, the SDK is overkill that breaks every time the router restarts.

If the onboarding asks for port forwarding, it's SDK. If it asks for a server URL, it's ADMS.

The simple test: if a vendor's onboarding instructions ask you to "set up port forwarding on your router" or "give us a static IP," they're using SDK. If they ask you to "set the server URL on the device," they're using ADMS. Pick ADMS unless you have an explicit reason not to. For the network-level mechanics of getting any biometric device talking to a PC or cloud in the first place, my guide on how to connect a biometric device to your computer walks through the cable, IP, and subnet setup step by step.

The 8 features that make integration comprehensive

1. Multi-device, multi-location sync. Three K40s across two outlets feeding one dashboard.
2. Offline buffering. Internet drops? The device stores up to 80,000 transactions and syncs when back online.
3. Two-way employee provisioning. Add staff in the cloud; fingerprint template flows down to the device.
4. De-duplication and reconciliation. Same fingerprint punched twice in 30 seconds collapses to one valid punch.
5. Payroll calculation engine. The most important bit — attendance data is available; combine it with basic salary structure and a few rules and you get net pay, EPF, ESI, Professional Tax, TDS, payslips — all auto-derived from punches.
6. Shop & Establishment Act register export. State-prescribed format for Maharashtra, Karnataka, Tamil Nadu on demand.
7. Geofence + selfie fallback for staff away from the device. Drivers, field merchandisers, multi-outlet floaters. Nice-to-have, not mandatory.
8. Audit trail. Every edited or manually adjusted punch logged with who, when, and why. Non-negotiable for inspection defence.

If a vendor's demo only shows you 1–4 of these, it isn't built for Indian SMB compliance. It's a global tool retro-fitted.

ZKTeco device compatibility: what plays nicely with cloud

If you're buying new in 2026, confirm ADMS is enabled in firmware. Older units sometimes ship with it disabled and need a firmware update before they'll talk to your cloud.

Setup walkthrough for K40 → cloud sync

The K40 is the most common Indian SMB device, so I'll use it as the example. The same logic applies to F18, MB360, IN01-A.

1. On the device: Menu → Comm → Ethernet → DHCP On (or set a static IP if your network requires one).
2. Confirm internet reachability: Menu → Comm → ADMS → Server URL and Server Port.
3. In your SaaS dashboard, get the ADMS server URL specific to your account (e.g., adms.rotabook.com on port 80 or 443).
4. Paste into the device. Set Enable Domain Name = Yes.
5. Punch once. Within 30 seconds the punch should appear in the cloud dashboard.
6. Repeat for each device. Tag each with its outlet name in cloud admin so multi-store reports work.

That's it. No port forwarding, no VPN, no Windows machine running ZKTime in the back office.

Rotabook vs ClockIt vs SalaryBox vs Truein: how Indian vendors compare

Five Indian-market tools claim "comprehensive ZKTeco integration." Here's how they actually compare on the features that matter for a small Indian shop.

Pick by use case. If you're an Indian retail or service SMB with 3–50 staff across one or two outlets, Rotabook and SalaryBox are the closest fit. ClockIt is solid technically but priced and built for a global audience. Truein leans toward larger multi-site organisations where contract workers and facial recognition dominate.

Here's the one-line read on each, in case you're shortlisting — honest, no puffery:

• Rotabook — built for Indian retail and SMB, including niche use cases. ADMS push supports K40, F18, MB360, eSSL and more. Shop Act registers + payroll + daily expense management + stock tracker built in. 15-minute setup.
• ClockIt — global, well-documented ADMS support, integration guides for most ZKTeco models. Pricing in USD. Strong technical fit, weaker on Indian payroll compliance.
• SalaryBox — Indian-first. Supports K40 and most ZKTeco devices via ADMS. Strong on payroll; multi-device admin UX feels dated.
• Truein — face recognition + geofence + ZKTeco ingestion. Pricier. Built for contract / multi-site teams.
• Kredily — free tier covers basic ZKTeco sync. Payroll solid for small teams.

ZKTeco payroll integration: from punch to payslip

Pulling punches is the start. The part nobody talks about is what happens between a fingerprint scan at 9:47 AM and a payslip on the 5th of next month.

Here's the chain. Latha, the saree-shop assistant from my overtime guide, punches in at 9:47 AM. Her device fires the punch to the cloud over ADMS. The software pairs that morning IN with her evening OUT later in the day, computes the hours against your shop's standard 8 or 9 (depending on state), and flags anything over the threshold as overtime at twice the ordinary rate. At month-end, the same engine subtracts EPF, ESI, Professional Tax and TDS from gross, generates Latha's payslip, and updates the Shop & Establishment Act register in the background. No spreadsheet. No manual re-keying.

If your software only shows punches and stops there, the rest happens in Tally or Excel on the 3rd of the month, with errors. The full workflow is what real-time attendance tracking with ZKTeco is supposed to deliver. For the overtime math itself, how to calculate overtime for shop staff in India walks through the formula and the state-by-state divisor question.

Where Rotabook fits

I built Rotabook because every other "ZKTeco-integrated" software I tested either needed a Windows machine running in the back office or quietly fell back to USB exports. Rotabook does ADMS push only.

For broader buying context, see my attendance system for small retail shops in India guide and the textile shop management software post — same integration story, different vertical angles.