ERP Implementation in Saudi Arabia: A Client-Side Guide
In this article
- What is different about ERP implementation in Saudi Arabia
- The phases from business case to hypercare
- ERP project plan: who owns what
- A realistic timeline for a mid-sized company
- Data migration and testing: where projects slip
- Data migration
- Testing
- ERP go-live checklist
- Mistakes specific to Saudi projects
- Key takeaways
- Frequently asked questions
- What are the steps of an ERP implementation?
- How long does ERP implementation take in Saudi Arabia?
- Does the ERP have to be ZATCA compliant before go-live?
- Should payroll run inside the ERP?
- What should the company team look like?
- When should we accept the system from the partner?
ERP implementation in Saudi Arabia follows the same phases as anywhere else, from business case to hypercare, but with local requirements that decide whether the project is legal and usable on day one: ZATCA e-invoicing integration, Arabic tax documents, 15 percent VAT and withholding tax, payroll obligations tied to GOSI, and a partner market that varies more than vendor brochures suggest. This guide walks through each phase from the company’s side and names the deliverables you must own yourself.
I write from that side. At NAF Company I led the end-to-end SAP Business One implementation, integrated with an MES, Jisr HR and a custom feed formulation system, and during 2024 I concurrently directed the SAP B1 lifecycle across several business units of the parent group: scope, vendor coordination, configuration, data migration, training and go-live. The lessons below are the ones that cost us time or that saved us from a bad cutover.
What is different about ERP implementation in Saudi Arabia
A vendor’s global methodology will not mention most of these, and each one has stopped a Saudi project I know of.
- ZATCA e-invoicing (Phase 2). Your ERP must generate invoices in ZATCA’s XML format, stamp them, and connect to the Fatoora platform for clearance of tax invoices and reporting of simplified invoices. Devices are onboarded with certificates. I explain the mechanics in my guide to ZATCA Phase 2 integration for ERP owners. Treat it as a workstream with its own owner, not a line in the partner’s checklist.
- Arabic documents and bilingual users. Tax invoices must be in Arabic; bilingual layouts are allowed. Many finance teams work in English and many operations teams in Arabic, so screen language, print layouts and training material must be planned per role.
- Tax configuration. VAT at 15 percent with zero-rated, exempt and reverse-charge cases, plus withholding tax on certain payments to non-residents. Have your tax adviser sign off the tax codes in the blueprint.
- HR and payroll realities. GOSI contributions, wage-protection file submissions, end-of-service provisions, Hijri-date handling for some HR policies, and a workforce with mixed nationalities. Most mid-sized companies run a dedicated Saudi HR system and integrate it with the ERP rather than forcing payroll into the ERP.
- Master data standards. Commercial registration numbers, VAT numbers and the national address format for your company, branches and B2B customers are checked by ZATCA, so data cleansing is a compliance task, not housekeeping.
- Partner market. Fewer, larger partners for SAP Business One and a large, uneven pool of Odoo partners. If you have not chosen a product yet, start with my comparison of SAP Business One vs Odoo for Saudi companies.
- Calendar. Plan around Ramadan working hours and the two Eid breaks; a go-live two weeks before Eid with half the key users on leave is a common and avoidable mistake.
The phases from business case to hypercare
Partners name these differently, but the content is stable. What changes from project to project is whether the company does its part in each one.
- Business case and sponsorship. Write down the three to five outcomes the ERP must deliver (for example, month-end close in five working days, real-time stock by warehouse, ZATCA compliance on all channels). Name an executive sponsor who will attend steering meetings. Without this, scope is decided by whoever shouts loudest in workshops.
- Requirements and selection. Document as-is and to-be processes and write testable requirements before you see demos. Score proposals on the same sheet. This is the phase most Saudi companies skip, and it is where the business analysis investment pays back many times.
- Project preparation. Contract, project charter, governance (steering committee, weekly project meeting, change-request procedure), environments, and the key-user team with their time formally released by their managers.
- Blueprint (design). Workshops per process; the partner writes the blueprint; you read every line and sign it. Everything not in the blueprint is a change request later.
- Realization (build). Configuration, reports, integrations, authorizations, and the e-invoicing setup. Your key users should be in the system from the first configured module, not at UAT.
- Data migration. Master data first, then open items, then opening balances, with at least two mock loads and reconciliation sign-off by finance and operations.
- Testing and training. Scripted user acceptance testing by your users with evidence, then role-based training on your own data.
- Cutover and go-live. A written cutover plan with owners and times, a go/no-go meeting with explicit criteria, and a freeze on configuration changes.
- Hypercare and closure. Daily issue triage for the first weeks, the first month-end close with the partner present, and formal acceptance only after it.
ERP project plan: who owns what
The single most useful document I produce at the start of a project is a one-page responsibility split. Partners sell days; they do not sell your decisions.
| Deliverable | Partner | Company |
|---|---|---|
| Business outcomes and scope boundaries | Advises | Owns |
| Blueprint document | Writes | Reviews line by line, signs |
| Configuration and reports | Builds | Validates with key users |
| Chart of accounts, cost centers, tax codes | Configures | Designs with CFO and tax adviser |
| Master data cleansing and templates | Provides templates | Cleans, fills, reconciles |
| Data migration loads | Executes | Reconciles and signs off |
| ZATCA onboarding | Configures solution | Portal access, OTPs, master data, certificate calendar |
| Integrations (HR, MES, e-commerce) | Builds its side | Owns interface design and the other systems’ vendors |
| UAT scripts and execution | Supports | Writes and executes |
| Training | Trains key users | Key users train end users |
| Cutover plan and go/no-go | Drafts | Decides |
| Hypercare issue log | Resolves | Prioritizes and tracks |
A realistic timeline for a mid-sized company
For a single company with finance, sales, purchasing, inventory and light production, I plan on the order of four to six months from kick-off to go-live when data is reasonably clean and key users are released at least two days a week. Multi-entity groups, manufacturing with an MES, or legacy data in several formats push that to nine months or more. The phases that stretch are never configuration; they are blueprint sign-off, data cleansing and testing, because those depend on your people’s time.
When I ran the SAP B1 rollout across business units for the parent group, the lever that kept the plan was sequencing: one entity as the template, its configuration and templates reused for the next, and a data governance framework with strict integrity controls during each cutover so migration did not become a bespoke project each time. A group that tries to go live everywhere on one date doubles the risk and halves the attention each entity gets.
Data migration and testing: where projects slip
Two phases account for most slippage, and both are company-owned.
Data migration
Separate master data (items, customers, suppliers, chart of accounts, employees), open transactions (open invoices, open purchase orders, stock by batch) and opening balances. Clean master data in the old system or in spreadsheets with a named owner per table. Run at least two mock loads: the first exposes format problems, the second must reconcile to the trial balance and stock count to the riyal and the kilogram. Only then schedule cutover. During the group rollout I built the governance framework for migration from legacy systems precisely because a reconciled mock load is the only evidence that go-live is safe.
Testing
UAT means your users executing scripted scenarios end to end on migrated data, with evidence filed and defects classified by severity. It does not mean watching the consultant click. On a different project I audited a delivered MES against the signed specification with a 60-point test plan across four cycles; it surfaced 3 defects and about 20 functional gaps, and that evidence let us negotiate a controlled partial acceptance instead of signing blind. The same discipline applies to an ERP: no test evidence, no acceptance.
ERP go-live checklist
Use this at the go/no-go meeting. Any “no” is a conversation about delay, not a note for later.
- Blueprint signed; all approved change requests built and tested.
- Second mock migration reconciled and signed by finance and operations.
- UAT complete; no open critical or high-severity defects; workarounds documented for the rest.
- ZATCA production onboarding done for every invoicing unit; test invoices cleared and reported in simulation; certificate expiry in the renewals calendar.
- Arabic and bilingual print layouts approved by finance and sales.
- Tax codes signed off by the tax adviser; first VAT return mapping confirmed.
- HR integration tested with a full payroll cycle in parallel.
- Authorizations and approval procedures configured and tested per role.
- Every end user trained on their own transactions; quick-reference sheets in the right language.
- Cutover plan with owners, times and rollback decision point; freeze on configuration.
- Backups, monitoring and support contacts confirmed; hypercare rota published.
- Legacy system set to read-only on the agreed date, not switched off.
Mistakes specific to Saudi projects
- Discovering ZATCA in the last month. Onboarding, master data and compliance checks need weeks, and the production switch is effectively one-way.
- Customer records without VAT numbers. B2B invoices will fail clearance. Clean the customer list in the first month of the project.
- Forcing payroll into the ERP. Saudi payroll rules and government files are better handled in a local HR system integrated with the ERP; we integrated Jisr HR with SAP B1 rather than rebuilding payroll.
- One language for everyone. Decide screen language, print language and training language per role, and test Arabic layouts early.
- Key users who are never released. If a department head will not release a key user for two days a week, that department is not ready to implement.
- Go-live before a holiday. Schedule go-live so the first month-end close happens with everyone present.
- Accepting on the go-live date. Accept after the first clean month-end close and VAT return, when the system has proven itself.
Key takeaways
- The phases are standard; success depends on the company owning scope, data, testing and decisions.
- In Saudi Arabia, ZATCA e-invoicing, Arabic documents, tax codes and HR integration are separate workstreams with named owners.
- Write testable requirements and a responsibility split before the partner starts billing days.
- Data migration needs at least two reconciled mock loads; UAT needs scripts, evidence and severity classification.
- Plan four to six months for a single mid-sized entity; sequence multi-entity groups with a template entity.
- Accept the system after the first clean month-end close, not on the go-live date.
Frequently asked questions
What are the steps of an ERP implementation?
Business case and sponsorship, requirements and selection, project preparation, blueprint, realization, data migration, testing and training, cutover and go-live, then hypercare and closure. The partner builds and configures; the company owns outcomes, decisions, data quality, test evidence and the go/no-go decision at each gate.
How long does ERP implementation take in Saudi Arabia?
For a single mid-sized company with clean data and released key users, plan four to six months from kick-off to go-live. Multi-entity groups, manufacturing with an MES, or messy legacy data push it to nine months or more. Time is lost in blueprint sign-off, data cleansing and testing, not in configuration.
Does the ERP have to be ZATCA compliant before go-live?
Yes, if your company is in a ZATCA integration wave. Every invoicing unit must be onboarded with a certificate, tax invoices must be cleared and simplified invoices reported through Fatoora from the first day of issuing from the new system. Run the full e-invoicing test cycle in simulation before the production switch.
Should payroll run inside the ERP?
Usually not for Saudi companies. GOSI, wage-protection files, end-of-service provisions and leave rules are handled well by local HR systems, and the ERP needs only the payroll journal, cost-center allocation and employee master. Integrating a dedicated HR system with the ERP is simpler and safer than rebuilding payroll in it.
What should the company team look like?
An executive sponsor, a project manager on the company side, a key user per process area with real time released, a finance lead for chart of accounts and tax, a data owner per master-data table, and an IT owner for integrations, infrastructure and ZATCA onboarding. Partners cannot substitute for any of these roles.
When should we accept the system from the partner?
After the first month-end close and VAT return on the new system have been completed cleanly, not on the go-live date. Tie final payment milestones to that event and to the closure of critical and high-severity defects, so hypercare has the partner’s full attention.
If you are planning an ERP project in Saudi Arabia and want someone on your side of the table through selection, blueprint, migration and go-live, see my ERP implementation service, read the SAP Business One manufacturing case study, or contact me to discuss your timeline.