Leave & Attendance Records Payroll Can Actually Use
Leave is the first thing employees dispute and attendance is the first thing that quietly corrupts payroll. Both are the same problem: a record that either exists at the moment it happened, or gets reconstructed later from goodwill and memory.
Ask a Kenyan employer how much annual leave a particular employee has left and you will usually get one of three answers: a confident number that turns out to be wrong, an honest "let me check with HR," or a number from a spreadsheet that has been maintained by three different people using two different accrual assumptions. All three are the same answer, which is that nobody actually knows.
That matters more than it sounds. Leave is a liability — untaken days are money the business owes in time or in cash — and it is the single most common thing employees raise formally. Attendance matters for a harder reason: the moment pay depends on presence, an attendance record stops being an administrative register and becomes a payroll input with statutory consequences.
Why leave goes wrong
Not through dishonesty. Through arithmetic maintained by hand across a year.
- Accrual is applied inconsistently. Someone computes monthly, someone else annually, and a mid-year joiner is pro-rated by a rule nobody wrote down.
- Approval happens off the record. Leave is agreed verbally or by message, taken, and recorded later — or not at all, if the person who agreed it forgets.
- Carry-over rules are folklore. What happens to untaken days at year end differs depending on who you ask, and the policy document says something a third thing.
- Types get conflated. Annual, sick, maternity, paternity, compassionate and unpaid all behave differently, and a single "days off" column erases the difference.
- Nobody sees the liability. The total untaken balance across the business is a number most employers have never seen, which means it has never been provided for.
The fix is not more diligence — it is moving the arithmetic into rules. Leave types with their own behaviour, accrual computed by rule rather than by person, requests approved on the record with a date and a name, and a balance that is derived rather than typed. Once that exists, the leave question has one answer and it is the same answer whoever asks.
A leave balance that someone maintains is an opinion. A leave balance the system derives is a fact — and only one of those survives a formal dispute.
Attendance is a payroll input, not a register
Plenty of Kenyan employers keep attendance for its own sake — a book at the gate, a sign-in sheet, a supervisor's notebook. That is fine until pay depends on it, and then the standard changes completely, because an attendance record has become the evidence behind a payslip line and therefore behind a statutory deduction.
The three cases where this bites are overtime, unpaid absence and casual or shift work. In each one, a payslip line traces back to an attendance entry — and if that entry arrived as a WhatsApp message from a supervisor on payroll day, the trace ends in a chat log. That is not a record you want to rely on when an employee disputes a month's pay.
Attendance as a register
- Captured on paper or in a book, at one place
- Overtime reaches payroll as a message or a verbal total
- Corrections are made by editing the original entry
- Nobody can reconstruct why a payslip line was what it was
- Disputes are settled by whoever is more certain
Attendance as a payroll input
- Captured against the employee, dated, at the point it happened
- Overtime flows into the run as data, once, from one source
- Corrections are regularisations — the original stays, the change is recorded with a reason
- Every payslip line traces to an attendance entry you can point at
- Disputes are settled by looking
That regularisation point is worth dwelling on. Attendance always needs correcting — a device was down, someone forgot, a shift changed at short notice. The question is whether a correction overwrites history or sits on top of it. Overwriting means you can never explain a past payslip; recording the correction with a reason and an approver means you always can.
What good looks like, concretely
The working setup
- Leave types defined separately — annual, sick, maternity, paternity, compassionate, unpaid — each with its own accrual and approval behaviour
- Accrual computed by rule, including pro-rating for mid-period joiners and leavers, so nobody does the arithmetic by hand
- Requests approved on the record by someone other than the requester, with dates and a trail
- A carry-over rule that is written down and applied by the system at year end, not negotiated annually
- Attendance captured against the employee at the point it happens, including field and multi-site staff
- Corrections as regularisations — reason, approver, timestamp; the original entry preserved
- One flow into payroll, so overtime cannot arrive twice through two channels and be paid twice
- A visible total leave liability, so untaken days are a number finance has seen rather than a surprise at exit
The double-payment trap
One specific failure is worth naming because it is common and expensive. Overtime is claimed through a form, and separately mentioned by the supervisor to whoever runs payroll. Both are honest. Both get paid. Nobody notices because the payslip is plausible and the employee is not going to raise it.
This is prevented structurally, not by care: there is exactly one path from attendance into payroll, and anything arriving by another route is not an input. The four-number reconciliation before approving a run — headcount, gross, deductions, net against last period — is what catches it when it happens anyway. The full sequence is in PAYE, NSSF, SHIF and housing levy.
What we do and do not do
What AWRA OpsHub does today
- Leave types with their own accrual and approval rules, and balances derived rather than maintained.
- Leave requests approved on the record, with dates, approver and history.
- Attendance capture against the employee, including multi-site work.
- Regularisation — corrections recorded with reason and approver, original entries preserved.
- A single flow from attendance into payroll, so variable pay traces to a record.
- Employee self-service, so balances and requests do not route through one person's inbox.
What it does not do
- We do not supply biometric hardware. Where you use devices, that is your hardware and your integration decision.
- We do not write your leave policy — accrual, carry-over and approval chains are yours to define.
- We do not advise on employment law. Statutory leave entitlements and their interpretation are for your HR adviser or advocate.
- We do not do shift rostering as a scheduling engine; attendance records what happened rather than planning who works when.
Statutory leave entitlements are set in law and change. Confirm current entitlements and obligations with your HR adviser or advocate — nothing here is legal advice.
Where to start
-
Write the policy down before configuring anything
Accrual per type, pro-rating, carry-over, who approves what. One page, agreed. Most leave disputes are policy ambiguity rather than system error.
-
Establish opening balances honestly
Agree each employee's current balance in writing before go-live. This is the uncomfortable step everyone wants to skip, and skipping it poisons the first year.
-
Turn on requests and approvals
Stop verbal leave immediately. This is the behaviour change; the software is the easy part.
-
Add attendance where pay depends on it
Start with the staff whose pay varies — overtime, casuals, shifts — rather than trying to track everyone at once.
-
Connect it to payroll and close the other routes
One path from attendance to payslip, and no side channels. Then run the pre-approval reconciliation every period.
Our take
Fix leave before attendance and attendance before payroll, and write the policy down before you configure any of it. Employers who do this in order stop having leave disputes within a quarter. Employers who buy payroll first get a fast calculator fed by the same messages and notebooks they had before, and then blame the software.
See leave and attendance that payroll can use
Leave types with real accrual rules, balances derived not typed, attendance captured at the point it happens, and one clean path into the payroll run.
Explore leave & attendanceFrequently asked questions
How are leave balances calculated?
By rule rather than by hand. Each leave type carries its own accrual behaviour, including pro-rating for people who join or leave mid-period, and the balance is derived from accrual less approved leave taken. That means the balance is the same number whoever asks and whenever they ask, which is the property that ends most leave disputes before they become formal.
What happens to untaken leave at year end?
Whatever your written policy says — carry-over in full, carry-over capped, forfeit, or pay out. The important part is that the rule is defined once and applied by the system rather than renegotiated each December, because carry-over folklore is one of the most reliable sources of leave disputes. Statutory minimum entitlements apply regardless of policy, so confirm those with your HR adviser or advocate.
Can attendance be corrected after the fact?
Yes, through regularisation rather than editing. A correction records the reason, the approver and the timestamp while preserving the original entry, so a past payslip line can still be explained. Attendance always needs correcting — devices fail, people forget, shifts change — and the difference between a system you can audit and one you cannot is whether corrections sit on top of history or overwrite it.
Do we need biometric devices?
Not necessarily, and we do not supply them. Attendance can be captured through the system directly, including for multi-site and field staff. Where you already use devices or want to, that is your hardware and integration decision. Start with the staff whose pay actually varies with attendance rather than trying to instrument everyone, because that is where the payroll risk sits.
How do we stop overtime being paid twice?
Structurally: there is exactly one path from attendance into payroll, and anything arriving by another route — a message to the payroll administrator, a note from a supervisor — is not an input. Double payment almost always happens because a claim travelled through both a form and a conversation, with both parties acting honestly. The pre-approval reconciliation of headcount, gross, deductions and net against the previous period catches it if it slips through anyway.
