Salesforce in Saudi Arabia, with the compliance boundary drawn properly.

ZATCA integration

Integration to a ZATCA capable invoicing system, so a closed opportunity produces a cleared e-invoice rather than a quote with no regulatory standing.

Arabic first layouts

Arabic first page layouts, record types and translation, with right to left presentation for teams working in Arabic.

Compliance master data

Account and contact records carrying VAT registration and national address fields, so the downstream invoicing system receives what ZATCA validates.

Governance model

Role hierarchy, sharing rules and field level security built for large organisations where access separation is a governance requirement rather than a preference.

Approval processes

Approval processes reflecting Saudi enterprise and government procurement, which involve more stages and more documentation than default configurations assume.

Local calendar

Local holiday calendar, working week and business hours applied to entitlements, SLAs and automation.

Does Salesforce handle ZATCA e-invoicing?

Not on its own. Clearance and reporting require a system built for ZATCA. Salesforce manages the commercial process and integrates to that system at the point of invoice.

Can the interface be Arabic?

Yes, per user. Arabic speaking users can work in Arabic with right to left layouts while others remain in English, on the same org.

We are already on Salesforce globally. Can you handle the Saudi rollout?

Yes. That is usually a localisation and integration project rather than a new build: tax treatment, Arabic layouts, local approval processes and the e-invoicing integration, inside your existing org and governance model.