When exactly does the UAE e-invoicing mandate become mandatory?

Under Ministerial Decisions 243 and 244 of 2025: voluntary use and a pilot from 1 July 2026. Businesses with annual revenue of AED 50 million or more must appoint an ASP by 30 October 2026 (extended from 31 July) and issue e-invoices from 1 January 2027. Other businesses appoint an ASP by 31 March 2027 and go live on 1 July 2027. Government entities go live on 1 October 2027.

What's the difference between UAE e-invoicing and Saudi ZATCA?

Different specifications and different submission models. UAE uses PINT-AE (Peppol-based, adapted) with ASP intermediaries. Saudi ZATCA uses its own XML schema with direct submission to Fatoora. Both achieve the same regulatory goal but through different technical implementations. Odoo's e-invoicing modules handle both regimes in one instance for multi-country groups.

Do we need a specific ASP, or can we use any?

Use any FTA-accredited Service Provider. The ASP marketplace is competitive with several providers offering similar services. Odoo integrates with multiple ASPs; you pick based on your operational preferences (existing relationships, pricing, support quality). We can recommend ASPs based on your specific entity structure during discovery.

What invoice fields are required by PINT-AE?

PINT-AE is based on Peppol BIS Billing 3.0 with UAE-specific extensions. Standard fields: supplier and buyer TRN, supplier and buyer name and address, invoice number and date, supply date, currency, line items with quantity / unit / price / tax / total, tax breakdown by rate, payment terms. UAE-specific extensions: emirate of supply, certain mandatory categorisations. Odoo's UAE localisation pre-populates these from existing master data.

What happens to existing Odoo VAT invoice templates?

The current VAT invoice template (bilingual Arabic/English) remains as the customer-facing PDF. The PINT-AE XML is generated alongside the PDF and submitted to the ASP — the customer doesn't see XML, your finance team and the ASP do. The PDF can be enhanced with the ASP's confirmation reference and the e-invoice unique identifier post-go-live.

How are rejections from the ASP handled?

Real-time rejection responses captured in Odoo. Each rejection has an ASP error code mapped to a triage owner — usually finance for tax-code mismatches, master-data team for buyer detail issues, ops for shipping/timing issues. Auto-retry handles transient ASP outages. Persistent rejection types feed into a regular review with the ASP.

Does this work with our existing accounting / VAT setup in Odoo?

Yes. The UAE e-invoicing module layers on top of the standard UAE VAT and CT setup. No re-implementation needed; existing tax codes, customer records, and invoice flows continue to work, with the XML generation and ASP submission added as an additional step.

What about credit notes and invoice amendments?

Credit notes (full and partial) are generated as separate e-invoice transactions in PINT-AE format with reference to the original invoice's unique identifier. Invoice amendments handled per FTA guidance — typically credit-note-plus-replacement-invoice rather than in-place modification. The workflow is built into the Odoo localisation.

What's the cost of implementation?

It depends on the number of UAE entities, how many ASPs you connect, your invoice volume, and how clean your customer TRN and address data is. We don't work from a price list: the free readiness check ends with a written plan and a fixed price for the setup, in AED, so the number you sign is the number you pay. ASP fees are separate (typically per-invoice or per-month from your chosen ASP — the marketplace is competitive). For existing Odoo customers, e-invoicing layering is cheaper.

How do we know which businesses are in scope?

The dividing line is annual revenue of AED 50 million: at or above it you go live on 1 January 2027, below it on 1 July 2027. Our discovery includes a scope check for each entity. If your business sits on a boundary, we err toward early readiness — getting ready a quarter early is cheap; getting caught after the mandate is expensive.

Are you an ASP yourselves?

No. We're an Odoo Gold Partner specialising in ERP implementation and integration. ASPs are a separate regulatory category. We integrate Odoo with whichever ASP you choose; we don't compete with them. This separation is intentional — it keeps our implementation incentives aligned with delivering you the best solution, not selling you our own intermediary service.

Does Odoo support UAE e-invoicing out of the box, and what do you add?

Odoo's UAE localisation already covers VAT, Corporate Tax and the bilingual invoice template. For e-invoicing we activate and configure the PINT AE localisation, connect Odoo to the Accredited Service Provider (ASP) you appoint, and set up validation handling with a triage queue and auto-retry. Invoices, ASP responses and the searchable 5-year archive all stay in Odoo, with no third-party middleware.

How long does UAE e-invoicing setup in Odoo take?

One entity using one ASP takes 4–6 weeks; a multi-entity UAE group using several ASPs takes 6–10 weeks. If you already run UAE VAT and Corporate Tax in Odoo, adding e-invoicing typically takes 2–3 weeks. Your ASP sets the floor: about 2 weeks for onboarding and 2 weeks for sandbox certification, so choose the ASP early.

What happens if we are not ready for UAE e-invoicing on our go-live date?

You risk per-invoice fines, plus VAT and Corporate Tax problems when invoices do not reconcile. Businesses with revenue of AED 50 million or more go live on 1 January 2027; other businesses go live on 1 July 2027. Getting ready a quarter early costs little. If your VAT setup needs work too, see UAE VAT and Corporate Tax in Odoo.

UAE E-Invoicing Mandate

UAE E-Invoicing on Odoo

UAE e-invoicing is set by Ministerial Decisions 243 and 244 of 2025: businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and issue e-invoices from 1 January 2027; everyone else goes live on 1 July 2027, and government entities on 1 October 2027. Invoices travel over a Peppol-based network in the PINT AE format. We connect Odoo to the ASP you appoint.

Last reviewed: October 12, 2026

What it is

The UAE Ministry of Finance set the e-invoicing framework in Ministerial Decisions 243 and 244 of 2025. It uses a Peppol-based exchange with the PINT AE data format and covers B2B and B2G transactions. The timeline: voluntary use and a pilot from 1 July 2026; businesses with annual revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and issue e-invoices from 1 January 2027; other businesses appoint an ASP by 31 March 2027 and go live on 1 July 2027; government entities go live on 1 October 2027. Every taxable supplier in scope must (a) generate invoices in the prescribed UBL-based XML format, (b) submit through an FTA-accredited Service Provider (ASP), (c) receive validation responses in near real-time, (d) archive invoices for the statutory retention period. Our Odoo build covers each step natively — XML generation, ASP integration, validation handling, and archive — with no third-party middleware.

Why it matters

The UAE e-invoicing mandate is non-negotiable for in-scope businesses and the penalties for non-compliance are substantial (per-invoice fines, plus VAT and CT implications when invoices don't reconcile). Beyond compliance: businesses that integrate e-invoicing into Odoo at go-live avoid the alternative — separate compliance vendors per requirement (UAE PINT-AE here, Saudi ZATCA next door, FatturaPA for European parents, IRN for Indian operations). Native multi-country e-invoicing in Odoo collapses the operational stack.

Features

What UAE E-Invoicing on Odoo does, capability by capability.
Capability	What it does
PINT-AE XML generation	Invoice XML built to the UAE PINT-AE specification (UBL 2.1-based) with every mandatory field — supplier and buyer TRN, supply date and emirate, line items with HS codes if applicable, tax breakdown by rate, payment means.
ASP routing	Routing through an FTA-accredited Service Provider (ASP) of your choice. Odoo integrates with the ASP's API for submission, validation response handling, and status tracking. Multi-ASP configurations supported for groups with multiple legal entities.
Real-time validation handling	Validation responses (accepted, rejected, validation warnings) captured inline. Rejected invoices route to a triage queue with the ASP's error code attached; auto-retry for transient failures; persistent issues escalate to finance.
B2B and B2G coverage	Both B2B (business to business) and B2G (business to government) flows, the two in scope. B2C invoices are outside the current mandate.
Multi-entity, multi-emirate	Multi-company UAE groups handled in one Odoo instance. Each legal entity submits through its own ASP relationship if needed; consolidated archive across entities.
Credit notes and amendments	Credit notes (full and partial) generated and submitted with reference to the original invoice. Amendment workflows aligned with FTA expectations.
5-year archive	Statutory archive retention with searchable retrieval by TRN, invoice number, supply date, or transaction reference. Documents retrievable on FTA audit request — including ASP confirmation receipts.
Multi-country compliance on one instance	If you operate in UAE plus Saudi Arabia (ZATCA), Italy (FatturaPA), India (GST IRN), France (Factur-X), Mexico (CFDI), or the EU more broadly, all regimes coexist on one Odoo instance with the right localisation per entity.

How it works

Mandate scope assessment

We confirm which of your entities go live on 1 January 2027 (revenue of AED 50 million or more), 1 July 2027 or 1 October 2027 (government), and the ASP deadline for each. Output: a written rollout roadmap.
ASP selection and onboarding

ASP shortlist based on your entity structure, invoice volume, and price preferences. Onboarding and credentials provisioning. Sandbox connection established for testing.
Odoo configuration

UAE PINT-AE localisation activated. ASP API endpoints, validation rules, and XML mapping configured. Existing customer/supplier records validated for required fields (TRN format, address completeness).
Sandbox testing

End-to-end test invoices submitted to ASP's sandbox. Validation flows exercised — clean invoices, deliberately-invalid invoices, credit notes, amendments. Triage queue tested with a representative sample.
Production go-live

Switch from sandbox to production credentials before your go-live date. First 30 days: real-time monitoring on every submission, daily status report on validation rates and any rejections.
Renewal + spec updates

PINT-AE specification will evolve through phases. We push spec updates into Odoo's localisation as the Ministry of Finance releases them. Bundled into ongoing Odoo support.

Deployment timeline

From a green-lit project: 4–6 weeks for single-entity, single-ASP setup; 6–10 weeks for multi-entity UAE groups using multiple ASPs. The hard floor is ASP onboarding (typically 2 weeks) and sandbox certification (2 weeks) — both gated by the ASP, not by us. For businesses already on Odoo with UAE VAT/CT in place, layering e-invoicing onto the existing setup is faster — typically 2–3 weeks.

Best for

UAE businesses with revenue of AED 50 million or more that must appoint an ASP by 30 October 2026 and go live on 1 January 2027, and those preparing for 1 July 2027. Especially valuable for: multi-entity UAE groups with both mainland and Free Zone subsidiaries; international operators with UAE subsidiaries managing PINT-AE alongside ZATCA, FatturaPA, GST IRN, or other regional e-invoicing regimes; suppliers to UAE government entities; high-invoice-volume businesses where bolt-on compliance tools would scale-fee unfairly.

Frequently asked questions

When exactly does the UAE e-invoicing mandate become mandatory?

Under Ministerial Decisions 243 and 244 of 2025: voluntary use and a pilot from 1 July 2026. Businesses with annual revenue of AED 50 million or more must appoint an ASP by 30 October 2026 (extended from 31 July) and issue e-invoices from 1 January 2027. Other businesses appoint an ASP by 31 March 2027 and go live on 1 July 2027. Government entities go live on 1 October 2027.
What's the difference between UAE e-invoicing and Saudi ZATCA?

Different specifications and different submission models. UAE uses PINT-AE (Peppol-based, adapted) with ASP intermediaries. Saudi ZATCA uses its own XML schema with direct submission to Fatoora. Both achieve the same regulatory goal but through different technical implementations. Odoo's e-invoicing modules handle both regimes in one instance for multi-country groups.
Do we need a specific ASP, or can we use any?

Use any FTA-accredited Service Provider. The ASP marketplace is competitive with several providers offering similar services. Odoo integrates with multiple ASPs; you pick based on your operational preferences (existing relationships, pricing, support quality). We can recommend ASPs based on your specific entity structure during discovery.
What invoice fields are required by PINT-AE?

PINT-AE is based on Peppol BIS Billing 3.0 with UAE-specific extensions. Standard fields: supplier and buyer TRN, supplier and buyer name and address, invoice number and date, supply date, currency, line items with quantity / unit / price / tax / total, tax breakdown by rate, payment terms. UAE-specific extensions: emirate of supply, certain mandatory categorisations. Odoo's UAE localisation pre-populates these from existing master data.
What happens to existing Odoo VAT invoice templates?

The current VAT invoice template (bilingual Arabic/English) remains as the customer-facing PDF. The PINT-AE XML is generated alongside the PDF and submitted to the ASP — the customer doesn't see XML, your finance team and the ASP do. The PDF can be enhanced with the ASP's confirmation reference and the e-invoice unique identifier post-go-live.
How are rejections from the ASP handled?

Real-time rejection responses captured in Odoo. Each rejection has an ASP error code mapped to a triage owner — usually finance for tax-code mismatches, master-data team for buyer detail issues, ops for shipping/timing issues. Auto-retry handles transient ASP outages. Persistent rejection types feed into a regular review with the ASP.
Does this work with our existing accounting / VAT setup in Odoo?

Yes. The UAE e-invoicing module layers on top of the standard UAE VAT and CT setup. No re-implementation needed; existing tax codes, customer records, and invoice flows continue to work, with the XML generation and ASP submission added as an additional step.
What about credit notes and invoice amendments?

Credit notes (full and partial) are generated as separate e-invoice transactions in PINT-AE format with reference to the original invoice's unique identifier. Invoice amendments handled per FTA guidance — typically credit-note-plus-replacement-invoice rather than in-place modification. The workflow is built into the Odoo localisation.
What's the cost of implementation?

It depends on the number of UAE entities, how many ASPs you connect, your invoice volume, and how clean your customer TRN and address data is. We don't work from a price list: the free readiness check ends with a written plan and a fixed price for the setup, in AED, so the number you sign is the number you pay. ASP fees are separate (typically per-invoice or per-month from your chosen ASP — the marketplace is competitive). For existing Odoo customers, e-invoicing layering is cheaper.
How do we know which businesses are in scope?

The dividing line is annual revenue of AED 50 million: at or above it you go live on 1 January 2027, below it on 1 July 2027. Our discovery includes a scope check for each entity. If your business sits on a boundary, we err toward early readiness — getting ready a quarter early is cheap; getting caught after the mandate is expensive.
Are you an ASP yourselves?

No. We're an Odoo Gold Partner specialising in ERP implementation and integration. ASPs are a separate regulatory category. We integrate Odoo with whichever ASP you choose; we don't compete with them. This separation is intentional — it keeps our implementation incentives aligned with delivering you the best solution, not selling you our own intermediary service.
Does Odoo support UAE e-invoicing out of the box, and what do you add?

Odoo's UAE localisation already covers VAT, Corporate Tax and the bilingual invoice template. For e-invoicing we activate and configure the PINT AE localisation, connect Odoo to the Accredited Service Provider (ASP) you appoint, and set up validation handling with a triage queue and auto-retry. Invoices, ASP responses and the searchable 5-year archive all stay in Odoo, with no third-party middleware.
How long does UAE e-invoicing setup in Odoo take?

One entity using one ASP takes 4–6 weeks; a multi-entity UAE group using several ASPs takes 6–10 weeks. If you already run UAE VAT and Corporate Tax in Odoo, adding e-invoicing typically takes 2–3 weeks. Your ASP sets the floor: about 2 weeks for onboarding and 2 weeks for sandbox certification, so choose the ASP early.
What happens if we are not ready for UAE e-invoicing on our go-live date?

You risk per-invoice fines, plus VAT and Corporate Tax problems when invoices do not reconcile. Businesses with revenue of AED 50 million or more go live on 1 January 2027; other businesses go live on 1 July 2027. Getting ready a quarter early costs little. If your VAT setup needs work too, see UAE VAT and Corporate Tax in Odoo.