What Just Happened: The VAT on Digital Services Explained

On January 1, 2026, Zimbabwe implemented what Finance Minister Professor Mthuli Ncube called a necessary step to level the playing field: VAT on imported digital services, collected through a withholding mechanism. The tax was announced in the November 2025 budget presentation and became law through Finance Act No. 7 of 2025.

The Official Rationale

According to Minister Ncube, the problem was straightforward. Foreign digital platforms like Netflix, Spotify, Amazon Prime, and even satellite internet provider Starlink were generating substantial revenue from Zimbabwean consumers without paying local taxes. Meanwhile, local service providers operating within Zimbabwe faced the full burden of domestic taxation—creating an uneven playing field.

"Payments for digital services are largely remitted offshore without being subjected to value-added tax or income tax. This gives foreign digital platforms an unfair competitive advantage over local service providers who are fully taxed within Zimbabwe." — Finance Minister Mthuli Ncube

The tax applies to a wide range of services:

• Subscription streaming platforms (Netflix, Spotify, Apple Music, YouTube Premium)
• Digital advertising (Google Ads, Meta advertising products)
• E-commerce platforms and marketplaces
• Cloud computing and storage services (iCloud, Google Drive, Dropbox)
• Satellite internet services (Starlink)
• E-hailing app commissions (Bolt, InDrive)
• Online gaming platforms
• Software-as-a-Service (SaaS) platforms

The implementation mechanism is clever: banks and mobile money operators act as withholding agents, collecting the VAT at the point of payment before funds leave the country. They then remit the collected taxes to the Zimbabwe Revenue Authority (ZIMRA) within 30 days.

Zimbabwe Joins a Growing Trend

Zimbabwe isn't alone in this approach. Several African countries have implemented similar digital services taxes, including Nigeria, Kenya, Uganda, Tanzania, and Sierra Leone. The global trend reflects governments' attempts to capture tax revenue from the rapidly digitizing economy.

The Implementation Chaos: A Tax Written in Confusion

What should have been a straightforward tax policy quickly descended into confusion, revealing the challenges of implementing tax policy in a complex digital ecosystem.

The Drafting Concerns That Shook Businesses

According to multiple reports and commentary from legal professionals, the Finance Act contained wording that raised significant concerns. Media reports and professional analysis noted that the language could be interpreted to apply to both goods and services supplied from outside Zimbabwe—not just digital services as the government intended.

This wasn't what the government claimed to intend—they stated publicly that the tax should only apply to digital services, not physical goods purchased online. But the law's actual wording created uncertainty.

Businesses importing physical goods suddenly faced potential additional tax liability on top of existing customs duties and VAT. The business community erupted in protest.

The Double Taxation Concerns

Another major concern emerged during implementation: many foreign digital services already charge customers VAT. With the new VAT collection mechanism also being applied, consumers feared paying tax twice on the same service—clear double taxation.

ZIMRA's response addressed this concern: according to official guidance, businesses already formally declaring and paying VAT on imported digital services through their tax returns wouldn't be subject to the withholding mechanism on the same transactions. However, this created operational challenges that ZIMRA acknowledged.

As ZIMRA Head of Technical Services for Domestic Taxes Mathias Chinanayi admitted to The Herald, "operational challenges remain," particularly around foreign service providers already charging VAT and the difficulty of separating goods from services on complex online platforms. He added that "work is ongoing to refine the framework and bring consistency and certainty."

In other words: the tax was implemented first, the details would be figured out later. Real money from real people would be at stake during this "refinement" period.

The Beautiful Irony: Banks as Tax Collectors and Taxpayers

Here's where the story gets interesting. The banks have been appointed as ZIMRA's collection agents for this tax. Every time a Zimbabwean pays for a foreign digital service, the bank must handle the VAT collection process—though the practical mechanics of distinguishing goods from services on every transaction remains one of the "operational challenges" ZIMRA admits is still being refined.

The expected responsibilities include:

1. Processing payments for digital services from foreign providers
2. Collecting the applicable VAT
3. Providing documentation to taxpayers
4. Remitting the collected tax to ZIMRA within specified timeframes

Failure to properly collect or remit the tax carries penalties and interest under the relevant tax legislation. The burden is real, the responsibility is clear, and the stakes are high.

But here's the twist that makes you smile: Zimbabwean banks are themselves among the country's biggest consumers of foreign digital services.

The Core Banking Conundrum

Many banks globally—and Zimbabwean financial institutions are no exception—rely heavily on foreign-developed core banking software. These aren't small subscriptions—they're substantial licensing agreements with ongoing maintenance fees, upgrade costs, and customization charges.

Major core banking platforms used by financial institutions worldwide include:

• Temenos T24 Transact: Used by over 700 banks globally. License fees can run into millions of dollars, with annual maintenance often 20-25% of the license cost.
• Oracle FLEXCUBE: Deployed at 600+ financial institutions across 140 countries. A comprehensive core banking platform with modules for retail, corporate, and investment banking.
• Infosys Finacle: Used by banks in 100+ countries, serving over 1 billion customers worldwide. Pricing based on scale of deployment and modules required.

Industry observers have long noted that financial institutions often end up paying for extensive feature sets and modules that they don't fully utilize, as these platforms are designed for global markets with varying regulatory and operational needs.

The Multi-Million Dollar Question: Core Banking Systems

Let's consider some illustrative scenarios. Imagine a financial institution with a major core banking platform implementation:

• Initial license and implementation: Multi-million dollar investment (scale varies widely by institution size and modules)
• Annual maintenance and support: Typically 20-25% of license cost
• Upgrade costs: Significant investments every few years
• Customization and integration: Ongoing annual expenses

Now consider the VAT implications on all of these payments. For institutions with substantial annual software expenditure, the additional tax burden becomes a meaningful line item in the budget.

Who Handles the Bank's VAT Compliance?

Here's the delicious irony: when a bank receives an invoice from Temenos, Oracle, or Infosys for their core banking software services, who exactly is responsible for handling the VAT compliance on that payment?

The bank itself must ensure proper tax treatment. But the regulations were written with consumer transactions in mind—Netflix subscriptions, Spotify payments, Starlink bills. The specifics of how banks handle VAT on their own substantial enterprise software purchases is one of those operational details still being refined.

Will banks rigorously apply the same standards to their own foreign software purchases as they do to consumer transactions? Will ZIMRA audit bank expenditures to ensure compliance? These are fair questions, and the answers aren't entirely clear yet.

The Real Cost: Who Actually Pays?

Taxes are rarely paid by those who remit them. In reality, the cost of the VAT on imported digital services will be passed along through various channels:

For Consumers

Your streaming subscriptions and cloud storage services just got more expensive. The combined impact of the digital services VAT, the 2% Intermediated Money Transfer Tax (IMT), and bank transaction fees can add up quickly.

Practical example based on typical transaction costs:

• Streaming service $10 subscription:
• Digital Services VAT: Applicable percentage
• IMT (2%): $0.20
• Bank transaction fee: Varies by provider
• Total additional costs can approach 20-30% on top of the base subscription price

For Banks

Banks face a strategic dilemma. They can:

1. Absorb the cost: Accept the increased software expenses and protect profit margins elsewhere
2. Pass it to customers: Increase banking fees to cover higher software costs
3. Seek alternatives: Explore local software solutions that don't trigger the imported services VAT

Option 3 is where things get interesting.

For Foreign Software Vendors

Companies like Oracle, Temenos, and Infosys might face pressure to adjust their pricing for the Zimbabwean market. Zimbabwe is a relatively small market—it's unlikely these global giants will make special concessions. More likely, they'll maintain their pricing and let Zimbabwean institutions deal with the increased cost.

Zimbabwe's Local Tech Scene: Ready or Not?

The question everyone is asking: can Zimbabwe's local tech sector actually fill this gap? The short answer is complicated—there's talent, there's potential, but there are also significant challenges.

The Talent is Real

Zimbabwe has consistently produced high-quality software developers. The country has a strong tradition of technical education, with universities like the University of Zimbabwe, National University of Science and Technology (NUST), and Harare Institute of Technology producing capable graduates.

The local tech ecosystem includes:

• Established companies: Econet Wireless, Cassava Smartech, Liquid Intelligent Technologies
• Tech hubs: Tech Hub Harare, Muzinda Hub, Moto Republic
• Emerging startups: Companies like Cashlinq (banking software as a service), NeedEnergy (AI-powered energy management), and dozens of fintech and software development firms

The Cashlinq Case Study

One particularly relevant example is Cashlinq, a Zimbabwean startup that has developed banking software as a service for African markets. Founded in 2022, Cashlinq positions itself as a solution that can work alongside or complement established core banking systems like T24 and FLEXCUBE, offering affordability and flexibility to banks and fintechs.

According to a 2023 Techzim report, Cashlinq has been expanding its footprint, working with financial institutions and mobile network operators. The company secured a deployment with a digital-only bank in Zambia and has been engaging with various financial service providers in the region to build solutions including second-generation mobile money wallets.

The company's value proposition is compelling: rather than adopting comprehensive foreign software packages where features may go unused, Cashlinq builds solutions tailored to local needs and regulatory requirements.

Other Notable Local Players

Zimbabwe's tech scene is growing, with companies offering various solutions:

• ZimHero: Custom software development, ERP systems, web and mobile apps
• Tyflex Investments: ERP, VoIP, and POS systems
• Kilomarket: Web design, branding, and marketing
• Various fintech startups: Including Golix, Access Forex, and Microhub Financial Services

However, most of these companies haven't yet built enterprise-grade core banking systems capable of running a major commercial bank. That level of complexity requires years of development, extensive testing, regulatory approval, and most critically—trust from highly regulated financial institutions.

The Accidental Business Case for Local Development

Here's where the VAT on imported digital services becomes potentially transformative. Before this tax, the business case for local software development competed against established foreign solutions on features, reliability, and brand recognition. Now, there's a new factor: cost.

The Math is Compelling

Let's model an illustrative scenario (note: actual contract values vary widely by institution):

Option A: Foreign Core Banking System

• Implementation and licensing: Substantial upfront investment
• Annual maintenance and support: Ongoing significant cost
• VAT on imported services: Adds to total cost of ownership
• Total ongoing annual cost: Significantly increased versus pre-2026

Option B: Local Development Partnership

• Custom development investment: Potentially lower initial outlay
• Annual maintenance and enhancement: Can be more cost-effective
• No imported services VAT (local company)
• Local talent employment creates additional economic benefits
• Potentially more attractive total cost of ownership

While specific numbers depend entirely on individual contracts and requirements, the principle is clear: VAT on foreign software fundamentally changes the economics of the build-versus-buy decision.

Beyond Cost: Strategic Benefits

Local development offers advantages beyond just tax considerations:

• Regulatory agility: When Zimbabwe's Reserve Bank changes a regulation, a local vendor can potentially adapt more quickly than waiting for a global vendor's release cycle.
• Local support: No waiting for responses from teams in different time zones. Your developers could be in Harare, operating in the same business environment.
• Feature relevance: Software built for Zimbabwean financial institutions by developers who understand the local context can naturally align with local use cases.
• Economic multiplier: Money spent on local development stays in Zimbabwe, creating jobs, building capacity, and strengthening the ecosystem.
• Data sovereignty: Increasing concerns about data privacy and sovereignty can favor solutions where data stays in-country.

The Hard Truth: Why Local Tech Still Faces Headwinds

Before we get too optimistic, let's acknowledge the real challenges facing Zimbabwe's local tech sector in competing for major banking software contracts.

1. The Trust Deficit

Banking is conservative by nature and by regulation. Banks are entrusting their core operations—every transaction, every account, every customer interaction—to their core banking system. A failure means catastrophic loss of money, reputation, and regulatory approval.

Established foreign software vendors offer:

• Decades of proven track record
• Hundreds or thousands of global implementations
• Financial stability and guaranteed long-term support
• Comprehensive insurance and liability coverage
• Regulatory approvals in multiple jurisdictions

A local startup, no matter how talented, struggles to match this credibility. "We built something great" is a tough sell when you're asking a bank to bet its entire operation on you.

2. Capacity Constraints

Core banking systems are enormously complex. They must handle:

• Real-time transaction processing at scale
• Multi-currency operations
• Loan origination and servicing
• Treasury and risk management
• Regulatory reporting
• Integration with payment networks, mobile money, cards, etc.
• 24/7 availability with disaster recovery
• Security and fraud prevention

Building software that does all of this reliably requires large teams of experienced developers working for years. Most Zimbabwean tech companies don't have the capital or capacity for this level of undertaking.

3. Infrastructure Challenges

Zimbabwe's tech sector operates under difficult conditions:

• Power outages: Unreliable electricity disrupts development and testing
• Internet connectivity: While improving, still inconsistent and expensive in some areas
• Brain drain: Top talent often leaves for better opportunities abroad
• Limited capital: Venture funding is scarce; banks are risk-averse
• Equipment costs: Hardware and development tools are expensive in foreign currency

4. The Regulatory Maze

Getting a software solution approved for use in regulated financial institutions requires navigating complex certification processes. Foreign vendors have teams dedicated to regulatory compliance across markets. Local startups often lack this specialized expertise.

Real Opportunities: Where Local Tech Can Win

Despite the challenges, there are genuine opportunities for Zimbabwe's tech sector. The key is to be strategic about where to compete.

Strategy 1: Complementary Solutions, Not Core Replacement

Rather than trying to replace established systems entirely, local developers can build complementary solutions that reduce dependency on expensive foreign modules:

• Customer-facing applications: Mobile banking apps, internet banking portals
• Reporting and analytics: Business intelligence dashboards tailored to local regulatory requirements
• Integration middleware: Connectors between core systems and local payment networks
• Specialized modules: Local compliance reporting, ZIMRA tax integration, mobile money connectivity

These solutions can interface with existing core banking systems while delivering specific value that justifies the investment.

Strategy 2: Target Smaller Institutions

Microfinance institutions, savings and credit cooperatives, and smaller financial service providers have simpler needs than major commercial banks. They're also more price-sensitive and potentially more willing to consider innovative solutions.

Success with smaller institutions builds the track record needed to approach larger banks eventually.

Strategy 3: Platform Approach

Rather than building everything from scratch, local companies can adopt a platform approach:

• Use proven open-source components for standard functions
• Focus development effort on local customization and integration
• Partner with international vendors for specific modules
• Build on modern cloud infrastructure for scalability and reliability

This approach allows local companies to provide banking software as a service rather than trying to replicate decades of established platform development.

Strategy 4: Form Consortiums

No single Zimbabwean tech company might have the capacity to build a complete core banking system alone. But a consortium of local companies, each contributing their specialization, could collectively compete:

• One company handles transaction processing
• Another specializes in security and fraud detection
• A third focuses on regulatory reporting and compliance
• A fourth provides customer experience and digital channels

Together, they could offer a comprehensive solution that keeps more money in the local economy while meeting institutional needs.

The Bottom Line: Will We Pay 15.5% and Complain, or Build?

Zimbabwe's VAT on imported digital services is now reality. The implementation has been messy, the regulations remain unclear in places, and consumers are rightfully frustrated about higher costs for streaming services and cloud storage.

But hidden within this frustration is a genuine opportunity. The tax has fundamentally changed the economics of software procurement in Zimbabwe. Foreign code just got more expensive. Local talent costs the same as it did yesterday.

The Universe is Sending a Signal

When banks—the very institutions mandated to collect this tax from consumers—face their own substantial invoices for foreign core banking systems, perhaps they'll start asking different questions:

• Do we really need all these features we barely use?
• Could a local solution meet our core needs at a more attractive total cost of ownership?
• What if we invested in building local capacity instead of sending millions offshore?
• Could this be an opportunity to differentiate our institution with truly localized services?

These are the questions that could spark transformation.

The Choice Ahead

Zimbabwe's tech sector stands at a crossroads. One path leads to simply accepting higher costs and complaining while continuing to import solutions. This is the easy path, the path of least resistance, the path of maintained mediocrity.

The other path is harder but potentially transformative: use this tax as the catalyst it could be. Build local solutions. Take calculated risks on local talent. Create the success stories that attract capital and build trust. Develop the track record that makes the next institution say, "Why not consider the local option?"

"The cost of importing code just went up. The cost of hiring Zimbabwean talent stayed the same. You do the math."

The math is compelling. The opportunity is real. The challenges are significant but not insurmountable. What's missing is will—the willingness of financial institutions to explore local solutions, the willingness of government to support local tech development with policy and procurement, and the willingness of investors to fund the patient capital needed to build enterprise-grade software.

A Question for the Decision Makers

To the bank executives reviewing your software budgets and seeing those new VAT implications: is this the wake-up call you needed? Will you reach out to local developers and have conversations about alternatives? Will you set aside a portion of your IT budget to pilot local solutions for non-critical systems and see what's possible?

To the tech entrepreneurs building the future in Harare, Bulawayo, and beyond: is this the business case you've been waiting for? Will you organize, collaborate, and pitch compelling alternatives? Will you build solutions worth trusting with serious operations?

To the policymakers at ZIMRA and the Ministry of Finance: beyond collecting tax revenue, will you intentionally use this policy to nurture local tech development? Will you create incentives for institutions to pilot local solutions? Will you streamline regulatory approval for locally-developed systems?

The Answer Isn't Clear Yet

It's entirely possible that Zimbabwe will simply pay the extra VAT and complain. Habits are hard to break, foreign brands have strong appeal, and risk aversion is rational in banking.

But it's also possible—just possible—that some executive at some institution will look at their increased software expenses and think, "There has to be a better way." And that executive will pick up the phone and call a local tech company. And together, they'll build something that works.

If that happens once, it could happen again. And again. And eventually, Zimbabwe might have a thriving software industry that serves not just local institutions, but exports solutions across Africa—solutions built by Zimbabweans who stayed home instead of seeking opportunities abroad.

The VAT on imported digital services might be the accidental catalyst Zimbabwe's tech sector has been waiting for. Or it might just be another frustrating cost in a difficult economy.

The difference depends entirely on what we choose to do next.

So the question stands: Is this the push our local tech sector needed, or are we just going to pay the extra 15.5% and complain?

Time will tell. But the opportunity is there, staring us right in the face, attached to every invoice with implications that are impossible to ignore.