SACCO Procurement Governance: Tender Committees, Thresholds & Member Money
Member money spent without competition is the finding that follows SACCO boards around — tender committees, thresholds, conflict-of-interest discipline, and the procurement trail SASRA-era governance expects.
When a SACCO buys — a branch renovation, twenty computers, a fleet vehicle, a marketing contract — it spends money that belongs to members who trusted the institution with their savings. That is a fiduciary standard, and it is why procurement is where SACCO governance is most visibly tested. The AGM question is never subtle: "Who supplied the vehicles, at what price, and who else quoted?" A board that answers from records survives the question. A board that answers from memory becomes the question.
The structure member money deserves
- Thresholds in writing, enforced in-system. Petty purchases at the branch; three quotations for mid-range spend; full tender committee above a defined line — the same threshold architecture any fiduciary institution uses, sized to the SACCO's scale.
- A tender committee that documents itself. Composition, quorum, declarations, comparisons, and the award reason — minuted per decision and attached to the procurement file, not filed in a separate binder that drifts from the transactions.
- Anti-splitting discipline. Two KES 240,000 orders to the same supplier in three weeks is one KES 480,000 procurement wearing a disguise. The system should surface related purchases automatically.
- Approval chains that cannot be bypassed — because the finding is rarely "the policy was wrong"; it is "the policy was not followed".
Conflict of interest: the SACCO-specific minefield
SACCOs are member-owned and community-rooted — which means suppliers are often members, and sometimes directors, or their relatives. That is not automatically wrong; undeclared, it is automatically a finding.
- A standing register of directors' and senior staff's business interests, updated annually and tabled with the supervisory committee.
- Per-procurement declarations: anyone connected to a bidder declares and steps out of that decision — recorded in the minutes.
- Member-owned suppliers compete on the same terms as everyone else: same RFQ, same deadline, same comparison sheet.
- Award concentration reviewed quarterly: one supplier above ~30% of a category deserves an explanation on file, whoever owns it.
The ICT procurement trap
The largest procurements many SACCOs ever run are core banking systems and ICT infrastructure — high-value, technical, and hard for a lay committee to evaluate. The discipline that survives scrutiny: written requirements before vendor contact, scored evaluation criteria fixed in advance, reference checks documented, and the scoring sheet retained. "The committee preferred vendor B" is not an audit trail; the scoring sheet is.
Receiving and payment: close the loop
The tender was competitive, the award was clean — and then the renovation is signed off by the branch manager who requested it, at 60% completion. Procurement governance ends at verified delivery, not at the award: goods received against orders by someone other than the requester, works certified against contract stages, and payment only on three-way match. For works and services, stage payments against certified completion protect the SACCO from financing a contractor's other projects.
What the supervisory committee should pull quarterly
The four-report procurement review
- All procurements above the committee threshold — with their files retrievable end-to-end.
- Exceptions report: emergency purchases, single-source awards, and waived steps, each with its justification.
- Award concentration by supplier and category, trailing four quarters.
- Open commitments vs budget — what has been promised against what was approved.
A SACCO that runs procurement this way is not slower — requisitions approve from phones, RFQs go out same-day, and the file that used to take a week to assemble assembles itself. The governance is a by-product of the workflow, which is the only kind that survives busy quarters.
What AWRA OpsHub does today
- Approval thresholds on value, enforced by workflow rules rather than remembered.
- Requisition approval enforced before an order can be raised — this is a real gate, not a convention.
- RFQs issued to multiple suppliers with quotations captured for comparison.
- Supplier prequalification with document capture and a review-and-approve step before a vendor is usable.
- Vendor blacklisting with reason, date and actor, and on-time performance from order history.
- A self-assembling audit trail across requisition, order, receipt, invoice and payment.
- Documents attach to the transaction itself — shipped 2026-08-01. Expenses, purchase orders, requisitions, quotations and assets all take Document Vault files directly: checksummed on upload, classified, every download logged, and archived rather than deleted when removed. The receipt now lives on the record it evidences instead of in a naming convention.
More we can add to your workspace
- A committee entity: a committee record with membership, quorum and minutes. A tender committee is modelled as a set of approvers and permissions today.
- Compulsory attachments, turning "no award without committee minutes" from a procedural rule into one the system enforces.
- Weighted scoring and an evaluation matrix — RFQ ships today, and RFP and RFI are what a technical evaluation inside the system needs.
- Deliveries verified against the order, with an over-receipt and shortage flag at the door.
- Collusion detection or price benchmarking.
The spend controls are genuinely enforced, which is the part that matters most to an auditor. What the middle column adds is evidence and evaluation: documents that justify a decision living on the transaction, and a scored evaluation inside the system. Agree a filing convention for both before your next tender rather than after it.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsAnswer the AGM question from records
Thresholds enforced, requisition approval gated before ordering, prequalified suppliers and a self-assembling audit trail.
See SACCO procurement in AWRAFrequently asked questions
What procurement thresholds suit a mid-sized SACCO?
A common pattern: branch petty procurement to KES 10,000–20,000; three written quotations to KES 500,000; tender committee above that, with board notification above KES 2–5 million. Size the bands to your annual spend and write them into policy — then let the system enforce whatever you adopted.
Can members demand to see procurement records?
Members exercise oversight through the AGM, the board, and the supervisory committee rather than by individual inspection — but that is exactly why the committee's independent access matters. A supervisory committee that can pull any file unaided is the members' answer.
How should we handle procurement from member-owned businesses?
Openly: they compete on identical terms, the ownership is declared on the comparison record, and connected directors step out of the decision. Banning member suppliers outright is usually unnecessary; hiding them is what destroys trust.
Who approves procurement between board meetings?
Management within its delegated thresholds; anything above waits or uses a defined urgent-approval route (e.g. chair plus one committee member, ratified at the next meeting, documented as an exception). The exception report keeps that route honest — if it is busy, the thresholds are wrong or the planning is.
