E-invoicing in the UAE means generating and transmitting invoices in a structured digital format through software that connects directly to the Federal Tax Authority (FTA). Unlike a PDF emailed to a buyer, a compliant e-invoice is machine-readable, validated in real time and retained in a government-linked system.
Businesses subject to the mandate cannot simply scan paper invoices or export spreadsheets and call them e-invoices. Your software either meets the FTA’s technical specifications, or it does not.
What should you check in your software before going live?
Use this checklist to assess whether your current or shortlisted software is ready. Each item maps to a requirement in the FTA’s technical specifications.
Format and schema
- Generates invoices in UBL 2.1 XML format natively (not as a conversion layer on top of PDF)
- Supports both tax invoices (B2B) and simplified tax invoices (B2C)
- Validates the XML against the FTA’s schema before transmission
Mandatory data fields
- Captures all mandatory fields listed in the UAE e-invoicing specifications
- Generates a unique UUID per invoice
- Generates a QR code for simplified invoices
- Handles multi-line invoices with per-line VAT calculation
- Supports zero-rated and exempt supply categories
Electronic signature
- Applies a QES from a UAE-accredited TSP
- Manages signing certificates and handles renewal
- Detects and flags any post-signature tampering
Peppol connectivity
- Integrates with an accredited UAE Peppol access point
- Sends and receives invoices via the Peppol network in real time
- Handles FTA validation responses and surfaces errors to the user
- Supports automatic retry on transmission failure
Audit and retention
- Maintains an audit log of every invoice event (created, signed, transmitted, cleared or rejected)
- Stores signed XML copies of all invoices for a minimum of five years
- Provides export functionality for FTA audits
VAT calculations
- Applies the correct VAT rate per line item (5% standard, zero or exempt)
- Calculates totals accurately to two decimal places in AED
- Handles discounts correctly at the line level and invoice level
Compliance updates
- Vendor has a process for releasing updates when the FTA changes its specifications
- Update timeline is contractually defined
- You can test updated versions in a sandbox environment before deploying
What data fields does your software need to capture?
Your software must be able to populate every mandatory field in the UBL 2.1 schema. Missing or incorrectly formatted fields will cause the FTA’s system to reject the invoice.
The mandatory fields include the following:
- Seller details, including name, address, VAT registration number (TRN) and trade licence number
- Buyer details, including name, address and TRN for B2B invoices
- Invoice number and issue date
- Supply date (if different from issue date)
- Line-item description, quantity and unit price
- Applicable VAT rate per line item (standard 5% or zero-rated or exempt)
- VAT amount per line and total VAT amount
- Discount amount if applied
- Total invoice amount (exclusive of VAT, inclusive of VAT and the difference between them)
- Currency code (AED for domestic transactions)
- Payment terms and due date
- Unique invoice identifier (UUID) generated by the software
- QR code for simplified invoices issued to consumers
Software that does not capture all the required fields at the time of the transaction cannot generate a valid invoice. The mandate does not permit manual workarounds or post-entry modifications to address missing information.
How must your software connect to the FTA system?
The UAE e-invoicing framework uses the Peppol network for invoice exchange. Your software must be able to connect to an accredited Peppol access point, which acts as the gateway between your system and the FTA’s platform.
The connection process works as follows:
- Your software generates the invoice in UBL 2.1 XML and signs it with a QES.
- The signed invoice is transmitted to your accredited Peppol access point.
- The access point forwards the invoice to the FTA’s platform for validation or clearance.
- The FTA returns a response (cleared or rejected) with a timestamp.
- For B2B invoices, the cleared invoice is then delivered to the buyer’s access point.
Software that only generates XML locally and expects you to upload files manually to a government portal will not meet the real-time transmission requirement. Your system needs an API connection to an accredited access point, either built in or available as an integration.
What security and audit requirements apply?
The FTA requires the following security controls to be in place.
- Qualified electronic signatures (QES) on every invoice, issued through a UAE-accredited trust service provider (TSP)
- Any change to a signed invoice must be detectable
- Secure key management for the signing certificates
- Audit logs that record every invoice generation, transmission and status update
- Data retention for a minimum of five years, consistent with the UAE VAT regulations
Your software must either implement these controls natively or integrate with a certified third-party service that does. If your current provider cannot demonstrate compliance with each of these points, that is a gap you need to close before the mandate applies to you.
Conclusion
The UAE e-invoicing mandate is not a document format change. It is a structural shift in how tax data flows between businesses and the FTA. Software that generates invoices without a direct connection to the Peppol network, without a qualified electronic signature and without schema-compliant XML will not pass FTA validation, regardless of how accurate the numbers are.
The checklist above covers the non-negotiable technical requirements. Go through each item with your current software vendor before your phase date. If gaps exist, getting them closed takes longer than most businesses expect, particularly around certificate setup and access point integration.
TallyPrime’s UAE e-invoicing module is built to the FTA’s specifications and handles the Peppol connection, UBL 2.1 generation and QES signing within a single system.
