Strong e-invoicing readiness starts with your ERP, not your invoice template. This guide helps Dubai finance teams check structured invoice data and the connection to an Accredited Service Provider. A PDF sent by email is not an e-invoice. For businesses in the AED 50 million or more revenue group, the 30 October 2026 ASP appointment deadline has passed; mandatory implementation is scheduled for 1 January 2027. Confirm your appointment status and test the full invoice workflow.
Deadlines: appoint an ASP first, then go live
Each group has two milestones: a date to appoint an ASP and a later date to go live.
| Business category | Appoint an ASP by | Go live by |
| Annual revenue AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Annual revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
The 30 October date replaced an earlier 31 July 2026 deadline for the largest businesses. Some older guides, and even some official documents, still show 31 July, so check the date against current Ministry guidance. Intra-group transactions currently benefit from a temporary grace period, so confirm how it applies to your group on the Ministry portal.
How a UAE e-invoice actually moves
The UAE uses a decentralized Peppol model, often described as five-corner:
- Your ERP produces the invoice data.
- Your ASP validates it against the PINT AE specification and sends it over the Peppol network.
- The buyer’s ASP receives it and delivers it to the buyer’s system.
- Tax data is reported to the Federal Tax Authority (FTA).
The ASP is a regulated intermediary, not a repair service. It cannot fix bad source data in your ERP.
Structured data vs PDF
A PDF, scan, image or email is a picture of an invoice. An e-invoice is structured data that a system can read, validate and send without retyping. According to the Ministry of Finance, PDFs, images, scans, Word files and emails do not count as e-invoices. That is why data quality matters more than invoice design.
Key data fields
The Ministry’s Mandatory Field Requirements, version 1.1 dated 28 October 2026, lists 51 fields for an electronic Tax Invoice in section 4.1. The separate commercial-invoice list differs. Use the relevant list together with PINT-AE rules for your transaction type; the count is not a substitute for checking required formats and conditions. Gaps often sit in customer identifiers, addresses, tax codes or line-item data.
The Ministry’s October 2026 field requirements say the participant identifier is based on your Tax Identification Number (TIN). For Corporate Tax-registered entities, the TIN is the first 10 digits of their Corporate Tax TRN. A Tax Group member uses its own identifier rather than the representative’s. Entities in scope without Corporate Tax registration need to obtain a TIN through the FTA. Confirm the actual endpoint setup with your ASP.
Four separate readiness questions
ERP readiness is not one yes/no question. Check each part separately:
- Data: does your ERP hold every required field, accurately?
- Format: can it, or your ASP, produce valid PINT AE structured data?
- Integration: is there a documented, supported connection between your ERP and your ASP?
- Exchange and reporting: do invoices reach the buyer and get reported, with status coming back to you?
ERP readiness checklist
| Check | What to verify | What failure looks like |
| Invoice data | Required fields captured in the correct format | Blank or free-text fields |
| Customer and supplier records | Legal names, addresses and tax numbers match registered records | Wrong or missing buyer tax number |
| Duplicates | One customer, one record | Same customer under three names |
| Tax configuration | Tax codes consistent across products and services | Mismatched tax codes |
| Credit notes and sequencing | Credit notes follow the same structured workflow, with no numbering gaps | Sequence gaps, unlinked credit notes |
| Integration | Connector, API or file export documented for your ERP version | No one owns the integration |
| Error handling | Rejections are visible and assigned for correction | Rejected invoices go unnoticed |
| Status tracking | Processing and exchange status visible in the ERP | Status lives only in the ASP portal |
| Audit trail | Corrections and statuses can be retrieved | No record of what was changed |
| Testing | Full end-to-end test of your invoice scenarios | First live invoice is the first test |
ERP-to-ASP integration options
No single method is mandated. Typical routes are a ready-made connector, an API, or a file export that the ASP converts. Ask your provider which it supports for your ERP and version, and who builds and maintains it.
Test end to end
Run the full path before go-live: ERP, your ASP, the buyer’s ASP, the buyer, and the tax reporting leg. Confirm that status and rejection messages come back into your ERP.
Illustrative example: one missing field
This is a simplified example, not a description of any specific client or system.
A Dubai distributor raises a sales invoice. The customer’s tax number was typed with a trailing space in the ERP. The ASP validates the invoice, finds the identifier invalid and rejects it. If rejection messages do not reach the ERP, the invoice looks “sent” to sales, but the buyer never receives a valid e-invoice and the sale is not correctly reported. The fix is a master data correction, a resubmission, and a process that shows rejections to the finance team the same day.
This is the reporting risk Finantrics helps finance teams close: clean source data, a clear rejection process and reconciled records.
Common failures
- Missing or wrongly formatted customer tax numbers
- Gaps in sequencing or credit note handling
- Mismatched tax codes
- No process to catch and fix rejected invoices
- Assuming the ASP will fix bad source data
Your data may be ready. Is your provider?
If your business is in the AED 50 million or more revenue group, the ASP appointment deadline was 30 October 2026. If the appointment is incomplete, check the current requirements and seek advice promptly. Check your provider against the Ministry’s official ASP list and confirm its fit for your ERP. Accreditation alone does not establish compatibility.
Before selecting a provider, check current accreditation, your ERP version, supported integration, error handling, testing responsibilities and ongoing support.
Discuss your e-invoicing data and reporting needs.
FAQ
1. Do I need a new ERP?
Not automatically. Your ERP must capture all mandatory fields, produce PINT AE-aligned structured data (directly or through your ASP’s conversion), and integrate with your ASP by connector, API or file. Compatibility depends on your ERP’s data model, version and the interfaces your ASP supports.
2. Can I send PDFs through the ASP?
No. PDFs, scans and emailed invoices are not e-invoices. The invoice must be structured data.
3. When does this apply to me?
For the AED 50 million or more revenue group, the ASP appointment deadline was 30 October 2026 and mandatory implementation is scheduled for 1 January 2027. Businesses below AED 50 million must appoint an ASP by 31 March 2027 and implement from 1 July 2027. In-scope government entities have a 31 March 2027 appointment deadline and 1 October 2027 implementation date. Check scope and any amendments on the Ministry of Finance portal.
4. What is the difference between my ERP and an ASP?
Your ERP creates and stores the invoice data. The ASP validates it, exchanges it over Peppol and supports tax reporting to the FTA.