Skip to main content

Uganda’s 2026 Income Tax and Excise Duty Amendments Took Effect on 1 July: What Businesses Should Review Now

Uganda Revenue Authority has confirmed that the Income Tax (Amendment) Act, 2026 and the Excise Duty (Amendment) Act, 2026 were assented to with a commencement date of 1 July 2026. URA has consequently advised taxpayers to review returns and declarations already filed for July 2026, August 2026 and subsequent periods and make any adjustments necessary to reflect the amended provisions.

For finance and tax teams, the important issue is not merely that the law changed. It is that the commencement date reaches back to the beginning of the 2026/27 financial year, while some taxpayers may already have filed returns before the administrative systems and return templates were updated.

That creates a practical compliance task: identify affected filings, determine whether they were prepared using the correct post-amendment rules, correct them where necessary and reconcile any resulting tax, payroll or credit consequences.

Why the timing matters

The legislative path helps explain why the compliance issue has arisen.

Parliament initially passed the Income Tax and Excise Duty amendment Bills ahead of the new financial year. In July 2026, the President returned both Bills to Parliament for reconsideration rather than assenting to them at that stage. Parliament later adopted the President’s recommendations on the returned Bills on 4 August 2026.

URA’s notice of 23 September 2026 now confirms that both Acts were ultimately assented to with a commencement date of 1 July 2026.

The result is an unusual operational position: the legal commencement date precedes the date on which many taxpayers received final implementation guidance.

That distinction matters because a return can be correctly filed using the information and system configuration available at the time, yet still require amendment once the final legal position and updated return mechanisms become clear.

Which returns has URA told taxpayers to review?

URA’s 23 September notice specifically identifies several returns that may require adjustment:

  • PAYE returns;
  • Excise Duty returns;
  • Withholding Tax returns;
  • VAT returns;
  • Gaming Tax returns, including monthly and weekly returns.

URA’s wording is important. It does not say that every taxpayer must amend every one of these returns. It says taxpayers should review their returns and declarations and make necessary adjustments to reflect the amended provisions from 1 July 2026.

Finance teams should therefore avoid a blanket response.

The correct approach is to identify which legislative changes are relevant to the organisation, determine whether July and August filings were affected, and amend only where the underlying tax treatment changed.

PAYE provides a clear example of the adjustment process

URA has already issued a separate implementation notice dealing with the revised PAYE rates for resident individuals.

That notice confirms that the updated resident-individual PAYE rates apply from 1 July 2026. URA further states that where a July or August 2026 PAYE return was filed before the return update, the employer should amend the affected return using the new PAYE return template.

URA also explains two important consequences.

First, any credit arising from the amendment may be available to the employer for utilisation in a subsequent PAYE return.

Second, employers are required to refund overpaid PAYE to affected employees, which may be achieved through adjustment in a subsequent payroll.

PAYE correction chain:
Tax return → employer tax ledger → payroll → employee balances → future return credits.

If those elements are not reconciled together, a technically correct amended return could still leave accounting or employee-level differences unresolved.

What finance teams should review now

The most practical response is a controlled July/August tax review.

Begin with the filed returns rather than the legislation in isolation.

For each tax type, identify the return actually submitted for July and August, the rate or rule used, the return template version, the amounts recognised in the general ledger and whether the relevant transaction was affected by the amended law.

Where a difference exists, finance should determine the required amendment and document how the revised amount flows through the accounting records.

For PAYE, that means reconciling amended tax to payroll and employee refunds.

For withholding tax, VAT, excise duty and gaming tax, the same principle applies: the corrected return should ultimately reconcile to the underlying transactions and tax-control accounts rather than existing only as an adjustment on the URA portal.

FGL analysis: the real risk is the gap between legal effect and operational implementation

The most useful governance lesson from this situation is broader than the 2026 amendments.

Tax changes often involve three different dates:

  • the date legislation is passed;
  • the date the law legally takes effect; and
  • the date the taxpayer’s systems, templates and operational processes are updated.

Those dates are not always the same.

Here, URA has confirmed a legal commencement date of 1 July 2026 while also instructing taxpayers in September to review July and August filings.

That creates what FGL would describe as an implementation-gap risk.

A company may have filed on time and still need to correct the return.

A payroll system may have calculated tax using the configuration available at the time and still need retrospective adjustment.

A tax-control account may appear reconciled to the original filing and still become incorrect once that filing is amended.

The control response should therefore be broader than asking:

“Did we file the return?”

The better question is:

“Does the return reflect the law that ultimately applied to that period, and does the amended position reconcile through our accounting records?”

A practical July/August review control

A good finance-team review should connect five pieces of evidence:

Legal basis → transaction data → tax computation → return filed → general-ledger balance

Where an amended return is required, the organisation should retain evidence showing why the amendment was made, who reviewed it, how the tax difference was calculated and how the accounting impact was treated.

For PAYE, there should also be evidence that affected employees received the benefit of any over-deducted tax rather than the employer simply retaining the resulting credit.

This becomes particularly important where amendments create credits that will be carried forward into later periods.

Without a clear reconciliation, those credits can become difficult to track and may later create unexplained differences between payroll, tax accounts and URA records.

Do not assume the amendment only affects September onwards

One of the most important points in URA’s notice is the explicit reference to July 2026 and August 2026.

A taxpayer reviewing only September onwards could therefore miss the periods URA specifically says should be reconsidered.

The appropriate review horizon begins on 1 July 2026.

That review should then continue into subsequent periods until the organisation is satisfied that its systems, rates, templates and filing processes fully reflect the amended rules.

What this article does not attempt to do

This brief deliberately does not provide a clause-by-clause analysis of every provision in the 2026 Income Tax and Excise Duty amendments.

The official sources reviewed for this article provide authoritative confirmation of the effective date, the affected return categories and specific PAYE implementation guidance. Parliament’s official materials also document the legislative reconsideration process.

FGL would prefer to base any detailed technical analysis of individual amended provisions on the final assented statutory text rather than infer the final law from earlier Bills.

That deeper analysis can follow once the final enacted text is available in an official, verifiable form.

FGL takeaway

The immediate task for finance teams is straightforward:

Do not wait for the next tax filing cycle. Review July and August 2026 now.

Identify which amendments affect the organisation, amend the relevant returns where required, reconcile those amendments back to accounting and payroll records, document resulting credits or liabilities and make sure the corrected treatment continues into future periods.

The broader lesson is equally important:

Timely filing is only one part of tax compliance. When legislation takes effect retrospectively relative to operational implementation, finance teams also need a controlled process for identifying and correcting filings already submitted.

Authoritative sources

FGL note: This article is an educational compliance brief. It does not replace the final enacted legislation, URA guidance applicable to a taxpayer’s circumstances, or professional advice. Where an amendment affects a specific transaction or tax position, the relevant enacted law and official guidance should be reviewed.

Free tools

Use an FGL calculator

Open the calculator directly instead of navigating through a separate tools page.

Continue with FGL

Practical resources
Discussion

Questions, corrections or another perspective?

Join the conversation below. Keep comments constructive, relevant and free of confidential information.

Popular posts from this blog

Ernst & Young v URA: VAT on Imported Services and the UGX 3.48 Billion Assessment

Jurisdiction: Uganda · Decision: Commercial Court, Civil Appeal No. 26 of 2022 · Judgment date: 11 June 2026 · FGL review: September 2026 Uganda's Commercial Court has upheld a VAT assessment of UGX 3,482,492,210 against Ernst & Young Uganda in a dispute over services received from non-resident group entities and other foreign service providers. The decision is important because it gives businesses a current judicial example of how Uganda's imported-services VAT rules can apply to cross-border support, technology and professional-service arrangements. What the case was about In Ernst and Young v Uganda Revenue Authority , Civil Appeal No. 26 of 2022, the dispute concerned services obtained from entities outside Uganda, including members of the wider EY network and third-party foreign suppliers. URA treated the services as imported services and assessed VAT for the period January 2014 to June 2018. EY challenged the treatment, including arguments about where the s...

Uganda Taxpayer Identification: How NIN, BRN and TIN Work After the 2025 Change

Jurisdiction: Uganda · Topic: Taxpayer identification · FGL review: September 2026 Uganda's taxpayer-identification framework changed in 2025. For tax-law purposes, an individual's National Identification Number (NIN) and a non-individual's Uganda Registration Services Bureau registration number are now used as tax identification numbers. At the same time, URA is still operating legacy TIN services while it integrates NIN, BRN and TIN records. That distinction matters. The legal identifier has changed, but taxpayers should not assume that every existing URA process, account reference or historic TIN has disappeared overnight. What the law changed The Tax Procedures Code (Amendment) Act, 2025 substituted section 4 of the Tax Procedures Code Act. For tax purposes, it provides that: an individual's NIN issued under Uganda's national identification system is used as the tax identification number; a registration number issued by URSB is used for a non-indivi...

IFRS 18 Implementation 2027: A Practical Guide for Finance Teams

IFRS 18 Presentation and Disclosure in Financial Statements becomes effective for annual reporting periods beginning on or after 1 January 2027. For finance teams, however, implementation begins before that date. A calendar-year entity applying IFRS 18 from 1 January 2027 will present 2026 comparative information under the new Standard. This means transactions, account mappings, management performance measures, cash-flow classifications and disclosure data being generated during 2026 may ultimately need to support an IFRS 18 presentation. IFRS 18 replaces IAS 1 Presentation of Financial Statements . Its most visible effect is on the statement of profit or loss, but implementation reaches much further: chart-of-account design, consolidation mappings, management reporting, investor communications, treasury classifications, expense analysis, comparative restatement, financial reporting controls and audit evidence may all need attention. The International Accounting Standards ...