Withholding tax is the obligation most often discovered late, and it is discovered late for a structural reason: it is a tax on somebody else's income that you are legally required to collect. The money belongs to your foreign supplier, the liability belongs to you, and nothing in your own tax position signals that you have missed it. Companies routinely pay a foreign consultant, a software licensor or a regional head office in full for years, and only learn what they owe when an assessment arrives covering every one of those payments at once. This page sets out what withholding tax in Saudi Arabia applies to, the rate each type of payment carries, when it has to be remitted, how treaty relief actually works in practice, and where the obligation most reliably breaks.
Withholding tax (WHT) is tax deducted at source by a payer in Saudi Arabia from a payment made to a non-resident, where that payment is income arising from a source inside the Kingdom. It is governed by the Income Tax Law and its By-Laws and administered by the Zakat, Tax and Customs Authority (ZATCA). The payer deducts the applicable percentage from the gross amount due, pays the balance to the supplier, and remits the deduction to ZATCA on the supplier's behalf.
Three properties of that mechanic explain almost every problem companies have with it.
Who has to withhold. The obligation attaches to a resident making a payment to a non-resident, and "resident" here is broader than most companies assume: it covers resident companies and establishments, permanent establishments of foreign companies in the Kingdom, and government and public bodies. Critically, it does not depend on your own tax status. A company wholly owned by Saudi or GCC nationals, which files Zakat rather than corporate income tax and never calculates a riyal of income tax on itself, still has to withhold on its payments to non-residents. Finance teams in Zakat-paying groups are the ones most likely to have never looked at this at all.
What makes a payment Saudi-sourced. The source rules in the Income Tax Law determine whether a payment falls in scope at all - broadly, income from an activity carried on in the Kingdom, from property located here, from a loan used here, or paid by a resident. The genuinely contested edge is services performed entirely outside the Kingdom for the benefit of a Saudi business: a foreign firm that never sends anyone to Riyadh but advises a Riyadh client. ZATCA has historically taken an expansive view, and outcomes on appeal have not been uniform. We do not pretend that is settled, and we would treat any adviser who states it flatly in either direction with caution. What we do is document the position taken, the facts it rests on and the reasoning behind it at the time of payment - because the difference between a defensible position and an indefensible one is usually the file, not the answer.
Withholding is one obligation inside a single relationship with one regulator - Zakat, corporate income tax, VAT, e-invoicing and customs now sit with ZATCA and increasingly share one audit trail. Our Tax & Zakat advisory practice covers that relationship as one engagement rather than as separate problems handled by separate people.
Saudi withholding tax has no brackets in the progressive sense. The rate is fixed by the type of payment, and the schedule has been stable since the Income Tax Law came into force. There are three rates - 5%, 15% and 20% - and which one applies is decided by how the payment is characterised.
| Type of payment to a non-resident | Withholding rate |
|---|---|
| Rent | 5% |
| Technical and consulting services (paid to an unrelated party) | 5% |
| Air tickets, and air or maritime freight | 5% |
| International telecommunications services | 5% |
| Dividends | 5% |
| Loan charges (interest) | 5% |
| Insurance and reinsurance premiums | 5% |
| Royalties | 15% |
| Payments to a head office or a related party for services | 15% |
| Any other payment not otherwise listed | 15% |
| Management fees | 20% |
Read that table as a classification problem rather than a rate table, because that is what it is in practice. The same commercial arrangement can sit at 5%, 15% or 20% depending on how the contract characterises it - and ZATCA reads the substance of what was supplied, not the description typed on the invoice. Three boundaries account for most disputes:
Two further mechanics change the arithmetic. First, withholding is calculated on the gross amount - there is no deduction for the supplier's costs, no netting against amounts they owe you, and no relief because the engagement was loss-making for them. Second, many contracts with foreign vendors carry a gross-up clause requiring you to pay the supplier the full invoiced amount net of any local tax. Where that clause is in force, the withholding stops being the supplier's cost and becomes yours, on top of the contract price: a 20% management fee grossed up is a 25% increase in the real cost of the contract. That is a commercial term worth negotiating before signature, and it is invisible to anyone reading only the price.
The rates above are the statutory domestic rates. Where Saudi Arabia has a double taxation treaty with the supplier's country of residence, a lower rate or an exemption may be available on certain income types - but the treaty does not change what you must do at the moment of payment. See section 3. And while this schedule has been stable for many years, the Income Tax Law and its By-Laws are amended, and classification is fact-specific: treat a rate quoted in any article, this one included, as orientation rather than as a position to file on.
The withholding calendar is short, monthly and unforgiving. Tax withheld must be remitted to ZATCA within the first ten days of the month following the month in which the payment was made, accompanied by the monthly withholding declaration filed through ZATCA's portal. Ten days is not much room, and it falls at the start of a month rather than the end, which is why it slips past finance calendars built around month-end close.
The detail that causes the most silent breaches is what starts the clock. The trigger is the payment, not the invoice, not the goods-received note and not the month the cost was accrued. It is also not limited to cash leaving a bank account: crediting the amount to the supplier's account, settling it by offset against amounts they owe you, or booking it through an intercompany current account all constitute payment. Groups that settle head-office recharges by journal entry rather than by transfer are withholding nothing on payments that were made, in the eyes of the law, the moment the entry was posted.
Three further obligations run alongside the monthly cycle:
Withholding records - contracts, invoices, payment evidence, residency certificates, the filings themselves and the working papers behind the classification of each payment - must be retained and retrievable for the statutory period, because a withholding audit is almost entirely a documentary exercise conducted years after the payments it examines.
What follows is the sequence we actually run. It is deliberately weighted towards the front - vendor data and contract terms - because withholding is a control that either exists at the moment of payment or does not exist at all. There is no month-end adjustment that retrospectively creates a deduction from money you have already sent abroad in full.
A withholding audit is a documentary exercise. What is examined is not whether your reasoning was sound in the abstract but whether the file supports it. For each non-resident payment, a defensible file holds:
Retain all of it for the statutory period. The documents that prove a position are almost always the ones nobody thought to keep, because at the time of payment they looked like ordinary correspondence.
Withholding failures are repetitive rather than dramatic. A vendor misclassified once is misclassified on every invoice they send until someone looks, which is why exposure accumulates quietly and then arrives in one assessment covering the whole audit window.
Consequences escalate rather than arriving at once. The law provides for fines on late payment that accrue with the length of the delay, and for penalties covering failure to withhold, failure to file and incorrect declarations, with separate and materially heavier treatment where conduct is treated as evasion rather than error. On audit a defective position is applied backwards across the whole window rather than corrected going forward, which is what turns a small recurring misclassification into a large number. We do not publish a penalty schedule here, and would suggest scepticism about any adviser's page that does: the amounts sit in instruments that are amended, have at times been subject to relief and amnesty initiatives, and depend on whether a failure is treated as negligent or deliberate. Exposure is assessed against your actual facts and the rules in force when you acted.
There is a quieter failure mode worth naming, because ZATCA will never raise it with you: over-withholding, and never reclaiming. Deducting 15% where the contract genuinely supported 5%, withholding from a resident supplier, or withholding at the domestic rate and then never filing the treaty refund claim triggers no audit, no penalty and no letter. It comes out of your supplier relationships and, where a gross-up clause applies, straight out of your margin. In our experience reviewing established withholding processes, unclaimed treaty refunds and over-withholding are close to as common as underpayment - they are simply invisible.
We are independent, we take no commission from software vendors, and we are not your supplier's agent. That matters on withholding more than on most topics, because the two parties to every one of these payments want different answers, and the foreign vendor's own tax adviser is not neutral about the rate you apply to their fee.
A withholding review has two halves. The first is the tax position: a sweep of the supplier master to identify every non-resident counterparty including the intercompany ones; a written classification of each payment stream against the Article 68 schedule with the reasoning recorded; a read of the contracts themselves for characterisation, gross-up clauses and mixed consideration that should have been split; a treaty assessment for each counterparty covering what relief exists and what evidence it requires; and a look back at payments already made, for exposure and for refunds that were available and never claimed.
The second half is what decides whether any of it survives contact with next quarter. Withholding fails when it depends on a person recognising a situation - a controller spotting a foreign vendor name, a treasurer remembering that a journal entry counts as payment. Residency status, payment classification and the applicable rate are master data, and the deduction itself is a control that belongs in the payment run. They should live in the system that already pays your suppliers, with the same ownership and change control as a price list. Where your current platform cannot hold vendor-level tax attributes or apply a deduction at payment, our Accounting systems evaluations assess what can - vendor-neutrally, with no reseller relationship steering the recommendation, and with "configure what you already have" as a live and frequently given answer. The wider ZATCA relationship this sits inside is the scope of our Tax & Zakat advisory practice.
Worth naming the mismatch first: withholding tax is not implemented, it is complied with, and it has applied to every non-resident payment you have already made. What takes time is establishing a defensible position across an existing payment history and then building a control that holds. Three things drive the duration - how many distinct non-resident payment streams need classifying, how much intercompany and head-office activity is involved (which is both the highest-rate and the least-documented category, and typically doubles the analytical work), and whether your accounts payable platform can carry vendor tax attributes without development. A company with a handful of foreign software licences and a modern ERP reaches a sound position quickly; a group with regional shared services, mixed licence-and-service contracts and settlement by intercompany journal does not. That is contract and systems complexity rather than headcount, so mid-size and large organizations often converge on similar timelines. We sequence by exposure - the highest-rate and highest-volume streams first, the long tail after - and scope a realistic timeline against your actual position during evaluation rather than quoting a standard duration that would not hold.
There is no licence price - withholding tax is a statutory obligation, not a product. Read the question the useful way and it becomes: what does withholding actually cost you over three years, and which parts are controllable? Four components. The tax itself, which is normally not your cost at all - it is deducted from the supplier - except where a gross-up clause moves it onto you, and that clause is the single largest controllable line in the whole calculation, negotiable at contract renewal and invisible to anyone reading only the headline price. The operating cost: configuring the control in your accounts payable system, and the monthly finance time spent calculating, filing and reconciling twelve times a year. The advisory cost of establishing the classification and treaty positions and revisiting them as contracts change. And the retrospective exposure - unwithheld tax, late-payment fines and potentially disallowed deductions applied across an entire audit window, which is the line that can dwarf all the others and the only one that is entirely avoidable. Against those sits recoverable value: treaty refunds never claimed, and over-withholding corrected. For some groups that offset materially exceeds the cost of the review. We build that picture for your actual profile at the start of an engagement, not at the end.
Withholding tax is the regulation, so the real question is whether your process complies with it - and that is what we assess: classifications against the Income Tax Law and its By-Laws, treaty positions against the applicable convention and the evidence it requires, and your filing record against the statutory deadlines. Data residency is a genuinely separate question, and it becomes live the moment the control moves into a system, which is where we recommend it should be. A withholding control holds supplier tax identifiers, residency certificates, contract terms and payment data, frequently in a cloud accounts payable or ERP platform hosted outside the Kingdom. Saudi Arabia's Personal Data Protection Law and sector-specific rules can constrain where that data is hosted and processed. We flag the residency requirements your activity actually triggers as part of any Accounting systems selection, rather than leaving it to be discovered after the platform is chosen.
None, in the sense the question implies - withholding applies by law, not by recommendation. What genuinely gets evaluated is narrower and considerably more valuable. On the tax side: how a contract should characterise and split mixed consideration so the rate reflects what is actually supplied; whether a service is better delivered by a resident entity, a registered branch or a non-resident supplier, each of which carries a different withholding and permanent-establishment profile; whether treaty relief is available and worth the evidentiary effort for a given counterparty; and who should bear the tax commercially. On the systems side, where a real comparison happens: whether your existing accounts payable platform can carry vendor residency and rate attributes and apply a deduction at payment through configuration, whether a tax-determination component should sit alongside it, or whether the platform itself is the constraint. That comparison is the substance of our Accounting systems evaluations, and because we take no vendor commission, "what you have is adequate, configure it properly" is an answer we are free to give and regularly do.
Yes, in almost every case - and this is the question that matters most, because a withholding process that lives outside the payment system is a process that will fail. There is no withholding tax application to install. What is needed is that three things become governed fields and enforced behaviours in whatever system already pays your suppliers: the vendor's residency status and country, the withholding classification and rate per payment type, and a deduction applied automatically at the payment run with the liability posted to its own account and a report that produces the monthly filing. Add treaty-claim status as a tracked attribute on the vendor record and the refund workstream acquires an owner for the first time. Most established ERP and accounting platforms support vendor-level tax attributes and withholding tax codes natively, so this is usually configuration rather than replacement. Replacement genuinely enters the conversation in three situations: the platform has no concept of a withholding tax code at all; payments are made from several disconnected systems and bank channels with no single controlled run; or intercompany settlement bypasses accounts payable entirely, so the largest-rate payments never touch the control no matter how well it is configured. Working out which of those you are in is exactly what our Accounting systems evaluations cover.
We do not publish a placeholder statistic here to fill the space a track-record section is expected to occupy. An unverifiable number - tax recovered, refunds claimed, assessments overturned - is exactly the kind of claim a serious finance director should discount in any adviser's pitch, including ours, so we hold our own copy to that standard. The real record is the set of documented engagements on our Success stories page, which we update as new engagements are completed and cleared for publication, rather than a summary figure standing in for it here.
The organizations that bring us withholding work tend to share a situation rather than a sector: enough cross-border payment volume that a misclassification compounds monthly, or enough group structure that head-office and affiliate recharges are material and undocumented. In practice that means subsidiaries of foreign parents paying regional shared-service and management charges, companies running significant foreign software and licensing estates, contractors and engineering firms buying specialist technical services from abroad, and Saudi groups with overseas financing or reinsurance arrangements. Rather than listing names here ahead of their own confirmation to be featured, we maintain the current, permissioned list on our customers page and update it as new relationships are cleared for publication.
Specific withholding engagements - the payment streams reclassified, the intercompany recharges brought into scope, the treaty refunds recovered and the controls built into the payment run - are documented individually rather than summarized here, both because each case has its own shape and because publishing project detail requires the client's clearance first. Tax work of this kind is also commercially sensitive in a way most advisory work is not: a withholding position exposes group structure, supplier relationships and intercompany pricing. Our projects page carries the engagements cleared for public reference, including tax and finance systems work as it becomes available to share.
We do not publish a client quote until the client has reviewed and approved the exact wording attributed to them, so this section will carry real, attributed testimonials from tax and finance systems clients as those approvals come in, rather than a composite or paraphrased quote standing in for one now. If a specific reference matters to your own decision, raise it during the initial evaluation and we will connect you with a comparable past client where confidentiality allows.
Withholding work rests on two things: direct familiarity with how ZATCA applies the source and classification rules in practice - which is not always what a plain reading of the By-Laws suggests - and working relationships with the tax, legal and finance systems specialists that a contested position, a cross-border treaty claim or an accounts payable rebuild eventually requires. Because we take no commission from software vendors or implementation partners, those relationships inform our advice without steering it. We list our accreditations and professional partnerships, alongside our wider technology partner network, on our partners page, and disclose any partnership specifically relevant to a client's evaluation as part of that engagement rather than as a general credential here.
We publish one page per tax rather than one page about tax, because the obligations behave differently and blur into uselessness when merged. If the payment you are withholding on is an imported service, the same payment almost certainly attracts reverse-charge VAT, and the two should be reconciled together: see VAT in Saudi Arabia and tax invoice requirements. If you import goods rather than services, the tax at the border is a different one again - Saudi customs tariff and duties covers classification, valuation and exemptions. If the question underneath your withholding problem is really whether a foreign supplier should be operating through a Saudi entity at all, the sequence starts earlier, with Company formation in Saudi Arabia and the post-incorporation registrations set out in Business setup in Saudi Arabia. And if several of these are live at once, that is the scope of our Tax & Zakat advisory practice as a single engagement.
Here is a fair self-test, and it takes about ten minutes. Pull your last twelve months of payments to non-resident suppliers, including the intercompany ones settled by journal entry. For each, ask three questions: what rate did we apply, what in the contract supports that rate, and did we remit within ten days of the following month. If any line has no confident answer, it has no confident answer for every payment in that stream - and it will keep not having one until somebody looks. Book a decision session and we will look at your actual position: your non-resident payment streams and how they are classified, the contract terms driving the rates and who bears them, whether treaty relief is available and being claimed, and whether the control sits in your payment system or in somebody's memory. If our honest answer is that your position is already sound, we will tell you that instead - it is a shorter conversation and a more useful one.