Key takeaways
- ZATCA Phase 2 (the integration phase) requires invoices to be generated, signed and reported from a compliant system, so e-invoicing must be built into the ERP, not bolted on.
- One database and one login for finance, stock, sales, HR and service removes the re-entry that creates most reconciliation problems.
- Start with the modules you need today and switch the rest on later; the vendor's roadmap and local support matter more than the longest feature list.
Why ERP selection changed in the Kingdom
Two things reshaped the ERP market in Saudi Arabia. The first is the ZATCA e-invoicing programme: Phase 1 (the generation phase) made electronic invoices mandatory, and Phase 2 (the integration phase) has been rolled out in waves since 2023, requiring businesses to integrate their invoicing systems with the FATOORAH platform. The second is Vision 2030, which pushed digital transformation into procurement rules, government platforms and customer expectations.
The result is that an ERP is now judged on compliance, integration and Arabic support as much as on ledgers and reports. A system that handles those natively saves months of add-ons and workarounds.
What ZATCA compliance actually requires from the software
For Phase 2, the ERP must produce invoices in the required XML format with the mandatory fields, apply the cryptographic stamp and QR code, keep an unalterable sequence, and clear or report invoices with ZATCA through the integration. Simplified tax invoices for retail and standard tax invoices for business customers follow different flows, so the system must handle both.
- Built in, not added on: compliance that lives in the finance module stays current when rules change.
- Every channel: point of sale receipts, project invoices and recurring billing all need the same treatment.
- Audit trail: who changed what, and when, must be visible for VAT and audit purposes.
SEJEL ERP was built with ZATCA Phase 2 e-invoicing in the finance module from day one, with VAT, WPS payroll and GOSI handled in the same system.
One database, one login: why it matters more than features
Most reconciliation pain comes from systems that do not share data. Stock sold at the till is updated in the inventory system later, payroll is exported to a spreadsheet, and the project manager keeps costs in a separate tool. Every hand-off is a chance for a mismatch.
An ERP where finance and accounting, purchasing and inventory, manufacturing and planning, sales and CRM, point of sale, HR and payroll, projects, assets and helpdesk share one database means every department works on the same numbers. Month-end closing becomes a review rather than an investigation.
Questions to ask before you sign
- Where is the data hosted? Hosting in the Kingdom simplifies compliance conversations and keeps latency low for branches across Saudi Arabia.
- Is the interface genuinely bilingual? Arabic and English should be first-class, including reports and the employee self-service portal.
- Can we start small? Switching modules on as the business grows protects the budget and the rollout.
- Who supports it? Local engineers, response times and an annual maintenance arrangement decide how the system behaves in year two.
- How does it connect? Nafath single sign-on, Ejar for leasing, banks, POS terminals and payment gateways should be ready connectors, not projects.
How SEJEL approaches it
SEJEL ERP is the in-house cloud ERP of SEJEL Smart Platform, the technology brand of Abdulmohsin Al Rossais & Sons Group Co. in Riyadh. Twelve modules share one database, one login and one price, it is hosted in the Kingdom with Arabic and English interfaces, and it ships with AI-powered insights and an employee self-service portal. Because the same team delivers point of sale, kiosks and integrations, the ERP is the centre of a connected stack rather than another island.