You Pay the VAT on Retention Long Before Anyone Pays You the Retention

A contractor certifies AED 1,000,000 of work. The client withholds 5% retention and pays AED 950,000. The contractor accounts for VAT on AED 1,000,000.

That is not a mistake, and it is not aggressive. It is what the law says, and it means the contractor has paid AED 2,500 of tax on money he will not see for two or three years — assuming he sees it at all.

Every contractor in this country has done this. Almost none of them have been told why, because the answer is not in any guide about retention. It is in two articles of the VAT law that never mention construction, and a set of dates that most systems do not store.

The law does not know what retention is

Start here, because it explains everything that follows.

Search Federal Decree-Law No. 8 of 2017 for the word "retention" and you will not find it. There is no retention article, no construction chapter, no special rule for the industry that generates more of these questions than any other. The Federal Tax Authority issued five Directives in July 2026 clarifying areas that had been read inconsistently — judicial expert services, VAT group exits, converting digital-currency values, life insurance and reinsurance, and the value of deemed supplies. None of them is about construction.

So the treatment of retention is not something you look up. It is something you derive, from two general rules that were written for every business in the country and happen to land on contractors hardest.

Rule one is the value of the supply. Article 34 says that where the consideration is monetary, the value of the supply is the consideration less the tax. The consideration is what you are contractually owed for the work — the whole certified figure. Retention does not reduce it. Retention defers part of it. Those are different things, and only one of them is a discount.

That is the whole of it. The withheld 5% is not a price reduction, it is a payment-timing arrangement over a price nobody disputes. Your client agrees he owes you the million. He is holding fifty thousand of it as security against defects. VAT is charged on the value of the supply, and the value of the supply is a million.

Rule two is the date. And rule two is where the real damage is.

Article 26 gives you four dates and no advice

Article 25 sets the general rule: tax is calculated on the date of supply, which is the earliest of a list — goods transferred, services completed, payment received, invoice issued.

Article 26 replaces it for contracts like yours. Where a contract "includes periodic payments or consecutive invoices" — which is every construction contract with monthly certificates in it — the date of supply is the earliest of four dates:

1. The date of issuance of any tax invoice.
2. The date payment is due, as specified on the tax invoice.
3. The date of receipt of payment.
4. The date of expiration of one year from the date the goods or services were provided.

Read that list again slowly, because there are three things in it that catch people.

"The date payment is due as specified on the tax invoice" is a trigger. Not the date payment arrives — the date it was due. You write a payment term on the document and the document creates a tax point on that date whether or not anyone pays you. On a FIDIC-shaped cycle where certification starts the clock and the clock is fifty-six days, the tax point has already fired long before the money moves.

"Any tax invoice" means any. If your process issues a document on submission of the application, before the consultant has assessed a thing, you have created a tax point on a value that is about to be revised downwards. The correction then has to be made through Article 62 — a tax credit note, within fourteen days — which is a real transaction, not an edit to the original. Contractors who invoice on application rather than on certification generate credit notes every month and call it normal.

The twelve-month rule is the one nobody plans for. Article 26(1)(d) fires one year after the services were provided, whether or not anything else has happened. No invoice, no certification, no payment, no conversation — the tax point arrives anyway. This is the article that catches the stalled job: work executed, application submitted, consultant silent, client in dispute, nothing certified for fourteen months. The revenue is still uncertain and the VAT is not.

Note what all four have in common. Not one of them is "the date the work was done." The tax point on a construction contract is set by documents and dates, and documents and dates live in a system.

The advance is the same rule pointing the other way

An advance or mobilisation payment is the mirror image, and it is simpler and more often got wrong.

Money arrives before any work is done. Receipt of payment is a trigger under Article 26(1)(c). So the tax point is the day the advance lands, the tax invoice is due within fourteen days under Article 67, and the VAT is payable in that period — on a supply that has not yet begun.

There is no deferral available. You cannot hold the advance against the first certificate and account for the tax then. The date of supply happened when the money hit the account, and the fact that the work is entirely in the future does not move it.

What follows is the part that produces wrong returns. The advance is later recovered by deduction from subsequent certificates, on the schedule the contract sets — often a fixed percentage, often after a threshold, sometimes accelerated late in the job. Each of those deductions reduces the cash on that certificate. None of them is a credit note.

The reason is that nothing has been credited. The advance was consideration for the contract and the VAT on it was correctly accounted for. The recovery deduction is the repayment of a liability you already booked, not the reversal of a supply. A system — or a finance clerk — that treats each recovery line as a negative supply reverses output tax that was properly due, and understates the return by the tax on every recovery instalment for the life of the contract.

The certificate has to carry that distinction on its face: gross valuation, then retention, then advance recovery, then back-charges, as four separate lines with four different behaviours. Collapse them into one "deductions" figure and the VAT is computed off the wrong base, monthly, quietly.

What this costs, in a shape you can check

The numbers below are illustrative. Yours are on your own certificates and will take you an afternoon to assemble.

Take a contractor certifying AED 4,000,000 a month, retention at 5%, and a retention balance that runs for two years past completion before the second release.

	Amount
Certified per month	4,000,000
Retention withheld per month	200,000
VAT accounted for on that retention, per month	10,000
Over twelve months of certificates	120,000

That AED 120,000 is tax paid to the authority on money the contractor has not received and, on the defects timetable in most contracts, will not receive for another two years or more. It is not a loss — the revenue is real and the tax is genuinely due — but it is working capital, financed by the contractor, at the contractor's own borrowing rate, on a balance nobody put in a schedule.

And this is on top of the retention itself, which is already the largest interest-free loan most contractors make without deciding to. The VAT is a second, smaller loan sitting on top of the first, and it is paid earlier.

If you want the underlying retention position with dates rather than an estimate, the retention release calculator takes the rate, the cap, the first-release percentage and the defects period straight off the contract in front of you and returns the two instalments and the date each falls due. The tax on them is 5% of the amount held, payable on the certificates that created it, years before those dates.

No, you cannot claim it back as a bad debt

This is the first question every finance lead asks, and the answer is almost always no.

Article 64 allows a supplier to reduce output tax for a bad debt, but only where all four conditions are met: the goods or services were supplied and the tax was charged and paid; the consideration has been written off in full or part as a bad debt in the accounts of the supplier; more than six months has passed from the date of the supply; and the supplier has notified the recipient of the amount written off.

Retention fails the second condition, and it fails it on principle rather than on paperwork. Retention is not a debt gone bad. It is a debt that is not yet due. Your accounts carry it as a receivable with a maturity, because that is what it is, and writing off a receivable that the contract says will be paid on a date in the future is not a bad-debt provision — it is a misstatement.

The relief is available for the case where it belongs: a certified amount the client has genuinely refused, aged past six months, written off, and notified. That is a real event and worth having a process for. It is not the retention balance.

Note also Article 64(2), which runs the other way and is the one contractors forget when they are the ones holding money back. If your subcontractor writes off what you have not paid him and notifies you, you must reduce your recoverable input tax on it.

Where a system either holds this or does not

Every part of the above is arithmetic. None of it requires judgement once the facts are recorded. Which means it is exactly the class of problem a system should have removed, and exactly the class most systems have not.

Four things have to be true.

The certificate has to be the tax document's parent. The value the VAT is computed on is the gross certified valuation, before retention and before advance recovery. If the invoice is produced by retyping a net figure out of a spreadsheet, the base is whatever was typed, and the only control on it is care.

The tax point has to be a stored date, not an inference. Four triggers, and the system has to know which one fired and when. That means the invoice date, the payment-due date derived from the contract's payment terms, the receipt date, and — this is the one nobody builds — a twelve-month clock running from when the work was provided, that raises something for a human before it expires rather than after.

Advance recovery has to be a repayment, not a credit. A recovery line reduces the cash on the certificate and reduces the advance liability. It does not touch output tax. A system that models it as a negative sales line gets this wrong by construction and will keep getting it wrong until somebody reconciles the advance account, which is usually at the final account.

The retention balance has to be a balance. Held to date, released to date, outstanding, by contract, with dates — as a ledger with two directions rather than a deduction line that vanishes into a total. The tax already paid on the outstanding balance is then derivable, which is the number that tells you what this is actually costing you.

E-invoicing removes the place this used to hide

Until now, a tax point was an opinion until an auditor formed a different one. From 2027 it is a transmitted, timestamped artefact sitting in a network log.

The UAE mandate is already running its appointment phase. Businesses with turnover of AED 50 million or more had to appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027; the tier below appoints by 31 March 2027 and goes live 1 July 2027; government entities follow on 1 October 2027. The penalty for failing to issue an electronic invoice where one is required runs at AED 5,000 per month.

What changes for this article is not the deadline. It is that the date of supply stops being reconstructable after the fact. Every document carries its date into a network that keeps it, which means the gap between the date you claimed and the date your own certificate register implies is now a query somebody can run — including somebody at the authority, which is the general shape of what an FTA audit now asks of your system rather than your team.

Project businesses have the hardest version of this, because the invoice is not generated by a transaction at all. It is assembled by a person from measurements, approvals and deductions. That is the whole argument of the readiness plan that starts with your own data rather than with a provider.

What to make a vendor show you

Six things, on a live screen, in this order. Every one of them is ordinary to describe and awkward to build, which is what makes the list useful.

1. Certify a valuation, deduct retention, and show the VAT computed on the gross figure rather than the net.
2. Show which of Article 26's four triggers set the tax point on that certificate, and the date.
3. Receive an advance, show the tax point on the receipt date and the invoice due within fourteen days.
4. Recover a slice of that advance on the next certificate, and show that output tax did not move.
5. Show a certificate whose work was provided eleven months ago and has never been certified, before the twelve-month rule fires rather than after.
6. Show the total VAT already accounted for on retention still outstanding, across all contracts.

Number five is the one that separates a product from a demo. Everything else on that list is arithmetic a competent implementation can add. A clock that watches for a date nobody has been asked about is a design decision, and it is either in the system or it is in somebody's memory.

The short version

VAT falls on the value of the supply, and retention does not reduce the value of the supply — it defers part of the payment of it. So the tax is due on the gross certified figure, on a date set by Article 26 rather than by when the work happened, and paid years before the retention comes back.

The advance is the same rule running the other way: taxed on receipt, invoiced within fourteen days, and recovered later by deductions that are repayments rather than credit notes.

None of that is a matter of interpretation. All of it depends on dates and documents your system either holds or does not. The tax question was settled in 2017. The systems question is the one still open on most contracts in this country.

What that looks like built — the certificate as the parent document, the tax point as a stored date, the advance as a liability with a schedule — is on the contracting page, and the system on it is Movinti, the contracting suite we built on Odoo. The wider set of things a contractor's system has to do before it is worth buying is in the piece on ERP for contractors.

This article describes how the rules are written. It is not tax advice on your contracts, and the particular conditions on a UAE construction contract are amended as routinely as the payment period is. Read it, then check your own certificates against it with your tax adviser.