EFRIS Uganda: 2026 E-Invoice Rules and Buyer Checks

EFRIS, the Electronic Fiscal Receipting and Invoicing Solution, is Uganda Revenue Authority's system for recording business transactions and transmitting them to URA as they happen. It has operated since January 2021. Since 1 July 2025, mandatory use covers VAT-registered taxpayers and specified non-VAT businesses in sectors gazetted by the Ministry of Finance, while taxpayers with annual sales below UGX 10 million are excluded from mandatory use.

Most guidance on EFRIS Uganda speaks to the seller: how to register, how to issue, how to integrate. This guide takes the other seat. Every fiscalised invoice a supplier issues lands in someone's purchase file, and the finance team that receives it lives with the consequences. Input VAT recovery, expense deductibility and the audit trail URA expects all depend on whether the documents in that file are valid fiscal evidence.

What follows works through the life of a received EFRIS document: identifying which fiscal document type you are holding, checking the data on its face, validating it against URA's record, resolving documents that fail or need correction, and retaining what proves your claims. This is not a portal login walkthrough or an ERP integration tutorial. Those belong to the issuing side. This is the receiving side, where the compliance risk sits quietly in the purchase ledger.

Who Must Use EFRIS in Uganda in 2026

The question of who must use EFRIS in Uganda now has two dated answers. From January 2021, every VAT-registered taxpayer was required to issue e-invoices or e-receipts through the system. From 1 July 2025, the mandate extended to businesses registered for income tax but not for VAT, provided they operate in sectors gazetted by the Ministry of Finance. URA's Commissioner General confirmed the second phase, the gazetted-sector approach and the exclusions in a Q&A published in April 2026. The gazette notice, not a general rule, decides whether a non-VAT business is caught, so a business unsure of its position should check the current notice or ask URA directly rather than assume.

Two boundaries soften the mandate. Businesses with annual sales below UGX 10 million are excluded from mandatory use, though voluntary adoption remains open to them. And cost is not accepted as a barrier: URA provides free issuance channels, including the EFRIS web portal and the mobile app, alongside the paid integration routes larger businesses use.

Adoption is broad but not complete. The Ministry of Finance's FY 2024/25 EFRIS adoption figures put 93,670 taxpayers on the EFRIS register, growth of 20% in a year, with usage at 78.4% in June 2025 against a target of 85%. Registration does not equal correct usage: roughly one taxpayer in five on the register was not actively using the system, which is why non-compliant documents still arrive in purchase files and why the checks in this guide exist.

Penalties for failing to issue fiscal documents sit in the Tax Procedures Code, and they fall on the supplier who should have issued through EFRIS. The buyer's exposure runs elsewhere, through deductions and input VAT claims that depend on holding valid fiscal documents. Parliament considered revised EFRIS penalty provisions during the 2026 amendment cycle, so confirm the wording in force with URA or the gazetted law before relying on a specific amount.

Kenya's eTIMS regime imposes comparable obligations across the border, and finance teams working in both markets can set the Kenya eTIMS requirements for finance teams beside the Ugandan position described here.

E-Invoice, E-Receipt, E-Credit Note or E-Debit Note: Know What You Are Holding

EFRIS produces four fiscal document types, and classifying them correctly at intake saves rework later.

An e-invoice documents a business-to-business supply and carries the buyer's details, including the buyer's TIN. This is the document a business purchaser should expect for stock, services and capital items, because it names that purchaser as the party to the transaction.

An e-receipt documents a retail or consumer sale. It is fiscally valid evidence that a sale happened, but it typically identifies no buyer. A staff member who pays for supplies at a shop counter will usually walk away with an e-receipt rather than an e-invoice.

An e-credit note is a downward adjustment issued after the original document, and an e-debit note is the corresponding upward adjustment. Neither replaces the original: each one references the fiscal document it corrects, and the original fiscal document number remains the thread that ties the sequence together. AP records should mirror that structure by filing every adjustment note against its original invoice rather than as a standalone document.

A business intending to claim input VAT or an expense deduction should hold an e-invoice bearing its own TIN, not a bare e-receipt. A document issued to the wrong party, or with no buyer identified at all, is weak tax evidence however genuine the underlying purchase was. Where a supplier has issued an e-receipt for what was really a business supply, the time to ask for a proper EFRIS invoice is at intake, not during an audit.

All four document types are fiscalised through EFRIS and carry the same fiscal identifiers, so the same verification checks apply whichever one you are holding.

What a Valid EFRIS Invoice Must Show

The EFRIS invoice requirements that matter to a buyer sit in two layers: the fiscal identifiers that prove the document lives in URA's system, and the commercial detail that proves it describes your transaction.

The fiscal layer has three elements to look for on the face of the document:

• Fiscal document number (FDN). The unique number EFRIS assigns when the document is fiscalised. It identifies this exact document in URA's records and is the reference every later correction must cite.
• Verification code. A code generated at fiscalisation that supports lookup of the document through URA's verification tooling.
• QR code. A scannable block encoding the document's fiscal details, allowing anyone holding the document to pull up the registered record and compare.

The commercial and tax layer is what the document says about the deal itself: the seller's name and TIN, the buyer's name and TIN for a business-to-business supply, the issue date, the description and quantity of goods or services, unit prices, the currency, the VAT rate and amount, and the totals.

Keep the two layers separate in your thinking, because they fail independently. A document can be genuinely fiscalised, with a real FDN and a QR code that resolves perfectly, yet describe the wrong goods, the wrong price or the wrong buyer. Fiscal identifiers prove existence; only comparison against your purchase order and delivery records proves accuracy.

For each received EFRIS invoice, capture into your AP records the FDN, the verification code, both TINs, the document date, the taxable amount, the VAT amount and the total, and retain the document file itself. That set is what lets you answer a URA query or an audit request years later without reconstructing anything from memory or chasing the supplier for a reprint.

How to Validate an EFRIS Invoice Through URA

There are two practical ways to validate an EFRIS invoice, and neither requires the buyer to be registered on the system.

The first is the QR code. Scan it with the EFRIS mobile app and the registered record appears. The second is URA's FDN validation facility on the EFRIS portal (efris.ura.go.ug), where you enter the fiscal document number and the receipt date; an advanced search accepts the verification code as well. Both routes answer the same question: does this document exist in URA's system, and what does the registered version say?

Validation is a comparison, not just a lookup. Once the system record is on screen, check it against the copy you hold across the same fields captured at intake, from the two TINs through to the VAT and total. A full match confirms the paper or PDF in your hands reflects the fiscalised record. Any difference means one of the two versions is wrong, and the document should not be posted until you know which.

Be precise about what a successful check establishes. EFRIS FDN verification proves the document was genuinely issued through the system and matches URA's record. It does not prove the goods or services were delivered, that the prices agree with your purchase order, or that the supplier is otherwise sound. The fiscal check slots into your existing invoice validation process and controls alongside three-way matching, duplicate detection and approval routing rather than replacing any of them.

When to run the check is a judgment about risk. Validate before posting and before payment for significant amounts, new suppliers and anything unusual. For high-volume, low-value flows, a risk-based sample is a defensible alternative to checking every document, provided the sampling rule is written down and exceptions are always checked in full.

When an EFRIS Document Fails Validation or Needs Correction

Exceptions fall into three patterns, and in every one of them the fix happens on the supplier's side.

The document cannot be found or verified. Do not post it as tax evidence. Go back to the supplier and request a properly fiscalised document. Allow for the possibility of an innocent explanation, such as a document issued offline that has not yet transmitted, but a supplier within the mandate who cannot produce a verifiable fiscal document after a reasonable interval is a compliance red flag worth escalating beyond the AP desk.

The copy you hold differs from the system record. The system record is the fiscal record. Ask the supplier to explain the difference and to issue whatever correction is appropriate. Resist the temptation to book from whichever version suits, because a purchase file built on figures URA does not hold is exposure waiting for an audit to find it.

The invoice is wrong, or the goods went back. Wrong price, wrong quantity, wrong buyer details, a return, a post-sale discount: all of these are corrected in EFRIS by the supplier, through an EFRIS credit note issued against the original FDN, or an e-debit note where the adjustment runs upward. The buyer's role is to request the correction, then file the correcting note together with the original so the pair reads as one transaction history.

The control principle underneath all three: editing figures in your own bookkeeping system changes nothing in the fiscal record URA holds. Only a fiscal correction document does that. Books that drift away from the fiscalised records behind them are precisely what URA's data-matched view of the economy is built to detect.

For every exception, keep the trail: the failed validation result, the correspondence with the supplier, and the correcting document once it arrives. If a dispute or audit comes later, that trail shows a finance function that caught the problem and handled it properly.

Why Valid EFRIS Documents Decide Deductions and Input VAT

The effort of validating and filing fiscal documents pays for itself in two places on the tax return.

The first is input VAT. Where a supplier is required to use EFRIS, URA expects a VAT-registered buyer's input tax claims to be supported by valid e-invoices carrying the buyer's TIN. A purchase documented only by an informal invoice from an EFRIS-obligated supplier puts the input tax claim at risk, whatever the commercial reality of the purchase.

The second is the income tax deduction. Expenditure claimed against suppliers within the EFRIS mandate risks disallowance when it is not supported by fiscalised documents. The July 2025 expansion widened the population of suppliers whose documents must be fiscal, which put this consequence in front of far more buyers. A buyer who kept accepting handwritten invoices from a newly gazetted supplier after that date was accumulating expenses that may not survive scrutiny.

The practical control for both is knowing which of your suppliers fall within the EFRIS mandate. Supplier onboarding should record VAT registration status and, since the 2025 expansion, whether the supplier's sector appears in the gazette. Periodic review should catch suppliers whose status changes. The answer determines what documentation your team insists on before an invoice is approved, so it belongs in the AP workflow.

Retention closes the loop. Keep fiscal documents and their validation evidence in line with Uganda's tax record-keeping requirements, so a claim made this year can be substantiated when questioned years later.

One caveat belongs here in plain terms. This article is general compliance orientation rather than advice on a specific taxpayer's position. Where a decision turns on a specific figure or filing position, confirm it against current URA guidance and take professional advice where the amounts justify it.

Issuance Channels, Offline Use and Where Bookkeeping Fits

A buyer does not need to operate EFRIS to process the documents it produces, but a working picture of the issuing side makes what arrives easier to interpret.

Suppliers issue fiscal documents through four main channels: the EFRIS web portal, the URA mobile app, electronic fiscal devices at the point of sale, and direct system-to-system integration between their own invoicing or ERP software and URA EFRIS. Which channel produced a document makes no difference to its validity; a fiscal document is a fiscal document once URA has registered it.

EFRIS also supports offline issuance for connectivity gaps, with transactions transmitted once the connection is restored. The buyer-side implication is timing: a document validated minutes after issuance may occasionally not yet appear in the system. Where the supplier says the document was issued offline, allow a short interval and check again before treating it as unverifiable.

Not every supplier owes you a fiscal document. A business below the UGX 10 million exclusion may legitimately issue ordinary invoices or receipts outside EFRIS. The buyer's control is knowing which suppliers are in scope rather than demanding fiscal documents from everyone who sends a bill.

That leaves the boundary this guide has drawn throughout, stated once in full. Issuing, fiscalising and transmitting invoices through EFRIS is the supplier's compliance obligation to URA. Extracting and recording data from received EFRIS invoices, whether the FDN and verification code into an AP register or line items into a ledger or spreadsheet, is ordinary bookkeeping on the buyer's side. Nothing a buyer does in its own records fiscalises a document or alters what URA holds, and no EFRIS integration is needed merely to capture, validate and account for the invoices a Ugandan business receives. Keep the two jobs distinct, run the checks in this guide at intake, and the purchase file will stand up to whatever URA's increasingly data-driven administration asks of it.