Integrating UAE Peppol E-Invoicing with Odoo — What Developers and Implementers Need to Know
UAE mandatory e-invoicing went live in pilot phase on 1 July 2026. Every UAE VAT-registered business sending B2B invoices must now route them through the UAE Peppol network as PINT AE XML. For Odoo developers and implementers working with UAE clients, this creates a specific integration challenge — Odoo does not ship with a native UAE Peppol access point. The transmission layer has to be added…
On 1 July 2026, the UAE officially launched its mandatory e-invoicing system through the UAE Peppol network. This required all VAT-registered businesses sending B2B invoices to route them through this network as PINT AE XML. For developers and implementers working with UAE clients, this created a specific integration challenge because Odoo does not come with a native UAE Peppol connection.
The UAE Peppol Network follows a four-corner architecture. Corner 2, the Seller ASP (Accredited Service Provider), is where the developer integration point lies. This ASP is responsible for validating invoices against the PINT AE schema, handling the Peppol transmission, and returning a status response. To integrate Odoo with the ASP, a connector must be built or configured between the account.move model and the ASP API.
The PINT AE XML schema, which is the UAE's national extension of Peppol BIS Billing 3.0, consists of 17 mandatory fields. These include BT-1 (invoice number), BT-2 (invoice date), BT-5 (currency code), BT-27 (supplier name), BT-29 (supplier VAT number), BT-35 (supplier address), BT-44 (buyer name), BT-46 (buyer VAT number), BT-50 (buyer address), BT-52 (buyer city), BT-55 (buyer country code), BT-110 (sum of invoice line net amounts), BT-112 (invoice total VAT amount), and BT-131 (invoice line net amount).
Additionally, every invoice line must include one of four VAT category codes (S, Z, E, O) and use UN/CEFACT codes for unit of measure (EA).
To successfully integrate Odoo with the UAE Peppol network, developers must map the PINT AE fields to the Odoo data model. This involves creating custom fields for the UN/CEFACT codes, VAT category codes, and fiscal positions. Common data quality issues include missing buyer VAT numbers, combined address fields, missing UN/CEFACT codes, VAT category code mismatches, and unassigned fiscal positions. Addressing these issues requires bulk updates, migration scripts, custom fields, and bulk assignments.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
