Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For schools & education
Fees that reconcile themselves, stores that measure the kitchen, procurement on the term calendar, assets with custodians, and payroll with statutory handled — one system for the bursar's whole world.
If any of these ring true, you are exactly who this was built for.
M-Pesa, three banks, cash at the office — and a bursar matching payment narrations to student names after dark.
Consumables bought by the lorry, issued by memory — and 10–20% of the spend evaporating between the two.
Term dates known for years, yet every term starts with urgent purchases at whatever price was quoted on the phone.
Labs, dorms, and sports stores replacing items nobody can find — an invisible annual tax.
Each capability links to a deeper feature tour.
Invoices per student, payments matched automatically across channels, arrears by class and family.
Receipts against POs, daily kitchen issues against student counts, variance reports weekly.
Consumption-planned buying, RFQs for the big four contracts, committee approvals on the record.
Labs, ICT, dorms, kitchens, buses — named custodians, term verification, maintenance schedules.
PAYE, NSSF, SHIF, and housing levy for teachers and support staff; casuals paid with proper records.
Term spend vs budget, store variances, arrears aging, and the asset report — generated, not typed.
One term of receipts, issues, and counts — the variance report pays for the project by itself.
Student invoices and payment references live; the exceptions queue replaces the evening ritual.
Procurement plans, asset verification rhythms, and payroll — the full bursar's calendar, systematized.
Schools are three businesses in one uniform — fees, logistics, and assets. What operations software must handle, and where school money actually leaks.
Term dates are known years ahead — yet week one is always a buying emergency. The term procurement cycle, the big four contracts, and kitchen arithmetic.
One invoice per student, a unique payment reference, all channels into one ledger — how bursars end the evening matching game and make arrears report themselves.
No — it governs the operations side: money, materials, assets, and payroll. Academic systems handle admissions, exams, and timetables; the two coexist, and many schools run both. If your academic system already invoices fees well, start AWRA at stores and procurement.
Yes — the admission number as payment reference matches automatically; unreferenced payments land in an exceptions queue with phone-number matching suggestions, so the bursar reviews a short list instead of a statement.
Boarding schools feel the store pain most, but day schools with significant assets, multi-channel fee collection, and staff payroll recover the cost quickly too. Start with the module that hurts most — fees for day schools, stores for boarding.
Go-live is timed to a term boundary: stores open with a count, fees open with verified balances per student at term start. One term of parallel discipline and the routines are set — mid-term big-bang migrations are what we avoid.
One store, one class of fee data, one asset room — see the term run governed, end to end.