Procurement Challenges in NGOs (And Solutions)
The seven procurement problems that generate most NGO audit findings — emergency purchases, quotation theatre, conflicted committees, undocumented approvals — and the systems that actually fix them.
Ask any NGO auditor where findings concentrate and the answer is procurement. Not because NGO staff are dishonest, but because procurement is where donor rules, field urgency, and weak documentation collide. A training happens next week, the approved supplier is out of stock, someone buys from whoever can deliver — and six months later there is a finding titled "procurement procedures not followed".
Here are the seven challenges we see most, and the fixes that hold up in the field, not just in the policy manual.
1. Emergency purchases that bypass the process
The pattern: activity dates are fixed, procurement lead times are ignored, and "urgent" becomes the reason to skip quotations. Donors rarely accept urgency created by poor planning.
The fix: procurement plans tied to activity calendars, so purchase requests are raised when activities are approved, not the week they happen. And a real emergency lane in your policy — defined criteria, higher approver, documented justification — so genuine emergencies don't force people to break the normal process.
2. Quotation theatre
Three quotes are required, so three quotes appear — two from briefcase suppliers who were never going to win. The paperwork is complete; the competition is fake.
The fix: a maintained supplier database with performance history, RFQs sent to suppliers simultaneously through a system that timestamps responses, and side-by-side quotation comparison recorded with the award decision. Fake competition gets much harder when the trail is structured.
3. Approvals that live in hallways
A director says "go ahead" in a corridor or on WhatsApp; the paper approval is signed weeks later, after the goods arrived. Auditors read retro-dated approvals as fabricated ones.
The fix: approvals happen in-system, before commitment, with the approval chain defined per threshold — e.g. program manager to KES 50,000, procurement committee above KES 250,000. Request-to-approval workflows make the compliant path the convenient one.
4. Conflicted committees and single-sourcing
Committee members related to suppliers, the same vendor winning everything, no conflict-of-interest declarations on file.
The fix: declarations as a standing agenda item recorded per procurement, supplier award concentration reports (one vendor above ~30% of category spend deserves a look), and rotation of committee membership. Visibility is the deterrent — publish award summaries internally.
5. Receiving without verification
Goods arrive, someone signs, quantities and specs are checked never. Short deliveries and substitutions surface at year-end stock counts, unexplainable.
The fix: three-way matching — purchase order, delivery, invoice — with receiving recorded against the PO, and quality holds for goods that need inspection before acceptance.
6. Field procurement with cash
Remote activities run on cash advances; purchases happen at markets without receipts; liquidation becomes creative writing.
The fix: mobile-first documentation — photos of goods, market price attestations, GPS-stamped receipts captured at purchase time. Where suppliers can be pre-qualified even roughly, pay them directly via mobile money instead of routing cash through staff. Our guide on donor fund tracking covers the advance-liquidation discipline that pairs with this.
7. Procurement records scattered everywhere
The requisition is in a file, quotes in email, the committee minute in a shared drive, the delivery note in a store, the invoice in accounts. Assembling one procurement file for an auditor takes a day; assembling forty takes the audit.
The fix: one system where the requisition, quotes, comparison, approval, PO, delivery, and invoice are linked as a single chain. This is the difference between procurement software and a policy manual — the audit trail assembles itself.
What good looks like
You know NGO procurement is under control when
- Any procurement file can be produced, complete, in under ten minutes.
- Approval thresholds are enforced by the system, not by memory.
- Quotations are compared side-by-side with recorded award reasons.
- No purchase order is created without an approved requisition behind it.
- Supplier performance (delivery time, quality, price stability) is tracked and consulted.
- Emergency purchases are rare, justified, and separately reported.
- Committee conflict-of-interest declarations exist for every award decision.
Everything on this list is what our NGO procurement system was built to enforce — thresholds, RFQs, committee records, and self-assembling audit files.
Make the compliant path the easy path
AWRA OpsHub gives NGOs governed procurement — requisitions, RFQs, committees, receiving, and supplier performance in one auditable chain.
See NGO procurement in AWRAFrequently asked questions
What procurement thresholds should a Kenyan NGO use?
Follow your donor's rules where specified; otherwise a common local pattern is: petty purchases under ~KES 10,000 with one receipt; three quotations from ~KES 10,000–250,000; formal committee tender above that. Whatever you adopt, write it in your procurement policy and enforce it consistently — auditors flag deviation from your own policy as readily as from donor rules.
Do we really need three quotations for everything?
No — that is what thresholds are for. Requiring quotes for tiny purchases pushes staff to split purchases or fake paperwork. Set a sensible floor, and put your rigor where the money is.
How do we handle procurement in remote areas with informal suppliers?
Document reality rather than pretending formality: market price surveys, photos of goods, witness attestations, and GPS-stamped mobile records. Donors accept context-appropriate documentation far more readily than perfect paperwork that is obviously reconstructed.
What is three-way matching and why does it matter?
It is the check that the purchase order, the delivery, and the invoice agree before payment. It blocks the classic leakages: paying for undelivered goods, paying twice, or paying a price different from what was awarded.
