Odoo ERP Implementation in Saudi Arabia: ZATCA, Arabic, Cost, Timeline

Most guides to Odoo in the Kingdom stop at "it is ZATCA compliant." The harder questions are which version, how many journals to onboard, who runs payroll and what it costs. Our Odoo implementation services team answers those first.

This guide is for owners, CFOs and IT leads planning a first Odoo rollout in Saudi Arabia. If the February 2027 deadline is your main worry, read our ZATCA Wave 25 plan for Odoo too.

What does an Odoo ERP implementation in Saudi Arabia include?

An Odoo ERP implementation in Saudi Arabia covers the usual sales, stock and accounting setup plus Saudi localization, ZATCA e-invoicing, Arabic layouts and local payroll. The table maps each workstream to its modules.

Workstream	What it covers	Odoo modules
Saudi accounting	Chart of accounts, 15% VAT, zero-rated, exempt, reverse charge	l10n_sa
VAT reports	VAT and withholding returns, Excel and PDF	l10n_sa_reports
ZATCA Phase 2	B2B clearance, B2C reporting, UBL 2.1 XML	l10n_sa_edi
Point of sale	Simplified tax invoices from each till	l10n_sa_pos, l10n_sa_edi_pos
Withholding tax	Preloaded 5%, 15% and 20% rates	l10n_sa_withholding_tax
Payroll	GOSI, WPS, allowances, end of service	l10n_sa_hr_payroll

The Odoo Saudi Arabia localization documentation lists these modules. The ZATCA modules are open source, but the Saudi reports and payroll are Enterprise features, so budget for Enterprise.

Should a Saudi implementation start on Odoo 19 or Odoo 20?

Start a new Saudi implementation on Odoo 19 or Odoo 20; both carry the current Saudi localization, and payroll needs usually decide between them. Do not start a new project on Odoo 17 or older.

Factor	Odoo 19	Odoo 20
Release	September 2025	September 2026
Standard support	To September 2028	Three years from release
Saudi accounting and ZATCA	Same documented features	Same documented features
Saudi payroll	GOSI rules, WPS, end of service	Adds GOSI API and Nitaqat report
Currency rates	Standard providers	Adds Saudi Central Bank (SAMA)
Best for	Teams that want a settled release	Projects needing richer payroll

We compared the 19.0 and 20.0 Saudi accounting pages in Odoo's documentation source and found them identical. The Odoo 20 Saudi payroll documentation adds GOSI integration and a nationalization report.

Odoo 20 also adds SAMA as a currency rate service, as listed in our Odoo 20 accounting release notes.

Older versions cause trouble. One Odoo 17 Community user hit a server error during Fatoora onboarding, and an Odoo 15 user could not find the e-invoicing modules at all.

How does Odoo ZATCA Phase 2 onboarding fit into the project plan?

Odoo ZATCA Phase 2 onboarding is a workstream inside the implementation, not a final step: you design journals for it, test it in simulation, then onboard each journal in production.

ZATCA started Phase 1 on 4 December 2021 and Phase 2 in waves from 1 January 2023, per its e-invoicing roll-out phases page. Each wave is notified at least six months ahead.

ZATCA's Wave 25 announcement covers VAT-subject revenue above SAR 187,500 in any year from 2022 to 2025, with integration due by 1 February 2027.

Five Odoo rules shape the design:

• Journals: each sales journal is onboarded separately, so choose one central journal or one per branch early.
• Branches: each branch uses the parent VAT number and its own Commercial Registration Number.
• Modes: Sandbox and Simulation come first; after Production submits an invoice, you cannot switch back.
• OTPs: Fatoora one-time passwords expire after 60 minutes.
• POS: each till's invoice journal is onboarded, and every order needs a customer.

Response codes and a dated plan are in our Wave 25 guide. For GCC-wide rules, see Odoo for Middle East VAT and GCC compliance.

How does Odoo Arabic invoicing and localization work?

Odoo Arabic invoicing works at two levels: a company setting that prints bilingual Gulf Cooperation Council layouts, and a language per customer and per user. Arabic is mandatory; English alongside is allowed.

Odoo's documentation states that tax invoices and simplified tax invoices, with their credit and debit notes, must be in Arabic. Switch on the Gulf Cooperation Council Format in Accounting settings for invoices and in POS settings for receipts.

Arabic is also a full interface language. Odoo's language settings let each user choose, so the warehouse can work in Arabic while finance works in English.

Plan these master data fields into the migration:

• Company name: 63 characters or fewer, the ZATCA limit.
• Address: district, building number and plot identification.
• Identification: Commercial Registration Number plus the VAT number, with SAR as currency.
• Customers: the same fields on every B2B contact, or clearance fails.

Credit and debit notes need a ZATCA reason, and a global discount line must carry the 15% tax. Train finance on both.

Can Odoo run Saudi payroll with GOSI, WPS and end of service?

Yes for most companies: Odoo's Saudi payroll localization computes GOSI, exports WPS files and handles allowances, end of service and sick leave. It needs the Payroll app in Enterprise.

The Saudi payroll documentation lists what it handles:

• Employee data: nationality drives the GOSI rate; each employee needs a 10-digit Saudi National or Iqama ID and a trusted IBAN.
• Allowances: housing, transport and other allowances, plus yearly Iqama, medical insurance and work permit costs.
• GOSI: Odoo 20 fetches contribution rates for the annuities, occupational hazards and SANED branches through the GOSI API.
• WPS: a Saudi WPS export per payslip or pay run, structured to MHRSD guidelines.
• End of service: monthly provisions plus the final benefit by termination reason.
• Sick leave: 30 days fully paid, 60 more at 75%, then unpaid.

Odoo 20 also adds a nationalization percentage report for the Nitaqat program.

Run at least one parallel payroll month before go-live, with real salaries, real leave and a real WPS file.

Where should a Saudi Odoo database be hosted?

Odoo's cloud runs Middle East production in India and Saudi Arabia, with backups in Europe and Canada; if every copy must stay in the Kingdom, choose on-premise or a local private cloud.

Odoo's privacy policy lists those regions for Middle East and Southern Asia and says backup locations cannot be chosen or restricted.

Hosting also sets the plan: Odoo Online works on Standard, while Odoo.sh and on-premise need Custom. Our guide to Odoo Online vs Odoo.sh vs on-premise covers the trade-offs.

How much does Odoo implementation cost in Saudi Arabia?

Odoo implementation cost in Saudi Arabia follows our published ranges: US$3k to US$9k small, US$9k to US$27k mid-size and US$27k to US$150k+ large, plus licences. These are ranges, not quotes.

Project size	Implementation (USD)	Approx. SAR at 3.75	Typical timeline
Small	US$3k to US$9k	SAR 11,250 to 33,750	4 to 8 weeks
Mid-size	US$9k to US$27k	SAR 33,750 to 101,250	8 to 14 weeks
Large	US$27k to US$150k+	SAR 101,250 to 562,500+	12 to 24 weeks
Data migration	US$1.2k to US$9k	SAR 4,500 to 33,750	Inside the project

The riyal is pegged at 3.75 to the dollar, so the SAR column is a straight conversion. Our Odoo implementation cost guide explains what moves a project between bands.

On the Odoo pricing page, US prices billed yearly are US$31.10 per user a month for Standard and US$61.00 for Custom. Prices shown in Saudi Arabia can differ.

Illustrative example: 20 full users cost US$7,464 a year on Standard (about SAR 27,990) or US$14,640 on Custom (about SAR 54,900). Light Users list at US$8.90 a month.

Many branches or tills, a large expatriate payroll, retention billing or Arabic report redesigns push a project up a band. For a quick figure, try the Odoo implementation cost calculator.

How long does an Odoo implementation in Saudi Arabia take?

A Saudi Odoo implementation takes 4 to 8 weeks for a small company, 8 to 14 weeks for mid-size and 12 to 24 weeks for a large group, with ZATCA tests and payroll parallel runs inside.

A typical sequence:

1. Discovery: processes, branches, journals, tills, users and ZATCA wave confirmed in writing.
2. Design: chart of accounts, taxes, journals, Arabic templates and payroll structure.
3. Build: configuration, integrations and any custom modules.
4. Data migration: customers, products, open items and opening balances with full Saudi addresses.
5. ZATCA testing: sandbox, then simulation on a database copy for every invoice type.
6. Training: finance on credit notes and retries; cashiers on customer capture.
7. Go-live: production onboarding journal by journal, plus a payroll parallel month.
8. Hypercare: daily review of ZATCA warnings and rejections.

Today, 1 February 2027 is about 13 weeks away. A Wave 25 company starting now should go live with accounting, invoicing and POS first, then add inventory depth or payroll in phase two.

For phases and roles in more depth, see our Odoo ERP implementation guide.

Which Saudi industries need extra Odoo setup?

Retail, food service, contracting, distribution and professional services each carry a Saudi edge case that adds setup time. The table shows where the effort goes.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Retail chains	Many tills, Arabic receipts, B2C reporting	l10n_sa_edi_pos with GCC receipt format	Onboard every till, test reprints
Restaurants and cafes	High receipt volume, combos, delivery apps	POS reporting with customer capture	Map delivery orders into journals
Contracting	Retention, advance payments, expatriate payroll	Retention tax group, Saudi payroll	Model retention, run parallel payroll
Wholesale and distribution	B2B clearance, credit notes	Clearance flow, ZATCA reason codes	Clean customer records first
Professional services	Withholding on non-resident fees	Withholding tax, reverse charge	Set fiscal positions and WHT rules

How do you choose an Odoo partner in Saudi Arabia?

Choose an Odoo partner in Saudi Arabia on proof of ZATCA onboarding, Arabic documents and Saudi payroll, not on office location. Ask every candidate:

• Version: which Odoo version do you propose, and why?
• ZATCA: how many journals and tills will you onboard, and who runs simulation?
• Arabic: will you show a sample bilingual invoice and receipt before sign-off?
• Payroll: who builds GOSI and WPS, and how many parallel runs are included?
• Support: who watches ZATCA rejections after go-live, and for how long?

How iVentureTeam helps with Odoo ERP implementation in Saudi Arabia

iVentureTeam runs Saudi Odoo projects from discovery to cleared invoices and a correct first WPS file. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Scoping: version choice, journal and branch design, ZATCA wave check and a written cost range.
• Localization: Saudi taxes, withholding and retention, Arabic invoice and receipt templates.
• ZATCA onboarding: sandbox, simulation and production for every sales journal and POS.
• Payroll: GOSI, WPS, allowances and end of service, with parallel runs.
• Training and support: our Odoo ERP training covers finance, cashiers and payroll officers, followed by hypercare.

Odoo ERP implementation in Saudi Arabia case study: a Middle East retailer

A Middle East retail business needed bilingual Arabic and English POS receipts from Odoo without changing the cashier's workflow. It ran on Odoo 11 and predates Phase 2, but Saudi retailers face the same receipt problem today.

The stock Odoo 11 receipt printed in one language. Product names, taxable and non-taxable amounts, subtotal and total had to read correctly in both scripts, with right-to-left Arabic on thermal printers.

We rebuilt the template so six elements render in both languages on one slip, and routed printing through a Raspberry Pi per POS station. Delivery took three weeks.

Read the bilingual Arabic and English POS receipts case study.

The bottom line on Odoo ERP implementation in Saudi Arabia

Odoo 19 and Odoo 20 cover what a Saudi company needs, from ZATCA Phase 2 to Arabic invoices and GOSI payroll; the real work is journal design, clean data, testing and payroll parallel runs.

Confirm your ZATCA wave, decide on hosting, count journals and tills, and get a written range. If Wave 25 applies, put accounting and invoicing live first and phase the rest.

Ready to plan your Odoo rollout in Saudi Arabia?

Get a scoped plan for your version, journals, tills and payroll before you commit. Request a Saudi Odoo implementation plan, call +91-90235-15208, or email business@iventureteam.com.