HRMS is one of four Suntel360 products. See all four →
Suntel360 · HRMS
HRMS: The employee lifecycle from onboarding through payroll
In production
12 modules shipped
Sync
Biometric punches sync once a day from ESSL devices. Shift rules pair each day's punches, and hours worked set one daily status — present, half day or pending, with late as a separate flag — 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 that is already reconciled. Performance cycles with real state machines for reviews and goals.
Sound familiar?
The situations people come to us with
If two or three of these describe a normal week at your organisation, this is the conversation worth having.
Attendance arrives as a device export that somebody cleans up in a spreadsheet before payroll can run.
A scheduled job pulls punches straight from each biometric device and files them against the right employee. If a device is unreachable, that is handled and visible rather than silently becoming absences.
The same two timestamps mean different things to HR and to payroll, so the same day gets counted twice differently.
Shift rules pair the punches and hours worked set one daily status, centrally. Everything downstream reads that one answer.
Leave is approved over chat, and the balance is corrected later from memory.
Leave requests carry an approval trail and move balances themselves, and a cancellation is recorded as a state rather than deleted.
Salary letters and identity documents sit in a shared drive that far too many people can open.
Employee documents carry public, private or HR-only visibility, checked on the server against the person asking — not hidden in the interface.
Performance reviews stall because nobody knows whose turn it is.
A review moves through self-review, manager review and HR sign-off as explicit stages, and goals are acknowledged by the employee rather than assigned at them.
Someone leaves and still has access, because removing them is three separate jobs.
Permissions resolve against a live lookup on every request, so revoking access takes effect on the next call rather than the next sign-in.
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 that is 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 that decide how punches pair for a given employee on a given day, and holiday calendars that set which days are working days for payroll.
Roles & Permissions
Per-module role and permission checks resolved against a live lookup on every request, so an access change takes effect immediately.
What changes
What HRMS is actually for
One employee record behind attendance, leave, payroll, performance, and documents — with biometric punches syncing on schedule, not re-keyed from spreadsheets.
- Stop re-keying attendance from device exports before every payroll run
- Run payroll from attendance that is already reconciled
- Let managers approve along the real reporting line
- Keep private documents genuinely private, enforced on the server
- Give reviews and goals a process instead of a shared document
Straight answers
HRMS questions
Including the ones where the answer is no.
Learn how it works: Biometric Attendance to Payroll, Step by Step
Which biometric devices are supported?
ESSL devices. A scheduled sync pulls punches from each device once a day and matches them to employees by the device user ID on their profile. Shift rules pair each day's punches, and hours worked set the daily status, present, half day or pending, with late as a separate flag. The payroll run reads those daily records.
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?
Yes, from a desktop browser. Employees can check in and out on the web, and those times set the day's status just as device punches do. Web check-in from a mobile phone is blocked. Where a record does not reflect the day, it can be corrected through the attendance module.
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.