UAE e-invoicing deadlines 2026–2027 and penalties explained
The UAE's mandatory e-invoicing regime is no longer a distant prospect — the first hard deadlines land in late 2026 and go live at the start of 2027. If your business turns over AED 50 million or more, the clock is already running: you need an Accredited Service Provider (ASP) appointed before 30 October 2026 and structured invoices flowing from 1 January 2027. This article lays out the phased timeline, explains the AED 50 million threshold and who is caught first, walks through the technical model, and sets out exactly what the penalties are if you miss the mark.
In this article
The phased mandate at a glance
The UAE is rolling out e-invoicing in waves rather than switching everyone on at once. The Ministry of Finance has adopted a Peppol-based Continuous Transaction Control (CTC) model: instead of uploading invoices to a government portal, you exchange structured invoices through accredited providers that report the data to the tax authority in near real time. The transition runs from a voluntary pilot in mid-2026 into the first mandatory wave at the start of 2027, with smaller businesses phased in later that year.
Here is the timeline of milestones and dates you need to plan around:
| Date | Milestone | Who it affects |
|---|---|---|
| 29 Sep 2025 | First official pre-approved ASP list published by the MoF | All businesses (selecting a provider) |
| 1 Jul 2026 | Voluntary / pilot phase opens — early adopters can start issuing | Any business ready to test |
| 30 Oct 2026 | Deadline to appoint an Accredited Service Provider (ASP) | Businesses with revenue ≥ AED 50M |
| 1 Jan 2027 | Mandatory issuance goes live — first wave | Businesses with revenue ≥ AED 50M |
| During 2027 | Later phased go-live deadlines for the next revenue bands | Businesses below AED 50M |
The date that matters most is 30 October 2026. Mandatory issuance starts 1 January 2027, but you cannot issue a single compliant e-invoice until an ASP is appointed and integrated. Leaving the appointment to December leaves no time for onboarding, testing and cleaning your master data — treat 30 October as the real deadline, not 1 January.
The AED 50M revenue threshold and who's first
The order in which businesses are brought into the mandate is driven by size. The first mandatory wave captures businesses with annual revenue of AED 50 million or more. If you sit at or above that line, you are in Phase 1: appoint an ASP by 30 October 2026 and begin mandatory issuance from 1 January 2027.
Businesses below AED 50 million are not exempt — they simply have more runway. The Ministry of Finance is phasing the lower revenue bands in through later deadlines across 2027, so a business at, say, AED 10 million will have a go-live date after the first wave. The direction of travel is clear: e-invoicing will eventually apply to essentially all VAT-registered businesses, so even if your deadline is later, the readiness work is the same.
Because the threshold is based on revenue rather than headcount or profit, it is worth confirming exactly which figure applies to your entity — group structures, free-zone companies and businesses with fluctuating turnover should check their position early. Our full UAE e-invoicing guide goes deeper on how the phases interact with VAT registration.
Appointing an ASP — the 30 October 2026 date
Under the CTC model you do not send invoices directly to the government. Instead, e-invoices are transmitted through a Ministry of Finance-accredited service provider (ASP) that validates each invoice, delivers it to your customer over the Peppol network, and reports the data to the tax authority. Appointing an ASP is therefore not optional plumbing — it is the mechanism by which you comply at all.
For the first wave, the ASP must be appointed by 30 October 2026, ahead of mandatory issuance on 1 January 2027. Not every vendor qualifies. ASPs must meet an experience requirement under Article 15 of Ministerial Decision No. 64 of 2025 — their solution must have been in live operation for at least two years — and appear on the official pre-approved list the MoF maintains. The first list was published on 29 September 2025, and by mid-2026 roughly 41–42 providers had been pre-approved.
Choosing an ASP is a strategic decision, not a box-ticking exercise. The right provider integrates cleanly with your accounting system, handles PINT AE validation, and keeps a compliant archive — the wrong one becomes a bottleneck at your busiest time of year.
If you are weighing providers, our guide to choosing an ASP sets out the accreditation checks, integration questions and red flags to watch for. You can also track every milestone on the interactive UAE e-invoicing calendar.
What's in scope: B2B, B2G and B2C
Not every transaction has to become a structured e-invoice on day one. The mandate is scoped by the type of counterparty:
- B2B (business-to-business) — in scope and mandatory. Invoices between VAT-registered businesses must be issued as structured e-invoices through an ASP.
- B2G (business-to-government) — in scope and mandatory. Supplies to government entities are covered on the same basis as B2B.
- B2C (business-to-consumer) — currently out of scope. Sales to final consumers are not yet caught by the mandate, though this is expected to be revisited in future phases.
Don't assume B2C stays out forever. The current scope excludes sales to final consumers, but the framework is built to extend. Businesses with a mix of B2B and B2C should design their systems so that switching B2C into scope later is a configuration change, not a re-implementation.
The technical model: Peppol, PINT AE, 50 fields
The UAE has deliberately chosen an open, international model rather than a proprietary portal. Three pieces define it:
- Peppol CTC (the "5-corner" model) — invoices travel from your ASP, across the Peppol network, to your customer's ASP, with the tax authority receiving the reported data as a fifth corner. It is continuous transaction control because reporting happens as the invoice is exchanged, not in a monthly return.
- PINT AE — the UAE's country-specific version of the Peppol International (PINT) structured-invoice standard. It defines the exact format and semantics every compliant e-invoice must follow.
- Around 50 mandatory data fields — the Electronic Invoicing System (EIS) data dictionary specifies roughly 50 required fields, including buyer and seller TRNs, Participant Identifiers (for example
0235followed by a 10-digit TIN) and HS codes for goods.
The practical implication is that your invoice data has to be complete and clean before it can be transmitted. Missing HS codes, malformed TRNs or absent participant identifiers will cause invoices to fail validation. If you want the full breakdown of the standard, see our explainer on what Peppol and PINT AE are.
Penalties for non-compliance
The mandate has teeth. Once your go-live date passes, issuing an old-style PDF or paper invoice instead of a compliant structured e-invoice is a violation — as is failing to retain the underlying data. The headline penalties are:
| Violation | Penalty |
|---|---|
| Failure to issue a tax invoice / e-invoice or tax credit note within the required period | AED 2,500 per detected case |
| Failure to keep the required tax records and e-invoicing data | AED 10,000 per violation |
| Repeated record-keeping violation within 24 months | AED 20,000 |
The AED 2,500 figure is per case, which is what makes non-compliance dangerous: a business that issues hundreds or thousands of invoices a month can accumulate very large exposure quickly if its system is not producing compliant e-invoices. The record-keeping penalties compound the risk, because the structured invoice data itself is now part of what you are legally required to retain and reproduce on request.
What to do now to be ready
Whether your deadline is January 2027 or later in the year, the preparation is largely the same, and most of it takes longer than businesses expect:
- Confirm your phase. Establish whether your annual revenue puts you in the AED 50M first wave or a later 2027 band, and note your go-live date.
- Shortlist and appoint an ASP. Check the MoF pre-approved list, confirm the two-year experience requirement, and appoint before 30 October 2026 if you are in the first wave.
- Clean your master data. Validate customer and supplier TRNs, add Participant Identifiers, and populate HS codes on your item master — this is usually the biggest hidden task.
- Fix your invoice data at source. Make sure your accounting system captures all ~50 mandatory PINT AE fields on every invoice, not as an afterthought.
- Test in the voluntary window. Use the pilot phase from 1 July 2026 to run real invoices end-to-end before it becomes mandatory.
Booking time now against these steps is far cheaper than paying AED 2,500 per rejected invoice in January. If you want a structured way to work through them, grab the readiness checklist below.
How FinSanad gets you compliant through an ASP
FinSanad is built for exactly this transition. Because your invoices are already structured, VAT-computed and stored with a full audit trail, the move to PINT AE is a connection rather than a rebuild. FinSanad captures the mandatory EIS fields at the point of entry, validates TRNs and HS codes before an invoice is issued, and connects to an accredited ASP to transmit over the Peppol network — so a compliant e-invoice leaves your system the moment you post the sale.
- PINT AE-ready invoices with the ~50 mandatory fields captured and validated up front.
- ASP connectivity so invoices flow over Peppol without you managing the network yourself.
- Compliant archiving of both the invoice and its structured data, ready for the record-keeping rules.
- One system for VAT and e-invoicing — see how it fits together in our UAE e-invoicing guide.
The result: when your go-live date arrives, compliance is already running in the background. To see it on your own books and region, request a demo and we'll walk you through the whole flow.