Payroll & PAYE/NSSF in Uganda: Getting the Basics Right
PAYE, NSSF and Local Service Tax are where Ugandan payroll gets fiddly. What a system genuinely helps with, what it does NOT automate the way Kenya's statutory payroll is automated, and why "confirm with URA" is the most honest line in this guide.
Payroll is the process businesses most want to "just automate," and the one where over-promising does the most damage. In Uganda, getting an employee's net pay right means handling PAYE, NSSF and Local Service Tax correctly, month after month, as rates and rules shift. This guide is deliberately careful about what software does and does not do here — because a wrong assumption about statutory automation is not a bug, it is an unpaid liability with penalties attached.
The honest headline, up front
AWRA OpsHub supports payroll operations, but Ugandan statutory automation (PAYE, NSSF, LST) is NOT built to the turnkey standard of our Kenyan payroll (PAYE/NSSF/SHIF). You configure the deductions to current requirements; the system computes and records against your configuration. Treat any vendor claiming fully automatic Ugandan statutory filing as something to verify in writing — and confirm all rates, bands and dates with URA/NSSF or your accountant. This is not tax advice.
What Ugandan payroll has to get right
- PAYE — pay-as-you-earn income tax, calculated on a banded scale that URA sets and revises. Getting the bands and reliefs right is the core of accurate net pay.
- NSSF — National Social Security Fund contributions, employer and employee portions, on qualifying earnings.
- Local Service Tax (LST) — a local government levy on earnings, deducted on a defined schedule.
- Accurate payslips — every employee should receive a clear breakdown of gross, deductions and net, and you should be able to reproduce any month on demand.
The exact rates, thresholds and filing dates for each of these change, and are outside the scope of any software vendor to state as settled fact. Confirm them with URA, NSSF, or your accountant every time they might have moved.
What a system genuinely helps with — and what it does not
| Task | Honest status in AWRA | What you should do |
|---|---|---|
| Employee records & contracts | Supported | Maintain staff master data as the payroll source of truth |
| Gross-to-net calculation | Supported (you configure the rules) | Set PAYE bands, NSSF and LST to current requirements |
| Payslip generation | Supported | Produce and reproduce clear payslips per period |
| Payroll records & reporting | Supported | Keep an auditable history of every run |
| Automatic URA/NSSF statutory filing | NOT built for Uganda | File through the official channels; use system reports as your source |
| Auto-updating statutory rates | NOT automatic — you maintain them | Update bands/rates when URA/NSSF revise them |
Why we say this plainly instead of claiming "fully compliant"
Kenyan statutory payroll (PAYE, NSSF, SHIF) is built into AWRA to a turnkey standard because that is our home market and we maintain it closely. Uganda is supported at the operations level — records, calculation against your configuration, payslips, reporting — but not to that same automated statutory standard. Saying so is not a weakness; it is the difference between a vendor you can trust with a liability and one you cannot. A payslip that is wrong because a band was assumed rather than confirmed is your penalty to pay, so the correct posture is: configure carefully, verify with the authority, and keep the records clean.
For teams that also run Kenyan operations, NGO payroll in Kenya shows what the turnkey standard looks like — and, by contrast, exactly what you are configuring manually for Uganda. The broader system-selection view is in the Uganda ERP buyer's guide.
Payroll operations you can keep clean and auditable
Employee records, gross-to-net you configure to current rules, clear payslips and a full run history — with an honest line on what is and is not automated for Uganda.
See AWRA for UgandaFrequently asked questions
Does AWRA calculate Ugandan PAYE, NSSF and LST automatically?
It calculates gross-to-net against the PAYE bands, NSSF and LST rules you configure — the computation and payslips are supported, but the statutory rules are maintained by you rather than automated to the turnkey standard of our Kenyan payroll. Set them to current requirements and confirm rates, bands and dates with URA/NSSF or your accountant, since these change.
Will it file our returns with URA and NSSF for us?
No — automatic Ugandan statutory filing is not built. You file through the official URA and NSSF channels, using the system's payroll reports as your accurate source. Be sceptical of any vendor claiming fully automatic Ugandan statutory filing, and ask them to prove it in writing.
What happens when URA changes the PAYE bands?
You update the bands in your payroll configuration so subsequent runs use the new figures. Because the rates are maintained by you rather than auto-updated for Uganda, it is worth building a habit of checking with URA or your accountant whenever a change is announced, and updating before the next run.
Can one system run Kenyan and Ugandan payroll together?
Yes, with an important caveat: Kenyan statutory payroll is built to a turnkey standard, while Ugandan payroll is supported at the operations level with statutory rules you configure. Running both in one system keeps records consolidated, but treat the two countries' statutory handling differently and verify the Ugandan side against URA/NSSF.
