Connect your Odoo ERP to the UAE eInvoicing system: PINT AE structured XML, an accredited service provider (ASP) connection, Tax Data Document reporting to the FTA, and an exception queue your finance team can actually run. Built and supported in the UAE by certified engineers. Trusted by 500+ businesses since 2014.
Odoo cannot make you UAE e-invoicing compliant on its own. The UAE eInvoicing system is a Peppol-based five-corner (DCTCE) model: your invoice must leave Odoo as PINT AE structured XML, travel through an Accredited Service Provider appointed from the Ministry of Finance list, reach your buyer's ASP, and be reported to the Federal Tax Authority as a Tax Data Document. Odoo's standard Peppol service and UAE localisation do not cover the PINT AE format or the UAE ASP channel out of the box.
The work is therefore an integration project: map Odoo data to the PINT AE fields, connect Odoo to your chosen ASP's API, handle acknowledgements and rejections inside Odoo, and clean the master data that will otherwise fail validation. Nifty IT delivers that integration end-to-end. Request a free Odoo readiness check or call 055 125 6266.
If you run Odoo in the UAE, the mandate lands on your ERP, not on your accountant. Every sales invoice and credit note that Odoo produces has to become a validated structured document before it is legally issued — and the moment your ASP rejects one, somebody in your finance team needs to see that rejection, understand the error code, fix the source record and re-transmit. None of that exists in a stock Odoo database today.
This page explains what changes, what Odoo already gives you, what has to be built, and how long it takes. It is written for finance leads and IT managers who need to brief a board, not for tax lawyers.
The UAE did not build a government portal you upload invoices to. It adopted the Peppol network with a fifth corner for the tax authority. Here is where Odoo sits in that chain.
Odoo raises the invoice and generates PINT AE XML from your posted document.
Accredited Service Provider validates, signs and transmits over the Peppol network.
Receives, validates and converts for delivery. It does not have to be the same ASP as yours.
Receives the structured e-invoice into their own ERP or accounting system.
Receives the Tax Data Document reported by the ASP in near real time.
Corner 1 is the only corner you control — and it is the one that decides whether everything downstream succeeds. A malformed TRN or a missing tax category in Odoo becomes a rejection at corner 2.
Partly — and the part it does not cover is the part that makes you compliant. This is the honest breakdown we give every client before quoting.
| Requirement | Standard Odoo | What Is Actually Needed |
|---|---|---|
| UAE VAT, TRN fields and tax invoice layout | Covered | The UAE localisation handles VAT codes, TRN capture and standard tax invoice printing. This part is genuinely fine. |
| Peppol network access | Partial | Odoo operates a Peppol access point service for European formats such as BIS Billing 3.0, XRechnung and NLCIUS. That service is not the UAE ASP channel, and Odoo does not appear on the Ministry of Finance pre-approved service provider list. |
| PINT AE structured XML generation | Not standard | A UAE e-invoicing module that builds PINT AE UBL 2.1 from the Odoo account.move record, including every mandatory field in the current UAE Data Dictionary. |
| ASP connection and transmission | Not standard | Authenticated API integration to your appointed ASP, with retry logic, queueing and idempotency so a network blip never double-issues an invoice. |
| FTA Tax Data Document reporting | Not standard | Handled through the ASP, but Odoo must supply complete, correctly typed data and record the reporting outcome against the invoice. |
| Rejection handling and re-transmission | Not standard | Status field, error log, exception list view, and a re-send action — so finance staff resolve failures without opening a support ticket. |
| Inbound e-invoice reception | Partial | Odoo can consume structured bills, but UAE reception through your ASP needs routing, supplier matching and a recipient reporting acknowledgement. |
| Archiving inside the UAE | Partial | Depends entirely on your hosting. Odoo Online region, Odoo.sh region or on-premise location must be reviewed against the in-country storage requirement. |
Assessment current as of August 2026. Odoo's localisation coverage and the MoF service provider list both change — we re-verify both at the start of every project.
Almost every rejection we see traces back to data that was perfectly acceptable for a PDF invoice and is not acceptable for a structured one.
Blank TRNs, TRNs typed into the wrong field, spaces and dashes, or one TRN duplicated across several contacts. PINT AE validation rejects all of it — and the invoice is not legally issued.
Custom Odoo taxes built over the years rarely carry the category, exemption reason or reverse charge flag the schema expects. Zero-rated and exempt lines are the usual failure point.
Lines with no description, no unit of measure, or a quantity of zero pass happily in Odoo and fail structured validation immediately.
Line totals that do not sum to the header, or per-line rounding that drifts by a fils, are a classic rejection. Odoo's rounding method has to be set deliberately, not left at default.
Without an exception queue, a failed transmission is invisible. You discover it when the 14-day window has passed and the penalty clock has already started.
Bespoke sales flows, third-party POS connectors and Excel imports that write directly to journal entries all sidestep the e-invoicing pipeline unless they are explicitly covered.
One project, delivered by engineers who work in Odoo every day and have read the Ministry's guidelines rather than a summary of them.
We connect to your database and produce a written gap report: version and hosting review, TRN completeness across all customers, tax code mapping to VAT categories, master data quality scores, and every custom flow that bypasses the standard invoice model.
Free for UAE businesses, and yours to keep even if you appoint someone else.
A UAE e-invoicing module that generates compliant PINT AE UBL 2.1 XML from Odoo invoices and credit notes, with every mandatory field of the current UAE Data Dictionary mapped, validated against the schema before it leaves your server, and versioned so a Data Dictionary update is a configuration change rather than a rebuild.
Authenticated API connection between Odoo and the ASP you appoint from the Ministry of Finance list. Queueing, retries, idempotency keys, credential rotation and full request/response logging — so that when a document is questioned twelve months later, you can prove exactly what was sent and when.
Every invoice carries a transmission status. Rejections land in a dedicated queue with the ASP error code translated into plain language and a direct link to the field that caused it. One button re-transmits. No developer required for day-to-day operation.
The unglamorous work that decides the project. Bulk TRN validation and correction, duplicate contact merging, tax code restructuring, unit of measure standardisation and rounding policy configuration — scripted, reviewed with your finance team, and executed in a staging copy first.
The mandate covers recipients too. We configure reception of supplier e-invoices through your ASP into an Odoo purchase journal, with automatic vendor matching, purchase order reconciliation and the recipient-side acknowledgement recorded.
The voluntary pilot has been open since July 2026 and it is the cheapest possible place to find your data problems. We onboard you through EmaraTax with your service provider and run real documents end-to-end while mistakes still cost nothing.
Where your Odoo database physically lives now matters. We review Odoo Online region, Odoo.sh deployment or on-premise infrastructure against the in-country storage requirement and, where needed, plan and execute the migration.
UAE-based support after 1 January 2027, when a rejected invoice becomes an urgent commercial problem rather than a test finding. Monitoring on the transmission queue, monthly compliance reporting, and schema updates applied as the Ministry publishes them.
Phase membership is set by annual revenue. If you are near the AED 50 million line, plan for Phase 1 — the cost of being early is a few weeks of project time; the cost of being late is a monthly penalty.
| Phase | Who | Appoint an ASP by | Mandatory go-live | Start now? |
|---|---|---|---|---|
| Pilot (voluntary) | Any business that opts in | Before joining | Open since 1 July 2026 | Join the Pilot |
| Phase 1 | Annual revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 | Urgent — Get Quote |
| Phase 2 | All other businesses in scope, below AED 50 million | 31 March 2027 | 1 July 2027 | Get Quote |
| Phase 3 | Government entities | 31 March 2027 | 1 October 2027 | Get Quote |
The Phase 1 ASP appointment deadline was extended from 31 July 2026 to 30 October 2026; the 1 January 2027 go-live was not moved. Dates are per Ministry of Finance announcements current as of August 2026 — always confirm against mof.gov.ae before acting.
Readiness assessment, TRN and tax code remediation, decision on hosting. This is the longest part of the project and the only part nobody can do for you at the last minute.
Select a provider from the Ministry's pre-approved list, sign, obtain API credentials, and let us build and test the Odoo connection in a staging database.
Businesses with revenue of AED 50 million or more must have appointed an accredited service provider. Missing this carries a monthly penalty under Cabinet Decision No. 106 of 2026.
Real documents through the pilot, side by side with your existing process. Accounts staff learn the exception queue while a rejection still has no consequence.
From this date, invoices from Phase 1 businesses must be issued and transmitted through the e-invoicing system within 14 days of the transaction.
Everyone else in scope. If you are below AED 50 million, your ASP deadline is 31 March 2027 — which means your Odoo work needs to start in the first quarter of 2027 at the latest.
The penalties are structured to punish delay rather than mistakes — which is precisely why the ERP work should start before the ASP deadline, not after it.
| Failure | Penalty | What it means for an Odoo user |
|---|---|---|
| Not appointing an ASP by the deadline | AED 5,000 per month of delay | A commercial decision, not a technical one — but you cannot test the Odoo integration until it is made. |
| Not implementing the e-invoicing system in time | AED 5,000 per month of delay | This is the ERP project. Six to ten weeks of work becomes a recurring monthly cost if it slips. |
| Failure to issue and transmit an e-invoice in time | AED 100 per invoice, capped at AED 5,000 per calendar month | Exactly what an invisible failed transmission queue produces — at volume, you hit the cap in days. |
| Failure to issue and transmit an electronic credit note in time | AED 100 per credit note, capped at AED 5,000 per calendar month | Credit notes are frequently overlooked in ERP scoping. They are in scope and they are penalised. |
| Not notifying the FTA of a system failure | AED 1,000 per day of delay | You need monitoring that tells you the integration is down, and a documented notification procedure. |
| Not notifying your ASP of changes to registered data | AED 1,000 per day of delay | Trade licence renewals, address and TRN changes need an owner and a checklist. |
Summarised from Cabinet Decision No. 106 of 2026 as published. Penalty schedules are revised from time to time — confirm current amounts with the FTA or your tax advisor before relying on these figures.
Note: Nifty Information Technology LLC is an IT and ERP integration company, not a tax agency. We build the technical capability inside Odoo to meet the mandate; we do not provide tax or legal advice. Confirm your phase, scope and obligations with your registered tax agent or the Federal Tax Authority.
Priced per project in AED after the readiness assessment, because the honest answer depends on how many customers lack a valid TRN and how much of your invoicing runs through custom code.
| Package | Best for | Included | Typical duration | Price |
|---|---|---|---|---|
| Readiness Assessment | Any UAE business running Odoo | Database review, TRN and tax code audit, gap report, phase confirmation, effort estimate | 3–5 working days | Free |
| Core Compliance | Standard Odoo, clean processes, single company | PINT AE generation, ASP integration, status tracking, exception queue, user training | 6–8 weeks | Get Quote |
| Compliance + Remediation | Databases with master data debt | Everything in Core, plus bulk TRN correction, duplicate merging, tax restructuring, rounding policy | 8–12 weeks | Get Quote |
| Enterprise / Multi-Company | Multiple entities, branches or free zone structures | Per-entity ASP routing, inter-company handling, consolidated monitoring, multi-currency | 10–16 weeks | Get Quote |
| Legacy Migration + Compliance | Moving to Odoo from Tally, QuickBooks or an older ERP | Odoo implementation, UAE localisation, data migration and e-invoicing delivered as one programme | 12–20 weeks | Get Quote |
| Managed Compliance Support | Live environments after go-live | Queue monitoring, schema updates, incident response, monthly compliance report | Monthly retainer | Get Quote |
ASP subscription fees are billed by your accredited service provider directly and are separate from Nifty's integration fees. We are happy to sit in on ASP selection calls with you.
Prefer email? [email protected] — we usually reply within one business day.
Six stages, run in a staging copy of your database until the day we switch it on in production. Your live invoicing is never the test environment.
We review your Odoo version, hosting region, chart of accounts, tax configuration and customer master. You receive a written gap report with a remediation list, an effort estimate and a clear statement of which phase and deadline apply to you.
You appoint the accredited service provider — it is your contract and your compliance obligation. We help you compare the pre-approved providers on the things that actually matter for an Odoo integration: API quality, sandbox availability, error reporting depth, throughput limits and UAE support hours.
Scripted TRN validation and correction, duplicate contact merging, tax code mapping to VAT categories, unit of measure standardisation and rounding policy. Reviewed line by line with your finance team, executed in staging, then re-run against production on cutover.
PINT AE generation is mapped field by field against the current UAE Data Dictionary and validated against the schema locally before anything is sent. We test against your real invoice patterns — multi-currency, reverse charge, zero-rated exports, discounts, deposits and part credits.
End-to-end transmission through your ASP's sandbox and then the live pilot. We deliberately break things — wrong TRN, missing tax category, network timeout — so your team sees every failure mode and knows what to do before it matters.
Production cutover with monitoring on the transmission queue from day one, a named engineer for the first month, documented procedures for system failure notification, and schema updates applied as the Ministry publishes them.
Based in Deira, Dubai since 2014, serving more than 500 UAE businesses. We invoice in AED with VAT, we are in your time zone, and we come on site across Dubai, Abu Dhabi and Sharjah when a go-live needs someone in the room.
E-invoicing touches your ERP, your hosting, your network and your backups. We already deliver managed IT, cloud, security and backup services — so nobody gets to say the problem belongs to another vendor.
Our scope is built from the Ministerial Decisions, the UAE Data Dictionary and the MoF guidelines — not from a competitor's blog post. When the rules are updated, we tell you what changed and what it costs.
The readiness assessment produces a real document with real numbers. You decide with the effort estimate in front of you rather than discovering the master data problem in week six.
Compliance you need a developer for is compliance that fails in month two. Everything we build is designed to be run by accounts staff, with training and documentation included.
We are not reselling one provider's product, so our advice on ASP selection has no commission attached. If you have already appointed one, we integrate with it.
Our base. Trading, logistics, contracting, retail and professional services firms across Deira, Business Bay, JLT, DIFC, Al Quoz and the free zones — including multi-entity groups with mainland and free zone companies invoicing each other.
Government-adjacent suppliers, energy services and contracting businesses where B2G invoicing and the October 2027 government phase both come into play. Remote delivery with scheduled on-site visits for workshops and go-live.
Manufacturing, distribution and wholesale operations in SAIF Zone, Hamriyah and the industrial areas — typically high invoice volumes, which makes the exception queue and throughput limits the deciding factors in ASP selection.
Not completely. Odoo's UAE localisation covers VAT configuration, TRN fields and standard tax invoice formats, and Odoo operates a Peppol access point service for European formats such as BIS Billing 3.0, XRechnung and NLCIUS. What it does not provide as standard is PINT AE structured XML generation, a connection to a UAE accredited service provider, Tax Data Document reporting, or rejection handling inside Odoo. Those require a UAE e-invoicing module and an integration project. As of August 2026, Odoo does not appear on the Ministry of Finance pre-approved service provider list, so you appoint an ASP separately and Odoo connects to it.
PINT AE stands for Peppol International Invoice — United Arab Emirates. It is the UAE's national specification of the Peppol invoice standard, expressed as UBL 2.1 XML with a defined set of mandatory fields published in the UAE Data Dictionary. The point of a structured format is that machines validate it: the tax authority, your ASP and your buyer's system all read the same fields the same way. A PDF invoice, a scanned copy, a Word file or an Excel sheet is not an e-invoice under the mandate, no matter how detailed it is.
Yes. Under Ministerial Decision No. 243 of 2025, both issuers and recipients must appoint an accredited service provider from the list published by the Ministry of Finance. Your ERP does not replace that obligation — the ASP validates your document, signs it, transmits it over the Peppol network and reports the Tax Data Document to the Federal Tax Authority. Odoo is corner one of the five-corner model; the ASP is corner two. You and your buyer do not need to use the same provider.
It depends on three things: how clean your master data is, how many entities you invoice from, and how much of your invoicing runs through customisations rather than standard Odoo. A single company on a standard database with valid customer TRNs is a materially smaller project than a five-entity group with a decade of accumulated tax codes. That is exactly why the readiness assessment is free — we would rather price from evidence than from assumptions. Note also that your ASP charges its own subscription, billed separately by them.
Six to eight weeks for a healthy single-company Odoo database, eight to twelve weeks where master data needs remediation, and ten to sixteen weeks for multi-entity groups or a migration from a legacy system. The build itself is rarely the constraint — data clean-up and getting ASP credentials issued are what set the calendar. If you are a Phase 1 business reading this in late 2026, start now rather than in December.
We work on Odoo 17, 18 and 19, on Odoo Online, Odoo.sh and on-premise deployments, in both Community and Enterprise editions. If you are on an older version, we will tell you honestly whether to build e-invoicing on it or use the mandate as the reason to upgrade — an unsupported version with a compliance integration bolted on becomes expensive to maintain. Hosting region also needs review against the requirement to keep invoice data inside the UAE.
You can, but the calendar is tighter than it looks. Phase 2 businesses must appoint an ASP by 31 March 2027 and go live on 1 July 2027 — and by then every ASP and every Odoo partner in the country is working through a queue created by Phase 1. Master data clean-up is also unaffected by which phase you are in: the TRNs that are missing today will still be missing in March. Joining the voluntary pilot early costs very little and removes all of the deadline risk.
A rejected document has not been legally issued, and the clock on the transmission window keeps running. This is why the exception queue matters more than any other part of the build. In our integration, every invoice carries a transmission status, rejections appear in a dedicated Odoo list with the ASP error code translated into plain language and a link to the offending field, and one button re-transmits after the fix. Without that, failures are silent until a penalty makes them loud.
The mandate's initial focus is business-to-business and business-to-government transactions, and Ministerial Decision No. 243 of 2025 sets out specific exclusions in Article 4 — including government entities acting in a sovereign capacity, certain international airline transactions and VAT-exempt financial services. Treatment of business-to-consumer transactions has been signalled for a later stage. Because scope is defined by the Ministry and revised over time, confirm your own position with a registered tax agent — and design the Odoo integration so that adding B2C later is a configuration change rather than a second project.
Often, yes — because you are going to pay for a compliance project either way, and doing it on a system you were planning to replace means paying twice. Migrating to Odoo with UAE localisation and e-invoicing delivered as a single programme typically runs twelve to twenty weeks, so a Phase 2 business starting in late 2026 has a comfortable path to the July 2027 deadline. We will tell you plainly if staying put and integrating your current system is the better commercial decision.
Yes. The obligations under the decision apply to recipients as well as issuers — you must appoint an ASP, process incoming electronic invoices and credit notes through the system, and meet the reporting timelines. Practically, this means Odoo needs to receive structured supplier invoices into a purchase journal, match them to vendors and purchase orders, and record the acknowledgement. It is a commonly under-scoped half of the project.
Yes. We are ASP-neutral and take no commission from any provider, so we integrate with whichever pre-approved service provider you have contracted. What we will ask for early is sandbox access, API documentation and a technical contact — the quality of those three things is the single biggest predictor of how smoothly the integration goes.
Ministerial Decision No. 243 of 2025 requires electronic invoice data to be stored within the UAE for the retention period set by the Tax Procedures Law. For Odoo users this makes hosting a compliance question rather than an IT preference: the region of your Odoo Online or Odoo.sh deployment, or the location of your on-premise servers and backups, all need to be reviewed. We include that review in the readiness assessment and plan a migration where one is needed.
Cabinet Decision No. 106 of 2026 sets administrative penalties including AED 5,000 per month of delay for failing to appoint an accredited service provider by the deadline, AED 5,000 per month of delay for failing to implement the e-invoicing system in time, AED 100 per electronic invoice or credit note not issued and transmitted within the prescribed timeframe (capped at AED 5,000 per calendar month), and AED 1,000 per day of delay for failing to notify the FTA of a system failure or your service provider of changes to registered data. Confirm current amounts with the Federal Tax Authority or a registered tax agent.
For the free readiness assessment: your Odoo version and hosting details, read access to a copy of the database or a guided screen-share, your approximate annual revenue so we can confirm your phase, and a list of any custom modules that touch invoicing. That is enough for us to produce the gap report. Send it to [email protected], or WhatsApp 055 125 6266 and we will take it from there.
Find out in 45 minutes. We review your database, confirm which phase applies to you, and give you a written gap report with an effort estimate — free, with no obligation, and yours to keep even if you appoint someone else to do the work.
Nifty Information Technology LLC — Burj Nahar Mall, M2 Floor, Office D2-4, Deira, Dubai · [email protected] · 055 125 6266