Paying casual workers in Kenya is routine for construction, retail, logistics, and seasonal work — but it is also where payroll risk concentrates: weak records, informal rates, and M-Pesa trails that do not reconcile back to cost centres. This guide is for finance and ops teams who need audit-ready discipline without slowing down field pay.
Who counts as “casual” in practice
Labels vary by industry, but for internal controls you should treat someone as casual or daily-rated when:
- They are paid by day, shift, piece, or task rather than a fixed monthly salary.
- They may rotate across sites or supervisors.
- They are not on the same statutory and contractual track as core salaried staff.
Your HR and finance policies should define the boundary; the important part is that every payment has a paper and digital trail tied to an approved rate and attendance.
What to capture before you disburse
Minimum viable records for each casual worker (or crew) per pay cycle:
- Identity reference — national ID or staff ref used consistently in your system.
- Rate agreement — daily/shift/piece rate, currency, and who approved it (supervisor or procurement).
- Attendance or output — signed sheet, gate log, piece count, or system clock aligned to the rate type.
- Site or cost centre — so GL allocation and project P&L stay honest.
- Payment channel — M-Pesa number registered to the worker (or documented exception).
When audits or disputes arise, this bundle matters more than the payment itself.
M-Pesa workflows finance teams should standardise
Most teams use B2C to phones for smaller, frequent payouts. Whatever rail you use, standardise:
- Batch naming — statement text that maps to payroll run ID and period.
- Maker–checker — separate preparation and approval for file uploads where possible.
- Same-day cut-offs — agreed time after which the run moves to the next business day.
- Failure handling — retries, reversals, and how unclaimed funds are cleared.
Export or API-backed reconciliation from your telco or bank statement should land in the same folder as the attendance register for that cycle.
Reconciliation checklist (per run)
- Sum of approved lines in your payroll file = sum of successful M-Pesa results (plus documented exceptions).
- Every phone number matches the worker master or a one-off exception log with sign-off.
- GL posting matches the cost centre / project tags on the register.
- Any reversals or partial pays have a ticket reference and updated net due.
Common pitfalls in Kenya
- Paying from personal numbers — breaks corporate traceability; use business-tagged flows.
- Mixing casual and supplier payments — use separate workflows so withholding and VAT treatment stay clear.
- Missing statutory context — casual regimes still interact with labour and tax rules; keep legal review on retainer for edge cases.
- Spreadsheet-only master data — version chaos; move approved rates and IDs into a system of record.
FAQ
Do we need a written contract for every casual? Policy-dependent; even short engagements benefit from a rate card and sign-in discipline.
How do we prove payment if the worker disputes the amount? M-Pesa confirmation + approved attendance + rate card for that period.
Can we automate bulk M-Pesa payroll? Yes — with the right controls: file validation, limits, and reconciliation reports. (See also Centy’s guide on bulk M-Pesa and payroll disbursements in Kenya.)
Closing
Casual pay is not “informal pay” — it is high-volume, high-risk pay that deserves the same rigour as salaried runs, with lighter templates. Standardise records, standardise M-Pesa batch discipline, and reconcile every cycle to the same IDs you used in the field.
Centy helps finance and people teams run payroll, payouts, and compliance workflows built for Kenya — including M-Pesa at scale. Request a demo to see how your stack could look end-to-end.
Leave a Reply