The UAE’s e-invoicing mandate has moved from “coming soon” to “in progress.” The voluntary and pilot phase opened on 1 July 2026, a Taxpayer Working Group is already testing the system with the Ministry of Finance (MoF) and Federal Tax Authority (FTA), and the first mandatory go-live date — 1 January 2027, for businesses with annual revenue of AED 50 million or more — is now less than five months away.

For businesses running Microsoft Dynamics 365 Business Central, this isn’t a policy update to skim and file away. It’s an ERP-level project with a hard deadline, and Business Central does not yet have a built-in way to meet it.

What’s changed since this mandate was first announced

A few developments have firmed up the picture considerably:

• Ministerial Decisions No. 243 and No. 244 of 2025 and Cabinet Decision No. 106 of 2025 formally set out the phased rollout and the administrative penalty framework.

• The FTA published its complete technical semantic model in February 2026 — 51 mandatory data fields for electronic tax invoices, aligned to the UAE’s national Peppol PINT AE specification.

• The Electronic Invoicing Guidelines (Version 1.1) were released by the MoF in June 2026.

• The ASP appointment deadline for large businesses was extended from 31 July 2026 to 30 October 2026 — though the go-live date of 1 January 2027 has not moved.

• Microsoft’s 2026 Wave 1 release introduced a unified Peppol/UBL e-invoicing integration framework (general availability 8 August 2026) and brought Peppol e-invoice purchase draft preview capability to Business Central — a step forward, but still short of native outbound compliance.

What e-invoicing means in practice

UAE e-invoicing is not a digitised PDF or a nicer-looking email attachment. It’s a structured, machine-readable invoice that is validated and exchanged automatically between systems.

The framework runs on a Decentralised Continuous Transaction Control and Exchange (DCTCE) model — commonly called the Peppol 5-corner model:

1. The seller’s ERP (e.g., Business Central) generates the invoice data.

2. An Accredited Service Provider (ASP) converts it into the required PINT AE XML format and validates it.

3. The invoice is transmitted over the Peppol network to the buyer’s ASP.

4. Tax data is reported to the FTA’s e-Billing system in near real time.

5. Both parties receive confirmation of successful exchange.

PDFs, scanned copies, and manually emailed invoices will not satisfy the mandate. Every electronic tax invoice must carry the buyer and seller’s Tax Registration Number (TRN), and every field in the invoice must map correctly to the FTA’s 51-field data standard.

The phased implementation timeline

B2C invoices remain outside the current scope; the initial mandate focuses on B2B and B2G transactions. Notably, businesses that aren’t VAT-registered but conduct B2B or B2G transactions are still in scope and must obtain a Tax Identification Number to use the Peppol network.

Administrative penalties: still the same structure, now backed by law

Cabinet Decision No. 106 of 2025 confirms the penalty framework businesses have been preparing for:

• Delay in implementing e-invoicing or appointing an ASP: AED 5,000 per month (or part thereof) for the period of delay.

• Failure to issue or transmit an electronic invoice: AED 100 per invoice, capped at AED 5,000 per month.

• Failure to issue or transmit an electronic credit note: AED 100 per credit note, capped at AED 5,000 per month.

• Failure to notify the FTA of system outages or technical issues: AED 1,000 per day until notification is made (typically expected within two business days of the outage).

• Failure to notify or update registered business information: AED 1,000 per day until the update is made.

These are administrative penalties aimed at recurring or unresolved non-compliance, not one-off errors — but they compound quickly for a business issuing invoices daily without a working ASP connection.

What this means specifically for Business Central users

This is the part most generic compliance articles skip, and it’s where businesses on Business Central need to pay closest attention: Business Central has no native UAE e-invoicing module.

Unlike Dynamics 365 Finance & Operations, which is receiving built-in e-invoicing functionality under 2026 Wave 1, Business Central compliance currently requires:

• A custom AL-language extension that reads posted sales invoices and credit memos and maps every relevant field to the FTA’s 51-field PINT AE data dictionary.

• Correctly configured master data — customer TRNs, tax registration details, item and tax category setup — since a field that looks fine on screen in Business Central can still fail FTA validation if it’s incomplete or inconsistently structured.

• A live connection to an MoF-accredited ASP, since Business Central generates and formats the invoice but cannot itself validate, transmit, or report it to the FTA. The ERP and the ASP are both required — neither replaces the other.

• A workflow for handling inbound Peppol e-invoices from suppliers, now partly supported by the Wave 1 purchase draft preview feature, alongside outbound invoice generation.

Where Samadhan comes in

Samadhan India has already worked through this exact configuration inside live Business Central environments for packaging industry customers — mapping sales invoice and credit memo data to the required field structure, cleaning up the master data gaps that typically cause validation failures, and setting up the ASP connectivity needed for compliant transmission. For manufacturers and packaging businesses running Corrugated Samadhan, Paper Samadhan, Folding Carton Samadhan, or Flexible Packaging Samadhan alongside Business Central, that means the e-invoicing layer can be built on top of an ERP setup we already know end-to-end, rather than treated as a bolt-on project for a new vendor to figure out from scratch.

Operational implications for businesses

Because validation now happens far earlier in the transaction lifecycle — at the point of transmission, not at quarter-end reconciliation — the practical priorities are:

• Accurate data capture at invoice creation. Errors surface immediately, not months later.

• Alignment between billing, ERP, and tax reporting systems, so the same invoice data holds up across Business Central, your ASP, and the FTA.

• Clear procedures for exceptions and downtime, given the AED 1,000-per-day penalty for unreported outages.

• A confirmed revenue threshold check. A business sitting close to AED 50 million in annual revenue should confirm now which phase applies to it — crossing the threshold mid-year can pull a company into Phase 1 unexpectedly.