Skip to main content

GST & compliance

Uganda EFRIS in ERPNext: Beyond VAT After the 2025 Expansion

Since 1 July 2025, 12 gazetted sectors in Uganda must use EFRIS whether or not VAT-registered. How the FDN gate and stock sync work in ERPNext.

Updated 12 Oct 20268 min readBy ManojFirst published 3 Aug 2026

For years Uganda's EFRIS mattered mainly to VAT-registered taxpayers. Under General Notice No. 2218 of 2025 (gazetted 25 July 2025, effective 1 July 2025), businesses in 12 gazetted sectors must use EFRIS whether or not they are VAT-registered. The consequence reaches income tax: the Uganda Revenue Authority (URA) cites Income Tax Act s22(3)(m), under which an expense isn't deductible without an EFRIS e-invoice or e-receipt where the supplier must use EFRIS. If you run ERPNext in Uganda, the Fiscal Document Number (FDN) gates both your invoices and your deductions. This guide covers the scope change, the FDN gate, goods registration and stock sync. It describes the setup, not tax advice: confirm your position with URA or a Ugandan tax adviser.

The trap is assuming EFRIS only matters if you're VAT-registered. The income-tax rule on purchases from non-compliant suppliers is the part that surprises finance teams. I lead ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru. Treating the FDN as a hard gate on both sales and purchases is the core of a Ugandan ERPNext setup.

Are you even in scope?

Before anything technical, establish whether EFRIS is mandatory for you: the 2025 expansion changed the answer for many companies that assumed they were out.

Interactive

EFRIS Scope Decider

Toggle whether you are VAT-registered and whether you operate in a gazetted sector to see if EFRIS e-invoicing is mandatory for you.

You must issue EFRIS e-invoices

Even without VAT registration, businesses in the gazetted sectors were brought into EFRIS from 1 July 2025 (URA General Notice 2218 of 2025). You must issue EFRIS e-invoices for your sales.

The 12-sector expansion (General Notice 2218 of 2025, effective 1 Jul 2025) is the “beyond VAT” shift — EFRIS is no longer a VAT-only obligation. Confirm your sector and current scope on the URA EFRIS portal.

VAT-registered taxpayers have been in scope from the start. (Parliament passed an amendment in April 2026 raising the VAT registration threshold from UGX 150 million to UGX 300 million, reported to take effect from 1 July 2026; check URA's current figure.) The 2025 change added businesses in 12 sectors regardless of VAT status: manufacturing; mining and quarrying; water supply, sewerage and waste management; electricity, gas, steam and air conditioning; construction; transportation and storage (passenger land transport excluded); accommodation and food service; information technology and communication; real estate; professional, scientific and technical activities; arts, entertainment and recreation; and wholesale and retail of fuel. Exclusions include turnover under UGX 10 million a year. If you are in scope, your sales are issued through EFRIS.

The FDN gate reaches your deductions

Here is the part finance teams miss. EFRIS validity gates more than VAT input credit: for purchases from suppliers required to use EFRIS, it gates the income-tax deduction.

Interactive

Purchase Deductibility Checker

Toggle whether a supplier must use EFRIS and whether their invoice carries an FDN to see whether the expense is at risk. Confirm with a Ugandan tax adviser.

Deduction at risk — no FDN on an in-scope purchase

The supplier is in a sector where EFRIS is mandatory, but the invoice has no Fiscal Document Number. Since the 1 July 2025 expansion, purchases from non-compliant suppliers in these sectors are disallowed as deductible expenses for income tax — not just blocked for VAT input credit. Get a valid EFRIS invoice before you book the cost.

Guidance as understood 2026-08-03 following the 1 Jul 2025 expansion. Deductibility and penalty rules change — confirm the current position with URA or your Ugandan tax advisor before relying on it.

Wire EFRIS into ERPNext

EFRIS exposes a system-to-system API, and a maintained community app, erpchampions/uganda_compliance (version-13, version-15 and version-16 branches), maps ERPNext documents to it. Verify it for your version; either way, the moving parts are the same.

Code recipe

Architect · Issue · Stock · Prevent

Copy-paste the layered architecture, the invoice-upload flow that stores the FDN, the goods and stock registration steps, and the habits that keep invoices valid and deductions safe.

There is a maintained community app — erpchampions/uganda_compliance (ERPNext v13/v14/v15). Verify its status for your version; either way these are the moving parts.

text
Layers:

  ERPNext (Sales Invoice, Purchase Receipt, Stock Entry)
      |  uganda_compliance app (or your integration)
      |  maps ERP docs -> EFRIS T-series JSON
      v
  URA EFRIS API  (system-to-system integration)
      |  validates, assigns FDN + verification code + QR
      v
  URA (fiscal record of every invoice / receipt)

EFRIS JSON envelope has three parts:
  data            — the invoice / goods / stock payload
  globalInfo      — device / taxpayer / auth context
  returnStateInfo — URA's response status

Store the returned FDN, verification (antifake) code and
QR back on the ERPNext document and render them on the
print format.

0 of 4 steps done

Tick a step’s number when it is done; the ticks stay on this device.

Register goods and report stock

EFRIS is not only invoicing: you register each sellable item as an EFRIS good with the right commodity code, unit and tax category, and report stock-in before you can invoice it. Map ERPNext Purchase Receipts, Stock Entries and Stock Reconciliations to the matching EFRIS stock operations so URA's ledger and yours agree.

Issue e-invoices that carry an FDN

On submit, map the Sales Invoice to the EFRIS payload, upload it, and store the returned FDN, verification code and QR on the document, then print them. Without a returned FDN, don't hand the customer the invoice; it isn't a valid fiscal document.

Screen purchases for the FDN

For suppliers required to use EFRIS, flag a missing FDN before the purchase is booked, so finance can ask for a proper e-invoice; without one the deduction is at risk. Store the supplier's FDN and QR on the purchase record for audit.

Reconcile stock on a schedule

Stock that doesn't match between EFRIS and ERPNext invites audit questions. Reconcile the EFRIS goods list against the ERPNext Item master, and EFRIS stock against ERPNext stock, on a schedule, not at year-end.

When sales, stores and finance each own a piece

In a Ugandan operation the sales desk issues invoices, the stores team manages goods and stock, and finance books purchases. EFRIS touches all three, and the failures sit between them: an item sold before it was registered with URA, an invoice handed over before the FDN came back, or a purchase booked from a supplier required to use EFRIS whose invoice had no FDN.

Make the FDN a gate the system enforces, not a check one desk remembers. No item reaches a sales invoice until it is registered; no invoice is issued until URA returns an FDN; no purchase from an in-scope supplier is booked without one. Automate the goods sync rather than registering SKUs by hand, and reconcile EFRIS against ERPNext on a schedule.

Draft policy for your finance and operations leads to ratify. Every sellable item is registered with URA before it appears on a sales invoice. No sales invoice is issued to a customer until EFRIS returns a Fiscal Document Number; a missing FDN is a hard block, not a warning. Purchases from suppliers required to use EFRIS are not booked without a valid FDN, to protect the income-tax deduction. EFRIS goods and stock are reconciled against the ERPNext Item master and stock ledger on a set schedule. Current scope, penalty and deductibility rules are confirmed with URA, not carried over from prior guidance. Ratify with your Ugandan tax adviser before adoption.

Use the app, or build the integration?

Use the uganda_compliance appBuild the integration
A maintained app covers your ERPNext version and current EFRIS fieldsNo maintained app matches your version or requirements
Standard invoicing, goods and stock sync, credit notesBespoke document flows or unusual stock handling
You want the fastest route to compliant invoicingYou need full control of the EFRIS mapping
Small IT team, prefer a supported dependencyIn-house capacity to track EFRIS API changes
Either way: verify FDN, QR and antifake code render on the print formatEither way: test the full invoice + stock flow before go-live

At a glance

AspectWhat to know
ScopeVAT-registered taxpayers, plus 12 gazetted sectors from 1 July 2025 (GN 2218 of 2025)
Valid documentFDN, verification code and QR from URA
Deduction ruleIncome Tax Act s22(3)(m), as URA cites it
In ERPNexterpchampions/uganda_compliance (version branches) or a custom build

FAQ: what do people ask most?

Is EFRIS only for VAT-registered businesses in Uganda?

No, not since 1 July 2025. Under General Notice No. 2218 of 2025, businesses in 12 gazetted sectors must use EFRIS whether or not they are VAT-registered, with exclusions such as turnover under UGX 10 million a year. VAT-registered taxpayers were already in scope.

What is a Fiscal Document Number (FDN) in EFRIS?

The FDN is the identifier URA assigns to each validated e-invoice or e-receipt, issued alongside a verification (antifake) code and a QR code. It is what makes the document a valid fiscal invoice. An invoice without an FDN is not a valid tax document, so the buyer cannot rely on it.

Can I still deduct a purchase if the supplier's invoice has no FDN?

Where the supplier is required to use EFRIS, URA's position (citing Income Tax Act s22(3)(m)) is that the expense isn't deductible without an EFRIS e-invoice or e-receipt. That is why you screen in-scope suppliers and ask for a proper e-invoice before booking. Confirm the current position with URA or a Ugandan tax adviser.

Does ERPNext integrate with EFRIS?

Not natively, but a maintained community app, erpchampions/uganda_compliance, has version-13, version-15 and version-16 branches. It syncs goods and stock, issues invoices carrying the FDN, verification code and QR, and handles credit notes. Verify it for your version; otherwise the integration is a custom build against URA's API.

What happens if we issue an invoice without an FDN?

It isn't a valid fiscal document. Your customer can't use it to claim input credit or to support their own deduction, and you are out of line with the EFRIS obligation, which carries penalties. Gate ERPNext so no invoice reaches a customer until URA returns an FDN.

Does EFRIS track stock or only invoices?

Both. EFRIS registers goods with commodity codes and tracks stock movements, so you register a sellable item and report stock-in before invoicing it. Keep EFRIS stock and ERPNext stock reconciled.

What is the bottom line?

Since July 2025 EFRIS reaches well beyond VAT, and the income-tax rule on purchases is the part that costs most when missed. Gate ERPNext on the FDN for sales and purchases, register goods before you sell them, and keep stock reconciled with URA.

Your next step

Running ERPNext in Uganda?

GST & compliance

Now see GST compliance

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 3 August 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.