$ 199.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1187 |
| Technical Name |
l10n_ae_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1187 |
| Technical Name |
l10n_ae_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
UAE E-Invoicing for Odoo
Federal Tax Authority compliant e-invoicing based on Peppol PINT AE and the 5-corner DCTCE model — generate, validate and submit through your Accredited Service Provider, directly from Odoo.
What It Does
This module makes Odoo ready for the UAE FTA e-invoicing mandate. It builds standards-compliant Peppol PINT AE (UBL 2.1) invoices, credit notes and debit notes, validates them against the PINT AE business rules, and submits them to your Accredited Service Provider (ASP) — corner 2 of the UAE 5-corner Decentralised Continuous Transaction Control and Exchange (DCTCE) model — for clearance, network delivery to the buyer and reporting to the FTA.
One-Screen Provider Setup
Configure your ASP endpoint, API key and sender ID, with a sandbox toggle and a one-click connection test.
Key Features
Peppol PINT AE UBL 2.1
Standards-compliant XML for invoices (388), credit notes (381) and debit notes (383) with the AE customization, TRN endpoints (scheme 0235) and VAT categories (standard, zero, exempt, reverse charge).
5-Corner ASP Submission
Submit documents to your Accredited Service Provider and poll clearance status, with full call logging, sandbox/production toggle and a scheduled status-poll job.
TRN Validation
15-digit UAE Tax Registration Number validation on the company and partners, surfaced as the Peppol electronic address.
Pre-Submission Validation
Checks PINT AE business rules (mandatory parties, totals coherence, VAT categories, credit-note references) before anything leaves Odoo.
QR & Status
Each invoice carries a QR payload and a live e-invoice status (To Send / Sent / Cleared / Rejected) on a dedicated tab.
Onboarding Wizard
A guided setup wizard captures the company TRN, emirate and ASP credentials in one step.
E-Invoice Status & QR on Every Invoice
A dedicated UAE E-Invoice tab on each invoice: status, ASP document ID, QR image and the generated payload.
Guided onboarding: company TRN, emirate and Accredited Service Provider credentials in one place.
Requirements
- Odoo 18.0 or 19.0 (Community or Enterprise).
- An account with an Accredited Service Provider on the UAE Peppol network.
- Python libraries: lxml, qrcode, requests (standard with most Odoo deployments).
Support
Email: odoo@gencbaris.com
Author: Baris Genc — gencbaris.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module