HRMS is part of our AI-powered platform. Explore all AI capabilities →
Suntel360 · HRMS
HRMS: The employee lifecycle from onboarding through payroll
System Status
0 processes active
Sync
Biometric punches sync on a schedule from ESSL devices. Shift rules and the holiday calendar resolve each punch pair into a defensible daily status — present, late, half day — that HR and payroll both read.
Govern
Role-based permissions resolved on every request, with employee documents carrying public, private, and HR-only visibility enforced on the server — not hidden in the interface.
Run
Payroll runs triggered on demand by authorised operators, reading attendance and leave that are already reconciled. Performance cycles with real state machines for reviews and goals.
Scenarios
Built for the way your workforce actually operates
Not thin modules behind one brand. Each area carries its own records, its own process, and its own access model.
Employee Experience
12 docsOne employee record behind attendance, leave, payroll, documents, and performance — with review cycles that have real stages.
Payroll Operations
4 docsA run that reads attendance and leave already reconciled, produces payslips from that same run, and is gated by permissions.
Line Managers
8 docsApprovals that follow the reporting line from the org chart, team attendance resolved against shifts, and review cycles with clear ownership.
People & Culture
5 docsLeave balances and requests, payslips, and personal documents with visibility rules that mean private really is private.
IT & Infrastructure
6 docsBiometric device sync with degradation handling, role-based permissions resolved per request, and managed cloud infrastructure.
Performance & Growth
6 docsReview cycles with self-review, manager review, and HR finalisation, plus goals with approval and progress states.
Documents
Document and master types across the employee lifecycle
One employee record behind attendance, leave, payroll, documents, and performance.
Onboard
Employee records, org chart, and business-unit assignment — the foundation everything else hangs off.
Attend
Biometric punches sync on a schedule. Shift rules resolve each pair into a daily status HR and payroll both trust.
Review
Performance cycles with self-review, manager review, and HR finalisation. Goals negotiated, not assigned.
Pay
Payroll runs triggered on demand by authorised operators, reading attendance and leave that are already reconciled.
Modules
Twelve functional areas, one organizational model
Each module reads from the same employee record through the same permission and visibility checks.
Employees
Employee records, organizational structure, and business-unit assignment, maintained as HRMS's own authoritative record.
Attendance
Shift-aware attendance resolution that reconciles device punches into a daily record.
Biometric Device Sync
Scheduled synchronization from ESSL biometric devices, with degradation handling when a device goes offline.
Leave Management
Leave requests, balances, and approvals that carry through to attendance and payroll.
Payroll
Permission-gated payroll runs triggered on demand by an operator, tied to attendance and leave records.
Payslips
Payslip generation and distribution built from the output of a completed payroll run.
Performance & Goals
Review cycles with self-review, manager review, and HR finalisation, plus goals that carry their own approval and progress states.
Recognition
Peer recognition recorded against an employee's record rather than lost in a chat channel.
Employee Documents
Document storage with public, private, and HR-only visibility rules enforced server-side.
Org Chart
Reporting structure derived from the same employee records that drive approvals and visibility.
Shifts & Holidays
Shift timings and holiday calendars that determine how a punch pair is interpreted for a given employee on a given day.
Roles & Permissions
Per-module role and permission checks resolved against a live lookup on every request, so an access change takes effect immediately.
Straight answers
HRMS questions
Including the ones where the answer is no.
Which biometric devices are supported?
ESSL devices, over their TCP protocol. The scheduled sync pulls punch records directly from each device and files them against the matching employee record.
Does payroll run automatically each month?
No. A payroll run is triggered on demand by an authorised operator. That is a deliberate choice — a pay cycle closes when the people accountable for it decide the inputs are right, not when a timer fires.
What happens to attendance when a device is offline?
The sync path handles an unreachable device explicitly rather than treating it as a clean run with no punches, so the gap is visible instead of quietly becoming absences.
Can managers see everything about their reports?
No. Visibility is driven by role and permission checks resolved on every request, and employee documents carry their own public, private, or HR-only classification enforced on the server.
Can employees work from home and still be counted?
Attendance is resolved against each employee's shift and the holiday calendar, and records can be corrected through the attendance module where a punch does not reflect the day.
Does it connect to the ATS?
Yes, in one direction that is live today: ATS authenticates recruiters against their HRMS employee record, and hiring-team job assignments are written back to that record. No candidate or application data is sent to HRMS.
See HRMS on your own scenario
Bring your attendance process, a payroll run, or a hiring round — and we will show you how the system handles it.