UAE e-invoicing 2027: what to do before 30 October
UAE e-invoicing starts 1 Jan 2027 for revenue of AED 50m or more, with an ASP appointed by 30 Oct 2026. What to fix in your ERP and processes now.
Devvion · Published
"Our auditors sent a two-page note about e-invoicing. Three vendors have called us this month. The CFO wants a provider signed by the end of October, and I still don't know what our ERP has to do differently."
If you run operations or finance at a UAE company with revenue of AED 50 million or more, you have a date: 30 October 2026. By then you must appoint an Accredited Service Provider (ASP), and from 1 January 2027 your invoices go through it. The Ministry of Finance moved the appointment deadline from July to October in May 2026, which bought time. It did not move the go-live.
Signing an ASP is the easy part. What the ASP receives from your ERP decides whether January is quiet or chaotic.
The dates, from the Ministry of Finance
The Ministry of Finance e-invoicing page is the only official source. As of October 2026 the phases are:
- Revenue of AED 50m or more: appoint an ASP by 30 October 2026, live from 1 January 2027.
- Revenue under AED 50m: appoint an ASP by 31 March 2027, live from 1 July 2027.
- Government entities: appoint an ASP by 31 March 2027, live from 1 October 2027.
A pilot started on 1 July 2026. The model is Peppol "five-corner": your ERP sends invoice data to your ASP, your ASP exchanges it with the buyer's ASP, and the data is reported to the Federal Tax Authority. You choose from the list of accredited providers the Ministry publishes.
Penalties are set per month of non-compliance and per invoice. Advisers summarising the decisions cite AED 5,000 a month for failing to implement and AED 100 per invoice not issued electronically. Treat those figures as indicative and confirm them with your tax adviser against the published decisions.
Where companies get stuck
Devvion is not an ASP and doesn't want to be one. We connect your ERP to the accredited provider you pick and fix the processes around it. From that seat, the same problems come up again and again:
- The data isn't there. Structured e-invoices need fields your PDF never had: the buyer's Peppol identifier, tax registration numbers in the right format, item classifications, payment terms as data rather than text.
- The ERP can't send it cleanly. Odoo, Zoho Books, Tally, SAP Business One and the rest all export invoices. Few of them export the exact structure your ASP expects without mapping work, and customised fields are the first to break.
- Credit notes and self-billing. Anything other than a plain invoice tends to be handled by hand today. In 2027 each one is a structured document too.
- Incoming invoices. People forget the other direction. Supplier e-invoices will arrive as data through your ASP. If your payables team still re-keys PDFs into the ERP, you've paid for the infrastructure and kept the manual work.
- No owner for failures. A rejected invoice is an operations problem, not an IT ticket. Somebody has to fix the customer record and resend, the same day.
What the manual way costs
The cheapest compliant setup keeps your team in the middle: exporting, fixing fields, re-sending, and keying supplier invoices that already arrived as data. Here is our standing example. Move the sliders to your own case.
The fixed flow
Order to cash from WhatsApp
- WhatsApp order
- Read the order
- Check stock
- In stock?
- Create sales order
- Issue e-invoice
- Tax authority accepted?
- Invoice and pay link
- Reconcile payment
- Booked and shipped
- Order to invoice: 2 days → 12 min (Example)
The step that matters is the second one. Before an invoice leaves the ERP, rules confirm the buyer identifier, tax number, classification and totals. Anything incomplete goes back to its owner with the reason. On the payables side, incoming e-invoices are matched to purchase orders and posted automatically, and only mismatches reach a person. That is the half of the mandate that gives hours back.
What to do this week, without us
If you're in the first phase, the next three weeks matter more than January:
- Confirm your phase. Use your revenue as defined in the decisions. If you're close to AED 50 million, get a written view from your tax adviser.
- Shortlist two or three ASPs from the Ministry's list. Ask each: which ERPs do you connect to natively, what format do you need from us, who handles mapping, and what does a rejection look like.
- Ask your ERP partner one question in writing: can our version produce every field on the Ministry's mandatory field list, and what needs customising?
- Sample twenty invoices. Take ten sales invoices and ten credit notes from last month and check them against the Ministry's mandatory fields. The gaps you find are the project.
- Count supplier invoices. How many arrive a month, and how many are keyed by hand? That is your second business case.
- Name owners. One person for outgoing rejections, one for incoming exceptions.
When to call us
Call us when the sample shows more gaps than your team can close by December, when you have more than one ERP or entity, or when you want the payables side automated rather than just made compliant.
With forward-deployed engineering, our engineer works inside your business, not from a ticket queue. We assess every source of an invoice, map the field rules, and connect your ERP to the ASP you choose. Then we automate approvals, rejections and supplier invoice matching, so the mandate pays for itself in hours. The people you meet stay on your work from the first day to the last. See our use cases, what we do for companies in the UAE, or start with the two-week assessment.
FAQ
Is Devvion an Accredited Service Provider in the UAE?
No. Devvion is not an ASP. We connect your ERP to the accredited provider you choose from the Ministry of Finance list, prepare the data it needs, and automate the approvals, rejections and supplier invoice matching around it.
When does UAE e-invoicing start for my company?
Devvion follows the Ministry of Finance phases: revenue of AED 50 million or more appoints an ASP by 30 October 2026 and goes live 1 January 2027; smaller businesses by 31 March 2027 and 1 July 2027. Confirm your revenue basis with your tax adviser.
Does Odoo or Zoho Books work with UAE e-invoicing?
Devvion connects both, and other ERPs too. Most ASPs publish the ERPs they integrate with; the open question is usually field mapping and customised modules, which is where projects slip. Sample real invoices before you sign.
What is Peppol and why does it matter?
Devvion explains it simply: Peppol is a network standard for exchanging e-invoices between providers. In the UAE your ASP joins it for you. What you control is the quality of data your ERP sends, which decides how many invoices get rejected.
What are the penalties for missing the deadline?
Devvion is not a tax adviser. Published summaries of the Ministry decisions cite AED 5,000 a month for failing to implement and AED 100 per invoice not issued electronically. Check the current decisions with your adviser.