UAE e-invoicing 2027: what every business has to do

The UAE is phasing e-invoicing in by business size. Businesses with annual revenue of AED 50 million or more go live on 1 January 2027, and all remaining in-scope businesses — including small and medium businesses, and businesses that are not registered for VAT — go live on 1 July 2027. Business-to-government invoicing follows on 1 October 2027. A voluntary pilot phase has been running since 1 July 2026.

PINT AE is the UAE's Peppol International Invoice specification — the technical format a UAE e-invoice must take. It is a structured UBL 2.1 XML document with a defined set of mandatory fields covering the seller and buyer identifiers, addresses, invoice lines, tax categories, payment details and totals. Once the mandate applies to you, a PDF or paper invoice no longer counts as a valid tax invoice for B2B supplies.

An ASP is a provider accredited by the UAE Ministry of Finance to transmit e-invoices over the Peppol network and report them to the FTA. Every in-scope business must appoint one — the obligation sits with the taxpayer, not the software vendor. Your accounting or ERP system connects to your chosen ASP, which converts, validates, exchanges and reports the invoice.

The UAE has set administrative penalties for e-invoicing failures, including a monthly penalty for failing to implement the system or appoint a service provider, a per-invoice penalty for invoices not issued or transmitted on time, and daily penalties for failing to report system failures or update registered data within the required window. Reported figures start at AED 5,000 per month for non-implementation.

Not yet — and we would rather say so plainly. AmalERP issues VAT-compliant tax invoices with TRN today, and PINT AE support through an Accredited Service Provider is on our roadmap ahead of the 1 July 2027 SME deadline. The practical implication is that businesses adopting AmalERP now get their books, customer data and invoicing in order first, which is the work that has to happen regardless of which system you end up transmitting through.

No. Accreditation is a separate regulated role with its own requirements — including a UAE-registered entity, information-security certifications, Peppol access point certification and prior e-invoicing operating experience. Accounting and ERP vendors normally integrate with one or more existing ASPs by API rather than becoming one, which is the approach AmalERP is taking.

Yes. Free zone companies are in scope of the UAE e-invoicing framework, so a company in DMCC, JAFZA, IFZA or any other free zone follows the same wave deadlines as a mainland company of the same size.

Business-to-consumer invoicing is excluded from the mandate at this stage, so a pure retail business is not required to issue e-invoices to shoppers. However, most businesses also buy from suppliers and issue at least some B2B invoices, and scope can be extended over time — so it is worth being on software that will handle it either way.

Saudi Arabia uses a clearance model for B2B: invoices are cleared by ZATCA before they are considered valid, and Arabic is mandatory on the invoice. The UAE has taken a Peppol-based exchange-and-report approach instead — invoices flow between Accredited Service Providers and are reported to the FTA, without pre-clearance. If you operate in both markets, expect two different integrations rather than one.

Yes. Transmission does not replace record-keeping. UAE tax records must generally be retained for at least five years, and the structured e-invoice files themselves are expected to be retained and retrievable on request. In practice this is handled between your service provider's archive and your own accounting system — confirm who is storing what before you sign with an ASP.

For most users, very little changes on screen: you raise the invoice in your accounting system as you do now. What changes underneath is that the system produces a structured file and hands it to your service provider instead of you emailing a PDF. The visible impact is stricter data requirements — a missing buyer tax number or an incomplete address that you could previously ignore will now block an invoice.

In a five-corner Peppol model your invoice is delivered to your customer's Accredited Service Provider, and each in-scope business is required to appoint one — so by the time the mandate applies to both of you, the receiving side should exist. During the transition, businesses in an earlier wave will be issuing e-invoices to customers who are not yet in scope, which is expected and handled by the phased design.

Choose the accounting system first. The service provider is a transmission layer you can change, while your accounting system holds your ledger, your history and your team's habits — it is by far the harder thing to switch later. What matters is that whichever system you pick has a credible, dated plan to connect to an accredited provider before your wave goes live.