If you run an online store or a software team in the UAE, you have probably heard that e-invoicing is coming. The harder questions are whether it covers your sales, which date applies to you, and what your store or accounting system must be able to do. Some answers changed in recent weeks.
This guide sets out what the official pages say, as we read them on 3 November 2026. It then gives you a preparation checklist and question lists for a service provider and a developer. Dates and phases can change, so confirm each date before you act on it.
What e-invoicing means in the UAE
The Federal Tax Authority (FTA) and the Ministry of Finance (MoF) describe an e-invoice as structured invoice data that is issued, exchanged electronically between seller and buyer, and reported to the FTA. A PDF, Word file, image, scan or email does not count. An emailed PDF invoice is not an e-invoice in this sense.
The model has five corners: the seller, the seller's accredited service provider (ASP), the buyer's ASP, the buyer, and the FTA. You do not connect to the FTA yourself. Your ASP checks the invoice data, passes it to the buyer's ASP as XML and reports the tax data to the FTA. According to the MoF page, the seller sends data to its ASP in an agreed format called PINT AE, and the ASP validates it and, if needed, converts it to the UAE standard XML. The guidelines say a business uses one ASP for both sending and receiving. The FTA's notices send businesses to its EmaraTax platform to complete the joining steps, but the FTA page says EmaraTax is not used to exchange the invoices themselves.
Dates as we read them, and why to check
The groups come from Ministerial Decision No. 244 of 2025, as amended, which splits businesses by revenue. It defines revenue as gross income for the most recent accounting period. These are the dates we read in the guidelines (version 2.0, 26 October 2026) and the FTA notice of 25 October 2026. Dates and phases can change, so confirm each one on the Ministry of Finance page before you act:
- Pilot and voluntary start. 1 July 2026. Any person may adopt the system voluntarily from that date.
- Revenue of AED 50 million or more. Appoint an ASP by 30 October 2026. Implement by 1 January 2027.
- Revenue below AED 50 million. Appoint an ASP by 31 March 2027. Implement by 1 July 2027.
- Government entities. Appoint an ASP by 31 March 2027. Implement by 1 October 2027.
The original decision gave 31 July 2026 for that group. Ministerial Resolution No. 66 of 2026 changed it to 30 October 2026, and the FTA notice and the guidelines show the same date. Dates have moved before, so an older article or a sales email may be out of date. Today is 3 November 2026, so the 30 October date has passed. If your revenue is AED 50 million or more and you have not appointed a provider, ask your tax adviser what that means for you now.
One more change matters. On 30 October 2026 the MoF announced a new Cabinet Decision on penalties that replaces the 2025 one. It sets AED 5,000 for a first violation, then AED 5,000 for each month or part of a month while it continues, capped at AED 50,000 in any 12 consecutive months. The page does not say when the new decision takes effect. An FTA notice of 25 October 2026 also warned of AED 5,000 for each month or part of a month of delay, including a missed provider deadline. Ask your adviser which rules apply to you and from when.
Does it apply to an online store?
The scope covers business-to-business (B2B) and business-to-government (B2G) transactions, whether or not the business is registered for VAT. Sales to consumers (B2C) are excluded. Decision 244 also excludes people who make only B2C supplies, until a later ministerial decision sets another date. The guidelines say there is no duty to issue an e-invoice for supplies to individuals outside a business. A shop that sells only to consumers may therefore have no outgoing e-invoices to issue today, and that can change.
Three situations can still bring a store in:
- Sales to companies. Wholesale accounts, corporate gift orders and any customer who gives you a tax number are B2B. Orders from government bodies are B2G.
- Exports. The FTA page says invoices going abroad must go through an ASP. The guidelines treat exports of goods and services as in scope, and they set a predefined placeholder address for a foreign buyer without a Peppol ID.
- Purchases. The FTA page says a business that makes only B2C supplies must still appoint an ASP if it receives goods or services from other businesses in B2B transactions. The decision excludes people who only make B2C supplies, so ask how the rules apply to what you buy: "We sell only to consumers but buy from companies. Do we need a provider, and from when?"
What your store or system must be able to do
The MoF publishes the mandatory fields as a separate document (version 1.1, dated 28 October 2026). For a tax invoice it lists 41 fields in six groups: invoice details, seller, buyer, document totals, tax breakdown and invoice lines. Buyer details include an electronic address and an identifier, and a UAE buyer registered for tax gives its tax registration number. One flag in the invoice type code marks a supply made through e-commerce.
The guidelines (version 2.0, dated 26 October 2026) and the FTA page add rules that touch store and finance software:
- Corrections. An e-invoice is not cancelled. You issue a credit note. Every refund, return or price correction in your store must be able to create one.
- Foreign currency. When the invoice is not in AED, tax amounts must also appear in AED. Ask how your multi-currency store will do this.
- Deposits. A tax invoice is issued when an advance payment arrives. The final invoice covers the balance and refers back to the advance invoice.
- No QR code. UAE e-invoices carry no QR code or barcode. A QR code is a Saudi feature, covered in our Saudi e-invoicing guide, so do not copy a Saudi template.
- Language. Arabic and English are supported. The FTA page adds that some emirates' rules may require Arabic.
- No custom fields. You cannot add your own optional fields to the PINT AE format. Industry needs go through your ASP.
- Records. For taxable persons the guidelines set five years after the tax period, with four more years in cases of dispute or audit. The MoF's 19 October 2026 notice says businesses must give the data to the FTA on request, and that the earlier rule to store e-invoice data inside the UAE was removed.
Choosing a service provider
The Ministry of Finance publishes a list of accredited service providers. It had 84 entries when we read it on 3 November 2026, and the page says it is updated periodically. We name no provider. The MoF's accreditation page sets conditions, including that the provider is active and Peppol-certified, has passed the OpenPeppol conformance tests, has at least two years of experience running an e-invoicing system, and meets insurance requirements. Its list of required documents includes ISO/IEC 27001 and ISO 22301 certificates. Ask any provider for proof, and check the MoF list yourself.
At an awareness meeting in Dubai on 29 September 2026 the FTA described the joining steps: choose a provider, sign with it and integrate with its system, then complete the remaining steps on EmaraTax. The FTA page also mentions a testing phase before go-live.
Questions for the provider
- Can you show your accreditation, and where does your name appear on the MoF list?
- How does our store or accounting system send you data: an API, a file upload or a ready connector? Who builds and maintains that link?
- Which formats do you accept, and what do you convert for us?
- When an invoice fails validation, how do we see the error, and who fixes it?
- Can you also receive our suppliers' invoices, since one ASP covers both directions?
- What test setup do you offer before go-live, and for how long?
- What do setup, each invoice and support cost? Where is our data held, and how do we export it if we leave?
Questions for your developer
- Which of our systems create invoices today: the store, accounting, point of sale or spreadsheets? Which one holds the master record?
- Can each system produce all the mandatory fields for a tax invoice? Where do we capture a company buyer's tax number at checkout?
- How do refunds, returns and price corrections create credit notes?
- How do deposits and final invoices link?
- What happens when the provider rejects an invoice, and who sees it?
- Where do we store the identifiers and status that come back from the provider?
- How long do records live, where, and can we retrieve them for the FTA?
Build, connect or buy
There are three routes. Use a connector from your accounting or store vendor, but only if the vendor confirms it works with your chosen provider. Add an integration layer between your systems and the provider. Or build invoicing into custom software. The right one depends on how many systems create invoices. Our guide to custom software or off-the-shelf covers the trade-offs. ESTASOFT has an office in Dubai, but these questions apply wherever you hire. For VAT and customs, see selling to the UAE and Saudi Arabia.
A preparation checklist
- List your sales as B2C, B2B, B2G and export, and note which systems create each invoice.
- Ask your tax adviser which revenue group you are in, which accounting period counts, which dates apply, and the purchases question above.
- Shortlist providers from the MoF list and send each the same question list.
- Check each invoice-creating system against the mandatory fields document.
- Decide how credit notes, deposits and foreign-currency orders will flow.
- Plan a test run with the provider before the date that applies to you, and name one owner inside your company.
What we could not confirm
- The text of the new penalties decision. The MoF notice gives no effective date.
- The issue date of Ministerial Resolution No. 66 of 2026, which is blank in the text we opened.
This is general information, not legal or tax advice. Check the current rules or ask a qualified adviser before you decide.
Need a hand?
If your store, accounting system or internal software must connect to the provider you choose, ESTASOFT offers integrations and APIs and custom software. Send a short brief on the contact page. We do not give legal or tax advice. For the market view, read eCommerce in Dubai and the UAE in 2026.
Sources
- Federal Tax Authority: UAE e-invoicing: scope (B2B and B2G, B2C-only person still needs an ASP if it buys from businesses), five-corner model, exports through an ASP, no QR code, credit notes instead of cancellation, Arabic and local rules, testing before go-live, EmaraTax not used to exchange invoices; page last updated 2 November 2026 (checked 3 November 2026)
- Federal Tax Authority: reminder on e-invoicing deadlines (25 October 2026): 30 October 2026 ASP appointment date for revenue of AED 50 million or more and the date for the below AED 50 million group; EmaraTax steps; AED 5,000 per month or part month of delay (checked 3 November 2026)
- Federal Tax Authority: joint awareness meeting for accredited service providers (29 September 2026): joining steps: choose a provider, contract and integrate, complete steps on EmaraTax; meeting held in Dubai on 29 September 2026 (checked 3 November 2026)
- Ministry of Finance: UAE eInvoicing: definition of an e-invoice, five-corner flow, PINT AE and UAE XML formats, list of legislation and guidance documents; page modified 30 October 2026 (checked 3 November 2026)
- Ministry of Finance: two ministerial decisions on scope and timelines (29 September 2025): original group dates, including 31 July 2026 for the larger group (checked 3 November 2026)
- Ministerial Decision No. 244 of 2025 on the implementation of the electronic invoicing system: revenue definition, pilot and voluntary start on 1 July 2026, group dates as first issued (31 July 2026 for the larger group), B2C exclusion in Article 5 (issue date blank in the text) (checked 3 November 2026)
- Ministerial Resolution No. 66 of 2026 amending Resolution No. 244 of 2025 (English text, May 2026 file): changes the appointment date for revenue of AED 50 million or more to 30 October 2026 and the implementation date to 1 January 2027; issue date blank in the text (checked 3 November 2026)
- UAE Electronic Invoicing Guidelines, version 2.0 (26 October 2026): timeline table, scope, one ASP for sending and receiving, PINT AE, no QR code, exports and placeholder address, advance payments, AED tax amounts, record keeping, no custom fields (checked 3 November 2026)
- UAE Electronic Invoice Mandatory Fields, version 1.1 (28 October 2026): 41 mandatory fields for a tax invoice in six groups, buyer identifier rules, e-commerce flag (checked 3 November 2026)
- Ministry of Finance: amendments to the electronic invoicing regulations (19 October 2026): Decision No. 197 of 2026: UAE data storage rule removed, data to be provided to the FTA on request (the page also covers a 24 month Tax Group exclusion, not used in the article) (checked 3 November 2026)
- Ministry of Finance: updated administrative penalties (30 October 2026): AED 5,000 first violation, AED 5,000 per month or part month, cap of AED 50,000 in 12 months; no effective date on the page (checked 3 November 2026)
- Ministry of Finance: accreditation of eInvoicing service providers: conditions a provider must meet: Peppol certification, conformance tests, two years of experience, insurance; required documents include ISO certificates; page modified 16 June 2026 (checked 3 November 2026)
- Ministry of Finance: eInvoicing accredited service providers: list of accredited providers (84 entries when read), updated periodically; page modified 2 November 2026; no provider named in the article (checked 3 November 2026)
