Magento 2 UAE E-Invoicing & VAT Compliance

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.

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.

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.

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.

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.

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.