ERPNext already holds most PINT AE fields, and every remaining gap is closable.
The built-in UAE module stops at VAT fields and the VAT 201 report. Master data, mapping and the provider connection decide the rest.
General information, not legal or tax advice. Confirm with your adviser.
Does ERPNext support UAE e-invoicing out of the box?
Not yet. On 23 September 2026, ERPNext's built-in UAE module covers VAT fields and the VAT 201 report but produces no PINT AE data, and a request for native UAE e-invoicing support on ERPNext's issue tracker is still open. An open-source app from ERPGulf covers part of the gap. Master data and the connection to your provider remain your work.
Stock ERPNext covers UAE VAT and stops there.
ERPNext's UAE regional module adds VAT fields and one report. On the development branch it adds a company TRN and a VAT emirate to invoices, names in Arabic for customers and suppliers, an Emirate field on addresses, a tax code with zero-rated and exempt flags on items, a line-level tax code, rate and amount on invoice items, reverse-charge fields on purchase invoices, and the UAE VAT 201 report.
Nothing in it generates PINT AE data or talks to an Accredited Service Provider. A request for native UAE e-invoicing support, opened on ERPNext's issue tracker on 17 December 2025, had no reply and was still open on 23 September 2026. A pull request adding an FTA Audit File and a UAE VAT register, opened on 28 April 2026, was closed without being merged on 19 May 2026. The newest release on the day we checked was v16.35.0, published on 15 September 2026.
We implement ERPNext and run our own books on it, and we are not an Accredited Service Provider. Nor are we a Frappe partner, so we read all of this as users do: from the public code and the public tracker.
Most mandatory fields exist already, and the gaps are specific.
Mapped against the Ministry of Finance's 51 mandatory fields for a tax invoice, most already exist in ERPNext under another name, such as invoice number and date, currency, due date, totals, item names, quantities and prices. The gaps are specific, and all of them are closable:
| Mandatory field | In ERPNext today | What closing it takes |
|---|---|---|
| Invoice transaction type code, eight flags | No field | Fields on the invoice, set by rules from the customer, the item and the scenario |
| Business process type and specification identifier | No field | Fixed values emitted by the integration |
| Seller and buyer electronic address and identifier | The TRN in the Tax ID field | Derive the TIN, the first 10 digits of the TRN, with scheme 0235. Handle the predefined endpoints for buyers not on the network |
| Legal registration identifier and its type (TL, EID, PAS, CD), and the licensing authority for a trade licence | Free-text registration details on the Company only | Structured fields on Company, Customer and Supplier, filled for every party |
| Country subdivision (the emirate) | The Emirate field the UAE module adds to addresses, holding names such as Dubai | Map each name to the seven codes rule IBR-128-AE allows (AUH, DXB, SHJ, UAQ, FUJ, AJM, RAK), make it mandatory, back-fill old addresses |
| Item classification: HS code for goods, service accounting code for services | A Customs Tariff Number field on items, nothing for services | Fill HS codes, add a service accounting code, and mark each item as goods, services or both |
| Credit note reason code | Returns have a free-text remark, not a coded reason | A reason field on credit notes, mapped to the specification's list |
| Unit of measure code | A Common Code field on UOM records (development branch) | Fill the code for every unit you invoice in |
| Payment means type code | Mode of Payment has a type, not a coded value | A mapping from each mode of payment to the code list |
| VAT amount and line amount in AED, per line | The UAE module's line tax fields and base-currency amounts | Emit both in AED on every line, including foreign-currency invoices |
| Tax category code and rate, per line and in the breakdown | Item tax templates and the item tax code | Map every template to one of the six UAE tax categories |
Twenty of the 51 fields describe the seller and the buyer. In ERPNext they live on Company, Customer, Supplier and Address, which is why the work starts with master data, not with invoices. The readiness checklist lists the record-by-record checks.
One invoice, traced field by field.
A worked example: an ordinary domestic tax invoice, standard-rated, paid by bank transfer. The identifiers are the business term numbers in the PINT AE 1.0.4 semantic model, and the codes come from its code lists. Illustrative values, not client data.
| PINT AE term | Where it comes from in ERPNext | Example value |
|---|---|---|
| IBT-001 Invoice number | Sales Invoice name, from its naming series | ACC-SINV-2026-00042 |
| IBT-002 Invoice issue date | Posting date | 2026-09-23 |
| IBT-003 Invoice type code | Fixed per document type | 380, named 'Commercial invoice' in the code list and used for a tax invoice |
| BTAE-02 Invoice transaction type code | A new field, set by rules | 00000000, no special case applies |
| IBT-005 Invoice currency code | Currency | AED |
| IBT-009 Payment due date | Due date | 2026-10-23 |
| IBT-031 Seller VAT identifier | Company Tax ID (the TRN) | The 15-digit TRN |
| IBT-034 Seller electronic address | Derived: first 10 digits of the TRN, scheme 0235 | The 10-digit TIN |
| IBT-030 and BTAE-15 Seller legal registration identifier and type | New structured fields on Company | The trade licence number, type TL |
| IBT-039 Seller country subdivision | Emirate field on the company address, mapped to a code | SHJ |
| IBT-081 Payment means type code | Mapped from the Mode of Payment | 30, credit transfer |
| IBT-130 Unit of measure code | UOM Common Code | H87, piece |
| IBT-151 Line VAT category code | Mapped from the item tax template | S, standard rate |
| BTAE-08 and BTAE-10 VAT and line amount in AED | Line tax amount and base amounts | Both in AED on every line |
Two of those rows need a decision rather than a lookup. The transaction type code is eight positions of 1 or 0, one each for free zone, deemed supply, margin scheme, summary invoice, continuous supply, agent billing, e-commerce and exports, so something has to decide each position for each invoice. And the invoice type code has a second value, 480, for an invoice issued by a party out of the scope of tax, which carries no tax details at all. Write both decisions down as rules, test them on last year's invoices, and only then automate them.
The ERPGulf app covers generation, with submission still to come.
ERPGulf, a Frappe developer that also publishes e-invoicing apps for Saudi Arabia and Malaysia, maintains uae_erpgulf, an open-source UAE e-invoicing app for ERPNext under the MIT licence. The repository was created in January 2026, a beta was posted on 23 April 2026, the release was announced on 5 June 2026, and the app is listed on the Frappe Cloud Marketplace for versions 15 and 16.
Its README describes what exists. The app generates structured invoice data as JSON, prepared for UBL 2.1 mapping. It covers sales invoices, credit notes and self-billed documents. It validates VAT and TRN details, HS codes for goods, service accounting codes, transaction type codes and payment means codes. It is candid about the rest: 'the structured invoice JSON generation layer is implemented', and submission workflows 'will be added in future phases'.
The app was first built against one provider, Flick. On 17 September 2026 its developers said a new version is provider-agnostic, with an adapter per provider. In August they had said another provider had not yet been tested. The most recent commit on the main branch is dated 8 September 2026.
That is real work, done in the open, and credit is due to ERPGulf for it. For an ERPNext client, it is where we would start: test it on your own scenarios, and contribute what is missing rather than build a parallel app.
Closing the gap takes five layers, and only one of them installs.
Five layers, finished before your implementation date under Ministerial Decision No. 244 of 2025, which is 1 January 2027 for revenue of AED 50 million or more, and 1 July 2027 below that line. Only the third layer is software you can install:
- Master data. TINs, legal registration identifiers, emirates on addresses, unit codes and tax categories, cleaned in ERPNext itself.
- Mapping. Every scenario you invoice, from free zone supplies to advance payments and retention, mapped to the transaction flags and tax categories, with each derivation written down.
- Generation. The invoice data produced from ERPNext, by the ERPGulf app, a provider's connector or a custom app. According to the Ministry of Finance, a provider may accept data in an agreed format and convert it into the UAE XML format itself, so producing a complete UBL document is not always your job.
- Connection. Posting to the API of the provider you appoint from the Ministry of Finance register, and storing each message-level status against its Sales Invoice, so that a rejection is visible where your accounts team works.
- Payables. Supplier e-invoices arriving from your provider as Purchase Invoices, matched to orders and receipts, because Ministerial Decision No. 243 of 2025 makes receiving through the system an obligation too.
Three routes to the provider, with the same data work under each.
| Route | What you get | What stays with you |
|---|---|---|
| Install the ERPGulf app | Open source, UAE validations, structured invoice data, an adapter per provider | Testing it on your scenarios, filling gaps, following its releases |
| Your provider's ERPNext connector, if it has one | Support from the party that carries the invoice | Master data, mapping, and a connector tied to one provider |
| A custom Frappe app | Exactly your scenarios and your provider's API | Maintaining it through every ERPNext upgrade |
Whichever route you take, the master data and mapping work is the same, and it does not go away. Choose the route by who will maintain it in two years, and by how many providers you may want to use.
Hosting location matters less than the decision's wording suggests.
Ministerial Decision No. 243 of 2025 asks for e-invoices, credit notes and associated data to be kept 'within the State' for the Tax Procedures Law period, and the Ministry's guidelines treat that as a question of whether the Federal Tax Authority can have them produced, complete and readable, rather than where the server sits. A provider can hold them for you under contract, and the duty stays yours. Confirm the arrangement with your tax adviser. Our own hosting is in Germany by default, with the UAE or your own servers on request.
Run version 15 or 16, and fold any upgrade into the same project.
The ERPGulf app is listed for versions 15 and 16, and its developers confirmed version 15 support on the forum. ERPNext's newest releases on 23 September 2026 were v16.35.0 and v15.121.3, both of 15 September 2026. If you run an older version, put the upgrade into the same project: an e-invoicing integration built on a version you are about to leave is built twice.
SolaryxDev does the ERPNext side of this work.
We deliver the gap report against the 51 fields, the master data clean-up, the mapping rules, the connection to your provider, and rejection handling in the screens your accounts team already uses, starting from the ERPGulf app where it fits.
See CRM and ERP implementation and UAE e-invoicing readiness. If you are still choosing an ERP, read ERPNext vs Odoo for a UAE SME, and if you are choosing a provider, read how to choose an ASP.
Frequently asked questions
Does ERPNext produce PINT AE invoices without extra work?
No. On 23 September 2026 the built-in UAE module covers VAT fields and the VAT 201 report only. PINT AE data and the provider connection need an app or an integration, plus master data work inside ERPNext itself.
Are there open-source apps that help?
Yes. ERPGulf's uae_erpgulf is MIT-licensed, listed for versions 15 and 16, validates UAE invoice data and generates structured invoice data. Its README says submission workflows follow in later phases, so check its current state before relying on it.
Which fields are UAE-specific?
The eight-flag invoice transaction type code, the legal registration identifier and its type (TL, EID, PAS or CD), the TIN-based electronic address with scheme 0235, the emirate as one of seven codes such as DXB or SHJ, and the VAT and line amounts in AED on every line of a tax invoice.
Does the ASP connect to ERPNext directly?
Only if it offers an ERPNext connector or accepts what an app such as ERPGulf's sends. Providers may accept an agreed data format through an API and convert it into the UAE XML format themselves. Ask which formats a provider accepts before you choose it.
How long does it take to make ERPNext ready for PINT AE?
It depends on your data more than on ERPNext. The five layers, master data, mapping, generation, connection and payables, have to be finished before your implementation date, and master data usually takes longest, because twenty of the 51 fields come from your company, customer and address records.