Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
NGO procurement
Procurement your donors can audit in minutes, not days
From requisition to receipt, every step — approvals, quotations, committee decisions, deliveries — linked in one chain that assembles its own audit file.
Sound familiar?
If any of these ring true, you are exactly who this was built for.
Retro-dated approvals
The go-ahead came verbally; the signature came after delivery. Auditors read that as fabrication.
Quotation theatre
Three quotes on file, but two were never real competitors — and donors are getting better at spotting it.
Scattered procurement files
Requisition in a cabinet, quotes in email, minutes on a shared drive, invoice in accounts.
Emergency purchases as the norm
Poor planning turns every activity into an urgent purchase that bypasses the policy.
What you get with AWRA OpsHub
Each capability links to a deeper feature tour.
Supplier and requester queries, tracked
Questions about a request or an order become tickets with an owner, a priority and an SLA clock, rather than a mail thread that ages until somebody asks about it in a meeting.
The approvals queue a grant audit asks for
Requests, RFQs, quotations and purchase orders queue in one Approvals Hub with the person and timestamp on every decision. Delayed orders sit in their own Control Tower lane, so a late delivery is visible before the reporting deadline.
Requisitions & threshold approvals
Staff raise requests; approval chains enforce your policy thresholds automatically.
RFQs & quotation comparison
Send RFQs to suppliers simultaneously, compare responses side-by-side, record the award reason.
Purchase orders & three-way matching
PO, delivery, and invoice must agree before payment — undelivered goods never get paid.
Supplier performance
Delivery time, quality, and price stability tracked per vendor — award concentration visible at a glance.
Procurement plans
Tie purchasing to activity calendars so requests are raised when activities are approved, not the week they happen.
Documents & exceptions
Quotes, minutes, delivery notes, and invoices attached to the transaction they belong to — exceptions flagged.
How teams get started
1
Load your policy thresholds
Petty cash, three-quote, and committee levels configured to match your procurement manual.
2
Run a live procurement
One real purchase goes request → approval → RFQ → award → receipt in the system.
3
Pull the audit file
Open the finished procurement and see the complete chain — the file assembled itself.
Guides from our blog
NGOs & Nonprofits
Procurement Challenges in NGOs (And Solutions)
The seven procurement problems behind most NGO audit findings — emergency purchases, quotation theatre, undocumented approvals — and the fixes that hold up in the field.
Read
NGOs & Nonprofits
Best ERP Software for NGOs in Kenya (2026)
What NGO teams should look for in an ERP — donor fund segregation, procurement governance, asset registers, and Kenya-specific compliance — with a practical evaluation checklist.
Read
NGOs & Nonprofits
How NGOs Can Track Donor Funds Properly
A practical system for tracking restricted funds from grant agreement to donor report — fund segregation, budget lines, burn rates, and audit-ready advances.
Read
NGOs & Nonprofits
Who Else Is on That System? Answering the Donor’s Data Clause
How to read the data protection annex in a grant agreement, which questions hosting answers and which stay yours, and how to answer the who-else question in one sentence for every funder.
Read
Procurement Insights
Nobody Checks In a Cleaning Contract
A service on a purchase order is now received by a delivery confirmation, not a check-in. Nothing enters stock, the cost is booked when the work is confirmed, and the people who sign for goods sign for work.
Read
Procurement Insights
A Three-Way Match for Work You Cannot Count
A delivery confirmation counts as received in the three-way match, so an order is not ready to pay while a service on it is unconfirmed, and paying past the match needs its own permission and a reason.
Read
Questions we are asked here
Frequently asked questions
Can approval thresholds match our procurement manual?
Not by value, and this is the answer to press us on rather than accept. Approving a procurement request is gated by who holds the approval permission — there is no value band that sends a request above a figure to a committee and one below it to a programme manager. If your manual is written that way, the routing stays a matter of who you grant the permission to and of your own discipline, not something the system enforces. What the system does refuse, on its own and by default: a delivery larger than the order is blocked at receiving, a payment that does not match its order and receipt is blocked unless someone with a specific permission overrides it in writing, and a stock adjustment above a value you configure needs a second person. So the enforcement is real and it sits downstream of the approval rather than inside it.
How does it prevent fake quotations?
RFQs go to suppliers from a maintained database simultaneously, responses are timestamped, and comparisons are recorded with the award decision. Award concentration reports make repeat-winner patterns visible.
What about purchases in remote areas?
Field staff document reality with mobile capture: photos of goods, market price attestations, and GPS-stamped records that sync when back online — documentation donors accept.
Does it work with our finance system?
Procurement lives alongside AWRA's finance modules, so committed and actual spend hit grant budgets automatically. Integrations are available if you keep an existing ledger.
Make the compliant path the easy path
Watch one of your real procurements run end-to-end in a governed chain.