
Before you send your next invoice from 1 January 2027, a handful of questions decide almost everything about it. For example, is the buyer in the UAE or abroad? Also, are they a free zone company? Is this a gift, a margin-scheme sale or a monthly summary? Are you raising a credit note? In turn, each answer changes which fields, codes and checks apply. That is why the UAE e-invoicing requirements can feel overwhelming at first.
So this guide works like a decision tree. First we explain the system and the mandatory fields. After that, we walk through each transaction type, including exports and imports, and show the validation rules that most often reject an invoice. Everything here comes from the Ministry of Finance (MoF) guidelines, the ministerial decisions and the official PINT AE specification.
Key takeaways
- From 1 January 2027, businesses with revenue of AED 50 million or more must issue B2B and B2G invoices as structured XML e-invoices through an Accredited Service Provider (ASP). Businesses below that threshold follow from 1 July 2027.
- A UAE tax e-invoice has 41 mandatory fields, plus line and transaction-type details. An 8-digit flag (for example 00000001 for an export) tells the system which special scenario applies.
- Late or missing e-invoices cost AED 100 each (capped at AED 5,000 a month), and failing to implement the system costs AED 5,000 a month, up to AED 50,000 in 12 months.
What are the UAE e-invoicing requirements?
In short, an e-invoice in the UAE is not a PDF. The MoF defines it as a structured electronic invoice that software can read and process automatically. As a result, PDFs, Word files, scans and emails don’t count. Instead, your system sends the invoice data to your ASP, which validates it, converts it to the UAE XML format (called PINT AE, based on the Peppol standard) and delivers it to your buyer’s ASP. At the same time, the tax data is reported to the Federal Tax Authority (FTA).
Think of it like a registered courier network. Your ERP packs the parcel, your ASP checks the label and hands it to the buyer’s ASP, and the FTA gets a copy of the delivery note. However, if the label is wrong, the parcel comes back.
| Topic | PDF invoice today | UAE e-invoice |
|---|---|---|
| Format | PDF, paper or email | Structured XML (PINT AE) |
| Who sends it | You, by email | Your ASP, over the Peppol network |
| Checks | Manual review by the buyer | Automatic validation by both ASPs |
| Tax authority | Sees it in your VAT return | Receives tax data per invoice |
| QR code | Not required | Not used: e-invoices carry no QR code |
Who must meet the UAE e-invoicing requirements?
The obligation applies to any person conducting business in the UAE, whatever their VAT status, for business-to-business (B2B) and business-to-government (B2G) transactions. Business-to-consumer (B2C) sales, on the other hand, are outside the system for now. However, Ministerial Decision No. 243 of 2025, as amended by Ministerial Decision No. 197 of 2026, excludes these transactions:
- First, sovereign activities of government entities that don’t compete with the private sector.
- International passenger air transport with an electronic ticket, and related services with an Electronic Miscellaneous Document.
- Similarly, international air cargo with an airway bill, but for 24 months only.
- Financial services that are exempt or zero-rated under Article 42 of the VAT Executive Regulation.
- Finally, transactions between members of the same VAT tax group, for 24 months from 1 January 2027.
The mandatory fields at a glance
The MoF’s Mandatory Field Requirements (version 1.1, 28 October 2026) list 41 fields for a tax invoice and 49 for a commercial invoice (an invoice that isn’t a tax invoice, for example from a business without a TRN). Here is how the 41 tax invoice fields group together:
| Group | Fields | Count |
|---|---|---|
| Invoice details | Number, date, type code, currency, transaction type code, payment due date, business process, specification ID, payment means code | 9 |
| Seller | Name, electronic address and identifier, legal registration ID and type, TRN, tax scheme, address line 1, city, emirate, country | 11 |
| Buyer | Name, electronic address and identifier, TRN, tax scheme, address line 1, city, emirate, country | 9 |
| Totals | Line net total, total without tax, tax total, total with tax, amount due | 5 |
| Tax breakdown | Taxable amount, tax amount, category code, rate | 4 |
| Invoice line | Line ID, quantity, unit of measure | 3 |
In addition, a few values are fixed. For example, the seller’s electronic identifier scheme is 0235 for UAE businesses, the tax scheme is VAT, the country code is AE, and the legal registration type must be TL (trade licence), EID (Emirates ID), PAS (passport) or CD (Cabinet decision). Moreover, your participant ID is based on your 10-digit TIN, which is the first 10 digits of your 15-digit TRN.
Tax categories you will use
| Code | Meaning | Key rule |
|---|---|---|
| S | Standard rate | Rate must be 5.00 |
| Z | Zero rated | Rate and tax amount must be 0 |
| E | Exempt | No rate; instead, an exemption reason code is required |
| O | Outside the scope of VAT | No rate |
| AE | Reverse charge | Tax amount 0; buyer TRN and goods type required |
Why the UAE e-invoicing requirements matter for GCC businesses
First, the penalties are real. Cabinet Decision No. 173 of 2026 sets fines for not implementing the system, for each missing e-invoice or credit note, and for not telling your ASP about changes to your FTA registration data. Second, deadlines are also tighter: under Decision No. 197 of 2026, e-invoices and e-credit notes must be issued and transmitted within 14 business days of the transaction date, unless the VAT law sets a different timeline for registrants.
Third, many UAE groups also trade across the GCC. For instance, Saudi Arabia already runs its own e-invoicing system, so groups often need two compliant set-ups side by side. You can compare the rules in our guide to VAT and e-invoicing across the GCC.
How it works: the five-corner model
The UAE uses a decentralised model with five “corners”. In practice, one invoice travels like this:
- Corner 1, the supplier, sends the invoice data from its ERP to its ASP.
- Corner 2, the supplier’s ASP, validates the data, converts it to PINT AE XML and generates a unique ID (UUID).
- Next, it sends the invoice to Corner 3, the buyer’s ASP, and reports the tax data to the FTA at the same time.
- Corner 3 validates the invoice and confirms the result back to Corner 2.
- If validation passes, Corner 3 delivers the invoice to Corner 4, the buyer, and reports its tax data to the FTA.
- Corner 5, the FTA, confirms receipt to both ASPs. If validation fails, Corner 3 confirms the failure and does not report, so the supplier corrects the data and sends it again.

Above all, remember that the ASP does not calculate your invoice. In other words, calculating values stays with you, and so does the legal obligation, even when the ASP transmits and stores the invoice for you.
Scenario guide: transaction types, exports and imports
Now for the decision tree. To begin with, every invoice carries an 8-digit transaction type code. Each position is 1 (applies) or 0 (doesn’t apply), and more than one can apply at once. For example, 00000000 is a normal domestic sale, while 10000000 flags a free zone supply.
| Position | Flag | What the system then expects |
|---|---|---|
| 1 | Free trade zone | In this case, the beneficiary ID must be provided |
| 2 | Deemed supply | Buyer endpoint 0235:9900000097; if no invoice goes to a recipient, it is only reported to the FTA |
| 3 | Margin scheme | VAT shown as 0, using the “standard rate additional VAT” category |
| 4 | Summary invoice | Invoicing period required; a negative total must be a credit note |
| 5 | Continuous supply | For retentions, the invoice shows only the amount now payable |
| 6 | Disclosed agent billing | Then a principal ID is required, different from the seller TRN |
| 7 | E-commerce | Similarly, delivery address, city and emirate are required |
| 8 | Exports | Delivery address outside the UAE; buyer without a Peppol ID uses 0235:9900000099 |
Exports under the UAE e-invoicing requirements
First of all, an export of goods or services is still an e-invoice. You set the eighth flag to 1, normally use the zero-rated category where the export qualifies, and give a delivery address outside the UAE. Because most foreign buyers aren’t on the UAE network, the MoF says you must use the predefined endpoint 0235:9900000099. Furthermore, the guidelines add that the same e-invoice may be provided to Customs.
Import scenarios
By contrast, imports are simpler. According to the MoF guidelines, importing goods or services into the UAE is not subject to any e-invoicing requirement, so you don’t issue an e-invoice to yourself for import reverse charge. In contrast, the domestic reverse charge on specified goods (such as electronic devices, precious metals, oil, natural gas, hydrocarbons and metal scrap) is in scope. Specifically, those invoices use category AE, show zero VAT, include the buyer’s TRN and state the type of goods.
Other scenarios to check
- Buyer not yet onboarded: in that case, issue the e-invoice with endpoint 0235:9900000098 and also send a regular tax invoice.
- Credit notes: above all, a reason code is required (for example cancelled supply, returned goods or tax charged in error), and the original invoice must be referenced, except for volume discounts (code VD).
- Self-billing: in this case, it is allowed for tax invoices only where both parties are VAT registrants and the buyer is on the system. Otherwise, it isn’t available for commercial invoices.
- Foreign currency: likewise, if the invoice isn’t in AED, the exchange rate and AED tax totals are mandatory.
- Exempt and out-of-scope supplies: these are still in scope, unless they are excluded transactions. Even so, a TRN isn’t mandatory on commercial invoices or on these supplies.
What do the UAE e-invoicing requirements cost?
To be clear, there is no official price for e-invoicing itself. Instead, ASPs set their own fees, and the MoF publishes only the list of accredited providers. Similarly, ERP changes depend on your system and data. What the law does fix, though, is the cost of not complying:
| Violation (Cabinet Decision 173 of 2026) | Penalty |
|---|---|
| Not implementing the system, including not appointing an ASP | AED 5,000, plus AED 5,000 per month; max AED 50,000 in 12 months |
| Not issuing or transmitting an e-invoice | AED 100 per invoice; max AED 5,000 per month |
| Not issuing or transmitting an e-credit note | AED 100 per credit note; max AED 5,000 per month |
| Not telling your ASP about changes to FTA data | AED 250 per day; max AED 5,000 per month |
If you run Microsoft Dynamics 365 Business Central, your ERP licences are a separate, existing cost. For reference, Microsoft lists Business Central Essentials at US$80 and Premium at US$110 per user/month, paid yearly (as shown on 11 November 2026; local pricing, taxes and partner offers vary). Therefore, your real budget items are:
- ASP subscription: generally priced by the provider on volume or connection.
- ERP connector: an extension or integration that sends data to the ASP and tracks status.
- Master data clean-up: TRNs, trade licences, emirates, Peppol IDs, units of measure and item classifications.
- Testing and training: in particular, each scenario you use needs a tested example before go-live.
How long does it take to meet the UAE e-invoicing requirements?
The legal dates are fixed by Ministerial Decision No. 244 of 2025 and Ministerial Resolution No. 66 of 2026:
| Who | Appoint an ASP by | Go live 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 |
Within those deadlines, however, your project timeline depends on how many scenarios you use and how clean your data is. A typical project runs through these phases:
| Phase | What happens for e-invoicing |
|---|---|
| Scoping | First, list your transaction types, flags, currencies and credit note reasons |
| Design | Next, map every mandatory field to your ERP and choose the ASP |
| Configuration | Then install the connector and add TRN, endpoint and emirate data |
| Data migration | Meanwhile, clean customer, vendor and item master data |
| Testing | After that, send one test per scenario in the ASP sandbox |
| Training | Also, teach finance to read errors and resubmit |
| Go-live | Finally, switch to production and monitor statuses daily |
What speeds it up? Above all, clean master data and a short list of scenarios. On the other hand, many free zone customers, foreign currencies, agent billing or custom invoice layouts slow it down. That is why we fix the exact timeline after a free consultation.
A practical example: one trader, four invoices
This scenario is illustrative; it isn’t a real client. Imagine a Dubai trading company with revenue above AED 50 million. Then, on one Monday, its accountant posts four documents in the ERP:
- A sale to a Sharjah retailer: standard rate, transaction code 00000000, buyer TRN and emirate SHJ.
- A sale to a Jebel Ali free zone company: code 10000000, with the beneficiary ID filled in.
- An export to Muscat: code 00000001, zero rated, Omani delivery address and buyer endpoint 0235:9900000099.
- A credit note for returned goods: reason code for returned goods, linked to the original invoice number.
All four go to the ASP. However, the free zone invoice comes back rejected: the beneficiary ID was empty, which breaks rule IBR-007-AE. So the accountant adds it on the customer card and resubmits. Consequently, by evening every document shows as validated, and the FTA has its tax data.
Best practices for the UAE e-invoicing requirements
- Map scenarios before fields. First, list every transaction type you use, then map the fields each one needs.
- Clean master data first. After all, a missing TRN, emirate, legal ID or beneficiary ID each breaks an AE validation rule.
- Validate before sending. Check the AE rules inside your ERP, for example TRNs must be 15 digits starting with 1 and ending with 03.
- Test every scenario. Before go-live, send at least one sandbox invoice per flag and per credit note reason you use.
- Watch the 14-day window. Meanwhile, monitor failed and pending e-invoices daily, so nothing misses the deadline.
- Keep your ASP informed. Similarly, tell it about FTA data changes within 5 business days to avoid daily fines.
- Plan storage. Finally, records must stay in the UAE for the Tax Procedures Law period, and delegating storage to an ASP doesn’t move the legal duty.
How Mohila can help
Mohila’s UAE E-Invoicing extension for Business Central connects Business Central to Fynamics, an MoF-accredited ASP. In addition, it adds the mandatory fields, validates invoices before sending and shows the status and exact rule for every failed document. For the integration details, read our guide to UAE e-invoicing and Business Central integration, or explore our Business Central services.
Talk to an Expert
Book a free 1-hour consultation to map your transaction types and get e-invoicing ready before your deadline. Already on Business Central? See our UAE E-Invoicing extension.
Frequently asked questions
Businesses with revenue of AED 50 million or more must go live by 1 January 2027, after appointing an ASP by 30 October 2026. Others go live by 1 July 2027, and government entities by 1 October 2027.
Yes. Exports are in scope. You set the export flag, give a delivery address outside the UAE and, if the buyer has no Peppol ID, use the predefined endpoint 0235:9900000099.
No. The MoF guidelines say imports of goods and services are not subject to e-invoicing requirements. However, the domestic reverse charge on specified goods is in scope.
There is no official fee; ASPs set their own prices. Penalties for non-compliance include AED 100 per missing e-invoice, capped at AED 5,000 a month, and AED 5,000 a month for not implementing the system.
It depends on your scenarios and data quality. The legal deadlines are fixed, but the project phases (scoping, mapping, data clean-up, testing, training and go-live) are planned after a free consultation.
Sources
- MoF: UAE Electronic Invoicing Guidelines (v2.0)
- MoF: UAE Electronic Invoice Mandatory Field Requirements (v1.1)
- Ministerial Decision No. 243 of 2025
- Ministerial Decision No. 197 of 2026
- Ministerial Resolution No. 66 of 2026
- Cabinet Decision No. 173 of 2026 (penalties)
- OpenPeppol: PINT AE validation rules
- Microsoft: Business Central pricing




