UAE E-Invoicing for Contractors and Real Estate: Progress Billing, Retention and the 2027 Mandate

Most of the e-invoicing guidance published for the UAE assumes a simple transaction: one delivery, one invoice, one payment. Contractors, developers and property managers do not live in that world. A single contract produces advances, monthly interim payment certificates, retention held and released years later, variation orders, back-charges to subcontractors and, on the property side, service charges, rent schedules and utility recharges.

Every one of those is a taxable supply or an adjustment to one, and from 2027 every one of them has to be issued as a structured e-invoice through an Accredited Service Provider and reported to the Federal Tax Authority. This guide walks through the specific cases, because that is where construction and real-estate businesses will either be ready or not.

Who in construction and property is in scope

The UAE e-invoicing framework applies to business-to-business and business-to-government transactions. For a contractor that includes interim payment certificates issued to a developer or main contractor, invoices to and from subcontractors, supplier invoices for materials, and consultancy fees. For a developer or property company it includes contractor invoices received, agency commissions, service charges billed to commercial tenants, and sales of commercial units to businesses.

Residential sales and rentals to individuals are business-to-consumer and sit outside the first phases, but a property company with both commercial and residential activity will be in scope for the commercial side and should design one process rather than two.

Timing follows revenue bands. Businesses with revenue of AED 50 million or more are expected to be live on 1 January 2027, with the next wave from 1 July 2027. Many main contractors and developers fall into the first wave. Their subcontractors, even if smaller, will feel the mandate earlier than their own deadline because the main contractor will expect structured invoices from them.

Progress billing: the interim payment certificate as an e-invoice

The interim payment certificate is the core document. Today it is usually a spreadsheet: work done to date, less previously certified, less retention, less advance recovery, plus VAT, equals amount due. The tax invoice is then produced from the certificate, often by hand.

Under e-invoicing the tax invoice must exist as structured data with defined fields: supplier and customer tax registration numbers, invoice type, taxable amount, VAT rate and amount, and references to related documents. The certificate logic does not change. What changes is that the invoice can no longer be a PDF typed from the certificate. The values have to come from a system that holds the contract, the cumulative certified value and the deductions as data.

Certificate line	How it appears in the e-invoice	What your ERP needs
Gross work certified this period	Taxable supply lines at 5% VAT	Contract or project with cumulative certification by cost code or milestone
Retention deducted	Separate deduction line or payment term; taxable amount unchanged	Retention percentage and running retention ledger per contract
Advance recovery	Deduction referencing the original advance tax invoice	Link between the advance invoice and each recovery
Variation order	Additional supply lines on the same invoice, referenced to the VO	Variation register with its own budget and billing lines
Back-charges or contra	Credit note or separate invoice, never a negative line netted silently	Credit note workflow linked to the original invoice

Retention: deduction, not discount

Retention is the area most often modelled wrongly. Retention does not reduce the value of the supply. The full certified amount is the taxable supply and VAT is due on it. Retention is money the client withholds from payment and releases later, usually at practical completion and at the end of the defects period.

In the e-invoice the taxable amount and VAT are therefore the full certified value. The retention appears as a deduction from the amount payable, or as a payment term, so that the structured data stays correct and the client's own system can record the liability. When retention is released, no new supply has taken place, so the release is a payment, not a new tax invoice. Your ERP should track retention receivable per contract and clear it on receipt rather than invoicing it again.

Where the contract treats retention differently, for example where the parties agree that VAT on retention is accounted for on release, take advice from your tax advisor and configure the system to that position. The point is that the treatment must be a system rule, not a decision the accountant makes on each certificate.

Advances and their recovery

An advance payment creates a tax point when it is received, so a tax invoice must be issued for it at that time. Under e-invoicing that is a structured invoice like any other. Each later progress invoice then recovers a portion of the advance as a deduction, referencing the advance invoice.

The system requirement is linkage. The advance invoice, the recovery schedule and each recovery line need to be connected so that the cumulative recovered amount never exceeds the advance and the references in the structured data are consistent. Spreadsheets manage this with a running column. ERPs manage it with a prepayment or advance object on the contract. Make sure yours has one.

Variation orders and claims

Variations add scope and value to the contract. In the e-invoice they are additional supply lines, ideally referencing the variation order number so the client can match them to their approval. Keep variations as separate billing lines rather than folding them into the base contract value, because the client's auditors and the FTA's reporting both benefit from the trail.

Disputed claims should not be invoiced until agreed. Issuing an e-invoice for a claim the client has not accepted creates a reported supply that may later need a credit note, and credit notes in the e-invoicing world are themselves structured, referenced documents. Invoice what is certified.

The receiving side: subcontractors and suppliers

Contractors are also buyers. Subcontractor certificates, steel, concrete, MEP packages and plant hire will all arrive as e-invoices. That changes procurement in two ways.

First, matching. A structured invoice can be matched to the purchase order and the goods receipt or certified work automatically, which removes a large manual job in most contracting finance teams. Second, disputes. If a subcontractor invoices more than you certified, the correction is a credit note on their side, not a hand-written adjustment on yours. Your procurement process needs a clean way to reject or hold a received e-invoice and request a corrected one.

Property companies: service charges, rent and recharges

For developers and property managers the invoicing pattern is recurring rather than progressive, but the same rule applies: every commercial tenant invoice is a structured e-invoice. Service charges, rent instalments, chilled water and utility recharges and parking all need a tax invoice at the correct tax point, with the right VAT treatment for commercial versus residential and for recharges that are disbursements.

Lease management software or spreadsheets that generate rent schedules will need to hand those schedules to a system that produces and transmits the e-invoice. If the lease system cannot do that natively, the integration into the ERP is the project.

What to do in the next 90 days

Start with a billing inventory. List every type of invoice your business issues and receives, with volume, who prepares it and which system it comes from. For most contractors that is five to eight types; for a property group it can be more.

Then map each type to the structured-data requirements. The hard cases are the ones in the table above. If your ERP already holds contracts, certification, retention and advances as data, the work is configuration and testing. If certificates live in Excel, the work is getting those values into the system of record before the invoice is generated, which usually means a project module or a focused integration.

Finally, choose and connect an Accredited Service Provider early, and run test transmissions for each invoice type. The providers are being accredited through 2026, and the ones that handle construction-style documents well will be busy by the fourth quarter.

How Kaido approaches it

Kaido has delivered e-invoicing integrations and project ERP for contracting and real-estate clients in the UAE, including Odoo project and contract setups with progress billing, retention and advance handling built in. Our e-invoicing engagements begin with the billing inventory above, a gap analysis against the FTA data dictionary, and a fixed-price plan covering ERP configuration, ASP integration and test transmissions for each of your invoice types.

The deadline is fixed. The businesses that treat this as a finance-and-systems project in late 2026 will be issuing compliant certificates in January. The ones that treat it as an IT task in December will not.