E-Invoicing Deadlines: Post-Go-Live Support in the UAE

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. In the post-go-live support phase specifically, the priority is: A daily check on transmission success rates and the error queue, with alerts for anomalies. Silence is not the same as success.

Work through these in order.

The post-go-live support phase is where this theme is cheapest to address: Quarterly: SLA performance, cost per document as volumes change, and whether the accreditation register still shows your ASP in good standing.

First, the classification error: assuming every sale is B2B or every sale is B2C without mapping the streams. Mixed businesses that improvise classification per invoice create exactly the discrepancies the structured data makes visible. Second, forgetting intercompany flows: groups implement for external customers and discover at hypercare that the largest document stream was internal all along.

Third, the PDF habit: teams that keep emailing PDFs 'as usual' during the cutover while assuming the network has taken over. From go-live, the structured transmission is the invoice; the PDF is a courtesy. Brief every customer-facing employee and retire the old templates on a defined date.

Fourth, archiving as an afterthought. The transmitted XML, validation responses and renderings must be stored tamper-evident and retrievable by number, date, counterparty and TIN. A folder of PDFs is not an archive, and discovering that during an FTA request is the wrong time.

The FTA holds your transmitted data independently: the question is never whether the data exists, but whether your records reconcile to it. Monthly, tie every sales invoice in the ledger to an accepted transmission, investigate gaps rather than assuming them, and keep the reconciliation as a signed record.

Track the two operational metrics that predict trouble: transmission lag against the 14-day rule, and rejection rate over time. A growing lag tail or a plateaued rejection rate is a process failure with a date on it: fix the process while it is still an internal finding.

Report a short snapshot to management monthly: volumes, rejection rate, average lag, rule changes on the horizon. Compliance that is not reported is compliance nobody owns.