supported biometric TCP/IP
Connect network attendance hardware such as supported biometric deployments through LAN connectivity.
Home / Biometric attendance
BIOMETRIC ATTENDANCE
Connect supported biometric attendance devices to your HR workflow.
Flowwkkr uses a licensed Windows agent to synchronize biometric attendance records from supported biometric deployments into the HR workspace.
What Flowwkkr includes
Explore the product area in more detail and see how it fits into the wider Flowwkkr HR workspace.
Windows Agent
Use the commercial Flowwkkr Agent to synchronize attendance from the client environment.
Duplicate protection
Attendance ingestion is designed to avoid inserting the same punch repeatedly.
Check-in / check-out
Keep attendance events available for daily attendance processing.
Audited sync
Synchronization is logged so administrators can review agent activity.
License-controlled
Commercial deployments can use license-controlled agent activation and expiry tracking.
What Flowwkkr Biometric Attendance actually does
Manual attendance registers are the single biggest source of payroll disputes and month-end delay in small and mid-sized businesses. Flowwkkr connects your biometric device to your HR system so punches arrive automatically, are matched to the right employee, and feed payroll without reconciliation.
Flowwkkr Biometric Attendance is the practice of using fingerprint, face or card devices to record employee attendance automatically instead of a paper register or manual entry, with those records flowing straight into HR and payroll software.
How the device connection works
Flowwkkr uses a licensed Windows agent that runs on a machine inside your office network. The agent connects to your supported biometric device over the local network and securely relays punch records to Flowwkkr. Your device stays where it is; the agent bridges it to your HR workspace.
The connection is device-specific. Each installation is bound to a machine fingerprint, so punches are attributed to the correct installation and cannot be replayed from another machine.
- Windows agent installed on an office machine
- LAN connection to your supported biometric device
- Secure, fingerprinted relay of punch records
- Duplicate-safe ingestion so retried punches are counted once
The full data path, end to end
Understanding each hop makes integration problems far easier to diagnose, which is why it is worth being explicit about it.
| Hop | What happens | Common failure |
|---|---|---|
| Employee to device | Fingerprint, face or card is captured | Enrolment quality too low, or not enrolled |
| Device stores punch | Device assigns a numeric User ID and timestamp | Device clock drift, wrong time zone |
| Device to agent | Agent pulls records over LAN | Wrong IP, port 4370/80 closed, VLAN blocked |
| Agent to Flowwkkr | Agent relays and marks the batch as sent | Agent offline or licence inactive |
| Flowwkkr ingests | Duplicate key check, then attendance calculation | Device User ID not mapped to an employee |
Employee mapping: the key to accurate records
A punch only becomes useful attendance once it is matched to an employee. Your biometric device identifies people by a numeric User ID. Flowwkkr maps that device ID to the correct employee record, so every punch lands on the right person automatically.
This mapping is the most common integration failure point, and the reason a device can appear to work while attendance looks wrong. Flowwkkr supports bulk mapping, so mapping a whole team is not a manual one-by-one task.
Why clock accuracy on the device matters
The device is the source of truth for time. If the device clock drifts, every late-arrival and overtime calculation drifts with it, and the error is invisible because it is consistent.
This is a genuinely common problem with devices that sit unpowered or unmonitored for long periods. Sync the device to a reliable time source as part of your setup, and re-check it quarterly.
What changes day to day
Once biometric attendance is connected:
- No more paper registers or end-of-day manual entry
- Month-end attendance closes in minutes, not days
- Overtime and late arrivals calculated consistently
- Fewer payroll disputes, because records come from the device
- Attendance auditable back to the raw punch
How the connection is kept secure
Attendance records describe where your staff were and when, which is more sensitive than most HR data. A punch stream that could be replayed from another machine, or injected by anyone who reached the endpoint, would undermine the whole system rather than just one record.
The agent is licensed and bound to a machine fingerprint, so a copied installation does not work somewhere else. Punches are relayed to your own tenant over an authenticated channel, and every ingested record is attributable to the installation that sent it.
| Risk | Consequence if unaddressed | How it is addressed |
|---|---|---|
| Agent copied to another machine | Punches replayed or duplicated from elsewhere | Machine fingerprint binding in the licence |
| Someone on the LAN posts fake punches | Attendance invented, payroll inflated | Agent-to-tenant authentication, not open posting |
| Records altered after ingestion | Audit trail defeated | Raw punch retained alongside the calculated record |
| Same punch relayed twice | Hours and overtime inflated | Duplicate key check at ingestion |
What to do when a device is replaced or added
Devices get replaced, and sites expand. The point of separating the device from the HR data is that this is an operation rather than a project: employee records and attendance history stay in Flowwkkr, and the new device only needs its User IDs mapped.
The one thing worth doing carefully is clearing the enrolment on a device you are retiring. A user ID left enrolled is an ID the next person inherits, and their first morning produces attendance against the wrong employee.
- Replace the device, keep the employee records untouched
- Bulk map the new device User IDs to the same employees
- Clear enrolments on any device leaving service
- Check the new device clock before go-live
- Confirm device count still matches your plan
Frequently asked questions
Which biometric devices does Flowwkkr support?
Flowwkkr integrates with supported ZKTeco LAN biometric devices through its licensed Windows agent. Bring your specific device model to the demo and we will confirm the integration for your exact unit before you commit.
Do I need to buy new hardware?
Usually not. If your existing ZKTeco device communicates over the LAN on the standard SDK port, Flowwkkr can work with it. Confirm your model with us before purchase.
What happens if the network goes down?
The device keeps recording punches locally. When the connection returns, the agent relays the stored punches and Flowwkkr counts each one once, because ingestion is duplicate-safe. There is no data loss and no double counting.
Is the connection secure?
Yes. The agent is licensed and bound to a machine fingerprint, so it cannot be cloned and run elsewhere. Punch records are relayed over an authenticated channel to your own tenant.
Can we keep using the device software directly?
Yes. The device keeps working exactly as it does on its own, including on its own screen. Flowwkkr reads the records; it does not take the device over.
See it against your own requirements
Bring your device model, shift pattern and employee count. We will confirm fit on a private 2-hour demo.
See Flowwkkr in action
Request a private 2-hour live demo and explore the HR workflow.