UAE E-Invoicing: What Actually Has to Change in Your Systems

UAE e-invoicing stopped being a future problem this summer. The pilot opened on 1 July 2026, and the first hard deadline is now close: businesses turning over AED 50 million or more have to appoint an Accredited Service Provider by 30 October 2026, then issue e-invoices for real from 1 January 2027. Smaller businesses follow, but the work they will have to do is the same work, and most of it is not the part people expect.

We implement and connect the systems that will have to produce these invoices, so this is written from that side. We are not an Accredited Service Provider ourselves, because accreditation is granted by the Ministry of Finance. We do work with accredited providers and can put one in place for you. What we do either way is make sure your ERP, your accounting and your order flow can actually hand an ASP a clean, complete invoice, which is where almost all of the real effort sits.

What the UAE is actually building

This is not a portal you log into and type invoices. The UAE has adopted a decentralised model built on the Peppol network, usually described as a five-corner model. In practice it works like this: you send your invoice to your Accredited Service Provider, your ASP passes it across the network to your customer’s ASP, your customer receives it, and in parallel the tax data is reported to the Federal Tax Authority in near real time. The Ministry of Finance accredits the service providers; the FTA receives the data.

The format is fixed too. Invoices must follow PINT AE, the UAE profile of the Peppol International Invoice specification. That matters more than it sounds, because a specification defines exactly which fields must be present and what they must contain. A PDF is not an e-invoice. Neither is a scanned image, an emailed invoice, or a spreadsheet export. If a required field is missing or malformed, the document does not pass.

The dates, and who they apply to

The rollout is staged by revenue, and each stage has two dates that are easy to confuse: the date you must have an ASP appointed, and the date you must actually be issuing e-invoices.

Who	Appoint an ASP by	Issuing e-invoices from
Businesses with revenue of AED 50 million or more	30 October 2026	1 January 2027
Businesses below AED 50 million	31 March 2027	1 July 2027
Government entities	31 March 2027	1 October 2027

The pilot and voluntary phase has been running since 1 July 2026, which is worth using rather than ignoring. Going through the process while it is optional means discovering your data problems in a period where a rejected invoice is a lesson rather than a compliance failure.

These dates come from the Ministry of Finance framework as it stands. Guidance on this programme has been updated several times, so confirm the current position against the Ministry of Finance before you plan around a specific date.

What is in scope, and what is not

The mandate covers B2B and B2G transactions: domestic supplies between businesses in the UAE, and eligible cross-border transactions where a UAE tax invoice is required under the VAT rules. Sales to consumers are not included.

Currently outside the mandate:

B2C transactions
Government activity carried out in a sovereign capacity, where it is not competing with the private sector
International passenger air transport where an electronic ticket is issued
Ancillary airline services linked to passenger transport where an Electronic Miscellaneous Document is issued
International transport of goods by air where an airway bill is issued
Financial services that are VAT-exempt or zero-rated

Being out of scope for now is not the same as being finished. If you sell both to businesses and to consumers, you are in scope for part of your revenue, and your system still has to tell the two apart correctly and reliably.

The part that actually takes the time

Appointing an ASP is a procurement decision and it can be done in a few weeks. The work that overruns is getting your own data into a state where a structured invoice can be generated from it without a human patching the gaps. In every system we have looked at, the same problems come up.

Customer master data is incomplete. A structured invoice needs the buyer identified properly, including their Tax Registration Number, a real legal name and a usable address. Most customer databases have been filled in over years by different people under time pressure. Missing TRNs, trading names entered instead of legal names, and addresses typed into a single free-text box are normal, and every one of them is a rejected invoice later.

Tax treatment is applied by hand. If someone decides at invoicing time whether a line is standard-rated, zero-rated, exempt or out of scope, that judgement has to move into the system as a rule attached to the product or the customer. A specification cannot accept “the finance team knows”.

Invoices are assembled outside the system of record. Plenty of UAE businesses run their operations in one place and produce the actual invoice somewhere else, often in a spreadsheet or a document template. That gap is invisible today and fatal under e-invoicing, because there is no clean structured source to send.

Credit notes and corrections are informal. Adjustments made by editing an invoice, issuing a replacement, or agreeing something over email have to become proper tax credit notes that reference the original document.

None of this is exotic. It is the ordinary accumulated mess of a business that has been growing faster than its systems. But it is the reason a project that looks like “connect to a provider” turns into six months of data work if it is left late.

If you are on Odoo, or an ERP generally

A modern ERP already holds most of what PINT AE asks for, which puts you in a much better position than a business invoicing out of spreadsheets. The work is usually mapping rather than building: confirming that each required field exists, is mandatory at entry, and is populated with the right value rather than a placeholder. Then the connection to your ASP, and a tested path for credit notes and rejections.

The one thing worth insisting on is that the invoice is generated from the same system that holds the order and the payment. If your ERP issues the invoice but your gateway settlement lands somewhere else and your books are reconciled by hand, e-invoicing will expose that gap rather than solve it. Getting those three connected is the same problem we write about in payment reconciliation, and it is worth solving once for both reasons.

What to do in the next month

Work out which cohort you are in. Take your annual revenue against the AED 50 million line. That decides whether your ASP deadline is weeks away or next year.
Audit your customer master data. Count how many active B2B customers are missing a TRN, a legal name or a structured address. That number is your real project size.
Find where invoices are actually produced. Not where they are supposed to be produced. If the answer includes a spreadsheet, that is the first thing to fix.
Check your tax rules are in the system, not in someone’s head. Pick ten recent invoices with unusual treatment and see whether the system would have got them right unaided.
Shortlist an ASP. They must be accredited by the Ministry of Finance. The Ministry publishes a list of pre-approved providers, and that list is the only one that counts.
Use the voluntary phase. Send real invoices through the process while mistakes are still free.

Common questions

Is a PDF invoice a valid e-invoice in the UAE?

No. An e-invoice under the UAE framework is a structured data file in the PINT AE format, exchanged over the Peppol network through an Accredited Service Provider. A PDF, a scan or an emailed invoice document does not meet the requirement, even if the information on it is correct.

Do I have to replace my accounting system or ERP?

Usually not. Most modern systems, Odoo included, already hold the data the specification needs. The work is confirming the required fields are present and correctly populated, moving tax treatment into system rules, and connecting to an Accredited Service Provider. Businesses invoicing out of spreadsheets or a disconnected document template are the ones that need a real system first.

What is an ASP, and can Tijara Tech be ours?

An Accredited Service Provider is a company accredited by the Ministry of Finance to transmit invoices across the network and report the tax data to the FTA. We are not an ASP and cannot act as one, because accreditation is granted by the Ministry of Finance. We do work with accredited providers, so we can put one in place for you or connect you to the one you have already chosen, and either way we get your systems and data ready for it.

My revenue is under AED 50 million. Can I wait until 2027?

You can, but the deadline is not the constraint, your data is. The cleanup of customer records, tax rules and invoice generation takes the same amount of time whichever cohort you are in, and it is the part that cannot be rushed at the end. Starting during the voluntary phase costs you nothing and removes the risk.

What happens if an invoice is rejected?

It has to be corrected and resubmitted, which means someone has to notice, understand why, and fix it. This is why the failure handling matters as much as the happy path. A setup where rejections land in a queue nobody monitors will quietly turn into unbilled revenue and a VAT return that does not reconcile.

Does this apply to sales to consumers?

Not currently. The mandate covers B2B and B2G transactions. If you sell to both businesses and consumers, your system still has to distinguish them correctly, because the B2B share is in scope and has to be handled properly.

Working out what UAE e-invoicing means for your systems, or want the data cleanup scoped before the deadline gets close? Book a consultation and we will tell you honestly how much work is actually in front of you.