ADMS push · ATTLOG compatible

Connect Supported ZKTeco Attendance Terminals to Your Staff Roster

Receive compatible ATTLOG punches from supported ZKTeco terminals using ADMS push, then compare employee clock-ins with scheduled shifts in Simple Roster Plus.

Register the terminal, match device user IDs to staff, and review punches beside the weekly roster.

  • ADMS push over HTTPS
  • Compatible ATTLOG ingest
  • Roster-connected attendance
Terminal + roster attendance
Attendance terminal beside the Simple Roster Plus attendance dashboard
Supported terminal → cloud
Who this is for

Built for Teams That Already Use a ZKTeco Terminal

This page is for managers who own or plan to use a supported ZKTeco attendance terminal and need roster-connected software around the punch data.

You already have the clock

Keep your supported terminal and send compatible attendance punches into Simple Roster Plus.

You need the weekly plan nearby

Use employee roster software context so clock-ins sit beside scheduled shifts—not in a separate spreadsheet.

You want honest limits up front

Compatibility depends on model, firmware, and configuration. This is not a claim that every ZKTeco device works.

Connection method

How ADMS Push Works

Supported ZKTeco terminals connect outbound to Simple Roster Plus using ADMS push over HTTPS on port 443.

Step 1

Register the serial

Add the terminal in Devices, assign a location, and keep the device enabled.

Step 2

Point the terminal

Set the public HTTPS server address and port 443 so the device can reach /iclock/*.

Step 3

Send ATTLOG

Enable ATTLOG or real-time attendance upload. Compatible punch events are received and stored.

Step 4

Review against the roster

Matched punches appear in attendance so managers can compare planned vs actual shifts.

What is received

What Attendance Data Simple Roster Plus Receives

Simple Roster Plus receives compatible ATTLOG punch events—not fingerprint or face templates.

Punch events

Compatible ATTLOG lines provide terminal user ID, timestamp, and in/out state interpretation.

Device identity

Devices are recognized by registered serial number. Contact updates last-seen visibility for managers.

Near-duplicate handling

Near-duplicate punches within a short window are suppressed so the log stays cleaner.

Staff matching

Match Terminal User IDs to Employees

Each terminal user ID must match the employee’s device user ID at the device’s location. Matching is not automatic without that setup.

  • Assign the device to a location.
  • Set each staff member’s device user ID to the terminal enrolment ID.
  • Mapped punches attach to the right employee for roster-connected attendance.
See how employee attendance software reviews present, late, and absent → See how clock events enter and get matched →
Matching view linking unmatched terminal device user IDs to staff Device user ID fields.
Map unmatched terminal user IDs to employees so punches attach to the right person.
Recover exceptions

Retain and Recover Unmatched Punches

If a terminal user is not mapped yet, Simple Roster Plus keeps the punch instead of dropping it.

Retain unknown users

Unmatched device punches stay available for review with the terminal user ID preserved.

Map when ready

Link the terminal user ID to an employee when you know who it belongs to.

Backfill earlier punches

After mapping, prior unmatched punches for that user can attach to the employee.

Terminal setup

What Must Be Configured on the Terminal

Setup is guided, not zero-configuration. Managers register the device in Simple Roster Plus, then enter Cloud Server / ADMS settings on the terminal.

Older firmware may require full push and poll URLs instead of a server address alone. The Add Device checklist shows both styles.

  1. Register the terminal serial in Simple Roster Plus and assign it to a location.
  2. Set the public HTTPS server address the device can reach.
  3. Use port 443 and enable HTTPS.
  4. Enable ATTLOG or real-time attendance upload. Do not rely on OPERLOG-only.
  5. Match terminal user IDs to employee device user IDs.
Honest boundaries

Compatibility Boundaries and Limitations

Buy with clear expectations. Simple Roster Plus supports selected ADMS-capable terminals that send compatible ATTLOG—not every ZKTeco product or connection method.

Supported today

ADMS push over HTTPS, compatible ATTLOG ingest, serial registration, staff matching, unmatched recovery, and roster-connected attendance review.

Not included

Pull TCP, LAN SDK, Windows agent, BioTime, ZKBio, biometric template storage, automatic discovery, remote device commands, or staff enrolment push to terminals.

Privacy boundary

Simple Roster Plus stores attendance punch events and staff identifiers, not fingerprint or face templates. Devices are recognized by registered serial number and can be disabled.

Setup guidance is based on ADMS Cloud Server settings commonly used by terminals such as the F22 family. Confirm your exact model and firmware can send compatible ATTLOG records to a cloud server.

Pricing and device slots

Device Slots Are Software Connections

Connect terminals within your plan limits. Device slots provide software connectivity. Biometric hardware is not included.

Free

$0 / month

1 device slot with a 30-day live sync trial after the first device connects.

Start Free

Pro

$49.99 / month

3 included device connectivity slots. Extra devices available as paid add-ons.

Start Free

See full plan details on the homepage pricing section. Multiple devices are supported within plan limits.

FAQ

Common Questions about ZKTeco Integration

Straight answers based on the current product—not a hardware catalog.

Which connection method is supported?

ADMS push. Supported terminals connect outbound to Simple Roster Plus over HTTPS on port 443 and send punches to public /iclock/* endpoints.

Does it support pull TCP?

No. Pull TCP, LAN SDK, and Windows-agent sync are not available in the cloud product.

Which ZKTeco models are supported?

Selected ADMS-capable terminals that send compatible ATTLOG. Compatibility depends on the terminal model, firmware, and configuration. There is no certified all-model list.

Is F22 supported?

Setup guidance is based on ADMS Cloud Server settings commonly used by terminals such as the F22 family. Confirm your exact model and firmware can send compatible ATTLOG records to a cloud server.

What terminal settings are required?

Register the serial in Simple Roster Plus, set the public HTTPS server address, use port 443, enable HTTPS, turn on ATTLOG or real-time attendance upload, and match terminal user IDs to employee device user IDs. Older firmware may need full push and poll URLs.

How are users matched to staff?

The terminal enrolment / user ID must match the employee’s device user ID at the device’s location. Matching is not automatic without that setup.

What happens to unmatched punches?

Unmatched punches are retained. When you map the terminal user to an employee, earlier unmatched punches for that user can backfill.

Is attendance real time?

Supported terminals can push punches promptly when ATTLOG / real-time upload is configured. The manager view is not a guaranteed live-streaming dashboard and may require a refresh.

Does Simple Roster Plus store fingerprints or face templates?

No. Simple Roster Plus stores attendance punch events and staff identifiers, not fingerprint or face templates.

Is hardware included?

No. Device slots provide software connectivity. Biometric hardware is not included.

Does it work with BioTime or ZKBio?

No. There is no BioTime or ZKBio integration in Simple Roster Plus.

What are the device limits by plan?

Free includes 1 device slot with a 30-day live sync trial. Plus includes 1 device. Pro includes 3 devices. Extra devices are available as paid add-ons where supported.

Start Free and Register Your First Supported Terminal

Create your account, add a device serial, and connect a supported ZKTeco terminal with ADMS push—then review punches beside your weekly roster.