Casual, Daily & Piece-Rate Workers in Kenyan Payroll
Payroll systems are built around a monthly salary. A large part of Kenyan employment is not — it is daily, seasonal, per-crate or per-garment. What actually works for casual labour here, the two employment-type vocabularies that do not match, and the legal clock nobody is watching.
Almost every payroll product in existence assumes an employee has a monthly salary, and almost every Kenyan employer of any size has a group of people who do not. The packhouse takes on thirty people for six weeks of harvest. The construction site pays fundis by the day. The workshop pays per garment finished. The distributor takes on loaders when a container lands. These are real employees with real statutory obligations, and the field the software wants to put them in — a monthly basic salary — is the one thing that does not describe them.
The honest position is that this system holds a monthly salary figure and no other pay basis. Everything below follows from that, and the workarounds are better than they sound.
Four shapes of labour, against what exists
How each pay basis fares
| Pay basis | Native support | What you actually do |
|---|---|---|
| Monthly salary | Yes | No |
| Daily rate | No | No |
| Hourly rate | No | No |
| Piece rate — per crate, garment, sack | No | No |
Built and maintained Configurable by you, not maintained by us Not built
There is no pay-basis field, so none of these is a setting you switch. The pattern for all three unsupported bases is identical: compute the gross outside, bring one number in, and keep the workings where an auditor and the worker can both see them. That is less unsatisfying than it sounds — the calculation was always going to be a tally somewhere, and what you genuinely need from payroll is that the statutory side is right.
What you actually get, which is the part that matters
Where a casual worker's pay is handled well and badly
Counting the work
Days worked can come from attendance records, and hours from clock-in and clock-out — the tokenised time portal means a worker with no login and no smartphone of their own can still be clocked. Output, though — crates, garments, sacks — is counted nowhere. That is a tally sheet.
Turning work into gross pay
No rate × quantity anywhere. You multiply, and you keep the multiplication.
Getting the gross into the payslip
An ad-hoc earning queued into the period, with taxable and pensionable flags set correctly. One entry per worker per period.
Statutory deductions on that gross
PAYE, NSSF, SHIF and the housing levy computed on what you entered. This is the half that carries real penalty risk, and it does not care whether the gross came from a salary or a tally.
The record afterwards
A payslip with full line detail per run, a P9A at year end, and the worker able to fetch both from a PIN-gated portal without a login. For a seasonal workforce this is unusually valuable — they leave, and their record does not.
Read this as a boundary rather than a failure. The arithmetic of casual pay is genuinely yours; the statutory treatment, the payslip and the year-end certificate are genuinely handled. Given that the expensive mistakes in Kenyan casual labour are almost always statutory rather than arithmetical, that is the right half to have automated.
Two employment-type vocabularies, and they do not match
A detail worth knowing before you design your reporting, because it will otherwise be discovered by somebody halfway through building a headcount analysis.
There are two places an employment type is recorded, and they use different lists. The employee record offers permanent, contract, casual and intern. The employment contract offers permanent, fixed term, casual, internship and probation. Only permanent and casual appear in both. So "contract" at employee level and "fixed term" at contract level are the same idea under two names, "probation" exists as a contract type with no employee-level equivalent, and an intern is an "intern" in one place and an "internship" in the other.
Nothing is broken by this — both fields work, and both are honest about what they hold. But they will not reconcile in a report, and if half your organisation classifies people at employee level while the other half does it on the contract, your headcount by type will be wrong in a way that takes a day to unpick. Pick one of the two as your source of truth, write it down, and treat the other as decoration.
What AWRA OpsHub does today
- Casual as an employment type at both the employee and contract level — the one classification the two vocabularies agree on.
- Attendance and clock-in / clock-out records, including through a tokenised PIN-gated portal for workers with no login.
- Ad-hoc taxable earnings queued into a payroll period, one per worker, with taxable and pensionable flags.
- Full statutory treatment — PAYE, NSSF, SHIF, housing levy — on whatever gross you enter.
- Payslips with per-line detail and a P9A at year end, retrievable by the worker after they have left.
- Employment contracts as records in their own right, with type, dates and the basic salary figure.
What it does not do
- No pay basis other than a monthly salary figure. No daily rate, no hourly rate, no piece rate.
- No output or piece counting of any kind. Crates, garments and sacks are a tally sheet, and nothing in the system wants to know about them.
- No rate × quantity calculation, so every variable gross is computed outside and entered as one number.
- No casual-to-permanent conversion tracking, and nothing watching how long somebody has been engaged as a casual.
- No gang, crew or muster-roll concept — a group taken on together is thirty separate employee records.
- No daily cash-payment register, which is how a lot of casual labour is genuinely paid.
- The two employment-type lists do not match, so headcount by type depends on which field you chose.
The absence of conversion tracking is the one with legal rather than administrative consequences. Kenyan employment law limits how long a working relationship can sit in the casual category before it is treated as something more permanent, with the entitlements that follow. Nothing here watches that clock. Keep the engagement dates and take advice on the threshold — the cost of getting it wrong is an entitlements claim, not a tidiness problem.
Choosing how to run it
Best
Real employee records, gross computed on a tally, statutory in payroll
Every worker exists properly, gets a payslip and a P9A, and the statutory side is correct. The tally sheet is a spreadsheet with worker, days or units, rate and gross, kept per period and archived. This is more work at onboarding and it is the only version that survives an inspection or a claim.
Practical for short seasons
Employee records created once and reused each season
A packhouse taking on largely the same thirty people every harvest should not recreate them annually. Keep the records, keep the tokenised portal access, and reactivate. The second season costs a fraction of the first, which is the argument for doing the first one properly.
Minimum defensible
Records plus a signed daily muster sheet, nothing in between
If you cannot yet get the tally into a spreadsheet, at least have a signed sheet per day and one earning per worker per period. Crude, and it is a record that exists and reconciles.
Avoid
Paying casuals in cash outside payroll entirely
Extremely common and the single most expensive habit in this area. No payslip, no statutory deductions, no P9A, no defence when somebody claims six months of unpaid entitlements, and no evidence of what was actually agreed. The saving is a few hours of administration; the exposure is unbounded.
The tally sheet is a legal document, so treat it like one
Because the multiplication happens outside the system, the sheet showing days or units, rate and gross is the only evidence of how a worker's pay was arrived at. Have the worker sign it or acknowledge it, keep a copy per period, and attach it to the employee record where attachments are logged and retrievable. A disputed casual wage with no signed tally is decided on whose memory is more confident, and it will not be yours.
Our take
Accept that the gross is yours to calculate — there is no daily, hourly or piece rate and nothing counts output — and take the half that is genuinely handled: real employee records, correct PAYE, NSSF, SHIF and housing levy on whatever you enter, payslips and a P9A the worker can still fetch after the season ends. Keep the tally as a signed document attached to the record, because it is the only evidence of how the figure was reached. Pick one of the two employment-type fields as your source of truth so headcount reports mean something. And keep engagement dates deliberately, since nothing is watching how long somebody has been "casual" and that clock is the one with real legal consequences.
Casual labour, properly on the record
Real employee records, attendance and tokenised clock-in for workers without logins, ad-hoc earnings with full statutory treatment, and payslips and P9As that outlast the season — with a plain statement that daily, hourly and piece rates are calculated by you.
See plans & pricingFrequently asked questions
Can we pay workers a daily, hourly or piece rate?
Not natively. The only pay basis held is a monthly salary figure — there is no daily rate, hourly rate or piece rate, and nothing counts output such as crates or garments. For all three you compute the gross outside the system and enter it as one ad-hoc taxable earning for the period. The statutory deductions then run correctly on that figure.
So what does the system actually do for casual workers?
The half that carries the penalty risk. It holds real employee records and contracts, records attendance and clock-in even for workers without logins, applies PAYE, NSSF, SHIF and the housing levy to whatever gross you enter, and produces a payslip with full line detail plus a P9A at year end that the worker can fetch from a PIN-gated portal after they have left. The arithmetic is yours; the statutory treatment and the record are not.
Why do the two employment-type lists disagree?
They were built at different points for different purposes. The employee record offers permanent, contract, casual and intern; the employment contract offers permanent, fixed term, casual, internship and probation. Only permanent and casual appear in both. Neither field is broken, but they will not reconcile in a report — so choose one as your source of truth and treat the other as decoration, before somebody builds a headcount analysis on the wrong one.
Does anything track how long someone has been a casual?
No, and this is the gap with legal rather than administrative consequences. Kenyan employment law limits how long a relationship can remain in the casual category before it is treated as more permanent, with the entitlements that follow, and nothing here watches that clock. Keep engagement dates deliberately and take advice on the threshold — the downside is an entitlements claim.
Can we handle a gang or crew as one unit?
No. There is no gang, crew or muster-roll concept, so thirty people taken on together are thirty separate employee records. That is front-loaded work, which is exactly why seasonal employers should create the records once and reactivate them each season rather than recreating them — the second harvest costs a fraction of the first.
What is the risk of just paying casuals in cash outside payroll?
It is the most expensive habit in this area. No payslip, no statutory deductions, no P9A, and no evidence of what was agreed or paid — so a claim for months of unpaid entitlements is decided on whose recollection is more confident. The administration you avoid is a few hours per period; the exposure has no ceiling.
