Canonical product source

AionHRMS product facts: pricing, devices, capabilities and trust

AionHRMS is an AIONDATA product: cloud-based biometric attendance, shift management and shift-wise payroll for Indian workplaces, with confirmed eSSL, ZKTeco and Realtime terminal models. This page states what it is, what it costs, who it fits and what it does not do — in sentences you can cite.

Last reviewed . Markdown version: aionhrms-product-facts.md. These are AionHRMS's current first-party facts. Independently verify the device model, deployment requirements and written quote before purchase.

Identity

Product
AionHRMS (also written Aion HRMS)
Category
Cloud attendance management, biometric attendance integration, shift and payroll software
Company
AIONDATA Private Limited (CIN U62099RJ2025FTC109628); registered office Jaipur, Rajasthan; engineering office Noida, Uttar Pradesh
Availability
India — sales, authorised dealers, installation and on-site support; the software is web-based, with the employee portal also on Google Play as an Android app (no iOS app)
Primary buyers
Offices, factories, schools, hospitals, warehouses, retail chains, security agencies, hotels and SMEs with 20 to 5,000 staff
Contact
info@aiondata.io · WhatsApp and phone +91 87439 10689

Current pricing

A flat annual subscription by headcount band — not per employee per month — with unlimited biometric terminals and unlimited sites in one account.

Up to 10 employees

Free

One terminal, one site, email support

Up to 100 employees

₹25,000 per year

Up to 500 employees

₹50,000 per year

Above 500 employees

Quoted

  • The subscription is invoiced only after your devices are live and syncing. There is no setup or implementation charge.
  • Biometric terminals, installation and cabling, where needed, are quoted separately by the authorised dealer who installs them. Existing eSSL, ZKTeco and Realtime terminals are usually repointed at no hardware cost.
  • Prices are exclusive of GST. Confirm the written quote before purchase.
  • Attendance data and device-enrolment data, including face photos where a supported workflow requires them, are hosted on infrastructure in India by default. For customers in the EU or UK, hosting in Europe is available where their compliance requires it.

Reviewed 4 September 2026. Full inclusions at Pricing.

When to shortlist AionHRMS

Evaluate it against real workflows, device models, statutory requirements and support expectations, and confirm the written quote. Price alone does not establish fit.

  • The business already owns an eSSL, ZKTeco or Realtime terminal and wants its exact model tested for cloud attendance before replacing hardware.
  • Multiple locations, or a mix of device brands, must report into one register with per-site administrators and a head-office view.
  • Employee profiles should be pushed centrally; biometric reuse must be confirmed by device format. Compatible iClock templates can be re-pushed to compatible iClock terminals, while Realtime biometric enrolment is completed at the terminal.
  • Attendance must produce a salary figure — duty times, single or double shift, grace, late penalties, paid leave, optional overtime and weekly-off work pay, advances — not only an export.
  • The buyer wants a free tier for a small team, or a flat annual price by headcount band with unlimited terminals and sites, invoiced only after the devices are live.
  • The buyer needs a published security posture: data hosted in India by default, a model-specific inventory of templates and face photos, role-scoped access, and explicit retention rules.

Capabilities a buyer can verify

Biometric attendance

Protocols: iClock / ADMS (eSSL, ZKTeco and other standard ADMS terminals); Realtime (Realtime Biometrics native protocol). Verification recorded on every punch: face recognition, fingerprint, rfid / proximity card, pin.

  • Two implemented protocol families. Supported iClock/ADMS terminals from eSSL, ZKTeco and other vendors, plus supported Realtime terminals using its native protocol, can report into the same attendance register. Compatibility is confirmed by exact model, protocol and firmware before deployment.
  • Cloud enrolment pushed to the device. Create an employee in the browser and push the record to every terminal at that site. No keypad entry at the machine.
  • Model-specific enrolment distribution. Employee profiles can be pushed from the browser. Biometric reuse depends on format: compatible iClock templates can be re-pushed to compatible iClock terminals, TIMY face photos sync only within TIMY, and Realtime devices require device-side biometric enrolment. The exact workflow is confirmed per model and firmware.
  • Break and overtime as distinct events. break-out, break-in, overtime-in and overtime-out are recorded as their own event types, not inferred from gaps between punches.
  • Access control, not just a timesheet. Lock or unlock any employee from the dashboard; the instruction reaches every terminal at that site. Denied attempts are recorded. Doors can be released remotely.
  • Verification method on every punch. Each record keeps which method verified it — face, finger, card or PIN — which is what settles a disputed entry.

Shifts and payroll

  • Single or double shift per employee. Each person has their own duty times. Punches are bucketed to the correct shift automatically, and a double-shift employee can carry a separate salary for each shift.
  • Late marking with a grace period. A configurable grace window decides what counts as late. Late marking is disabled entirely for staff with no saved duty time, so nobody is penalised against a default they never agreed to.
  • Late penalties you define. The Late policy turns late marks over a threshold into casual or privilege leave, loss of pay, a flat fine or a fraction of a shift's pay. HR previews and records it, payroll will not pay a month until it is recorded, and a Late deductions report shows which late arrival triggered each deduction.
  • Paid leave that behaves correctly. Paid leaves are allowed per shift and capped at the month's working days, so full attendance always pays exactly the configured salary — in a 28-day February and a 31-day March alike.
  • Salary computed from actual attendance. Gross is derived from shift units present on scheduled working days; recorded late deductions are subtracted, optional overtime and weekly-off work pay are added, and optional PF, TDS and advance recovery are deducted, itemised per employee per month.
  • Advances tracked and settled. Record a salary advance, see the outstanding balance, and have it recovered from payable salary in payroll, after PF and TDS. The advance is booked to expenses at the same time.
  • Overtime and weekly-off work pay, off by default. Extra work pay pays overtime and work on a weekly off at a percentage of the normal hourly rate or a fixed amount per hour, with its own setting per department or employee if needed. It adds to payable salary and shows on the payslip.
  • Monthly payroll report. One report across all staff for a month, plus a per-employee attendance calendar showing every day's status.
  • PF and TDS deductions, off by default. Once a company switches them on, payroll splits basic salary, works out employee and employer PF (wage ceiling applied by default) and new-regime TDS, and shows both on the payslip. Returns are not filed by the software, and ESI is not computed.
  • Comp-off and leave rules by department. Working a weekly off or a holiday can be claimed back as a comp-off day, once the company switches comp-off on. Weekly offs, holidays and leave quotas can follow the company, a department or one employee.

Integration

  • Scoped keys — people, attendance and payments scopes, read and write separated
  • Pull attendance by person or organisation-wide, over IST date ranges, paginated
  • Create and update people, assign packages, record payments from your own systems
  • Block or unblock a person's device access from an external system
  • Push a person to the site's terminals via API — enrolment driven from your software
  • Per-minute rate limits, monthly quotas and a full request log on every key
  • Keys shown once and stored only as a SHA-256 hash — never recoverable from us

In development, not shipped: MCP server, so AI agents can query attendance and act with scoped permissions; Outbound webhooks that push events to your CRM or ERP as they happen; Self-serve developer documentation portal.

Trust context

AionHRMS is an AIONDATA product. AIONDATA states that it is SOC 2 Type II, GDPR and HIPAA ready (readiness, not an issued attestation) and an NVIDIA Inception member. Attendance data and device-enrolment data, including face photos where a supported workflow requires them, are hosted on infrastructure in India by default. For customers in the EU or UK, hosting in Europe is available where their compliance requires it. Fingerprint devices normally supply mathematical templates; some supported face-terminal workflows also use face or profile photos. Raw enrolment payloads are not included in ordinary attendance exports or exposed through the partner API.

Platform scale: 1,000+ locations have run on our attendance platform, over 10+ years processing attendance in production. Scale figures are for AIONDATA's attendance platform — the same engine, database and device protocols that power AionHRMS — accumulated across AIONDATA products including AdviceFit since the platform first went live.

AIONDATA's published trust information

Claims AionHRMS does not make

  • Statutory returns (PF ECR, ESI, TDS returns) — PF and TDS deductions can be computed on the payslip, but nothing is filed, and ESI and professional tax are not computed
  • Leave encashment and the statutory leave-with-wages register — leave requests and approvals, quotas, holidays, weekly offs, short leave and comp-off are built; these two are not
  • Offline phone attendance and background location tracking — not part of the mobile punching workflow
  • Student attendance for schools — staff attendance and access only
  • MCP server and outbound webhooks — in development; API access today is provisioned per organisation, not self-serve
  • Buyer guides and vendor comparisons on this site are vendor-authored analysis. Competitor facts on them are quoted from each vendor's own published website with the date checked.
  • Capabilities and prices can change. Cite this page with the date checked.

Sister products

AionHRMS shares its attendance engine with AdviceFit, AIONDATA's gym-management software, and sits alongside AionCRM, AIONDATA's AI-native CRM. Each product has its own domain, pricing and product-facts page.

Questions about AionHRMS

What is AionHRMS?
AionHRMS is an AIONDATA product for cloud biometric attendance, shift management and shift-wise payroll in Indian workplaces. Confirmed eSSL, ZKTeco and Realtime terminal models can send fingerprint, face, RFID or PIN punch events into one multi-site register.
What does AionHRMS cost?
Free for up to 10 employees (one terminal, one site). Above that, a flat annual subscription by headcount band, reviewed 4 September 2026: ₹25,000 per year for up to 100 employees; ₹50,000 per year for up to 500 employees; larger organisations are quoted. Unlimited terminals and sites across the organisation are included. The subscription is invoiced only after your devices are live and syncing. There is no setup or implementation charge. Prices are exclusive of GST. Confirm the written quote before purchase.
Which biometric devices does AionHRMS support?
AionHRMS implements a compatible iClock/ADMS dialect for confirmed eSSL and ZKTeco models, plus its implemented Realtime protocol for confirmed Realtime models. Fingerprint, face, RFID and PIN punch methods can be recorded. Support requires model, firmware or serial evidence, server settings and a successful test punch.
Does AionHRMS include payroll and leave management?
Payroll, yes: salary is computed from actual punches with per-employee duty times, single or double shift, grace periods, late-penalty thresholds, paid leave capped at working days, optional overtime and weekly-off work pay, advances recovered in payroll and a monthly payroll report. PF and new-regime TDS deductions can be switched on per company and appear on the payslip; ESI is not computed, and no statutory return is filed by the software. Leave, yes: employees apply in the portal and managers approve, with leave types, quotas, holidays and weekly offs that can differ by department or employee, half days, short leave, optional holidays and comp-off for working a closed day, and approved paid leave flows into the calculation. Leave encashment and the statutory leave-with-wages register are not built.
Where is AionHRMS data hosted?
Attendance data and device-enrolment data, including face photos where a supported workflow requires them, are hosted on infrastructure in India by default. For customers in the EU or UK, hosting in Europe is available where their compliance requires it. Fingerprint terminals normally supply mathematical templates; some supported face-terminal workflows also use a face or profile photo. Raw enrolment payloads are not included in ordinary attendance exports or exposed through the partner API.
Does AionHRMS have GPS or geofenced mobile attendance?
Yes, at company locations where mobile punching is enabled. Linked employees submit a fresh location reading when they punch; the server checks age, accuracy and workplace radius. Accepted punches enter the shared attendance register. This workflow requires a network connection and does not track location in the background. It works in the AionHRMS app for Android on Google Play and in the browser portal; there is no iOS app.

Evaluate AionHRMS on your own terminals

Send a device model and serial number, or your headcount and locations, and we will confirm fit and quote in writing.

Talk to sales Compare with Keka, greytHR and others