UAE E-Invoicing for Real Estate

UAE lease agreements commonly use post-dated cheques for the full annual rent, but under PINT-AE each collection period is its own invoice. A one-year commercial lease at AED 240,000/year issued as four AED 60,000 quarterly invoices needs four PINT-AE documents, not one. The cheque schedule is a payment reference, not a document combining periods.

ERP mapping: your property-management ERP (Yardi, MRI, RealPage, or a locally-built system) must emit one invoice record per rent period. TrustBill's recurring-invoice scheduler reads the lease's start date, term and billing frequency from your master data, then generates PINT-AE per period at the right VAT category derived from the unit type. Residential-rent invoices are generated with VAT category E and land on the PINT-AE network as exempt supplies (still required to submit — exempt is not out-of-scope).

Edge cases: (1) mid-term unit type change (e.g. residential converted to short-term rental holiday-let) — the switch triggers a mid-lease VAT recategorisation, and the very first standard-rated period must reference the prior exempt period in cac:AdditionalDocumentReference; (2) tenant deposit applied to final rent — treat as payment (cbc:PrepaidAmount) not as a discount.

The rule of thumb: rebilled at cost = potential disbursement (VAT category O, out of scope for VAT); marked up = your supply (VAT category S, standard-rated 5%). Once you mark up any line, the whole line becomes standard-rated — you cannot split the margin from the base and rate them differently under UAE VAT law.

PINT-AE mapping: at-cost rebilling appears as cac:AllowanceCharge with a disbursement reason code, referencing the underlying invoice (DEWA bill, community master invoice) via cac:AdditionalDocumentReference. Marked-up rebilling appears as a normal invoice line with VAT category S.

Common failure: mixing at-cost and marked-up items in the same service-charge invoice without separating them into distinct line groups. Under PINT-AE the line-level tax category is what the FTA uses to reconcile against the tenant's input-VAT claim — inconsistent categories inside one document is a validation-clean but reconciliation-broken output.

A landlord holding 20+ commercial units across three towers wants a monthly consolidated statement per tenant — one document listing every unit's rent and service charge. PINT-AE does not have a native "multi-property statement" document type; the compliant pattern is one PINT-AE invoice per unit per period, with a matching statement PDF for the tenant's convenience.

TrustBill generates both automatically: n PINT-AE invoices submitted to the FTA network (one per unit-period), plus a single consolidated statement PDF for the tenant with references (via cac:AdditionalDocumentReference on each invoice) to a shared statement UUID. That way the tenant reconciles one PDF while the FTA sees the granular structured data.

Edge case: tenant occupies multiple units under one lease (a multi-unit master lease). Here one PINT-AE per period is fine and the invoice carries multiple InvoiceLines — one per unit. Do not artificially split into per-unit invoices; that breaks the tenant's downstream matching.

Dubai's Ejari and Abu Dhabi's Tawtheeq generate a tenancy contract number that most commercial tenants require on every rent invoice. Under PINT-AE, this number belongs in cac:AdditionalDocumentReference with a specific documentTypeCode identifying it as a tenancy-registration reference — not in cbc:BuyerReference (which is reserved for the buyer's order/PO number).

Some real-estate ERPs shove the Ejari number into a generic 'notes' field; that renders on PDF but disappears from the structured XML, which then fails downstream matching for large tenants running e-invoicing reconciliation. TrustBill's real-estate workflow reads Ejari/Tawtheeq from the lease master data and injects it into cac:AdditionalDocumentReference automatically on every recurring rent invoice.