Procurement Software in Kenya: From Request to Payment Without the Gaps
Procurement is where the money leaves, and in most Kenyan organizations it leaves through a process nobody owns end to end. What to fix in what order, what to make a vendor prove, and the straight answer on what our own system does and does not do.
Almost every organization can tell you what it sold last month. Far fewer can tell you what it committed to spend. The gap between those two sentences is procurement, and it is where the largest recoverable losses in a Kenyan business usually sit — not in dramatic fraud, but in ordinary purchases that nobody could see coming, compare against anything, or match to what actually arrived.
The symptom is familiar. A department needs something. Someone WhatsApps a supplier they have used before. The goods arrive, sometimes short, and the delivery note goes into a drawer. Six weeks later an invoice appears that nobody recognises, finance pays it because the goods are clearly in the store, and at year end the auditor asks who approved it. Nobody did. Nobody refused either — there was simply no point at which approval was a thing that happened.
Procurement software exists to put that point back in. Everything else it does is secondary.
The four gaps, in the order they cost you money
Organizations rarely need all of procurement at once, and buying out of sequence is the most reliable way to end up with an expensive system that people route around. The sequence below is ordered by how much each gap costs while it stays open, not by how impressive it looks in a demo.
-
Commitment is invisible
You know what you have paid. You do not know what you have promised to pay. Until an approved order is a record, the budget you are managing is always a few weeks out of date, and always in the optimistic direction. This is the gap that turns a healthy month into an unexplained overdraft.
-
Approval happens after the fact
If the first formal step is the invoice, then approving is theatre — the money is already gone, the goods are already in the store, and the only remaining question is who signs. Approval has to sit before the commitment or it is not a control.
-
Prices are never compared
Most single-source buying is habit rather than corruption: the supplier is known, the order is urgent, and comparing takes a day nobody has. But a habit that is never tested becomes a price nobody negotiates. You do not need three quotes on everything — you need them above a threshold you set deliberately.
-
What arrived was never checked against what was ordered
Short deliveries, over-deliveries and substituted items are all normal. What is not normal is finding out at stock-take. Receiving against the order — at the door, by the person receiving — is the cheapest control in this entire list and the one most often skipped.
A budget that only counts payments is a rear-view mirror. The number that matters is committed spend, and most organizations have never computed it.
[Procure-to-pay](/glossary/procure-to-pay), plainly
The chain has six links. Software is worth buying when it makes each link a record that references the one before it, and worth nothing when it just gives each link its own screen.
The six links and what each one is for
Step What it exists to prevent
Purchase request Buying that nobody asked for, and demand that nobody recorded
Approval Commitment without authority, and authority without a trail
RFQ and quote comparison Paying a habit price above a threshold where comparison is worth the day it costs
Purchase order A commitment that exists only in someone's inbox
Goods receipt Paying for what did not arrive, and absorbing what arrived unasked
Invoice and payment Paying twice, paying early, or paying a price nobody agreed
The test of whether these are really one chain is boring and decisive: open a payment and walk backwards. Payment to invoice, invoice to receipt, receipt to order, order to approval, approval to request. If you can do that in five clicks without leaving the system, you have procurement software. If any step is a scanned attachment or a name someone remembers, you have six screens.
The threshold question nobody sets deliberately
The single most useful thing most Kenyan organizations can do is decide, on purpose, what amount requires what. Not a policy document — three numbers.
A workable starting point for an SME
The numbers matter far less than having them. Pick thresholds you will actually enforce, write them into the system, and raise them when they start causing queues rather than catching problems. A threshold that everyone bypasses is worse than none, because it teaches people the controls are decorative.
Why the thresholds belong in the system, not the handbook
A policy in a document depends on the person in front of it remembering, caring and not being in a hurry. A threshold in the workflow routes the request whether or not anyone remembers. The handbook is still worth writing — but it should describe what the system already enforces, rather than substitute for it.
What is actually built — and what is not
Most buyer's guides are written by the vendor and read like it. Here is the honest boundary of our own procurement module, because you will find it out in week three anyway and it is cheaper for both of us if you find out now.
What AWRA OpsHub does today
- Purchase requests with approval routing by amount, department or budget line, enforced by the workflow engine rather than by convention.
- RFQs to selected suppliers, with quotations returned and compared side by side, including a ranked analysis of who won on price, on lead time and on completeness.
- Supplier prequalification — a public apply-to-supply pipeline where a vendor submits documents, you review, and approval turns them into a usable supplier record.
- Purchase orders generated from the approved request or the winning quote, so the commitment references what authorised it.
- Budget checks at the point of commitment, so an order that would breach a budget line is caught before it is placed, not at month end.
- Goods receiving matched against the order, with an over-receipt guard that refuses or flags quantities beyond what was ordered, and short deliveries reported rather than blocked.
- A vendor portal where suppliers see their orders, submit quotations and track payment status without emailing anyone.
- Spend and supplier analytics — stale RFQs, delayed orders, price anomalies and supplier performance surfaced as signals rather than reports you must remember to run.
What it does not do
- We do not do three-way matching, and we do not call it that. What ships is an honest two-way match: ordered against received. The billed leg has no data source yet — a supplier's invoice is stored as a file and nothing reads it — so the third comparison cannot be made and the interface never claims it is.
- No invoice capture or OCR. Supplier invoices are attachments, not parsed line data. Entering them is still a person's job.
- No RFP or RFI, no sealed bids, no weighted panel scoring. Only RFQs exist. Donor-style tender evaluation happens outside the system.
- No inspection or quality-hold gate at receipt. Batches carry a quality status you can set, but nothing withholds stock from availability pending inspection — so four-way matching is not achievable.
- No payment runs or batch payment approval. Payments are recorded individually.
- We do not integrate with IFMIS or PPIP. Public-sector tendering compliance is outside what we do.
The two-way / three-way distinction is the one worth pressing every vendor on, not just us. Ask to see the supplier's invoice lines — the actual figures from their document — inside the system. Many products that advertise three-way matching are comparing an order against a receipt and against a valuation the system generated itself, which compares your own arithmetic with your own arithmetic.
That last point is not modesty, it is the most practical thing in this article. "Three-way matching" is the most oversold phrase in procurement software. The third leg requires the supplier's billed quantity and price as structured data, which means someone or something has to read their invoice. If a vendor cannot show you that data on screen, the third leg does not exist, whatever the brochure says.
What to make a vendor demonstrate
Not describe. Demonstrate, live, using a scenario you bring. Every item below takes under five minutes and each one has ended a sales process I have been in.
The procurement demo scorecard
Bring your own scenario: one order, one short delivery, one price change.
Commitment appears before payment
Make them prove it: Approve an order and show the budget line move immediately — before any invoice or payment exists. If committed spend is not a number on a screen, the budget control is retrospective.
Approval cannot be skipped
Make them prove it: Try to raise a purchase order above the threshold without approval. The correct outcome is that you cannot, not that it is discouraged.
Receiving is matched at the door
Make them prove it: Receive 80 of 100 ordered, then try to receive 40 more. Watch what happens to the 20 over. Ask whether short deliveries block or report — blocking goods that are physically on the floor is how a control gets bypassed.
Quotes compare on more than price
Make them prove it: Enter three quotes where the cheapest has the longest lead time and is missing a line. Ask the system who won and why.
The billed leg is real
Make them prove it: Ask to see the supplier invoice's own line quantities and prices as data in the system. Not the attachment — the figures. This is where "three-way matching" usually turns out to be two-way.
The chain walks backwards
Make them prove it: From a payment, click back to invoice, receipt, order, approval, request without leaving the system or opening an attachment.
Separation of duties
Make them prove it: Try to approve your own request. Then show the trail of who approved what, when, and at what amount.
The Kenyan specifics that actually matter
Most procurement advice is written for markets where suppliers invoice electronically, credit terms are standard and delivery is predictable. Three local realities change what good looks like.
- Supplier invoices arrive as paper, PDF or a WhatsApp photograph. Any system whose controls depend on structured supplier invoice data will quietly fail here. Design your process so the strong control is at receiving, where you have staff and physical goods, rather than at invoice, where you have a photograph.
- Mobile money is a real payment rail, not an edge case. Supplier payments by M-Pesa need to reconcile like any other payment, against the same order and the same ledger. If mobile money lives in a separate spreadsheet, half your supplier spend is outside the control you just bought.
- Prices move. Quotes go stale in weeks on imported goods. A comparison from six weeks ago is not a comparison, and a system that does not date-stamp and expire quotations is helping you make an old decision confidently.
- Prequalification is doing more work than people expect. Getting supplier documents — registration, tax compliance, bank details — captured once, before the first order, removes most of the scramble later, particularly for anyone who will face a donor or statutory audit.
The one report to run every week
Open orders, aged. Every purchase order that has been approved but not fully received, sorted oldest first. It is a short list in a healthy organization and a horror story in an unhealthy one, and it catches — without any further analysis — the supplier who took a deposit and went quiet, the order somebody duplicated, the delivery that arrived but was never receipted, and the commitment sitting against a budget that has already moved on.
Ten minutes a week. If you adopt nothing else from this article, adopt that.
Where to go next
The end-to-end mechanics are worked through in the procure-to-pay process, and the receiving control specifically in the goods received note. If the matching distinction in this article is new to you, what three-way matching actually is is worth twenty minutes before you sit through any vendor demo.
Sector-specific versions of this problem are covered in school procurement, procurement challenges in NGOs and SACCO procurement governance. If procurement is the second module you are buying rather than the first, how inventory and procurement work as one record is the piece that ties them together.
Our take
Fix commitment visibility first, approval routing second, receiving-against-order third, and quote comparison fourth — in that order, whatever the demo showed you first. Three of those four are cheap and can be running inside a fortnight. And press every vendor, including us, on whether their three-way matching has a real third leg; the answer tells you how carefully the rest of the product was built.
See procurement that starts before the money leaves
Requests routed by threshold, RFQs compared side by side, orders that move the budget the moment they are approved, and receiving matched against what was ordered — with the boundaries above stated plainly rather than discovered later.
See plans & pricingFrequently asked questions
What does procurement software actually do that a spreadsheet cannot?
It makes approval happen before the commitment, and it makes committed spend a number you can see. A spreadsheet can record what you bought; it cannot refuse an order that breaches a budget line, route it to the right approver, or tell you today what you have already promised to pay. Everything else — RFQs, supplier records, analytics — is useful, but that is the part that changes outcomes.
How much does procurement software cost in Kenya?
For an SME, expect a per-user monthly subscription rather than a licence. AWRA is priced in Kenyan shillings and procurement is part of the platform rather than a separate product, so the cost scales with the people who use it and the modules you switch on. Current plans are on the pricing page. Be careful comparing headline prices against systems that charge separately for supplier portals or approval workflows.
Does AWRA do three-way matching?
No, and we will not claim it. What ships is an honest two-way match — what was ordered against what was received — with an over-receipt guard at the door. The third leg needs the supplier invoice's own quantities and prices as structured data, and today a supplier invoice is a file that nothing reads. Ask every vendor to show you that data on screen; the phrase is widely used for what is really a two-way match.
Can we start with procurement without buying the whole system?
Yes. Procurement is one module and can be switched on by itself. In practice most organizations turn on inventory alongside it fairly quickly, because receiving against an order is where the two meet and it is the cheapest control in the chain.
Does it handle RFQs and supplier prequalification?
Yes to both. RFQs go out to selected suppliers and returned quotations are compared side by side with a ranked analysis. Prequalification is a public apply-to-supply pipeline: a prospective supplier submits their documents, you review them, and approval turns them into a usable supplier record. What is not built is RFP, RFI, sealed bids or weighted panel scoring.
Will it work for public-sector or donor-funded procurement?
For donor-funded buying, yes in the sense that approvals, thresholds, supplier documents and the audit trail are all recorded and exportable, which is usually what an audit asks for. For public-sector tendering, no — we do not integrate with IFMIS or PPIP, and formal tender evaluation with panel scoring happens outside the system.
What is the most common procurement mistake you see in Kenya?
Approving after the goods have arrived. Once the delivery is in the store, approval is a formality and everyone knows it, so the control decays into a signature. The second most common is having thresholds that nobody enforces, which teaches staff that the whole framework is decorative.