Odoo UAE E-Invoicing Setup: PINT AE, ASPs and Odoo 19/20 Readiness

Most guides stop at "Odoo supports Peppol". That is true in Europe and misleading in Dubai. Our Odoo integration services team read the Ministry of Finance decisions, the Odoo source code and the Apps Store listings to write down what the setup really involves.

This guide is for finance leads, Odoo administrators and partners running Odoo 17, 18, 19 or 20 for a UAE entity. For the broader picture on VAT, corporate tax and Saudi ZATCA, read our guide on Odoo for UAE VAT, FTA e-invoicing and GCC compliance first.

How does UAE e-invoicing work in the five-corner model?

UAE e-invoicing is a decentralized exchange: your system sends a structured XML invoice to your ASP, the ASP delivers it to the buyer's ASP and reports tax data to the FTA. The Ministry of Finance calls this the Decentralized Continuous Transaction Control and Exchange model, or DCTCE.

The Ministry's eInvoicing programme page defines the roles. A PDF, a Word file, a scanned copy or an email is not an eInvoice. Only structured PINT AE data counts.

Two points matter for setup. The FTA does not clear invoices before you send them, so a rejection comes back from an ASP. And the buyer side is in scope too: your Odoo must receive supplier eInvoices, not only send them.

When is Odoo UAE e-invoicing mandatory, and what are the penalties?

Phase 1 starts on 1 January 2027 for businesses with revenue of AED 50 million or more, and the ASP appointment deadline for that group is 30 October 2026. The dates come from Ministerial Decision No. 244 of 2025, as amended in May 2026.

Revenue means gross income in the most recent accounting period. B2C transactions are excluded until the Minister decides otherwise, and transactions inside one VAT group get a 24-month grace period from 1 January 2027.

The penalties were published in December 2025 under Cabinet Decision No. 106 of 2025: AED 5,000 per month or part of a month for failing to implement or appoint an ASP on time, and AED 100 per late eInvoice or eCredit note, capped at AED 5,000 per month.

Two more fines apply: AED 1,000 per day for an unreported system failure, and AED 1,000 per day for not telling your ASP about changes to registered data. The Ministry's October 2026 programme deck cites a newer Cabinet Decision No. 173 of 2026, so confirm the current table before you budget.

One more rule changed on 1 October 2026. Ministerial Decision No. 197 of 2026 requires an eInvoice to be issued and transmitted within 14 business days of the transaction. Odoo invoices that sit in draft for a month become a compliance problem.

Is Odoo ready for UAE e-invoicing out of the box?

Odoo 19 and Odoo 20 cover UAE VAT accounting fully, but they do not generate PINT AE XML or act as a UAE Peppol access point, so an ASP connector is required. We checked the Odoo documentation and the 19.0 and 20.0 source code on 24 October 2026.

The Odoo 20 UAE localization ships three modules: l10n_ae for the chart of accounts and taxes, l10n_ae_reports for VAT and corporate tax reporting, and l10n_ae_pos for receipt compliance. Currency rates sync from the Central Bank of the UAE.

Odoo's own Peppol access point is free and available in Community, but the electronic invoicing documentation lists only European countries, Turkey and the United Kingdom as eligible. The supported formats are BIS Billing 3.0, XRechnung and NLCIUS. PINT AE is not among them.

In the source code, the account_peppol module lists 21 default countries, none in the GCC, and there is no PINT AE module in the 19.0 or 20.0 addons. What Odoo does know is the UAE Peppol scheme: 0235, "UAE Tax Identification Number (TIN)", appears in the partner Routing ID list.

Users have noticed. On the Odoo forum, an implementer asked whether Odoo plans to become an ASP or integrate with one; the replies confirm no official roadmap or pricing. Odoo S.A. is not on the Ministry's accredited list either.

What is PINT AE, and how does it map to Odoo invoice data?

PINT AE is the UAE specialization of the Peppol International Invoice format: structured XML with UAE-specific mandatory fields, tax categories and identifiers. Most of the data already lives in Odoo; the work is mapping it correctly and filling the fields Odoo does not hold today.

• Participant identifier: 0235 followed by the 10-digit TIN, which is the first 10 digits of the TRN. Odoo maps scheme 0235 to the partner VAT field, so your connector must write the TIN, not the full 15-digit TRN.
• Seller and buyer data: legal names in Arabic and English, addresses, TRN and registration identifiers, taken from company and contact records. They must match FTA records exactly.
• Invoice type codes: electronic Tax Invoice, Tax Credit Note, Commercial Invoice, Credit Note, plus the self-billed versions. Odoo's invoice and credit note types need a code mapping per scenario.
• Tax categories: standard 5%, zero-rated, exempt, out of scope and reverse charge, each with a category code on every line. Odoo's UAE tax groups map well if nobody has created ad hoc taxes.
• AED totals: VAT and total payable must always be presented in AED at the Central Bank rate, even on USD or EUR invoices. Odoo's automatic rates cover this if the rate date matches.
• Special endpoints: exports to buyers without a Peppol ID and deemed supplies use fixed endpoint values from the Ministry guidelines.

In our experience, master data causes more rejections than XML structure. Clean customer TRNs, addresses and legal names before any connector goes in. Our guide to how Odoo Accounting works shows where each field sits.

How do you choose an accredited service provider for Odoo?

Choose an ASP that is on the Ministry's accredited list, has a tested Odoo connector for your exact version, and can handle your credit note, free zone and multi-currency cases. Price per invoice matters less than the cost of a failed go-live.

The Ministry's list of accredited service providers showed 70 accredited ASPs and 3 pre-approved providers on 22 October 2026, including Zoho, Tally, SAP, Avalara, Pagero, ClearTax, Deloitte and EY. Pre-approved is not accredited.

The Odoo Apps Store listed 48 apps for "UAE e-invoicing" on 24 October 2026, from free base frameworks to paid connectors for named ASPs, most under US$300 per module. Check each listing's supported versions; many cover Odoo 17 and 18 but not 20 yet.

Questions to ask every shortlisted ASP:

• Status: accreditation number on the Ministry list, not a "pre-approved" press release.
• Odoo coverage: supported versions and editions, and who maintains the connector after an upgrade.
• Inbound: how supplier eInvoices reach Odoo, ideally as draft vendor bills with the XML attached.
• Rejections: how a negative status shows in Odoo and who fixes it.
• Pricing and data: subscription versus per-document fees, inbound costs, and where invoices are stored and retrieved for an FTA request.

How do you set up UAE e-invoicing in Odoo step by step?

The setup runs in ten steps: readiness check, master data, ASP selection, EmaraTax onboarding, connector installation, mapping, testing, go-live and monitoring. The FTA's own sequence is select an ASP first, contract and integrate, then complete EmaraTax.

1. Check your version: Odoo 17 standard support ended in September 2026. If you are on 16 or older, plan the upgrade now; our Odoo version support timeline shows every end date.
2. Clean master data: TRN, TIN, Arabic and English legal names, addresses and emirate on your company and on every B2B customer and supplier.
3. Review taxes: keep only the UAE localization taxes, assign the right tax group to each, and remove duplicates created over the years.
4. Shortlist ASPs: pick two or three from the Ministry list that support your Odoo version and hosting.
5. Test three hard scenarios: a partial credit note against two invoices, a free zone customer with beneficiary details, and a USD invoice with AED totals.
6. Sign and onboard: contract with one ASP, then log in to EmaraTax, open the E-INVOICING tile, select the ASP and proceed. Each entity onboards with one ASP only.
7. Install the connector: on Odoo.sh or on-premise, install the module on a staging branch first; on Odoo Online, deploy the middleware integration.
8. Map and configure: invoice type codes, tax category codes, endpoint identifiers, and the 14-business-day issuance window as an activity or alert.
9. Run a parallel period: send real invoices in the ASP sandbox for two to four weeks and reconcile status messages against Odoo.
10. Go live and monitor: add a Peppol status column to the invoice list, set a daily check for rejected documents, and document who handles failures.

Step 1 deserves a tool. Our free Odoo Health Check reports your version, modules and upgrade risks in a few minutes, which is exactly what an ASP will ask about.

What does Odoo UAE e-invoicing cost?

Expect three cost lines: the ASP's fees, the connector or integration build, and any Odoo upgrade or plan change needed to run it. The Ministry does not publish ASP prices, so get written quotes from at least two providers.

ASP fees are usually a subscription, a per-document fee, or both, plus onboarding. Ask for the price of inbound documents too, because receiving supplier eInvoices is part of the mandate.

Connector costs run from free to under US$300 per Apps Store module, plus configuration. An API integration on Odoo Online needs the Custom plan, listed on the Odoo pricing page at US$61.00 per user per month billed yearly in the US.

For the integration project itself, our published Odoo implementation cost ranges apply: a focused e-invoicing integration usually sits at the small end, US$3k to US$9k over 4 to 8 weeks, as an industry estimate. Complex multi-entity groups with custom builders cost more.

If your Odoo is older than 17, add the upgrade; our Odoo upgrade services page explains the steps.

Odoo Online, Odoo.sh or on-premise: which hosting works for UAE e-invoicing?

All three hosting options can comply, but Odoo Online cannot run Apps Store or custom modules, so Online users must connect through an ASP API or middleware. Odoo.sh and on-premise users can install a connector module directly.

Odoo's documentation states that Odoo Online is incompatible with custom and Apps Store modules. That rules out most of the 48 connectors for Online databases. The alternative is an ASP that offers an API-based integration, with the Custom plan providing Odoo's external API.

Hosting also affects records. The Ministry's guidelines treat storage as retrievability: records must be producible to the FTA wherever servers sit, and taxable persons keep eInvoices for 5 years after the tax period. Our guide to Odoo Online vs Odoo.sh vs on-premise covers the trade-offs.

Which industries feel UAE e-invoicing in Odoo the most?

Trading, logistics, construction and retail groups feel it first, because of volume, free zone scenarios and multi-entity structures. The table shows where projects usually need extra care.

How iVentureTeam helps with Odoo UAE e-invoicing

iVentureTeam prepares Odoo for the UAE mandate end to end: readiness review, ASP shortlist, connector or API integration, field mapping and supervised go-live. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Readiness review: version, modules, tax setup and master data checked against the PINT AE mandatory fields.
• ASP selection: a scored shortlist from the accredited list, with sandbox tests on your three hardest invoice scenarios.
• Integration build: connector configuration on Odoo.sh or on-premise, or an API integration for Odoo Online, through our Odoo integration services.
• Custom scenarios: our Odoo customization services handle free zone beneficiaries, self-billing and multi-ASP groups.
• Go-live and support: parallel run, cutover and a rejection-handling playbook for your finance team.

Odoo UAE e-invoicing case study: bilingual tax receipts for a Middle East retailer

Before e-invoicing, the same problem showed up on paper: a receipt that both the customer and the tax record could accept. A Middle East retail business on Odoo 11 Point of Sale printed single-language receipts that satisfied neither Arabic-speaking customers nor audit needs.

iVentureTeam rebuilt the POS receipt template so product name, taxable amount, non-taxable amount, subtotal and total print in both English and Arabic, with correct right-to-left rendering. Printing runs through a Raspberry Pi per POS station on standard thermal hardware.

The project took 3 weeks. Every sale now produces one receipt with itemized taxable and non-taxable amounts, the cashier workflow did not change, and future changes such as VAT fields are template edits, not projects. The same discipline applies to PINT AE: get the data right once.

Read the full bilingual Arabic and English POS receipts in Odoo case study.

The bottom line on Odoo UAE e-invoicing

Odoo gives you a compliant UAE accounting base, and an accredited service provider plus a tested connector gives you the exchange layer; neither works without the other. Treat it as an integration project with a hard date, not a module install.

If your revenue is AED 50 million or more, the ASP appointment deadline is days away and go-live is 1 January 2027. Everyone else has until 31 March 2027 to appoint and 1 July 2027 to comply. Start with master data and version; those take the longest to fix.

Ready to connect Odoo to a UAE accredited service provider?

Get a readiness plan with an ASP shortlist and a cutover date. Request an Odoo UAE e-invoicing readiness review, call +91-90235-15208, or email business@iventureteam.com.