UAE E-Invoicing 2026: What Every VAT-Registered Business Must Do Now

UAE e-invoicing becomes mandatory in waves. Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and issue structured PINT AE XML invoices from 1 January 2027. Every other business follows by 1 July 2027, and government entities by 1 October 2027. A voluntary pilot opens 1 July 2026.

UAE e-invoicing is the biggest change to day-to-day business administration since VAT launched in 2018. Under Ministerial Decisions No. 243 and 244 of 2025 (issued late September 2025), every VAT-registered business in the UAE will eventually have to issue invoices in a structured digital format, transmitted in real time to the Federal Tax Authority (FTA) through an approved provider. Penalty exposure sits separately under Cabinet Decision No. 106 of 2025, published December 2025.

The pilot opens on 1 July 2026, mandatory compliance follows in waves through 2027, and the intra-group transition window runs all the way to 1 January 2029. This guide covers the UAE e-invoicing timeline, the PINT AE format requirements, who must comply, the penalty framework, and what UAE SMEs should be doing now — the short answer being more than most have started. Because the structured e-invoice builds on the same content a standard tax invoice must carry, our UAE tax invoice requirements guide is a useful companion read. If you would rather hand the readiness work to a specialist, our e-invoicing setup support in the UAE covers system review, master-data cleanup and ASP coordination end to end.

Every UAE einvoicing rule, and the article that sets it

Most coverage of this mandate repeats the same four dates without saying where any of them come from. Below is the whole framework with the instrument and article number against each line, so you can check any figure yourself rather than take our word for it. Every entry was verified against the published text on 3 August 2026.

Rule	The figure or date	Primary source
Revenue threshold that splits the two waves	AED 50,000,000	MD 244 of 2025, Art. 5(1)(a)–(b)
Pilot Programme commences	1 July 2026	MD 244 of 2025, Art. 3(4)
Voluntary adoption opens to anyone	1 July 2026	MD 244 of 2025, Art. 4
ASP appointment — revenue ≥ AED 50M	30 October 2026 (replaced 31 July 2026)	MD 66 of 2026, Art. 1
UAE e-invoicing go live date — revenue ≥ AED 50M	1 January 2027	MD 244 of 2025, Art. 5(1)(a)
ASP appointment — revenue < AED 50M	31 March 2027	MD 244 of 2025, Art. 5(1)(b)
Go-live — revenue < AED 50M	1 July 2027	MD 244 of 2025, Art. 5(1)(b)
Government entities — appoint, then go live	31 March 2027, then 1 October 2027	MD 244 of 2025, Art. 5(1)(c)
Intra-group grace inside one VAT group	24 months from 1 January 2027	Guidelines V1.1, §6.3.2.1
Window to transmit an invoice or credit note	14 days from the Date of Business Transaction	MD 243 of 2025, Art. 6(5)
Notify the FTA of a system failure	2 business days	MD 243 of 2025, Art. 12
Notify your ASP of changes to registered data	5 business days	MD 243 of 2025, Art. 5(3)
Where invoice records must be stored	Within the UAE	MD 243 of 2025, Art. 11
How long records must be kept	5 years; 7 years for real estate records	Guidelines V1.1, §5.4
How long real estate records must be kept for VAT	15 years after the end of the tax period	CD 52/2017 Art 71(2), as amended by CD 100/2024
How many ASPs you may appoint	Exactly one, covering both sending and receiving	Guidelines V1.1, §6.1
B2C transactions	Outside the system until the Minister decides otherwise	MD 244 of 2025, Art. 5(2)
Invoice format	XML only — no QR code, no barcode	Guidelines V1.1, §5.3

One line in that table deserves a health warning. Ministerial Decision No. 66 of 2026 clearly replaces the 31 July 2026 appointment deadline with 30 October 2026, but the Ministry’s own Electronic Invoicing Guidelines V1.1, dated 1 June 2026, still print the original date in their phased-implementation table. The later Decision is the operative law and the one every advisory firm is working to, yet the guidance has not caught up. If your appointment date falls in that window, confirm the current position with the Ministry or your ASP in writing rather than relying on either document alone.

The UAE e-invoicing mandate 2026 explained

The UAE e-invoicing mandate 2026 is the government’s move to structured, real-time tax invoicing, set out in Ministerial Decisions No. 243 and 244 of 2025. It does not switch on all at once. Twenty twenty-six is the preparation and pilot year — the phase where the framework, the PINT AE format and the Accredited Service Provider network all come into place before any business is pushed onto them.

Here is the point most owners miss: for the whole of 2026, participation stays voluntary. The mandate has a legal foundation and a published rollout, but no VAT-registered business is compelled to issue a structured e-invoice during 2026. The first hard obligation — appointing an ASP — lands on large taxpayers (revenue of AED 50 million or more) on 30 October 2026, with mandatory issuing from 1 January 2027.

So when you read “UAE e-invoicing mandate 2026”, read it as the year to get your data and systems ready, not the year you must be live. Treating 2026 as a runway rather than a cliff-edge is exactly what separates a calm transition from a scramble. Our e-invoicing setup advisory maps that runway onto your specific accounting stack.

Is there a UAE e-invoicing deadline in July 2026?

Yes and no — and it is worth clearing up, because “UAE e-invoicing deadline July 2026” is one of the most-searched phrases on the topic. There is a date in July 2026, but it is not a compliance deadline for the average business. 1 July 2026 is when the FTA’s pilot phase opens, and taking part is voluntary and limited to a selected Taxpayer Working Group.

The original rules did set 31 July 2026 as the deadline for large taxpayers to appoint their ASP. That date has since moved — a UAE e-invoicing deadline extension in everything but name. Ministerial Decision No. 66 of 2026 replaced paragraph (a) of clause (1) of Article 5 of Ministerial Decision 244 of 2025 in full, pushing the large-business ASP appointment deadline back to 30 October 2026 while leaving the 1 January 2027 go-live untouched. So if you were planning around a July 2026 cut-off, check the current text — the appointment window is now longer, not shorter. The e-invoicing deadline UAE businesses actually have to hit is the go-live date, and that has never moved.

For most SMEs, then, July 2026 carries no penalty and no obligation. It is the month to start testing, not the month to be finished. The real deadlines are 1 January 2027 for large businesses and 1 July 2027 for everyone else. For the receiving-side detail behind those dates, our UAE tax invoice format 2026 guide sets out what a valid structured invoice must contain.

The UAE e-invoicing timeline at a glance

If you want the UAE e-invoicing timeline in one breath: pilot in mid-2026, large businesses live at the start of 2027, everyone else by mid-2027, then a longer tail for government bodies and VAT groups. The einvoicing timelines in the UAE run in waves rather than as a single switch, and your own date depends on your revenue and entity type.

Read as a sequence, it goes like this. The pilot opens on 1 July 2026. Large taxpayers (AED 50 million or more) appoint an ASP by 30 October 2026 and issue structured invoices from 1 January 2027. Every other VAT-registered business appoints an ASP by 31 March 2027 and goes live by 1 July 2027. Government entities follow, live by 1 October 2027. Finally, invoices between members of the same UAE VAT group get a transition window running until 1 January 2029.

The wave-by-wave table further down sets each of these dates against who they affect. The one habit worth building now, wherever you sit on the timeline, is to work backwards from your own go-live date and give the data cleanup the months it genuinely needs. If you have not confirmed your VAT status yet, our VAT registration in the UAE guide is the place to start.

What e-invoicing actually changes

So what is e invoicing, stripped of the acronyms? It is issuing an invoice as structured data another system can read and validate on its own, instead of as a document a person has to open and re-key. You will see it written both ways — e-invoicing and e invoicing, einvoicing without the space — and they all describe the same thing.

UAE e-invoicing replaces the PDF-and-email workflow with a structured, machine-readable process. Electronic invoicing UAE rules mean that instead of sending your client a PDF invoice and filing a copy, your accounting system generates an XML file in the PINT AE (Peppol International UAE) format.

That file is transmitted through your Accredited Service Provider (ASP) to your client’s ASP and to the FTA at the same time.

The FTA gets a copy of every invoice as it’s issued. There is no more quarterly reporting gap where errors go unnoticed until the next VAT return. The system validates data against the FTA’s rules before the transaction is recorded. Mismatched TRNs, wrong VAT classifications and missing address fields are caught automatically.

PDFs, Word documents and Excel spreadsheets don’t qualify as valid e-invoices under the new rules. PINT AE XML is the only format the FTA accepts.

Einvoicing is not just a VAT-registered business problem

Here is the single most misread part of the framework. Almost every summary you will read frames this as a rule for VAT-registered businesses. The Ministry of Finance does not frame it that way. Chapter 6.1 of the Electronic Invoicing Guidelines says that all Persons who make a Business Transaction in the UAE are within scope “notwithstanding their VAT registration status”, and the guide’s own highlights repeat that Electronic Invoicing is mandatory regardless of VAT registration status unless a transaction is specifically excluded under Article 4 of Ministerial Decision 243 of 2025.

That has three consequences worth sitting with. If you are below the VAT registration threshold but still trading B2B, you are in scope on the same wave as everyone else under AED 50 million. If you are in scope but not registered for any UAE tax type, you must approach the FTA for a Tax Identification Number, because the TIN is what identifies you on the network — and the guidelines are explicit that even inside a tax group your TIN is the first ten digits of your own TRN, not the group representative’s. And if you have no place of residence in the UAE but are obliged to issue tax invoices under the VAT law, chapter 6.3.3 says those invoices have to take the form of Electronic Invoices too.

One more structural detail that catches finance teams during budgeting: you appoint exactly one Accredited Service Provider, and that single appointment has to cover both sending and receiving. There is no arrangement where you use one provider for sales invoices and a cheaper one for purchase invoices. If you are mapping this onto your ledger structure, our e-invoicing ERP mapping guide for the UAE chart of accounts walks through where the fields land.

Who actually has to comply

Business type	Current scope
VAT-registered business (B2B or B2G transactions)	In scope — mandatory by wave deadline
Government entities (B2B and B2G)	In scope — mandatory by 1 October 2027
B2C-only businesses (selling to individual consumers only)	Excluded from issuing e-invoices; must receive them from suppliers
Non-VAT-registered businesses	Not required to issue; may need FTA TIN to receive
Intra-group transactions within a UAE VAT group	In scope, with a 24-month grace period running from 1 January 2027 — compliance is deferred, not removed
Proforma invoices, quotations, internal purchase orders	Out of scope — continue in PDF/Excel workflow (see our proforma invoice UAE guide)

The practical reality: even businesses excluded from the issuing requirement will need accounting systems capable of receiving and processing PINT AE XML files. Their suppliers will be sending structured invoices rather than PDFs. Nearly every business in the UAE will be operationally affected.

The structured-invoice trail also makes the 5-year record-keeping requirement under UAE AML compliance materially easier to evidence — every transaction is timestamped, immutable, and FTA-traceable by default.

What the rules genuinely exclude, and what only looks excluded

Chapter 7 of the guidelines lists the exclusions, and the list is shorter than most business owners hope. Four categories sit outside the system.

Business transactions carried out by a government entity qualify only where all three conditions hold at once: the transaction is conducted by a government entity, in a sovereign capacity, and not in competition with the private sector. That mirrors the treatment those bodies already get under the VAT law.

Airlines get a carve-out with three limbs. International passenger transport provided by an airline where an electronic ticket is issued sits outside the system permanently, as do ancillary services supplied directly to the passenger where an electronic miscellaneous document is issued. International transport of goods by an airline against an airway bill is excluded too, but only temporarily — Article 4(1)(d) of Ministerial Decision 243 of 2025 caps it at twenty-four months from the date in Article 5 of Decision 244.

Financial services exempt from VAT under Article 42 of the VAT Executive Regulation are excluded, and so are those exempt services when supplied to non-resident customers as zero-rated exports under Article 31. The guidelines close the obvious loophole in the same breath: financial services that would be standard-rated if supplied to a resident stay in scope even when they qualify as zero-rated exports.

The fourth category is simply whatever the Minister adds later by further decision.

Now the ones that only look excluded. Being inside a VAT group does not take intra-group invoices out of scope — chapter 6.3.2.1 is explicit that the grace period “affects the timing of compliance only” and that on expiry the requirements apply in full. An investment holding company earning purely passive income is out of scope, but the moment it recharges management costs to a related party it has made a business transaction and has to register. And the administrative exceptions the FTA grants for ordinary tax invoices under the VAT Executive Regulation do not carry over to electronic invoices at all — if you rely on one of those today, assume it disappears.

The rollout, wave by wave

Date	Milestone	Who is affected
1 July 2026	Pilot phase opens — voluntary participation under FTA supervision	FTA-selected Taxpayer Working Group
30 October 2026	Deadline to appoint an ASP (moved from 31 July 2026 by Ministerial Decision No. 66 of 2026)	Businesses with revenue ≥ AED 50M
1 January 2027	Mandatory e-invoicing begins — go-live date confirmed unchanged	Businesses with revenue ≥ AED 50M
31 March 2027	Deadline to appoint an ASP	Businesses with revenue < AED 50M and government entities
1 July 2027	Mandatory e-invoicing — all remaining businesses	All VAT-registered B2B and B2G businesses
1 October 2027	Full mandatory compliance	All government entities
1 January 2029	End of intra-group transition period	Invoices between members of the same UAE VAT group

[[chart:einvoicing-rollout-timeline]]

Why you can’t transmit to the FTA without an Accredited Service Provider

You cannot transmit e-invoices directly to the FTA. You must use an Accredited Service Provider (ASP) — a technology company approved by the FTA to validate invoices against PINT AE rules and transmit them through the Peppol network.

The FTA runs this on a 5-corner Peppol model, and it’s easiest to follow as a chain. You are Corner 1: you create the invoice in your accounting system as PINT AE XML. Your ASP is Corner 2, validating that file against FTA rules and transmitting it over the Peppol network. On the other side, your buyer’s ASP is Corner 3, receiving the invoice and validating it again. Your client, Corner 4, gets the validated invoice landed in their own accounting system.

The FTA sits at Corner 5, picking up consolidated tax data from both ASPs at once, with no separate submission from you. If the network itself is what you want to understand — who runs it, how the underlying four-corner design works and how the UAE identifier is built — we cover that separately in our guide to Peppol e-invoicing explained.

The catch is that the chain only completes when both the supplier and the buyer are onboarded with an ASP. Your readiness depends partly on your clients’ and suppliers’ readiness too.

The four clocks that start on your go-live date

Once you are live, the mandate stops being a project and becomes a set of running deadlines. Four of them are written into Ministerial Decision 243 of 2025, and between them they generate most of the penalty exposure.

The first is the transmission window. Article 6(5) gives you fourteen days from the Date of Business Transaction to issue and transmit the electronic invoice or credit note through the system. That date is defined as the earlier of the date the transaction occurred or the date you received payment, so a prepayment starts the clock even when nothing has shipped. If you are VAT-registered, the shorter timeline in the VAT law sits on top of this rather than replacing it.

The second is the system-failure notice. Article 12 requires both issuer and recipient to notify the FTA of a system failure within two business days of it occurring. Two days is short enough that it needs an owner and a documented procedure before you go live, not a scramble on the day.

The third is the data-change notice. Article 5(3) gives you five business days from the FTA confirming an amendment to your registered details to tell your ASP in writing. Change of address, change of authorised signatory, change of trade name — all of it counts.

The fourth is retention. Article 11 requires the invoices, credit notes and associated data to be stored inside the UAE, and the guidelines set the period at five years following the relevant tax period for a taxable person, five years from the end of the calendar year of creation for everyone else, and seven years for real estate records. That last figure is the general Tax Procedures floor; for VAT purposes Article 71(2) of the VAT Executive Regulation holds real estate records for fifteen years after the end of the tax period. A dispute or an FTA audit adds four more years on top.

What missing those clocks costs, in arithmetic

Take a mid-sized trading company in its first full month of mandatory compliance. Its connector breaks mid-month. Sixty sales invoices never reach the recipient, twenty credit notes go the same way, and the finance team reports the outage to the FTA four days after it started rather than within two business days.

Running that through the schedule annexed to Cabinet Decision 106 of 2025:

• Sixty untransmitted electronic invoices at AED 100 each comes to AED 6,000, but the schedule caps that violation at AED 5,000 per calendar month, so the charge is AED 5,000.
• Twenty untransmitted electronic credit notes at AED 100 each is a separate violation with its own AED 5,000 monthly cap, so the full AED 2,000 applies.
• The late system-failure notification runs at AED 1,000 for each day of delay or part thereof. Four days of delay is AED 4,000.

That is AED 11,000 for one bad month, and none of it touches the underlying VAT position. The largest single line is the one nobody budgets for — the notification, not the invoices. A connector failure you report inside two business days costs nothing under row four of the schedule. The same failure reported a week later is where the money goes.

Every invoice now carries this data

Every invoice transmitted through the system must include all mandatory data fields specified in the Ministry of Finance’s UAE Electronic Invoicing Guidelines, version 1.1 dated 1 June 2026, which supersede the first operational guidance issued in February 2026. The core field categories are:

Data category	Required fields
Invoice details	Invoice number, date, type code, currency code, payment due date
Seller details	Seller name, electronic address (TIN), legal registration, TRN, address
Buyer details	Buyer name, electronic address, TRN where applicable, address
Document totals	Line net amounts, totals with and without tax, tax amounts, payable amount
Tax breakdown	Tax category code, rate, taxable amount, tax amount per category
Line item details	Line ID, quantity, unit of measure, item price, tax category, AED equivalents

Your Tax Identification Number (TIN) — the first 10 digits of your TRN — is your participant identifier on the Peppol network. If you are not registered for any UAE tax type, you must obtain a TIN from the FTA before your mandatory deadline. This applies even to VAT-exempt businesses that fall within scope. If you want a refresher on how to read and confirm a counterparty’s TRN, see our UAE TRN verification guide.

The PINT AE field map, in practical terms

The Peppol International Invoice (PINT AE) specification is the structured XML schema that every UAE e-invoice must follow. It builds on the global PINT base and layers UAE-specific fields on top — TRN, FTA tax category codes, AED-as-base-currency rules, and the FTA’s electronic address format.

Below is the practical field map every accounting team needs to validate against before going live.

Block	Required field	Notes for UAE preparers
Document type	Document type code	380 standard tax invoice, 381 credit note, 383 debit note, 384 corrected invoice
Document type	Invoice number	Unique and sequential per legal entity
Document type	Issue date	ISO 8601 (YYYY-MM-DD) — the FTA timestamps receipt independently
Document type	Due date	Required where payment terms apply
Currency	Document currency	Foreign-currency invoices permitted; AED equivalent at FTA-published rate is mandatory
Seller	Legal name	Must match trade licence exactly
Seller	TRN (15 digits)	Validated against the FTA register in real time
Seller	Electronic address (TIN-based Peppol ID)	First 10 digits of TRN + FTA-issued scheme identifier
Seller	Registered address	Building, street, area, emirate, country code (AE)
Seller	Contact email / phone	Required on the Peppol envelope
Buyer	Legal name + TRN where VAT-registered	Buyer-without-TRN paths only valid for the limited B2C carve-out
Buyer	Electronic address	Buyer must be onboarded with their own ASP to receive
Buyer	Delivery address (if different)	Used for place-of-supply determination
Line items	Line ID	Sequential per invoice
Line items	Item description + classification code	UNSPSC or similar where available
Line items	Quantity + unit of measure (UN/ECE Rec 20)	Reject codes are common where preparers use free text
Line items	Unit price + line net amount	Both in document currency and AED
Line items	VAT category code (S, Z, E, O) + rate	Standard, zero, exempt, out-of-scope — mis-coding is the most common rejection reason
Totals	Total net, total VAT, total gross, payable amount	Must reconcile to the sum of lines within rounding tolerance
Tax breakdown	VAT subtotal per category and rate	Required for every rate touched on the invoice
Payment	Payment terms + bank account (IBAN)	Mandatory when payment is on credit terms
Place of supply	Country of supply + emirate code	Drives FTA reporting allocation

That gives you the 21 core data blocks. Practically every UAE accounting platform — Zoho Books, Xero, QuickBooks Online, Tally, Odoo, SAP, Oracle NetSuite, Microsoft Dynamics 365 — will need configuration changes to produce all of these fields cleanly.

The two most common gaps we see in pre-pilot audits are missing unit-of-measure codes on service line items and missing VAT category codes on zero-rated exports. Easy enough to fix in master data. Genuinely painful to fix across 12,000 historical records with a deadline bearing down.

For the underlying invoice format requirements, our UAE tax invoice format 2026 guide and credit note UAE VAT format guide cover the document-level rules in detail.

Who is actually on the pre-approved ASP list for UAE einvoicing?

First, a correction to something you will see repeated across a lot of UAE e-invoicing coverage. Under Article 5(2) of Ministerial Decision 243 of 2025 the list of Accredited Service Providers is published by the Ministry of Finance, not the FTA. So the ASP list UAE businesses should be working from sits on mof.gov.ae. A good deal of published commentary names large international tax-technology brands as UAE pre-approved providers on the assumption that a global Peppol footprint carries over automatically. It does not. Accreditation here is a separate UAE process under Ministerial Decision No. 64 of 2025, and several very well-known names are not on the list.

Below is the list of ASP for e-invoicing in UAE exactly as published on the Ministry’s pre-approved register, checked on 3 August 2026, when it carried 42 entries. Names are given as they appear on the register, which is the form you will need when raising a purchase order.

#	Pre-approved provider	#	Pre-approved provider
1	Advintek Consulting Services LLC	22	KGRN Chartered Accountants
2	Azentio Software Orion (Middle East) FZ-LLC	23	Marmin AI Software Design LLC
3	BDO Digital Solutions FZ-LLC	24	Microvista Technologies LLC
4	Casim L.L.C-FZ	25	Moore JFC Consulting LLC
5	Comarch Middle East FZ LLC	26	New Age Software Limited
6	Complyance Electronics L.L.C	27	Orchida Soft Computer Systems LLC
7	Covoro AI – FZCO	28	Oxinus Holding Limited
8	Cygnet Digital IT Solutions L.L.C	29	Pagero Gulf FZ-LLC
9	Dariba Technologies LLC	30	SAP Middle East & North Africa LLC
10	Defmacro Software DMCC (ClearTax)	31	Skill Quotient Technologies
11	Deloitte & Touche - M E	32	Spendconsole FZ LLC
12	DP World Digital GCC FZE	33	SunTec (Xelerate) Business Solutions DMCC
13	EDICOM Middle East Services	34	Suntech Business Solutions DMCC
14	EY Consulting LLC	35	Tally Software Solutions FZCO
15	Flick Network L.L.C	36	TAXILLA FINOPS 360 – FZCO
16	Fynamics Techno Solutions – FZCO	37	Taxlabs.ai
17	Hamt Information Technology L.L.C (EVATRA)	38	Tax Star L.L.C-FZ
18	Infinite IT Solutions FZCO	39	Techventures Information Technology Services
19	Information Dynamics LLC	40	TronStride FZC
20	InvoiceNow biz - F.Z.C	41	Unified SSK Information Technology L.L.C
21	InvoiceQ For Information Technology Limited	42	VATit Consultant Gulf Ltd

Two things to take from that table. Of the Big Four, only Deloitte and EY appear in their own name, alongside BDO’s digital arm — so if your audit firm has told you it will handle your ASP layer, check the register before you assume it. And the register is a mix of established platform vendors, regional accounting-software houses and a number of newer UAE entities, which means brand recognition is a poor filter. Judge on the integration and support criteria in the next section instead.

Pre-approval is also not the finish line. Full accreditation under Ministerial Decision No. 64 of 2025 is what is required before production go-live, and it is being granted in stages. Always check the Ministry of Finance pre-approved provider register yourself before signing anything — it changed on the day we last checked it, and any list published in an article, including this one, is a snapshot.

Velmont Crest’s accounting practice’s position on the ASP question: we are not an Accredited Service Provider, and we will never be. Our role is to sit on your side of the table — review your accounting stack, audit your master data, shortlist ASPs that match your platform and invoice volume, negotiate pricing, and coordinate onboarding.

The ASP runs the pipes; we make sure your data flows through them cleanly.

Picking an ASP without regretting it

Once the FTA finalises its accredited list, the selection process should be driven by your accounting stack and invoice volume, not by brand recognition. Use this checklist when evaluating shortlisted ASPs.

Criterion	What to ask
Native accounting integration	Confirmed connector for your specific platform — Zoho Books, QuickBooks Online, Xero, Tally, Odoo, SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 BC / F&O — and your specific edition
Pricing model	Per-document, per-month tier, or annual flat — which is cheapest at your real volume, and how does it scale if you grow 2x?
Inbound Peppol support	Can you also receive supplier invoices through the same ASP? Receiving-side support is often overlooked and frequently sold separately
PINT AE certification status	Pre-approved vs fully accredited — and the vendor’s timeline for full accreditation
Multi-entity / multi-TRN support	Critical for group structures with several VAT-registered entities; some ASPs charge per entity
Sandbox availability	Can you run real-shape test invoices before mandatory go-live? Pilot-phase testing is the difference between calm Q1 2027 and chaos
SLA and uptime	Look for ≥99.5% uptime with documented FTA-failure notification workflow — the AED 1,000/day penalty for failure-notification gaps is real
Support quality	Arabic and English support hours, response SLAs, dedicated onboarding manager for the first 90 days
Data residency	Where invoice data is stored — UAE-resident storage simplifies record-keeping evidence under the Tax Procedures Law
Exit terms	Data portability if you change ASP — full PINT AE archive export in machine-readable form

The biggest mistake we see in ASP selection is optimising for headline price per invoice while ignoring integration depth. A 10 fils-cheaper-per-invoice ASP that needs custom middleware for your ERP will cost you AED 50,000 in integration work before you send a single invoice.

Start with platforms that natively integrate with your accounting stack. Then compare pricing inside that shortlist.

What it really costs

A word on what follows. The ranges below are third-party market estimates for software and ASP costs, not published tariffs and not Velmont Crest fees — no ASP publishes a standard UAE price list, so nobody can quote these as verified figures, and we are not going to pretend otherwise. Treat them as planning anchors for a budget conversation and get written quotes from shortlisted providers before you commit to a number. Every business has stack quirks that move it.

Business profile	Setup (one-off)	Ongoing (monthly)
Small SME — under AED 5M revenue, single entity, cloud accounting (Zoho Books, QuickBooks Online, Xero), under 200 invoices/month	AED 5,000 – 15,000	AED 200 – 500
Mid-SME — AED 5M – 50M revenue, 1–3 entities, mid-tier ERP (Tally Prime, Odoo, NetSuite Starter, Dynamics 365 BC), 200 – 1,500 invoices/month	AED 25,000 – 80,000	AED 1,000 – 3,000
Large SME / lower-mid-market — AED 50M+ revenue, multi-entity, complex ERP (SAP S/4HANA, Oracle NetSuite, Dynamics 365 F&O), 1,500+ invoices/month	AED 100,000 – 300,000	AED 3,000 – 10,000

What is actually inside those numbers:

• Setup costs typically cover: ASP onboarding fee, accounting-software upgrade or plan change, middleware or connector build, master-data cleanup (TRN, address, VAT-code audit), VAT classification review, internal process redesign, training, and parallel-running during pilot.
• Ongoing costs typically cover: ASP subscription or per-document fees, software upgrade tier, monthly reconciliation between issued and received invoices, and ad-hoc support for rejected invoices and FTA-failure notifications.

Two cost drivers tend to surprise finance leads. The first is receiving-side onboarding: most ASP quotes default to outbound only, so if you take in 400 supplier invoices a month, inbound processing can double your ongoing cost unless you negotiate it in. The second is multi-entity pricing. ASPs often charge per TRN rather than per group, which means a holding company with five operating subsidiaries is really five ASP relationships until you push for a master agreement.

If you want a sanity check on what your VAT exposure looks like under the new structured-invoice regime, our UAE VAT calculator gives a quick base-case for output and input VAT positions across the rate categories that PINT AE validates.

What the FTA can fine you for

Cabinet Decision No. 106 of 2025 (published December 2025) sets out the confirmed penalty schedule for UAE e-invoicing non-compliance. Penalties apply only once e-invoicing is mandatory for your business — from 1 January 2027 for large taxpayers, and 1 July 2027 for all other VAT-registered businesses. No penalties apply during the voluntary pilot phase:

#	Violation as worded in the annexed table	Penalty
1	Failure by the issuer to implement the system, including failing to appoint an ASP within the prescribed timeline	AED 5,000 for each month of delay or part thereof
2	Failure by the issuer to issue and transmit an electronic invoice to the recipient within the prescribed timeline	AED 100 per electronic invoice, up to AED 5,000 per calendar month
3	Failure by the issuer to issue and transmit an electronic credit note within the prescribed timeline	AED 100 per electronic credit note, up to AED 5,000 per calendar month
4	Failure by the issuer to notify the Authority of a system failure within the prescribed timeline	AED 1,000 for each day of delay or part thereof
5	Failure by the recipient to notify the Authority of a system failure within the prescribed timeline	AED 1,000 for each day of delay or part thereof
6	Failure by the issuer or recipient to notify the appointed ASP of changes to data registered with the Authority	AED 1,000 for each day of delay or part thereof

Those six rows are the complete schedule — there is no seventh. Two things follow that businesses tend to get wrong. The credit-note penalty in row 3 carries its own AED 5,000 monthly cap separate from the invoice cap in row 2, so a bad month can breach both. And rows 4 and 5 apply to each side independently, which means a buyer who fails to report the same outage is exposed on their own account even though the failure originated with the supplier.

Two further exposures sit outside this schedule rather than inside it. Incorrect or incomplete invoice data carries no fixed amount here, but the FTA will cross-reference the structured data against VAT and corporate tax returns and discrepancies can open an audit. Failing to keep e-invoice records inside the UAE breaches Article 11 of Ministerial Decision 243 of 2025 and is dealt with under the Tax Procedures Law rather than Cabinet Decision 106.

Beyond direct fines, the practical penalties are significant: clients on the new system may not be able to accept non-compliant invoices, rejected invoices delay payment, and the FTA will use e-invoicing data to cross-reference VAT returns and corporate tax filings. For context on how the FTA structures penalty frameworks across taxes, see our guide to UAE tax penalties 2026.

Cleanup now vs scrambling in June 2027

Consider a Dubai SME issuing 150 B2B invoices per month with a July 2027 mandatory deadline. The figures below are an illustrative model built to show the shape of the difference, not quoted prices from any provider.

Scenario A — proactive cleanup (starting now):

• Accountant spends 8 hours auditing customer/supplier TRN records: AED 1,200 one-off
• Software upgrade to PINT AE-compatible plan: AED 300/month (AED 3,600/year)
• ASP onboarding fee: AED 500 one-off; ongoing per-invoice fee approximately AED 0.50 = AED 900/year
• Total first-year cost: approximately AED 6,200 (AED 1,200 + AED 3,600 + AED 500 + AED 900)

Scenario B — last-minute compliance (scrambling in June 2027):

• Emergency data cleanup with incomplete supplier records (many are unresponsive): 3–4 weeks of internal time
• 40 invoices rejected in the first month — payments delayed by an average of 12 days each
• Two key clients request credit notes and reissuance: 8 hours of accountant time
• FTA notification penalty for one 3-day system failure during rushed onboarding: AED 3,000
• Total disruption cost: AED 8,000–15,000 (excluding opportunity cost of delayed receivables)

For a well-run business, preparing early isn’t really optional. It’s just the cheaper way through.

[[chart:einvoicing-compliance-cost]]

Where SMEs keep getting tripped up

The most common problem we run into is a TRN mismatch on supplier invoices, where the TRN on a supplier’s PDFs doesn’t match the one registered with the FTA. The PINT AE validation engine rejects those invoices outright, so you have to resolve the mismatches before they ever enter the system.

Then there are the B2C businesses that assume they’re fully exempt. Being off the hook for issuing e-invoices doesn’t mean your accounting system needs no upgrade — your suppliers will start sending you structured XML, and if your system can’t parse PINT AE files, you end up with no automated record of what they billed you.

A quieter trap is waiting for the ASP list to be finalised. The FTA keeps publishing its approved list as the pilot progresses, and some businesses are holding off on everything until it’s complete. That’s backwards: the data cleanup, the software review and the internal process mapping can all happen now, before you’ve picked a specific ASP.

Plenty of firms also assume their software will “just update.” Cloud providers like Zoho Books and QuickBooks will probably add PINT AE support, but not every version or pricing tier gets it, so check your specific plan rather than the platform in general. And don’t ignore the B2G angle. If any of your revenue comes from government contracts, you face the same deadlines as large B2B traders, and you should plan as though the large-business deadline applies to you.

For related record-keeping requirements that sit alongside e-invoicing compliance, see our overview of financial record-keeping obligations in the UAE.

How to prepare, step by step

Step 1: Audit your current invoicing setup

List every accounting system, invoicing tool or ERP you use. Contact each vendor and ask specifically: does this platform support PINT AE XML format and Peppol integration? What is your UAE e-invoicing roadmap and expected release date? Get written confirmation.

Step 2: Run a data quality audit

Export your full customer and supplier master data. For every record, verify: the TRN is accurate and matches the FTA register; the legal name matches the trade licence; the registered address is complete. Flag every mismatch for resolution. This step alone typically takes 2–4 weeks for businesses with 200+ counterparties.

Step 3: Resolve TRN and address mismatches

Contact suppliers and clients with incorrect or missing TRNs. Request updated trade licence copies and FTA TRN certificates. Update your master records. This cannot be done in a day — build in time for suppliers who are slow to respond.

Step 4: Review your VAT and corporate tax classifications

UAE e-invoicing requires accurate tax category codes on every line item. Review your VAT classifications — standard-rated, zero-rated, exempt — and ensure they are correctly coded in your system. Misclassifications that may have gone unnoticed in PDF invoices will be rejected by the PINT AE validation engine. If your business also files corporate tax, see our corporate tax UAE guide for context on how e-invoicing data will be used in CT cross-referencing.

Step 5: Plan your ASP selection and budget

Once the FTA publishes its approved ASP list, shortlist providers based on your invoice volume, your accounting software’s integration options, and per-invoice pricing. Build ASP costs into your 2026 and 2027 operating budgets. For most SMEs issuing under 500 invoices per month, ASP costs will be modest — but the selection and onboarding process takes time.

Step 6: Test before your deadline

Use the pilot phase (July 2026 onward) to test your full chain: invoice generation → ASP validation → Peppol transmission → buyer receipt. Identify and fix rejection errors during the pilot, not after your mandatory deadline has passed.

How Velmont Crest can help you land this

UAE e-invoicing isn’t a distant change. The pilot begins in months, and the first mandatory wave is half a year away. For businesses above AED 50 million, October 2026 is when ASP appointment must be complete, with mandatory compliance from January 2027.

For smaller businesses, the urgency is almost as high. Your largest clients will be on the new system from January 2027, and their ERPs will expect PINT AE invoices.

If you’re still sending PDFs, you’ll face payment delays and potential client loss before your own July 2027 deadline arrives.

Three things are worth doing now. Check your software vendor’s roadmap, run a TRN data audit, and budget for ASP costs. Most of the rest falls into place once those are moving.

If you are unsure where your current setup stands, Velmont Crest’s e-invoicing advisory service covers system review, data cleanup, VAT classification review and ASP coordination — the practical groundwork that determines whether your transition is smooth or disruptive.

For broader VAT compliance context alongside e-invoicing, see our VAT services in Dubai page and our article on VAT registration in the UAE.

Deep-Dive E-Invoicing Scenarios

Once the fundamentals above are clear, these scenario guides cover the invoice flows that trip up real implementations:

• Reverse-charge supplier flows under UAE e-invoicing — who issues what when the buyer accounts for the VAT
• Self-billing rules in the UAE e-invoicing framework — when the customer generates the invoice
• Summary invoice format requirements — consolidating multiple supplies into one e-invoice
• VAT-grouping invoice flows — issuing under a group TRN without breaking validation
• POS integration for retail e-invoicing — high-volume B2C reporting from the till
• Recharges and disbursements on e-invoices — the classification that decides whether VAT applies
• Arabic and bilingual e-invoice formats — what the PINT AE schema does and does not do with Arabic
• Zero-rated export invoices under e-invoicing — the tax category that gets mis-coded most often
• Multi-currency invoices and FX rates — which rate the AED equivalent has to use
• Phase 2 readiness for 2027 — what changes once the second wave goes live

If you need a compliant document today while your ASP onboarding is still in progress, our UAE tax invoice generator builds one to the current FTA field requirements, and the VAT deadline tracker keeps the filing dates alongside your e-invoicing milestones. Businesses trading in or out of a designated zone should also read our note on designated-zone VAT treatment, because the zone status drives the tax codes the validation engine checks.

---

Official references:

• Federal Tax Authority — UAE E-Invoicing Portal
• UAE Ministry of Finance — E-Invoicing Initiative
• Cabinet Decision No. 106 of 2025 — Violations and Penalties (PDF)
• Ministerial Decision No. 243 of 2025 — the Electronic Invoicing System (PDF)
• Ministerial Decision No. 244 of 2025 — Implementation of the Electronic Invoicing System (PDF)
• Ministerial Decision No. 66 of 2026 — amending Article 5 of Decision 244 of 2025 (PDF)
• UAE Electronic Invoicing Guidelines, version 1.1, 1 June 2026 (PDF)
• Peppol International Standard