Voluntary Start
1 Jul
2026
2026
Pilot opens for all
Large Biz Mandate
1 Jan
2027
2027
Revenue ≥ AED 50M
SME Mandate
1 Jul
2027
2027
Revenue < AED 50M
Non-Compliance Fine
AED
5,000
5,000
Per month of delay
Section 01
What is UAE E-Invoicing?
Understanding the Electronic Invoicing System (EIS) from first principles
Simple Definition
UAE e-invoicing is a government-mandated system requiring businesses to issue, exchange, and store invoices in a structured machine-readable XML format, transmitted through an Accredited Service Provider (ASP) on the Peppol network, with tax data reported to the FTA in near real-time. It is fundamentally different from emailing a PDF.
📄 Traditional Invoice (Old Way)
- Paper invoice printed and mailed
- PDF sent via email
- Manually keyed into accounting system
- No real-time reporting to tax authority
- FTA only sees data at VAT return filing
- High risk of fraud and errors
- No machine-readable structured data
⚡ E-Invoice (New Way — Required)
- Structured XML file (machine-readable)
- Transmitted via Peppol network through ASP
- Auto-validated against 50+ mandatory fields
- Reported to FTA in near real-time
- FTA has live visibility into all B2B transactions
- Tamper-evident digital format
- Compliant with PINT-AE standard
🌍 Why is the UAE doing this?
The UAE is following a global wave of e-invoicing mandates. Countries like Saudi Arabia (ZATCA), Italy, France, Singapore, Malaysia, and most EU nations have already implemented or announced mandatory e-invoicing. Key UAE motivations include:
- Tax Transparency: Give the FTA real-time visibility into all B2B and B2G transactions, not just quarterly VAT returns
- VAT Compliance: Reduce underpayment, fraud, and manual errors in VAT reporting
- Digital Transformation: Part of UAE's broader National Strategy for Digital Economy
- International Alignment: Enable UAE businesses to exchange invoices seamlessly with global trading partners on the Peppol network
- Audit Efficiency: Enable automated, data-driven tax audits instead of manual document reviews
- Economic Competitiveness: Reduce friction in B2B trade and lower compliance costs long-term
Section 02
Legal Framework
The laws and decisions that govern UAE e-invoicing
📜 Decree-Law 16 of 2024
Amended the UAE VAT Law to formally introduce the concept of e-invoicing, the Electronic Invoicing System (EIS), the Tax Reporting Mechanism, and digital invoice storage. This is the foundational legal change that enabled the entire framework.
📜 Ministerial Decision No. 243 of 2025
Defines the scope of mandatory e-invoicing — which businesses, which transactions, and what exclusions apply. Confirms it applies to all persons conducting B2B or B2G business in the UAE, regardless of VAT registration status.
📜 Ministerial Decision No. 244 of 2025
Establishes the phased implementation timeline — the specific deadlines for each category of business to appoint an ASP and go live with mandatory e-invoicing. Published September 28, 2025.
📜 Cabinet Decision No. 106 of 2025
Establishes administrative penalties for non-compliance. These are gazetted law — not estimates. Penalties apply to issuers and recipients once formally mandated. Voluntary adopters face zero penalties during the voluntary period.
📜 Ministerial Decision No. 64 of 2025
Supporting regulation covering additional technical and procedural requirements of the EIS framework. Part of the complete legislative package for e-invoicing implementation.
📋 UAE E-Invoicing Guide v1.0 (Feb 23, 2026)
The FTA's official 16-page technical document detailing the complete set of required data elements, PINT-AE XML structure, mandatory field requirements, code lists, and 15 use cases covering specific invoicing scenarios including exports and self-billing.
Governing Bodies: The UAE Ministry of Finance (MoF) oversees the overall e-invoicing program and ASP accreditation. The Federal Tax Authority (FTA) manages tax compliance, receives invoice data, and enforces penalties. Both bodies must approve Accredited Service Providers.
Section 03
Scope & Applicability
Who must comply and which transactions are covered
Broad Scope — Key Rule
E-invoicing is mandatory for ALL persons conducting business in the UAE for B2B and B2G transactions, regardless of VAT registration status, unless specifically excluded. You do NOT need to be VAT-registered to be covered — you just need to do business in the UAE.
✅ In Scope (Must Comply)
- All B2B (Business-to-Business) transactions
- All B2G (Business-to-Government) transactions
- Export invoices (must be reported, but not transmitted via Peppol)
- Self-billing invoices (buyer issues on behalf of seller)
- Third-party issuance arrangements
- Both issuers AND recipients of invoices must comply
- Foreign businesses operating in the UAE
❌ Out of Scope (Excluded)
- B2C (Business-to-Consumer) transactions — currently excluded, future phase TBD
- Sovereign government acts not competing with private sector
- Exempt or zero-rated financial services
- Certain airline and international transport services
- Other exclusions defined by Ministry of Finance
📄 Document Types Covered Under EIS
| Document Type | When Used | Peppol Transmission |
|---|---|---|
| Electronic Tax Invoice | Taxable supplies where a VAT tax invoice is required under UAE VAT rules | Required |
| Electronic Tax Credit Note | To correct, cancel, or reduce a previously issued Electronic Tax Invoice | Required |
| Commercial Invoice | Non-VAT transactions, exempt or out-of-scope supplies, or where a VAT invoice is not required | Required |
| Export Invoice | International exports out of UAE | Report only (no Peppol) |
Section 04
Full Implementation Timeline
Every key date from 2024 through 2027
Q4 2024 — ✅ Completed
ASP Accreditation Program Launched
UAE Ministry of Finance began accrediting Peppol Access Point providers (ASPs). First cohort of service providers started onboarding. Decree-Law 16 of 2024 enacted to amend the VAT law.
September 28, 2025 — ✅ Completed
Ministerial Decisions 243, 244 & 64 Published
Official legal framework confirmed. Scope, exclusions, phased timeline, and technical standards all formally established. Cabinet Decision No. 106 of 2025 also published (penalties).
February 23, 2026 — ✅ Completed
UAE E-Invoicing Guide v1.0 Released
FTA published 16-page technical document with complete PINT-AE schema, 50+ mandatory data fields, XML structure, code lists, and 15 invoicing use cases. This is the definitive technical specification.
May 10, 2026 — ✅ Completed
MoF Update: ASP Deadline Extended for Large Businesses
For businesses with revenue ≥ AED 50 million, the ASP appointment deadline was extended from July 31, 2026 to October 30, 2026. The mandatory go-live date of January 1, 2027 remains unchanged.
July 1, 2026 — 🔜 Upcoming
Voluntary Phase & Pilot Program Opens
Any business that meets the FTA technical requirements can start e-invoicing voluntarily. A pilot program runs with selected taxpayers. NO penalties apply during voluntary period. Early adopters gain zero compliance risk.
October 30, 2026 — 🔜 DEADLINE
ASP Appointment Deadline — Large Businesses (≥ AED 50M)
Businesses with annual revenue of AED 50 million or more must appoint an FTA & MoF approved Accredited Service Provider by this date. Failure triggers AED 5,000 per month penalty. Also must be ready to receive e-invoices.
January 1, 2027 — 🚨 MANDATORY
E-Invoicing Goes Live — Large Businesses
All B2B and B2G invoices for businesses with annual revenue ≥ AED 50M must be issued and transmitted via the EIS in PINT-AE XML format through their ASP. Paper and PDF invoices are no longer legally valid for these transactions. Penalties apply from day one.
March 31, 2027 — 🚨 DEADLINE
ASP Appointment Deadline — SMEs & Government Entities
All businesses with revenue below AED 50M and all government entities must appoint their accredited ASP by this date and be ready to receive e-invoices.
July 1, 2027 — 🚨 MANDATORY
E-Invoicing Goes Live — SMEs (All Remaining Businesses)
Businesses with annual revenue below AED 50M must now transmit all B2B and B2G invoices through the EIS. This covers the vast majority of UAE businesses. No more PDF or paper invoices for B2B transactions.
October 1, 2027 — 🚨 MANDATORY
E-Invoicing Goes Live — Government Entities
All public sector and government entities must be fully operational on the EIS. This completes the full rollout of UAE mandatory e-invoicing across all sectors.
📊 Quick Reference Deadline Table
| Business Category | Revenue Threshold | ASP Appointment By | Mandatory Go-Live |
|---|---|---|---|
| Large Businesses | ≥ AED 50 million/year | Oct 30, 2026 | Jan 1, 2027 |
| SMEs & Other Businesses | < AED 50 million/year | Mar 31, 2027 | Jul 1, 2027 |
| Government Entities | N/A (public sector) | Mar 31, 2027 | Oct 1, 2027 |
| Voluntary Adopters | Any size | From Jul 1, 2026 | Zero penalties apply |
Section 05
Peppol Network & the 5-Corner Model
The technical architecture that powers UAE e-invoicing
🌐 What is Peppol?
Peppol (Pan-European Public Procurement On-Line) is a globally recognized, open, and interoperable framework for the secure electronic exchange of business documents including invoices, purchase orders, and credit notes. Originally created for European public procurement, it has been adopted by governments across Asia-Pacific, the Middle East, and the UAE. The UAE Ministry of Finance officially adopted Peppol following the Dubai E-Invoicing Exchange Summit in 2024. The UAE uses Peppol because it is globally proven, enables interoperability with international trading partners, and avoids the need for a single centralized government portal.
🔄 How an Invoice Travels — The 5-Corner Model
Corner 1
Supplier
Your business — creates the invoice in your ERP
→
Corner 2
Seller's ASP
Validates XML, transmits via Peppol, reports to FTA
→
Corner 3
Buyer's ASP
Receives invoice, validates, reports to FTA, delivers to buyer
→
Corner 4
Buyer
Receives validated invoice from their ASP
⬆
Corner 5
FTA e-Billing
Receives tax data from BOTH Corner 2 & 3 simultaneously — cross-validates
UAE's Unique Dual Reporting Feature
In the UAE model, BOTH the seller's ASP (Corner 2) AND the buyer's ASP (Corner 3) independently extract tax data and report it to the FTA (Corner 5). The FTA then cross-validates both submissions. This dual-validation approach is stricter than most other countries' systems and ensures complete accuracy.
📨 Participant Identifier (Peppol ID)
- Every business gets a unique Peppol Participant Identifier
- Format:
0235+ your 10-digit TIN (Tax Identification Number) - TIN = first 10 digits of your Corporate Tax Registration Number (TRN)
- Businesses not required to register for corporate tax must still register with FTA to obtain a TIN
- This ID is how your ASP routes invoices to the correct buyer on the network
📬 Peppol MLS (Message Level Status)
- The FTA sends a Message Level Status (MLS) acknowledgement to each ASP following tax data submission
- MLS confirms successful receipt or flags failures
- Ensures accurate information sharing among all 5 corners
- Businesses must notify FTA within 2 business days of any system failure or transmission issue
Section 06
PINT-AE Format & XML Standard
The technical invoice format mandated by the UAE FTA
What is PINT-AE?
PINT-AE stands for Peppol International Invoice — UAE (Arabian Emirates). It is the UAE-specific adaptation of the global Peppol BIS Billing 3.0 standard. Think of it as the "common language" that all businesses, ASPs, and the FTA must speak when exchanging invoices. It is based on UBL 2.1 (Universal Business Language) XML and includes UAE-specific mandatory fields, VAT rules, and invoicing scenarios.
✅ Valid Invoice Formats
- ✓ Structured XML using PINT-AE standard
- ✓ UBL 2.1 compliant XML
- ✓ Machine-readable, auto-processable
- ✓ Transmitted via accredited ASP
❌ Invalid Invoice Formats (After Mandate)
- ✗ PDF invoices (even digitally signed)
- ✗ Paper invoices
- ✗ Scanned image invoices (JPG, PNG)
- ✗ Excel spreadsheet invoices
- ✗ Word document invoices
- ✗ Any non-PINT-AE XML format
📋 Key Mandatory Data Fields (50+ Required)
Every e-invoice must contain all mandatory fields from the PINT-AE Data Dictionary. The FTA's technical guide specifies the full list. Key categories include:
| Category | Key Fields Required | Notes |
|---|---|---|
| Seller Details | Legal name, TIN (10-digit), TRN, Peppol Participant ID, address | Both TIN and TRN required |
| Buyer Details | Legal name, TIN, Peppol ID (where available), address | Buyer Peppol ID required where known |
| Invoice Header | Invoice number, issue date, invoice type code, currency code | Must reference original for credit notes |
| VAT Details | VAT category (standard, zero, exempt), VAT rate, taxable amount, VAT amount | Breakdown required per line |
| Line Items | Item description, quantity, unit price, line total, HSN/SAC codes | Each line fully itemized |
| Totals | Total taxable amount, total VAT, total invoice value, allowances/charges | Machine-calculable from lines |
| Payment | Payment means, due date, IBAN/bank details (where applicable) | Optional but recommended |
| Document References | Purchase order reference, contract reference, original invoice ID (for credit notes) | Traceability requirement |
A VAT invoice under existing UAE rules has 35 mandatory data points. The new e-invoice under PINT-AE requires 50+ mandatory fields. Your ERP must be mapped to capture all additional fields.
Section 07
Accredited Service Providers (ASPs)
The backbone of the UAE e-invoicing ecosystem
What is an ASP?
An ASP (Accredited Service Provider) is a company officially approved by both the UAE Ministry of Finance and the FTA to provide e-invoicing services. Every business subject to the mandate must appoint one. Businesses cannot connect directly to the FTA e-invoicing network — all invoices must flow through an ASP. ASPs occupy Corners 2 and 3 of the 5-corner Peppol model.
✅ What ASPs Must Do (Mandatory Responsibilities)
- Validate every invoice against PINT-AE schema (50+ fields)
- Convert ERP/accounting data to required XML format
- Transmit invoices over the Peppol network
- Report tax data to FTA e-Billing System (Corner 5) in real-time
- Deliver invoice to buyer via their ASP (Corner 3/4)
- Send MLS acknowledgement of receipt/failure
- Store all invoice data securely within UAE for 10 years
- Reject non-compliant invoices and notify the sender
- Monitor and apply regulatory and PINT-AE standard updates
- Provide technical support and API/middleware integration
❌ What ASPs Cannot Do (Key Limitations)
- Cannot guarantee VAT accuracy — that is the business's responsibility
- Not liable for penalties if your business submits incorrect data
- Not responsible for compliance gaps caused by internal business failures
- Cannot advise on VAT calculations or tax law interpretation
- Accreditation is UAE-specific — does not cover other countries (e.g. KSA, Malaysia)
- Cannot operate without maintaining active MoF & FTA accreditation
🏅 ASP Accreditation Requirements (What MoF Requires)
- ISO 27001 certification (information security)
- ISO 22301 certification (business continuity)
- Multi-Factor Authentication (MFA) on all systems
- End-to-end data encryption
- Minimum 2-year operational track record
- UAE-based data residency / local data hosting
- Certified Peppol Access Point membership
- Documented SLAs and uptime guarantees
🔍 How to Choose the Right ASP
Key criteria when evaluating ASPs for your business:
- Accreditation status: Must be approved by both MoF AND FTA — check the official MoF list at mof.gov.ae
- ERP compatibility: Does it integrate natively with your system (SAP, Oracle, Dynamics 365, etc.)?
- Pricing model: Per-invoice, per-month, or enterprise pricing — understand total cost
- SLA commitments: Uptime guarantees, failover procedures, 2-day FTA notification capability
- Implementation experience: Have they done it for businesses your size/sector before?
- Local support: UAE-based support team in your timezone
- Multi-country support: If operating across the GCC, can they support KSA ZATCA and other mandates too?
- Switching: Yes, you can switch ASPs, but it requires data migration, Peppol ID transfer, and ERP reconfiguration — plan carefully
Section 08
ERP Integration & Implementation Steps
How to get your business systems ready for e-invoicing
🔧 Step-by-Step Implementation Roadmap
- Step 1 — Understand Your Phase: Determine which deadline applies to your business based on annual revenue. Large businesses (≥ AED 50M) must comply from Jan 1, 2027. SMEs follow from Jul 1, 2027.
- Step 2 — Register for TIN: If you don't already have a Corporate Tax Registration Number (TRN), register with the FTA. Your TIN is the first 10 digits of your TRN and is required for your Peppol Participant ID.
- Step 3 — Select & Appoint an ASP: Research and appoint an FTA & MoF approved Accredited Service Provider before your deadline. This is a legal requirement. Allow 2–4 months for full integration and testing.
- Step 4 — ERP Data Mapping: Work with your ASP and IT team to map all internal ERP data fields to the 50+ mandatory PINT-AE fields. This includes TRNs, Participant IDs, HSN/SAC codes, and VAT breakdowns per line item.
- Step 5 — Capture Buyer Peppol IDs: Start collecting your buyers' Peppol Participant IDs (0235 + 10-digit TIN). Without this, invoices cannot be routed to the correct buyer on the network.
- Step 6 — API/Middleware Integration: Your ASP will install middleware or provide an API that connects your ERP to the Peppol network. Most major ERPs (SAP, Oracle, Dynamics, Sage, QuickBooks) have pre-built connectors.
- Step 7 — Configure Credit & Debit Notes: Credit notes and debit notes must also be issued in PINT-AE XML format and must reference the original e-invoice identifier. Update your workflows accordingly.
- Step 8 — Testing: Run end-to-end tests before your go-live date. Test invoice submission, validation, FTA reporting, buyer delivery, and acknowledgement receipt. Resolve all errors.
- Step 9 — Staff Training: Train finance and accounts payable/receivable staff on new workflows. Most ASPs automate the XML conversion — staff should understand what triggers an e-invoice and how to handle rejections.
- Step 10 — Go Live & Monitor: Begin live transmission. Monitor for validation failures, transmission errors, and FTA acknowledgements. Set up real-time alerts. Ensure 2-day FTA notification protocol is in place for any system failures.
Section 09
Data Storage Requirements
Where, how long, and in what format invoices must be kept
Minimum Storage Period
10 Years
All e-invoices & credit notes
Data Location
UAE Only
Must be stored within UAE
FTA Notification
2 Days
If system failure occurs
💾 Data Storage Rules
- All invoice and credit note data must be stored within the UAE (data residency requirement)
- Storage must preserve data integrity — invoices cannot be altered after transmission
- Data must be retrievable by the FTA on demand at any time during the 10-year period
- Your ASP handles archiving as part of their accredited service
- In the event of switching ASPs, ensure data migration includes all archived invoices
- Businesses must notify the FTA within 2 business days if their e-invoicing system fails
- Storage failure or inability to produce invoices for FTA = AED 10,000–20,000 penalty
Section 10
Penalties & Fines
Official administrative penalties under Cabinet Decision No. 106 of 2025
Voluntary Adoption = Zero Penalties
Businesses that implement e-invoicing before their mandatory deadline during the voluntary phase are fully exempt from all penalties. This is the single most effective way to eliminate compliance risk entirely. Going live early is now possible from July 1, 2026.
| Violation | Penalty Amount | Legal Basis |
|---|---|---|
| Failure to appoint an ASP by deadline | AED 5,000/month of delay | Cabinet Decision 106/2025 |
| Failure to implement e-invoicing by mandatory date | AED 5,000/month from day 1 | Cabinet Decision 106/2025 |
| Reporting breach (invoice-level failures) | AED 5,000/month cap | Cabinet Decision 106/2025 |
| Failure to issue an e-invoice when required | AED 2,500 per missing invoice | Cabinet Decision 40/2017 (amended) |
| Failure to maintain required records | AED 10,000–20,000 (escalates for repeat violations) | Cabinet Decision 40/2017 (amended) |
⚠️ Additional Non-Monetary Consequences
- Loss of input VAT credit — you may not be able to claim VAT refunds
- Customer compliance failures — your non-compliant invoices force penalties on your buyers too
- Loss of business opportunities — large enterprises and government buyers will refuse non-compliant suppliers
- Non-compliance status with FTA — triggers increased audit scrutiny
- Potential criminal liability for fraudulent e-invoicing practices
Important: Penalties fall on the business, not the ASP. Even if your ASP causes a delay, you are legally responsible. Ensure your ASP contract includes SLA commitments and liability clauses for ASP-caused failures.
Section 11
Compliance Checklist
Click the circles to track your readiness — saved in this session
- Determine your revenue category — are you ≥ AED 50M (Phase 1) or < AED 50M (Phase 2)?
- Register for Corporate Tax / obtain TIN — needed for your Peppol Participant ID even if not CT-liable
- Review all B2B and B2G transactions — identify every invoice flow that will be in scope
- Identify excluded transactions — confirm which of your transactions qualify as B2C or otherwise excluded
- Shortlist 3+ ASPs from the official MoF accredited provider list at mof.gov.ae
- Evaluate ASPs — check ERP compatibility, pricing, SLAs, implementation experience, and local support
- Appoint your ASP — sign contract before your applicable deadline (Oct 30, 2026 or Mar 31, 2027)
- Map ERP data fields — align all internal fields to the 50+ PINT-AE mandatory fields in the FTA data dictionary
- Collect buyer Peppol IDs — gather the Peppol Participant IDs of all your regular B2B customers
- Integrate ASP with ERP — complete API/middleware setup and configure invoice workflows
- Configure credit & debit notes — ensure they use same XML format referencing original invoice ID
- Test end-to-end — validate submission, transmission, FTA reporting, buyer delivery, and MLS acknowledgement
- Set up failure notification protocol — ensure team knows to notify FTA within 2 days of system failure
- Train finance & AP/AR team — new workflows for issuing, receiving, and handling rejected e-invoices
- Verify data storage — confirm ASP stores data within UAE and meets 10-year retention requirement
- Consider early voluntary adoption — go live before mandatory date to eliminate all penalty risk
Compliance Progress0 / 16 completed
Section 12
Comparisons
UAE vs Saudi Arabia (ZATCA) and E-Invoice vs PDF
🆚 UAE E-Invoicing vs Saudi Arabia (ZATCA)
| Feature | UAE (EIS) | Saudi Arabia (ZATCA Fatoorah) |
|---|---|---|
| Model | Decentralized (5-corner Peppol) | Clearance-based (centralized) |
| Standard | PINT-AE (UBL 2.1 XML) | UBL 2.1 / XML with QR code |
| Network | Peppol open network | ZATCA centralized platform |
| B2C Scope | Excluded (for now) | Included (Phase 2) |
| Real-time Clearance | Near real-time reporting | Pre-clearance before sending |
| Service Provider | MoF+FTA accredited ASP | ZATCA approved ECSP |
| Data Residency | UAE only | KSA only |
| International Interoperability | High (Peppol global network) | Limited |
🆚 E-Invoice vs PDF Invoice
| Feature | PDF / Paper Invoice (Old) | UAE E-Invoice — PINT-AE (New) |
|---|---|---|
| Format | Human-readable only | Machine-readable XML |
| Transmission | Email, post, WhatsApp | Peppol network via ASP |
| FTA Reporting | Only at VAT return filing | Near real-time |
| Validation | Manual / none | Automated against 50+ fields |
| Error Detection | Discovered at audit | Rejected before transmission |
| Fraud Risk | High | Low (tamper-evident) |
| Legal Validity (post-mandate) | Not valid for B2B | Only valid format |
| Data Fields | ~35 fields (VAT invoice) | 50+ mandatory fields |
| Archiving | Manual | Automated (10 years, UAE) |
| ERP Integration | Manual export/print | Automated API flow |
Section 13
Glossary of Key Terms
All the important acronyms and concepts defined
EIS — Electronic Invoicing System
The UAE's national mandatory e-invoicing framework, introduced by the Ministry of Finance and FTA, covering all B2B and B2G transactions.
ASP — Accredited Service Provider
A company accredited by the UAE MoF and FTA to validate, transmit, and report e-invoices on the Peppol network. Every business must appoint one.
PINT-AE — Peppol International Invoice, UAE
The UAE-specific XML invoice format standard based on UBL 2.1 and the Peppol BIS Billing 3.0 global standard. All UAE e-invoices must comply with PINT-AE.
Peppol — Pan-European Public Procurement On-Line
A globally recognized, open, decentralized network for electronic exchange of business documents. The UAE adopted Peppol as the backbone of its EIS.
5-Corner Model
The Peppol architecture used in the UAE: Supplier (1) → Seller's ASP (2) → Buyer's ASP (3) → Buyer (4), with both ASPs reporting tax data to FTA (5) simultaneously.
TIN — Tax Identification Number
The UAE national tax identifier used for e-invoicing. It is the first 10 digits of your Tax Registration Number (TRN). Required even for non-VAT-registered businesses.
TRN — Tax Registration Number
The 15-digit VAT registration number issued by the FTA. The first 10 digits form your TIN used as the Peppol participant identifier.
Participant Identifier (Peppol ID)
The unique network address for each business on the Peppol network. Format: 0235 + 10-digit TIN. Used to route invoices to the correct buyer's ASP.
CTC — Continuous Transaction Control
A tax compliance model where invoice data is reported to the tax authority in real-time (or near real-time) at the time of transaction, rather than periodically.
DRR — Digital Reporting Requirements
The broader framework that gives the FTA ongoing visibility into economic activity through structured digital data, not just periodic filings.
FTA — Federal Tax Authority
The UAE government body responsible for tax administration, VAT compliance, e-invoicing enforcement, and receiving invoice data via the EIS.
MoF — Ministry of Finance
The UAE government ministry overseeing the overall e-invoicing program, ASP accreditation, and policy framework.
UBL — Universal Business Language
An open library of standard XML business document formats (invoices, purchase orders, etc.) published by OASIS. PINT-AE is based on UBL 2.1.
MLS — Message Level Status
Peppol standard for broadcasting acknowledgements of successful or failed invoice transmissions between all parties in the 5-corner model.
B2B — Business-to-Business
Transactions between two businesses. All B2B invoices are in scope for UAE mandatory e-invoicing.
B2G — Business-to-Government
Transactions from businesses to government entities. All B2G invoices are in scope for UAE mandatory e-invoicing.
B2C — Business-to-Consumer
Transactions from businesses to individual consumers. Currently excluded from the UAE e-invoicing mandate. A future phase may include them.
DCTCE — Decentralized Continuous Transaction Control and Exchange
The technical model used in the UAE EIS, where invoices are exchanged peer-to-peer through ASPs on the Peppol network, with simultaneous reporting to the FTA.
HSN/SAC Codes
Harmonized System Nomenclature (goods) and Services Accounting Codes (services) — classification codes required in PINT-AE invoice line items.
Credit Note (Electronic)
An e-document issued to correct, cancel, or reduce a previously issued Electronic Tax Invoice. Must use the same PINT-AE XML format and reference the original invoice ID.
Section 14
Frequently Asked Questions
25 key questions with detailed answers — click to expand
📌 BASICS
What is UAE e-invoicing and how is it different from a PDF invoice?
UAE e-invoicing means issuing invoices as structured XML files (in PINT-AE format), transmitted through a government-accredited service provider (ASP) on the Peppol network, with tax data reported to the FTA in real-time. A PDF invoice is a human-readable document — not machine-readable, not validated, and not connected to any tax reporting system. After the mandatory date, PDFs are no longer legally valid for B2B or B2G transactions in the UAE.
Does e-invoicing apply to businesses that are not VAT-registered?
Yes. The UAE e-invoicing mandate applies to ALL persons conducting B2B or B2G business in the UAE, regardless of VAT registration status. Non-VAT-registered businesses must still obtain a TIN (Tax Identification Number) from the FTA and comply with the mandate unless they fall within a specific exclusion.
Are B2C transactions included in the UAE e-invoicing mandate?
No — B2C (business-to-consumer) transactions are currently excluded from the mandate. Only B2B and B2G transactions are in scope. The government has not yet announced when or if B2C will be included in a future phase.
What is the difference between TIN and TRN in UAE e-invoicing?
TRN (Tax Registration Number) is the 15-digit VAT registration number issued by the FTA. TIN (Tax Identification Number) is the first 10 digits of your TRN and is the national identifier used specifically for e-invoicing purposes. Your Peppol Participant ID is formatted as "0235" followed by your 10-digit TIN.
Which government laws govern UAE e-invoicing?
The key legal instruments are: Decree-Law 16 of 2024 (amends UAE VAT Law to introduce e-invoicing), Ministerial Decision No. 243 of 2025 (scope and applicability), Ministerial Decision No. 244 of 2025 (phased timeline and deadlines), Ministerial Decision No. 64 of 2025 (supporting technical provisions), and Cabinet Decision No. 106 of 2025 (administrative penalties). The FTA also published UAE E-Invoicing Guide v1.0 on February 23, 2026 as the definitive technical specification.
📅 TIMELINE & DEADLINES
When is e-invoicing mandatory for large businesses with revenue above AED 50 million?
Large businesses with annual revenue of AED 50 million or more must appoint an ASP by October 30, 2026, and must be fully live on mandatory e-invoicing by January 1, 2027. The voluntary pilot opens for everyone from July 1, 2026.
When is e-invoicing mandatory for small and medium businesses?
SMEs with annual revenue below AED 50 million must appoint their ASP by March 31, 2027, and must go live with mandatory e-invoicing by July 1, 2027.
What happens if I adopt e-invoicing voluntarily before the mandatory date?
You are fully exempt from all penalties during the voluntary period. Voluntary adoption also gives you more time to resolve integration issues, train staff, and optimize your workflows without compliance pressure. The voluntary phase opens July 1, 2026 for any technically ready business.
🔧 TECHNICAL
What is PINT-AE and what does it stand for?
PINT-AE stands for Peppol International Invoice — UAE (Arabian Emirates). It is the UAE-specific XML invoice format standard based on UBL 2.1. All UAE e-invoices must comply with PINT-AE. It includes UAE-specific mandatory fields, VAT requirements, and invoicing scenarios. It is a localized adaptation of the global Peppol BIS Billing 3.0 standard but is not identical to it.
How does the Peppol 5-corner model work in the UAE?
When you issue an invoice: (1) You create it in your ERP. (2) Your ASP validates the XML and transmits it via Peppol. (3) The buyer's ASP receives it. (4) The buyer receives the invoice. Meanwhile, both Corner 2 and Corner 3 simultaneously report tax data to the FTA (Corner 5), which cross-validates both submissions. MLS acknowledgements confirm successful delivery at each step.
Can I still send PDF invoices after the mandate takes effect?
No. After your mandatory go-live date, PDF invoices, paper invoices, scanned copies, and Excel files are not legally valid for B2B or B2G transactions. Only PINT-AE XML invoices transmitted through an accredited ASP are considered valid e-invoices under UAE law.
How must credit notes be handled under UAE e-invoicing?
Electronic credit notes must be issued in the same PINT-AE XML format as regular e-invoices and must reference the unique identifier of the original e-invoice being corrected or cancelled. They must be transmitted through your ASP via the Peppol network just like any other invoice.
How do I integrate my ERP (SAP, Oracle, Dynamics 365) with e-invoicing?
Your chosen ASP will provide API-based middleware that connects to your ERP. The ASP handles format conversion (your ERP data → PINT-AE XML). You must first map all your internal ERP data fields to the 50+ mandatory PINT-AE fields (data dictionary mapping). Most major ERP vendors (SAP, Oracle, Microsoft, Sage) have pre-built connectors for UAE Peppol compliance. Implementation typically takes 2–4 months.
🏢 ASP QUESTIONS
Is it mandatory to appoint an ASP? Can I connect to the FTA directly?
Yes, appointing an ASP is legally mandatory. Businesses cannot connect directly to the FTA e-invoicing network. All invoices must flow through an accredited ASP that is approved by both the Ministry of Finance and the FTA. Your ASP occupies Corner 2 (seller's side) in the 5-corner model.
Can I switch my ASP provider after going live?
Yes, you can switch ASPs, but it requires careful planning. The transition involves: data migration of all archived invoices, transferring or re-registering your Peppol Participant ID, ERP reconfiguration and re-integration, and thorough testing to ensure no compliance gaps during the switchover period.
Is the ASP liable if my invoice contains a VAT error?
No. ASPs are technical intermediaries, not tax advisors. They validate invoice structure and format compliance — but VAT accuracy, correct tax codes, and correct amounts are entirely your responsibility. Under UAE regulations, all financial penalties for errors fall on the business, not the ASP. Review your ASP contract carefully for liability limitations.
Where can I find the official list of approved ASPs in the UAE?
The Ministry of Finance maintains and regularly updates the official list of Accredited Service Providers on their website at mof.gov.ae. Only use ASPs on this official list to ensure full compliance with the UAE EIS framework.
⚠️ PENALTIES & RISK
What are the exact penalties for not complying with UAE e-invoicing?
Under Cabinet Decision No. 106 of 2025: Failing to appoint an ASP = AED 5,000 per month of delay. Failing to implement e-invoicing after mandatory date = AED 5,000 per month from day one. Failing to issue an e-invoice when required = AED 2,500 per missing invoice. Failing to maintain required records = AED 10,000–20,000 (escalating for repeat violations). Additional consequences include loss of input VAT credit and potential criminal liability for fraud.
What happens if my ASP system fails and I miss a submission deadline?
You must notify the FTA within 2 business days of any system failure. Document the failure and work with your ASP to resolve it immediately. Penalties under Cabinet Decision 106/2025 still apply to your business even for ASP-caused failures — ensure your ASP contract includes SLA commitments, uptime guarantees, and liability clauses for their system failures.
How long must e-invoices be stored and where?
All e-invoices must be stored for a minimum of 10 years. The data must be stored within the UAE (data residency requirement). It must preserve integrity (tamper-evident), be retrievable by the FTA on demand at any time, and be capable of reproduction in the original format. Your ASP handles this as part of their accredited service.
🌐 WEBSITE BUILDING
What features should a UAE e-invoicing compliance website or SaaS platform include?
Key features to consider: (1) PINT-AE XML invoice generator with all 50+ mandatory fields. (2) ERP integration connectors (SAP, Oracle, Dynamics, QuickBooks, Xero). (3) Peppol network connection (you'd need ASP accreditation from MoF/FTA). (4) Real-time FTA reporting engine. (5) Invoice validation against PINT-AE schema. (6) 10-year UAE-based archive. (7) Credit note management. (8) Buyer Peppol ID lookup/directory. (9) Compliance dashboard with submission status. (10) Multi-company and multi-currency support. (11) Failure alerts and 2-day FTA notification workflow.
What are the steps to become a licensed ASP in the UAE?
To become a licensed Accredited Service Provider: (1) Apply to the Ministry of Finance through the official ASP accreditation process. (2) Obtain ISO 27001 (information security) and ISO 22301 (business continuity) certifications. (3) Demonstrate minimum 2-year operational track record as a technology/e-invoicing provider. (4) Implement Multi-Factor Authentication and end-to-end encryption across all systems. (5) Become a certified Peppol Access Point member. (6) Establish UAE-based server infrastructure for local data residency. (7) Pass MoF technical and operational audits. Full requirements are published by the Ministry of Finance at mof.gov.ae.
What APIs or integrations are needed to build a UAE e-invoicing platform?
A UAE e-invoicing platform needs: (1) Peppol AS4 or AS2 access point protocol for network transmission. (2) PINT-AE XML schema validation engine. (3) FTA e-Billing System API for tax data reporting (requires ASP accreditation). (4) ERP connector APIs for SAP (Business Suite/S4HANA), Oracle (Fusion/EBS), Microsoft Dynamics 365, Sage, QuickBooks, Xero, Zoho. (5) A UBL 2.1 XML library for invoice generation. (6) MLS (Message Level Status) acknowledgement processor. (7) UAE-compliant encrypted data storage API. (8) REST/webhook API for client business systems to push invoice data.