UAE E-Invoicing (PINT AE) for Odoo 19 Community documentation

Who it is for: companies in the United Arab Emirates that run their invoicing in Odoo 19 and must prepare e-invoices for their ASP, and the accountants and partners who set them up.

The examples: the pictures show a demo company, Al Noor General Trading LLC in Dubai, in AED. Its names, TRNs and licence numbers are fictitious and only have the right format. It has eleven customer invoices and one credit note from 14 September to 29 October 2026; the documents were prepared on 30 October 2026 by Amira Saleh (administrator). The ASP is shown as Your appointed ASP and its answers were typed by hand: nothing was sent anywhere. The figures in the text are those of the pictures.

1. Unzip the package. Inside is taqnix_uae_einvoicing.zip; unzip it to get the folder taqnix_uae_einvoicing.
2. Copy the folder into one of the addons_path folders of your Odoo server and restart Odoo.
3. Log in as an administrator, activate Developer mode, open Apps and press Update Apps List.
4. Remove the “Apps” filter, search UAE E-Invoicing and press Install.

# or from the command line
./odoo-bin -c odoo.conf -d YOUR_DATABASE -i taqnix_uae_einvoicing --stop-after-init

After the installation:

1. Open Accounting → Accounting → E-Invoicing (UAE) → Settings and tick Use UAE e-invoicing for this company; enter the legal registration and the name of your ASP and press Save.
2. Press Tax categories and check the category of each sale tax (see Tax categories).
3. Optional: press PINT AE Schematron and install the official rules (see Install the official Schematron).
4. Fill in the identifiers of your customers (see Company and customer identifiers).

A document moves through the statuses Draft (made but invalid, or the invoice was reset), Ready (made and not invalid), Sent to ASP, then Accepted, Rejected or Error. Once a document is sent, its invoice cannot be reset to draft or deleted: correct it with a credit note.

On a customer, open the tab UAE E-Invoicing:

The emirate is read from the state of the address (Dubai, Abu Dhabi, Sharjah, Ajman, Umm Al Quwain, Ras Al Khaimah, Fujairah) and written with its PINT AE code (for example DXB). A foreign customer needs a state / region on its address.

Open Settings → Tax categories to see all sale taxes in one editable list. Pre-set the UAE taxes fills the category of the UAE taxes that have none; a category you chose is never overwritten. A tax without category blocks the file.

On a posted customer invoice or credit note of a company that uses UAE e-invoicing, open the tab UAE E-Invoicing. You see the transaction type (BTAE-02), the export flag, the credit note reason for a credit note, the UUID once the file was made, the e-invoice status and the Readiness checklist. When everything passes, press Generate e-invoice in the header.

The flags free trade zone, deemed supply, profit margin scheme, summary invoice, continuous supply, disclosed agent billing and e-commerce are shown under Not supported in this version: they are read-only and a document that would need them is blocked.

1. Open Accounting → Accounting → E-Invoicing (UAE) → Readiness, or select invoices in the list of customer invoices and choose Check e-invoicing readiness in the Action menu.
2. Choose the dates (or leave them empty) and keep Only documents not sent yet ticked.
3. Press Run the checks: the counts Checked, Ready, With errors and Generated appear with the list of problems (document, customer, level, message).
4. Press Generate the ready ones to make and validate the files of the invoices without errors.

A batch takes at most 2,000 documents; above that, choose a shorter period. The action Generate PINT AE e-invoices of the invoice list does the same without the dialog.

The tab Validation log of the document shows each check and every failed rule with its identifier. After you install the Schematron, or fix a customer, press Validate again (or Regenerate after a change of the invoice). A document already sent keeps the validation it had.

1. Install the Python package saxonche on the Odoo server and restart Odoo. The dialog shows saxonche installed when it is found.
2. Open E-Invoicing (UAE) → Settings → PINT AE Schematron.
3. Either download the file yourself from the official address shown (docs.peppol.eu/poac/ae/pint-ae/resources.zip) and upload it (Upload your file, then Install the uploaded ZIP), or tick Allow downloading the Schematron from docs.peppol.eu in the Settings and press Download from docs.peppol.eu (the server downloads it).
4. The SHA-256 of the ZIP is compared with the expected one of PINT AE Billing 1.0.4. Only the four compiled rule files and the unit code list are kept; their own SHA-256 is checked again before every use.
5. Press Validate again on the documents prepared before, or select them in the outbox and use the action Validate again.

Stop using the installed rules switches the Schematron off. The files stay on the server in the Odoo data folder (taqnix_uae_einvoicing/<database>/).

Open Accounting → Accounting → E-Invoicing (UAE) → Outbox. The list shows the document, the invoice date, the customer, the type, the total, the Validation and the Status badges, the ASP reference and the date it was generated. Rejected, error and invalid documents are red; accepted ones are grey.

Group by status, validation or customer; search by name, customer, ASP reference or UUID. Documents are created by the module only: there is no New or Delete button.

The UUID is made once from the database and the invoice and never changes, even when the file is regenerated. The tabs History and Note hold the log and a free note (managers).

1. Give the file to your ASP (portal, e-mail or the channel your ASP gives you).
2. On the document press Set status, choose Sent to ASP and type the reference the ASP gave you; press Apply.
3. When the ASP answers, press Set status again and choose Accepted, Rejected or Error with the ASP’s message.

A rejection or an error needs the ASP’s message. The reference is checked against the ASP reference format of the settings (# a digit, A a letter, * a letter or a digit). Nobody can change or delete the log.

In the outbox, select documents and choose Download XML files (ZIP) in the Action menu (at most 1,000 at a time). The ZIP holds one XML file per document and a manifest.json with, for each file, the document, type, UUID, SHA-256, status, validation and company, and the note that the files were prepared for the ASP and are not sent or certified. Validate again in the same menu re-validates the selection.

The file itself is a PINT AE Billing 1.0.4 UBL invoice or credit note: CustomizationID urn:peppol:pint:billing-1@ae-1, ProfileID urn:peppol:bis:billing, the transaction type flags, the UUID, the seller with endpoint scheme 0235 and its TIN, the TRN, the legal entity, the buyer, the tax totals and the lines. A document not in AED also carries the tax currency AED, the exchange rate, a second tax total in AED and the AED total.

Open Accounting → Accounting → E-Invoicing (UAE) → Settings:

The footer buttons open the Tax categories, Pre-set the UAE taxes and the PINT AE Schematron dialog.

Each user sees only the documents of the companies they have access to. The outbox records cannot be created, edited or deleted by hand, and the log can be neither changed nor deleted.

The 5% VAT of the standard rated total must equal the official tolerance (rule aligned-ibrp-s-09). With Odoo’s UAE default, Round per line, an invoice with many lines can drift: the module blocks it and asks you to set the tax rounding to Round Globally.

What was checked: seven reference documents made by the module (standard, credit note, zero rated, mixed exempt, out of scope 480, export in USD, reverse charge) pass the OASIS UBL 2.1 XSD and the official PINT AE 1.0.4 Schematron (both layers) with no failed rule; a broken file is reported invalid. The module has 163 automated tests, green on a fresh database.

What the module is not

Documents and scenarios not covered

Checks and validation

Points not confirmed by an official source (ask your ASP)

Dates to check

Per the Ministry of Finance decisions listed in the module notes (Ministerial Decision No. 244 of 2025 as amended by Ministerial Decision No. 66 of 2026), as read on 29 October 2026: businesses with revenue of AED 50 million or more had to appoint an ASP by 30 October 2026 and implement e-invoicing from 1 January 2027; the other businesses appoint an ASP by 31 March 2027 and implement from 1 July 2027 (government entities from 1 October 2027). These dates have already changed once: check the current text on the Ministry of Finance website and with your ASP.

Replace the folder with the new version, restart Odoo and run -u taqnix_uae_einvoicing. Your outbox, its log, the identifiers on the contacts and the tax categories are kept.

When you uninstall the module, the prepared XML files stay as attachments of their invoices; the outbox and its log are removed. The downloaded Schematron files stay in the Odoo data folder (taqnix_uae_einvoicing/<database>/): delete them by hand if you want.

Installation help and bug fixes are included for 6 months, with lifetime updates. Contact us through the marketplace page where you bought the module or write to support@taqnix.com with your Odoo version and a screenshot.