Why is the UAE introducing e-invoicing?
The UAE introduced VAT in 2018. E-invoicing is the next step in digitising tax compliance. Instead of invoices travelling as PDFs and paper, with tax data reaching the authority only through periodic returns, invoices become structured data that flows between businesses and to the Federal Tax Authority (FTA) as transactions happen.
For the government, this means better visibility of VAT and fewer opportunities for fraud. For businesses, it means faster processing, fewer data-entry errors and, over time, simpler compliance. It also means a technical project: your invoicing system must produce and exchange data in a defined format through a defined channel.
The UAE did not build a central government invoice portal. It chose a model built on Peppol, the international e-delivery network already used across Europe and Asia-Pacific, adapted with a UAE specification and a tax-reporting layer.
Who must comply with UAE e-invoicing?
The Ministry of Finance has set out the scope and the phases in ministerial decisions. In summary:
- Transactions covered: business-to-business (B2B) and business-to-government (B2G). Business-to-consumer (B2C) is not part of the initial scope.
- Businesses covered: businesses carrying out these transactions in the UAE, brought in through a phased rollout that starts with larger businesses (by revenue) and extends to the rest in later phases.
- Government entities: included in their own phase.
- Exclusions: certain transaction types are excluded or treated differently. Check the official decisions for the current list.
Two points businesses often miss. First, receiving is affected as well as issuing. Your suppliers’ invoices will arrive through Peppol, so accounts payable needs a process too. Second, groups with several UAE entities, free zone companies or branches on different systems need a plan for every invoicing source, not just the main ERP.
Because dates and thresholds can be adjusted, we don’t list deadlines here. Check the Ministry of Finance’s e-invoicing page for the schedule that applies to your business.
How does the UAE 5-corner model work?
The UAE uses what is often called a decentralised continuous transaction control and exchange (DCTCE) model, built on Peppol’s 4-corner exchange with a fifth corner for tax reporting.
| Corner | Who | What happens |
|---|---|---|
| 1 | Supplier | Your ERP creates the invoice data |
| 2 | Supplier’s ASP | Validates against PINT AE and sends over Peppol |
| 3 | Buyer’s ASP | Receives the invoice on Peppol |
| 4 | Buyer | Receives the structured invoice in their system |
| 5 | Federal Tax Authority | Receives the tax data reported by the ASPs |
The practical consequence: your system’s integration point is your ASP, not the FTA. The ASP handles Peppol exchange and reporting. Your job is to send complete, accurate invoice data to your ASP and to handle the responses.
What is PINT AE?
PINT AE is the UAE’s national specification of the Peppol International (PINT) invoice model. It defines:
- The XML structure (based on UBL) for invoices and credit notes.
- The mandatory and conditional fields: supplier and buyer details, Tax Registration Numbers, invoice type, dates, line items, tax categories and rates, totals and currency.
- Code lists for tax categories, units of measure, invoice types and payment means.
- Business rules that validate amounts, rounding and field combinations.
- Rules for specific scenarios such as zero-rated exports, reverse charge, self-billing and disclosed agents.
If you’ve worked with Peppol BIS Billing 3.0 in Europe, PINT AE will look familiar, but with UAE-specific fields and rules. Don’t assume a European Peppol integration works in the UAE unchanged.
What is an Accredited Service Provider (ASP)?
An ASP is a service provider accredited by the UAE Ministry of Finance to exchange e-invoices on Peppol and report data to the FTA on behalf of businesses. The Ministry publishes the list of accredited providers.
Every in-scope business needs to appoint an ASP. Choosing one is a commercial and technical decision: API quality, ERP connectors, support, pricing model and data residency all matter. We cover this in detail in what an ASP is and how to choose one.
Co-Mate is not an ASP. We build the connection between your ERP and the ASP you choose, and we design it so you can change ASP later without rebuilding your integration.
What changes inside your business?
E-invoicing is often treated as an IT task. In practice it touches several teams:
- Finance: tax codes must map precisely to PINT AE categories. Credit notes need clear references to original invoices. Rejections need an owner.
- Sales and customer service: customer records need correct Tax Registration Numbers and Peppol identifiers. Missing data blocks invoices.
- Accounts payable: inbound e-invoices arrive in structured form, which is an opportunity to automate matching and approval.
- IT: the ERP must expose invoice data reliably, and the integration must be monitored.
How do you integrate your ERP with UAE e-invoicing?
There are three common routes:
- ERP vendor module. Some ERP vendors offer UAE e-invoicing modules for certain versions, often tied to specific ASPs.
- Middleware connector. A separate service reads invoices from your ERP, maps them to PINT AE, validates them and sends them to your ASP’s API. It works with any ERP, including older or customised systems, and stays ASP-agnostic. This is the route we usually build.
- ASP portal. Manual entry or file upload into the ASP’s web portal. Only realistic for very low volumes.
A typical connector does six things: extract, map, pre-validate, submit, write back status, and (optionally) receive inbound invoices. You can read more in our guide to integrating e-invoicing with an existing ERP.
UAE e-invoicing readiness checklist
Use this list to judge where you stand:
- We know which phase applies to each of our UAE entities.
- We have listed every system that issues invoices (ERP, POS, branch tools, spreadsheets).
- Customer records have valid Tax Registration Numbers and addresses.
- Our tax codes are mapped to PINT AE tax categories, agreed with finance.
- We have sample invoices for every scenario we issue (standard, zero-rated, exempt, reverse charge, exports, credit notes).
- We have shortlisted or appointed an ASP and requested sandbox access.
- We know who will handle rejected invoices and how.
- We have a test plan and a go-live date with buffer before our phase deadline.
If you ticked fewer than half, start now. The longest tasks (data clean-up and mapping) don’t depend on the final go-live date. You can also take our free e-invoicing readiness check.
Common mistakes to avoid
- Waiting for the ASP to “handle everything”. The ASP transmits and reports. It can’t fix missing data in your ERP.
- Locking into one provider through the integration. If the connector is written against one ASP’s proprietary format, switching later is expensive.
- Testing only the happy path. Credit notes, exports and reverse-charge invoices fail most often.
- Ignoring inbound invoices. Receiving through Peppol is part of the model. Plan accounts payable too.
- Treating it as a one-off. Specifications and code lists will be updated. Budget for maintenance.
How does UAE e-invoicing compare with Saudi Arabia?
Many GCC groups operate in both countries and assume one solution will cover both. The models are different enough that it rarely works without design:
| Aspect | UAE | Saudi Arabia |
|---|---|---|
| Model | Peppol-based 5-corner exchange | Central clearance and reporting (FATOORA) |
| Your integration point | Your Accredited Service Provider | ZATCA’s APIs (directly or via a provider) |
| Format | PINT AE (UBL-based XML) | UBL 2.1 XML with ZATCA rules |
| Signing and QR | Handled in the Peppol/ASP process | Your solution signs with a CSID and creates a QR code |
| Initial scope | B2B and B2G | B2B, B2C and B2G for VAT-registered persons |
The good news is that the hardest part, getting clean and complete invoice data out of your ERP, is shared. A single canonical invoice layer can feed a UAE ASP and a ZATCA Phase 2 integration side by side.
How Co-Mate helps
We make your existing ERP UAE e-invoicing ready: field gap analysis against PINT AE, an ASP-agnostic connector, sandbox testing with your ASP, go-live support and monitoring. See our UAE e-invoicing integration service for details.