The first UAE e-invoicing deadline has passed. Businesses with revenue of AED 50 million or more had until 30 October 2026 to appoint an Accredited Service Provider (ASP) and go live on 1 January 2027 (Ministerial Resolution No. 66 of 2026). Everyone else is next: a business under AED 50 million must appoint an ASP by 31 March 2027 and implement by 1 July 2027, according to the Ministry of Finance's E-Invoicing Guidelines, version 2.0 of 26 October 2026.
Five months is enough to sign an ASP contract, and tight for the part that decides whether your invoices pass validation: getting 51 specific data fields out of your accounting or ERP system, clean, on every invoice. This article maps those fields to where they usually live in an SME's systems. It is a practical reading of the official documents, not legal or tax advice.
ASP prices are covered in what ASPs charge and how Zoho, Xero and QuickBooks connect, and the integration plan in our ASP deadline and integration checklist.
What changed in the last two weeks of October
Penalties were rewritten. On 30 October 2026 the Ministry announced Cabinet Decision No. 173 of 2026, which repeals Cabinet Decision No. 106 of 2025. Under the new table:
- Not implementing the system, including not appointing an ASP, costs AED 5,000 for the first instance and AED 5,000 for each month or part of a month it continues, capped at AED 50,000 in any 12 consecutive months (Decision 173, annex item 1). Decision 106 had no cap.
- Not issuing and transmitting an e-invoice or e-credit note stays at AED 100 per document, up to AED 5,000 per calendar month (items 2 and 3).
- Not telling your ASP about changes to the data you registered with the FTA drops from AED 1,000 a day under Decision 106 to AED 250 a day, capped at AED 5,000 a month (item 4).
- System-failure fines are gone, and one violation gets one penalty even if you are both issuer and recipient (Ministry of Finance).
Article 2 matters for planning: the decision does not apply to voluntary issuers (Article 2(2)), and the guidelines say penalties apply only from your mandatory date (section 8.2). A small business that goes live early can iron out problems without fine exposure. To us that is the best argument for starting in the first quarter of 2027 rather than in June.
The mandatory fields list was reissued. The UAE Electronic Invoice Mandatory Fields, version 1.1, dated 28 October 2026, lists 51 fields for an electronic tax invoice and 49 for a commercial e-invoice.
The scope rules were already eased. Ministerial Decision No. 197 of 2026, in force from 1 October 2026, excludes transactions inside a VAT tax group for 24 months from 1 January 2027 and repeals the system-failure article of Decision 243 (Ministry announcement).
The dates that apply to you
| Who | Appoint an ASP by | Implement by |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
Source: E-Invoicing Guidelines v2.0, section 8.3, reflecting Ministerial Decision No. 244 of 2025 as amended. A pilot programme for invited businesses and voluntary adoption for everyone both opened on 1 July 2026 (sections 8.1 and 8.2), and the Ministry says the five-corner exchange is now live (programme update, October 2026). "Revenue" means gross income in your most recent accounting period, based on your financial statements (Guidelines, section 3). Scope is wider than VAT: e-invoicing applies to any person doing business in the UAE regardless of VAT registration status, unless excluded under Article 4 of Decision 243 (Mandatory Fields v1.1, highlights).
Field mapping: where the 51 fields live in your systems
The invoice that leaves your ASP is an XML document in PINT AE, the UAE profile of the Peppol international invoice. OpenPeppol publishes it as PINT AE Billing version 1.0.4, alongside the Tax Data Document that both sides use to report to the FTA. Your ASP builds it from the data you send. If the data isn't there, the ASP can't invent it.
We grouped the Ministry's 51 tax-invoice fields by the place they normally come from in an SME's accounting or ERP setup. Field numbers follow the Ministry's list.
| Source in your system | Fields (MoF numbering) | Where we expect gaps |
|---|---|---|
| Invoice header | 1 to 9: number, date, type code, currency, transaction type flags, payment due date, business process type, specification identifier, payment means code | Transaction type flags and payment means are rarely stored per invoice today |
| Your own company record | 10 to 20: legal name, electronic address and identifier, legal registration ID and its type, TRN, tax scheme, address, city, emirate, country | Registration ID type (TL, EID, PAS or CD) and the emirate as a separate field |
| Customer master | 21 to 29: name, electronic address and identifier, TRN, tax scheme, address, city, emirate, country | The buyer's TIN and Peppol endpoint. This is where most of the clean-up sits |
| VAT configuration | 35 to 38 and 46 to 47: tax category code, rate, taxable and tax amounts per category and per line | Tax codes set up for the VAT return, not mapped to the PINT AE code list |
| Item master | 39 to 45 and 50 to 51: line ID, quantity, unit of measure code, net and gross price, price base quantity, item name and description | Free-text units such as "pcs" or "box" instead of a code |
| Calculated totals | 30 to 34 and 48 to 49: line totals, totals with and without tax, amount due, line VAT and line amount in AED | Line-level AED amounts on invoices raised in USD or EUR |
The fields that trip people up
The electronic address. Your Peppol participant identifier is 0235 followed by your 10-digit TIN, and the TIN is the first 10 digits of your Corporate Tax TRN (Guidelines, section 3). If you are in a tax group, use your own TIN, not the group representative's (Mandatory Fields v1.1). Every B2B customer record needs the same. Many hold a 15-digit TRN in a notes field, if at all.
Customers who are not on the system yet. If a buyer has not implemented e-invoicing and has no participant identifier, you put the predefined endpoint 0235:9900000098 on the e-invoice and still send a regular tax invoice, a PDF for example (Guidelines, section 10.2). For an export buyer without a Peppol ID, the endpoint is 0235:9900000099 (section 10.4). Your system needs a rule for both.
The transaction type code. This is a string of eight 1/0 flags: free zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, e-commerce supply and exports (field 5). Your accountant knows these facts about a sale; the ERP usually doesn't. Decide where each flag gets set: customer, item, or the person raising the invoice.
No extra fields, no QR code. You cannot add optional fields of your own to PINT AE; industry-specific data has to be agreed with your ASP (Guidelines, section 12.2, notes 24 and 25). E-invoices are XML only and carry no QR code or barcode (section 5.3). If customers rely on a custom "project code" on your invoices, ask the ASP now how it will travel.
Commercial invoices. A business that is not VAT-registered issues a commercial e-invoice with 49 fields. It drops the buyer's tax identifier and the AED line amounts, adds the buyer's legal registration ID and type, and uses the seller's TIN where there is no TRN (Mandatory Fields v1.1, section 4.2).
A readiness plan from now to 31 March
The Ministry's own checklist starts with one question: have you identified the data points and made sure your accounting or ERP system can extract them (Guidelines, Appendix 2)? This is how we would work through it.
- Export last quarter's B2B invoices and fill the 51 columns from the table above. Count the blanks per column. A column that is mostly empty tells you more than any vendor demo.
- Fix the customer master first. TIN, emirate, legal registration ID and type. Ask customers for their TIN on your next statement run.
- Map tax codes and units of measure to the code lists in the PINT AE specification. It is a one-off mapping table.
- Pick the ASP. See the register of accredited providers; its October programme deck counted 65 accredited and 5 pre-approved (MoF, October 2026). Onboarding is started by you, not the ASP, through EmaraTax (Guidelines, Appendix 1, step 2).
- Test all six steps the guidelines list: sending data to the ASP, the ASP issuing to the buyer, the delivery confirmation, receiving supplier invoices, tax data reporting to the FTA, and the reporting confirmation (Appendix 1, step 3). Receiving matters as much as sending: suppliers in the large-business group start sending you e-invoices in January.
- Agree who fixes rejections. The checklist asks for an error governance model with the ASP. Write down who sees a rejected invoice and how fast.
Operating in the UAE and Saudi Arabia
If you also invoice from a Saudi entity, the two mandates overlap in early 2027. ZATCA's Wave 25 covers every taxpayer whose VAT-subject revenue exceeded SAR 187,500 in 2022, 2023, 2024 or 2025, and requires integration with the Fatoora platform by 1 February 2027 (ZATCA, 24 July 2026).
The models differ. Saudi Phase 1 required QR codes on e-invoices from December 2021, and Phase 2 connects your own solution directly to ZATCA (ZATCA, roll-out phases). The UAE uses no QR code and routes everything through an ASP over Peppol (Guidelines, sections 5.1 and 5.3). Our advice for a two-country group: keep one clean customer and item master, and build two output adapters. One invoice template for both countries is where these projects stall.
Frequently asked questions
We are under AED 50 million. What is our real deadline?
Appoint an ASP by 31 March 2027 and implement by 1 July 2027 (Guidelines v2.0, section 8.3). You can go live voluntarily before that, and voluntary issuers are outside the penalty decision (Cabinet Decision 173, Article 2(2)).
What is the largest fine for missing the implementation date?
AED 50,000 in any 12 consecutive months, built from AED 5,000 for the first instance plus AED 5,000 per month (Cabinet Decision No. 173 of 2026). Per-invoice fines are separate.
Do we need e-invoicing if we are not VAT-registered?
Yes, unless an Article 4 exclusion applies. You issue a commercial e-invoice and, without a Corporate Tax TIN, register with the FTA for one (Mandatory Fields v1.1).
Our customer has not joined the system yet. Can we still send an e-invoice?
Yes. Use the predefined endpoint 0235:9900000098 and also send a regular tax invoice such as a PDF (Guidelines, section 10.2).
Are invoices between companies in our VAT group in scope?
Not for 24 months from 1 January 2027. Ministerial Decision No. 197 of 2026 excludes transactions between members of the same tax group for that period. Each member still onboards with its own participant identifier (Guidelines, Appendix 1, step 2).
Where Fanpino can help
The ASP handles validation and Peppol routing. Your side is data extraction, master-data clean-up and the connector between your ERP and the ASP's API, including how rejections flow back. That is integration work, and we build it for clients in Dubai and across the GCC. If your invoices come from more than one system, or from software your ASP has no ready connector for, talk to us about the integration.
Sources: Ministerial Decision No. 244 of 2025; Ministerial Resolution No. 66 of 2026; Ministerial Decision No. 197 of 2026; Cabinet Decision No. 173 of 2026; Cabinet Decision No. 106 of 2025 (repealed); MoF announcement, 30 October 2026; UAE E-Invoicing Guidelines v2.0; UAE Electronic Invoice Mandatory Fields v1.1; UAE eInvoicing Programme, October 2026; OpenPeppol PINT AE specifications; ZATCA Wave 25 announcement. All checked on 2 November 2026.
