ERPNext implementation in Saudi Arabia, ZATCA-ready

Saudi Arabia is one of the fastest-growing markets for ERPNext for a simple reason: the compliance calendar. Since 2021 every VAT-registered business has had to issue electronic invoices, and since 2023 ZATCA has been integrating businesses wave by wave into its Fatoora platform, where each invoice is cleared or reported through an API before it is valid. Licensed ERPs charged for that as a module and a per-user fee; ERPNext, an open-source ERP on the Frappe framework, has the Saudi VAT and e-invoicing groundwork in its regional setup and no licence at all, so the budget goes into the implementation and the integration rather than into seats.

It also fits how mid-sized Saudi companies actually run. Arabic and English side by side, a chart of accounts that maps to Saudi VAT categories, manufacturing and stock modules that trading and industrial companies in the Eastern Province and Riyadh need, and a framework in Python that lets us build the pieces that are yours — a contracting progress-billing flow, a GOSI reconciliation, a Qiwa contract export — without forking the product.

'ZATCA-ready' should mean something specific. It means your standard tax invoices are cleared by ZATCA's API with a cryptographic stamp before your customer sees them, your simplified invoices are reported within 24 hours, your devices are onboarded with valid CSIDs, your invoice hash chain never breaks, and all of this was proven in the ZATCA sandbox before your integration wave's deadline — not a QR code on a PDF. That is the standard we implement to, and the assessment tells you where you are against it today.

Phase 1 — the generation phase — is what most businesses already have: tax invoices with the mandatory fields and a QR code, no tampering, no deletion. ERPNext's Saudi regional setup produces that QR code on every tax invoice and simplified invoice. Phase 2 — the integration phase — is where the work is. Each invoice becomes a UBL 2.1 XML document with a UUID, a counter, the hash of the previous invoice and a cryptographic stamp; standard (B2B) invoices are sent to ZATCA for clearance and are not valid until ZATCA returns them stamped; simplified (B2C) invoices are stamped on your side and reported within 24 hours; and every device that issues invoices holds a CSID obtained through a compliance and production onboarding process.

We implement Phase 2 on ERPNext with a dedicated integration app that sits beside ERPNext rather than inside it — so ERPNext upgrades cleanly and the ZATCA layer is versioned on its own. The rollout has a fixed shape: map your invoice types and branches to ZATCA's rules; generate and validate XML against ZATCA's schema; onboard each device in the compliance environment and pass the compliance checks; run a parallel period in the sandbox on real invoices; then obtain production CSIDs and go live with monitoring on every clearance and reporting call, because a rejected invoice at month-end is a finance problem, not an IT one.

Timing matters more here than in any other module. ZATCA announces integration waves by revenue threshold with a deadline for each, and the onboarding, sandbox testing and production cut-over take two to four weeks of calendar time even when the software is ready. If your wave has been announced, tell us the date in the first conversation and we plan the implementation backwards from it.

• Phase 1 — QR-coded tax and simplified invoices, mandatory fields, no deletion, bilingual print formats
• Phase 2 — UBL XML, UUID and counter, previous-invoice hash, cryptographic stamp per device
• Clearance for standard invoices, reporting within 24 hours for simplified invoices, credit and debit notes handled the same way
• CSID onboarding per device in compliance and production environments; certificate renewal in the runbook
• Sandbox parallel run on real invoices, then production go-live with alerting on every ZATCA response

The finance configuration is where a Saudi implementation earns its keep. We set up the chart of accounts with the tax categories ZATCA and the VAT return need — standard-rated at 15 %, zero-rated exports and qualifying supplies, exempt financial and residential supplies, out-of-scope — with reverse-charge handling on imported services and customs VAT on imported goods. The VAT return is then a report from the ledger, reconciled to the invoices ZATCA has cleared, rather than a spreadsheet built at the end of the period. The same discipline that took Mohan Impex in India from three days of monthly GST preparation to four hours applies directly to a Saudi VAT return.

Language is a compliance requirement, not a preference: tax invoices must be in Arabic, and can be bilingual. ERPNext ships an Arabic translation and right-to-left layouts; we complete the localisation for your business — Arabic item, customer and supplier names held alongside English in the masters, bilingual print formats for every outward document, Arabic report headers, and Hijri dates where a contract, a government submission or a Ramadan schedule needs them. Your finance team works in the language they prefer and your customers receive a document in the language they expect.

Payroll in the Kingdom has its own rules and every one of them is configurable in ERPNext's HR and payroll modules once someone has done it before. GOSI contributions are calculated at the rates for Saudi nationals and for expatriate employees on the correct wage base; the monthly salary file is generated in the WPS format your bank submits to Mudad; end-of-service benefits accrue under the Labour Law's half-month and full-month rules and are paid out correctly on resignation or termination; annual leave, sick leave and Ramadan working hours follow the statute; and iqama, passport and contract expiry dates are tracked with reminders so a renewal is never missed.

Where government platforms offer an interface — Qiwa for employment contracts, Muqeem for residency data — we align ERPNext's employee master to the fields they expect so exports and reconciliations are routine. The UNO MINDA and RKCL platforms show what we build on Frappe when the standard HR module is not enough: custom doctypes and workflows for training, certification and compliance that reuse ERPNext's users, permissions and reporting rather than reinventing them.

Where the ERP runs is a board-level question in Saudi Arabia. The Personal Data Protection Law is in force, sector regulators have their own residency and cloud expectations, and many of our clients simply want their ledger inside the country. We deploy ERPNext three ways for Saudi companies: self-hosted on an in-Kingdom cloud region — Google Cloud's Dammam region or Oracle Cloud's Riyadh and Jeddah regions — or a local Saudi provider; on your own servers for companies that keep everything on-premise; and on a Gulf-region cloud such as AWS Bahrain or the UAE where in-Kingdom hosting is not mandated and the economics favour it. Frappe Cloud is the quickest start for a company that does not have a residency requirement.

Every deployment gets the same operating setup regardless of where it runs: Docker-based ERPNext with MariaDB and Redis, nightly encrypted backups to a second location, a tested restore procedure before go-live, role-based access with two-factor authentication, an audit trail on every document, and monitoring with a named engineer on call. We document the setup against PDPL's requirements so that your data-protection officer or auditor gets a written answer rather than a promise. The MOSPI platform, run under Government of India data-residency rules, is the reference for how we handle a regulator's requirements end to end.

Our Saudi work is run from Al-Khobar with the delivery team in Bangalore — two time zones that overlap for most of the working day, which is how the PIF Co-Builder smart-incubator platform in Riyadh and our Gulf portal work for OMSB and be'ah were delivered. Discovery workshops, training and go-live support happen on site with your team; configuration, customisation and integration happen in Bangalore with daily visibility. Training is delivered in English and Arabic with bilingual documentation.

The method is the same six-phase implementation we run everywhere — a fixed-fee fit-gap study, a prototype company on your real transactions, customisation and data migration in parallel, role-based training and acceptance testing, module-by-module go-live and a hypercare month — with the Saudi compliance work threaded through it: ZATCA onboarding starts in the configuration phase, the VAT return is tested in acceptance, and the first live payroll and the first VAT period fall inside hypercare so our consultants are there for both.

As a guide from our implementations, a single-company rollout of accounting, buying, selling and stock with ZATCA Phase 2 goes live in 10–14 weeks; add manufacturing, quality and multi-branch stock, or Saudi payroll for several hundred employees, and four to six months is realistic. The cost is driven by modules and branches in scope, customisation depth, the state of your data — Tally, QuickBooks, Sage, Odoo or spreadsheets — integrations with banks and government platforms, and hosting; there is no per-user fee, and we quote discovery as a fixed fee and the implementation as a fixed price for the agreed scope.

The companies that get the most from ERPNext in the Kingdom are the ones a licensed ERP prices out or under-serves: manufacturers in Dammam and Jubail who need production planning, quality and traceability; trading and distribution businesses with landed cost, multi-warehouse stock and VAT on imports; contracting companies that need projects, progress billing, retention and equipment tracking in one ledger; and services and technology companies scaling with Vision 2030 programmes who need finance, HR and CRM that will not need replacing at the next stage of growth.

A note on references, because we would rather you hear it from us: our ERPNext implementations to date have been for Indian manufacturers, traders and programmes — Jyoti CNC, Mohan Impex, UNO MINDA, RKCL, MOSPI — and our Gulf delivery has been enterprise portals on Liferay for PIF, OMSB and be'ah. The Saudi localisation work on this page is done by the same ERPNext team, from the same Al-Khobar office, with the same method. Ask us for a reference call with any of those clients, and for a working ZATCA sandbox demonstration before you sign anything. The broader practice is on the Frappe & ERPNext services page.