Hikvision face terminals feeding Indian HRM attendance

What the Hikvision integration does

Face punches as attendance

Access events from Hikvision MinMoe DS-K1T series terminals become clean check-in and check-out records in Indian HRM.

Works with your Hik setup

Whether you run HikCentral, iVMS, or standalone terminals, events forward to the Indian HRM punch API with a small connector, so your existing access-control install stays untouched.

Attendance rules applied

Late marks, half-days, overtime, and week-offs are computed from your policy and shifts, the same as any biometric device.

Door control stays separate

Indian HRM only consumes punch events. Your door relays, anti-passback, and access levels remain fully managed by the Hikvision system.

De-duplicated on arrival

Repeated events inside the debounce window are dropped and replays are applied only once, so noisy access logs do not corrupt hours.

Payroll-grade records

Every payslip line backed by a face-verified event, which holds up in PF, ESI, and labour inspections.

Setup in four steps

1. Create an API key — Under Settings, Attendance Integration, create a key with device type Hikvision. The key is shown once, copy it then.
2. Set up event forwarding — Point your HikCentral event rule, listening server, or connector script at the Indian HRM punch API with the key in the request header. The integration page shows ready-to-use examples.
3. Map person IDs to employee codes — Use the Hikvision person ID as the employee code in Indian HRM, or translate it in the forwarder, so each event maps to the right person.
4. Send a test event — Walk one person through the terminal and confirm the punch in Punch Logs. The needs-mapping list will show any ID that did not match.
5. Go live — Enable forwarding for all terminals. Each device can carry its own ID so punches stay attributable per door.

Why customers use this integration

• Reuses the face terminals you already installed for access control, no second device at the door.
• Attendance stops being a CSV export from iVMS. It is live, deduplicated, and shift-aware.
• Contactless face punches remove buddy punching without new hardware.
• HR sees who is in the building now, across every Hikvision door that forwards events.
• Access control and attendance stay decoupled, so a change in one never breaks the other.

Hikvision integration FAQs

Does Indian HRM connect to Hikvision terminals directly?

Hikvision speaks its own protocol, so events reach Indian HRM through a forwarder: a HikCentral event rule, the ISAPI listening-server feature, or a small connector script that posts to the punch API. The integration page in your dashboard shows working examples with the exact URL and header to use.

Will this interfere with door access control?

No. The integration only reads punch events. Door schedules, access levels, and anti-passback continue to be managed entirely by your Hikvision system. If the forwarder is ever down, doors keep working and only attendance sync pauses.

How are people matched between the two systems?

By employee code. The simplest setup is using the same code as the Hikvision person ID when you enrol faces. If your person IDs already exist, the forwarder can translate them. Unmatched events are held in a needs-mapping list instead of being dropped.

Is a batch mode available for buffered events?

Yes. The punch API accepts single events and batches, so a forwarder that queues events during a network issue can submit the backlog in one call. Duplicates are detected server-side, which makes re-sending safe.

What Hikvision hardware does this cover?

Any terminal whose events you can forward, which in practice means the MinMoe face terminals (DS-K1T331, DS-K1T341, DS-K1T671 and similar) plus fingerprint models, standalone or under HikCentral. If it produces an access event with a person ID and time, it can become an attendance punch.