WHT on Software, SaaS, and Digital Services:How Saudi Arabia Taxes Tech Payments

Technology payments sit at the intersection of royalties (15%) and technical services (5%) — and the Saudi WHT framework was not specifically designed for the subscription economy, cloud computing, or API-based digital services. This creates genuine classification ambiguity that finance and procurement teams must navigate carefully.

The volume of tech payments flowing from Saudi businesses to non-resident technology vendors has grown rapidly with Vision 2030 digitalisation initiatives, cloud migration programmes, and global software standardisation. Every subscription renewal, every SaaS licence fee, every cloud compute invoice from AWS, Azure, or Google is a potential WHT event. For large enterprises, the cumulative annual exposure across dozens of tech vendor relationships can be substantial.

The core classification question is the same as for all WHT categories: what is the Saudi entity paying for? A right to use the vendor’s IP (royalty, 15%)? A service that the vendor actively provides (technical service, 5%)? Or a combination of both? The answer is not always in the contract title — it requires an analysis of the substance of the arrangement.

Perpetual or term licences for software installed and run on the Saudi entity’s own infrastructure are royalties. The Saudi entity pays for the right to use the vendor’s proprietary code. The vendor does nothing more after delivering the licence — the Saudi entity uses the right independently.

This category is clear: enterprise software licences (ERP, CRM, database licences, operating systems), perpetual or annually renewed, where the software runs on the customer’s hardware or private cloud, are subject to 15% WHT as royalties. This includes Microsoft EA licences for on-premise software, Oracle database licences, SAP software licences, and similar arrangements.

Software-as-a-Service (SaaS) subscriptions are the most difficult category. The Saudi entity does not receive a software licence to install or run — it accesses the vendor’s hosted software through a browser or API. The vendor maintains, hosts, updates, and runs the software. The Saudi entity gets an output: the ability to use the application.

The classification debate: is a SaaS subscription a right to use software (royalty, 15%) or a service being delivered by the vendor (technical service, 5%)? Two credible analytical positions exist:

Royalty position: The SaaS customer is paying for a time-limited right to access and use the vendor’s proprietary application. The underlying IP being exploited is the software. Whether accessed locally or via the cloud, the economic character is a use-right — a royalty.

Service position: The vendor actively operates, maintains, updates, and delivers the service. The customer is not using software they control — they are consuming an output. This is more analogous to a service being performed for the customer’s benefit, similar to outsourcing.

ZATCA has not issued specific published guidance distinguishing SaaS from traditional software licences at the time of writing. The prevalent approach among Saudi tax practitioners is to analyse the substance of each arrangement: where the customer has limited control, cannot customise the underlying software, and is essentially consuming a standardised output, the service classification is stronger. Where the customer has a defined licence with specific user counts and access rights tied to the vendor’s IP, the royalty classification is stronger.

Cloud infrastructure — compute, storage, networking sold as a utility (IaaS) — presents a different analysis from SaaS. The customer is purchasing compute resources and storage capacity. The vendor (AWS, Azure, GCP) operates the hardware and infrastructure; the customer runs its own workloads on rented capacity. There is no specific software licence granted — just infrastructure access.

The strongest classification for IaaS-type cloud services is technical services (5%) — the vendor is providing a technical/computing service rather than licensing proprietary software. The customer has no right to the underlying IP; they are simply consuming infrastructure capacity. This analysis is more defensible than for SaaS, where the vendor’s proprietary application is directly being used.

Platform-as-a-Service (PaaS) arrangements fall between IaaS and SaaS and require case-by-case analysis. Where a PaaS arrangement gives the customer access to proprietary development tools and platform capabilities, a royalty element may be present.

Payments for digital content licences (data feeds, databases, media content) are royalties — the payment is for a right to use or access content owned by the non-resident. Payments for API-based data services (where the vendor delivers data outputs on request) are more likely technical services — the vendor is actively retrieving and processing data to deliver outputs.

Payments for online advertising platforms (Google Ads, Meta advertising) are a separate and often-overlooked WHT category. Where a Saudi company pays a foreign digital advertising platform for advertising services, the WHT analysis depends on whether the payment is for a service (placing ads) or a licence (using the platform). Most digital advertising payments are best characterised as services at 5%, though this requires confirmation against the specific platform terms.

International telecommunications services attract 5% WHT. However, Ministerial Resolution No. 484 (published November 2022) introduced a specific exclusion: amounts paid for a local telecoms company’s use of an international network to pass, transfer, or deliver Saudi subscribers’ calls, and amounts paid for international roaming services, are not subject to WHT.

This exclusion is narrow and applies to the technical interconnection and roaming infrastructure costs of Saudi telecoms operators — not to general digital or internet service payments. A Saudi company paying a foreign telecoms provider for international calling services is still within scope of the 5% WHT. The exclusion benefits Saudi telecoms operators, not their corporate customers.

Does Microsoft 365 (cloud subscription) attract 5% or 15% WHT?

Microsoft 365 is a SaaS subscription — Microsoft hosts and delivers the software as a service. The classification debate applies. Many practitioners treat it as a royalty (15%) given that the subscription is fundamentally a time-limited right to access Microsoft’s proprietary application suite. However, the service delivery element (Microsoft actively runs, hosts, and updates the software) supports a 5% technical service position. Given the uncertainty and ZATCA’s absence of specific guidance, the conservative approach is 15% with documentation. Amounts are often material for large enterprise Microsoft agreements — seek specific advice.

What about subscriptions to data analytics or AI platforms?

Data analytics platforms where the vendor processes and returns outputs (analysis, reports, scores) are most naturally characterised as technical services at 5% — the vendor is actively doing work. Platforms that grant access to a proprietary AI model or analytics tool that the Saudi entity uses itself to run its own queries are closer to a royalty (15%) for access to the IP. The distinction matters enormously at scale.

How should a Saudi company handle WHT compliance for dozens of small SaaS subscriptions?

The WHT obligation applies regardless of the size of the payment. There is no de minimis threshold. However, ZATCA’s practical enforcement focus on small-value payments is limited compared to large contracts. The risk-proportionate approach for small SaaS subscriptions is: classify consistently, withhold correctly, maintain records, and remit on the standard monthly cycle. Finance teams should build SaaS WHT tracking into their accounts payable workflow rather than treating it as a one-off exercise.