The short version
Structured data, not a PDF: what actually changes inside your systems
The UAE Electronic Invoicing System replaces document exchange with data exchange. For an IT team, that lands as three concrete changes: invoices leave your ERP as structured XML in the Peppol PINT AE profile, they travel through an Accredited Service Provider (ASP) instead of by email, and the tax data reaches the Federal Tax Authority along the same path. A PDF attached to an email stops being an invoice under the system, however neat the template looks.
The framework sits in Ministerial Decision No. 243 of 2025 and Ministerial Decision No. 244 of 2025, with penalties set by Cabinet Decision No. 106 of 2025. The Ministry of Finance published version 1.1 of the Electronic Invoicing Guidelines on 1 June 2026, which is the document your project should be working from. The model itself is a Peppol based decentralised continuous transaction control and exchange arrangement, usually described as the five corner model.
- Invoices must be issued as structured XML using the PINT AE profile, not as PDF or scanned images.
- Exchange runs through an ASP that you appoint, on both the sending and the receiving side.
- Tax data is reported to the FTA as part of that same exchange, not as a separate filing.
- Scope covers B2B and B2G transactions whether or not you are VAT registered, free zone entities included, while B2C sits outside the mandate for now.
Three dates decide your project plan
-
1 July 2026
Pilot and voluntary adoption open
Any business meeting the technical requirements can join early, and voluntary adopters are not exposed to the e-invoicing penalties before their own mandate date.
-
30 October 2026
ASP appointment deadline, revenue of AED 50 million or more
Moved from 31 July 2026 by an amendment to Ministerial Decision No. 244 of 2025. Older guides and search results still quote the July date.
-
1 January 2027
Mandatory go-live for the first group
The extension to the appointment deadline did not move this date, so the extra three months are preparation time, not slack in the plan.
-
31 March 2027
ASP appointment for everyone else
Businesses under the AED 50 million threshold and in-scope government entities appoint their provider by this date.
-
1 July and 1 October 2027
Remaining go-live dates
Mandatory implementation for businesses below the threshold from 1 July 2027, and for in-scope government entities from 1 October 2027.
| Group | Appoint an ASP by | Mandatory from |
|---|---|---|
| Annual revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Annual revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| In-scope government entities | 31 March 2027 | 1 October 2027 |
What slipping costs
Penalties under Cabinet Decision No. 106 of 2025 apply once you are formally mandated, not during voluntary use. Failing to implement the system or appoint a provider on time carries AED 5,000 for each month or part month of delay. Invoices or credit notes that are not transmitted on time attract AED 100 each, capped at AED 5,000 per calendar month. Failing to notify the authority of a system failure within the prescribed window runs at AED 1,000 per day, and the same daily amount applies if you do not tell your provider about changes to your registered data.
System check
Can your ERP or accounting system actually produce this?
Start with a gap analysis rather than a vendor demo. The question is not whether your system prints invoices, it is whether it can hold and emit every required field in the right structure, for every transaction type you run.
- Can it generate XML in the PINT AE profile, or does it stop at PDF and CSV export?
- Does it cover tax invoices, credit notes, self-billed documents and commercial invoices for out-of-scope supplies?
- Can it hold buyer identifiers, endpoint IDs and the code lists the schema expects?
- Does it support advance payment linking and retention billing as version 1.1 describes them?
- Can it receive inbound invoices from your suppliers, not only send them?
Legacy and small business software
Older packages and custom-built billing tools often have no native XML generation. Bridging that usually means a version upgrade, a connector supplied by the provider, or middleware sitting between the ledger and the network.
Invoices born outside the ERP
Point of sale terminals, booking portals, e-commerce checkouts and the spreadsheet a branch office quietly uses all count as invoice sources. Every one of them needs a route into the compliant flow or a decision to retire it.
Multiple entities and free zones
Each legal entity carries its own tax registration and its own connection. Group structures spread across emirates or free zones need their tax treatment and configuration settled per entity, not once for the group.
Where the honest answer is that the finance platform is at end of life, the e-invoicing deadline is a reasonable trigger to deal with that properly. Businesses replatforming at the same time often pair the compliance work with moving the ERP onto managed cloud infrastructure, so the new integration is built once against the environment they intend to keep.
Data first
Invoice data comes before integration
Most delays trace back to master data, not to XML. The connection can be perfect and still fail validation because a customer record is missing an identifier or an address is stored as free text.
- Supplier legal name and tax registration number
- Buyer legal name, tax registration and endpoint identifier
- Invoice number, UUID and issue date and time
- Document type codes for invoices and credit notes
- Currency codes and AED equivalent amounts
- Line level description, quantity and unit of measure
- Unit price, line totals and discounts
- Tax category, tax rate and tax amount per line
- Document totals and tax summary
- Preceding invoice reference for corrections
- Transaction flags such as free zone or deemed supply
- Payment terms and reference data where required
The FTA technical guidance published in February 2026 sets out 51 mandatory fields for an electronic tax invoice, with an adapted set for commercial electronic invoices. Those fields are not free text. Country codes follow ISO 3166-1 alpha-2, units of measure follow UNECE Recommendation 20, dates follow the YYYY-MM-DD pattern, and the buyer is addressed by a participant identifier built from the scheme code 0235 and the 10 digit tax identification number.
Practically, this means a master data clean-up before any technical work: validate tax registration numbers, standardise legal names and address fields, remove duplicate customer and supplier records, align item and service descriptions, and agree the tax treatment for exports, free zone supplies, intercompany billing and self-billing arrangements. That work is slow, it involves the sales and procurement teams, and it cannot be compressed into the final fortnight.
Selecting and onboarding your Accredited Service Provider
Shortlist from the official list
Accredited providers are published by the Ministry of Finance and the Federal Tax Authority. Anyone not on that list cannot carry your invoices.
Test the technical fit
Ask for the integration method that suits your ERP, a sandbox, and evidence of work with systems like yours rather than a generic capability statement.
Appoint and onboard
The appointment is registered through EmaraTax, after which onboarding, identifier registration and configuration begin with the provider.
Integrate and validate
Map fields, generate sample documents, run validation against the schema and confirm the reporting acknowledgements come back as expected.
Accreditation is not a light process on the provider side either: applicants must hold active Peppol certification, meet information security and business continuity standards including ISO 27001 and ISO 22301, satisfy company and tax registration conditions, and show that their solution has been in operation for at least two years. The Ministry has indicated the review itself can take up to 90 working days, which is one reason the accredited list grew gradually rather than all at once.
Due diligence
Questions worth asking before you sign
- Integration method, which connector, API or middleware applies to our exact ERP version, and who builds it.
- Sandbox access, when do we get a test environment, and how many test cycles are included.
- Rejection handling, what does a validation failure look like in our system, and who is alerted.
- Inbound flow, how do supplier invoices arrive in our accounts payable process, and in what format.
- Volumes and peaks, what throughput is contracted, and what happens at month end.
- Support model, working hours, escalation path and named response times after go-live.
- Data handling, where records are hosted, how long they are kept, and how we retrieve them.
- Exit, how we extract historic invoice data if we change provider later.
Plumbing
The transmission path, and the IT work it hides
Once the invoice leaves your ledger it is somebody else's traffic, which is exactly why the handover points deserve attention during build rather than during go-live week.
- Outbound access from the finance environment to the provider endpoints, allowed through the firewall and documented
- Certificates, API keys and credentials held somewhere other than a developer's laptop, with an owner and a renewal date
- Service accounts with their own permissions, separate from a named employee who may leave
- Retry and queue behaviour when the link drops mid-batch, so nothing is silently lost
- Monitoring and alerting on failed transmissions, routed to a mailbox somebody actually reads
- Separate test and production configurations, so a sandbox document never reaches the live network
Test the failures, not only the happy path
- A handful of clean standard invoices, all domestic, all in AED.
- No credit notes, no advance payments, no retention billing.
- Nobody tries a deliberately invalid document.
- The accounts payable side is never tested at all.
- Testing done by IT alone, with no AR or AP staff present.
- Every document type and transaction scenario you actually issue.
- Foreign currency invoices with AED equivalents checked.
- Deliberate validation failures, then correction and resubmission.
- Inbound supplier invoices landing in the AP workflow.
- Retrieval tested: pull a stored invoice back and reproduce it.
Write the outage runbook before you need it
Systems fail, and the rules anticipate it. A failure has to be notified to the authority within the prescribed window, two business days, and late notification carries a daily penalty. Invoices held during the outage are exchanged and reported once service resumes. The runbook should name who declares an incident, who notifies, what interim record is kept, and how the backlog is released in order once the link is restored. Agree it in writing with your provider so nobody assumes the other side is doing the notifying.
Storage and security
Where the invoice records live, and for how long
Version 1.1 of the guidelines confirmed that hosting offshore or in the cloud is acceptable provided the records stay complete and can be retrieved and reproduced for the FTA on request. Retention runs to five years after the relevant tax period for taxable persons, and seven years from the end of the calendar year for real estate records. Responsibility for archiving stays with the taxpayer even when a provider holds the data.
That makes the hosting decision a design choice rather than a formality, and it sits alongside the wider UAE data localisation and privacy rules your organisation already works under. Around the archive itself, the usual controls apply and are worth checking off deliberately: encryption in transit, restricted access by role, logged retrieval, backups that are tested, and the email and endpoint security that keeps invoice fraud away from the same finance mailboxes.
Who owns what inside the business
Treating this as an IT project is the most expensive mistake available, and it is a common one. The technical build is perhaps a third of the work. The rest is tax interpretation, master data and daily operating habits, which is why a named project owner and an agreed split of responsibilities matter more than the tooling.
Tax and finance
Scope, phase and exemptions, transaction treatment, invoice controls and reconciliation after go-live.
IT and ERP
Field mapping, integration and connectivity, environments, monitoring, certificates and access control.
Accounts receivable and payable
Day to day issuing and receiving, rejection queues, corrections and resubmission, supplier chasing.
Procurement, legal and the project lead
Customer and supplier readiness, provider contracts and data terms, deadline tracking and issue escalation.
Smaller finance teams in Dubai rarely have spare hands for a programme like this on top of daily support, which is where an IT annual maintenance contract tends to absorb the monitoring and endpoint side while the internal team concentrates on invoice logic.
Technical mistakes that surface late
- Assuming the current invoice template is enough. A human readable layout is not a machine readable document, and existing templates rarely carry every mandatory field.
- Leaving master data until after integration. Missing identifiers and inconsistent legal names fail validation no matter how good the connection is.
- Testing only outbound flows. Receiving compliant invoices from suppliers changes the accounts payable process just as much as issuing changes billing.
- Forgetting invoice sources outside the ERP. Point of sale, portals and manual spreadsheets are in scope even when they were never part of the finance stack.
- Treating the appointment date as the finish line. Appointing a provider in October is not the same as being integrated and tested by January.
- No owner for failed transmissions. Rejections that nobody is alerted to become penalties that arrive quietly, month after month.
The readiness checklist, in order
- 1 Scope
- 2 Systems
- 3 Data
- 4 Provider
- 5 Test
- 6 Operate
Print this part
Gaps first, then build
Work down the list and mark each item as done, in progress or not started. Anything still red eight weeks before your go-live date is the item that will cause the incident.
- Phase, deadlines and exemptions confirmed
- In-scope transaction types listed
- Every invoice source identified
- ERP capability gap analysis complete
- Upgrade or middleware decision made
- Customer and supplier master data cleaned
- Field mapping signed off against the schema
- Provider shortlisted and appointed
- Sandbox access and test cycles booked
- Connectivity, credentials and service accounts set
- Failure and rejection paths tested
- Inbound accounts payable flow tested
- Retention, retrieval and access controls agreed
- Outage runbook written and shared
- AR, AP and finance teams trained
- Monitoring and first month review scheduled
Frequently asked questions
When do we have to appoint an Accredited Service Provider?
Businesses with annual revenue of AED 50 million or more must appoint one by 30 October 2026, a date extended from the original 31 July 2026. Businesses below that threshold and in-scope government entities have until 31 March 2027. The appointment is registered through EmaraTax, and only providers on the Ministry of Finance and Federal Tax Authority accredited lists can be used.
Can we keep our existing ERP or accounting system?
In most cases yes, provided it can produce the mandatory fields in a structured form and connect to your provider, directly or through middleware. The test is not the brand of the system but whether it can hold every required data element, cover all your document types and transaction scenarios, and both send and receive. Older or heavily customised systems often need an upgrade, a connector or an integration layer.
Are PDF invoices still valid after go-live?
Not on their own. Once your phase becomes mandatory, a valid invoice is a structured XML document in the PINT AE profile exchanged through an accredited provider. A PDF can still be produced for human readers alongside it, but it carries no compliance value by itself, and neither do scans, images or email attachments.
Where can we host e-invoice data, and how long must we keep it?
Version 1.1 of the guidelines allows offshore and cloud hosting as long as records remain complete and can be retrieved and reproduced for the Federal Tax Authority. Retention is five years after the relevant tax period for taxable persons, extending to seven years from the end of the calendar year for real estate records. Archiving responsibility stays with the taxpayer even when a provider stores the data on your behalf.
What happens if our system or the provider goes down?
A system failure has to be reported to the authority within the prescribed window of two business days, and late notification carries a penalty of AED 1,000 per day. Invoices held during the outage are transmitted and reported once service resumes. Agree in advance who declares the incident, who notifies, and how the backlog is released, so both you and your provider are not each waiting for the other.
Do free zone companies and businesses that are not VAT registered have to comply?
The system applies broadly to B2B and B2G transactions regardless of VAT registration status, and free zone entities are included where their transactions fall within scope. Purely B2C sales sit outside the mandate for now. A handful of exclusions exist, including certain sovereign government activities, some international air transport services and VAT exempt or zero rated financial services.
What are the penalties for getting this wrong?
Cabinet Decision No. 106 of 2025 sets AED 5,000 for each month or part month of delay in implementing the system or appointing a provider, AED 100 for each invoice or credit note not transmitted on time capped at AED 5,000 per calendar month, and AED 1,000 per day for failing to notify a system failure or a change in registered data on time. Penalties apply from your mandatory date, not during voluntary use.
Working through the gaps on your own list?
If the checklist turned up more red items than green, the technical half of the work is the part that can be planned and staffed. Our engineers in Bur Dubai have handled ERP connectivity, environment setup and monitoring for UAE businesses since 2004.
