Attendance → payroll

Biometric attendance with payroll built in

The punch that opened the gate should be the punch that decides the salary. In most organisations it is not — attendance lives in one system, salary is rebuilt in a spreadsheet, and the two disagree by the third of every month.

A biometric attendance system with payroll computes salary directly from device punches rather than from a re-keyed summary. In AionHRMS each employee has their own duty times for one or two shifts; punches are assigned to the correct shift automatically; late marks are counted against a grace period you configure; and salary is derived from shift units actually present, with paid leave applied and late penalties deducted as either a flat fine or a fraction of a shift's pay. Advances are recorded and settled against future payments, and a monthly payroll report covers the whole workforce.

2 shifts

per employee, each with its own duty times and salary

Grace

a late window you set — not a vendor default

Paid leave

applied per shift, capped at the month's working days

Advances

recorded, tracked and settled against the next payment

How the salary is actually computed

The formula is published here rather than hidden, because a payroll number nobody can explain is a payroll number nobody trusts. Working days come from the calendar month minus your paid-leave allowance, so a 31-day month and February both pay the configured salary at full attendance.

  • Working days = days in the month − paid leaves allowed
  • Paid units = shift units present + paid leaves, capped at working days
  • Gross = per-unit rate × paid units, per shift
  • Late penalty applies only above the count threshold you set
  • Net = gross − late deduction, then advances settled separately

Shifts are the unit, not days

A trainer working 06:00–10:00 and 17:00–21:00 is not doing a long day, and a nurse whose duty starts at 22:00 does not belong to the calendar date it ends on. Treating the shift as the unit is what makes both of those come out right.

  • One or two shifts per employee, configured individually
  • Punches bucketed to the correct shift automatically
  • Double-shift employees can carry a separate salary per shift
  • Late marking disabled entirely for staff with no saved duty time, so nobody is penalised against a default they never agreed to

Late rules that a manager can defend

Late deductions cause more disputes than any other part of payroll. The way through is a rule everyone knows in advance and a record that shows exactly which days triggered it.

  • Grace period in minutes, applied consistently
  • A threshold count before any penalty applies at all
  • Penalty as a flat fine, or as a configurable fraction of a shift
  • Per-employee attendance calendar showing every day's status
  • Every punch retains its terminal and verification method

What is not included

Being precise here matters more than anywhere else on this site, because a payroll gap discovered mid-cycle is expensive.

  • Statutory filing — PF, ESI and TDS returns are not filed by AionHRMS
  • Leave application and approval workflows — paid-leave allowance is applied, but there is no request/approve flow
  • Payslip templates and CTC structuring beyond the calculation described above
  • If any of these is a hard requirement, tell our team before you commit

Attendance-only versus attendance with payroll

AionHRMSAttendance-only software
End of monthA computed salary figure per employee, itemised.An export somebody rebuilds in a spreadsheet.
ShiftsPer-employee duty times, one or two shifts.Often a single company-wide timing.
Late marksGrace period, threshold, and a defined penalty.Usually a flag, with the deduction done by hand.
Paid leaveApplied in the calculation and capped correctly.Tracked separately, if at all.
AdvancesRecorded with an outstanding balance.A note in a diary.
Source of truthOne — the punch.Two, which disagree.

Frequently asked questions

Does AionHRMS actually run payroll, or just export attendance?
It computes salary. Each employee has duty times and a salary configuration; the system derives gross from shift units present, applies paid leave, deducts late penalties above your threshold, and produces a per-employee figure and a monthly report. What it does not do is file statutory returns.
Can two employees have different shift timings?
Yes — duty times are per employee, not per organisation, and each can be single or double shift.
How are paid leaves handled?
You set an allowance per month. Paid units are the sum of shifts present plus the allowance, capped at the month's working days, which means full attendance always pays exactly the configured salary regardless of month length.
What about overtime pay?
Overtime-in and overtime-out are captured as distinct events and appear in the attendance record. If you need overtime paid at a specific multiplier, tell our team the rule you use so we can be precise about what is supported today rather than guess.
Can a manager run payroll, or only the owner?
Payroll access is a permission an owner grants. A manager without it can see attendance but not salary.

One record from the gate to the salary sheet

Stop reconciling attendance against payroll. They should never have been two numbers.