FTA E-Invoicing in UAE: What Businesses Need to Know in 2026

If your business issues B2B invoices in the UAE, the way you produce and transmit those invoices is about to change fundamentally.

The UAE is introducing mandatory e-invoicing in phases based on business size. This is not a format change. It is a structural shift from PDF invoices and paper documents to structured, machine-readable XML transmitted in near real time to the Federal Tax Authority through a certified intermediary.

For businesses still running legacy accounting systems, manual invoicing processes, or Tally-based workflows, the deadline creates a compliance forcing function. Understanding what the mandate requires – and when – is the starting point for preparing effectively.

What Is UAE FTA E-Invoicing and Why Is It Mandatory?

UAE FTA e-invoicing is a mandatory electronic invoicing system established under Federal Decree-Law No. 16 of 2024 (amending the UAE VAT Law) and Federal Decree-Law No. 17 of 2024 (amending the Tax Procedures Law).

The detailed framework is set out in Ministerial Decisions No. 243 and No. 244 of 2025, with penalties defined under Cabinet Decision No. 106 of 2025.

The Ministry of Finance published the Electronic Invoicing Guidelines V1.0 in February 2026, followed by an updated V1.1 on 1 June 2026 reflecting further technical specifications. These guidelines govern the technical format, data requirements, and transmission process that all covered businesses must follow.

The mandate applies to B2B (business-to-business) and B2G (business-to-government) transactions. B2C transactions are currently excluded from the requirement. The FTA’s objective is real-time tax data visibility – receiving invoice information almost instantly rather than waiting for quarterly VAT returns.

A standard PDF invoice, a Word document invoice, or a scanned paper invoice will have no compliance value once the mandate applies to your business. The only compliant format is a structured XML document in the PINT AE specification, transmitted through an FTA-Accredited Service Provider.

The PINT AE format is a UAE-specific extension of the global Peppol PINT standard. An electronic tax invoice requires 51 mandatory fields; a commercial e-invoice requires 49.

These fields cover seller and buyer identification details, VAT breakdowns, line-level item data, document totals, and UAE-specific indicators including VAT treatment, place of supply, and free zone classification.

With the legal background clear, here is when the requirements apply.

The UAE E-Invoicing Implementation Timeline

The UAE is taking a phased approach based on business revenue size.

Deadlines in the UAE e-invoicing rollout have been revised before. Always confirm the current schedule directly at mof.gov.ae before planning around specific dates, as the Ministry of Finance has the authority to adjust timelines as the rollout progresses.

One specific exemption to note: intragroup transactions benefit from a 24-month grace period from the e-invoicing mandate. Businesses in multi-entity group structures have additional time to implement e-invoicing for intercompany invoices.

However, planning for this should begin in parallel with the main mandate preparation – the configuration work required is largely the same.

The core principle to act on is this: Phase 1 businesses have less time to prepare than Phase 2 businesses, but no business should wait until the final phase to begin. ERP configuration, ASP integration, and master data preparation take longer than most businesses expect.

With the timeline understood, the next question is how the system actually works.

How the UAE Peppol 5-Corner Model Works

The UAE has adopted a Peppol-based decentralised e-invoicing architecture, sometimes called the 5-corner model or DCTCE model. Understanding the model explains why appointing the right ASP is more than a procurement decision.

The five corners work as follows:

Corner 1 – Your business (supplier). Your ERP or accounting system generates the invoice in the PINT AE XML format and sends it to your Accredited Service Provider.

Corner 2 – Your ASP (supplier side). Your ASP validates the invoice data against PINT AE rules, ensures all mandatory fields are present, and transmits the invoice through the Peppol network.

Corner 3 – Your customer’s ASP (buyer side). The buyer’s ASP receives the invoice, acknowledges it, and delivers it to the buyer’s system.

Corner 4 – Your customer (buyer). The buyer receives the compliant XML invoice directly in their own system.

Corner 5 – The FTA. Both the supplier’s ASP and the buyer’s ASP independently extract and report tax-relevant data to the FTA in near real time. This dual-reporting design gives the FTA real-time oversight without sitting in the middle of every invoice transmission – it is what makes this model significantly more effective for tax enforcement than traditional e-filing approaches.

For businesses, the most important practical implication is that your ERP is Corner 1. It generates the invoice. If your ERP cannot produce the required PINT AE format with all mandatory fields populated correctly, the entire chain fails at the first step.

With the technical model understood, here is what every UAE business needs to do before their phase deadline.

What Businesses Need to Do Before the Deadline

1. Determine which phase applies to your business. Check your annual revenue against the AED 50 million threshold. Phase 1 covers businesses above this level; Phase 2 covers smaller businesses in a subsequent rollout.

Regardless of which phase applies, preparation should begin well in advance – ASP onboarding, ERP configuration, and master data preparation cannot be completed in a few weeks. Confirm your current deadline at mof.gov.ae.

2. Assess your current invoicing system. PDF invoices, Word templates, and manual billing processes do not produce PINT AE compliant XML. Businesses using these methods need either to configure their existing ERP to produce the correct output, or to migrate to a compliant system before the deadline.

Businesses on legacy on-premise accounting tools – including Tally and older NAV versions – should treat the e-invoicing mandate as a trigger to evaluate whether migration is more cost-effective than retrofitting.

3. Select and onboard an FTA-Accredited Service Provider. Only businesses connected to an FTA-accredited ASP can transmit compliant e-invoices. The ASP is a compliance partner for the long term – evaluate them on technical capability, support responsiveness, experience with UAE-specific e-invoicing requirements, and their integration approach with your existing ERP. Not just cost.

Every UAE business will also need a Peppol Participant ID – formatted as 0235: followed by their 10-digit UAE Tax Identification Number – to participate in the network.

4. Clean your master data. Every buyer you invoice through the e-invoicing system needs a Peppol Participant ID. Collecting and validating buyer TINs and Peppol IDs before go-live is a data quality task that consistently takes longer than businesses expect.
5. Configure and test your ERP. UAE e-invoicing technical guidance requires 51 mandatory fields for an electronic tax invoice and 49 for a commercial e-invoice. These include seller and buyer identification, VAT breakdowns, line-level detail, document totals, and UAE-specific fields such as VAT treatment, place of supply, and free zone indicators.

Your ERP must be configured to produce all required fields correctly and tested against your ASP’s validation engine well before any go-live date. System testing followed by User Acceptance Testing should be completed with several weeks to spare before the mandatory deadline.

The five steps above define the preparation work. The choice of ERP determines how easy or difficult that preparation is.

What FTA E-Invoicing Means for Your ERP

The e-invoicing mandate makes ERP selection and configuration a direct compliance decision.

A business running a modern, cloud-based ERP like Dynamics 365 Business Central is positioned to meet e-invoicing requirements through configuration and certified integration with an accredited ASP. Business Central’s architecture supports the structured data fields required by the PINT AE specification and can be integrated with UAE-approved Peppol access points.

A business running a PDF-based billing tool, a basic cloud accounting package, or a legacy on-premise system faces a harder path. These systems were not designed to produce structured XML with 50+ mandatory fields, and retrofitting them for e-invoicing compliance is typically more expensive and less reliable than migrating to a purpose-built ERP.

For businesses preparing for FTA e-invoicing compliance through Business Central, the configuration work covers PINT AE field mapping, ASP integration setup, and testing against the Peppol network before the mandatory go-live date.

Ongoing configuration management is also required as the Ministry of Finance continues to refine technical specifications. Having a reliable Dynamics 365 support partner ensures your setup stays aligned with regulatory updates.

Burhani™ works with UAE businesses to assess their current invoicing systems, identify the gap between their current output and PINT AE compliance requirements, and implement the configuration and integration needed to meet the mandate.

The readiness of your ERP determines how smoothly you meet the mandate. Here is the broader picture.

Final Thoughts

UAE FTA e-invoicing is not a distant concern. For businesses with AED 50 million or more in revenue, the first mandatory phase is already in motion. For all other businesses, preparation before your phase deadline is the difference between a controlled implementation and a rushed compliance scramble.

The businesses that will find this transition straightforward are those already running a well-configured ERP – one that manages invoice data at the field level rather than producing formatted PDFs. The businesses that face the most disruption are those still generating invoices manually or through systems that cannot produce structured XML.

The time needed to select an ASP, configure your ERP, collect buyer Peppol IDs, and complete UAT testing should not be underestimated. This is typically a three to four month project at minimum. Starting early gives time to test, train, and resolve issues before the deadline becomes mandatory.

Note: E-invoicing regulations and deadlines in the UAE have been updated multiple times since initial announcement. Always confirm current requirements and timelines directly with the Ministry of Finance (mof.gov.ae) or a qualified tax advisor before making compliance decisions.

Frequently Asked Questions