Every NGO finance team in Africa has the same Tuesday morning. The PEPFAR quarterly report is due Friday. Global Fund wants their PUDR by next week. The EU's Annex VI template arrived a month ago and somebody hasn't started. And the spreadsheet that holds all the answers is one wrong VLOOKUP away from a number nobody can defend in an audit.

This guide is about what changes when donor reporting stops being an Excel job and becomes a query against a system that already knows the answer. It's written for NGO and INGO finance directors, grants managers, and HR leads — the people doing the rebuild every quarter.

The real problem isn't the formats. It's the source data.

Most NGO finance teams can build any donor format if they have clean source data: every salary payment, tagged to a grant, with the FX rate used, the cost category it falls under, and supporting payslip evidence. That source data is usually scattered across a payroll system that doesn't know about grants, a grants tracker that doesn't know about salaries, and a set of timesheets that may or may not have made it into anybody's spreadsheet.

Until the source data is grant-attributed at the moment of payroll — not reconstructed at quarter-end — every report will require manual rebuild. That's where most NGO finance teams lose 3-5 days per cycle.

What grant attribution actually means in practice

A field officer in Kenya earning KES 85,000 monthly might be funded 60% by PEPFAR, 30% by Global Fund, and 10% by EU core. Those percentages should be:

Configurable per employee, per period. Allocations change as grants expand or contract. Q1 might be 60/30/10; Q2 might be 50/40/10 when a new grant cycle starts.
Effective-dated. Every change is timestamped so you can rebuild any past payroll's attribution exactly as it was at the time.
Audit-traceable. Each allocation links back to the source document — donor letter, internal approval, board minutes.
Available to payroll as input, not bolted on after. The May payslip already contains the grant split. Reports are queries against that, not reconstructions.

See how this looks in production on the NGOs industry page — including a worked example with three concurrent grants.

PEPFAR reporting: cost categories and the FY mismatch

PEPFAR uses the US Government fiscal year (October to September) and requires expenditure analysis by cost category: Care & Treatment, Prevention, Above-Site, OVC, HIV Testing Services, plus management and administration. Each salary attribution must roll up cleanly to one of these.

The category isn't always the same as the grant. A community health worker might be funded by PEPFAR (the grant), working on Care & Treatment (the cost category), reporting through the Above-Site administrative structure. The system needs to capture all three.

Practical check: when the PEPFAR auditor arrives, can you produce a single export showing every salary payment in the period, attributed by grant, by cost category, and by support site? If that's a one-click export, you're fine. If it's a rebuild, you have a system gap.

Global Fund: modules, interventions, and the PUDR

Global Fund expenditure reporting works through modules (HIV/AIDS, TB, Malaria, RSSH, etc.) and interventions inside each module. The Progress Update / Disbursement Request (PUDR) template wants expenditure detail by module per quarter. Your payroll allocation needs the same granularity.

The hard part: a senior nurse working on HIV/AIDS and TB shouldn't be split 50/50 if her actual time was 70/30. Project timesheets — submitted weekly by field staff, tagged to module and intervention — are the only honest way to attribute. Anything else is an assumption that won't survive an in-country verification.

USAID, EU, and FCDO: the rest of the donor mix

USAID requires line-item budget vs. actual reporting per cooperative agreement, with cost-share documentation if matching is part of the award. The EU's General Conditions require expenditure reporting per heading (A.1 Staff, A.2 Travel, etc.) with the salary slip backup attached for direct project staff. FCDO is more flexible but expects outputs- and outcomes-based reporting that needs the staff attribution to roll up correctly.

The common pattern: every donor wants the same source data — salary, attributed to their grant, in their format — and every donor wants it differently. The system needs templates per donor, with the source data already in place.

What auditors actually check

From our work with NGO finance teams across Kenya, Uganda, Tanzania, Ethiopia, Nigeria, Ghana and South Africa, three things come up in nearly every donor audit:

Tracing a sample payment back to source. The auditor picks a salary line from the quarterly report and asks for: the original payslip, the timesheet that drove the hours, the grant allocation rule in effect that month, and the approval trail for the rate. You should be able to produce all four in under a minute.
FX consistency. If the grant ledger is in USD and the salary was paid in local currency, what rate did you use, when was it set, who approved it? Spot rate, monthly locked rate, or custom — the policy needs to be documented and applied consistently.
Cost-allocation methodology. Why is this employee 60% PEPFAR? Is it because of an annual approval (acceptable for back-office staff), a quarterly review (acceptable for programme leads), or weekly timesheet data (required for direct service staff)? Each level has its own audit standard.

The reporting cadence that actually works

The pattern we see in NGO finance teams that have moved past spreadsheets:

Monthly: Payroll runs with grant attribution already in place. A management report shows budget vs. actual per grant, with variance flagged.
Quarterly: Donor reports generate per template. Finance reviews, signs, submits. Total time: half a day per donor, not five days.
Annually: Audit pack pre-built before the auditor arrives. Sample-trace queries answer in seconds.

What to do if you're still in spreadsheets

The shortest path forward isn't a 12-month enterprise project. It's:

Map your current grant portfolio — name, donor, amount, start, end, cost categories used.
Map your current staff by attribution — who is on which grant, at what percentage.
Pick one upcoming reporting cycle as your pilot. Don't try to backfill historical data; start clean from a chosen month.
Run the next month's payroll inside the new system, in parallel with your existing process. Reconcile the two outputs.
From the second month, run only inside the new system. Reporting goes from rebuild to query.

If you'd like to see how SmartHR Africa handles this end to end — including the donor-format templates and the audit-trace workflow — book a working demo with your real grant portfolio. Or jump straight to the NGO industry page for the full feature list and country focus.

PEPFAR, Global Fund and USAID Payroll Reporting: a Practical Field Guide for NGO Finance Teams