Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Uganda
Nobody failed to report. The Gulu count passed through four hands before Kampala saw it.
Inventory that counts, procurement with real approvals, donor funds tracked to the shilling, and field teams that work offline from Kampala to Karamoja — supported in your timezone.
- The subject
- Not whether your teams report. How many hands a fact passes through before Kampala can use it — because every hop is a chance for it to change, and no amount of reminding shortens a chain.
- E-invoicing
- EFRIS is URA's and we do not integrate with it. Our transmission layer is Kenya's eTIMS and it is Kenya-only. We run alongside your EFRIS process and the records reconcile. No roadmap date here.
- Payroll
- Kenya-only. PAYE and NSSF are not calculated here. Employee records, attendance, leave and payroll cost allocation to grants and cost centres are.
- Support
- Nairobi, which shares a working day with Kampala. An escalation at 3pm is answered at 3pm. It is the one claim on this page that no amount of engineering elsewhere can copy.
The chain, as topology
Six facts, and how many hands each one passes through before Kampala can use it
Ask why an upcountry number is wrong and the answer is almost always framed as a discipline problem — somebody did not report, somebody reported late. It is a topology problem. A fact captured four hops from where it happened has had four opportunities to change, and no amount of reminding fixes a chain that long. Count the hops in the middle column; the right-hand column is the same fact captured once.
4hops today
What is actually on the shelf in Gulu
How it travels now
Storekeeper counts on paper Phones the branch supervisor Supervisor emails a weekly summary Head office keys it into a workbook
Captured once, where it happens
The storekeeper counts on a phone with no signal. It syncs when there is one, and Kampala sees the count rather than a summary of it.
4hops today
That a delivery arrived two cartons short
How it travels now
Noted on the delivery note Delivery note travels with the next vehicle Filed at head office Found during a reconciliation, if ever
Captured once, where it happens
The receipt is entered against the order at the gate, and the shortfall exists as a variance the same hour it happens.
3hops today
That a vehicle changed hands
How it travels now
Verbal handover between two staff Remembered by one of them Written down at audit time
Captured once, where it happens
Custody changes on the asset record with a name, a date and a condition, at the moment of the handover.
3hops today
What a grant has actually spent
How it travels now
Costs coded later from receipts Allocated by whoever does the report Reconstructed monthly into a donor template
Captured once, where it happens
The grant and budget line are tagged when the cost is entered, so burn rate is a filter rather than a reconstruction.
3hops today
That somebody approved a purchase
How it travels now
Verbal or WhatsApp approval Document created afterwards to describe it Filed for the audit
Captured once, where it happens
The approval is the transaction. Above a threshold it refuses rather than warns, and the timestamp is the decision rather than a record of one made elsewhere.
3hops today
What a field team did this week
How it travels now
Written in a notebook Photographed and sent Typed up by somebody in Kampala
Captured once, where it happens
Stock and asset movement captured on the spot with no signal, synced on return, against the programme it belongs to.
None of this is a claim that Ugandan teams report badly — they report exactly as well as a four-hop chain allows, which is the point. The only durable fix is to shorten the chain to one hop, and the only way to do that upcountry is capture that works with no signal. That is why the offline card is a design centre on this page rather than a feature in a list.
Operations in Uganda
The distance between Kampala and the district office is the whole problem, and no tax rate describes it.
EFRIS is above and it is URA's. What actually breaks a Ugandan operation is that the thing you are managing is four hours away and reports by phone. A store in Gulu, a field team in Karamoja, a vehicle somebody signed for eighteen months ago — the record of all three is either captured where the work happens or reconstructed later from memory, and there is no third option.
Inventory
Upcountry stores in the same stock position as head office
Each store holds its own position, transfers are confirmed on arrival rather than on despatch, and what is in motion is a state instead of a discrepancy. The Monday morning question stops being which spreadsheet is right.
Budget controls
Grant lines tagged at entry, not reconstructed at report time
Kampala runs one of the largest NGO sectors on the continent and most of it still rebuilds donor reports by hand. Model the grant as a project, code the cost to it as it is entered, and the burn rate is a filter rather than an excavation. Restricted and unrestricted separate on that coding rather than on an enforced wall — nothing blocks a cost coded to the wrong grant, which is why the coding discipline is the thing to design.
Procurement
An audit file that assembles itself over the year
Requisition, threshold approval, RFQ comparison, purchase order, three-way match. The threshold refuses rather than warns, and the file a donor asks for in November was built in March without anybody trying.
Assets
Vehicles and ICT with a name against each one
Named custodian, location, condition at every hand-off, movement history and attached documents. The verification round becomes a rhythm instead of an annual crisis. No service calendar and no fuel log — the register is custody, not maintenance.
Offline operations
Field capture where there is no signal to wait for
Stock transfers, inventory check-out and check-in, and asset movements recorded offline on mobile and synced on return. Built for East African connectivity, in East Africa, which is a design centre here rather than a concession.
Supplier prequalification
The prequalification round as a pipeline, not a shared drive
Suppliers apply through your own public form, submissions are reviewed and approved in the system, and an approved applicant becomes a vendor record without anybody retyping a certificate.
One thing that belongs here rather than in the questions: support is in your timezone. Nairobi and Kampala share a working day, so an escalation at 3pm is answered at 3pm. That is worth more to an upcountry operation than most feature comparisons, and it is the only claim on this page that no amount of engineering elsewhere can copy.
Recognisable, we hope
Four symptoms of the same chain being too long
Field operations you cannot see
Upcountry branches and field teams report by phone call and WhatsApp photo — and reconcile approximately.
Donor reports built by hand
Kampala hosts one of Africa's largest NGO sectors — and most of it still reconstructs donor reports from spreadsheets.
Procurement on trust
Quotations in email, approvals verbal, and audit files assembled in a panic week.
Software priced and supported from far away
Dollar-priced platforms with support that answers when Kampala sleeps.
Running in the product today
- Multi-store stock with transfers confirmed on arrival, blind counts with valued variance, and goods in motion held as a state rather than a gap.
- Grants and budget lines coded at entry, with live burn rates. A grant is modelled as a project rather than a fund entity, so restricted and unrestricted separate by coding rather than by a wall — see the note below.
- Procurement thresholds that refuse, RFQ comparison, purchase orders and three-way matching, with the authorisation trail attached to the transaction.
- Supplier prequalification end to end — your own public application form, review, approval, and an approved applicant becoming a vendor record.
- Asset registers with named custody, movement history, condition on hand-off and documents attached.
- Offline capture for four field operations — stock transfers, inventory check-out and check-in, and asset movements — syncing on return. Counting, receiving a purchase order and job time are not among them.
- UGX as your base currency, with foreign-currency grants recorded at the rate actually applied rather than converted at a rate nobody wrote down.
More we can add — on the roadmap, and commissionable now
- An EFRIS integration. Our fiscal e-invoicing transmission is Kenya's eTIMS and it is Kenya-only. In Uganda we run alongside whatever you use to meet URA's requirements and the two reconcile; transmission to EFRIS with retries, a failure queue and a reconciliation report is an ordinary integration project rather than a research one.
- Ugandan statutory payroll. The maintained statutory rule engine covers exactly one country and it is Kenya. Employee records, attendance, leave and payroll cost allocation are real here; PAYE and NSSF calculation is not.
- Bank statement reconciliation. M-Pesa matching exists and is Kenya-only; matching a bank statement does not exist for any market, in any form.
- A maintenance schedule on an asset. Service interval, next-service date and fuel log and no distance held anywhere. The custody register is real; the fleet calendar is yours.
What we would decline, and would rather say now
- We will not file anything with URA. We hold the records a return is built from and we will make them reconstructable; the return is filed by you and your accountant. A filing obligation cannot actually be transferred to a software vendor, so a vendor who accepts it has sold you comfort rather than protection.
- We will not tell you whether a cost is allowable against a grant. Donor eligibility is a judgement with a clawback attached, and it belongs with your finance lead and your donor's rules. We will hold the evidence, tag the line and show the working.
The four items in the middle column are work rather than positions, and each is commissionable now on the usual terms: a written specification, a timeline and a price, agreed before any money moves. The evidence that this is real rather than a sales line is Kenya — the eTIMS transmission and the statutory payroll engine both exist because Kenyan clients needed them and commissioned them, and neither arrived on a roadmap by itself. We will not print a date on this page. We will put one in a quote.
Read the middle column carefully if EFRIS or Ugandan payroll is your first requirement rather than your third. A vendor already shipping either one starts where we would be finishing, and in that case buying locally is the rational move — we would rather write that sentence here than lose your third month to it.
How this starts
Three moves, and the first one is a single site
01
Start where it leaks
Stock, procurement, or donor funds — the first module targets your loudest problem.
02
Run a real month
Your grants, your stores, your approval chains — live, with training on your data.
03
Extend across the operation
Branches, field teams, and assets onboard module by module.
Read before you shortlist
Guides for this market
East Africa Guides 8 min
Donor Fund Tracking for Ugandan NGOs: Kampala to the Field
The Kampala–field gap, sub-grantee money as accountable advances, and mobile money at program scale — donor fund discipline for Uganda's NGO sector.
Read
East Africa Guides 7 min
Digitizing Business Operations in Uganda: Closing the MoMo-to-Stock Gap
Ugandan SMEs digitized payments a decade before operations — EFRIS pressure, the reconciliation gap, and the stock-first sequence Kampala businesses are using in 2026.
Read
East Africa Guides 8 min
Multi-Country NGO Operations: One System, Five Tax Regimes
Four registrations, four currencies, one donor report — country dimensions, cross-border cost allocation, inter-office balances, and consolidation without the quarterly ritual.
Read
Procurement Insights 11 min
Three Quotes and No Way to Score Them
We have requests for quotation with real line items and recorded responses. We have no request for proposal, no scoring model, no panel and no sealed bids. Those are not degrees of the same thing, and one of the four cannot be substituted procedurally.
Read
Procurement Insights 11 min
What Reaches the Job and What Does Not
A purchase can name the job it is for, and so can a stock issue — costed at the price stamped when it left the store, so a finished job cannot change price later. Two things never reach the job at all, and one of them will surprise you.
Read
Point of Sale 11 min
The Session That Only Counts the Cash
A till session opens with a float, records every drop, and closes with a counted figure and a variance against the person who counted it. All of it is about cash — so on a counter where most customers pay by phone, the strongest control in the shop is watching the smallest pile of money.
Read
Questions we are asked in Kampala
Straight answers, and what an EFRIS pipeline would involve
Does AWRA integrate with URA's EFRIS e-invoicing?
Not as a built-in integration today — we are honest about this. AWRA runs your operations (stock, procurement, assets, donor funds) alongside your existing EFRIS fiscalization process, and invoicing records reconcile against it. If EFRIS integration is essential to your use case, talk to us about your requirements and timeline before committing.
Does it handle UGX and Ugandan VAT?
Yes — Ugandan Shilling and the standard 18% VAT rate are supported for transactions and reporting, alongside multi-currency grants (USD/EUR grants spent in UGX with explicit exchange tracking).
What about Ugandan statutory payroll (PAYE, NSSF)?
Statutory payroll engines are currently maintained for Kenya. For Uganda we recommend keeping your existing payroll process for now and using AWRA for the operations side — and telling us your payroll needs so we can scope localization honestly rather than promise it casually.
Is support really available in our timezone?
Yes — AWRA is built and supported from Nairobi, in the same timezone as Kampala. Onboarding runs remotely with live sessions, and East African deployments are our home ground, not a distant market.
Can we run this alongside EFRIS without keying everything twice?
Partly, and the honest shape of it matters more than a yes. What runs here is the operation — stock, procurement, approvals, assets, jobs, the record of what happened. What runs in EFRIS is the fiscal document. There is no connection between the two, so a sale that has to appear in both is entered in both, and the second entry is a person. What we can do is make that person's job small and checkable rather than reconstructive: the document is raised from a record that already exists, with the quantities, the customer and the values settled, so nobody is deciding facts at the point of transcription. The connection itself is on the roadmap rather than a boundary, and it is commissionable now — Kenya's eTIMS transmission exists because a client needed it and paid for it, and if EFRIS transmission is what stands between you and a decision we will come back with a written specification, a timeline and a price. What we will not do is print a date nobody has bought.
Does it track vehicle maintenance, fuel and service intervals?
No, and this is one we have to be careful about because we said otherwise once. There is no service interval, no next-service date, no fuel log and no distance held anywhere in the product. The asset register knows what you own, who has it, what condition it was in at each hand-off and where it has been — which is custody and history, not maintenance. Those are genuinely different things and a register that appears to do the second is worse than one that plainly does the first, because somebody stops keeping the spreadsheet that was working. This is a boundary rather than a backlog, and the reason is that fleet maintenance is a real product category with real vendors in it: scheduling, parts, workshop, downtime. We are not going to build a thin version and let you find out in month four that it does not schedule anything. Buy that from somebody whose business it is, and use us for custody, cost attribution and the movement history underneath it.
Will the system tell us whether a cost is allowable against a grant?
No, and you should want a vendor to say so. Donor eligibility is a judgement about your specific agreement with your specific funder, and it carries a clawback attached — which means a wrong answer is not an inconvenience, it is money you have already spent coming back out of a budget that has moved on. We hold the coding: which grant, which budget line, which site, which period, with the supporting document attached and the approval trail intact. What we will not do is encode somebody's reading of an agreement we have not seen and let a screen imply it has been checked. That is a boundary rather than a backlog and it protects you specifically: the failure mode of an eligibility flag is a finance officer who stops reading the agreement. Your grant manager and your auditor make that call; we make sure the evidence they need is retrievable rather than reconstructed.
Bring your Ugandan operation to a demo
One store, one grant, one field team — see them run governed, with honest answers about what is and isn't localized yet.