ERP System in Saudi Arabia: Requirements, Options and Implementation Guide

An ERP (enterprise resource planning) system is integrated business software that runs finance, procurement, inventory, sales, HR and operations on one shared database. In Saudi Arabia, an ERP must also handle ZATCA e-invoicing Phase 2, 15% VAT, Arabic and Hijri dates, WPS payroll through Mudad, GOSI contributions and PDPL-compliant data handling.

This guide is written for CFOs, CIOs and business owners planning an ERP in Saudi Arabia, whether replacing spreadsheets and disconnected accounting software or modernising a legacy system. It covers ERP modules, Saudi-specific requirements as of October 2026, the main platforms, custom versus off-the-shelf, implementation steps, cost drivers and the mistakes that sink projects.

What is an ERP system and what does it do?

An ERP system replaces separate tools for accounting, stock, purchasing, sales and HR with one platform where every transaction updates every department at once. When a branch sells an item, stock, revenue, VAT, cost of sales and the customer balance all change in a single step. The result is one version of the truth, faster month-end closing, fewer manual reconciliations and reliable data for decisions.

Core ERP modules

• Finance and accounting: general ledger, payables, receivables, banking, fixed assets, budgeting, multi-entity consolidation and VAT returns.
• Procurement: purchase requests, approvals, purchase orders, supplier management and three-way matching.
• Inventory and supply chain: warehouses, transfers, batches and expiry, landed costs and demand planning.
• Sales and CRM: quotations, orders, pricing, invoicing, collections and customer history.
• Manufacturing: bills of materials, work orders, production planning and quality.
• Projects and contracting: project costing, progress billing and retention, which matters for Saudi contractors.
• HR and payroll: employee records, contracts, leave, payroll, end-of-service benefits and government integrations.
• Reporting and BI: dashboards, KPIs and audit trails.

What Saudi-specific requirements must an ERP meet?

ZATCA e-invoicing Phase 2

Every sales invoice, credit note and debit note from your ERP must comply with ZATCA's e-invoicing rules. In Phase 2 the ERP generates XML invoices to ZATCA's UBL 2.1-based standard, applies cryptographic stamps and QR codes, sends B2B tax invoices for clearance before they reach the customer, and reports B2C simplified invoices within 24 hours. ZATCA's Wave 25 announcement (24 July 2026) extends integration to taxpayers with VAT-able revenue above SAR 187,500, with a deadline of 1 February 2027. Our e-invoicing guide explains each requirement in detail.

VAT at 15%, Zakat and withholding tax

The ERP must calculate standard-rated (15%), zero-rated, exempt and out-of-scope supplies correctly, support VAT-inclusive pricing and produce the data for ZATCA's VAT return. Depending on ownership, businesses also need Zakat or corporate income tax and withholding tax on payments to non-residents, so the chart of accounts and tax codes must be designed for Saudi rules from the start.

Arabic language and Hijri dates

Arabic must work throughout: right-to-left screens, Arabic item and customer names, bilingual invoices (the human-readable e-invoice must be in Arabic) and Arabic reports. Hijri date display and conversion remain useful for HR documents, contracts and some government correspondence.

Payroll: WPS through Mudad, GOSI and end-of-service

Saudi employers pay salaries under the Wage Protection System (WPS) of the Ministry of Human Resources and Social Development, submitted through the Mudad platform, which cross-checks payroll against GOSI registrations. An ERP payroll module should generate WPS-ready files, calculate GOSI contributions for Saudi and non-Saudi employees, handle Saudisation (Nitaqat) reporting needs and compute end-of-service benefits under the Labour Law. Many businesses connect a specialist Saudi HR and payroll system to the ERP instead.

Data protection and data residency

ERP databases hold employee, customer and supplier personal data, so the Personal Data Protection Law (PDPL) applies. It is enforced by the Saudi Data and AI Authority (SDAIA) and became fully enforceable on 14 September 2024, with fines of up to SAR 5 million for serious violations. Transfers of personal data outside the Kingdom are allowed only under the law's conditions. Government entities and operators of critical infrastructure must also meet National Cybersecurity Authority (NCA) controls, including the Essential Cybersecurity Controls (ECC), which shape hosting and access decisions. Our PDPL compliance guide covers the obligations in depth.

In-Kingdom hosting options have grown: Oracle operates public cloud regions in Jeddah and Riyadh, and Microsoft announced in February 2026 that its Saudi Arabia East Azure region would be available for customer workloads from Q4 2026. Always confirm which specific ERP services, backups and support access actually run in-Kingdom.

What are the popular ERP systems in Saudi Arabia?

• SAP S/4HANA: the established choice for large enterprises, government-linked companies and complex manufacturing, available on-premise or through SAP's cloud offerings, with Saudi localisation and e-invoicing compliance options.
• Oracle Fusion Cloud ERP and Oracle NetSuite: Fusion for large, multi-entity finance-led organisations; NetSuite as a cloud ERP for mid-sized and fast-growing businesses.
• Microsoft Dynamics 365: Finance and Supply Chain Management for larger organisations and Business Central for small and mid-sized businesses, with strong links to Microsoft 365 and Power BI.
• Odoo: a modular platform with an open-source core and an enterprise edition. Its Saudi fiscal localisation includes ZATCA e-invoicing support, and it is popular with SMEs that want flexibility at a lower licence cost.
• Regional and Saudi ERP and accounting systems: Arabic-first products built around ZATCA, VAT and Saudi payroll, typically suited to SMEs and specific sectors such as trading, contracting and retail.
• Custom ERP: built around your processes, either from scratch or as custom modules on an open framework.

ERP comparison table for Saudi businesses

Option	Typical fit	Arabic and ZATCA	Customisation	Implementation effort
SAP S/4HANA	Large enterprises, complex operations	Localisation available; e-invoicing via SAP or partner add-ons	Deep, but specialist skills needed	High
Oracle Fusion / NetSuite	Large finance-led groups / growing mid-market	Localisation and partner e-invoicing solutions	Configurable; extensions via platform tools	Medium to high
Microsoft Dynamics 365	Mid-market to enterprise, Microsoft-centric firms	Localisation and partner e-invoicing solutions	Strong via extensions and Power Platform	Medium to high
Odoo	SMEs and mid-market, multi-activity businesses	Saudi localisation with ZATCA support	Very flexible; open framework	Low to medium
Regional / Saudi ERPs	SMEs, sector-specific needs	Usually Arabic-first, ZATCA built in	Limited to vendor roadmap	Low
Custom ERP	Unique processes, integration-heavy environments	Engineered to your requirements	Unlimited; you own the code	Medium to high

Treat this as a starting point. Partner quality and the fit of your processes to the product usually matter more than the brand.

Custom ERP vs off-the-shelf: which should you choose?

Choose off-the-shelf when your processes are close to industry standard, you need proven finance and compliance functions quickly, and you prefer predictable vendor upgrades. Resist heavy customisation: every modification makes future upgrades and ZATCA updates harder.

Choose custom or hybrid when your competitive advantage lives in the workflow, such as unusual pricing, contracting or service models, when you must integrate many legacy and government systems, when licence costs per user become prohibitive at scale, or when you need full control over data location. A common hybrid is a standard ERP for finance and compliance with custom portals, mobile apps and automation around it. In our industrial automation project, RPA with AI decision layers integrated across operational ERP systems delivered a 72% reduction in processing time; see the industrial automation case study.

How is an ERP implemented, and how long does it take?

1. Discovery and requirements (weeks): map current processes, pain points, reports, integrations and Saudi compliance needs.
2. Selection: shortlist two or three products and partners; run scripted demos using your own scenarios, including ZATCA invoices and WPS payroll.
3. Design: chart of accounts, tax codes, approval workflows, roles, integrations and data migration plan.
4. Build and configure: configuration, extensions, e-invoicing onboarding, integrations with POS, e-commerce, banks and government platforms.
5. Data migration: cleanse and load masters and opening balances; run trial migrations.
6. Testing: unit, integration and user acceptance tests, plus testing in ZATCA's simulation environment.
7. Training and go-live: bilingual training, cut-over plan and a hypercare period with daily issue tracking.
8. Optimisation: dashboards, automation and additional modules once the core is stable.

Timelines vary with scope. A single-entity deployment of a standard product with few integrations can go live in a few months; multi-entity, multi-country or manufacturing programmes commonly take a year or more. Avoid going live in your busiest season or near a ZATCA wave deadline.

What drives ERP cost in Saudi Arabia?

Prices vary widely by product, partner and scope, so compare total cost of ownership over five years rather than licence quotes. The main drivers are:

• Number of users, entities and branches, and the licence model (subscription or perpetual).
• Modules in scope, especially manufacturing, projects and payroll.
• Customisation and extensions beyond standard functionality.
• Integrations: e-invoicing, POS, e-commerce, banks, Mudad and GOSI, and legacy systems.
• Data migration volume and quality.
• Hosting: public cloud, in-Kingdom cloud, private cloud or on-premise.
• Training, change management, support and annual upgrades, including compliance updates.

Why do ERP projects fail, and how can you avoid it?

• Unclear ownership: ERP treated as an IT project instead of a business programme with an executive sponsor.
• Over-customisation: recreating old habits inside the new system, which raises cost and blocks upgrades.
• Poor data: migrating duplicated customers, wrong VAT numbers and inaccurate stock, which triggers e-invoice rejections from day one.
• Underestimated integrations: POS, online store, banks and government platforms left until late.
• Weak Arabic and local compliance: discovering after go-live that invoices, payroll files or reports do not meet Saudi requirements.
• Insufficient training: users fall back to spreadsheets, and the ERP becomes an expensive ledger.
• Security as an afterthought: broad access rights, no audit trails and unclear data residency, creating PDPL and NCA exposure.

Next step

Whether you are selecting your first ERP, integrating an existing one with ZATCA and your POS system, or building custom modules around it, Amwaj Solutions can help you design an architecture that lasts. Explore our ERP and custom software service or request a consultation; we respond within 24 to 48 business hours.