Suprema BioStar events, turned into Indian payroll attendance
Feed punch events from Suprema BioStation and FaceStation devices into Indian HRM through BioStar 2. Your access control platform keeps running the doors, Indian HRM turns the events into shifts, attendance, and payroll days.
BioStar 2 events post to the Indian HRM punch API in real time, so premium Suprema hardware finally feeds Indian payroll rules.
What the Suprema integration does
BioStation and FaceStation punches
Fingerprint and face events from Suprema devices become check-ins and check-outs with shift, late, and OT rules applied.
BioStar 2 friendly
Events flow from BioStar 2 to the Indian HRM punch API via its API or a small connector. Your BioStar configuration, zones, and door rules stay as they are.
India-ready attendance rules
Grace periods, half-day thresholds, week-offs, and night shifts are computed the way Indian HR policies define them, which BioStar alone does not do.
Access control untouched
Indian HRM consumes events only. Suprema keeps full control of doors, elevators, and security zones.
Safe against repeats
Duplicate events and connector re-sends are applied exactly once, so attendance hours stay correct even when the event stream is noisy.
Compliance-grade trail
Every attendance day traces to a biometric event, giving payroll a punch-to-payslip trail for PF, ESI, and labour audits.
Setup in four steps
- Create an API key — Under Settings, Attendance Integration, create a key with device type Suprema. Copy it when shown, it appears only once.
- Connect BioStar 2 — Use the BioStar 2 API or a connector script to forward door events to the Indian HRM punch API with the key in the header. Examples are on the integration page.
- Align user IDs with employee codes — Set each BioStar user ID to the Indian HRM employee code, or translate in the connector, so events map to the right people.
- Send a test event — Badge one person through a device and confirm the punch lands in Punch Logs with the right name and time.
- Go live — Enable forwarding for all devices and let the attendance rules take over from there.
Why customers use this integration
- Your Suprema investment starts doing double duty: security at the door, verified attendance for payroll.
- HR stops exporting event logs from BioStar and massaging them in Excel every month.
- Late marks, OT, and LOP follow Indian policy definitions instead of generic time-and-attendance defaults.
- Unmatched events surface in a needs-mapping list, so enrolment mistakes are caught early.
- Payroll disputes shrink because every deduction is backed by a biometric event.
Suprema integration FAQs
How do Suprema events reach Indian HRM?
Through BioStar 2. Its API exposes device events, and a small connector forwards each one to the Indian HRM punch API with your key. The integration page shows the endpoint, the header, and copy-paste examples in Python and Node.
Do door permissions or schedules change?
No. Suprema remains the system of record for access control. Indian HRM only reads events and never writes anything back to BioStar, so there is zero risk to your security configuration.
What if the connector goes down for a few hours?
Events stay in BioStar. When the connector resumes it can submit the missed window as a batch, and server-side duplicate detection makes the catch-up safe to re-run. Attendance backfills for the gap.
How are employees matched?
By employee code. Either enrol BioStar users with IDs equal to their Indian HRM employee codes, or let the connector translate IDs. Events with no match wait in a needs-mapping list for HR instead of disappearing.
Which Suprema devices are covered?
Anything that reports events into BioStar 2: BioStation 2 and 3, BioEntry, FaceStation 2 and F2, and X-Station, whether used for fingerprint, face, or card. If BioStar sees the event, it can become an attendance punch.