Electronic invoicing mandates are spreading across the Middle East and Eastern Mediterranean at a pace that would have been hard to imagine five years ago. What started as a modernization push by a handful of tax authorities has become a regulatory wave, with governments from Riyadh to Ankara requiring businesses to submit invoices through centralized digital platforms. For ERP vendors, this creates a straightforward challenge: either your software handles the local compliance requirements, or your customers have to find someone who can bolt it on. Odoo has chosen to address the gap directly, rolling out dedicated EDI documentation and localization support for Saudi Arabia, Jordan, Egypt, and Turkey in a single coordinated update.
Saudi Arabia and the ZATCA FATOORAH System
Saudi Arabia’s e-invoicing mandate is arguably the most ambitious in the region. The Zakat, Tax and Customs Authority, known as ZATCA, has been rolling out its FATOORAH system in phases since 2021, and by now the requirements are clear and non-negotiable. Every business-to-business and business-to-consumer invoice must be generated electronically, stamped with a cryptographic hash, and transmitted to ZATCA’s platform in near-real time. Phase two of the mandate tightened the screws further, requiring integration with ZATCA’s validation system so that invoices are verified before they’re even issued to the buyer.
Odoo’s Saudi localization now covers the full lifecycle of FATOORAH compliance. The system generates invoices in the XML format that ZATCA expects, applies the required QR codes and cryptographic stamps, and handles the API handshake with ZATCA’s clearance platform. For businesses already running Odoo in the Kingdom, this means the e-invoicing workflow lives inside the same accounting module they use for everything else — no third-party middleware, no manual exports to a separate compliance tool.
Jordan Joins the Mandate
Jordan’s Income and Sales Tax Department, the ISTD, has been building toward mandatory e-invoicing for several years, and the framework is now active for registered businesses. The Jordanian system is less technically complex than Saudi Arabia’s — there’s no real-time clearance model yet — but the reporting requirements are strict. Invoices need to follow a prescribed format, include specific tax identification details, and be available for audit through digital channels.
Odoo’s Jordanian localization handles the structural requirements: the right fields in the right format, proper tax breakdowns that match ISTD expectations, and export capabilities that satisfy the department’s submission protocols. It’s a less dramatic technical lift than the Saudi integration, but for businesses operating in Amman or across the broader Jordanian market, having this built into the ERP eliminates a compliance headache that previously required custom development or standalone invoicing software.
Egypt’s Tax Authority Portal
Egypt’s e-invoicing journey has been one of the more aggressive rollouts in the region. The Egypt Tax Authority, or ETA, began mandating electronic invoices for large enterprises in 2020 and has been progressively expanding the requirement to smaller businesses. Today, all registered taxpayers are expected to issue invoices through the ETA’s centralized e-invoice portal. The system requires digitally signed documents, real-time submission, and a specific UBL-based data format that the portal can validate automatically.
Odoo’s Egyptian localization addresses the full submission pipeline. Invoices generated inside Odoo are formatted to the ETA’s specifications, digitally signed using the taxpayer’s credentials, and pushed to the portal through its API. The practical effect is that an accountant in Cairo can issue an invoice from the same Odoo interface they use for purchase orders and bank reconciliation, and the compliance layer handles itself in the background. Given that the ETA has been increasingly aggressive about enforcement — including blocking non-compliant businesses from issuing tax invoices entirely — having this baked into the ERP rather than layered on top is a meaningful reduction in operational risk.
Turkey’s e-Fatura and e-Arsiv Systems
Turkey was actually ahead of most of its neighbors on electronic invoicing. The Revenue Administration, known as GIB, introduced the e-Fatura system for business-to-business transactions and the e-Arsiv system for business-to-consumer invoices years ago. What makes Turkey’s landscape unusual is the integrator model: businesses don’t connect directly to GIB but instead go through certified EDI integrators who handle the transmission and validation. Odoo’s Turkish localization currently works with a single integrator, which simplifies the initial setup but means businesses need to ensure their integrator agreement is in place before the Odoo connection can go live.
The e-Fatura format itself is based on UBL 2.1, and Odoo’s implementation generates the compliant XML, handles the digital signature requirements, and manages the acknowledgment workflow where the buyer confirms receipt through the same integrator channel. For companies doing business in Turkey, this is table-stakes functionality — you simply cannot operate without e-Fatura compliance — and having it native to the ERP removes what has traditionally been one of the more painful integration projects in the Turkish market.
Canadian EFT and Branch-Level Fiscal Configuration
Alongside the Middle Eastern and Turkish e-invoicing work, Odoo shipped two additional localization features worth noting. The first is Electronic Funds Transfer payment file generation for Canadian businesses. Canadian EFT follows specific formatting standards set by the Canadian Payments Association, and Odoo can now generate compliant payment files directly from the accounting module. This is particularly relevant for companies running payroll or vendor payments through Canadian banks, where the alternative has traditionally been manual file preparation or a separate payment processing tool.
The second addition is new guidance for branch-level fiscal localization. Many businesses operate across multiple tax jurisdictions — a company headquartered in Dubai with a branch in Riyadh and another in Cairo, for instance. Each branch may need its own chart of accounts, tax rules, and e-invoicing configuration. Odoo’s updated documentation walks administrators through setting up branch-specific fiscal localizations within a single database, which is considerably cleaner than the old approach of maintaining separate instances or relying on workarounds to handle multi-jurisdiction compliance.
The Bigger Picture
What makes this batch of updates significant isn’t any single country — it’s the pattern. Electronic invoicing mandates are becoming the norm rather than the exception in the Middle East and North Africa, and ERP vendors that don’t keep pace with these requirements effectively lock themselves out of fast-growing markets. Saudi Arabia alone represents one of the largest ERP opportunities in the region, and businesses there have zero tolerance for software that can’t handle ZATCA compliance natively.
For Odoo’s existing user base in the region, these updates mean fewer third-party dependencies and a more integrated compliance workflow. For businesses evaluating ERP options, the breadth of country-specific e-invoicing support is increasingly a deciding factor. The gap between ERP platforms that treat localization as a first-class concern and those that leave it to implementation partners continues to widen, and this update puts Odoo firmly in the former camp for four more markets.