EFRIS & VAT in Uganda: What Your Business System Should Handle
A plain-English look at what URA's EFRIS and 18% VAT actually require, what an operations system should and should not claim to do about them, and how to buy without falling for an "integration" that was never real.
EFRIS is the single most misunderstood line in Ugandan software buying. Vendors wave "EFRIS integrated" across a slide, businesses assume it means "the software files everything for me," and the gap between those two things is where money and trust get lost. This guide separates what URA actually requires from what an operations system can honestly do about it — so you buy on evidence, not on a confident tone of voice.
One disclaimer up front, and it is the honest one: rates, thresholds and filing rules change, and this is not tax advice. Treat everything below as the shape of the problem, and confirm the specifics with URA or your accountant.
What EFRIS and VAT actually are
- EFRIS — the Electronic Fiscal Receipting and Invoicing Solution operated by URA. In practice it means qualifying businesses issue fiscalised invoices/receipts that URA can see, whether through the URA portal, an EFRIS device, or an approved system integration.
- VAT — Uganda's standard rate is 18%. If you are VAT-registered, your invoices, records and returns have to reflect it correctly, and your input/output VAT has to reconcile.
- The link between them — EFRIS is how the invoice is fiscalised; VAT is what the invoice has to compute and report. A business system touches both, but it does not replace either.
What an operations system should honestly do
Here is the straight answer for AWRA OpsHub, and the standard you should hold any vendor to. Split the claim into what is genuinely supported and what is not:
| Capability | Honest status | What that means for you |
|---|---|---|
| UGX transactions & records | Supported | Sales, purchases, stock and reporting all run in Ugandan shillings |
| 18% VAT on transactions & reports | Supported | VAT-aware records and reporting so returns reconcile to real data |
| Multi-currency for cross-border trade | Supported | Trade in KES/USD/UGX and report consistently |
| Operations reconciled against EFRIS | Supported | Your stock, sales and invoicing records line up with your EFRIS invoices |
| Automated EFRIS e-invoicing/fiscalisation | NOT built in today | AWRA does not fiscalise invoices to URA for you — you run EFRIS alongside it |
The distinction that saves you money
A system that keeps clean, VAT-correct operations records and reconciles them against your EFRIS process is doing its job. A system that claims to be your EFRIS fiscalisation is claiming something AWRA does not do — and something you should make any vendor prove live before you believe it. If direct EFRIS integration is essential to your workflow, make it a written requirement and confirm the current position with us first.
EFRIS integration is a build we can quote today
"Not built in" describes what ships in the standard product, not the limit of what AWRA OpsHub can do in Uganda. Kenya's eTIMS integration exists because Kenyan clients needed it and commissioned it; it did not appear by itself. The same door is open here. If direct EFRIS fiscalisation, a mobile money feed or a URA-shaped return is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
EFRIS fiscalisation
Invoice submission against URA's published interface, with the parts vendors gloss over — retries, a failure queue, and a daily report of sales with no fiscal reference — built the way eTIMS was built.
MTN, Airtel and bank feeds
Mobile money and bank statement feeds pulled into the Payments Register, so collections match invoices without anyone re-keying a statement at month end.
Payroll and statutory returns
PAYE and NSSF schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt in a spreadsheet each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
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. We publish scope rather than a roadmap slide, and we will not pretend in a demo that something exists when it does not.
Tell us what you need integratedHow the two actually work together in practice
The workable pattern is simple: your operations system is the system of record, and EFRIS is the fiscalisation layer it reconciles to. Sales are captured against stock in AWRA; invoices are fiscalised through your EFRIS process; and at close, the two agree because both draw on the same real transactions rather than a re-typed summary. When they disagree, you have found a genuine problem — a missed sale, an off-book issue — instead of a data-entry artefact. This is the same discipline Kenyan businesses adopted under eTIMS: let compliance fall out of good records rather than bolting it on afterwards.
The questions to ask a vendor about EFRIS
- "Show me, don't tell me." Ask to watch an invoice fiscalise, live, inside their system. If they can only describe it, treat "integrated" as marketing.
- "What exactly is built vs roadmap?" A trustworthy vendor draws that line for you unprompted.
- "How do your records reconcile to EFRIS at month-end?" The good answer is a report, not a promise.
- "Who confirms the VAT treatment — you or URA?" The only correct answer points you to URA and your accountant.
The wider selection framework — offline, UGX, support, one connected system — is laid out in the Uganda ERP buyer's guide. EFRIS is one line on that checklist, but it is the line most likely to be oversold, which is why it earns its own page.
Operations records that reconcile to EFRIS — honestly
UGX-ready, 18% VAT-aware, and straight with you about what is built and what is not. Run clean operations and let compliance follow from good records.
See AWRA for UgandaFrequently asked questions
Does AWRA OpsHub fiscalise invoices to EFRIS automatically?
No — automated EFRIS e-invoicing is not built in today. AWRA keeps your operations and invoicing records in order and reconciles them against your existing EFRIS fiscalisation process. If direct EFRIS integration is essential to your use case, raise it explicitly before committing and confirm the current position with us. Treat any vendor's "fully integrated with EFRIS" claim as something to watch working live, not accept on trust.
Does it handle 18% VAT correctly?
Yes — VAT-aware records and reporting are supported so your returns reconcile to actual transactions rather than a re-typed summary. That said, VAT rates and rules can change and this is not tax advice; confirm the current treatment for your business with URA or your accountant.
We are not VAT-registered yet. Do we still need any of this?
The operations discipline matters regardless of VAT status — clean stock, sales and purchasing records are what protect margins and satisfy lenders. VAT-aware features simply switch on when you register; you are not paying for compliance machinery you cannot use.
Can we run EFRIS on the URA portal and AWRA for everything else?
Yes, and that is the common, honest pattern: fiscalise through your EFRIS process, run stock, purchasing, branches and reporting in AWRA, and reconcile the two at close. Both draw on the same real transactions, so they agree when operations are clean and flag a genuine issue when they do not.
