Skip to main content
Devices · Payroll

ZKTeco payroll integration for companies in Pakistan

A ZKTeco unit on the gate already knows who arrived. StreamHCM takes those punches into attendance and then into payroll, so the month is not retyped from a USB file.

Quick answer

StreamHCM lists native support for ZKTeco, eSSL, Suprema and Fingertec. The device records the punch. Attendance applies grace, late and shift rules. Payroll uses that result for the wage. Punches sync to cloud attendance, and a device can store them locally if the link drops. This page does not publish ports, an SDK, or a method name such as ADMS.

StreamHCM
StreamHCM HR & Payroll Team

Written and reviewed by the StreamHCM HR & Payroll Team. Last updated 15 November 2026.

The brand list is the one on HR integrations. What the punch becomes is the attendance module and the biometric attendance system. The pay run can be tried in the payroll calculator. Shift rules are shift scheduling software.

How do ZKTeco punches reach payroll?

The failure this page is about is the gap after the terminal. Someone exports the day, someone else pastes it into Excel, and payroll starts later. Connecting the terminal removes that paste. Exceptions stay visible. Ordinary days do not need a second register. These four steps are the path the site already states. They are not a wiring diagram.

  1. The person uses the ZKTeco, eSSL, Suprema or Fingertec unit already on the gate.
  2. The punch lands on the attendance record. Grace, late and the shift are applied there.
  3. A missing punch or unapproved overtime stays visible for a manager. Ordinary days are not retyped.
  4. The pay run reads that attendance for the wage, then applies FBR tax and EOBI.

This page does not publish device IPs, ports or a private SDK. Bring the model you own to the trial. The site names the four brands, not every firmware version.

How do you connect a ZKTeco machine to payroll software?

ZKTeco integrations, in general, move punches in three ways. The table labels those ways as industry practice, not as a StreamHCM setting. This site states that punches sync into cloud attendance, and a device can store them when the link drops and send them later. It does not name ADMS, a LAN SDK or USB as the product's method.

How ZKTeco integrations generally move punches
General methodHow it usually worksWhat StreamHCM's site states
Cloud push, sometimes called ADMSThe device sends punches to a server when it is online.Punches sync to cloud attendance. The site does not use the name ADMS.
LAN pull via an SDKSoftware on the office network asks the device for new punches.Not stated. This page does not publish an SDK, a port or an IP.
USB or CSV exportSomeone copies a file off the device and pastes it into payroll.Described as the gap to remove, not as StreamHCM's method.

How are device user IDs matched to employees?

Payroll can only pay a punch it can attach to one person. On the device, that person is whoever was enrolled. In the HR system, that person is one employee record. The biometric page says you enrol employees on the device. This site does not name a field for the device user ID, so this page will not invent one.

  • One employee record, not a second code created because the person moved branch.
  • One enrolment on the device for that same person.
  • A leaver removed from the device when they leave the employee record.
  • A new joiner enrolled before you expect their first day in the pay run.

What should you test before the first live payroll?

Run these checks on a real week before the pay run is the one you bank. They are a test list, not a claim that the device configures itself. A night shift that crosses midnight stays one attendance day, which is how StreamHCM's shift type works. Approved leave and a public holiday must not be paid as absence.

The overtime guide is the note on factory overtime. Overtime still waits for approval before it is paid.

  • One device identity per employee, and no duplicate enrolment.
  • The device clock, against the time you expect the shift to use.
  • A missing out-punch, and where that exception shows before lock.
  • A night shift that crosses midnight, still one day.
  • A leave day, so approved leave is not marked absent.
  • A public holiday on that branch's calendar.
  • A power cut: punches stored on the device, then synced when power and the link return.

Why are punches missing from payroll?

A missing punch is an exception, not a reason to rebuild the month in Excel. Check the person, the device and the shift before you type a time. If the device was offline, it can store punches and sync when the connection returns. Lock payroll only after that sync.

Why a punch can be missing from payroll
What you seeWhat to check
The day is blank in attendanceThe person is enrolled once, on the device that they actually used.
The device has the punch, payroll does notThe punch was left on a USB export, or the device has not synced yet.
In-punch onlyThe out-punch is missing. Miss-punch rules should keep the gap visible.
The night shift split in twoThe shift must cross midnight as one attendance day. See shift scheduling.
A leave day looks absentThe leave was approved on the same record attendance reads.
The day vanished after a power cutWait for the device to sync. Do not lock payroll on an empty day.

A company with a Karachi gate and a Lahore gate can keep a terminal at each site. Punches still land on the employee's attendance, and the branch is the one already on the employee record. How a shift is entered is how to set up a shift.

Sources

FAQ

ZKTeco and payroll questions

Yes. The integrations module lists native support for ZKTeco, alongside eSSL, Suprema and Fingertec. Punches from the device go into attendance. Payroll reads that attendance. This page does not publish device IPs, ports or a private SDK guide.

No. ZKTeco is the attendance device. Payroll is StreamHCM's pay run: gross, FBR tax, EOBI and the other lines. The integration's job is to stop someone retyping the register before payday.

In general, devices are connected by a cloud push, by software that pulls punches over the local network, or by a USB or CSV file someone exports. StreamHCM's published description is that punches sync into cloud attendance, and a device can store punches and sync later. This page does not name ADMS, a port or an SDK as the method.

Each person needs one identity on the device and one employee record. The biometric page says you enrol employees on the device. This site does not publish the field StreamHCM uses to store a device user ID. Before payroll, check that one person is not enrolled twice and that a leaver is not still on the device.

Send the device punches into the same attendance record payroll uses, and hold exceptions (a missing punch, an unapproved overtime hour) for a manager instead of a fresh spreadsheet. That is the point of connecting the ZKTeco unit to the pay run.

Yes. A missing punch or an unapproved overtime hour should be visible before the pay run is locked. Monitoring every ordinary day, line by line, is the work the integration is meant to remove.

Usually the punch never reached the attendance record, the person is not the same identity on the device and in the HR system, the shift is missing, or the month was locked before a correction. An offline device can still hold punches and sync when the link returns. A USB file that nobody imported is not in payroll.

Tell us the model during the trial. The site names the brands, not every firmware version. We confirm the unit you already own before you commit.

Connect one device before you connect the site

14-day trial. No card on this site. Tell us the model on the gate and we confirm it against the brands this page names.