A PDF invoice can be read by a person. An e-invoice in the UAE has to be read by machines: your ASP, the buyer's ASP, the buyer's ERP and the Federal Tax Authority. That only works if every invoice carries the same fields, in the same structure, with valid values. The Ministry of Finance published a data dictionary for exactly this purpose. Most of the effort of going live is making sure your ERP can fill it for every invoice, every time.
FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.
Key points
- A fixed data model. The UAE uses PINT AE, the UAE version of the Peppol invoice standard, with a published data dictionary.
- Master data drives it. Most fields come from customer, product and company records, not from the invoice screen.
- TRNs and endpoints. Buyer tax numbers and network identifiers are the most common gaps.
- Clean before you connect. A data clean-up in Odoo before onboarding prevents most rejections.
The data model in brief
UAE e-invoices follow PINT AE, a specialisation of the Peppol International invoice model for the UAE. The Ministry of Finance's data dictionary lists the fields, which are mandatory, which apply only in certain cases, and the allowed values. Some fields are familiar from any tax invoice; others, such as network identifiers and transaction type codes, are new for most companies.
PINT AE
The UAE invoice specification on Peppol
TRN
Seller and, for B2B, buyer tax registration numbers
AED
VAT amounts must also be stated in dirhams
Line level
VAT category and rate on every line
The field groups and where they come from in Odoo
| Group | Typical fields | Source in Odoo |
|---|---|---|
| Document | Invoice number, issue date, invoice type, currency, payment due date | Invoice header and journal sequence |
| Seller | Legal name, TRN, address, emirate, network endpoint ID | Company record |
| Buyer | Legal name, TRN for registered buyers, address, network endpoint ID | Customer record |
| Lines | Item description, quantity, unit of measure code, unit price, discounts, net amount | Invoice lines and product records |
| Tax | VAT category code, rate and amount per line and in total | Taxes and fiscal positions |
| Totals | Total excluding VAT, VAT total, total including VAT, amount payable, VAT in AED | Calculated by Odoo |
| References | Original invoice for credit notes, purchase order or contract reference | Reversed entry and customer reference fields |
The data dictionary also includes transaction type indicators for special cases such as free zone transactions, deemed supplies, the profit margin scheme and summary invoices. If any apply to your business, map them early.
The fields that fail most often
- Missing or invalid buyer TRNs for business customers.
- Buyer network endpoint IDs not known, so the invoice cannot be routed.
- Free text lines without a product, so units of measure and tax categories are missing.
- Units of measure that do not map to the standard codes, such as custom units like set or lot.
- Foreign currency invoices without the VAT amount in AED.
- Credit notes without a reference to the original invoice.

A data clean-up plan in Odoo
Before onboarding with your ASP, spend two to four weeks on data. It is the cheapest insurance against a painful go-live.
- Export all active customers and check TRNs against the FTA's verification service; mark consumers and foreign customers clearly.
- Complete addresses with emirate for every UAE customer and the company itself.
- Collect network endpoint IDs from your main B2B customers, or confirm with your ASP how they will be looked up.
- Replace free text invoice lines with service products, and map every unit of measure to the standard code.
- Review taxes and fiscal positions so every line gets the right VAT category automatically.
- Stop editing posted invoices; use credit notes from now on, so the habit is in place before go-live.
- Customers checked
- Products and units mapped
- Taxes reviewed
- Test invoices through the ASP
- Go live
Where this fits
This is the data side of the project. The provider side is in how to choose an Accredited Service Provider, and the deadlines and penalties are in UAE e-invoicing from 2027. Your VAT return will draw on the same data, as explained in preparing VAT 201 from Odoo.
Companies that clean their data first usually go live in weeks. Companies that connect first and clean later spend months handling rejections one invoice at a time.
FlexCode prepares your Odoo data for UAE e-invoicing
We audit customers, products, units and taxes against the UAE data dictionary, fix the gaps and test with your ASP before go-live.
Frequently asked questions
What standard do UAE e-invoices use?
PINT AE, the UAE specification of the Peppol International invoice model, with a data dictionary published by the Ministry of Finance.
Does every invoice need the buyer's TRN?
For VAT-registered business buyers, yes. Consumers and foreign buyers are handled differently.
What is a network endpoint ID?
The identifier that lets the Peppol network route an invoice to the buyer's ASP.
Can I keep free text lines on invoices?
It is risky. Lines without a product often lack the unit and tax data required. Use service products instead.
Does Odoo hold all the required fields?
Most of them, across company, customer, product, tax and invoice records. Some identifiers may need to be added with your ASP connector.
Talk to us about how Odoo fits your business. Book a free call
Sources
This article explains the rules in general terms and is not tax or legal advice. Check the details for your company with your tax adviser.
Run invoicing, stock and accounts from one system.
FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.