UAE PINT-AE Mandate
UAE E-Invoicing on Odoo
The UAE's e-invoicing mandate phases in from July 2026 for B2B and B2G transactions, with the framework adapted from Peppol PINT-AE. Every VAT-registered business in scope will need to issue e-invoices through an accredited service provider, with continuous transaction control by the Ministry of Finance. Odoo handles the entire flow — from invoice generation in the UAE-required XML format through to ASP submission and archive — natively inside your ERP.
Last reviewed:
What it is
The UAE Ministry of Finance announced the UAE e-invoicing framework, adapted from Peppol International (PINT-AE), with a phased rollout from July 2026 for B2B and B2G transactions. 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
-
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 (taxable to taxable) and B2G (taxable to government entity) flows supported as the mandate phases in. B2C (taxable to consumer) handled per Ministry of Finance guidance once finalised.
-
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 (PPF), 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 fall into the mandate's phase 1 (July 2026 B2B/B2G), phase 2, etc., based on Ministry of Finance announcements as they're released. Output: written rollout roadmap aligned to phases.
-
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 at the mandate effective date for your phase. 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
Every VAT-registered UAE business that will fall into the mandate's phase 1 (B2B and B2G from July 2026). 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; B2G suppliers to UAE government entities where the mandate hits first; 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?
The Ministry of Finance has announced a phased rollout starting July 2026 for B2B and B2G transactions in scope. B2C and broader B2B coverage will follow in subsequent phases. The exact phase-by-phase scope (which TRN ranges, which transaction types, which thresholds) is being finalised by the Ministry of Finance. We track these announcements and update implementation guidance as they're released.
-
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?
Single-entity, single-ASP setup: AED 25,000–50,000 (USD 6,800–13,600) fixed-price. Multi-entity UAE groups using multiple ASPs: AED 50,000–120,000 (USD 13,600–32,600). 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 Ministry of Finance is publishing scope criteria with the phased rollout — typically TRN bands, transaction-type categories, and volume thresholds. Our discovery includes a scope check based on current Ministry of Finance guidance. 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.