
Quick answer
ERPNext can be used for UAE e-invoicing, but not on its own. Its UAE regional setup stores TRNs, Arabic names and VAT flags, yet it does not create PINT AE files or connect to Peppol. You need a connector to an Accredited Service Provider, clean master data and a credit-note workflow. Businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026.
Key takeaways
- ERPNext's UAE regional setup adds TRN, Arabic name, Emirate and VAT flags, but no PINT AE or Peppol connection.
- You need a connector that sends each submitted Sales Invoice to an Accredited Service Provider (ASP).
- Revenue AED 50 million+: appoint an ASP by 30 October 2026, go live 1 January 2027. Others: 31 March 2027 and 1 July 2027.
- In ERPNext, Cancel and Amend must give way to credit notes once an invoice has been sent.
- Most rejections come from master data: customer TRNs, addresses, unit codes and tax templates.
Table of contents
- When Must ERPNext Users Go Live?
- Does ERPNext Support UAE E-Invoicing Out of the Box?
- How ERPNext Fits the Five-Corner Model
- Three Ways to Connect ERPNext to an ASP
- Choosing an ASP for ERPNext
- Mapping ERPNext Data to PINT AE
- Step-by-Step: Getting ERPNext Ready
- Why Cancel and Amend Must Change
- Receiving Supplier E-Invoices in ERPNext
- Common ERPNext E-Invoicing Mistakes
- What Are the Penalties?
- How SGA World Helps ERPNext Users
- Frequently asked questions
ERPNext is a popular choice for UAE businesses that want an open-source ERP with full accounting, inventory and VAT. With e-invoicing becoming mandatory from 1 January 2027 for large businesses, the question we hear most from ERPNext users is simple: is ERPNext enough, or do we need something else?
Planning your ERPNext e-invoicing project? Our ERP advisory team can scope the connector, clean your data and test with your provider.
This guide explains what ERPNext already does for UAE tax, what it does not do, how to connect it to an Accredited Service Provider, which fields map to the UAE’s PINT AE format, and the steps to go live safely. For the regulations themselves, read our complete guide to e-invoicing in the UAE.
When Must ERPNext Users Go Live?
| Category | Appoint an ASP by | E-invoicing mandatory from |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
Revenue means gross revenue in your most recent financial period. The large-business appointment date was moved from 31 July to 30 October 2026, but the go-live date did not change. See our note on the deadline extension.
Does ERPNext Support UAE E-Invoicing Out of the Box?
Partly. When a company’s country is set to the United Arab Emirates, ERPNext’s UAE regional setup adds fields that VAT reporting needs. In ERPNext v15 these include:
| Where | Fields added |
|---|---|
| Sales Invoice | Company TRN, Customer Name in Arabic, VAT Emirate, Tax Refund provided to Tourists |
| Purchase Invoice | Company TRN, Supplier Name in Arabic, Reverse Charge Applicable, Recoverable Standard Rated Expenses |
| Invoice items | Tax Code, Tax Rate, Tax Amount, and Is Zero Rated / Is Exempt flags |
| Item | Tax Code, Is Zero Rated, Is Exempt |
| Customer and Supplier | Name in Arabic, plus the standard Tax ID field |
| Address | Emirate |
ERPNext also includes a UAE VAT 201 report for the VAT return.
What it does not include is the e-invoicing layer itself:
- generating the invoice as a PINT AE XML file (based on UBL 2.1);
- sending it over the Peppol network;
- connecting to an Accredited Service Provider (ASP) and reading back the result;
- reporting the tax data to the FTA.
That work belongs to your ASP, and ERPNext needs a connector to reach it.
How ERPNext Fits the Five-Corner Model
The UAE uses a five-corner model. ERPNext sits at corner 1, where you raise the invoice:
- You (supplier): submit the Sales Invoice in ERPNext.
- Your ASP: converts it to PINT AE, validates it and sends it over Peppol.
- Your customer’s ASP: receives and checks it.
- Your customer: receives it in their own system.
- FTA: receives the tax data reported by the provider.
The connector is the link between corner 1 and corner 2. Every invoice that leaves ERPNext must carry complete, correct data, because the ASP rejects anything that fails validation.
Three Ways to Connect ERPNext to an ASP
| Route | How it works | Best for | Watch out for |
|---|---|---|---|
| Connector app inside ERPNext | A Frappe app builds the PINT AE file when a Sales Invoice is submitted and sends it to the ASP’s API. Status and IDs are written back to the invoice. | Most businesses with steady B2B volume | Must be built and tested for your ERPNext version and your chosen ASP |
| ASP middleware | The ASP’s platform pulls submitted invoices through the ERPNext REST API, converts and sends them. | Groups with several systems feeding one ASP | Sync timing, and making sure every invoice is picked up |
| Manual upload to the ASP portal | Invoices are exported or keyed into the ASP’s portal. | Very low volumes only | Slow, error-prone and hard to reconcile at month-end |
Whichever route you choose, ask the provider to show a live test with ERPNext, not just a slide, and confirm who maintains the connector after ERPNext upgrades.
Choosing an ASP for ERPNext
Since 1 October 2026, Ministerial Decision No. 168 of 2026 requires every provider to hold full accreditation; the earlier preliminary-approval stage has ended. Before you sign:
- check the provider is on the Ministry of Finance’s list of accredited e-invoicing service providers;
- confirm it supports ERPNext, through its own connector or a partner’s;
- ask how it handles rejected invoices, credit notes and incoming supplier invoices;
- compare pricing: per invoice, per bundle or a flat fee;
- check data retention and how you export records for your auditors.
Mapping ERPNext Data to PINT AE
Most e-invoice rejections are caused by data, not software. This is where an ERPNext project spends most of its time.
| PINT AE data | Where it lives in ERPNext | What to check |
|---|---|---|
| Supplier legal name and TRN | Company (Tax ID) and Company TRN on the invoice | One TRN per legal entity, matching EmaraTax |
| Buyer legal name and TRN | Customer (Tax ID) | Legal name, not a trading or short name |
| Buyer Arabic name | Customer Name in Arabic | Filled for every B2B customer |
| Buyer address and Emirate | Customer Address (Emirate field) | Complete street, city, Emirate and country |
| Buyer Peppol address | Not standard in ERPNext | Usually added by the connector; get it from the customer or their ASP |
| Item description and classification | Item, Tax Code | Codes chosen for the actual item, not copied |
| Unit of measure code | UOM | ERPNext v15 has no standard code field; the connector or a custom field maps each UOM to the required code |
| VAT category and rate | Item Tax Template and Sales Taxes and Charges Template | Standard, zero-rated, exempt and out-of-scope set up separately |
| Credit note reference | Sales Invoice with Is Return and Return Against | Always linked to the original invoice |
| Currency and exchange rate | Sales Invoice currency fields | AED amounts for VAT where the invoice is in another currency |
Practical tip: run a report of active customers with an empty Tax ID, Arabic name or Emirate before you start testing. Fixing a few hundred customer records takes days, and it is the most common reason first test invoices fail.
Step-by-Step: Getting ERPNext Ready
- Confirm your phase. Check last period’s gross revenue against AED 50 million to see whether 30 October 2026 applies to you.
- Check your ERPNext version and hosting. Connectors are built for current versions such as v15 and v16. On Frappe Cloud, confirm your plan allows the connector app to be installed.
- Choose and appoint your ASP. Pick an accredited provider that supports ERPNext, then appoint it on EmaraTax.
- Install and configure the connector. Enter the ASP credentials, map your companies and decide which document types are sent.
- Clean the master data. Customers, suppliers, addresses, items, UOM codes and Arabic names, as in the table above.
- Review tax templates. Make sure each VAT treatment, including zero-rated exports, exempt supplies and reverse charge, has its own template and Tax Code.
- Lock down cancellation. Remove the Cancel permission on Sales Invoice for most users, so corrections go through credit notes.
- Test every invoice type. Standard-rated, zero-rated, exempt, credit notes, multi-currency and any self-billing, first in a test environment, then with a friendly customer.
- Train the team and set a daily check. Someone must review rejected or pending invoices every day after go-live.
Why Cancel and Amend Must Change
ERPNext lets you cancel a submitted invoice and amend it into a new version. Under e-invoicing, once an invoice has been sent and accepted, it is a legal tax invoice held by your customer and reported to the FTA. Cancelling it in ERPNext does not recall it.
The correct route is a credit note: in ERPNext, a Sales Invoice marked Is Return against the original, sent through the ASP in the same way. Where the original was wrong, issue the credit note and then a new correct invoice. Agree who can raise credit notes and how they are approved.
Receiving Supplier E-Invoices in ERPNext
Your ASP also receives e-invoices from your suppliers. Depending on the connector, these can be brought into ERPNext as draft Purchase Invoices for your team to check against purchase orders and receipts. Two rules help:
- review incoming drafts every day, and match them to POs and receipts before submitting;
- never key in a supplier invoice by hand if it has already arrived through the ASP, or you will duplicate the cost and the input VAT.
Common ERPNext E-Invoicing Mistakes
- Using a customer’s short or trading name instead of the legal name.
- Missing Tax IDs, Arabic names or Emirate on customer addresses.
- Leaving UOM codes unmapped, so every invoice line fails validation.
- One tax template for everything, so zero-rated and exempt lines are sent as standard-rated.
- Cancelling and amending sent invoices instead of issuing credit notes.
- Testing with real customers before the connector has been tested internally.
- Upgrading ERPNext without re-testing the connector.
What Are the Penalties?
Under Cabinet Decision No. 106 of 2025, failing to implement e-invoicing or appoint an ASP on time costs AED 5,000 per month. Not issuing an invoice or credit note electronically when required costs AED 100 per document, up to AED 5,000 a month. Late notification of a system failure or data change costs AED 1,000 per day.
How SGA World Helps ERPNext Users
SGA World works with ERPNext as accountants and ERP advisers, so we look at e-invoicing from the finance side as well as the system side:
- Readiness review: your phase, deadlines, invoice types and current ERPNext set-up.
- ASP and connector selection: comparing accredited providers that support ERPNext.
- Data clean-up: customer and supplier records, items, UOM codes and tax templates.
- Testing: every invoice type, credit notes and supplier invoices, before go-live.
- Ongoing compliance: monthly checks alongside your VAT returns and bookkeeping.
Read more about ERPNext in Dubai and our ERP advisory services, or book a consultation. If you use Zoho Books instead, see our Zoho Books e-invoicing setup guide.
ERPNext E-Invoicing UAE – FAQs
01.Is ERPNext compliant with UAE e-invoicing?
Not on its own. ERPNext stores the data an e-invoice needs, but it does not generate PINT AE files or exchange invoices over Peppol. You need a connector to an Accredited Service Provider on the Ministry of Finance's list, plus correct master data and tax set-up.
02.Do I need to replace ERPNext to comply with e-invoicing?
No. ERPNext stays your invoicing and accounting system. A connector app or an ASP integration sends each submitted invoice to your provider, which validates it, exchanges it over Peppol and reports the data to the FTA.
03.Which ERPNext versions can be connected?
Connectors are generally built for current versions, such as ERPNext v15 and v16. Older versions may need an upgrade before a connector can be installed and tested.
04.Can I use ERPNext on Frappe Cloud for e-invoicing?
Yes, provided your plan lets you install the connector app your ASP or implementer supplies. Check this before you choose a connector, because shared plans can limit custom apps.
05.How do I correct an e-invoice in ERPNext?
Raise a credit note, which in ERPNext is a Sales Invoice marked Is Return against the original invoice, and send it through the ASP. Do not cancel and amend an invoice that has already been sent.
06.What happens to purchase invoices from suppliers?
Supplier e-invoices arrive through your ASP. Depending on the connector, they can be brought into ERPNext as draft Purchase Invoices for review, so they should not be keyed in again by hand.
07.When must ERPNext users go live?
Businesses with revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and go live on 1 January 2027. Others appoint by 31 March 2027 and go live on 1 July 2027. Government entities go live on 1 October 2027.
08.Does e-invoicing apply to POS sales to consumers?
Not in the current phases. B2C transactions are outside scope under Ministerial Decision No. 244 of 2025 until a later decision sets a date, so retail POS invoices to individuals are not affected yet.


