UAE E-Invoicing with NetSuite: What Changes and How to Get Ready

The Ministry of Finance sets the rules and the Federal Tax Authority (FTA) receives the data. The legal framework sits in Ministerial Decisions No. 243 and No. 244 of 2025, which define who is in scope and when each group must comply, with later amendments to the timetable and a separate Cabinet Decision on penalties.

For a finance team on NetSuite, the practical change is simple to describe and harder to deliver. Every in-scope invoice and credit note must leave NetSuite as complete, valid data that your service provider can convert and send within the rules, and every supplier e-invoice must arrive in NetSuite without retyping.

Mandatory e-invoicing starts on 1 January 2027 for the largest businesses and is phased in through 2027. As of November 2026, these are the dates under Ministerial Decision No. 244 of 2025, as amended by Ministerial Decision No. 66 of 2026:

The original ASP deadline for large businesses was 31 July 2026. In May 2026 the Ministry moved it to 30 October 2026 after assessing market readiness, but it kept the 1 January 2027 go-live. A pilot phase began in July 2026.

For a NetSuite project, the date that matters is not the go-live itself but the date your ASP integration must be tested and signed off, which is several weeks earlier. If you are in the first phase and have not started, the build, testing and data clean-up now share a window of a few weeks.

For the wider picture of how the timetable fits into ERP planning, see our guide to ERP implementation in the UAE and GCC.

Every business conducting B2B or B2G transactions in the UAE is in scope unless a specific exclusion applies. That includes businesses that are not VAT-registered, because commercial invoices are covered as well as tax invoices.

In NetSuite terms, you need to be able to tell an in-scope invoice from an out-of-scope one on every transaction. A retailer that sells to consumers and to trade customers, for example, will e-invoice its trade sales and not its consumer sales, so the customer record or the transaction form must carry that distinction.

The UAE uses a decentralised five-corner model on the Peppol network. You never send an invoice straight to your customer or to the FTA: your ASP sends it to your customer's ASP, and both providers report the tax data to the FTA.

The format on the network is PINT AE, the UAE's national version of the Peppol PINT invoice specification. The Ministry of Finance publishes the mandatory fields for tax invoices and commercial invoices; the current version, V1.1, is dated 28 October 2026. Your ASP handles the conversion, but it can only convert the data NetSuite gives it.

Each business is identified by its TIN, the first 10 digits of its Corporate Tax registration number. Its Peppol participant ID is 0235 followed by that TIN, and that is the address your ASP uses to reach a customer. Each member of a tax group uses its own TIN, not the representative member's.

NetSuite keeps doing what it does today: sales orders, invoices, credit memos and vendor bills. What changes is the data each record must carry and what happens to it after approval.

These changes sit on top of your existing VAT set-up, so it is worth checking that first; our page on VAT-compliant ERP in the UAE covers what a sound configuration looks like.

NetSuite supports UAE e-invoicing through an integration with your ASP rather than as a ready-made country feature. Oracle's Electronic Invoicing SuiteApp provides a general framework for generating and receiving e-documents, but Oracle states that it does not include native support for country-specific requirements on its own.

The SuiteApp generates XML or JSON from supported transactions using templates you can build, sends them by email or through custom sending methods such as web services or scripts, and converts inbound XML into vendor bills, vendor credits or sales orders. As of November 2026 we found no Oracle-published UAE localisation for it, so check the SuiteApp marketplace and your ASP's offer before you design anything.

Whichever route you choose, treat it as an integration project with monitoring and error handling, not a form change. Our NetSuite integration services team builds and supports these connections, and the NetSuite integration guide explains the underlying options.

Most rejected e-invoices fail on data, not on the connection. Before mapping anything, check that each piece of information the e-invoice draws on exists in NetSuite, in one place, for every in-scope customer and transaction.

Treat this table as a starting checklist, not the full specification. The Ministry's mandatory fields document lists every required element and its rules, and your ASP will confirm which of them it derives automatically and which it expects from you.

If you are unsure how clean your account is, a free NetSuite health check is a quick way to find duplicate customers, inconsistent tax codes and unused forms before they turn into rejections.

Work through these steps in order. Data and decisions come first, the build comes after.

1. 1

   Confirm your phase

   Work out your revenue band, your ASP deadline and your go-live date for every UAE legal entity. If you are in the first phase and have not appointed an ASP, do it now.

2. 2

   Appoint an accredited ASP

   Choose from the Ministry's list of approved providers. Ask how they connect to NetSuite, whether they handle inbound invoices, and how they support several entities in one account.

3. 3

   Get a TIN for every entity

   Your TIN is the first 10 digits of your Corporate Tax registration number. An entity that is not registered for Corporate Tax must register with the FTA to receive one.

4. 4

   Clean customer and vendor data

   Collect TINs from business customers, fix legal names and addresses, and close duplicate records. This usually takes longer than the technical build.

5. 5

   Map NetSuite to PINT AE

   Work through the Ministry's mandatory fields document with your ASP and agree where each field comes from in NetSuite, including defaults and exceptions.

6. 6

   Design the inbound flow

   Decide how supplier e-invoices become vendor bills and credits, how they are matched to purchase orders and who approves them.

7. 7

   Test end to end in a sandbox

   Run invoices, credit notes, foreign-currency sales, zero-rated and exempt lines, and deliberate errors through the ASP's test environment.

8. 8

   Cut over with monitoring

   Agree the first transaction date, switch numbering and forms, and set up a daily rejections queue with a named owner before go-live.

If e-invoicing is part of a wider change, such as a new subsidiary or a move onto NetSuite, plan it inside the main project; our NetSuite implementation services cover both.

In a OneWorld account, each UAE legal entity is a separate e-invoicing participant with its own TIN, its own Peppol participant ID and its own phase, based on its revenue. A group can therefore have one subsidiary going live in January 2027 and another in July 2027.

Store identifiers on each subsidiary, not in one company-wide field, and make sure your ASP and your connector can handle several senders from one NetSuite account. Check, too, how intercompany invoices between UAE subsidiaries will be issued, because they are business transactions like any other.

Members of a VAT group each use their own TIN. Transactions between members of the same VAT group are in scope, but the Ministry's guidelines give them a 24-month grace period from 1 January 2027, which buys time for intercompany flows without removing the need to plan them.

For how subsidiaries, intercompany and consolidation work in NetSuite generally, see our guide to NetSuite OneWorld, and for finance process design, our NetSuite financial management services.

Cabinet Decision No. 173 of 2026, announced in October 2026, sets the current UAE e-invoicing penalties and replaces Cabinet Decision No. 106 of 2025. The main fines are:

The new decision also removed the earlier penalty for failing to notify the authority of a system failure, made it explicit that buyers who stop meeting their obligations as recipients can be penalised, and applies only one penalty where the same business is both issuer and recipient for the same violation. The guidelines state that penalties apply only from the date a business is required to implement.

In implementations we've run, the connector is rarely what delays go-live. The delays come from customer data nobody owned, credit memo habits nobody questioned and an accounts payable team that was not in the room.

Starting with the connector

The connector is the easy part. Missing TINs, inconsistent tax codes and duplicate customers are what cause rejections, so clean the data first.

Credit memos as an afterthought

Credit memos created without a link to the original invoice are a common cause of rejections. Fix the process that creates them, not just the template.

Forgetting accounts payable

Teams focus on sales invoices and only discover at go-live that supplier e-invoices are arriving with nowhere to go.

One TIN field for a whole group

In a OneWorld account each UAE subsidiary has its own TIN and its own e-invoicing obligations. Store identifiers per subsidiary.

Nobody owns rejections

A rejected invoice that sits in a queue for a week is an invoice that was not issued on time. Name an owner and a daily routine.

Testing only the happy path

Test the awkward cases: foreign currency, mixed VAT lines, partial credits, edited invoices and a customer with no TIN.

What to check first

Run a saved search of active business customers without a TIN, a list of tax codes used in the last twelve months, and a count of credit memos created without a source invoice. Those three numbers tell you more about your readiness than any vendor demo, and they show where the clean-up effort will go.

The trade-off between routes is mostly about who maintains the mapping. A connector moves that work to the vendor but ties you to its release schedule; a custom build gives you control but makes every PINT AE update your job. For most single-entity accounts with standard billing, the connector is the pragmatic choice.

If you want a second opinion on your plan, book a NetSuite consultation with our team.