No Export. No Re-Keying. No Reconciliation Week.
Attendance and payroll are the same system, so payable days are derived from the punches you already have — with every day's contribution visible and explainable.
The single most expensive step in most payroll cycles is the one nobody designed: someone exports attendance to a spreadsheet, adjusts it by hand for leave, holidays, half days and the exceptions they remember, and re-keys the result into payroll. That step is where the month's errors are introduced, and it is invisible in every process diagram because it happens in a spreadsheet on one person's laptop. It also destroys the audit trail — once a figure has been typed rather than derived, there is no way to explain it later beyond trusting whoever typed it. AttendancePay does not have that step, because attendance and payroll are not separate systems with an integration between them. Punches, approved leave, holidays, week-offs, shift assignments, overtime and regularizations are all evaluated against your configured attendance policy to produce a payable-days figure, and that figure carries its derivation. When someone disputes a payslip you open the derivation and see which rule produced which day, rather than recounting the month by hand and hoping to reach the same number.
What the spreadsheet step actually costs
Errors are introduced after the data was already correct
The attendance system had the right record. It was correct until it was exported, adjusted and re-typed. Every hand-off is an opportunity to transpose a number, and none of them leave a trace.
The derivation is lost
A payable-days figure that was typed cannot be explained. Months later, when an employee or an auditor asks how a number was reached, the honest answer is that someone worked it out at the time.
Policy is applied from memory
Whether a week-off between two absences is paid, whether a half day costs half a leave and half a day's pay, which record wins when a holiday and approved leave fall on the same date — all applied by whoever is doing the reconciliation, differently each time.
Exceptions surface during the run, not before it
Missing punches, employees with no salary record and unapproved regularizations are discovered while payroll is running, turning a routine correction into a deadline problem.
Late corrections rewrite issued payslips
An attendance record edited after payroll has run leaves the payslip and the attendance report permanently disagreeing, with neither being wrong.
How attendance to payroll works
- 1
Every day is resolved against the policy
For each employee and each date, the system evaluates shift assignment, punches, approved leave, holidays, week-offs and regularizations in a defined precedence order — so a date carrying several of these at once resolves the same way every time.
- 2
Policy rules are applied as configuration
Grace periods, half-day thresholds, late-mark rules, sandwich treatment of week-offs, minimum days to earn a paid week-off and overtime eligibility are settings rather than judgement calls.
- 3
Payable days are produced with a derivation
The result is a payable-days figure alongside a per-day breakdown showing what each date contributed and which rule decided it.
- 4
Exceptions are surfaced before the run
Employees with missing punches, no salary record, pending regularizations or no attendance at all are listed for review while there is still time to fix them.
- 5
The period locks on approval
Once payroll is approved the attendance period locks, so later edits cannot silently change an issued payslip; corrections carry forward as adjustments instead.
What you get
All attendance methods feed the same calculation
Biometric, kiosk, mobile GPS, face recognition and WhatsApp punches all produce attendance records in one place, so payroll does not care how someone marked attendance.
Configurable payable-days policy
Denominator basis, week-off treatment, sandwich rules, half-day thresholds, late-mark accumulation and holiday pay are all configured rather than assumed.
Defined precedence between conflicting records
A date carrying a holiday, a week-off, approved leave and a punch resolves through a stated precedence order rather than whichever check ran last.
Overtime carried through to pay
Overtime eligibility, rates and multipliers — including separate treatment for normal days, week-offs and holidays — flow into the payroll run where the policy allows it.
Joiner and leaver boundaries
Counting is floored at the date of joining and capped at the last working day, so pre-joining dates are never paid and never appear as absence.
Regularization with an audit trail
Missing punches are corrected through an approval flow that records the change and its reason against the attendance record, so the exception becomes data rather than an email.
Pre-run exception reports
Coverage and exception reports list who is missing what before the run starts, rather than during it.
Period locking
Attendance for an approved payroll period is locked, keeping the payroll register and the attendance report reconcilable.
Who this is for
See attendance to payroll on your own data
Start free for 7 days — no credit card. Or book a walkthrough with our team.
Frequently asked questions
Do we need to export attendance and import it into payroll?⌄
No. Attendance and payroll are the same system, so payroll reads the attendance records directly. There is no export, no adjustment spreadsheet and no re-keying step, which removes the place most payroll errors are actually introduced.
How is a payable-days figure explained to an employee?⌄
Each payroll entry carries a per-day derivation showing what every date contributed and which rule decided it — present, absent, approved leave, holiday, week-off, half day or regularized. A dispute becomes a question about whether the rule is right, rather than an argument about arithmetic.
What if a date has both approved leave and a punch?⌄
Precedence between conflicting records is defined in configuration rather than left to whichever check ran last. Holiday, week-off, approved leave and actual attendance resolve in a stated order, so the same combination always produces the same result.
Does it handle the sandwich rule?⌄
Yes, as an explicit setting that is off by default. When enabled, a week-off or holiday bracketed by unauthorised absence can be treated as unpaid. It is opt-in because it materially changes pay and should be a documented policy decision that employees can be told about, not a default they discover on a payslip.
What about employees who joined mid-month?⌄
Counting is floored at the date of joining, so dates before someone joined are neither paid nor counted as absence. Without that floor, a system that fills unmarked days as absent manufactures a fortnight of absence for every new joiner.
Can attendance still be edited after payroll has run?⌄
The period locks when payroll is approved. Corrections found afterwards are carried into the next cycle as an adjustment rather than rewriting an issued payslip, which is what keeps the payroll register and the attendance report reconcilable over time.