To be compliant, an e-invoice issued in the UAE should adhere strictly to the provisions laid out by the Data Dictionary and PINT AE standards regarding the technical specifications for UAE e-invoicing. If a document is created using either a structured XML format or (preferably) a structured JSON format, it is classified as valid under the FTA’s tax invoicing criteria. PDFs and paper invoices will no longer be accepted after 2027.
This blog outlines all the mandatory fields that need to be filled out, as well as what security features must be included, and how long they must be retained. This information will assist you with maintaining compliance with the UAE e-invoicing regulations.
Core Technical Foundation: PINT AE and UBL Standards
The UAE e-invoice specifications consist of the PINT model developed from the Peppol International e-invoicing Model, which has been designed with the UAE VAT regulations. The Ministry of Finance in the UAE published these specifications on 19 June, 2025, which include the UBL invoicing data dictionary for e-invoicing, credit notes, and debit notes.
Businesses generate the relevant e-invoice data through their respective ERP systems, and the ASP-UAE subsequently authenticates, digitally signs, and transmits the e-invoices to the sender using the Peppol Network. A key point to remember is that all e-invoices must be in a machine-readable format so as to allow for the automated validation of e-invoices and reduce the risk of human error during manual interpretation.
Invoice Header: Supplier, Buyer, and Document Essentials
All e-invoices that meet the compliance requirements of the UAE contain an e-invoice header, which contains structured header data containing information about the legal identity of the suppliers & buyers (including the TRN), along with information regarding the transaction context.
The following header fields are required:
- Supplier Detail: Legal Name, TRN (tax registration number), address, contact information, ASP identifier.
- Buyer Detail: Legal Name, TRN (only for VAT-registered buyers), address, contact information.
- Document Identifiers: Invoice Number (UUID), Date/Time Issued (UTC), Type of Invoice-Codes 380 are invoices & 381 is credit notes.
- Basic Financial Information: Currency Code (AED – primary), Payment Terms, Due Date, PO Reference.
These required header fields allow for e-invoice integration between supplier ERP systems and electronically submitted invoices through the FTA-approved e-invoicing provider network.
Line-Level Detail: Goods, Services, and VAT Breakdown
The line items of the invoice present the main taxable content of the invoicing system and require detailed UAE e-invoicing technical specifications. Each line item should include the following information:
- Description of the goods/services, quantity, and unit of measure
- The unit price and line total excluding VAT, VAT percentage is 0% or 5% or exempt, and the VAT amount should be stated for that line.
- The tax category codes must include standard, zero-rated, exempt, reverse charge, and free zone.
- If there are any discounts, allowances, or charges for the line items, this should also be included on the line level.
The summary for the aggregate totals section will provide the taxable amount, total VAT, and gross payable (including VAT). Having this in place allows accurate and automated VAT returns to be submitted to the FTA.
Security and Authenticity: Digital Signatures, QR Codes, Hashes
The security of UAE e-invoices is embedded directly into the UAE e-invoice XML format and protected from tampering.
Core security elements of the UAE E-Invoices are:
- UAE e-invoices’ digital signature (the ASP-applied cryptographic seal that validates the authenticity of the issuer of the UAE e-invoice).
- The QR Code on the UAE e-invoice provides the means to scan and obtain verification through the hash & transmission details of the UAE e-invoice.
- A hash value, which is the digital fingerprint of the invoice content, provides for Integrity checks.
- A timestamp and system acknowledgment ID of transmission received from the FTA platform.
Through the aforementioned security elements, UAE e-invoices can be instantly validated through QR Code scan or API queries, which are critical to fulfilling the UAE’s e-invoicing audit requirements.
Complete Mandatory Fields Reference Table
| Section | Mandatory UAE e-invoice mandatory fields | Purpose |
| Supplier | Legal name, TRN, address, ASP identifier | Legal/tax identification |
| Buyer | Legal name, TRN (if VAT-registered), address | Recipient accountability |
| Document | Unique Invoice Number, UTC date/time, type code | Uniqueness/tracking |
| Lines | Description, qty, unit price, VAT rate/amount | Tax calculation base |
| Totals | Taxable amount, total VAT, gross total | Payment authorisation |
| Security | Digital signature, QR code, hash, timestamp | Fraud prevention |
This matrix guides UAE e-invoicing ERP integration field mapping projects.
Storage and Archiving: Storing E-Invoices in the UAE Rules
According to the UAE tax procedure law, all e-invoices must be retained within the UAE for five years or longer, as well as be accessible to the FTA as XML or JSON data during an FTA audit.
The e-invoices also must have
- A hash chain that is tamper-proof and ensures integrity.
- The ability to retrieve the invoice from storage within 15 days of an inspection request; and
- Storage of the invoice on the UAE territory, which precludes the use of any offshore cloud services.
Accredited Service Providers in the UAE are typically responsible for providing compliant storage for e-invoices as a managed service.
ERP Integration: Mapping to UAE E-Invoicing Data Dictionary
Within the region of the United Arab Emirates, the majority of electronic invoice integration issues/challenges experienced through ERP systems are primarily due to fields in which data capture is only partially completed. Some areas of concern are as follows:
- A missing tax category code for the zero-rated/free zone supplies.
- Lack of complete validation logic for the buyer TRN.
- Missing line-level discount tracking.
- UTC timestamp generation issues.
The recommendation of the UAE e-invoicing guidance regarding the integration of e-invoicing is to:
- Perform an audit of the current data captured from invoices and validate it against the UAE e-invoicing Data Dictionary.
- To develop an e-invoice API to provide integration workshops and support with ASP endpoints.
- Conduct tests using sample payloads to validate transactions in the UAE e-invoicing Sandbox.
- To set up throttles for any validation rejection that occurs.
At this point, ERP modules for SAP, Oracle, and TALLY have developed and deployed support for the UAE e-invoicing requirements via SAP/Oracle/TALLY/ZOHO.
Credit Notes, Debit Notes, and Document Lifecycle
Unlike traditional invoices, UAE e-invoices also encompass other transactional documents, for example:
- Negative VAT lines on Credit Notes which reference the original credit note’s invoice UUID
- Debit Notes follow the same structure as a Credit Note for transactional adjustments.
- All types of documentation should include the UAE e-invoice digital signature along with Peppol transmission.
A document reference creates an audit trail for the original and correction transactions and supports ongoing transaction control.
Validation Workflow: From ERP to FTA Acknowledgment
An e-Invoice XML format that complies with UAE requirements goes through the following validation process:
- The ERP creates a structured payload that contains all of the UAE required fields for e-Invoicing.
- The e-Invoice ASP in the UAE checks the information for compliance with syntax and business rules, and then verifies the TRN status.
- The ASP adds the digital signature, creates the QR/hash, and sends the e-Invoice over Peppol.
- The FTA platform confirms that it received the e-invoice, and accordingly, the buyer receives a copy.
- The accounting and reconciliation process for a business takes place through API updates regarding the status of the transactions that were sent to the supplier and subsequently returned by the FTA.
Any e-invoices that have been rejected trigger a gap analysis process to identify the issues that led to the rejection and thus to fix those issues in the future.
Common Compliance Pitfalls and Fixes
| Pitfall | UAE e-invoice mandatory fields Issue | Fix |
| Missing buyer TRN | Validation failure | ERP TRN lookup/validation |
| Incorrect UTC timestamps | FTA rejection | System clock synchronisation |
| Incomplete VAT categories | Tax miscalculation | Master data governance |
| Poor line descriptions | Audit flags | Item master standardisation |
UAE e-invoicing readiness checklist prevents these via pre-go-live testing.
Conclusion
In order for businesses to successfully achieve compliance with the UAE e-Invoicing system introduced by the Federal Tax Authority (FTA) in 2026-2027, they must become proficient in the UAE e-Invoice Required Fields and UAE e-Invoicing Technical Specifications. By implementing structured XML Format generation of UAE e-invoices, Digital Signature Security, and the secure storage of UAE e-invoices, companies will create the secure and tamper-proof foundation needed to enable compliance with the Digital VAT requirements outlined by the FTA.
By integrating with FTA-accredited e-Invoicing Providers via an ERP system early on in the process, businesses will enjoy e-Invoicing benefits such as Automatic Processing, Shorter Processing Periods, and Greater Audit Confidence while eliminating the risk of incurring penalties for non-compliance with UAE e-invoicing requirements. The technical foundation for e-invoicing is complex, but it can be developed through the execution of a step-by-step UAE e-invoicing implementation guide that employs a systematic approach.
Frequently Asked Questions (FAQs)
- What formats are required for a compliant UAE e-invoice?
Both the XML and JSON formats for e-invoices follow the UAE’s Arabic format and structure and are required to follow the UAE’s e-invoicing legislation. The PDF and paper formats of e-invoices do not meet the FTA’s definition as compliant e-invoices under the legislation.
- Which uae e invoice mandatory fields are most critical?
The following mandatory fields for every e-Invoice submitted in the UAE are: the TRN for both Supplier and Buyer; the UUID of the e-Invoice; the VAT rate and amount on each line item; the total amount for the e-Invoice; the Digital Signature for the e-Invoice; and the QR Code for the e-Invoice must all be included for the e-Invoice to be validated.
- Where must UAE e-invoices be stored?
Every taxable person must maintain all of their e-invoices within the territory of the UAE for a period of five years or longer in accordance with Chapter 26 of the UAE’s Tax Procedures Law. Any e-Invoices stored offshore using cloud computing will not satisfy the FTA’s need for a tax audit in the UAE.
- How does the ASP fit into technical validation?
A licensed ASP in the UAE is responsible for validating that every e-Invoice submitted via the FTA’s system meets the dictionary requirements, applies the digital signature, generates the QR codes, and then transmits the e-Invoices to the FTA via the Peppol Network.
- What ERP preparation is needed for UAE e-invoicing technical specifications?
You must map every line item in your ERP to the appropriate mandatory field for the e-Invoice; maintain a UTC Timestamp for each line item; include category codes for VAT; and have API Integration with the ASP in order to test your ERP in the ASP Sandbox.
