Royalties attract 15% WHT on the gross payment — the middle tier in the Saudi framework. IP-intensive businesses and technology groups face this rate on every licence fee, patent royalty, and know-how payment flowing out of the Kingdom.
Blog
-
WHT on Royalties and Licence Fees in Saudi Arabia: What Finance Teams Must Know
WHT on Royalties and Licence Fees in Saudi Arabia: What Finance Teams Must Know Dariba.co Saudi Tax Intelligence 01What Are Royalties for Saudi WHT Purposes?
The Saudi WHT framework does not provide a statutory definition of “royalties” in Article 63 — it lists the rate without defining the category. This is deliberate: the term is understood by reference to its ordinary commercial meaning and to OECD treaty principles where a DTT applies.
In practice, royalties cover payments for the right to use intellectual property. This includes: patent licences; trademark licences; copyright licences; software licences (the use-right component); know-how and trade secret payments; technology transfer fees; brand royalties; and any other payment for the right to use a proprietary intangible asset owned by the non-resident. The 15% rate applies to the full gross payment — before any deduction for costs or expenses incurred by the non-resident in generating or maintaining that IP.
The essential characteristic is that the Saudi party is paying for a right — to use, to reproduce, to exploit — not paying for a service to be performed. The non-resident does not do anything more after the licence is granted; the Saudi entity uses the right. That use-right character distinguishes royalties from services at the conceptual level, though in practice many technology contracts blur both elements.
Software Licences — A Common and Often Mishandled Category
Software licences are one of the most frequently encountered royalty payments in Saudi Arabia and one of the most frequently misclassified. A licence fee for the right to use a non-resident’s software — to install it, to run it, to access it — is a royalty subject to 15% WHT. It does not matter whether the software is delivered on physical media, downloaded, or accessed as a cloud-based SaaS product. The right-of-use character determines the rate.
Where a software contract bundles licence fees with implementation services, the two components carry different WHT rates (15% and 5% respectively) and should ideally be separately identified and priced in the contract. A combined lump-sum contract may result in ZATCA applying the higher rate (15%) to the entire payment if it cannot determine the service element with certainty.
Worked Example — Software Licence FeeRiyadh-based logistics company Gulf Routes Co. pays a US software company SAR 600,000 per year for a perpetual licence to use supply chain management software. There is no service element — the US company provides the licence and the Saudi company uses the software independently.
WHT rate: 15% (royalty — right to use software). WHT: SAR 90,000. Gulf Routes remits SAR 510,000 to the US company and SAR 90,000 to ZATCA within the first 10 days of the following month.
02Know-How and Technology Transfer Payments
Know-how payments — fees for access to undisclosed proprietary technical or commercial information — are royalties. These arise frequently in manufacturing licensing agreements, franchise arrangements, and technology transfer contracts. Where a non-resident grants a Saudi entity access to its confidential process knowledge, formulations, or operational procedures in exchange for an ongoing fee, that fee is a royalty at 15%.
Franchise fees — periodic payments for the right to use a foreign brand, system, and associated know-how — are similarly royalties. Franchise arrangements that combine brand royalties with management services should be disaggregated: the royalty component at 15% and any genuine management component at 20%.
03The Royalty vs Service Distinction in Practice
The line between a royalty (15%) and a service (5%) is crossed when the non-resident actively performs work rather than simply granting a right of use. The test is: after the payment, is the non-resident’s obligation discharged (royalty), or does the non-resident continue to deliver something (service)?
A perpetual software licence: royalty. An annual maintenance and support contract for that software: service. A database access licence: royalty. A data analytics consultancy using that database: service. The categorisation requires a payment-by-payment analysis — not a contract-level assumption.
SaaS and Cloud ServicesSaaS and cloud service arrangements present a genuine classification challenge. Where the non-resident provides an ongoing service (hosting, processing, delivering outputs) and the Saudi entity has no right to use the underlying software independently, the payment may be closer to a service than a licence. But where the SaaS arrangement is effectively a time-limited software use right, royalty treatment is more appropriate. This is an area where ZATCA’s position continues to develop and professional advice should be sought for material SaaS contracts. See the dedicated article on Software, SaaS, and Digital Services WHT for deeper analysis.
04Treaty Relief on Royalties
Saudi Arabia’s DTTs frequently reduce the domestic 15% royalty WHT rate. Many treaties provide for a 10%, 8%, or even lower rate on royalties paid to qualifying residents of the treaty partner country. Some treaties distinguish between different types of royalties — software and database royalties may be treated differently from industrial patent royalties in certain treaties.
To claim treaty relief, the non-resident must provide: a valid residency certificate from the competent authority of their home country; evidence of beneficial ownership of the royalty income; and satisfaction of any other treaty conditions. The certificate must be in place before the payment is made at the reduced rate. Filing for a refund of over-withheld tax after the fact is possible but administratively complex.
Worked Example — Treaty Reduction on RoyaltiesAl-Baraka Technology Co. pays a French company SAR 400,000 in annual patent royalties. The Saudi-France DTT reduces the royalty withholding rate to 8% (confirm the applicable treaty rate with current treaty text and professional advice).
Without treaty: 15% × SAR 400,000 = SAR 60,000 WHT. With treaty (8%): SAR 32,000 WHT — a saving of SAR 28,000 per year. The French company must provide a valid French tax residency certificate and demonstrate beneficial ownership of the royalty. Al-Baraka maintains the certificate and documentation for 10 years.
05FAQs — WHT on Royalties
Are trademark licence fees subject to 15% WHT?
Yes. Payments for the right to use a non-resident’s trademark in Saudi Arabia are royalties, subject to 15% WHT on the gross payment. This applies to brand licences, franchise royalties based on turnover, and any periodic payment for trademark use rights — regardless of whether the trademark is for a product, a service brand, or a hospitality concept.
If I buy a perpetual software licence with a one-time payment, does WHT still apply?
Yes. The WHT obligation arises at the point of payment, not as a recurring annual obligation. A one-time lump sum for a perpetual software licence is still a royalty payment — the character of what is being paid for (a right of use) is the same regardless of the payment structure. WHT of 15% applies to the full one-time payment at the time it is made.
What documentation should I keep for royalty WHT payments?
The minimum required records are: recipient name and address, type and amount of payment, and amount withheld — maintained for 10 years. In practice, you should also retain: the licence agreement; invoices; payment confirmations; and, where a treaty rate applies, the residency certificate and beneficial ownership documentation. ZATCA audits of IP payment structures are one of the more intensive audit areas in Saudi tax, and thorough documentation is essential.
Key Takeaways- Royalties attract 15% WHT on the gross payment — covering patents, trademarks, copyrights, know-how, and software licences.
- Software licences are royalties regardless of delivery method (physical, download, or cloud-based access), provided the payment is for a right of use rather than an active service.
- Blended contracts (licence + services) should be disaggregated: 15% on the licence fee and 5% on the service component. Lump-sum contracts risk the higher rate being applied to the whole.
- Treaty relief can reduce the 15% domestic rate — but requires proactive documentation including a valid residency certificate obtained before the payment date.
- IP payment structures are a primary ZATCA audit focus. Maintain complete documentation for 10 years from each payment date.
WHT on Software, SaaS, and Digital Services:How Saudi Arabia Taxes Tech Payments
Software and digital payments are among the fastest-growing cross-border payment categories for Saudi businesses — and among the most frequently misclassified for WHT. The royalty vs service distinction has never been more practically important than in the SaaS era.
Why Tech Payments Are the Most Contested WHT Category
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.
Traditional Software Licences — Generally Royalties
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.
Najd Industrial Co. pays SAR 1.2 million annually to renew its SAP ERP software licence. The licence covers the right to run the SAP software on Najd’s own servers in Saudi Arabia. No services — just the licence right.
WHT: 15% × SAR 1.2 million = SAR 180,000. SAP (or its licensing entity) receives SAR 1.02 million. Najd remits SAR 180,000 to ZATCA by the 10th of the following month. Over 5 years, this is a SAR 900,000 WHT cost on a SAR 6 million licensing relationship.
SaaS Subscriptions — The Grey Zone
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.
Given the absence of definitive ZATCA guidance on SaaS classification, the conservative approach — and the one most defensible in an audit — is to treat SaaS subscriptions as royalties (15%) unless a well-reasoned service analysis can be documented. Applying 5% without documentation exposes the Saudi payer to a 10-percentage-point assessment shortfall plus delay penalties. If the amounts are material, seek a formal position from a qualified Saudi tax advisor.
Cloud Infrastructure Services
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.
Digital Content and API Services
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.
Telecommunications Services — The 2022 Exclusion
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.
FAQs — Software and Digital Services WHT
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.
- Traditional on-premise software licences are royalties at 15% — the right-to-use character is clear.
- SaaS subscriptions are genuinely ambiguous — the conservative position is 15% (royalty) absent a well-documented service analysis. Seek specific advice for material SaaS contracts.
- Cloud infrastructure (IaaS) is most defensibly classified as technical services at 5% — the vendor is selling compute capacity, not licensing proprietary software.
- The 2022 telecoms exclusion narrows the scope of the international telecoms WHT — but only for interconnection and roaming costs of Saudi telecoms operators, not for general digital service payments.
- Document the classification basis for every material tech vendor payment. ZATCA audits of tech payment WHT treatment are increasing as digital spend grows.