UAE Tax & Digital Compliance Guide · Updated August 2026
UAE e-Invoicing Guide: Requirements, Timeline, ASP Rules & Business Readiness
The UAE is introducing mandatory electronic invoicing for business transactions in phases from 2027. The change affects much more than the format of an invoice. It changes how businesses create invoices, send them to customers, receive supplier invoices, report transaction data to the Federal Tax Authority and retain electronic records.
Businesses within scope will use an Accredited Service Provider (ASP) to exchange structured electronic invoices through the UAE’s Peppol-based Electronic Invoicing System. PDF invoices, Word documents, scans, images and invoices sent only by email are not electronic invoices under the new framework.
For businesses with annual Revenue of AED 50 million or more, the current deadline to appoint an ASP is 30 October 2026 and mandatory implementation begins on 1 January 2027.
UAE e-Invoicing at a Glance
What Is e-Invoicing in the UAE?
UAE e-Invoicing is the electronic creation, exchange and reporting of invoice and credit note data through the official Electronic Invoicing System.
A compliant Electronic Invoice is issued, transmitted and received in a structured electronic format that can be processed automatically. The UAE standard uses XML and the Peppol PINT-AE specification.
A PDF can be an electronic copy of an invoice, but it is not an Electronic Invoice under the UAE framework. The same applies to Word documents, scanned invoices, image files and invoice information sent only by email.
Is a PDF Invoice Compliant With UAE e-Invoicing?
No. A PDF on its own does not meet the definition of a UAE Electronic Invoice because it is not the structured invoice data exchanged through the Electronic Invoicing System.
There is an important transitional exception in practice. Where a supplier is already required to use e-Invoicing but its UAE business customer has not yet onboarded, the supplier still issues the Electronic Invoice through the system and uses the prescribed temporary endpoint. A normal readable invoice, such as a PDF, is also provided to the buyer where required. The PDF does not replace the Electronic Invoice.
Why Is the UAE Introducing e-Invoicing?
The Electronic Invoicing System forms part of the UAE’s wider digital transformation of tax administration and business processes.
The Ministry of Finance identifies objectives including:
- improving tax compliance and reducing VAT leakage;
- reducing manual invoice processing and data-entry errors;
- improving the speed and security of invoice exchange;
- strengthening electronic audit trails;
- supporting the future pre-population of certain VAT return information;
- giving the FTA access to relevant transaction data in near real time; and
- reducing paper handling and improving digital record management.
UAE e-Invoicing Laws and Regulatory Framework
The main rules currently governing the UAE Electronic Invoicing System include:
Who Must Comply With UAE e-Invoicing?
The scope is broader than VAT registration. Electronic Invoicing applies to a Person conducting Business in the UAE in respect of Business Transactions, unless the Person or transaction falls within a specific exclusion.
Depending on the facts, this can include:
- UAE mainland companies;
- Free Zone companies;
- UAE branches;
- VAT-registered businesses;
- businesses that are not registered for VAT;
- Government Entities carrying out transactions within scope; and
- certain non-UAE established Persons conducting Business Transactions for which UAE invoicing requirements apply.
A business should not use VAT registration status alone to decide whether e-Invoicing applies.
Which UAE Transactions Are Within Scope?
| Transaction | Current e-Invoicing position |
|---|---|
| B2B – Business to Business | In scope unless specifically excluded |
| B2G / G2B – Business and Government | In scope unless specifically excluded |
| G2G – Government to Government | In scope unless specifically excluded |
| B2C – Business to Consumer | Currently outside mandatory e-Invoicing |
| Transactions involving natural persons not conducting Business | Generally outside scope |
UAE e-Invoicing for Free Zone Companies
Free Zone companies are not automatically excluded from the Electronic Invoicing System. A Free Zone business carrying out Business Transactions in scope should assess its implementation phase in the same way as other businesses.
Free Zone transactions also have specific invoice-data requirements. Where the customer is a Free Zone entity, the Electronic Invoice requires beneficiary information in addition to customer information. In a normal transaction, the customer and beneficiary may be the same entity. Where the ultimate user or beneficiary is different, that information needs to be captured correctly.
Free Zone businesses should therefore review customer data, beneficiary fields, exports, VAT treatment and ERP mapping before implementation.
UAE e-Invoicing Timeline 2026–2027
The UAE is implementing e-Invoicing in phases. A business should identify its phase using the Revenue definition and current implementation decisions rather than relying on an old implementation table.
The original Phase 1 ASP deadline was 31 July 2026. Ministerial Decision No. 66 of 2026 replaced that date with 30 October 2026. The 1 January 2027 implementation date did not change.
How Is the AED 50 Million Revenue Threshold Calculated?
For e-Invoicing implementation, Revenue means the gross income earned during the business’s most recent Accounting Period, based on financial statements prepared under applicable UAE requirements.
Where those financial statements are not available, other documentation acceptable to the FTA may be used. Businesses close to AED 50 million should confirm the Revenue figure before deciding that Phase 2 applies.
How Does the UAE 5-Corner e-Invoicing Model Work?
The UAE uses a Decentralised Continuous Transaction Control and Exchange model built around five parties.
The supplier sends invoice data to its ASP. The supplier’s ASP validates the data and converts it into the UAE-standard XML format where necessary. It then sends the Electronic Invoice to the buyer’s ASP while reporting the required Tax Data to the FTA.
The buyer’s ASP validates the invoice and delivers it to the buyer. The buyer’s ASP also reports the required Tax Data to the FTA after successful validation. Electronic status messages confirm whether exchange and reporting were successful.
Businesses do not simply upload every invoice manually to an FTA invoice portal. Their ASP forms the connection between the business systems, the Peppol network and the tax-reporting process.
Does the FTA Have to Clear Every UAE e-Invoice Before It Reaches the Buyer?
The published UAE model should not be described in the same way as a traditional central pre-clearance system.
Under the 5-corner model, the supplier and buyer ASPs perform the invoice exchange and validation while required Tax Data is reported to the FTA. The system returns message-level status information for exchange and reporting. Businesses should therefore design their processes around successful ASP validation, exchange and Tax Data reporting rather than assume that every invoice waits for a separate manual FTA approval.
What Is an Accredited Service Provider?
An Accredited Service Provider is an e-Invoicing service provider approved by the UAE Ministry of Finance to provide Electronic Invoicing Services under the UAE framework.
Depending on the solution and commercial arrangement, the ASP supports functions such as:
- business onboarding through EmaraTax;
- creation of the Peppol Participant Identifier;
- invoice-data validation;
- conversion into the UAE-standard XML where required;
- secure invoice exchange between supplier and buyer;
- Tax Data reporting to the FTA;
- status and transmission messages;
- ERP and accounting-system integration; and
- technical support and transaction logging.
Appointing an ASP does not transfer the business’s responsibility for the accuracy of invoice content, VAT treatment or its own record-retention obligations.
Can a Business Use More Than One ASP?
A Person within scope should onboard with one ASP for its Electronic Invoicing requirements, covering both the sending and receiving of Electronic Invoices.
VAT groups need separate consideration. Each legal entity within the VAT group is onboarded individually and receives its own Participant Identifier based on its own TIN. Different VAT group members may use different ASPs.
What Format Will UAE e-Invoices Use?
UAE Electronic Invoices are issued, transmitted and received in XML format. They use Peppol’s PINT-AE billing specifications and the UAE data requirements.
The official guidance also confirms that the Electronic Invoice itself does not require a QR code or barcode.
A business does not necessarily have to make users work directly with raw XML. Its accounting or ERP system can exchange invoice data with its ASP in an agreed format, with the ASP converting that data into the required UAE XML where necessary.
Types of UAE Electronic Invoices and Credit Notes
The Ministry’s guidance recognises six main Electronic Invoice categories:
A Commercial Invoice is relevant where the sale does not require a VAT Tax Invoice, including certain exempt or out-of-scope supplies and invoices issued by businesses that are not VAT registered. If the Business Transaction is within e-Invoicing scope, the commercial invoice can still need to be issued electronically.
When Must an Electronic Invoice Be Issued?
Where the issuer is VAT registered, the Electronic Tax Invoice or Electronic Tax Credit Note must be issued and transmitted within the timing required under the UAE VAT rules.
Subject to that VAT rule, Ministerial Decision No. 243 of 2025 provides a general requirement to issue and transmit an Electronic Invoice or Electronic Credit Note within 14 days from the Date of Business Transaction.
The Date of Business Transaction is defined by reference to the earlier of the transaction occurring or payment being received. Businesses should therefore review invoice timing as well as invoice format.
Mandatory UAE e-Invoice Data
The exact mandatory fields depend on the document type and transaction scenario. Businesses should therefore map their systems against the UAE Mandatory Field Requirements and PINT-AE specification rather than rely on a generic invoice template.
The data model can require information covering areas such as:
- supplier and buyer identification;
- TRN or TIN where applicable;
- licence and address information;
- Participant Identifiers;
- invoice number and issue date;
- document type;
- currency;
- goods or service information;
- quantity, prices and taxable values;
- VAT category, rate and VAT amount;
- totals and payable amount;
- references to earlier documents where required; and
- additional fields for specific scenarios such as Free Zone transactions.
Customer and supplier master data should therefore be reviewed before integration begins. Incorrect legal names, identifiers, tax data or transaction codes can prevent successful validation and create downstream accounting and VAT errors.
What Is the UAE Peppol Participant Identifier?
Each business onboarded to the UAE Electronic Invoicing System receives a Participant Identifier, also known as an Endpoint ID, so that invoices can be routed correctly through the Peppol network.
The UAE Participant Identifier uses the scheme code 0235 followed by the business’s 10-digit Tax Identification Number (TIN).
Where a business is already registered with the FTA for a tax type, its TIN is the first 10 digits of its 15-digit TRN. A Person that falls within e-Invoicing scope but does not otherwise need tax registration must obtain a TIN through the FTA onboarding process.
How Does e-Invoicing Work for VAT Groups?
UAE VAT grouping does not mean that the group uses only the representative member’s Peppol identity.
Each member of a VAT group is onboarded separately for e-Invoicing. Each member uses its own TIN to generate its own Participant Identifier, and different group members may select different ASPs.
This is particularly important for groups operating several ERP systems because e-Invoicing data may need to be consolidated separately when the group prepares its normal VAT reporting.
24-Month e-Invoicing Grace Period for VAT Group Transactions
Business Transactions between members of the same VAT group remain within the scope of the UAE Electronic Invoicing System, but the June 2026 guidance provides a temporary implementation grace period.
The grace period runs for 24 months from 1 January 2027.
During that period, e-Invoicing does not have to be implemented for Business Transactions carried out between members of the same VAT group. The grace period affects timing only. It does not permanently remove intra-group transactions from e-Invoicing scope.
What Happens if the Buyer Is Not Yet on UAE e-Invoicing?
The phased rollout means some suppliers will become mandatory before some of their customers.
Where a UAE business customer has not yet implemented e-Invoicing and does not have a Participant Identifier, the supplier uses the prescribed temporary endpoint:
0235:9900000098
The supplier still processes the Electronic Invoice through the system and provides the buyer with the normal readable invoice required for its accounting or VAT records.
Special UAE e-Invoicing Endpoints
| Scenario | Endpoint | Use |
|---|---|---|
| UAE business buyer not yet onboarded | 0235:9900000098 | Transitional local-business endpoint |
| Deemed supply | 0235:9900000097 | Prescribed buyer electronic address for deemed supplies |
| Export buyer without Peppol ID | 0235:9900000099 | Prescribed export endpoint |
Special Invoice Scenarios Businesses Should Review
The Ministry’s guidance identifies several scenarios with additional e-Invoicing requirements. These include:
How Are Advance Payments Treated Under UAE e-Invoicing?
Where a business receives an advance payment and VAT becomes due, a Tax Invoice is issued when the advance is received.
When the final invoice is issued, the Ministry’s Version 1.1 guidance states that it should cover only the remaining balance, rather than invoicing the full contract value again. A reference to the earlier advance invoice can be included in the relevant PINT-AE reference fields or invoice note.
Simple example
For a contract of AED 10,000 plus VAT with a taxable AED 1,000 advance, the advance invoice covers AED 1,000 plus VAT. The later final invoice covers the remaining AED 9,000 plus VAT and references the earlier advance invoice.
How Are Retention Amounts Treated?
Retention arrangements are particularly relevant to construction, engineering and long-term project contracts.
The Ministry confirms that businesses can continue using compliant commercial and accounting practices for retention. One accepted approach is to issue an Electronic Invoice for the amount currently payable after the retention adjustment.
A separate Electronic Invoice can then be issued for the retained amount when the buyer becomes liable to release and settle it. The contract and payment terms should support the invoice treatment used.
Can UAE e-Invoices Be Stored on Cloud Servers Outside the UAE?
Yes, subject to the Electronic Invoicing storage requirements.
Article 11 of Ministerial Decision No. 243 of 2025 refers to storing Electronic Invoices, Electronic Credit Notes and associated data within the State. The Ministry’s Version 1.1 guidance clarifies how this requirement applies to modern ERP and cloud environments.
Storage infrastructure can be located inside or outside the UAE where the records remain secure, their integrity is preserved, and the business can promptly retrieve and reproduce complete and readable records for the FTA when requested.
Using an ASP or cloud provider for storage does not transfer the business’s legal responsibility for record retention.
UAE e-Invoicing Record Retention Periods
| Record type / Person | General retention period |
|---|---|
| Taxable Person | 5 years following the Tax Period to which the data relates |
| Person other than a Taxable Person | 5 years from the end of the calendar year in which the document was created |
| Real estate records | 7 years from the end of the calendar year in which the document was created |
Additional retention periods can apply in circumstances such as tax disputes, ongoing audits, notices of intended audit and certain voluntary disclosures. Businesses should therefore align e-Invoice archiving with the wider Tax Procedures record-retention rules.
What Is Excluded From UAE e-Invoicing?
The UAE framework contains specific exclusions. They should be applied narrowly rather than treated as broad industry exemptions.
- B2C transactions until a later implementation date is determined;
- qualifying sovereign activities of Government Entities;
- specified international passenger airline services where an Electronic Ticket is issued;
- specified ancillary airline services where an Electronic Miscellaneous Document is issued;
- international air transportation of goods where an Airway Bill is issued, during the temporary exclusion period;
- specified VAT-exempt financial services and certain related zero-rated exports; and
- any additional transactions excluded by a future Ministerial Decision.
Businesses in aviation, financial services and government contracting should review the exact conditions rather than assume the whole sector is excluded.
UAE e-Invoicing Penalties
Cabinet Decision No. 106 of 2025 sets specific administrative penalties for businesses that have entered mandatory e-Invoicing.
| Violation | Penalty |
|---|---|
| Failure to implement the system or appoint an ASP within the required timeframe | AED 5,000 per month or part of a month |
| Failure to issue and transmit an Electronic Invoice on time | AED 100 per invoice, capped at AED 5,000 per calendar month |
| Failure to issue and transmit an Electronic Credit Note on time | AED 100 per credit note, capped at AED 5,000 per calendar month |
| Failure to notify the FTA of a System Failure within the required period | AED 1,000 for each day or part of a day of delay |
| Failure to notify the ASP of specified changes to FTA-registered information within the required period | AED 1,000 for each day or part of a day of delay |
What Is the Deadline for Reporting an e-Invoicing System Failure?
An issuer or recipient must notify the FTA of a System Failure within 2 Business Days from the date the failure occurs.
Businesses should include this requirement in their incident-response procedure and agree with their ASP who monitors failed transmissions, who escalates technical problems and how pending invoices are exchanged and reported once service resumes.
When Must Changes to FTA-Registered Information Be Given to the ASP?
Where relevant registered data is amended with the FTA, the issuer or recipient must notify its appointed ASP in writing within 5 Business Days after receiving confirmation of the amendment from the FTA.
Why UAE Businesses Should Prepare Before Their Go-Live Date
UAE e-Invoicing is not only an IT project. It affects finance, VAT, accounts receivable, accounts payable, sales, procurement, customer onboarding, ERP administration, contracts, data governance and internal controls.
A company can have technically capable software and still experience implementation problems if its customer information, supplier information, VAT codes, invoice types or approval processes are incomplete.
The practical preparation work should therefore begin with the business process and data, followed by ASP selection, integration and testing.
UAE e-Invoicing Implementation: What Businesses Should Do Now
How e-Invoicing Affects Accounting and VAT
Electronic Invoicing makes the quality of accounting and VAT data more important because transaction data moves directly from the business’s systems through the ASP and into the reporting framework.
Businesses should expect changes to:
- sales invoicing;
- credit note controls;
- VAT codes and tax categories;
- customer and supplier master data;
- accounts receivable;
- accounts payable;
- invoice reconciliations;
- audit trails;
- VAT return preparation; and
- document retention.
How UAE e-Invoicing Affects ERP and Accounting Software
The business’s ERP or accounting system needs to hold enough structured data for the ASP to generate, validate, exchange and report compliant Electronic Invoices.
Depending on the current system, implementation may involve:
- new customer and supplier data fields;
- updated VAT and transaction codes;
- invoice and credit-note mapping;
- API or middleware integration with the ASP;
- automatic capture of status messages;
- inbound supplier-invoice processing;
- changes to advance and retention billing;
- role and approval changes; and
- electronic storage and audit-trail controls.
Businesses using SAP, Oracle, Microsoft Dynamics, Zoho Books, QuickBooks, Xero, Tally or other accounting platforms should confirm the integration method with both the software provider and the selected UAE ASP.
UAE e-Invoicing Readiness Checklist
Common UAE e-Invoicing Mistakes to Avoid
- Treating a PDF as an e-Invoice. A standalone PDF is not a compliant Electronic Invoice.
- Using the old 31 July 2026 ASP deadline. The Phase 1 appointment date is now 30 October 2026.
- Waiting until go-live to begin integration. ASP contracting, data work and testing should be completed beforehand.
- Focusing only on accounts receivable. The system also changes how supplier invoices are received and processed.
- Assuming non-VAT businesses are excluded. VAT registration is not the test for e-Invoicing scope.
- Assuming Free Zone companies are excluded. Free Zone businesses can be fully within scope.
- Ignoring master-data quality. Tax and identification data must be accurate.
- Ignoring advance payments and retentions. Existing contract billing may need to be mapped to the e-Invoicing treatment.
- Depending entirely on the ASP for record retention. The business remains responsible for compliance.
How Credora Consultancy Can Help With UAE e-Invoicing
UAE e-Invoicing requires tax, accounting, data and technology teams to work together. Credora Consultancy focuses on the tax and accounting side of that implementation and can work alongside a company’s ERP provider, ASP and internal IT team.
Credora can assist with:
- e-Invoicing scope and implementation-date reviews;
- entity and VAT-group assessments;
- invoice and credit-note process reviews;
- customer and supplier data reviews;
- VAT code and transaction mapping;
- Free Zone, export and special-scenario analysis;
- advance-payment and retention workflow reviews;
- PINT-AE accounting-data gap analysis;
- ASP evaluation from a tax and accounting requirements perspective;
- coordination with ERP and system-integration teams;
- end-to-end testing support; and
- record-retention and internal-control reviews.
Credora does not need to replace the company’s existing ERP or accounting software. The objective is to make sure the tax treatment, accounting data and business processes that feed the e-Invoicing system are ready for compliant implementation.
Explore Credora
Related UAE Tax and Accounting Services
UAE e-Invoicing sits closely alongside VAT compliance, accounting systems and wider tax reporting. Explore related Credora services.
