Solutions
Attendance that reaches the payslip
Biometric and card attendance feeding shift rosters, overtime at legal multiples and leave accrual, so paid days are never typed twice.
The problem
Attendance lives on a device and payroll lives in a spreadsheet, so somebody retypes one into the other every month. The retyping is where the arguments come from: a missing half-day, an overtime hour at the wrong rate, a leave balance nobody can reconcile.
What changes
The same system records attendance and runs the payroll, so paid days are never entered twice. Shift rosters, night and holiday differentials, overtime at legal multiples and leave accrual all reach the payslip as figures with a rule behind them.
How it works
- Attendance arrives from biometric devices or cards, against the roster the employee is actually on.
- Shifts, night differentials and holiday rates are applied from the calendar for that establishment.
- Overtime is calculated at the legal multiple and held until somebody approves it.
- Leave accrues and is drawn down on the same record, so the balance is one number rather than two.
- The payroll run reads all of it directly, and each figure on the payslip links back to the rule that produced it.
What you get
- Paid days are never typed a second time, so the commonest payroll argument disappears.
- Overtime at the legal multiple, approved before it is paid rather than questioned after.
- Provincial holiday calendars per establishment, not one setting for the whole company.
- Leave accrual and encashment on the same record the payslip reads.
In practice
Who it is for, and what setup involves
What the payroll run reads, and what it does not
It reads the attendance record: the shift somebody was rostered on, the hours the device recorded against it, the leave they had already taken, and the overtime an approver signed off. Those become paid days without anybody transcribing a monthly summary, which is where the arithmetic usually goes wrong.
What it does not read is a device export somebody has tidied up first. If the roster is wrong, the payslip will be wrong in exactly the way the roster is wrong, and it will say so — the figure links back to the shift that produced it, so a dispute ends at a roster rather than at somebody’s recollection.
Overtime waits for a person
Overtime is calculated at the legal multiple, but it does not reach a payslip until an approver has seen it. That is deliberate. An unusual month is nearly always either a genuine push or a rostering mistake, and both are cheaper to resolve before the bank file is generated than after the money has moved.
Night and holiday differentials come from the calendar of the establishment the employee is registered at, not from one company-wide setting. A group with branches in two provinces does not have one holiday list.
Where this stops
It does not decide whether an absence was authorised. Somebody still has to mark leave as approved, and if nobody does, the day is unpaid and the employee will ask why — correctly. The system removes the retyping, not the supervision.
It also does not import years of historical attendance. Balances can be opened at a starting figure so the first month is right; reconstructing three years of a biometric device’s logs is a data exercise, and we quote it separately rather than implying it is free.
Questions people ask before they buy
Start working within Twenty minutes, your own data, no slides.
Bring a month of your own sales, a payslip you argue about, or last term’s fee sheet. We will show you what it looks like in MjFour.