Short answer: the defensible default in Saudi Arabia is that VAT falls due on the full certified value of work, including the amount retained, at the earlier of issuing the tax invoice or receiving payment — not when retention is released years later. A deferral position does exist, and some advisors will argue it, but it rests on a reading of the continuous-supply tax point rules rather than on any explicit retention carve-out, and the downside is late-payment penalties on VAT that ZATCA considers was already due. The rest of this article explains what retention is, exactly where it sits on an interim payment certificate, why published guidance conflicts, what each treatment costs you, and how to book and track it. This is general guidance for finance and commercial teams, not tax or legal advice — confirm your position with your own tax advisor or directly with ZATCA before you set an invoicing policy.

What retention is, and why VAT gets confusing

Retention (ضمان أعمال، محتجزات) is a percentage of each certified payment that the employer withholds as security for defects and completion. A very common Saudi arrangement is 10 percent deducted from every interim certificate until accumulated retention reaches 5 percent of the contract sum, with half released at substantial completion (taking-over) and the balance released after the defects liability period and the certificate of making good defects. Public-sector and Etimad-tendered work follows the government procurement rules and its own final-account mechanics, but the economics are the same.

The VAT confusion comes from a mismatch between three different dates: the date the work is performed, the date the contractor is paid, and the date the money is contractually due. Retention deliberately pushes the third date years past the first. VAT law is built around a tax point (date of supply) that normally attaches to performance, invoicing or payment — none of which obviously map onto an amount the employer is holding but has not yet approved for release. That gap is where the conflicting guidance lives.

Where retention sits on an IPC (مستخلص)

An interim payment certificate in KSA is normally built cumulatively, and the order of the deductions matters because it determines the taxable base. A typical structure runs as follows.

Note that the retention line is applied to the value of work, before VAT — never to the VAT-inclusive amount. Withholding retention out of the tax you have collected on behalf of ZATCA is a common and expensive drafting error in subcontracts.

Cumulative value of work executed to date, priced from measured BOQ quantities, plus any approved variations
Plus materials on site (if the contract allows), plus price adjustment or escalation if applicable
Less the cumulative value previously certified — the difference is the gross value of this certificate
Less advance payment recovery, commonly a fixed percentage of each certificate until the mobilisation advance is fully recovered
Less retention at the contract rate, subject to the retention cap
Equals the net amount certified, to which VAT is added to give the cash payable
Memo lines: retention held to date, advance outstanding, and any contra-charges, LDs or backcharges

The two competing treatments, and why sources disagree

Treatment A, VAT at certification. The construction service has been performed and measured, and the certificate and tax invoice cover the full gross value, so output VAT is accounted on the full certified value and retention is simply a deduction from the cash settlement of an already-taxed receivable. On this view retention is a payment-terms issue, not a supply-value issue.

Treatment B, VAT at release. The KSA VAT Implementing Regulations contain special tax point rules for continuous and periodic supplies, broadly linking the tax point to the invoice date or the date payment becomes due under the contract, with a backstop period. The argument is that retention is not contractually due at certification — it becomes due only on the release event — so the tax point for that slice is deferred, and a separate tax invoice is issued then.

Sources conflict because both readings are internally coherent and neither is settled by a widely published, retention-specific ruling. Big-4 KSA commentaries tend to describe the timing risk and recommend documenting a position rather than asserting one; ZATCA guidance addresses continuous supplies and advance payments in general terms rather than naming retention; and many vendor blogs simply paraphrase UAE or Indian practice, which is not authority here. Treat anything you read, including this article, as input to a question you put to your advisor in writing.

Conservative versus deferred: what each one actually risks

Treatment A is conservative. You remit output VAT earlier than you collect it, so on a large project you are funding VAT on money you will not see for two or three years. On SAR 1.3 million of retention held, that is SAR 195,000 of VAT paid ahead of cash — real, but quantifiable and bounded, and recoverable in full when the retention is released.

Treatment B improves cash flow but creates exposure. If ZATCA disagrees, the assessment is not just the VAT (which you would have paid eventually anyway) but late-payment penalties and interest running from the original due date, across every affected certificate on every project, compounding quietly over a multi-year contract. There is a commercial cost too: your employer cannot recover input VAT on the retained slice until you issue that later tax invoice, and sophisticated clients often refuse the arrangement outright.

Whichever you choose, apply it consistently across all contracts, document the reasoning, obtain your advisor's confirmation in writing, and make sure the contract payment clause and your invoicing template say the same thing. Mixed treatment across projects is the single easiest thing for an auditor to find.

Worked example: interim certificate No. 7, in SAR

Contract sum SAR 40,000,000. Mobilisation advance of 10 percent (SAR 4,000,000) received and invoiced with VAT at receipt, recovered at 10 percent of each certificate. Retention 10 percent of each certificate, capped at 5 percent of the contract sum (SAR 2,000,000). VAT at 15 percent.

The whole dispute in this certificate is worth SAR 36,000 of timing. Across the project to date it is SAR 195,000 — the VAT on the SAR 1,300,000 of retention held. That is the number to put in front of your advisor and your CFO, because it frames the question as cash-flow timing against penalty exposure rather than as an abstract technical debate.

Cumulative value of work executed: 13,000,000
Less previously certified: (10,600,000)
Gross value this certificate: 2,400,000
Less advance recovery at 10 percent: (240,000)
Less retention at 10 percent: (240,000)
Net amount certified: 1,920,000
Treatment A taxable base 2,160,000 (gross less advance recovery, because VAT was already accounted on the advance when it was received) — output VAT 324,000, cash due 2,244,000
Treatment B taxable base 1,920,000 — output VAT 288,000 now, plus 36,000 invoiced when this tranche of retention is released
Cumulative retention held after this certificate: 1,300,000, still below the 2,000,000 cap

How to book it: Retention Receivable and Retention Payable

Retention is not a discount and it is not a bad debt — it is revenue you have earned and cash you are owed, so it belongs on the balance sheet and must never be netted quietly against revenue. Under Treatment A the certification entry is: debit Accounts Receivable 2,244,000; debit Advance Payment Received (contract liability) 240,000; debit Retention Receivable 240,000; credit Revenue 2,400,000; credit Output VAT 324,000.

On the payables side, retention you withhold from subcontractors is a Retention Payable and should be aged by release event exactly the way you age your own. Classification under SOCPA-adopted IFRS depends on the release condition: where the balance becomes payable purely with the passage of time it is a receivable, whereas where release is conditional on making good defects or on agreeing the final account, many preparers carry it as a contract asset until that condition is satisfied. Split current from non-current on the expected release date, not the certificate date, and consider whether a long defects liability period introduces a significant financing component.

Release, the final account, and your subcontractors

At taking-over, the first tranche of retention is released. Under Treatment A no VAT event occurs — you debit Bank and credit Retention Receivable, because the VAT was accounted years earlier. Under Treatment B you must issue a tax invoice at that moment for the released amount plus VAT, referencing the original certificates, which means the system has to still know, at release, which certificate each riyal of retention came from and at what rate. That traceability is the real operational cost of the deferral position.

The final account is where retention collides with everything else: agreed variations, LD deductions, backcharges and claim settlements. If the final settlement reduces the value of a supply already invoiced, that is a credit note event with its own ZATCA Phase-2 requirements, not an adjustment you make silently against the retention balance. Remember the mirror image on the subcontract side as well — input VAT is recoverable only against a valid tax invoice, so if your subcontractor defers VAT on retention, your recovery on that slice is deferred too. Retention held from subcontractors is the natural hedge for retention held from you, provided the release dates are genuinely back-to-back.

What your ERP has to track

Most accounting systems in the Kingdom treat retention as a manual deduction typed onto an invoice, which is why so many contractors reconcile retention in spreadsheets and discover unclaimed balances years after handover. A system built for construction should hold retention as a tracked object, not a line of text.

At minimum it needs a retention rate and cap per contract with the cap enforced automatically on each certificate; cumulative retention held by project, by employer and by subcontractor; a release schedule tied to substantial completion and the defects liability period, with alerts; the ability to apply either VAT treatment as a configurable policy, producing the correct taxable base and a ZATCA Phase-2 compliant tax invoice or credit note at each event; and an audit trail linking every released riyal back to the certificate that generated it. Advance recovery, retention and VAT all interact on the same certificate — that combination is what generic ERPs most often get wrong.

In IntellaQ Flow, retention sits alongside job costing by cost code, BOQ and progress billing in the construction module (/industries/construction/), so the IPC, the retention ledger, the subcontractor retention mirror and the e-invoice all come from one set of numbers instead of being reconciled after the fact. That does not decide your VAT position for you. The software should be able to execute whichever treatment your tax advisor confirms — and prove, years later at release or at audit, exactly how each figure was derived.

VAT on Retention in Saudi Construction Contracts