Payroll runs and approvals
Prepare, check and approve a run, with every figure explained and the approved version locked.
At launch. Core and Plus.
| Employee | Gross | NSSF | SHIF | Levy | PAYE | Net |
|---|---|---|---|---|---|---|
| A. Wanjiru | 120,000.00 | 6,480.00 | 3,300.00 | 1,800.00 | 24,909.35 | 83,510.65 |
| B. Otieno | 85,000.00 | 5,100.00 | 2,337.50 | 1,275.00 | 15,269.60 | 61,017.90 |
| C. Mutua | 60,000.00 | 3,600.00 | 1,650.00 | 900.00 | 8,538.35 | 45,311.65 |
| D. Achieng | 45,000.00 | 2,700.00 | 1,237.50 | 675.00 | 4,499.60 | 35,887.90 |
Checks before anyone approves
A run stops on the errors that cause penalties and warns on the ones that need a second look.
- Missing KRA PIN or TIN, bank account or mobile-money number
- Basic pay below the minimum wage for the occupation and zone
- Total deductions above two-thirds of pay
- Differences from last month, by person and by amount
Approvals that fit the size of your team
By default, the person who prepares a run sends it to someone else to approve. In a small team one person can do both: the owner switches this on in settings, and every run approved that way is marked as self-approved in the audit trail. Core has one approval step. Plus adds several steps, amount thresholds and escalation.
Locked means locked
An approved run doesn't change. A correction creates a new version, keeps the old one, and reverses and re-posts the ledger entry so your books never hold a duplicate.