E-invoicing is one of the biggest changes to how UAE businesses issue and receive invoices since VAT arrived in 2018. The UAE Ministry of Finance has announced a mandatory e-invoicing system for business-to-business (B2B) and business-to-government (B2G) transactions, with a phased rollout starting from 2026. For most companies, the ERP or accounting system will be at the center of the change.
This guide explains the model at a high level, what it means for your ERP data and processes, and the practical steps you can take now. It is not legal or tax advice. Requirements and timelines can change, so always check the latest guidance from the Ministry of Finance and the Federal Tax Authority (FTA), and consult your tax advisor on how the rules apply to your business.
What is changing
Today many UAE companies issue tax invoices as PDFs sent by email. Under e-invoicing, invoices are exchanged as structured electronic data in an agreed format, so the buyer's system can read them automatically and the relevant tax data is reported to the authorities. A PDF on its own is not an e-invoice in this sense.
The rollout is phased. The Ministry of Finance has announced the approach and is introducing it in stages, with different groups of businesses expected to come into scope at different times. Rather than relying on dates quoted in blogs or vendor marketing, check the latest timeline published by the Ministry of Finance and plan backwards from the date that applies to you.
The 5-corner model and PINT AE in plain English
The UAE has chosen a decentralized model often described as the "5-corner" model, built on the Peppol network and a UAE-specific data standard called PINT AE.
- Corner 1: the supplier creates the invoice in its ERP or accounting system.
- Corner 2: the supplier's Accredited Service Provider (ASP) validates the invoice, converts it to the required format and sends it across the network.
- Corner 3: the buyer's ASP receives the invoice and delivers it to the buyer.
- Corner 4: the buyer receives the structured invoice into its own system.
- Corner 5: the tax authority receives the relevant invoice data reported by the ASPs.
In practice this means your ERP does not usually talk to the government directly. It connects to an ASP, which handles validation, delivery and reporting. Your job is to make sure the ERP produces complete, accurate invoice data and can exchange it reliably with your chosen ASP.
PINT AE is the UAE's version of the Peppol International invoice specification. It defines the fields an invoice must contain and how they are structured. Some of these fields are already on your tax invoices today; others may be new or currently held only in free-text notes.
Why data readiness matters most
The technical connection to an ASP is usually the easier part. The harder part is the data. If customer records, item codes or tax settings are inconsistent, invoices will be rejected or need manual fixing, which defeats the purpose. Areas to review include:
- Customer and supplier master data: legal names, addresses, Tax Registration Numbers (TRNs) and any identifiers needed for the network, kept in proper fields rather than notes.
- Tax codes: correct mapping of standard-rated (5%), zero-rated, exempt and out-of-scope supplies, and reverse charge where relevant.
- Item and service data: clear descriptions, units of measure and classifications.
- Invoice numbering and document types: consistent sequences for invoices, credit notes and debit notes across entities and branches.
- Currency handling: AED values for foreign currency invoices and correct exchange rates.
- Payment terms and references: purchase order numbers and contract references your customers, especially government entities, may require.
Cleaning this data is also good housekeeping for VAT compliance in your ERP and corporate tax reporting, so the effort pays back beyond e-invoicing.
What your ERP needs to support
Most modern ERP platforms are working on e-invoicing features for the UAE, but readiness varies by product, edition and version. Questions to ask your vendor or partner:
- Can the system generate invoices in the PINT AE structure, or will it rely on the ASP to convert the data?
- Which ASPs does it integrate with, and is that through a standard connector or a custom API?
- How are rejections and status updates fed back into the ERP so finance can act on them?
- Can it receive e-invoices from suppliers and match them to purchase orders and goods receipts?
- How does it handle credit notes, multi-entity groups and invoices raised from other systems such as POS or billing platforms?
- Is your current version supported, or will you need an upgrade?
If you run several systems that create invoices, such as an e-commerce platform, a field service app and a separate accounting package, you will need a clear plan for how each one feeds the e-invoicing process. This is often a good moment to review your wider ERP integration setup.
Steps to prepare your business
- Confirm your scope and timeline. Check the latest Ministry of Finance announcements and confirm with your tax advisor when and how the requirements apply to each of your entities.
- Map your invoicing landscape. List every system and process that issues or receives invoices, including manual ones.
- Run a data gap review. Compare your current invoice data against the PINT AE requirements and list missing or inconsistent fields.
- Clean master data. Fix TRNs, addresses, tax codes and item data at the source in your ERP.
- Assess your ERP's readiness. Decide whether you can use built-in features, need an upgrade or need integration work.
- Select an ASP. Compare accredited providers on integration options, support, pricing model and fit with your ERP.
- Update processes and controls. Define who handles rejected invoices, how credit notes are approved and how incoming e-invoices are checked.
- Test end to end. Send and receive test invoices covering your main scenarios before your go-live date.
- Train your team. Finance, sales and procurement staff need to understand what changes in their daily work.
Common mistakes to avoid
- Waiting for the final deadline before looking at data quality.
- Treating e-invoicing as an IT-only project rather than a finance and operations change.
- Assuming your current ERP version will be updated automatically.
- Forgetting invoices created outside the main ERP.
- Building heavy custom code before the ASP and ERP vendor connectors are clear.
How we help
We configure ERP systems to support UAE compliance. For e-invoicing, that typically means a readiness review, master data cleanup, tax code mapping, ASP integration and testing on platforms such as Zoho, Odoo, ERPNext and Dynamics 365 Business Central. You can read more about our approach on our UAE e-invoicing ERP page. We work alongside your tax advisor, who remains responsible for interpreting the rules for your business.
