The practical guide · UAE
UAE e-invoicing.
Clearly explained.
E-invoicing in the UAE means issuing invoices as structured data, exchanged through accredited service providers and reported to the FTA. This guide covers who it affects, when to be ready, how an invoice travels and what goes inside it.
Government sources only Checked
Start with the essentials
Dubai Creek · UAEConnected exchange and tax reporting.
01 / The essentials
A PDF is a document.
An e-invoice is structured data.
Under the UAE system, invoice data is issued, exchanged and received in a format software can process. Emailing a PDF or scanning a paper invoice alone does not do that. A normal invoice is made for a person to read. An e-invoice is made for the buyer’s system and the FTA to process, and it travels through accredited providers rather than by email. Our article on why a PDF invoice is not a UAE e-invoice compares the two with one sale.
Businesses in scope
Business transactions, including B2B and B2G. VAT registration is not the test for inclusion.
An accredited provider
An accredited service provider (ASP) connects your business to invoice exchange and tax reporting. You appoint one ASP for both sending and receiving. What an ASP does.
PINT-AE / XML
A UAE invoice specification and a structured electronic format, rather than a visual template.
B2C transactions, and businesses dealing exclusively in them, are outside the current mandatory rollout until a further ministerial decision. Mixed B2B and B2C businesses need to identify their in-scope transactions. See who must use e-invoicing in the UAE.
Source: Decision 243: scope and definition · Decision 244: B2C exclusion · Mandatory Fields: scope and PINT-AE
What about exclusions and tax groups?
Specific exclusions include qualifying sovereign government activity, certain airline supplies and VAT exempt or zero rated financial services. These have conditions: a sector label alone is not enough.
Decision 197 of 2026 also excludes transactions between members of the same tax group for 24 months from 1 January 2027. Guidelines v2.0 still call this a grace period in section 6.3.2. Transactions with anyone outside the group stay in scope.
A person who is excluded can still choose to issue e-invoices. The decisions then apply to them, except the penalty decisions.
Source: Decision 197 of 2026, Article 4 as replaced · Guidelines v2.0, sections 6.3.2 to 7
02 / Your deadlines
Two dates to plan around.
Appoint your provider first. Implement the system by the second deadline.
Revenue below AED 50 million
Most small businesses
- Appoint your ASP by
- 31 March 2027
- Implement by
- 1 July 2027
Revenue AED 50 million or more
Larger businesses
- Appoint your ASP by
- 30 October 2026
- Implement by
- 1 January 2027
Government entities
Government phase
- Appoint your ASP by
- 31 March 2027
- Implement by
- 1 October 2027
Revenue means gross income for the most recent accounting period, based on the financial statements or other documentation acceptable to the FTA. The pilot and voluntary implementation start date was 1 July 2026.
Updated deadline: Decision 66 of 2026 moved the larger-business ASP appointment deadline from 31 July to 30 October 2026. That date has now passed. The 1 January 2027 implementation date is unchanged. Guidelines v2.0 show 30 October in section 8.3. One MoF FAQ answer still says 31 October, but the decision text says 30 October. For the change log, tax groups and what to do now, read UAE e-invoicing deadlines.
Source: Decision 244, Articles 1 and 3 to 5 · Decision 66 of 2026 · Guidelines v2.0, section 8.3
03 / The five-corner flow
Follow one invoice.
Four corners exchange the invoice. The fifth handles tax reporting. “Corner” simply means a participant in the system.
- C1
Supplier
Creates invoice data in its business system.
Agreed format → - C2
Supplier’s ASP
Validates data. Converts to XML when needed.
PINT-AE XML → - C3
Buyer’s ASP
Validates the invoice and delivers it.
Agreed format → - C4
Buyer
Receives the invoice in its business system.
Invoice received
in parallel
successful validation
FTA reporting
Tax data collection, validation and reporting confirmations.
Exchange: C3 → C2 → C1
Tax reporting: C5 → C2 → C1 / C5 → C3 → C4
A small Dubai furniture trader sells 2 chairs at AED 100 each to a design studio. Both are in scope.
- Create. The trader’s accountant raises the invoice in its business system: AED 200 net, AED 10 VAT, AED 210 due (the calculation is in section 04).
- Validate. The system sends the invoice data to the trader’s ASP (C2), which checks it and converts it to PINT-AE XML.
- Exchange and report. C2 sends the invoice to the studio’s ASP (C3) and reports the tax data to the FTA (C5).
- Deliver. C3 validates the invoice, passes it to the studio’s system (C4) and reports the tax data too.
- Confirm. Confirmations come back to both businesses. If the trader later finds an error, it issues a credit note.
Invoice + TDD
The XML invoice goes between providers. Tax data is sent to Corner 5 as a Tax Data Document (TDD).
MLS confirmations
Message Level Status (MLS) messages report validation and reporting outcomes. Providers pass confirmations back to their businesses.
What happens if validation fails?
If the buyer’s ASP fails validation, it sends a negative status to the supplier’s ASP and Corner 5. It does not submit a TDD for that failed validation. Monitor both exchange and reporting outcomes with your provider.
Source: MoF: how e-invoicing works · Guidelines v2.0, framework
04 / PINT-AE, mapped
What goes inside the invoice?
PINT-AE defines the meaning and rules of UAE electronic invoice data. XML carries that data between systems. Peppol provides the interoperability framework used for exchange.
The MoF baseline lists 51 fields for a tax invoice and 49 for a commercial invoice. The map below groups them into business records you can prepare. Document type and transaction scenario determine the detailed requirements.
Invoice header
Invoice record + configurationNumber, issue date, document type, currency, transaction flags, due date, business process and specification identifiers, payment means.
Seller
Company masterLegal name and registration, address, country, tax identifier and scheme, electronic address and its identifier scheme.
Buyer
Customer masterName, address and electronic endpoint. The tax invoice list includes buyer tax details; the commercial list includes legal registration details.
Invoice lines
Items + quantities + pricesLine ID, item name and description, quantity, unit code, net and gross unit prices, price base quantity, line net amount, tax category and rate. Tax invoices also include line VAT and payable amounts in AED.
Tax breakdown
Tax treatmentTax category, rate, taxable base and tax amount, grouped by the applicable category and rate.
Document totals
Invoice calculationSum of line net amounts, total excluding tax, total tax, total including tax and the amount due.
This is a business-data map, not an XML template. Use the official field list and your ASP’s current PINT-AE validation rules for implementation. The numbers above are section labels, not PINT field identifiers.
Source: MoF Mandatory Fields, tax and commercial tables
Identity matters
A TIN, a TRN and an endpoint have different jobs.
- TIN
- A 10-digit tax identification number used for participant identification.
- TRN
- The 15-digit tax registration number. Keep the applicable tax registration details separate from the routing address.
- UAE endpoint
0235 : [10-digit TIN]The identifier scheme plus the electronic address. Your ASP registers the endpoint.
Source: Definitions and endpoint fields
Transaction flags and tax categories are different.
The eight transaction flags describe scenarios: free trade zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, e-commerce and exports. More than one can apply.
A tax category describes the tax treatment of a supply. The guidelines distinguish standard rate, zero rate, exempt, outside scope, domestic reverse charge and margin scheme. A 0% amount alone does not tell the whole story.
Source: Transaction flags · Guidelines v2.0, scenarios (section 10.4) · tax categories (section 10.5)
Illustrative calculation
One line. Three levels of data.
Assume a standard-rated AED invoice with no discount, extra charge or prepayment.
- Line
- 2 units × AED 100 AED 200 net
- Tax breakdown
- AED 200 × 5% AED 10 tax
- Document totals
- AED 200 + AED 10 AED 210 due
05 / Get ready
Prepare the records.
Then test the whole journey.
Confirm your scope and dates
Identify transaction types, document types and the changes needed in your invoicing system.
Choose your accredited provider
Check the MoF list. Since 1 October 2026 a provider must be accredited; the pre-approval stage no longer exists. Appoint one ASP for both sending and receiving. Compare integration, data security, support, pricing and storage arrangements, and confirm what is included and who handles failures.
Initiate onboarding in EmaraTax
The business starts the process. If you have no tax registration, first register with the FTA for a TIN. Then work with the selected ASP to obtain your participant identifier and agree the data format.
Clean and map your records
Use the PINT-AE map above to check company and customer details, endpoints, items, units, taxes and totals.
Test sending, receiving and reporting
Test the end-to-end exchange, confirmations and error resolution before go-live. Assign responsibility for monitoring and subsequent changes. Our small-business readiness checklist turns these steps into a working sheet.
Source: Readiness steps · MoF provider selection checklist · MoF provider list · Decision 168 of 2026: accreditation · Guidelines v2.0, section 6.1: one ASP
06 / After go-live
Keep the process complete.
Issue on time
VAT registrants follow the VAT-law issuance timeline. For other cases, Decision 243 now requires issuance and transmission within 14 business days of the business transaction. A business day is any day except weekends and federal government holidays.
Handle corrections
Cancellation, reduced consideration, refunds and administrative or numerical errors can require electronic credit notes under Article 6.
If the system is down
Decision 243 no longer has a separate duty to notify the FTA of a system failure. Article 12 was repealed from 1 October 2026. The guidelines expect your provider to tell you and the FTA about service disruptions and to send delayed invoices once service returns. Ask your provider how it handles outages.
Keep registration data current
Notify your ASP in writing within five business days of receiving the FTA’s confirmation of a change to registered data.
Source: Decision 243, Articles 5 and 6 · Decision 197 of 2026, Article 6(5) and the repeal of Article 12 · Guidelines v2.0, section 15.4 (ASP duties)
Retention: keep retrievable records, not just a printed copy.
Keep all e-invoices, e-credit notes and their associated data for the period set by the Tax Procedures Law. You must be able to give them to the FTA when it asks. Agree storage, access and retrieval with your provider. Using your provider for storage does not transfer your responsibility.
Guidelines v2.0 explain the retention periods, extensions and storage arrangements in section 5.4 and Appendix 4 (section 16).
Source: Decision 197 of 2026, Article 11 as replaced · Guidelines v2.0, section 5.4 · Appendix 4, storage
What penalties are specified?
- Not implementing the system, including not appointing an ASP: AED 5,000 for the first instance, plus AED 5,000 for each month or part of a month the failure continues. The total is capped at AED 50,000 in any 12 consecutive months.
- Not issuing and transmitting an e-invoice: AED 100 per e-invoice, up to AED 5,000 per calendar month. Credit notes have the same amounts.
- Not telling your ASP about changes to data registered with the FTA: AED 250 for each day or part of a day, up to AED 5,000 per calendar month.
Cabinet Decision 173 of 2026 replaced Cabinet Decision 106 of 2025. It does not apply to businesses that use e-invoicing voluntarily. If one person is both issuer and recipient for the same violation, only one penalty applies. These are the published amounts and can change. The PDF does not show the Official Gazette date.
Source: Cabinet Decision 173 of 2026, Articles 2 to 4 · Annexed table · Guidelines v2.0, section 11
07 / Common questions
The details people ask about.
Do I need to replace my accounting or ERP system?
The framework allows your system to submit invoice data to an ASP in an agreed format. Check whether your current system can supply the required data and integrate with your provider before deciding on a replacement.
Source: Integration and data management · MoF framework
Does a non-VAT-registered business issue a tax invoice?
Being in scope for e-invoicing does not itself make a business VAT registered. The MoF provides a separate commercial electronic invoice field list for invoices that are not tax invoices. A business with no tax registration registers with the FTA in EmaraTax to get a tax identification number (TIN).
What if my buyer has not joined yet?
Your buyer’s onboarding status does not remove your own obligation. For a buyer not yet implemented and without a participant identifier, the guidelines specify endpoint 0235:9900000098. A regular tax invoice is also required for that buyer when issuing a tax invoice.
Source: Buyer not yet implemented
Is any part of e-invoicing free?
To be accredited, a provider declares that it will give 100 free e-invoice exchange and reporting services a year to each end user, counted from the date that user signs. The decision does not say what counts as one service. Ask your provider what the 100 covers and what it charges after that.
Source: Decision 168 of 2026, Article 9(4) · Provider selection guide, pricing · MoF e-invoicing FAQ, service provider questions
Is a QR code the requirement?
The UAE guidelines describe electronic invoices as XML documents without a QR code or barcode. Adding a code to a PDF does not establish the required exchange and reporting process.
Source: Invoice format
08 / Official sources
Read the rules behind the guide.
Every regulatory source linked here is published by the UAE Ministry of Finance. Checked on 3 November 2026. Later decisions or guidance may change these requirements. Some MoF documents still refer to Decision 64 of 2025, which Decision 168 of 2026 replaced from 1 October 2026.
- UAE eInvoicing programme
Official overview, framework and programme resources.
- Electronic Invoicing Guidelines · V2.0, 26 October 2026
Framework, scope, readiness and operational guidance.
- Electronic Invoice Mandatory Fields · V1.1, 28 October 2026
Separate field lists for tax and commercial invoices.
- Ministerial Decision 243 of 2025
Scope, duties, credit notes and issue timing, as originally published.
- Ministerial Decision 197 of 2026
Amends Decision 243 from 1 October 2026: exclusions, 14 business days, storage, and the repeal of the system failure notice.
- Ministerial Decision 244 of 2025
Revenue definition, rollout dates and B2C exclusion.
- Ministerial Decision 66 of 2026
Revised appointment date for revenue of AED 50 million or more.
- Ministerial Decision 168 of 2026
Provider accreditation from 1 October 2026, including the 100 free services commitment.
- Considerations for Selecting an ASP · V1.1, 28 October 2026
Integration, security, support and commercial questions.
- Cabinet Decision 173 of 2026
E-invoicing violations and administrative penalties. It replaced Cabinet Decision 106 of 2025.
- MoF service provider list
Check the current provider list and published status.
Prepared by Dxbitz Technology for StarterKit. This page explains the official material in plain language. For a specific transaction, use the applicable decision, current technical rules and the advice of your tax adviser or accredited provider.
This is general information from official sources, checked against the linked documents on 3 November 2026. Ask your accountant or tax adviser to confirm how it applies to your business.
Get your business records ready.
Explore the Starter Plan for ERPNext and e-invoicing setup.
See what’s included