Questions we actually get asked

It's a Decentralised Continuous Transaction Control and Exchange (DCTCE) model with five parties: the supplier, the supplier's Accredited Service Provider, the buyer's Accredited Service Provider, the buyer, and the FTA, which receives a report of every transaction as it moves between access points.

Yes. The Ministry of Finance has clarified that free zone businesses — including DMCC, JAFZA, IFZA, RAKEZ, ADGM and DIFC entities — are in scope for e-invoicing, with no free zone exemption.

Cabinet Decision No. 106 of 2025 sets an administrative penalty of AED 5,000 per month for non-compliance, applied until the taxpayer implements a compliant e-invoicing system.

Not currently. The published framework covers B2B and B2G transactions. The Ministry may extend it to B2C through a separate decision in future, but nothing has been formally announced.

Structured XML using UBL or the UAE's PINT AE data dictionary, transmitted through an Accredited Service Provider. Scanned images, PDFs and paper invoices don't qualify as electronic tax invoices under the framework.

The FTA's semantic model published in February 2026 sets out 51 mandatory fields for electronic tax invoices, covering invoice details, seller information, and buyer information.

Yes, offshore and cloud data storage is permitted, provided records remain retrievable by the FTA on request.

API integration, SFTP, CSV/bulk upload, and point-of-sale connectors are all supported — you pick whichever fits your existing ERP or accounting stack without a migration.

It depends on ERP complexity and invoice volume, but a well-scoped integration is typically measurable in weeks rather than months — comfortably inside the ASP appointment window if you start now.

Yes. The system has been open for voluntary use since 1 July 2026, which gives your team a window to test the integration, fix data gaps, and reach the mandatory deadline with a system that's already proven in production.

Not necessarily. Our implementation team handles the PINT AE mapping and Peppol routing directly; your side mainly needs someone who knows your ERP's data structure.

Ongoing validation, routing, and archiving continue automatically. If the Ministry updates the technical schema or timeline, we update the validation engine on our side rather than asking you to re-integrate.