On 23 February 2026 the UAE Federal Tax Authority released the UAE Electronic Invoice Mandatory Fields document. It lists all required data elements for electronic tax invoices and commercial electronic invoices, aligned with the Peppol PINT-AE specification. The message for businesses is clear: your system must be able to generate structured XML with every mandatory field, or your invoices will be rejected.
Below is a simplified checklist grouped by category. The full technical list should be read alongside the FTA's PINT-AE implementation guide, but this is the practical starting point for finance and IT teams.
Mandatory field categories
Fields are grouped into the following categories. Each category has several individual data points. The full FTA publication lists 51 separate fields.
| Category | What it covers | Examples |
|---|---|---|
| Document identification | Invoice number, issue date, type, currency | Invoice ID, tax invoice type, currency, exchange rate |
| Seller information | Name, address, TRN, TIN, legal identifier, electronic address | Trade license, VAT TRN, Peppol ID 0235: |
| Buyer information | Name, address, TRN, TIN, legal identifier | Buyer TRN, free-zone flag, legal form |
| Line items | Item name, quantity, unit code, price, discount, VAT | Item code, unit (EA, KGM), VAT rate 5%, line net amount |
| Tax totals | VAT per rate, taxable amount, tax amount, exemption reason | Taxable amount AED 1,000, VAT AED 50 |
| Payment and delivery | Payment terms, due date, delivery location | Payment means, due date, supply date |
| Special scenarios | Free zones, margin scheme, deemed supply, advance payments | Free zone transaction flag, margin scheme indicator |
| Commercial only | Non-tax invoice data for B2B commercial invoices | Commercial invoice indicator, reference numbers |
HSN-style commodity codes are not currently mandatory, but the FTA has signalled they may become required for certain sectors in a later phase. Businesses in trading, manufacturing and construction should prepare their item master data accordingly.
How to choose an Accredited Service Provider (ASP)
An ASP is your gateway to the UAE e-invoicing network. It is responsible for transmitting your electronic invoices to buyers and to the FTA through the Peppol network. Choosing the wrong ASP can cause integration delays, repeated rejections and penalty exposure. Use the following criteria.
1. Active Peppol certification
The ASP must be an active Peppol Access Point and be able to pass OpenPeppol conformance testing. Ask for the certification ID and the last test date. Certification must include PINT-AE, not just the generic Peppol BIS Billing 3.0.
2. FTA pre-approval
The ASP must appear on the FTA list of accredited service providers. Do not accept a vendor that is "in the approval process" unless you are willing to take the compliance risk.
3. ERP / accounting integration depth
Ask which ERPs and accounting packages the ASP supports with a native connector. Manual upload portals are acceptable for very small volumes, but for any scale you need API-level integration. The best ASPs offer pre-built connectors for Tally, Zoho Books, QuickBooks, Xero, Odoo, Sage and major retail POS systems.
4. XML generation and validation
Does the ASP validate the 51 mandatory fields before submission, or does it just pass through whatever you send? Pre-submission validation in the ASP portal or API is a major time saver. It catches missing buyer TRNs, invalid unit codes and tax-rate mismatches before the FTA rejects the invoice.
5. Support and onboarding speed
With the large-business deadline on 30 October 2026, ASP capacity will become constrained. Ask for a realistic onboarding and sandbox testing schedule. A good ASP can move a well-prepared business from contract to production in 4β6 weeks. A poorly prepared one can take three months.
6. Pricing model
ASP pricing usually has a fixed monthly fee plus a per-invoice or per-document fee. For high-transaction businesses, the per-invoice cost can dominate. Negotiate based on your expected monthly volume and ask whether credit notes and purchase invoices are charged separately.
7. Data residency and logs
The FTA requires you to retain e-invoice data for at least five years. Ask the ASP how long logs are kept, how they are accessed, and how the ASP will support an FTA audit request. The contract should explicitly address log retention and audit support.
Short checklist before signing with an ASP
- β Active Peppol certification for PINT-AE
- β Listed on the FTA accredited ASP list
- β Native API or connector for your ERP / accounting system
- β Pre-submission validation of the 51 mandatory fields
- β Clear onboarding and sandbox timeline
- β Transparent pricing for your invoice volume
- β 5-year data retention and audit support in the contract
- β Bilingual Arabic / English invoice support
- β Buyer Peppol ID lookup or onboarding support
Bottom line
The 51 mandatory fields are the minimum data your invoices must carry. The ASP is the partner that makes those invoices legally exchangeable. Do not treat ASP selection as an afterthought. Test the integration, validate the XML, and make sure the contract covers data retention and audit support before the deadline arrives.