Procurement your donors can audit in minutes, not days

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.

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.

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.

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.