ERP for Saudi Arabia, built around how you actually operate and compliant with ZATCA Phase 2 from the start

It depends on scope, and any vendor quoting before they understand your process is guessing. What drives the number: how many sites, how many integrations, how much of your process is genuinely non-standard, how clean the data is that has to migrate, and whether ZATCA Phase 2 compliance has to be built in from the start. We give a fixed price after discovery.

ZATCA Phase 2, which requires cryptographic sealing and real-time integration with Fatoora, applies to the invoicing module, not to the ERP as a whole. Systems we build for Saudi Arabia include a ZATCA-compliant e-invoicing module with UUID generation, QR code, XML in the UBL 2.1 format, and direct Fatoora API integration. Compliance is a named deliverable in the scope, not a late addition.

We build the tax engine to Saudi rates and categories by default for Saudi-operated systems. The ZATCA Phase 2 invoice module handles VAT calculation, credit notes, debit notes and the clearance/reporting API calls. If you operate across VAT and zero-rated categories the scope conversation includes the tax treatment design.

No. The Regional Headquarters requirement affects multinationals seeking Saudi government contracts and certain regulatory licences. For private-sector contracts, a non-resident supplier can contract directly with a Saudi company. We will tell you plainly if your procurement route requires a local or RHQ-licensed supplier.

For Saudi health data the system runs in-country. For everything else, we discuss the hosting region in week one. Saudi Arabia's PDPL came fully into force in 2024 and imposes restrictions on cross-border transfers of personal data. We configure the data transfer framework as part of contract preparation.

This depends on how you classify the payment. Custom software development is generally treated as a service and attracts 5% withholding tax in Saudi Arabia. Licence fees are classified as royalties and attract 15%. A Saudi tax adviser should confirm the applicable category before the contract is signed. We do not provide tax advice; this answer is for orientation only.

Potentially yes. Unlike the UAE, Saudi Arabia does levy withholding tax on certain cross-border payments, and the rate depends on the payment type. We factor this into the commercial discussion at proposal stage so the invoice amount and the net received are clear before you commit.

For private-sector projects, we contract directly. For Saudi government contracts, procurement typically routes through a locally licensed supplier, and some contracts require Saudi content certification under the Nitaqat programme. We will tell you which procurement route your project falls under and whether we can support it or not.

India is UTC+5:30 and Saudi Arabia is UTC+3, a difference of two hours and thirty minutes. Sunday to Thursday is the working week in Saudi Arabia; our team runs to match it. An 8:00am meeting in Riyadh is a 10:30am start in Pune. There is no effective overlap problem.

Arabic and English in a single interface, with right-to-left layout for Arabic. We build the language layer as part of scope, not as a post-go-live addition, and we test it with Arabic data rather than Latin placeholders.

You do. Repository access, documentation and a full handover are written into every contract. We would rather be kept because the work is good than because leaving is difficult.