Payroll is one of the highest-stakes recurring processes in any business. I have built, extended, and supported payroll systems in production — covering the full employee lifecycle from onboarding through attendance, leave, overtime, and termination, with each step feeding correctly into the pay run. If your payroll is still a spreadsheet, or a system you cannot change without calling a vendor, I can help you fix that.

What I Build Into Payroll Systems

The payroll systems I work on handle the full employee lifecycle: employee records, contracts, attendance, leave and overtime management, configurable deduction and allowance rules, pay run processing, and the audit trail that shows exactly how every figure was calculated.

Compliance in Kenya means PAYE following current KRA schedules, NSSF under the current regulations, SHIF, and Housing Levy. Each of these changes over time — I build the calculation engine against configurable schedules so when rates or rules are updated, you change the configuration, not the code. The same engine supports Uganda and Tanzania compliance where needed, with each country's rules applied independently per entity.

Template-Driven Rules

Different employees have different terms: different allowances, overtime rates, leave entitlements, and deduction structures. A payroll engine that requires a developer to add each variation is too rigid for real operations. I build template-driven rule engines your HR team can configure: define an allowance or deduction type once, assign it to the relevant employee groups, and the engine applies it consistently across every pay run.

Attendance, Leave, and Overtime

Payroll accuracy depends on what happened during the pay period. Systems I build include attendance tracking that feeds directly into pay calculations — whether from biometric device imports, system clock-in/clock-out, or HR-approved timesheets. Leave management tracks balances and accruals so the correct days are deducted and carried forward. Overtime is configured per role or grade and applied automatically.

Reports and Audit Trails

Every pay run produces the reports your organisation needs: payroll summary, individual pay component breakdown, and deductions register. Every change to any pay record is logged — who changed it, what it was before, what it became. That log is how you defend every figure during an audit or a statutory review.

Integrations Into Payroll

Payroll does not sit in isolation. I integrate payroll systems with HR workflows, attendance devices, and finance platforms so data flows between them rather than being re-keyed from reports. If the organisation runs ERPNext, I extend the payroll module within that environment rather than building a parallel system.

ERPNext Payroll

I have extended and administered ERPNext/Frappe deployments in production, including payroll configuration for Kenya. If your organisation already runs ERPNext, adding or improving the payroll module within that environment is often the right approach. I have worked on ERPNext implementations covering Kenya, Uganda, and Tanzania.

How I Deliver This

1

Current state review

Map the existing process, find the gaps, agree on scope before writing code.

2

Rules and compliance design

Deduction types, allowance templates, and compliance schedules documented before building.

3

Engine development

Configurable payroll engine built with automated calculation tests against known scenarios.

4

Data migration

Employee records and historical data migrated and validated before go-live.

5

User acceptance

HR and finance teams verify calculations against known pay runs before the system goes live.

6

Go-live

Phased transition with your team supported through the first live pay runs.

Frequently Asked Questions

Both. For organisations already on ERPNext I extend the payroll module within that environment. For others I build a standalone system. The approach depends on what you already have and what your team needs to maintain.

Yes. The calculation engine applies each country's statutory rules independently per entity. An employee in Kenya gets PAYE under KRA schedules; an employee in Uganda gets PAYE under URA schedules. Consolidated reports are available across all entities.

Rates are stored as configuration, not hardcoded. When KRA, NSSF, or SHIF publishes updated schedules, the configuration is updated and the next pay run uses the correct figures automatically.

I can build integrations into finance systems and ERPNext. The specific approach depends on the platform — share what you use and we can assess what makes sense.

Role-based access means each user sees only what their role permits. Every change is logged with who made it and when. Access to pay data is restricted to authorised users only.

What I Can Build

  • Full employee lifecycle management
  • Attendance, leave, and overtime tracking
  • Template-driven payroll rule configuration
  • PAYE, NSSF, SHIF, Housing Levy (configurable schedules)
  • Multi-country: Kenya, Uganda, Tanzania
  • Pay run reports and deductions register
  • Full audit trail on all payroll changes
  • ERPNext/Frappe payroll module development
  • HR and finance system integration
  • Role-based access control

Tech Stack

Laravel PHP 8+ MySQL React.js ERPNext / Frappe

Ready to start?

Tell me about your project and I'll outline a realistic scope and approach.

Get a Quote