Magento 2 UAE E-Invoicing & VAT Compliance

Key Features

UAE FTA-compliant tax invoice PDF layout — supplier and recipient details, sequential invoice number, date of supply, and 'Tax Invoice' designation per FTA requirements

Tax Registration Number (TRN) printed on every invoice, credit note and applicable order document, configurable per store view

Per-rate VAT breakdown table showing taxable amount, 5% standard-rate VAT, zero-rated and exempt lines, and total VAT in AED

Bilingual Arabic/English invoice templates with correct RTL rendering, Arabic numerals option, and a font stack that ships Arabic glyphs in the PDF

Peppol PINT-AE / UBL document model so invoices can be serialized to the structured e-invoice format the UAE mandate is built on

REST and GraphQL endpoints exposing the structured invoice payload for your Accredited Service Provider (ASP) connector or middleware to consume

Credit-note (credit-memo) handling that mirrors the original tax invoice, references it, and produces a compliant Tax Credit Note document

Reverse-charge mechanism support for applicable B2B/import scenarios — flags the line, suppresses output VAT correctly, and annotates the invoice

Admin configuration under Stores → Configuration with ACL-guarded access, multi-store-view TRN/branding, and per-website toggles

Cron-backed queue for e-invoice payload generation and retry, with admin visibility into generated/failed documents

Multi-store-view and multi-website aware — correct TRN, legal entity and language per storefront

Built on Magento service contracts and plugins (di.xml) rather than core file overrides, so it survives Magento and Adobe Commerce upgrades

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

UAE Magento merchants face two overlapping obligations: today's FTA VAT invoice rules (TRN display, 5% VAT breakdown, supplier/recipient details, AED amounts) and the upcoming UAE e-invoicing mandate built on the Peppol PINT-AE standard and the 5-corner Accredited Service Provider model. Magento Open Source and Adobe Commerce core produce a generic invoice PDF — it does not carry a Tax Registration Number, a proper tax summary, Arabic content, or any structured e-invoice payload. This module closes that gap.

ECOSIRE builds this as a proper Magento 2 module under app/code/Ecosire/UaeEinvoicing — not a theme hack. It uses service contracts and plugins/interceptors on the invoice and credit-memo flows, observers on sales_order_invoice_save_after, a di.xml-wired tax-summary service, and admin configuration under Stores → Configuration guarded by ACL. Invoice and credit-note PDFs are regenerated through a custom renderer so every document shows your TRN, a per-rate VAT table, totals in AED, and an Arabic/English bilingual layout with correct RTL handling.

For e-invoicing we build the document model toward Peppol PINT-AE / UBL, expose it via REST and GraphQL so an Accredited Service Provider (ASP) connector or your middleware can pull a structured invoice, and add cron for queued generation and retry. Because the FTA programme is still rolling out, we scope the exact transmission integration with you at build time and ship what your phase requires.

This is build-to-order: you tell us your Magento edition, version and tax setup; we build, install on your environment (or staging first), test against your real catalog, and hand over with documentation. It is not an instant Adobe Commerce Marketplace download.

What you get

A custom Magento 2 module (app/code/Ecosire/UaeEinvoicing) compatible with your declared Magento Open Source or Adobe Commerce version

Installation on your environment — staging first where available — including setup:upgrade, di:compile and static-content deploy

Configured FTA-compliant tax invoice and credit-note PDF templates with your TRN, legal entity and bilingual layout

REST/GraphQL endpoints and the Peppol PINT-AE / UBL document model wired to your tax configuration

Admin user guide plus technical README covering configuration, ACL roles, cron jobs and the e-invoice payload structure

Post-deployment support window with bug fixes and a documented update path as the UAE e-invoicing mandate phases roll out

Who this is for

UAE-based Magento store owner

Runs a Magento Open Source or Adobe Commerce store in the UAE and needs invoices that satisfy FTA VAT rules now and the e-invoicing mandate next — without re-platforming or stitching together fragile overrides.

Finance / VAT compliance manager

Owns FTA filing and audit readiness. Needs every invoice and credit note to carry the TRN, a correct 5% VAT breakdown in AED, and reverse-charge handling, with a clean structured payload ready for e-invoicing submission.

Magento developer or agency lead

Manages the store's codebase and wants a properly architected module (service contracts, plugins, di.xml, ACL) that survives upgrades and exposes clean REST/GraphQL — not core hacks they have to untangle later.

How Magento 2 UAE E-Invoicing & VAT Compliance Compares

Criterion	ECOSIRE	Custom Build	Competitor
UAE FTA-compliant tax invoice layout with TRN	Included	Partial support	Partial support
Per-rate 5% VAT breakdown in AED on every document	Included	Partial support	Partial support
Bilingual Arabic/English invoices with correct RTL/glyph rendering	Included	Partial support	Not included
Peppol PINT-AE / UBL structured e-invoice document model	Included	Not included	Not included
REST & GraphQL exposure for ASP / middleware integration	Included	Partial support	Not included
Credit-note and reverse-charge handling	Included	Partial support	Partial support
Built on plugins/service contracts (upgrade-safe, no core hacks)	Included	Partial support	Partial support
Installed, tested and supported on your store by the vendor	Included	Not included	Not included

Frequently Asked Questions about Magento 2 UAE E-Invoicing & VAT Compliance

How long does delivery take, and what do you need from me?

Because this is build-to-order, a typical build runs about 2–4 weeks depending on your Magento edition, version, tax configuration and whether ASP/e-invoice transmission is in scope for your phase. To start we need your Magento Open Source or Adobe Commerce version, your TRN and legal entity details, your current tax/VAT setup, and access to a staging environment. We confirm a firm timeline after a short scoping call.

What ongoing support and updates do I get after launch?

Every build includes a post-deployment support window covering bug fixes and configuration help. The UAE e-invoicing programme is still phasing in, so we provide a documented update path and offer ongoing maintenance to keep the module aligned with the Peppol PINT-AE standard and your applicable mandate phase. Updates beyond the initial window are handled as a maintenance agreement.

Does this work on Magento Open Source as well as Adobe Commerce?

Yes. The module is built on standard Magento 2 architecture — service contracts, plugins/interceptors, observers, di.xml and ACL — so it runs on both Magento Open Source and Adobe Commerce. We build against your specific version and test on your environment. If you use Adobe Commerce features such as advanced B2B or shared catalogs, we account for them during scoping.

Will this fully submit my invoices to the FTA automatically?

We build the structured Peppol PINT-AE / UBL document model and expose it via REST/GraphQL so it is ready for transmission through an Accredited Service Provider (ASP). Actual transmission goes through an ASP under the UAE 5-corner model. We scope and integrate your chosen ASP connector at build time where that is in scope; we do not claim to be the FTA's clearance platform ourselves.

Does it handle Arabic invoices and credit notes correctly?

Yes. We ship bilingual Arabic/English templates with proper RTL rendering and a font stack that embeds Arabic glyphs in the generated PDF, so Arabic content renders correctly rather than as missing boxes. Credit notes (credit memos) reproduce the same bilingual layout, reference the original tax invoice, and are produced as compliant Tax Credit Notes.

Will it survive Magento upgrades?

That is a core design goal. We avoid core file overrides and instead use plugins/interceptors, observers, service contracts and di.xml wiring, all inside an isolated module under app/code. This keeps your invoicing customizations separate from core, so Magento and Adobe Commerce upgrades are far less likely to break them. We also hand over documentation so your team or ours can maintain it.