E-invoicing in the UAE and Oman: what your ERP must be ready for

Large businesses in the UAE have until 30 October 2026 to appoint an Accredited Service Provider for e-invoicing, and the system goes live for them on 1 January 2027. Oman is close behind, with its first mandatory phase starting on 1 April 2027. For many finance and IT teams this is being treated as a vendor selection exercise. It is mostly an ERP and data exercise, and the time left is shorter than it looks.

Where the deadlines stand

In the UAE, the Ministry of Finance moved the deadline for appointing a provider from 31 July to 30 October 2026 for businesses with annual revenue of AED 50 million or more. It kept the go-live date of 1 January 2027 unchanged (Deloitte, Gulf News). The extension responded to concerns from large taxpayers about the choice of technical options and pricing among accredited providers (Middle East Briefing).

The later phases are also fixed:

• businesses below AED 50 million must appoint a provider by 31 March 2027 and go live on 1 July 2027,
• government entities have the same appointment date and go live on 1 October 2027.

(KPMG, Zoho)

In Oman, the Tax Authority started a pilot with 100 selected companies on 1 August 2026, and Decision No. 189/2026 set the mandatory dates. Phase 1 starts on 1 April 2027 for taxpayers with annual supplies above OMR 5 million, and Phase 2 starts on 1 October 2027 for everyone else (Sovos, Comarch).

Groups that trade in both countries face two go-lives within three months of each other.

What actually changes

Both countries use the same basic design. Invoices are no longer PDFs sent by email. They become structured data files, sent from the seller's provider to the buyer's provider, with the tax authority receiving the data along the way. The UAE uses a Peppol-based model with its own PINT-AE format, and the rules cover both business-to-business and business-to-government invoices (Fonoa, Banqup). Oman's Fawtara programme follows a similar model through accredited providers (Banqup, Sovos).

The practical consequence is simple. If an invoice leaves your ERP with a missing or wrong field, it does not reach the customer in a corrected form later. It is rejected, or it goes out wrong with the authority watching.

The cost of being late

The UAE has already set the penalties. Under Cabinet Resolution No. 106 of 2025, failing to implement the system on time, including failing to appoint a provider, costs AED 5,000 for each month or part of a month of delay. Failing to issue and send an e-invoice on time costs AED 100 per invoice, up to a monthly cap. Failing to tell the Federal Tax Authority about a system failure costs AED 1,000 a day (Gulf News, Middle East Briefing).

The fines are modest for a large company. The bigger risk is operational: invoices that customers cannot accept, payments that slip, and a finance team spending January fixing data by hand.

Five things to fix inside the ERP

A provider can only send what your ERP gives it. These are the areas where projects usually find problems.

1. Customer master data. Every buyer needs a correct tax registration number, legal name and address in the format the standard expects. Many ERPs hold years of duplicates and free-text entries. Clean them now, starting with your top customers by invoice volume. 2. Invoice fields and codes. Structured invoices need items, units, tax categories and exemption reasons as codes, not descriptions. Map every tax code in your system to the national format, and check the unusual cases: zero-rated exports, exempt supplies, designated zones and reverse charge. 3. Credit notes, advances and retentions. These cause the most rejections. The UAE's updated guidelines (version 1.1) explain how to treat advance payments and retention amounts. For example, the final invoice after an advance should cover only the remaining balance and refer back to the advance invoice (Crowe, MBG). Construction, contracting and project businesses should test these flows first. 4. The connection to the provider. Decide who builds and owns the integration between your ERP and the provider, how rejected invoices come back into the system, and who in finance is responsible for fixing them the same day. This is the seam that breaks most often after go-live. 5. Storage and audit. E-invoices and their data must be kept complete, unaltered and retrievable for the statutory period (Crowe, MBG). Check that your archive can return a specific invoice quickly when the tax authority asks.

Choosing a provider without regretting it

With the deadline close, some companies will sign with the first provider that answers. A few questions save trouble later:

• Does the provider have a tested connector for your ERP and version, and can you speak to a customer using it?
• How are rejected invoices reported back, and how quickly?
• If you also trade in Oman, will the same provider be accredited there, or will you run two integrations?
• What does pricing look like when your invoice volume doubles?
• How do you leave the provider if you need to, and who owns the data?

Xoft's view

E-invoicing looks like a compliance project, but it is the first time many organisations in the region will see the true quality of their own invoice data. Companies that treat it as a data clean-up and an integration project, not just a contract with a provider, will go live with fewer rejections and a cleaner ERP. With less than four weeks to the UAE appointment deadline, the best next step is to run a sample of last month's invoices against the national format and see how many would pass. That number shows how much work is left.

Written by the Xoft team in Muscat and Dubai.