E-Invoicing Deadlines for Facilities Management Companies (UAE E-Invoicing)

The phase dates come from Ministerial Decision No. 244 of 2025 as amended by MD No. 66 of 2026. Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and exchange e-invoices from 1 January 2027. All other persons conducting business follow from 1 July 2027. A voluntary pilot has run since 1 July 2026 for businesses that want to go early.

Revenue here has a specific meaning: gross income for the most recent accounting period as shown in your financial statements, not a calendar-year figure and not turnover as loosely used. A business sitting near the threshold needs to work this out properly rather than guess, because the phase determines the deadline and the deadline determines the project plan.

There is a second deadline inside the obligation that surprises people: once e-invoicing applies to you, each invoice must be transmitted through the system within 14 days of the business transaction (Article 6(5) of MD No. 243 of 2025). That is an operational deadline, not a project deadline, and it is what makes the error queue a daily discipline rather than a monthly one. Contracted service schedules with KPI-linked billing, consumables pass-through and multi-site contracts. Government and corporate clients validate strictly. KPI adjustments need a defined credit/debit workflow. Multi-site contracts need site references on every line or document.

Work through these in order.

KPI adjustments need a defined credit/debit workflow. Multi-site contracts need site references on every line or document.

The most expensive mistake is starting late and compressing the phases that cannot be compressed: data cleansing, provider selection and testing. A provider chosen in a hurry is a provider chosen on price, and price is the weakest predictor of a smooth go-live. The second mistake is testing with demo data: clean demo invoices validate cleanly and teach nothing, while your real edge cases wait for production to reject them.

The third is organisational: no named owner for the error queue. Rejections need same-day triage by someone with the authority to get data fixed, mappings changed or customers called. An error queue without an owner becomes a late-transmission queue, and the 14-day clock does not pause for organisational ambiguity.

The fourth is treating e-invoicing as an IT project. The connector is the easy part; the tax-code mapping, the numbering discipline and the customer communication are where implementations succeed or fail. Put the tax judgement and the process design ahead of the technology in the plan, and staff them accordingly.

Compliance you cannot demonstrate is compliance you cannot defend. The evidence file has four parts: transmission logs showing every invoice went out, validation responses showing they were accepted, monthly reconciliations tying transmissions to the ledger, and the archive with the transmitted XML retrievable by number, date, counterparty and TIN.

Build the monthly routine once and run it monthly: reconcile, measure 14-day lag distribution, sample field quality, review the rejection trend, log rule changes. Twenty minutes of routine beats twenty hours of reconstruction.

When the FTA asks questions, the answer is the routine's output: logs, reconciliations, correction trails. Businesses with the routine answer in days; businesses without it answer in months, from memory.