The short answer
A ZKTeco machine cannot talk to payroll software directly. It only records punches (a user number and a time). Something in the middle has to turn those punches into payable attendance — apply shifts, grace minutes, holidays and leave — and then hand the result to payroll. That middle step is attendance software. The rest of this guide is about doing that step well.
What payroll actually needs from attendance
Raw punches are almost useless to payroll on their own. Before you connect anything, agree on which numbers payroll will receive for each employee and each month:
| Number | Why payroll needs it |
|---|---|
| Employee code | To match the person in attendance with the person in payroll. Must be the same in both. |
| Days present | The base for monthly or daily pay. |
| Days absent (unpaid) | For deductions — only days that are not leave, holiday or a weekly day off. |
| Paid leave and unpaid leave days | Paid leave is not a deduction; unpaid leave is. They must not be mixed with absence. |
| Half days | Usually paid at half — your half-day rule decides when a short day counts as one. |
| Late minutes | If your policy deducts for lateness, after the grace minutes. |
| Overtime minutes | For overtime pay, after the shift ends. |
Notice that every one of these depends on rules — the shift, the grace period, the holiday list, approved leave. That is why the rules belong in one place: the attendance system. Payroll should receive finished numbers, not punches.
Three ways to move attendance into payroll
1. Export a file from desktop software
The classic setup: a Windows program such as eTimeTrackLite or ZKTime.Net pulls punches from the machine over the office network, you export a report to Excel, then import or retype it into payroll.
- Good: no extra cost if you already have it.
- Weak: the office PC must be on, every branch needs its own copy, and someone has to remember to download before payroll. One forgotten branch means wrong salaries.
2. A monthly register from an attendance server
The machines push every punch to a server as it happens (ADMS push mode), so all branches are always in one place. At month end you open the monthly register, check it, and export it as CSV — which opens in Excel and imports into almost any payroll system.
- Good: nothing to download, all branches together, and the register already applies shifts, leave and holidays.
- Weak: still one manual export and import each month.
3. Connect payroll with an API
If your payroll is your own software, or supports imports by API, it can fetch the worked-out days itself. This removes the monthly file completely. The details — endpoints, keys and webhooks — are in ZKTeco attendance API: send punches to payroll.
- Good: no files, no copying, can run every night or on payroll day.
- Weak: someone has to write the small piece of code on the payroll side.
| Desktop export | Monthly register (CSV) | API | |
|---|---|---|---|
| Office PC needed | Yes | No | No |
| All branches in one place | No | Yes | Yes |
| Manual steps each month | Download, export, import | Export, import | None |
| Needs a developer | No | No | A little |
| Best for | One small office | Most businesses | Own payroll software |
A clean monthly payroll run, step by step
- Pick a cut-off date and keep it every month — for example the last day of the month, or the 25th if salaries go out on the 1st.
- Check machines are online the day before cut-off. A machine that lost its connection still keeps punches and sends them when it is back, but only if it gets back online before you export.
- Enter all approved leave for the month. Leave that is not entered shows as absence and gets deducted.
- Check the month's holidays are in the holiday list, so nobody is marked absent on a public holiday.
- Look for missing punches. Someone with a first-in but no last-out usually forgot to punch out — fix it with the manager before export, not after the salary is paid.
- Export the monthly register (or let payroll pull it by API).
- Import into payroll, then compare totals: number of employees and total overtime hours should match what the register showed.
- Run payroll and make the payslips. If you do not have payroll software yet, the free payslip generator makes a clean PDF payslip per employee.
Match employee codes first — the mistake that breaks everything
On the machine every person is a user number (sometimes called user ID, enroll number or PIN). In payroll they are an employee code. If these are different, every import needs a lookup table, and one typo pays the wrong person.
The simple rule: use the payroll employee code as the user number on the machine. Enrol new people with that number from day one. If your machines already use other numbers, set the employee code in the attendance system once and let it do the matching.
Problems that cause wrong salaries
Night shifts across midnight
Someone works 22:00 to 06:00. A system that thinks in calendar days sees two half days. The attendance system needs proper night-shift support so the whole shift counts on the day it started.
Wrong machine clock
The machine stamps each punch with its own clock. A clock ten minutes fast turns punctual people into late ones. Check Menu → System → Date/Time on every machine, especially after a power cut.
Double punches
People often punch twice to be sure. Good attendance software uses the first punch in and the last punch out and ignores the rest; check yours does before you trust overtime totals.
Leave counted as absence
If leave lives in a spreadsheet and attendance in another system, payroll sees an absence. Keep leave in the attendance system so the day shows as "on leave", paid or unpaid, before payroll gets it.
New joiners and leavers
Someone who joined on the 15th is not absent for the first 14 days. Set joining and leaving dates so those days are not counted as absences.
An example: turning attendance into pay
Payroll formulas are set by your company and local labour law, so treat this only as an illustration of how the numbers fit together. Say a monthly salary of 30,000 for a 30-day month, and attendance shows 2 unpaid absent days and 6 hours of overtime paid at 1.5×:
| Item | Calculation | Amount |
|---|---|---|
| Daily rate | 30,000 ÷ 30 | 1,000 |
| Absence deduction | 2 × 1,000 | −2,000 |
| Hourly rate (8-hour day) | 1,000 ÷ 8 | 125 |
| Overtime | 6 × 125 × 1.5 | +1,125 |
| Pay | 30,000 − 2,000 + 1,125 | 29,125 |
Attendance software supplies the 2 days and the 6 hours. Payroll owns the rates and the formula. Keeping that line clear makes both systems easier to check.
Frequently asked questions
Can a ZKTeco machine connect directly to payroll software?
No. The machine only stores punches — a user number and a time. Attendance software has to turn those punches into worked days, late minutes, overtime and leave first; payroll then receives those finished numbers by file or by API.
Do I need eTimeTrackLite or ZKTime.Net for payroll?
No. Those desktop programs are one way to get attendance off the machine, but they need an office PC that stays on and a separate copy per branch. A cloud attendance server receives punches from every branch directly and exports the same monthly data.
What file format should I export for payroll?
CSV is the safest choice. It opens in Excel and almost every payroll system can import it. Agree the columns with payroll once — employee code, days present, absent days, leave days, late minutes and overtime minutes — and keep them the same every month.
How are night shifts handled for payroll?
The attendance system must support shifts that cross midnight, so a 22:00 to 06:00 shift counts as one working day on the date it started. Without that, the shift is split into two short days and both payroll and overtime come out wrong.
Does PunchSync calculate salaries?
No. PunchSync is the attendance side: it receives punches from ZKTeco and eSSL machines, applies shifts, grace minutes, leave and holidays, and gives you daily and monthly attendance with late and overtime minutes as CSV, PDF or through its REST API. Your payroll software calculates the pay.