Compliance & Security Aug 24, 2026 • 12 min read

The timeline, with the dates that actually bind

Which two of these bind you depends on your revenue. The rest are context.

The Accredited Service Provider deadline was originally 31 July 2026 and was extended to 30 October 2026 by an amendment to Ministerial Decision No. 244 of 2025. Treat the extension as breathing room that has already been spent, not as evidence that further slippage is coming. The later dates follow the same phased schedule; confirm them against current Ministry of Finance and Federal Tax Authority guidance before you plan around them.

What the mandate actually requires

The most common misreading is that e-invoicing means emailing a PDF with a QR code on it. It does not. The UAE has adopted a five-corner Decentralised Continuous Transaction Control and Exchange model built on the Peppol network. In plain terms:

• You issue an invoice as structured XML conforming to the PINT AE schema — the UAE specification of the Peppol International Invoice.
• Your Accredited Service Provider transmits it across the network to your customer's provider.
• Reporting to the tax authority happens as part of that exchange, rather than as a separate filing you remember to do.

The consequence is that the invoice becomes machine-readable data rather than a document. A field that is missing, mistyped or coded wrongly is no longer a cosmetic problem that a human reader would forgive — it is a rejected transaction.

FTA e-invoicing, Peppol and PINT AE: what each term means

Vendor material uses these three terms almost interchangeably. They are different layers of the same system:

• FTA e-invoicing is the mandate itself: the requirement, set by Ministry of Finance decisions and administered by the Federal Tax Authority, for in-scope businesses to issue and report B2B and B2G invoices electronically as structured data.
• Peppol is the network the invoices travel on. The UAE adopted it instead of building a central government clearance platform, so your invoice moves from your Accredited Service Provider to your customer's, and the data is reported to the authority as part of that exchange.
• PINT AE is the data specification each invoice must follow on that network: the UAE version of the Peppol International Invoice, with the fields, codes and rules the UAE requires.

Put simply: the mandate decides that you must comply, Peppol decides how invoices move, and PINT AE decides what each invoice must contain. Your ERP owns the data, your Accredited Service Provider owns the transmission, and your finance team owns the obligation.

Who is in scope, and who is not

The mandate covers B2B and B2G transactions. B2C is outside the initial scope. Ministerial Decision No. 243 of 2025 sets out specific exclusions, including:

• Activities carried out by government entities in a sovereign capacity, where they are not competing with the private sector.
• International passenger air transport services where an electronic ticket is issued.
• Ancillary airline services covered by an Electronic Miscellaneous Document.

Scope questions get expensive when they are assumed rather than checked. If a meaningful share of your revenue sits near one of these boundaries, confirm the treatment with your tax adviser before you design anything around it.

Your ERP is not your Accredited Service Provider

This is the single most important thing to understand before you talk to any vendor, and it is where money gets wasted.

Your ERP produces the invoice data. An Accredited Service Provider is a separately accredited party that transmits that data across the network and handles reporting. You need both. Accreditation is not a formality: a provider must be Peppol-certified and, under the criteria set out in 2026, must have had its solution in operation for at least two years. ERP vendors are not accredited by virtue of being ERP vendors.

So when a supplier tells you their software "makes you compliant", the useful follow-up is: are you an Accredited Service Provider, or do you integrate to one? Both answers are fine. Only one of them is what they said.

What actually breaks: audit this before you buy anything

In every implementation we have seen, the integration is the small part. The data is the large part. Structured invoicing exposes every shortcut your finance team has been quietly absorbing for years, because a human could read around them and a schema cannot.

Run this audit first. It takes days, not weeks, and it tells you whether your remaining months go into clean-up or into integration:

• Customer TRNs. How many B2B customers have no tax registration number recorded, or one that fails a format check? This is usually the largest single gap.
• Item master discipline. Do items carry consistent codes, descriptions and units of measure — or does the same product exist three times because three people created it?
• Tax codes per line. Standard-rated, zero-rated, exempt and out-of-scope supplies must be distinguishable at line level, not decided by whoever raises the invoice.
• Invoices raised outside the system. Every invoice produced in a spreadsheet or a Word template is an invoice that cannot be transmitted. Count them honestly.
• Credit notes and corrections. A structured system needs a proper referenced credit note, not an amended reprint of the original.
• Multi-entity and multi-currency. If you invoice from more than one legal entity, each needs its own registration details carried correctly on every document.

The output of that audit is the only reliable input to a budget. Anyone quoting you a figure before it exists is guessing.

What to do in the time remaining

• Now. Run the data audit above. Establish whether you are above or below the AED 50 million threshold, because it decides which deadline is yours.
• In parallel, not after. Shortlist Accredited Service Providers. The 30 October 2026 appointment deadline does not wait for your clean-up to finish.
• Then. Fix the master data, close the off-system invoicing routes, and map your ERP output to the schema.
• Before go-live. Test through the voluntary phase rather than discovering rejections on live customer invoices in January.

Where ERPNext fits

ERPNext holds the structured transaction data the schema depends on, and because it is open-source, the item master, tax templates and customer records can be extended with the fields PINT AE expects, then mapped to your Accredited Service Provider's interface. There are no per-user licence fees, which matters when compliance work suddenly requires more people to touch the system.

We will say the same thing here that we would say in the room: the ERP is not the accreditation, and most of the work is data quality rather than integration. If your books are clean, this is a project of weeks. If they are not, no software shortens it.

For related reading, see our UAE VAT compliance guide, our ERPNext implementation cost guide, our UAE implementation service, and, if you are also choosing a system, our comparisons of NetSuite alternatives for UAE businesses and ERPNext vs SAP costs. Groups operating across the Gulf should also read how the requirement differs in Saudi Arabia, Bahrain and Qatar.

This guide is general information, not tax advice. Confirm how the rules apply to your business with your tax adviser or against current Federal Tax Authority and Ministry of Finance guidance. Last reviewed 14 September 2026.

Frequently asked questions

When does UAE e-invoicing actually become mandatory?

For large businesses — those with revenue of AED 50 million or more — mandatory e-invoicing and reporting begins on 1 January 2027. Before that, those businesses must appoint an Accredited Service Provider by 30 October 2026, a deadline extended from the original 31 July 2026. The pilot and voluntary phase opened on 1 July 2026. Businesses below the threshold must appoint a provider by 31 March 2027 and go live on 1 July 2027, and government entities go live on 1 October 2027.

What is PINT AE and why does it matter more than the deadline?

PINT AE is the UAE's national specification of the Peppol International Invoice — the data schema your invoices must conform to. It matters more than the deadline because it is the part you cannot fix at the last minute. The mandate is not satisfied by emailing a PDF or attaching a QR code; it requires structured XML in which every required field is present, correctly typed and correctly coded. If your item master, tax codes or customer TRNs are incomplete today, no service provider can invent that data for you in December.

Is my ERP the same thing as an Accredited Service Provider?

No, and this is the most common and most expensive misunderstanding. Your ERP produces the invoice data. An Accredited Service Provider is a separately accredited party that transmits it across the Peppol network and reports to the tax authority. You need both. Accreditation requires the provider to be Peppol-certified and to have operated its solution for at least two years, so ERP vendors are not automatically accredited. Treat any vendor claiming their ERP alone makes you compliant with real caution.

Which transactions are actually in scope?

The mandate covers B2B and B2G transactions. B2C is outside the initial scope. Ministerial Decision No. 243 of 2025 also sets out specific exclusions, including activities conducted by government entities in a sovereign capacity where they are not competing with the private sector, international passenger air transport where an electronic ticket is issued, and ancillary airline services covered by an Electronic Miscellaneous Document. Confirm how the exclusions apply to your own transaction types with your tax adviser rather than assuming.

How does the UAE model differ from Saudi Arabia's ZATCA system?

Saudi Arabia's Fatoora model routes invoices through a central government platform for clearance. The UAE has taken a decentralised route: a five-corner Decentralised Continuous Transaction Control and Exchange model built on the Peppol network, where accredited providers exchange invoices between trading partners and report to the authority. The practical difference for a group operating in both countries is that one ERP has to satisfy two genuinely different architectures, which is an argument for keeping the invoice data clean and standards-based in one system rather than bolting on a country-specific workaround.

What happens if we are not ready in time?

Non-compliance carries financial penalties, with figures in the region of AED 5,000 per month cited for certain violations — confirm the current schedule against Federal Tax Authority guidance, as the framework is still being detailed. The larger practical risk is commercial rather than punitive: if your invoices cannot be accepted through the network, your customers cannot process them, and payment stops. For most businesses the cash-flow consequence arrives before any penalty does.

Can ERPNext produce compliant e-invoice data?

Yes. ERPNext holds the structured transaction data the schema requires and is open-source, so the item master, tax templates and customer records can be extended with the fields PINT AE expects and the output mapped to your Accredited Service Provider's interface. The honest framing is that ERPNext gets your data compliant and connects to an accredited provider — it does not replace one. Most of the real work is data quality rather than integration.

We have weeks, not months. What should we do first?

Do not start with software selection. Start with an audit of the data the schema depends on: how many customers are missing a valid TRN, how many items lack a correct tax code, how many invoices are raised outside the system as manual documents. That audit takes days and determines everything else, because it tells you whether your remaining time goes into clean-up or integration. Appointing an Accredited Service Provider is a hard deadline at 30 October 2026, so run that selection in parallel rather than after.

What is Peppol in the UAE?

Peppol is the international e-invoicing network the UAE has adopted for its mandate. Instead of sending invoices to a central government platform, a business sends them through its Accredited Service Provider, which exchanges them with the customer’s provider over Peppol and reports the data to the tax authority. The invoice itself must follow PINT AE, the UAE’s Peppol data specification.

What is FTA e-invoicing?

FTA e-invoicing is the UAE’s electronic invoicing mandate, set by Ministry of Finance decisions and administered by the Federal Tax Authority. It requires in-scope businesses to issue B2B and B2G invoices as structured data rather than PDFs, exchanged through an Accredited Service Provider. Businesses with revenue of AED 50 million or more go live on 1 January 2027, and other businesses on 1 July 2027.

Ready to upgrade your enterprise?

Contact TABSYST Services