Realtime native protocol
Realtime biometric integration with HRMS and payroll
Realtime terminals are widely deployed across India and well supported by dealers in every major city. AionHRMS speaks Realtime's native push protocol directly — not through an adapter — so your existing machines report into a cloud HRMS that also carries attendance through to salary.
AionHRMS integrates with compatible Realtime biometric attendance machines using Realtime's own push protocol, implemented natively. Once a confirmed terminal is pointed at our server it registers itself, pushes attendance and accepts supported employee-enrolment commands. The same account can also accept confirmed eSSL and ZKTeco terminals over iClock/ADMS; compare each vendor's current supported-model list before choosing software for a mixed estate.
How to connect a Realtime terminal
Changing only the server setting normally leaves existing on-device enrolments in place, but confirm this on the exact model and firmware before cutover. AionHRMS can push employee profiles and open the Realtime enrolment workflow; biometric enrolment itself is completed at each Realtime terminal and is not pushed cross-brand.
- 1Register the terminal in AionHRMS with its serial number and select the Realtime protocol
- 2On the device, open the communication or server settings menu
- 3Set the server address to the AionHRMS endpoint we give you, and the port alongside it
- 4Save and let the device poll — it registers itself and appears as online
- 5Push your employee list from the browser; the device receives it on its next poll
We confirm compatibility from your model and serial number before you commit to anything. If a terminal will not work, we say so rather than propose a workaround.
What Realtime's own software does well
Realtime supplies a cloud HRMS alongside its hardware, and for a single-brand site it is a reasonable fit — it is built by the people who built the terminal, and it is often bundled with a new device purchase.
- Written specifically for Realtime terminals, so device support is first-party
- Frequently bundled with new-device purchase
- Covers core HRMS, attendance, leave and payroll modules
What changes when the same machine reports to AionHRMS
The difference is not the Realtime terminal — it keeps working exactly as it does. The difference is what happens once you own hardware from more than one manufacturer, which almost every organisation does within five years.
- Realtime, eSSL and ZKTeco terminals in one register, at one login
- Employee profiles managed centrally; biometric enrolment completed at each Realtime terminal
- Shift-wise payroll: per-employee duty times, late rules with a grace period, penalties as fine or shift fraction
- Advances recorded, tracked and settled against the next payment
- Your data stays with a vendor-independent platform rather than a hardware manufacturer
Frequently asked questions
- Does AionHRMS support Realtime machines natively?
- Yes. Realtime's push protocol is implemented directly in our device layer rather than being translated through a generic adapter, which is why Realtime terminals can sit alongside eSSL and ZKTeco units in the same account.
- Will switching erase enrolled fingerprints on the device?
- Changing only the server address normally leaves on-device enrolments in place, but we verify the procedure for the exact model and firmware before cutover. Realtime biometric templates are not pushed from AionHRMS.
- Can I run Realtime's software and AionHRMS at the same time?
- A terminal generally pushes to one server at a time, so in practice you choose one. Plan the switch deliberately rather than assuming both will run in parallel.
- Which Realtime models are supported?
- Support is confirmed by exact model, serial, firmware and a successful test punch against the implemented native protocol. A configurable server address is necessary but is not, by itself, a compatibility guarantee.
Related
Send us your Realtime model number
We will confirm compatibility in writing before you spend anything.