Carrier Deskapp.
Implementation

Cloud ERP in Saudi Arabia and the UAE: E-Invoicing, VAT, Data Residency and Costs

ZATCA Phase 2 clears B2B invoices through a central platform, while UAE e-invoicing runs through accredited providers, with the largest taxpayers due to go live from early 2027. Here's what your ERP must handle in each country, where it can be hosted, and what it typically costs.

Carrier Deskapp editorial team · November 2026 · 10 min read

The Gulf requirements that rule out an ERP before the demo

If you're choosing a cloud ERP in Saudi Arabia, the UAE or both, check compliance first. Features come second. The two countries run different e-invoicing models. Saudi Arabia uses a central clearance platform (ZATCA's Fatoora). The UAE uses a decentralized, Peppol-based network run through accredited providers. One ERP can handle both, but the integration work, partner skills and cost differ in each country.

Before you book demos, test each shortlisted vendor against four requirements:

  • E-invoicing: a proven ZATCA Phase 2 integration for Saudi entities, and a named UAE Accredited Service Provider (ASP) connection for UAE entities.
  • Tax engine: 15% VAT in Saudi Arabia and 5% in the UAE, plus reverse charge, zero-rated and exempt supplies, intra-GCC rules and VAT return reports. The two tax configurations must stay separate in one instance.
  • Arabic: Arabic on invoices and customer-facing documents, and ideally an Arabic interface for finance and warehouse staff.
  • Hosting: a clear answer on where production data, backups and support access sit, measured against your sector's data rules.

Our position: for most mid-market groups, e-invoicing and hosting should decide the shortlist, and functional fit should rank the survivors. A vendor that's excellent at manufacturing but relies on an unproven third-party ZATCA plug-in is the riskier choice, because that plug-in is what can stop you issuing valid invoices.

Advertisement

ZATCA Fatoora Phase 2: what ZATCA e-invoicing ERP integration involves

Saudi Arabia introduced e-invoicing in two phases. Phase 1, which began in December 2021, required electronic invoice generation. Phase 2, the integration phase, has rolled out in waves since January 2023. Each wave is defined by revenue, and the thresholds have kept falling, so smaller and smaller businesses are being pulled in. ZATCA notifies each taxpayer group of its wave in advance, typically several months ahead. That notice is your real project deadline. Check the Fatoora portal for your entity's status instead of assuming you have time.

In practice, Phase 2 requires the ERP or its connector to:

  • Produce invoices as UBL 2.1 XML that matches ZATCA's data dictionary. B2B documents are shared as PDF/A-3 with the XML embedded.
  • Stamp each invoice cryptographically, with a UUID, an invoice counter and the hash of the previous invoice. That links invoices into a chain that can't be altered.
  • Add a QR code with the required tag-length-value fields.
  • Register each invoicing unit (solution, branch or point-of-sale device) on the Fatoora portal and manage its certificates. Each unit receives a compliance certificate first, then a production certificate.
  • Clear standard (B2B and B2G) tax invoices through ZATCA before they go to the buyer, and report simplified (B2C) invoices within 24 hours.
  • Apply the same rules to credit and debit notes, with the reference to the original invoice recorded correctly.

Integration red flags

  • Failed clearances land in an email inbox instead of a queue inside the ERP with retry and resubmission.
  • The connector can't explain how it keeps the hash chain intact when an invoice is cancelled or reissued, or after an outage.
  • Certificates are renewed by hand, and nobody is named as responsible.
  • The vendor can't show live Phase 2 clearance in a reference environment for your edition and version.

Major suppliers, including SAP, Oracle, Microsoft Dynamics 365, Odoo and regional ERP vendors, offer Phase 2 support either natively or through localization partners. Find out which applies to you. A native feature is updated with the product. A partner add-on is a separate contract with its own release cycle.

UAE e-invoicing: ASPs, Peppol and the 2027 deadlines

The UAE chose a different model. Businesses don't send invoices to a government platform. They connect to an Accredited Service Provider. The ASP validates each invoice, exchanges it with the buyer's ASP over a Peppol-based network, and reports the tax data to the Federal Tax Authority. This is often called a five-corner model. Invoices follow the UAE's PINT AE specification. The first stage covers B2B and B2G transactions, and B2C is out of scope for now.

The ministerial decisions published in 2025 set a phased timeline, as we understand it:

  • Revenue of AED 50 million or more: appoint an ASP in the second half of 2026 and go live around the start of 2027.
  • Revenue below AED 50 million: appoint an ASP in early 2027 and go live around mid-2027.
  • Government entities: a later go-live, in the second half of 2027.

If you're in the larger group, your ASP appointment date has likely already passed or is imminent, so confirm your status now. Dates like these get revised, so check the current schedule with the Ministry of Finance and your tax adviser before building a project plan around it.

For UAE e-invoicing, an ERP mostly has to (1) hold all the mandatory PINT AE fields, including buyer endpoint IDs and correct tax categories; (2) connect to your chosen ASP through an API; and (3) pull in rejections and status updates. Many ERP vendors partner with one or more ASPs, and some of those ASPs also offer ZATCA connectivity. For a dual-country group, one provider covering both countries is usually simpler to run, provided its ZATCA work is as mature as its Peppol work.

Watch master data quality. Peppol routing depends on correct buyer identifiers, and teams that skip the customer master cleanup tend to see high rejection rates in the first month.

VAT, Arabic and other local requirements

E-invoicing gets the attention, but several other local requirements cause rework late in projects.

VAT setup. Saudi Arabia charges 15% VAT and the UAE 5%. Each has its own return format, its own rules for real estate, financial services and exports, and its own treatment of designated zones (UAE) or special zones (Saudi Arabia). A dual-country group needs separate legal entities, tax codes and return reports, with no shared tax codes. Intercompany sales between your Saudi and UAE entities are cross-border supplies and must be invoiced that way, including under each country's e-invoicing rules.

Corporate tax and zakat. The UAE introduced a 9% federal corporate tax for financial years starting from June 2023. Saudi Arabia levies zakat on Saudi- and GCC-owned businesses and income tax on foreign-owned shares. Your ERP won't calculate these returns itself. But your chart of accounts and fixed-asset setup must produce the numbers your tax adviser needs, so design them with that adviser.

Arabic. Saudi tax invoices must include Arabic, and bilingual Arabic-English layouts are standard. In the UAE, English invoices are common, but authorities can ask for Arabic versions of records. Test three things separately: Arabic printed output (right-to-left layout, mixed-direction addresses, amount in words), an Arabic user interface, and Arabic search on item and customer names. Some products print Arabic well but offer only a partial interface.

Adjacent systems. Payroll usually sits outside the core ERP. It has to connect to GOSI and Mudad in Saudi Arabia and to the Wage Protection System in the UAE. Most groups run a local payroll product that posts to the ERP's general ledger. Agree that integration early.

ERP data residency in the GCC: what the rules require and what vendors offer

Data residency comes up in nearly every Gulf ERP evaluation, and it's often misunderstood. Saudi Arabia's Personal Data Protection Law, now in force, limits transfers of personal data outside the Kingdom, with exceptions and conditions. Government entities, critical infrastructure operators and SAMA-regulated firms face stricter localization under National Cybersecurity Authority cloud controls and sector rules. The UAE's federal data protection law sets transfer conditions. DIFC and ADGM have their own regimes, and health data carries explicit localization rules.

For a private manufacturer or distributor outside regulated sectors, in-country hosting is often a contract or policy choice rather than a legal requirement. Government customers and large local buyers increasingly write residency clauses into supplier contracts, though. Have counsel licensed in each country review your case.

Where the major vendors stand, in general terms. Regional availability changes often, so verify each point at contract stage:

ProviderGulf hosting positionWhat to verify
Oracle (Fusion Cloud ERP, NetSuite)Public cloud regions in the Gulf, including Saudi Arabia and the UAEWhether your SaaS product and edition run in-country, not just the infrastructure services
SAP (S/4HANA Cloud)Local data center options, including through regional partnersWhich S/4HANA Cloud edition is offered locally, and where support teams access data from
Microsoft (Dynamics 365)Azure regions in the UAE; Saudi availability has been announced or is rolling outDynamics 365 availability in the specific region, and where backups and disaster recovery sit
AWS / Google Cloud (for partner-hosted ERP)Regional presence in the UAE, Bahrain, Saudi Arabia or Qatar, depending on provider and dateWho runs the stack, and the partner's certifications and service levels
Partner-hosted Odoo or regional ERPsUsually hosted in-country by the implementation partnerThe partner's financial strength, security certifications and exit terms

The main point: a cloud region in the country doesn't mean your ERP tenant runs there. Ask for the tenant location, the backup and disaster recovery location, and where support staff connect from. Get all three in the contract.

Costs and timelines for single- and dual-country rollouts

The figures below are typical 2026 market ranges for mid-market and lower-enterprise deployments, in USD. Pricing in Riyadh and Dubai varies by contract, user mix and partner rates, so confirm with vendors and implementers.

ScenarioTypical timelineImplementation costRecurring cost
Add a ZATCA Phase 2 connector to an existing ERP6–12 weeks$5,000–$40,000$100–$1,500/month, or per-invoice pricing
Add a UAE ASP connection to an existing ERP6–14 weeks$5,000–$50,000Per-document or tiered ASP fees, often $200–$2,000/month
New cloud ERP, single country, 25–100 users4–8 months$80,000–$400,000$70–$250 per user/month
New cloud ERP, Saudi Arabia + UAE, 50–200 users6–12 months$150,000–$750,000$70–$250 per user/month, plus two e-invoicing services
Enterprise multi-entity rollout9–18 months$600,000–$3M+Negotiated enterprise terms

The biggest cost drivers are the number of legal entities, the number of invoicing units to register with ZATCA, Arabic form design, integrations with payroll, banks and warehouse systems, data migration quality, and any premium for in-country hosting. A second country typically adds 20–40% to a single-country project, not 100%, because design work and core configuration are shared.

A worked example (hypothetical)

Say a distributor has its headquarters in Riyadh, a branch in Dubai, 70 ERP users and about AED 80 million in UAE revenue. That puts the UAE entity in the first group, with a go-live around the start of 2027. The sensible order is Saudi Arabia first, including ZATCA clearance. The UAE entity follows six to eight weeks later on the same instance, with its ASP integration tested during the pilot window. Under the ranges above, implementation would cost roughly $250,000–$450,000. Subscriptions would run about $90,000–$180,000 a year, plus e-invoicing fees in both countries. Hold 15% contingency for Arabic layouts and master data cleanup.

Next step

Before issuing an RFP, build one table listing each legal entity, its revenue band, its ZATCA wave or UAE deadline, and any residency obligations from regulators or customer contracts. Shortlist only vendors that can show live clearance in Saudi Arabia, a named ASP connection in the UAE, and a contract-backed tenant location. If your earliest deadline is less than six months away, connect your current system first and replace the ERP afterward. Don't try to do both at once.

Common questions

Does our cloud ERP have to be hosted in Saudi Arabia to comply with ZATCA?

No. ZATCA's e-invoicing rules cover invoice format, cryptographic stamping, clearance and reporting. They don't set the hosting location. Hosting requirements come from the Personal Data Protection Law, NCA cybersecurity controls for government and critical infrastructure, sector regulators such as SAMA, and customer contracts. Have local counsel confirm which apply to your business.

Can one ERP instance handle both ZATCA and UAE e-invoicing?

Yes, as long as each country is set up as a separate legal entity with its own tax configuration and e-invoicing connector. Saudi entities send invoices for clearance through ZATCA's Fatoora platform. UAE entities exchange invoices through an Accredited Service Provider. Some providers cover both countries, which reduces the number of vendors you manage.

What happens if our ERP misses our ZATCA integration wave deadline?

ZATCA can impose penalties for failing to meet e-invoicing obligations, and invoices that aren't properly cleared may not be treated as valid tax invoices. Buyers may also refuse or delay payment on them. If your deadline is close, a certified standalone connector on your current system is usually faster than rushing a full ERP replacement.

Do UAE e-invoicing rules apply to B2C sales?

Under the program as published, the first phase covers B2B and B2G transactions, and B2C is not included for now. Retailers still need correct VAT invoicing and should design master data with future expansion in mind. Confirm the current scope with the Ministry of Finance or your tax adviser, because phase details can change.

How much should we budget for Arabic localization?

If the ERP already supports right-to-left output and an Arabic interface, plan for roughly $5,000–$30,000 for bilingual invoice, statement and delivery note layouts, plus translation of item and customer master data. Costs rise sharply if the product needs custom work to print Arabic correctly. These are typical 2026 ranges that vary by partner, so get fixed quotes for the layouts during the RFP.

Written by the Carrier Deskapp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.