Realtime terminals, reporting to payroll on their own

What the Realtime Biometric integration does

Punches in as they happen

Fingerprint, face, and card punches from Realtime T-series and similar terminals reach Indian HRM within seconds over the device cloud push.

No PC, no pen drive

The terminal is the one making the connection. No desktop software, no static IP, no USB downloads. Enter the server address once and it keeps reporting.

Late marks by your rules

Grace period, late threshold, and half-day cutoffs come from your attendance policy and the rostered shift, so the same 9:35 punch can be fine for one shift and late for another.

Every branch in one register

Machines at different sites each report under their own serial number, and all punches land in one attendance register tagged by device.

Retry-safe by design

Realtime devices re-send unacknowledged punches. Indian HRM applies each punch exactly once, so retries and double badges never corrupt hours worked.

Muster to payslip

Attendance days feed payroll directly, so PF, ESI, OT, and LOP calculations sit on punch-backed data with a clean audit trail.

Setup in four steps

1. Register the device — Under Settings, Attendance Integration, add an entry with device type Realtime and the serial number from the device info screen.
2. Enter the server settings — On the terminal, open the cloud or server communication menu and enter the server address and port from your integration screen.
3. Set clock and timezone — Choose the device timezone in Indian HRM and make sure the machine clock matches it.
4. Match employee codes — Enrol staff on the device with user IDs equal to their Indian HRM employee codes so every punch maps automatically.
5. Test and roll out — Confirm a test punch in Punch Logs, then repeat the same settings on each Realtime machine.

Why customers use this integration

• Month-end attendance is already in the system, not sitting inside the machine waiting for a download.
• HR sees late marks and missing punches the same day, when they can still be fixed.
• Device-side memory plus server-side de-duplication means outages do not lose punches and retries do not double them.
• Unmatched punches queue up visibly instead of vanishing, so a wrongly enrolled ID is caught in the first week.
• One register across all branches makes multi-site payroll consolidation a non-event.

Realtime Biometric integration FAQs

Does this need the Realtime desktop software?

No. Terminals with cloud push connect on their own: server address and port on the device, serial number registered in Indian HRM, done. If you run an older model that only talks to the desktop tool, that tool or a small script can post punches to the Indian HRM punch API instead.

How fast do punches appear?

Within seconds on a normal connection. Each punch is pushed as it happens and shows in the Punch Logs screen, so you can verify a new device with a single test punch instead of waiting for a batch window.

What if two people share a device user ID by mistake?

Every punch maps by employee code, so a shared or wrong ID sends both people's punches to one employee. The fix is renumbering the device user ID to the right employee code. The Punch Logs screen makes this visible quickly because in and out times stop making sense for that employee.

Is the connection secure?

Punches travel over HTTPS, only registered device serials are accepted, and you can add an IP whitelist per device so punches are only taken from your office connections. API keys for middleware are stored hashed, the same way passwords are.

Can attendance from the device be edited afterwards?

Corrections go through regularization with approval, and every raw punch stays in the log unchanged. Once a payroll period is locked, backdated device punches cannot rewrite paid days, which protects a closed month from a machine replaying old data.