Uganda Wants 15% of Your Software Spend — Here’s What That Means for Tech and Business

Uganda’s proposed 2026 tax amendments introduce a subtle but far-reaching change: payments for software — including SaaS subscriptions like Google Workspace, Microsoft 365, cloud hosting, and other online tools — will now be treated as royalties instead of digital services.

That one classification shift changes everything.

Under the current system, software accessed over the internet typically falls under digital services tax (DST) at 5%. But the amendment redefines such payments as royalties, which attract a 15% withholding tax (WHT).

In plain terms, Uganda is moving from lightly taxing software consumption to treating it as intellectual property usage — and taxing it three times as much.

What changed — and why it matters

The government’s logic is straightforward: when a business pays for software, even via the cloud, it’s effectively paying for the right to use intellectual property.

That aligns with a broader global shift. Countries are increasingly rethinking how to tax digital services, especially as software becomes subscription-based and borderless. Kenya, for instance, introduced a Digital Service Tax (DST) in 2021 (later replaced by a broader Significant Economic Presence tax), while Rwanda applies VAT on digital services consumed locally.

But Uganda’s approach goes further.

Instead of taxing software as a service, it reclassifies it as a royalty, pushing it into a higher tax bracket traditionally used for licensing fees, patents, and intellectual property.

The SaaS reality: where theory meets friction

On paper, the rule is simple:
If a Ugandan business pays $100 for software, it should:

• Withhold $15 (15%) and remit it to URA
• Pay the remaining $85 to the provider

But that’s not how SaaS works in practice.

Most software today is:

• Subscription-based
• Automated (credit card or mobile payments)
• Charged directly by foreign providers

You don’t “withhold” anything from Google, Microsoft, or AWS — they bill your card instantly.

So what happens?

The likely outcome: grossing up

Businesses will still pay the full subscription fee to the provider — and then pay the 15% tax separately to URA.

That effectively turns a $100 subscription into $115.

Multiply that across:

• Cloud hosting
• APIs
• Dev tools
• AI services (OpenAI, GitHub Copilot, etc.)

…and suddenly, software costs in Uganda rise significantly.

Compliance: easier said than done

This is where the policy gets murky.

Who ensures compliance?

• URA expects Ugandan companies to track and declare foreign payments
• But payments are often:
  • Automated
  • Fragmented across teams
  • Paid via cards or fintech platforms

For SMEs and startups, this introduces a new compliance burden:

• Tracking all SaaS spend
• Calculating withholding tax
• Filing returns

And for many, especially smaller businesses, the reality may be simple:
non-compliance — until enforcement catches up.

The ripple effects: beyond just higher costs

1. Software just got more expensive

This is the most immediate impact.

Ugandan businesses rely heavily on foreign SaaS:

• Email and collaboration (Google Workspace, Microsoft 365)
• Cloud infrastructure (AWS, Azure)
• Payments, analytics, CRM, AI tools

A 15% tax layer makes every one of these tools more expensive — at a time when digital adoption is still growing.

2. Will this push more people toward piracy?

It’s a real risk.

Africa already struggles with high software piracy rates, driven by:

• Cost sensitivity
• Limited access to payment methods
• Weak enforcement

By increasing the cost of legitimate software, this policy may unintentionally:

• Push individuals and small businesses toward cracked software
• Undermine cybersecurity
• Hurt compliance and data protection efforts

Ironically, a tax meant to increase revenue could expand the informal software economy.

3. Could vendors pull back from Uganda?

Unlikely — but friction will increase.

Global providers won’t exit Uganda, but they also won’t adapt their systems for local tax compliance.

That means:

• No built-in withholding mechanisms
• No localized billing adjustments
• Limited support for tax documentation

Ugandan businesses will bear the complexity.

4. What about local software companies?

This is where things get interesting.

Locally developed software is not directly targeted by this change — the tax mainly applies to payments to non-resident providers.

That creates a potential advantage:

• Local SaaS providers may become more competitive
• Enterprises may consider switching to Ugandan solutions

But there’s a catch.

Most local tech firms still rely on:

• Foreign cloud infrastructure
• Third-party APIs
• Development tools

So even local players indirectly feel the cost increase.

The bigger picture: digital transformation at a crossroads

Uganda is still in the early stages of digital transformation.

Many businesses:

• Are moving from paper to digital
• Are adopting cloud tools for the first time
• Are integrating payments, CRM, and automation systems

This tax arrives at a critical moment.

From a policy perspective, it makes sense:

• Broaden the tax base
• Capture value from the digital economy
• Align with global tax trends

But from a technology adoption perspective, it introduces friction:

• Higher costs
• More complexity
• Slower adoption for SMEs

Without clear guidance on:

• SaaS vs software licensing
• Automated payment handling
• Compliance thresholds

…the policy risks becoming hard to enforce and easy to bypass.

The AI angle: a new layer of cost

Just as businesses begin adopting AI tools — from coding assistants to automation platforms — this tax quietly raises the cost of entry.

AI is lowering the cost of building software globally.
But in Uganda, this tax could raise the cost of accessing that innovation.

That creates a paradox:

• Development is getting cheaper
• Access is getting more expensive

What happens next?

The amendment is still subject to parliamentary approval, and implementation details will likely come from URA guidelines.

Key questions remain:

• Will there be thresholds for small businesses?
• Will card-based payments be treated differently?
• Will URA enforce strictly or gradually?