This is a build-to-order module, not an instant download. Typical lead time is one working week. After purchase we run a short requirements workshop (your Odoo version and edition, entities, TRNs, chart of accounts, and which Accredited Service Provider you contract with), then build the module, test it against the ASP sandbox, run UAT with your finance team, and cut over to production aligned to your FTA go-live wave. Complex multi-entity or multi-ASP setups sit at the longer end of the range.

Every engagement includes a post-launch support window with an agreed SLA and a named contact, covering bug fixes and adjustments to keep you aligned with FTA and Peppol PINT AE rule changes during that period. Because the FTA programme and Peppol specifications continue to evolve, we also offer an ongoing maintenance retainer for rule updates, ASP changes, and version upgrades across Odoo 17, 18 and 19 after the initial window ends.

Yes. Under the UAE's five-corner Peppol model, structured invoices are exchanged and reported to the FTA through Accredited Service Providers — Odoo cannot connect to the network directly. This module is the connector and transformation layer inside Odoo; you contract separately with an accredited ASP, and we integrate against their sandbox and production endpoints. The module is ASP-agnostic, so we build to whichever provider you choose.

We build the module for Odoo 17, 18 or 19, on either Community or Enterprise, targeting your specific database. It extends native accounting (account.move, account.tax, fiscal positions) rather than replacing it, so it works alongside your existing invoicing. We confirm your exact version and edition during the requirements workshop and scope the build accordingly.

No. Your team keeps invoicing exactly as they do today. The module adds a compliance layer that transforms each posted invoice into Peppol PINT AE / UBL XML, validates it against FTA rules, and submits it to your ASP. Finance sees a submission status on each invoice and clear field-level messages if data needs fixing before it reaches the tax authority — there is no parallel system to maintain.

The module ships with 5% UAE VAT tax codes, groups and fiscal positions mapped to Peppol tax category codes, and validates each invoice (TRN format, correct rate, zero-rated / exempt treatment) before submission. If the ASP or FTA rejects a document, the reason is logged to the invoice chatter, the invoice returns to a resubmittable state, and scheduled jobs retry transient failures automatically — so nothing silently fails.