For detailed information +90 542 381 3868'Call.
Table of contents
When does the UAE e-invoicing mandate start?
What changed in May 2026 – and what did not
Who must comply with e-invoicing in the UAE?
What counts as an e-invoice? Why a PDF is not enough
Which transactions are in scope and which are excluded?
How the UAE e-invoicing system works (Peppol five-corner model)
UAE e-invoicing penalties: how much are the fines?
How to choose an Accredited Service Provider (ASP)
What new Dubai companies should plan from day one
How UAE e-invoicing differs from Türkiye's GİB e-Fatura system
Month-by-month plan: September 2026 to July 2027
For many business owners in Dubai, an invoice is still a PDF produced by an accounting package and an email that carries it. From 2027 that definition stops working. The UAE Electronic Invoicing System requires invoices to be created as structured data, delivered to the buyer through a service provider accredited by the Ministry of Finance, and reported electronically to the Federal Tax Authority.
Short answer
Businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and start using the system on 1 January 2027. Businesses below that threshold have until 31 March 2027 to appoint an ASP, with mandatory use from 1 July 2027. Government entities go live on 1 October 2027. The pilot and voluntary phase opened on 1 July 2026.
Although Dubai is one emirate, this is not a Dubai-only rule. It applies federally across the UAE. Whether you hold a mainland or a free zone licence does not decide the outcome. Two things do: whether your transactions fall inside the scope, and which side of the revenue threshold your business sits on.
The UAE is rolling the system out in phases by revenue level and entity type rather than switching everyone on at once. The original rules set 31 July 2026 as the ASP appointment deadline for large businesses. On 10 May 2026 the Ministry of Finance moved that date to 30 October 2026, while leaving the 1 January 2027 go-live untouched.
| Phase | Who it covers | ASP appointment deadline | Mandatory use |
|---|---|---|---|
| Pilot and voluntary | Selected pilot participants and volunteer businesses | Not applicable | From 1 July 2026 |
| Phase 1 | Annual revenue equal to or above AED 50,000,000 | 30 October 2026 | 1 January 2027 |
| Phase 2 | Annual revenue below AED 50,000,000 | 31 March 2027 | 1 July 2027 |
| Government entities | Federal and local government bodies | 31 March 2027 | 1 October 2027 |
The test uses gross revenue for the most recent financial period — not net profit and not the VAT base. The decision wording sets the threshold at "equal to or above", so a company reporting exactly AED 50 million belongs in Phase 1, not Phase 2.
Where audited financial statements do not exist, other evidence acceptable to the Federal Tax Authority may be used. Businesses that changed their financial year, went through a merger or demerger, or sit inside a group with several legal entities need to confirm their phase on a documented basis. Deciding on the strength of "we are somewhere around 50 million" creates retrospective penalty exposure; if you are close to the line, prepare on the Phase 1 timetable.
Most of the confusion in the market starts here, and plenty of pages still show 31 July 2026. The Ministry of Finance announcement of 10 May 2026 covered three points.
| 1 | Changed · ASP appointment moved three months For businesses at or above AED 50 million, the deadline moved from 31 July 2026 to 30 October 2026. The Ministry cited market readiness, the need for wider technical choice, and price competition. |
| 2 | Changed · accreditation rules relaxed Providers may now operate white-label and outsourced models, with responsibility still resting on the accredited ASP. The official pre-approved provider list passed 40 during 2026. |
| 3 | Unchanged · go-live stays 1 January 2027 Three extra months for provider selection, but a narrower integration window. Signing an ASP in late October and going live in December is not realistic for most ERP-dependent groups. |
The Ministry of Finance published version 1.1 of the UAE E-Invoicing Guideline on 1 June 2026, ahead of the pilot. It clarifies three areas in particular: the scope of data storage obligations, how advance payments are invoiced, and field-level treatment of retention billing. Confirm in writing which guideline version your provider or internal team is building against — a mapping exercise done against version 1.0 is now incomplete.
Ministerial Decision 243 does not limit scope to VAT-registered companies. The core rule is that any person conducting business in the UAE on a regular and independent basis is covered for every commercial transaction that is not expressly excluded. So the conclusion "we are not VAT registered, this does not apply to us" is wrong.
B2B transactions are the primary field of application. B2G transactions — supplies to government bodies — are also in scope apart from the listed exclusions. Purely B2C transactions sit outside the mandatory system until a further Ministerial Decision is issued.
No. Free zone status alone grants no exemption. Being licensed in DMCC, IFZA, RAKEZ, Meydan, DIFC or anywhere else does not change the analysis. Mainland companies, free zone companies, sole establishments and other legal persons all face the same two questions: is the transaction in scope, and which revenue phase applies? The threshold decides the date, not the scope.
They can. Scope attaches to conducting business in the UAE, not to VAT registration. A company below the VAT registration threshold, one that has not yet registered, or one making only zero-rated supplies still has to use the system if it issues B2B or B2G invoices. This is the distinction most often missed by finance teams used to turnover-based national rules.
A UAE e-invoice is a structured data document suitable for automatic electronic processing. A PDF, a Word file, a scan, or the email itself is not a structured e-invoice. You can keep giving customers a human-readable copy, but the compliant flow must run in the prescribed data structure across the authorised network.
The practical consequence for finance teams: if your current system only produces PDFs and sends emails, changing the file extension solves nothing. Product and customer master data, tax codes, invoice lines, currency, discounts, references and correction documents all have to be mapped to machine-readable fields. In most projects this mapping work — not the software purchase — is what sets the timetable.
The general rule is broad: transactions carried out as part of business activity in the UAE are included. Ministerial Decision 243 sets out a limited list of transaction exclusions.
| Excluded transaction | Point to watch |
|---|---|
| Government activities carried out in a sovereign capacity and not in competition with the private sector | Commercial activities of the same entity remain in scope |
| International passenger air transport where the airline issues an electronic ticket | Domestic legs and agency commissions are assessed separately |
| Ancillary airline services supplied directly to the passenger and recorded on an Electronic Miscellaneous Document | Only services supplied directly to the passenger qualify |
| International air cargo services covered by an electronic air waybill | Time-limited: 24 months from the system taking effect |
| Certain VAT-exempt or zero-rated financial services under Article 42 of the VAT Executive Regulations | Other services of the same institution stay in scope |
A company can have both in-scope and out-of-scope transactions. Aviation, financial services, government supply, mixed B2B and B2C sales, and VAT group structures should not draw a general conclusion from their licence activity; each transaction type has to be classified on its own. In practice the useful exercise is to list your revenue lines in a table and answer "is this transaction in scope?" in writing for each row. That table then sets both the integration scope and your defence in an audit. Excluded businesses may still join voluntarily.
The UAE uses a Peppol-based Decentralised Continuous Transaction Control and Exchange (DCTCE) model. In this five-corner design the parties are the supplier, the supplier's ASP, the buyer's ASP, the buyer, and the Federal Tax Authority. The key difference from a central-portal model is that the invoice travels across a network of two accredited providers rather than through a single government portal.
| 1 | Supplier to its own ASP Invoice data moves from the accounting or ERP system to the Accredited Service Provider through an API, a file upload or a direct ERP connector. |
| 2 | Validation and conversion to PINT AE The supplier's ASP validates the data against the business rules and converts it to the UAE standard XML where needed. Missing or invalid fields are rejected at this point. |
| 3 | Parallel reporting to the FTA As the validated e-invoice moves to the buyer's ASP, the required tax data is reported to the Federal Tax Authority at the same time. There is no separate filing step. |
| 4 | Buyer's ASP to the buyer The buyer's provider delivers the e-invoice into the buyer's system and passes validation results back to the parties. The buyer must also have its own ASP. |
PINT AE is the UAE adaptation of the Peppol International Invoice specification. It defines the country-specific business rules, mandatory fields and code lists. A system being able to "produce XML" is not sufficient on its own; the data structure has to match PINT AE requirements and the integration method of the provider you choose. Before signing, ask the provider to generate a sample invoice in a test environment and compare it field by field against your own ERP output.
Administrative penalties are set out in the schedule to Cabinet Decision 106 of 2025. Businesses that join voluntarily are not subject to these penalties before their own mandatory phase begins.
| Violation | Administrative penalty |
|---|---|
| Failure to implement the system on time, including failure to appoint an ASP on time | AED 5,000 for each month or part of a month of delay |
| Failure to issue and transmit an e-invoice on time | AED 100 per e-invoice, capped at AED 5,000 per calendar month |
| Failure to issue and transmit an electronic credit note on time | AED 100 per document, capped at AED 5,000 per calendar month |
| Issuer failing to notify the FTA of a system failure on time | AED 1,000 for each day or part of a day of delay |
| Recipient failing to notify the FTA of a system failure on time | AED 1,000 for each day or part of a day of delay |
| Failure to notify the ASP of a change in FTA records on time | AED 1,000 for each day or part of a day of delay |
Watch out: the double-penalty reading
The official schedule treats failure to implement the system and failure to appoint an ASP as one violation item. Some sources add them up as "AED 5,000 for the ASP plus a separate AED 5,000 for the system", giving AED 10,000 a month. The wording of the decision does not support that reading. For the amount that would apply in a specific case, rely on FTA practice and professional advice.
| Obligation | Deadline | Notify |
|---|---|---|
| Reporting a system failure | 2 business days | Federal Tax Authority |
| Reporting a change in FTA records | 5 business days | The appointed ASP |
| Issuing and transmitting an e-invoice or electronic credit note | 14 days from the date of the commercial transaction | The buyer, via the ASP network |
Specific VAT deadlines continue to apply to the last row; where the two rules differ, the shorter period binds. Naming one owner and one backup for failure notifications keeps the two-day window from lapsing over a holiday.
E-invoicing readiness is not a software purchase. Tax, finance, sales, procurement and IT have to work from the same data and control model. The sequence below has held up well across transition projects.
| 1 | Build a scope inventory List every legal entity, branch, sales channel and B2B, B2G and B2C flow in a single table. |
| 2 | Document your phase Test the AED 50 million threshold using gross revenue for the last financial period and record the statements you relied on. |
| 3 | Choose an ASP from the official list Compare integration method, security, support, service levels, data portability and exit terms before contracting. |
| 4 | Assess your ERP or accounting system PINT AE fields, XML generation, API connectivity, status messages and error handling all belong in the test scope. |
| 5 | Clean up master data Legal names, addresses, TRN or TIN, customer records, product and service codes, currencies and tax categories must be consistent. |
| 6 | Re-check your VAT logic Run scenario testing for standard-rated, zero-rated, exempt, reverse charge, export and mixed supplies. |
| 7 | Design the correction process Decide who approves an electronic credit note for cancellations, price reductions, returns and numerical errors. |
| 8 | Run a pilot Test missing fields, wrong identifiers, connection drops, rejection messages and resubmission — not just the happy path. |
| 9 | Write a failure-notification procedure Define owner, backup, evidence and escalation for the two-business-day window. |
| 10 | Manage record changes Add a control that completes the notification to your ASP within five business days of FTA approval. |
| 11 | Train the people involved Everyone who creates, approves, transmits, reconciles or fixes invoices should know the limits of their role. |
| 12 | Keep your go-live evidence Test results, the provider appointment, the contract, the mapping document, error logs and training records belong in one audit file. |
Since 1 July 2026 any business can join voluntarily and is not subject to the penalty regime until its own mandatory date. For Phase 1 companies that means November and December 2026 can be used as a live testing period with real transactions. Seeing your first rejection message on 12 November 2026 is a very different experience from seeing it on 3 January 2027.
The ASP validates, converts, transmits and reports your invoices. A poor choice creates schedule risk, not just cost. Being on the Ministry of Finance list is the first condition; fitting your systems is the second.
UAE rules set no standard ASP price. Fees vary with transaction volume, the number of systems, integration method, support level and contract scope. The "X dirhams a month" figures circulating online usually describe a single-entity, low-volume, no-integration scenario that may bear no relation to your case. The reliable approach is to request at least two or three written quotes against the same scope definition and compare total cost of ownership.
When setting up a company in Dubai, invoicing infrastructure deserves the same attention as the licence and the bank account. Even if you start far below AED 50 million, choosing a cheap accounting package that cannot produce compliant data turns into an expensive migration project ahead of the 1 July 2027 phase.
Items to settle at formation: activity code, customer type, sales countries, VAT registration status, expected invoice volume, currencies, e-commerce or POS connections, and the correction workflow. A business selling only to consumers is outside the mandatory system for now, but its first corporate order changes the picture for that transaction.
For company structure see our company formation in Dubai page, our accounting services in Dubai guide, and for tax scope our Dubai tax consultancy content.
For a finance team used to the Turkish e-Fatura system, the UAE model looks familiar but works differently. The points that cause most confusion are set out below.
| Topic | Türkiye (GİB e-Fatura / e-Arşiv) | UAE (Electronic Invoicing System) |
|---|---|---|
| Regulator | Revenue Administration (GİB) | Ministry of Finance (rules) and Federal Tax Authority (operation) |
| Architecture | Centralised; GİB portal or a private integrator | Peppol-based five-corner DCTCE model; an accredited provider is mandatory |
| Data format | UBL-TR | PINT AE (UAE adaptation of the Peppol invoice specification) |
| Scope trigger | Turnover limits and sector rules; a value threshold for e-Arşiv | Revenue only sets the phase; scope follows the transaction type (B2B, B2G) |
| Link to VAT registration | Registration status and thresholds are decisive | A company without VAT registration can still be in scope |
| B2C | Covered through e-Arşiv invoices | Outside the mandatory system until a further Ministerial Decision |
| Buyer obligations | A registered taxpayer receives the invoice from the system | The buyer needs its own ASP; failure notification applies to the buyer too |
| Timeline | Phased, with 1 January 2027 for simplified-basis taxpayers | Large businesses 1 January 2027, others 1 July 2027, government 1 October 2027 |
Treat the table as a conceptual bridge. Turkish thresholds and sector rules should be checked against current GİB circulars, and using e-Fatura in Türkiye creates no automatic right or exemption in the UAE: your Dubai company needs its own ASP appointment and its own integration.
Reading the timetable as a list of tasks is more useful than reading it as a list of dates. The plan below is a realistic sequence for a Phase 1 company; Phase 2 businesses can run the same order shifted roughly six months later.
| Period | Work to do | Output |
|---|---|---|
| September 2026 | Scope inventory, revenue threshold assessment, ERP gap analysis | Scope report and phase decision |
| September – October 2026 | Quotes from three ASPs, test-environment demonstration, contracting | Signed ASP agreement |
| 30 October 2026 | Phase 1 ASP appointment deadline | Official appointment record |
| November 2026 | Master data clean-up, PINT AE field mapping, VAT scenarios | Data mapping document |
| December 2026 | Voluntary live testing, rejection and failure scenarios, staff training | Test logs and training records |
| 1 January 2027 | Phase 1 mandatory use begins | Live operation |
| January – March 2027 | Error-rate monitoring, reconciliation, supplier and customer follow-up | Monthly compliance report |
| 31 March 2027 | ASP appointment deadline for Phase 2 and government entities | Official appointment record |
| 1 July 2027 | Phase 2 mandatory use begins | Live operation |
| 1 | Planning against the old timetable Working from sources that still show 31 July 2026 — or, in the opposite direction, treating the change as a delay and losing sight of 1 January 2027. |
| 2 | Assuming a free zone exemption Carrying the corporate tax advantages of a free zone licence across to e-invoicing scope, where they do not apply. |
| 3 | Using VAT registration as the test Assuming that no VAT registration means no obligation. Scope follows business activity. |
| 4 | Preparing only the sending side Building the outbound flow and neglecting inbound. The buyer must have its own ASP as well. |
| 5 | Leaving master data until last Discovering inconsistent customer names, tax numbers and product codes only after the provider has been signed. |
| 6 | Not designing the correction flow Leaving open who approves an electronic credit note, and within what deadline, for cancellations and returns. |
| 7 | Keeping no evidence Failing to file test results, the appointment record, training logs and failure notifications. That file is your defence in an audit. |
World Company Setup helps you plan company formation in Dubai together with the tax and accounting structure that follows it. The technical transmission of e-invoices runs through a service provider accredited by the Ministry of Finance; our role is to make sure company type, operating model, accounting infrastructure and transition timetable are considered together, so integration is not left to the last weeks.
To review the formation and accounting structure of your Dubai company, you can request a free consultation.
Author: Turgut Akkuş – Accounting and Tax Specialist, World Company Setup
Legal review: Rabia Kahraman, Attorney at Law – International Trade and Tax Law
Disclaimer: The dates, thresholds and penalties in this article reflect official publications of the UAE Ministry of Finance and the Federal Tax Authority as at 9 September 2026. Rules and amounts can change; check official sources on the day you act. This article is general information and does not constitute legal or tax advice.
<p>As at 9 September 2026 the pilot and voluntary phase is running and the mandate has not yet started. Businesses with annual revenue of AED 50 million or more must use the system from 1 January 2027; those below the threshold from 1 July 2027. Government entities start on 1 October 2027.</p>
<p>Partly. On 10 May 2026 the Ministry of Finance extended the ASP appointment deadline for large businesses from 31 July 2026 to 30 October 2026. The 1 January 2027 go-live date did not change. What moved was the provider appointment step, not the system itself.</p>
<p>The appointment deadline is 30 October 2026. Because the system has to be operational on 1 January 2027, leaving the decision to the final week removes the November and December window for integration and testing.</p>
<p>They must appoint an ASP by 31 March 2027 and use the system from 1 July 2027. Government entities share the 31 March 2027 appointment deadline but go live on 1 October 2027.</p>
<p>No. Free zone status alone grants no exemption. Whether the licence is in DMCC, IFZA, RAKEZ, Meydan or DIFC, what matters is whether the transactions are in scope and which revenue phase applies. The transaction exclusions in the Ministerial Decision are then checked separately.</p>
<p>They can. The scope in Ministerial Decision 243 attaches to persons conducting business in the UAE and is not limited to VAT-registered businesses. Having no VAT registration does not put you outside the system.</p>
<p>No. A PDF, Word file, scan, image or the email itself is not a structured e-invoice. A compliant e-invoice must be created in a machine-processable format (PINT AE) and transmitted through an accredited service provider.</p>
<p>Transactions with consumers remain outside the mandatory system until a further Ministerial Decision is issued. B2B and B2G transactions of the same business are assessed separately and are in scope.</p>
<p>Failing to implement the system or appoint an ASP on time can trigger AED 5,000 for each month or part of a month of delay. Failing to issue and transmit an e-invoice on time costs AED 100 per document, capped at AED 5,000 per calendar month. Late failure and record-change notifications can attract AED 1,000 per day.</p>
<p>There is no single regulated price. Fees depend on invoice volume, ERP connectivity, setup, support, archiving and contract scope. Request comparable written quotes, against the same scope definition, only from providers on the current Ministry of Finance accredited list.</p>
<p>Both the issuer and the recipient must notify the Federal Tax Authority within two business days of a system failure that prevents compliance. Keep the notification evidence and incident logs, and process pending documents in a controlled way once the system is back.</p>
<p>The UAE uses PINT AE, the national adaptation of the Peppol International Invoice specification. A system being able to produce XML is not enough on its own; the data structure has to satisfy the PINT AE business rules and the integration method of your chosen ASP.</p>
<p>Yes. In the five-corner model both the issuer and the recipient must be connected to an accredited service provider. The two-business-day system failure notification also applies to the recipient.</p>
<p>No. The Turkish GİB e-Fatura system and the UAE Electronic Invoicing System are independent, with different rules, formats (UBL-TR and PINT AE) and provider structures. Your Dubai company needs a separate ASP appointment and its own integration under UAE rules.</p>