ERP software in Saudi Arabia: a buyer's guide (ZATCA, data residency, Arabic)

Choosing ERP software in Saudi Arabia comes down to four checks before price: Phase 2 e-invoicing in the plan you will actually buy, where your records and backups are stored, Arabic across screens, invoices and reports, and a local partner who will implement and support it. A product that fails any one of them does not belong on the shortlist.

This guide explains each check, what the official rules say, how three well-known vendors document hosting and localisation, and how the price is built. It ends with a decision table and a checklist you can send to vendors as-is. Everything below was read on official and vendor pages on 14 October 2026; it is general information, not tax or legal advice.

What does ERP mean, and when does a company need one?

Microsoft describes enterprise resource planning (ERP) as business management software that integrates core processes across finance, supply chain, manufacturing, human resources, procurement and project management, and stores transactional and operational data in a central database [1]. In practice, the ERP system meaning is simple: one record for each customer, item, supplier and employee, used by every department instead of being typed again in each one.

Accounting software keeps the books. An ERP runs the operations that create the entries: the purchase order, the goods received, the stock movement, the sales order, the delivery and the invoice. That is why companies usually look at an ERP when several departments re-key the same data, when stock sits in more than one warehouse, when purchases need approvals, or when the group has more than one company.

Typical ERP modules:

• Finance: general ledger, receivables, payables, bank, fixed assets, VAT.
• Sales and point of sale: quotations, orders, invoices, returns and credit notes.
• Procurement: suppliers, purchase requests, approvals, purchase orders and supplier invoices.
• Inventory and warehouses: items, batches, transfers and stock counts.
• Manufacturing or projects: bills of materials, work orders, project budgets and billing.
• HR and payroll: employee files, leave and salaries, often through a local add-on.

The four Saudi checks before any ERP demo

Features look alike in every demo. These four checks decide whether a product can work for a company registered in the Kingdom.

A gap in one check is not always fatal: a partner app may add Phase 2 or Arabic. Get the fix, its price and the name of whoever maintains it in writing before the product stays on the list.

ZATCA e-invoicing inside an ERP: what the rules require

ZATCA's e-invoicing (Fatoora) rules came in two phases: generation from 4 December 2021 and integration from 1 January 2023, rolled out in waves [2][5]. On 24 July 2026 ZATCA set the criteria for Wave 25: taxpayers whose revenue subject to VAT exceeded SAR 187,500 in 2022, 2023, 2024 or 2025 will be notified to integrate their e-invoicing solutions with the Fatoora platform by no later than 1 February 2027 [6].

Phase 2 changes how invoices leave the system [2]:

• Standard tax invoices (usually business to business) are sent to ZATCA for clearance before they are shared with the buyer. ZATCA validates the XML and returns it with its cryptographic stamp and a QR code.
• Simplified tax invoices (usually business to consumer) are stamped by your own solution and reported to ZATCA within 24 hours of issue.
• Format: invoices are generated in XML, or as PDF/A-3 with the XML embedded, and credit and debit notes follow the same route.

An ERP issues invoices from several places: sales orders, the point of sale, project billing and returns. Every one of those paths must run through the compliant e-invoicing component. ZATCA's guideline notes that an e-invoicing solution may contain one or more units [2], and each unit is onboarded to Fatoora and receives its own cryptographic stamp identifier. Ask how many units your branches, tills and companies will need.

Customisation is the second risk. ZATCA lists functions an e-invoicing solution must not have, including deleting or editing issued invoices (cancellation is only by a credit note and a new invoice), resetting the invoice counter, running more than one invoice sequence per unit, and editing system logs [2]. Any change your implementer makes to sales or invoicing screens must leave those controls intact.

Who provides the ZATCA component differs by product. Microsoft lists Saudi Arabia among the countries where Business Central is localised by partners on its international version [4]. Odoo documents a Saudi e-invoicing module, recommends testing every invoicing flow in ZATCA's simulation portal first, and warns that switching the connection to production cannot be undone [7]. Ask who maintains that component when ZATCA updates its specifications, and how fast updates reach you.

ZATCA also publishes a list of solution providers that passed its qualification process. ZATCA describes the list as indicative and not an approval of any solution, and says taxpayers may use any provider whose solution meets the requirements [8]. Being on the list is a useful signal; a live test invoice is better evidence.

ERP data residency: where your records and backups live

Hosting is where ERP options narrow fastest, because an ERP holds everything: invoices, ledgers, contracts, salaries and customer files.

ZATCA's Guideline for Tax Invoicing and Records under VAT Provisions (version 3, May 2026) says records must be retained within the Kingdom in electronic form, and that for a taxpayer resident in the Kingdom the computer or server must be located in the Kingdom. A permanent establishment may keep a central system abroad if a workstation in the Kingdom gives access to all its VAT data. Records are kept in Arabic, for at least six years, and for 15 years for real estate [3].

ZATCA's e-invoicing guideline (May 2023) adds that invoices may be stored on servers in the Kingdom or in the cloud under the VAT rules, and that cloud-hosted data must be reachable through a direct link that can be given to ZATCA for audit [2]. Read the two documents together, and ask ZATCA or a licensed tax advisor how they apply to the hosting model you are considering.

Personal data adds a second test. Article 29 of the Personal Data Protection Law, as amended by Royal Decree M/148 dated 5/9/1444H, allows personal data to be transferred outside the Kingdom only for listed purposes, without harm to national security, with an adequate level of protection based on the competent authority's assessment, and limited to the minimum data needed [9]. Employee files and customer records in an ERP hosted abroad fall within that article. Our guide to data residency in Saudi Arabia covers those conditions in detail.

What three vendors document about hosting, as of 14 October 2026:

Backups deserve their own question. A primary database in one country with backups copied to another can still mean records leave the Kingdom.

Arabic support: more than a translated menu

Arabic in an ERP is a compliance point, not only a comfort. ZATCA's VAT guideline requires invoices to be issued in Arabic in addition to any other language, with every field of the tax invoice completed in Arabic; the Arabic text is the approved version and any other language counts as a translation. Records are kept in Arabic, and data entered into an electronic system must be in Arabic [3]. The printed or PDF version of an e-invoice must also be in Arabic, with Arabic or Hindi numerals both accepted [2].

Vendor language lists vary. Microsoft's table of Business Central platform and application languages did not include Arabic on 14 October 2026; the same page says partners can supply translations for languages Microsoft does not [4]. In that case the Arabic layer is part of the partner's work, and should be tested as such.

Test Arabic with your own data, not the demo company:

• an invoice to a customer whose name and address are in Arabic, printed and saved as PDF;
• a credit note for a partial return, in Arabic;
• a search for an Arabic item name with and without diacritics and the letter hamza;
• the VAT report and the general ledger exported in Arabic;
• a mixed Arabic and English item description on a purchase order.

Vendor management in an ERP: suppliers, approvals and input VAT

When buyers search for a vendor management system, they often mean the procurement side of an ERP: the supplier master file, purchase requests and approvals, purchase orders, goods receipts and matching the supplier's invoice before payment. A separate tool can do this, but then approved invoices must flow into the ERP rather than becoming a second ledger.

The Saudi angle is input VAT. ZATCA's VAT guideline expects a business to keep a valid tax invoice in Arabic to support its deduction of input tax [3], and buyers' right to deduct VAT charged by suppliers subject to e-invoicing depends on invoices that are electronically generated and meet the generation requirements [2]. Tax invoices between registered businesses carry the buyer's VAT registration number [3].

So the procurement module should:

1. store each supplier's VAT registration number and commercial details once, with approval for any change;
2. keep the supplier's e-invoice file (XML or PDF/A-3) attached to the purchase invoice;
3. flag supplier invoices that lack Arabic fields or your own VAT number before they are posted;
4. route purchases above an amount you set to a second approver;
5. match purchase order, goods receipt and invoice before payment is released.

These controls also shorten the VAT review, because every input-tax claim already has its supplier invoice attached.

What ERP software costs: licences are the visible part

ERP prices are usually per user, and the licence is only one line of the budget. Two published examples, as shown on 14 October 2026:

Odoo showed prices in US dollars when we opened the page, with a discount that applies for 12 months to the initial users ordered. Microsoft's figures come from its US pricing page, which notes that prices are for information and the final price appears at checkout; a Saudi partner may quote differently. Check whether VAT is included before you compare.

Illustrative example. A distributor in Dammam has six people who work in the ERP all day and ten who only approve purchases or look up stock. On Business Central Essentials with Team Members, the licences would be 6 × $80 × 12 = $5,760, plus 10 × $8 × 12 = $960, a total of $6,720 a year. That figure still excludes the partner's Saudi localisation, implementation, data migration, integrations, training and tax.

The full budget usually includes:

• subscriptions or licences, per user, per company or per module;
• Saudi localisation: the ZATCA e-invoicing component, Arabic layouts and VAT reports, if they are sold separately;
• implementation: process design, configuration, data migration and testing;
• integrations: bank, point of sale, e-commerce, payroll and government portals;
• hosting, if you choose a private cloud or your own servers;
• training and support after go-live, with response times in writing.

Decision table: which ERP deployment fits your company?

The hosting model drives much of the compliance work. Use this table to narrow the options before you compare features.

If none of the four fits a process that is central to how you make money, a ready-made ERP may need a custom module, or a separate system connected to it. Our guide to custom software development in Saudi Arabia explains when to buy, connect or build.

A buyer's checklist for ERP software in Saudi Arabia

Send these twelve questions to every vendor or partner in writing, and score the answers before you compare prices.

1. Phase 2 in the quote: is ZATCA Phase 2 e-invoicing included in the plan and edition you are quoting, or sold separately?
2. Every invoice path: do sales, point of sale, project billing and returns all issue invoices and notes through the compliant component?
3. Units: how many e-invoicing units will our branches, tills and companies need, and who onboards them on Fatoora?
4. Simulation test: can you send a standard and a simplified invoice from our test company to ZATCA's simulation portal before we sign?
5. Updates: who maintains the ZATCA component, and within what time after ZATCA changes its specifications?
6. Data location: in which country are the primary database and every backup, and can you confirm that in the contract?
7. Audit access: how would ZATCA reach our records, and can we export all invoices in XML for at least six years?
8. Arabic: can you show Arabic screens, invoice prints, credit notes and VAT reports with our own data?
9. Procurement: does the supplier file hold VAT numbers, and does the system match orders, receipts and invoices?
10. Personal data: where are employee and customer records processed, and what does that mean under PDPL Article 29?
11. Total cost: what are the licence, localisation, implementation, integration, hosting and support costs for three years, with and without VAT?
12. Exit: if we leave, in what format do we get our data and invoice archive, and within how many days?

Our guide to choosing a software company in Saudi Arabia suggests how to score written answers like these.

Your next step

This week, list every place your company issues an invoice today, every user who will need the system, and every branch and company. Then send the twelve questions above to three ERP vendors or partners, and ask each for a test invoice in ZATCA's simulation portal from the plan they quote. The ERP software in Saudi Arabia that passes all four checks with your own data is your shortlist; compare prices only within it. If a gap remains that no product covers, you can read about O AI, a software and AI company in Al Khobar, on our home page.