eSSL eTimeTrackLite vs ClockIt

Written for people already running eTimeTrackLite on a PC in the office. Your eSSL terminals stay exactly where they are — this is a software change, not a hardware one.

Start free — no card

Switching takes one settings change on the terminal. No re-enrolment, no new hardware, no local server.

Your eSSL devices already work with ClockIt

eTimeTrackLite talks to your terminals over ADMS — eSSL's push protocol. So does ClockIt. That means the switch is one field on the device: change the server address from your local install to ClockIt's, and punches start arriving in the cloud instead.

Nobody re-enrols a fingerprint or a face. Biometric templates live on the terminal, not in eTimeTrackLite, and changing where it pushes does not touch them.

What eTimeTrackLite is

eTimeTrackLite is eSSL's own time and attendance software, bundled with its biometric terminals and distributed through its dealer network in India. You download it and install it on a Windows machine, where it keeps a local database and acts as the server your eSSL devices push their punches to. A web edition exists, but it is still an install on your own machine rather than a hosted service. A lite version ships free with the hardware, with paid editions and per-device licensing handled through resellers.

This guide covers:

eTimeTrackLite 10eTimeTrackLite 11eTimeTrackLite 12eTimeTrackLite Web

Why teams move off eTimeTrackLite

It is one PC away from being your single point of failure

The install, the database and the punch history all live on one Windows machine in the office. When that machine is off, reimaged, upgraded or simply retired by someone who did not know what was on it, the attendance system goes with it. This is by far the most common reason teams start looking.

Dealer-mediated licences and versions

Upgrades, licence keys and per-device activation typically run through whichever reseller supplied the hardware. That is fine until you change supplier, open a branch in another city, or need an answer on a Sunday before payroll closes.

Nothing outside the office is covered

The software is built around the terminal on the wall. Site staff, field engineers, drivers and anyone working across locations are not in it, so they live on a parallel spreadsheet that has to be merged by hand every month.

Each branch tends to become its own island

Multi-branch operators commonly end up with one install per branch and no single view. Consolidating for payroll means collecting reports from each site and reconciling them manually — the exact task that quietly consumes the last two days of every month.

eTimeTrackLite and ClockIt side by side

Compared on structure — where the software runs, what it covers and how it is licensed. We do not quote eSSL prices or licence terms here, because those vary by reseller and edition and we cannot verify them for your account.

 eTimeTrackLiteClockIt
Where it runsDownloaded and installed on a Windows PCCloud — nothing to install or keep running
Where your data livesA local database on that machineHosted, backed up, reachable from anywhere
Your eSSL terminalsPush punches to your local install over ADMSPush punches to ClockIt over the same ADMS protocol
Re-enrolment on switchingNone — templates stay on the device
AI Face range supportSupportedSupported — all nine AI Face models
Access from outside the officeVPN, port forwarding or an exposed serverAny browser, plus iOS and Android apps
Staff without a terminalNot covered by the device softwareMobile, GPS and web clock-in on the same account
Multi-branchCommonly one install per branch, merged manuallyEvery branch in one account
Shift schedulingShift and roster assignmentScheduling with publishing, swaps and coverage
Leave and time offLeave module in the paid editionsBuilt in, with accruals and approvals
Timesheet approvalsHandled outside the attendance softwareBuilt in, with an audit trail
Job or cost codes on the punchKeyed at the terminal, costed to Projects and Tasks
Payroll exportsAttendance reports to re-keyPayroll-ready exports and API
Licence modelFree lite edition, paid editions via resellers$2.99 per employee per month, free plan available
Access control (doors)Available in the wider eSSL suiteNot offered — see below

What ClockIt does not replace

ClockIt is a workforce management product, not an access-control or facilities system. If your eSSL setup is also handling door access, visitor management or canteen deduction, ClockIt does not take those over. Many sites run both — the terminal keeps doing door control through eSSL's own software while ClockIt takes attendance, scheduling and payroll. Worth checking before you plan a cutover, because those modules are often licensed as one package.

Your eSSL terminals stay

Every one of these connects to ClockIt over ADMS. Pick your model for the exact menu path, or see the full eSSL device list.

How to switch

  1. 1

    Export your punch history first

    Pull your attendance history out of the existing software as CSV or Excel before you change anything. The data lives in a database on your own PC or server, and the export is trivial while the system is running — much less so after a machine is retired or a licence lapses. Keep it regardless of whether you import it; payroll audits reach back years.

  2. 2

    Create your ClockIt account

    Free to start, no card. Add your employees, set your pay period, and rebuild your shift and overtime rules. If you are coming off a system that has been running for years, this is the moment to fix the rules that were always slightly wrong rather than port them across unchanged.

  3. 3

    Repoint the device at ClockIt

    On the terminal, go to Menu → Comm → ADMS / Cloud Server and change the server address to ClockIt's. That is the entire switch. You are changing which server the device pushes to — you are not reflashing, resetting or re-enrolling anything.

  4. 4

    Map device user IDs to ClockIt employees

    Each terminal already stores an enrolment number against every fingerprint or face. You match those IDs to your ClockIt employee records once. Biometric templates never leave the device, so nobody re-enrols.

  5. 5

    Reconcile one full pay period

    Run a complete pay period in ClockIt and reconcile it against the last period from your old system before you decommission the old server. Note that the terminal pushes to one server at a time, so this is a sequential check against your exported history rather than two systems running side by side.

Implementing ClockIt's biometric kiosks eliminated buddy punching overnight. The facial recognition is instant and works perfectly even in our warehouse environment. It's the most secure time tracking decision we've made.

James Wilson
Plant Manager, Apex Manufacturing

eTimeTrackLite to ClockIt: common questions

Will my eSSL devices work with ClockIt, or do I need new hardware?
They work. ClockIt speaks ADMS — the same push protocol eTimeTrackLite uses — so any eSSL terminal with a Cloud Server or ADMS option in its menu can push to ClockIt instead. That covers the K990, X990, F22, MB160, uFace 302, iFace 102 and K30 Pro, and the complete AI Face range: Viktor, Arion, Jupiter, Mars, Eris, Magnum, Neptune, Mercury and Uranus. You are changing a server address, not buying hardware.
Do employees have to re-enrol their fingerprints or faces?
No. Biometric templates are stored on the terminal itself, not in eTimeTrackLite, and changing the server address does not touch them. You map each device enrolment ID to a ClockIt employee once and every existing enrolment keeps working.
Can I run eTimeTrackLite and ClockIt at the same time?
Not on the same terminal. An ADMS device pushes to one server address at a time, so pointing it at ClockIt means it stops pushing to eTimeTrackLite. For a genuine parallel trial, point one terminal at ClockIt and leave the rest where they are, or export your history and reconcile a full pay period after switching. We would rather say so now than have you find out mid-cutover.
What happens to the attendance history already in eTimeTrackLite?
It stays in the local database on your machine and it is yours. Export it to Excel or CSV while the install is still running and keep the file — reaching that database after the PC has been reimaged or retired is genuinely hard, and this is the step people most often skip.
eTimeTrackLite is free with the device. Why pay for ClockIt?
Because the free edition is doing a smaller job. It captures punches from the terminal onto one PC. It does not cover the staff who never touch that terminal, it does not put your branches in one view, and it does not carry leave, approvals and payroll-ready output. If a single site with a single clock and one person doing payroll works for you, the free edition is a reasonable answer and we will not pretend otherwise. The cost case for ClockIt is the manual consolidation and re-keying it removes, not the software licence.
Do I need a static IP or port forwarding?
No. ADMS is push-based: the terminal opens the connection outward to ClockIt, so it works on ordinary broadband or 4G with no static IP, no port forwarding and no inbound firewall rules.
Does ClockIt work with the eSSL AI Face terminals?
Yes, all nine. The AI Face range is eSSL's badge on the same ZKTeco SpeedFace platform, so it uses the identical ADMS push protocol. Viktor, Arion, Jupiter, Mars, Eris, Magnum, Neptune, Mercury and Uranus each have a setup guide on the eSSL device hub.
Can employees enter a job or cost code at the terminal?
Yes. eSSL terminals with a keypad can take a job, project or cost code as part of the punch. The code travels to ClockIt with the punch and resolves to the matching Project or Task, so hours are costed to the right job without a paper job sheet.

Running different software?

Keep the hardware. Lose the server.

Point one eSSL terminal at ClockIt and see a full day of punches arrive before you decide anything. Free to start, no card.

Start free — no card