Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For SACCOs & microfinance
Member deposits live in the core banking system. Member money also buys vehicles, renovates branches, and pays allowances — AWRA wraps that operational spend in the same discipline as the loan book.
If any of these ring true, you are exactly who this was built for.
"Who supplied the vehicles, at what price, who else quoted?" — answered from memory instead of records.
The balance sheet says tens of millions in assets; nobody can say where half of them are.
Floats topped up on request, retired on faith, reviewed at year-end when the variance is history.
Sitting allowances paid casually — a recurring audit note and a PAYE exposure in one.
Each capability links to a deeper feature tour.
Thresholds enforced, tender committees documented, quotations compared on the record, anti-splitting surfaced.
Fleets, branch fit-outs, ICT — named custodians, movement history, verification rhythms, exit clearance.
Live budgets per branch and department, commitments counted, over-budget requests escalating visibly.
Spending recorded at the branch, visible at head office same-day, reviewed monthly per manager.
Staff payroll with PAYE, NSSF, SHIF, and housing levy current — sitting allowances through payroll, taxed correctly.
Supervisory committee read-only access to trails, registers, and exceptions — independent of management-prepared reports.
A branch-by-branch count builds the living register and reconciles it to the financial schedule.
Your procurement policy and expense envelopes configured — the system starts enforcing what the board adopted.
Supervisory committee gets independent read-only visibility; inspection prep becomes a printout.
The core system runs the loans; nothing runs the rest. Procurement, assets, branch expenses, and payroll — where member money leaks and governance is tested.
The AGM question is never subtle: who supplied, at what price, who else quoted? Thresholds, conflict-of-interest discipline, and files that answer for themselves.
Every operating shilling is a dividend shilling that left early — live budget envelopes, sitting allowances done properly, and the monthly five-number review.
No — members, savings, loans, and dividends stay in your core system. AWRA governs the operational spend around it: procurement, assets, expenses, and payroll, with the reporting boards and supervisory committees need on that spend.
Inspections test governance evidence: procurement files, asset verification, expense controls, and policy enforcement. When those controls run in a system, the evidence assembles itself — sampled transactions retrieve end-to-end in minutes instead of file-hunting weeks.
Yes — read-only roles scoped to oversight: full visibility of procurement chains, registers, and exception reports, zero ability to edit, with their access itself logged. Independent visibility without operational interference.
The modules scale down: start with the asset register and procurement thresholds — the two highest-exposure areas — on a small-team plan, and add branch budgeting and payroll as you grow. Governance debt is cheapest to fix while the institution is small.
Bring one procurement file, your asset schedule, and one branch's expenses — see them governed end to end.