Monthly processing with allowances, deductions, loans and advances, reading the attendance and approved leave the institution already has.
Book a demoPayroll week starts with somebody asking HR for the leave taken, HR checking a planner, and the two disagreeing about a half day in the second week. The deduction gets argued about in front of the person it affects.
Then the payslips are printed, put in envelopes, and handed out - so anybody who loses one asks for a reprint, and anybody querying a figure from four months ago needs somebody to go and look.
When the salary run reads the same attendance and leave records the institution already keeps, there is nothing to ask for and nothing to reconcile.
Grouped by the job it does rather than listed as one long set of features.
Basic, allowances and deductions defined per role or per person, so a change is a setting rather than a spreadsheet formula.
Unpaid leave and absence read from the register the institution already keeps rather than from a separate list.
Staff loans with instalment schedules that deduct automatically until they are settled, and advance salary handled as such.
Generated per person per period, visible to that member of staff in their own portal rather than printed and handed out.
Statutory and institutional deductions applied by rule rather than calculated by hand each month.
Export the file your bank expects for a bulk transfer instead of entering each payment.
One salary for somebody who teaches at two sites, rather than a duplicate record and a manual merge.
What was paid, when and why, for as long as you are required to keep it.
Salary cost by department, campus or period, posting to accounting without a second entry.
The leave nobody agrees on. HR has a planner, the teacher has a count, payroll has a deduction, and all three differ. The argument happens on payday.
The loan that kept deducting. A staff loan is settled but the deduction runs one more month, because the schedule lived in a spreadsheet nobody updated.
The teacher at two campuses. One person, two timetables, one salary. Systems that assume one member of staff belongs to one site produce two half-payslips.
The payslip query from four months ago. Somebody asks why a deduction was made in April. If payslips were printed and handed out, answering means finding a paper copy.
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Runs the salary cycle, manages structures, loans and deductions, and produces the bank file.
See their own payslips and loan balance in their own portal. Nothing about anybody else.
Salary cost by department and campus, without asking for a breakdown to be prepared.
Salary and bank details are withheld from roles that have no reason to see them.
Attendance and approved leave come from the same records the institution already maintains, so the deduction agrees with the register rather than with somebody's recollection of it.
Salary cost posts to accounting from the run itself. The staff record supplies the contract terms. A leaver closes the payroll position at the same time their access ends.
That is the difference between payroll software and payroll as part of the institution: the inputs are already there and already agreed.
The parts of the institution this touches most.
The two-campus teacher, the half-settled loan, the disputed leave deduction. Those tell you more than a demo payslip.
Book a demo