UAE e-invoicing will be mandatory in phases from 2026, and registered businesses must transition to structured, machine-readable invoices routed through FTA-accredited service providers. Implementing it properly means aligning your ERP, data, and controls with the MoF/FTA eInvoicing Programme standards (Peppol PINT AE, XML/JSON, real-time reporting, and local archiving).
Regulatory basics
- Scope: Applies to all registered businesses for B2B transactions, subject to exclusion defined in Article 4 of Ministerial Decision No. 243 of 2025 – Issued 12 Sep 2025; paper/PDF invoices alone will not be valid once the mandate is in force.
- Timeline: Phase 1 (large taxpayers) starts July 2026; full rollout follows in later phases for smaller businesses and government entities.
- Legal framework: MoF/FTA eInvoicing Programme sets technical and tax‑data rules, and invoices must comply with UAE VAT Law, executive regulations and Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System.
- Penalties: Cabinet Decision No. 106 of 2025 On the Violations and Administrative Penalties Resulting from Violation of the Legislation Regulating the Electronic Invoicing System
Technical requirements
- Format: Invoices must be generated as structured data (XML or JSON) using standards such as Peppol PINT AE or UBL; simple PDFs or scans do not qualify.
- Mandatory content: Supplier/buyer details including TRN, invoice number and date, description, quantities, VAT rate and amount, and a secure digital signature and timestamp.
- Transmission model: UAE will use a Peppol “5‑corner” model where suppliers and buyers connect through Accredited Service Providers (ASPs), with MoF/FTA as the fifth corner collecting and storing invoices with 50 mandatory fields.
Data Dictionary content
The table below lists the mandatory fields when issuing a tax invoice:
The table below lists the mandatory fields when issuing any other invoice (commercial invoice) related to, exempt, or out-of-scope supplies:
System and process design
- Upgrade ERP/accounting: Configure your ERP or accounting system to natively create e-invoices in XML/JSON mapped to the MoF data dictionary and PINT AE schema, and expose APIs to your chosen ASP.
- ASP integration: Select an FTA-accredited ASP able to send/receive Peppol PINT AE invoices and route the tax data in real time to the FTA e-billing infrastructure.
- Real-time flows: Design workflows so invoices are validated and transmitted immediately on issue (or within allowed tolerance), with failure handling and resubmission logic.
Controls, archiving, and governance
- Storage location: E‑invoices and credit notes must be stored electronically within the UAE in line with the Tax Procedures Law; offshore hosting is generally not acceptable.
- Record retention: Maintain secure, searchable archives with access controls to support tax audits and legal record‑keeping for the required retention period. Data retention is 7 years per current law.
- Compliance controls: Implement master‑data governance (TRNs, tax codes), approval workflows, and monitoring dashboards; technical failures must be reported to FTA within specified timelines (e.g., two business days in some guidance).
Practical implementation steps in the UAE
- Gap assessment: Map current invoicing (formats, channels, timelines) against FTA e-invoicing requirements and classify invoices by type (B2B, B2G, B2C, exempt).
- Vendor selection & contracting: Shortlist FTA-accredited ASPs and/or compliant software vendors, review their Peppol capabilities, UAE data‑hosting, SLAs, and integration options.
- Pilot and training: Use the sandbox/pilot period (2026) to test end-to-end flows, validate data, train finance/IT teams, and refine SOPs before mandatory go-live dates.
- You can refer FAQ’s through the following link: Click here
For support, assistance, advisory and implementation of the invoicing system as per the legal regulatory framework and to meet compliance requirements, please feel free to contact us at tax@alphaequitymc.com
