— UAE VAT
ERPNext for UAE VAT compliance: setup, filing, and FTA-ready in 2026.
A working guide from an ERPNext Gold Partner that has configured VAT for 200+ UAE entities since the 5% regime began in 2018. What ERPNext gives you, what it doesn't, and how to make a fresh install FTA-ready in a week.
TL;DR
Five things to know.
- ERPNext ships UAE VAT support natively. Tax Templates, Tax Rules and a UAE-VAT regional return report are all in core. No paid module required.
- Filing is still manual on EmaraTax. ERPNext gets you VAT-201-shaped data; a human keys it into the FTA portal each period. The FTA does not publish a documented public submission API.
- Reverse charge is a separate tax template. Imports and overseas services need their own purchase template that books output and input VAT simultaneously. Easy to forget on day one.
- Designated zones need both Tax Category on the party and tax rules on the item. Goods qualify for zero-rating; services do not. Mis-tag and you'll over- or under-claim.
- VAT groups need a custom consolidated report. ERPNext's standard report is per-company. Multi-entity VAT groups are a one-week add-on we build as standard.
Context
Why UAE VAT compliance is non-trivial in any ERP.
UAE VAT looks deceptively simple on paper. A flat 5% standard rate, a single VAT-201 form, monthly or quarterly periods depending on turnover. Most software vendors will tell you their accounting tool "supports UAE VAT" because they can stamp a 5% line on an invoice. That isn't VAT compliance.
The work is in the edge cases. The FTA Executive Regulations identify roughly two dozen distinct scenarios that change how a transaction is taxed: standard-rated, zero-rated, exempt, out-of-scope, reverse-charge on imports, reverse-charge on services, deemed supplies, designated-zone goods movements, intra-GCC transactions (now largely treated as outside-GCC since not all states implemented the framework), partial exemption, capital-asset adjustments, profit-margin scheme for second-hand goods, and a handful more.
Each of those scenarios needs to land in the right box on the VAT-201 — which is itself broken out by emirate for standard-rated supplies — or the FTA reconciliation flags it. ERPs that "support VAT" rarely model this granularity. The ones that do, like ERPNext, push the configuration burden onto the implementer. Setup is doable but unforgiving.
Beyond setup, filing cadence is itself a trap: businesses below AED 150 million annual turnover file quarterly, those above file monthly, and the threshold tests cut both ways. Period mismatches between the ERP's accounting period and the VAT period are a routine source of reconciliation pain when month-end and quarter-end don't line up cleanly with the FTA's tax periods.
And finally, designated zones — JAFZA, DAFZA, ADGM-adjacent zones, RAK FTZ for goods, and so on — are treated as "outside the UAE" for VAT on goods movements, but very much inside for services. Get the customer's tax category wrong and you'll either charge VAT on a zero-rated supply (your customer will refuse to pay it and they'd be right) or miss VAT on a standard-rated one (your problem at audit).
Out of the box
How ERPNext handles UAE VAT natively.
ERPNext's tax engine has three layers and you'll touch all three.
1. Sales Taxes and Charges Templates. These define how a tax behaves: account head, rate, whether it's calculated on net or gross, and whether it's deducted, added, or actual. For the UAE you'll typically maintain at minimum: UAE VAT 5% — Standard, UAE VAT 0% — Zero Rated, UAE VAT — Exempt, UAE VAT — Out of Scope, and a separate UAE VAT — Reverse Charge for imports. You'll build mirror Purchase Taxes templates for the buy side. Many of these come pre-seeded when you set "United Arab Emirates" as the country during install.
2. Tax Rules. Where templates define what a tax does, Rules define when it applies. Rules let you say: if Customer's Tax Category is "Designated Zone" and Item's Tax Category is "Goods", apply the Zero-Rated template. Rules cascade by priority. Done well, your sales team never has to pick a tax template manually — the right one defaults from the customer + item combination.
3. The UAE VAT regional report. ERPNext ships a UAE-specific report (under Accounting → UAE VAT 201) that aggregates posted invoices into the seven boxes of the VAT-201 form, broken out by emirate where required. It pulls from the Sales Invoice and Purchase Invoice records, separates standard-rated by emirate (boxes 1a–1g), zero-rated, exempt supplies, reverse-charge imports, and recoverable input VAT. Output is a screen view plus CSV export.
Three things the standard setup does not handle, which catch most teams:
- VAT on advances. If you take customer deposits before invoicing, ERPNext doesn't automatically generate a tax invoice on the receipt date. You either accept that and use customer down-payment invoices manually, or you bolt on a small workflow.
- Tax invoice numbering rules. Article 59 requires sequential numbering by tax invoice. ERPNext's default naming series usually satisfies this but you should set the series at the company level and verify gaps don't appear.
- Bilingual tax invoices. Article 59 requires Arabic on the tax invoice. ERPNext's default print formats are English; a custom print format with Arabic field labels is a 1–2 day job and we ship a template.
Setup
Seven steps to make a fresh ERPNext install FTA-ready.
- 01
Set country = United Arab Emirates at company creation
This seeds the base UAE Chart of Accounts (or you can replace it with your auditor's version), pre-creates a UAE VAT 5% account head under Duties and Taxes, and enables the UAE-VAT regional report. If you migrate from a non-UAE company set later, you fix this manually — easier to do it on day one.
- 02
Build your Tax Templates
At minimum five sales templates (Standard 5%, Zero-Rated, Exempt, Out-of-Scope, Reverse Charge) and four purchase templates. Set the account head consistently so the regional report aggregates correctly. Test each template by booking a draft invoice.
- 03
Define Tax Categories
Create categories for: Mainland UAE, Designated Zone — Goods, Designated Zone — Services, GCC Implementing State (largely vestigial now), Outside GCC. Tag every Customer and Supplier. Tag items with their goods/services flag where it differs from the master default.
- 04
Wire Tax Rules
Create Tax Rules that cross-reference Customer Tax Category and Item Tax Category to pick the right template automatically. Set priorities so the most specific rule wins. Verify by drafting test invoices for each scenario before going live.
- 05
Configure TRN field and validation
Rename the Tax ID label to "TRN" on Customer and Supplier forms via Customize Form. Add a client script that validates the 15-digit format and warns on duplicates. Make TRN mandatory on the customer record for any party you'll issue tax invoices to.
- 06
Customize the tax invoice print format
Add Arabic field labels (Tax Invoice الفاتورة الضريبية, TRN, Date of Supply تاريخ التوريد), the supplier TRN, the customer TRN, place of supply, and a clearly printed "Tax Invoice" header. Keep an "Original" / "Duplicate" watermark variant for re-issues. Apply at the company level so all entities inherit.
- 07
Run a parallel period before cutover
Before going live, post one full month of representative transactions in ERPNext alongside your existing system. Run the VAT-201 report. Reconcile box-by-box against the manual return your finance team would file. Discrepancies are almost always tax category misconfiguration on a customer or item — easy to fix before you trust it with real numbers.
Failure modes
What we see go wrong.
Tagging the customer instead of the transaction. A designated-zone customer buying services should still be charged 5% — but if the team has slapped "Zero Rated" as a default tax template on the customer record, every invoice goes out at 0%. Tax Categories + Rules fix this; default tax templates on the customer don't. Use Rules.
Forgetting reverse-charge on overseas SaaS. Every UAE business that pays for AWS, Google Workspace, Microsoft 365, Adobe, or any non-UAE software vendor owes reverse-charge VAT on those imports of services. We see this missed routinely — usually by businesses whose ERP was set up by someone non-UAE-trained. The reverse-charge purchase template handles it but somebody has to remember to use it on those bills.
Using "Exempt" when the right answer is "Out of Scope". These are different VAT-201 boxes and different audit treatments. Exempt = within scope but no VAT (residential rent, certain financial services, local passenger transport). Out of Scope = not subject to UAE VAT at all (sale to a non-UAE party of goods that never enter the UAE). Mixing them up doesn't change cash, but it does mis-state the return.
Period mismatch on year-end. If your fiscal year is calendar and your VAT period is quarterly, the December VAT return covers Oct–Dec but the financial year closes 31 Dec. Adjustments posted in January with a December date will land in the next VAT period. We script a "VAT cutoff" report that flags any backdated entries crossing a return boundary.
Multi-entity
VAT grouping for free-zone holdcos.
Most of our UAE clients above mid-market run more than one legal entity: a mainland trading company, a free-zone holdco, sometimes a services entity in a designated zone, occasionally a Saudi or Oman subsidiary. The FTA permits VAT grouping for two or more legal persons under common control, filing a single consolidated VAT-201 under the group's representative TRN.
ERPNext handles the multi-company side natively. One database, one user pool, separate Companies with separate Charts of Accounts (or shared, your call). Inter-company transactions can be configured to auto-post the matching entry on the counterparty company. So far so good.
Where it stops is the consolidated VAT-201. The standard regional report runs against one company at a time. For VAT groups we build a small custom report that unions the underlying tables across the group's member companies, eliminates intra-group supplies (which fall outside the scope of VAT for grouped entities), and outputs the group-level VAT-201. It's a one-week piece of work and we treat it as a standard add-on for grouped clients.
Two caveats. First, if your group spans the UAE plus another GCC country, those don't group — Saudi VAT is a separate jurisdiction with its own ZATCA filing, even under common ownership. Second, the FTA can refuse a VAT group application or require restructuring; we recommend the legal/tax advice on whether to group come from your auditor before we wire the ERP for it.
Questions
FAQ.
Does ERPNext support the UAE FTA VAT return format out of the box?
ERPNext ships a UAE-VAT regional report that maps invoices to the FTA return boxes (standard-rated supplies, zero-rated, exempt, reverse-charge imports, etc.) by emirate. It is not a one-click filing — the UAE FTA does not yet expose a public API for VAT-201 submission — but the report consolidates the data you need to key into the EmaraTax portal each period.
Can ERPNext auto-file VAT returns with the FTA?
No. As of 2026 the FTA does not publish a documented automated submission API for VAT-201. Returns still go through the EmaraTax portal manually. ERPNext gets you to the line items; a human submits.
Does ERPNext support designated zones (Free Zones treated as outside UAE for VAT)?
Yes — through Tax Categories and Tax Rules. You configure each customer or supplier with a category that triggers different tax templates (e.g. zero-rated for designated-zone goods). Setup needs care: services into designated zones are still standard-rated, only goods qualify, so we tag items as well as parties.
How does ERPNext handle reverse-charge VAT on imports and overseas services?
You create a separate purchase tax template that applies output VAT and recoverable input VAT in the same entry. The net cash effect is zero, but the values flow into boxes 3 (standard-rated supplies) and 9/10 (recoverable VAT on imports) of the VAT-201. We set this up as standard for every UAE client.
How is UAE VAT in ERPNext different from Saudi ZATCA?
Two big differences. First, Saudi mandates Phase 2 e-invoicing with cryptographic stamps and ZATCA Fatoora integration; the UAE has its own e-invoicing programme on a different timeline (see our UAE e-invoicing guide). Second, KSA uses 15% VAT vs UAE's 5%. Same Tax Template machinery, different rates and different downstream integrations.
Can one ERPNext instance handle multiple UAE entities under a VAT group?
Yes — you run multi-company in a single ERPNext instance with a shared Chart of Accounts approach, then consolidate VAT reporting at the group level. We build a custom consolidated VAT report for VAT-grouped clients because the standard report runs per-company.
What about VAT on partial-exemption businesses (e.g. residential property)?
ERPNext does not auto-calculate the input-tax apportionment ratio. We typically build a small custom DocType that holds the period's residual ratio and a script that applies it during VAT return preparation. This is a standard ask and we have a pattern for it.
Does ERPNext store the FTA TRN on customer/supplier records?
Yes — the standard Customer and Supplier DocTypes have a Tax ID field; we rename the label to "TRN" for UAE clients and validate the 15-digit format with a client script. The TRN flows through to invoice PDFs as required by Article 59 of the Executive Regulations.
How long does a VAT-ready ERPNext setup take?
For a fresh install on a single UAE entity, the VAT-specific configuration is typically 2–3 days of consultant work on top of base implementation. Multi-entity / VAT-group setups add a week. The longer pole is always Chart of Accounts and opening balances, not the tax engine itself.
— Ready when you are
Talk to a real ERP consultant.
A 30-minute call is the fastest way to know if we're a fit. No slides.