Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Rwanda
Rwanda runs on documentation and discipline — your operations should too. Inventory, procurement, assets, and donor funds with the audit trail built in, in RWF.
The chain, as artefacts
Ask most organizations for the file behind a purchase and a person goes and builds it — from an inbox, a drawer and somebody's memory of who said yes. That is not a filing problem, it is a sequencing problem: the evidence is being created after the fact instead of by the fact. Read the right-hand column and note what is missing from it, which is nothing.
Somebody asks, against a budget line, with a reason.
The request, its requester, its date and the budget it was drawn against.
Above a limit the transaction stops. It is refused, not flagged.
A refusal that exists as a record, and the authority that later lifted it.
Suppliers quote and the quotes are compared in one place.
Every quote received, including the ones that lost.
One is chosen and the reason is recorded at the moment of choosing.
The award reason, which is the single hardest thing to reconstruct afterwards and the first thing a reviewer asks for.
The commitment is made and is visible as a commitment.
A committed figure that exists before any invoice does.
Goods arrive and are counted in against the order.
What was ordered against what actually turned up, with the difference visible.
Order, receipt and invoice are reconciled before money moves.
The exception, held rather than passed through, with the variance shown to whoever approves it.
The invoice is settled and the settlement knows what it cleared.
A payment linked to the invoices it discharged, closing the chain back to the requisition.
This is a governance capability and it is not a certification. It produces a trail that stands up when somebody follows it. It does not make a statement about your compliance posture — that is your auditor's judgement and your board's, and any vendor telling you their software makes you audit-proof is describing a product that cannot exist.
Operations in Rwanda
EBM is above and it belongs to an approved provider. The Rwandan operating fact is that you will be asked to show the chain, and the difference between a good organization and a well-documented one is whether the chain existed before the question. Every capability below is chosen because it produces the evidence as a side effect of doing the thing, which is the only version that survives a busy quarter.
Procurement
Requisition to payment as one unbroken chain
Threshold approvals that refuse rather than warn, RFQ comparison with the losing quotes retained, purchase orders and three-way matching. Who authorised what, against which budget, on what date — a lookup rather than an email search.
Document vault
Documents attached to the transaction, not to a person
The supplier invoice against the receipt, the contract against the vendor, the delivery note against the movement — previewable in place and retrievable by the transaction rather than by remembering who filed it. This is the single largest time saving when somebody asks for a file.
Assets
Custody as a record rather than an assumption
Named custodian, approved movements, condition captured at each hand-off and a verification rhythm you set. An equipment register that was accurate the day it was typed is the thing this replaces.
Inventory
Cross-border stock that is still yours while it is in motion
Kigali operations supplying Goma and Bujumbura hold stock at locations they do not own and in transit between locations they do. Both are positions rather than gaps, with transfers confirmed on arrival.
Budget controls
Grants tagged when the cost is entered
Grants modelled as projects, costs coded to them at entry, burn rates live, and donor reporting built from the same records the procurement chain produced rather than assembled beside them. Restricted and unrestricted separate by that coding rather than by a wall the software enforces.
Offline operations
District work captured where it happens
Stock transfers, inventory check-out and check-in, and asset movements recorded on mobile without a signal and synced on return, so field activity enters the record on the day rather than the week.
A note on what this does and does not prove. These are governance capabilities, not a certification. They produce a trail that stands up when someone follows it; they do not make any statement about your compliance posture, and any vendor telling you their software makes you audit-proof is describing a product that cannot exist.
Recognisable, we hope
Rwanda's institutions expect documentation discipline that spreadsheets and memos cannot deliver.
Kigali's growing NGO and program hub reports to the same global donors — with the same spreadsheet pain.
Approvals, quotes, and deliveries that cannot be traced end-to-end in minutes.
Equipment registers that were accurate the day they were typed.
Running in the product today
Absences — on the roadmap, and commissionable now
What we would decline, and would rather say now
The middle column is absences rather than positions, and each is commissionable now on a written specification, a timeline and a price, agreed before any money moves. The evidence that this is a real offer is Kenya, where the eTIMS transmission and the statutory payroll engine were both built exactly that way by clients who needed them. We will not name a date here; we will name one in a quote.
The language row deserves a second look before anything else on this list. English-only is a genuine constraint rather than a setting, and the test is not whether your finance lead is comfortable in English — it is whether the person keying transactions at the store is. Test it with them.
How this starts
Procurement or donor funds first for most Kigali organizations — the audit trail pays immediately.
Real transactions, real approvals, training on your data.
Assets, inventory, and field mobile follow module by module.
Read before you shortlist
Rwanda expects documentation by default — procurement chains, living asset registers, and donor funds where the record is a by-product of the transaction, not a scramble.
Four registrations, four currencies, one donor report — country dimensions, cross-border cost allocation, inter-office balances, and consolidation without the quarterly ritual.
A practical system for tracking restricted funds from grant agreement to donor report — fund segregation, budget lines, burn rates, and audit-ready advances.
Four East African authorities run four separate schemes against four separate interfaces, and one question separates them: can the sale complete when the authority cannot be reached? We built for one answer, for one country. The consequence we had never written down is that the receipt your customer carries out of the shop does not yet carry the fiscal reference — and a POS filing that failed three times had nowhere to go, which we fixed the day we published this.
EAC currencies differ in unit value by roughly thirty times, so adding two of them together produces a number that looks reasonable and is wrong by an order of magnitude. Three ways a system can answer "what did we spend", only one of them honest — and a report of ours that adds Ugandan shillings to Kenyan ones and calls a budget breached on the result.
A help desk fills with personal data faster than any other module, and most of it belongs to people who will never have an account. Our public support path is built well for exactly those people — and the export and erasure tools take a user account as their argument. Also: tickets are on no retention timer and have no deletion path at all.
Questions we are asked in Kigali
Not as a built-in integration today — we say so plainly because Rwanda's compliance culture deserves straight answers. AWRA governs operations alongside your existing EBM process, and if EBM integration is essential for you, we will scope it against your actual requirements rather than promise it in a sales call.
Yes — Rwandan Franc and the standard 18% VAT rate are supported for transactions and reporting, with multi-currency grant tracking for donor-funded work.
Yes — donor fund tracking, procurement governance, and asset custody are the core of the product, and they are exactly the disciplines Rwandan partners and donors audit for. The supervisory-grade reporting is built in, not bolted on.
Nairobi — same region, one hour's difference, with remote onboarding and live training sessions. East Africa is our home market.
Yes, and the reason it works is sequencing rather than filing. Each stage of a purchase leaves its own artefact as it happens — the request and who made it, the budget it was drawn against, the refusal above a threshold and the authority that lifted it, the quotations and why one was chosen, the receipt, the match, the payment. So the file is assembled by having done the work rather than gathered afterwards from an inbox and somebody's memory. That is the whole design of the chain section on this page. What we will not claim is that producing a file is the same as passing a review: the file being complete is ours, the controls being adequate is yours.
No, and nobody selling software should. An audit trail that stands up is a by-product of how the product is built — approvals that refuse rather than warn, a record of who changed what and when, evidence attached to the transaction it justifies. Whether *your* controls are adequate is a question about your organisation: who has which permission, whether the person approving is independent of the person requesting, and what your board and your funders require. That is a boundary rather than a backlog and it will not change with a commissioned build, because the moment a vendor implies certification, somebody stops asking their own auditor. Ask us to show the trail. Ask your auditor whether it is sufficient. Those are two different conversations and it is worth keeping them apart.
As a governed transfer with a confirmed arrival, which is the part most systems get wrong on a border. The destination is a location whether or not you own it, the goods are an owned position while they are in motion, and the transfer stays open until somebody at the far end confirms the quantity that actually arrived — so a shortage belongs to the leg it happened on rather than to whichever count found it. The costs of the leg attach to the consignment as their invoices arrive, which on a cross-border move is usually weeks. What this is not: we do not clear anything, hold any tariff schedule, or track a transit regime. We hold what the movement cost and where the goods were while it happened; the border is your forwarder's and we will not imply otherwise.
One procurement chain, one grant, one asset register — governed end to end, with honest localization answers.