Regional vs global ERP for Saudi and Gulf businesses
A global platform with a localisation layer, or a system built for the region first. The trade is breadth against how deep compliance goes and who owns it when the rules change.
| What you are comparing | Global ERP + localisation | Regional-first ERP |
|---|---|---|
| E-invoicing | Via a localisation pack or a third-party connector, on the vendor's release schedule | Core behaviour, updated as the authority publishes |
| Arabic | Interface translation; printed and thermal output varies by module | Bidirectional throughout, including printed invoices and thermal receipts |
| Zakat and regional tax | Often an add-on or a partner customisation | Built in alongside VAT |
| Who fixes a rule change | Vendor, then localisation partner, then you — in sequence | One party |
| Breadth of functionality | Very wide; decades of modules and a large partner ecosystem | Narrower, focused on what the region actually runs |
| Fit for multinationals | Strong — consolidated group reporting across many countries | Depends on how far outside the region you operate |
Localisation is a layer, and layers have seams
Global platforms handle regional requirements through localisation packs. It works, and it is how most large multinationals run. The cost is structural: the requirement lives outside the core, so it updates on a different schedule and is often owned by a different company than the one that wrote the software.
When ZATCA publishes a change, a regional-first system changes. A layered system changes when the vendor ships it, the localisation partner adapts it, and your implementer applies it — three parties, three timelines, and a compliance deadline that moves for none of them.
Where "supports Arabic" stops being true
Almost every ERP claims Arabic support, and almost every one delivers a translated interface. The gap shows further down: a printed tax invoice with an Arabic customer name and a discount line, a thermal receipt from a till, an Arabic product description that survives export to Excel, a report that stays readable right-to-left.
Ask for that printed invoice during evaluation. One document exercises most of what breaks, and it is far cheaper to discover in a demo than in month two.
When the global platform is the right choice
If you consolidate across many countries, need statutory reporting in a dozen jurisdictions, or your group has already standardised on a platform, a regional system is the wrong shape regardless of how good its Saudi compliance is. Group consistency is a real requirement, not a preference.
The honest split: if the Gulf is where your operation lives, buy for depth here. If the Gulf is one region of many, buy for consolidation and accept the layer.