Punch ≠ payroll
Biometric devices never reconcile with salary LOP, so finance re-keys late marks by hand.
Human Resources that runs attendance, leave, and payroll together
ScholarERP HR is the people operating system for your campus — biometric staff attendance, policy-driven leave, and salary runs that stay in sync with the same employee master. No more separate tools for punch, CL balance, and payslips.
3-in-1
attendance · leave · payroll
1
employee master for every process
Audit-ready
punches, approvals & payslips
The problem
Why campus HR still feels like three disconnected jobs
When attendance lives in a biometric vendor app, leave on WhatsApp, and payroll in Excel, nobody trusts month-end — and principals cannot see who is actually on campus.
Leave without coverage
Verbal CL approvals leave classes uncovered and balances disputed.
Shadow staff lists
HR, academics, and accounts each maintain a different employee directory.
Month-end dread
Payslip cycles slip because attendance and leave were never closed cleanly.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Staff attendance
Biometric / RFID / app check-in for teaching and non-teaching staff with shift rules, late marks, and daily presence boards.
Leave management
CL, EL, SL, LOP and custom types — apply, approve, balance, and calendar views that substitute planners can trust.
Faculty & staff payroll
Salary structures, deductions, TDS summaries, bank disbursement packs, and digital payslips from the same employee record.
Employee directory
Contracts, departments, campuses, qualifications, and reporting lines as the HR system of record.
Shift & holiday rules
Honor academic calendar offs and campus shifts so punches and leave calculations stay fair.
Manager self-service
HODs approve leave and review team attendance without waiting on a paper file.
LOP → salary linkage
Approved unpaid leave and attendance exceptions flow into the next payroll run automatically.
Compliance trails
Every punch override, leave decision, and payslip issue is timestamped for audits and inspections.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Onboard
Create the employee profile — role, campus, contract, and bank details.
-
02
Track presence
Capture daily staff attendance via devices or app; flag exceptions early.
-
03
Govern leave
Employees apply; managers/HR approve; balances and calendars update.
-
04
Run payroll
Close the period with attendance + leave inputs, then issue payslips.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
HR Manager
Owns directory, policies, attendance exceptions, and payroll close.
Principal / Director
Sees staffing strength, absence trends, and payroll readiness.
HOD / Manager
Approves leave and reviews department attendance.
Employee
Views punches, applies leave, and downloads payslips.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
One truth
for people data across campus
Faster
month-end salary close
Fewer
disputes on leave & late marks
“Attendance, leave, and payroll finally speak the same language. Our HR desk stopped being a reconciliation war room every month.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Is staff attendance separate from student attendance?
Yes. Student Attendance covers learners. Human Resources manages employee punches, shifts, and exceptions — while both can share device infrastructure where configured.
Can we use only leave and payroll without biometric attendance?
Yes. Start with directory + leave + payroll, then connect devices when ready. Modules share the same employee master.
Does this replace Staff Management, Leave, and Payroll pages?
Human Resources is the suite overview. Deep workflows also live in Staff Management, Leave Management, and Faculty Payroll for role-specific detail.
How does leave affect salary?
Approved LOP / unpaid leave can reduce the Faculty Payroll period automatically when policy mapping is enabled.
See HR attendance → leave → payroll in one demo
Walk a sample employee from punch and CL approval through a payslip cycle.