Mandatory e-invoicing in the UAE: how to prepare Odoo, 1C, and other accounting systems

An electronic invoice under the UAE's new system is a structured data set exchanged between the supplier and buyer and submitted to the Federal Tax Authority. The Ministry of Finance specifically states that a PDF, Word file, image, scan, or email is not an eInvoice by itself.

The system primarily covers B2B and B2G transactions, except in specifically defined cases. Exchange is based on OpenPeppol and the national PINT AE specification. Therefore, the accounting system must generate a complete data set, send it to an accredited provider, receive technical statuses, and retain the processing history.

An accredited provider provides access to the e-invoicing infrastructure but does not fix processes or data within the company. Before connecting, determine where the original invoice is created, which system stores the parties’ details, who handles errors, and how the received document becomes an accounting entry.

Currencies, discounts, advance payments, credit notes, intercompany transactions, and cross-border operations require separate checks. If the rules are not aligned, the connected system will reject documents or move manual work from email to an integration error queue.

Odoo supports EDI and Peppol for several countries, but standard Peppol functionality does not confirm readiness for UAE national requirements. In the current Odoo 18 documentation, the UAE is not included in the published list of countries for standard Peppol registration, while UAE rules require appointing a provider from the Ministry of Finance list.

In practice, you need to verify the localization and capabilities of the selected ASP, then determine the integration method: a direct API or a separate middleware service. If necessary, add missing fields, validation rules, an exchange queue, and clear business-user statuses in Odoo. Learn more about system implementation and customization on the page Turnkey Odoo.

Having CIS EDI in a 1C configuration does not mean it complies with the UAE model: formats, operators, and transmission rules differ. However, replacing the core ERP is usually unnecessary; an integration layer can be created between 1C and an accredited ASP.

If a group uses 1C, Odoo and other systems simultaneously, the owner of each data type is defined before development. Details, tax categories and amounts must not be edited independently in multiple sources.

The preparation principle remains unchanged:

• identify the source of mandatory fields
• align the data with PINT AE
• configure integration with an accredited ASP
• receive incoming documents
• process technical statuses

An ERP may have a localized module, a ready-made provider adapter, or only a general integration interface. Choose the architecture after checking the specific version, transaction volume, number of legal entities, and ASP capabilities—not just the platform name.