People operations
HR and payroll for NGOs: people systems that survive audits
NGO HR has a requirement most HR software ignores: every salary is ultimately charged to donor money, so people data and funding data must reconcile. This guide covers what that means for employee records, leave, attendance, and payroll.
Employee records built for funded positions
In an NGO, a position exists because a budget line funds it. Employee records should carry contract type, duty station, and the funding allocation — which grants pay which share of the salary. When this lives in the system, the payroll-to-grant reconciliation that consumes finance teams every month becomes automatic.
Leave that follows policy, not memory
Leave types, accrual rules, and approval chains differ by organisation and country. The system should let HR define leave types and balances per policy, route requests through the same approval engine as everything else, and keep the decision history. Staff see their balances; managers see their team; HR stops being the bottleneck.
- Configurable leave types with balances and carry-over rules
- Requests from the employee portal with line-manager or role-based approval
- Decisions recorded with actor, timestamp, and comment
Attendance for offices and field sites
A head office can use IP-restricted check-in; a field site may need a QR kiosk or supervised self-attestation. The mistake is forcing one method everywhere. Attendance software for NGOs should let each site declare which methods it accepts, and feed the same timesheet records regardless of capture method.
Payroll with country rules as data
Tax brackets, social security contributions, and statutory deductions change yearly and differ by country. Systems that hard-code one country’s rules age badly. Look for payroll engines driven by versioned country rulesets, so a new tax year is a data update — and salary cost lands on the right grants automatically.
- Versioned rulesets per country and year
- Gross-to-net calculation with auditable line items
- Salary allocation across funding sources per employee
Frequently asked questions
Can staff request leave from their phone?
Yes — a self-service portal lets staff submit leave, see balances, and track approval status from any device, which matters for field teams without daily laptop access.
How does salary allocation across grants work?
Each employment record carries a funding split (for example 60% grant A, 40% grant B). Payroll applies the split, so grant-level personnel cost reports are produced without spreadsheet gymnastics.
What about volunteers and incentive workers?
Mixed workforces are normal in NGOs. Role-based access means volunteers can use the portal for the few workflows that apply to them without seeing employee-only modules.
Is e-signature supported for HR documents?
Approval signatures are stored in the user profile and applied to decisions where the organisation requires them, creating signed audit records.
Keep reading
What is NGO ERP?
NGO ERP explained: how grant-centric resource planning differs from generic business ERP, which modules matter, and how to evaluate a system for your organisation.
Grant management software
How grant management software works: awards, budget lines, amendments, spend control, and donor reporting — and what to look for when choosing a system.
NGO procurement
How NGO procurement software enforces donor compliance: purchase requests against budget lines, RFQs, bid comparison, purchase orders, and vendor management.