UAE e-invoicing: what it is, who it covers, and what to do now

Electronic invoicing means invoices are created, exchanged and received as structured data — data a system can read and check field by field — not as PDFs or paper documents passed from hand to hand. The legal basis is Federal Decree-Laws No. 16 and 17 of 2024. Ministerial Decision No. 243 of 2025 sets the scope and obligations, Ministerial Decision No. 244 of 2025 sets the phases and dates, and the Ministry of Finance published official Electronic Invoicing Guidelines v1.0 in February 2026.

Every e-invoice uses one format: PINT AE, the UAE's localisation of the Peppol International Invoice format. The exchange runs on the Peppol network through accredited service providers — the five-corner model explained below — and a business may not send invoices to the Federal Tax Authority (FTA) directly.

The system covers business-to-business (B2B) and business-to-government (B2G) transactions by businesses operating in the UAE. That includes free-zone companies and branches of foreign companies. Sales to individual consumers (B2C) sit outside the first phase.

One warning matters for small firms: scope is framed around doing business, not around VAT registration. A business that is not VAT-registered should not assume it is out of scope — check your position against Ministerial Decision No. 243 of 2025 before you decide you can ignore the dates.

• In scope: B2B invoices between businesses operating in the UAE
• In scope: B2G invoices to government entities
• In scope: free-zone companies and UAE branches of foreign companies
• Outside the first phase: B2C sales to individual consumers

A voluntary pilot opened on 1 July 2026. Businesses with annual revenue of AED 50 million or more had to appoint an accredited service provider by 30 October 2026 — a date extended from 31 July 2026 — and their mandate starts on 1 January 2027. Businesses below AED 50 million appoint a provider by 31 March 2027 and start on 1 July 2027. Government entities appoint by 31 March 2027 and start on 1 October 2027.

The full phase table, with the decisions behind each date, is on the mandate and deadlines page.

You are corner 1, the supplier. Your accredited service provider (corner 2) validates your invoice, converts it to the UAE format and sends it over the Peppol network to your customer's provider (corner 3), which delivers it to your customer, the buyer (corner 4). The FTA (corner 5) receives the tax data from the exchange — it is not a mailbox you send invoices to. The journey is set out corner by corner on the five-corner model page, and providers and Peppol IDs are explained on the Peppol and access points page.

Where does InstaJack fit? Honestly: InstaJack is not an accredited service provider, and InstaJack does not exchange e-invoices today. What InstaJack already puts on every invoice is the data the system runs on — a sequential invoice number, your firm's TRN, the 5% VAT split and line-by-line detail — so when your phase arrives, the work is connecting that invoicing to an accredited provider, not rebuilding it. Our step-by-step guide for small firms is at UAE e-invoicing for small firms.

Under the five-corner model your software does not "send an email to the FTA". It connects — directly or through an access point — using machine-to-machine interfaces (APIs): your invoice data goes out in the standard format, validations and acknowledgements come back, and statuses like reported or delivered attach to the invoice in your records. For a small firm the practical questions are boring and decisive: does the software connect for you, what happens when the connection is down at the moment of invoicing, and can you see each invoice's status without asking anyone?

InstaJack's position stays the one stated across this cluster: the invoice fields and flows are being built to the published model, the provider connection goes through the F1–F12 adapter work recorded in our build notes, and no customer files through the app until that work ships and is proven. Software that demos a smiling "submitted" animation is not the same as software whose submissions an ASP has accepted — ask any vendor, including us, which of the two you are looking at.