1. Home
  2. Blog
  3. Cloud ERP Architecture: Tenancy, Upgrades, Integration and Shared Security

Cloud ERP Architecture: Tenancy, Upgrades, Integration and Shared Security

  • 8 min read
  • Tranquil team

Cloud ERP architecture decides the answers to questions buyers usually ask only after go-live: why last weekend’s upgrade changed the layout of a custom invoice, why the bank file cannot be sent from the system, and how many documents must be keyed in again if the database fails at three in the afternoon. A price comparison does not answer any of these, and neither does a vendor’s statement that the data is safe.

The cost of moving and the migration steps are covered in our cloud ERP migration guide. This page looks at the structure underneath: how customers share the system, how it changes over time, how it connects to banks and ZATCA, how it is backed up, and which part of security belongs to the vendor and which to you.

What cloud ERP architecture covers

NIST Special Publication 800-145, the usual reference definition, describes cloud computing by five essential characteristics, three service models and four deployment models. The characteristics are on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service. A traditional ERP copied onto a rented server usually has neither rapid elasticity nor measured service, even if the vendor calls it cloud.

For an ERP buyer the definition matters less than five practical questions, which the sections below take in order:

  1. Who else runs on the same system?
  2. How and when does it change?
  3. How does it exchange data with other systems?
  4. How quickly can it be restored, and to what point?
  5. Who is responsible for each layer of security?

Single-tenant and multi-tenant cloud ERP

In a multi-tenant system all customers run on one copy of the application and usually one database platform, with each company’s data kept apart logically. In a single-tenant system each customer has its own application instance and database, managed by the vendor. A third pattern, often sold under the same name, is a hosted installation, where a conventional ERP is copied onto cloud servers and run by the vendor or a partner.

Question Multi-tenant Single-tenant Hosted installation
Upgrades Same release for everyone, on the vendor’s date Can be scheduled per customer Usually a paid project
Changes to code Rarely allowed; configuration only Sometimes, at the customer’s cost Usually allowed
Running cost Lowest, shared Higher Server rent plus support
What to ask Release notice and test window Who patches the instance Who patches the server and database

Neither tenancy model is safer by design. What changes is control over timing. A company that cannot accept a release in the week of the VAT return or the year-end close needs to know, before signing, how much notice the vendor gives and whether a release can be deferred.

Environments, upgrades and customizations

A cloud ERP is never finished. The vendor fixes defects and ships new features, and the company changes its own settings, approval steps and print layouts. Both kinds of change need somewhere to be tried first, so ask whether you get a test environment with a recent copy of your own data, and how often it can be refreshed.

The bigger architectural question is how customization is done. Configuration (settings, switches, approval rules, report layouts) survives upgrades because the vendor tests the product with those options. Changes to the vendor’s code do not, and every release becomes a small project of its own. The rule we apply in implementations is to exhaust configuration before accepting any code change, and to keep a written list of every code change that remains.

After each release, test the few processes that hurt most when they fail: posting a sales invoice and its e-invoice submission, preparing the VAT return, posting payroll to the ledger, and printing the documents customers and suppliers see. That takes an hour and catches most surprises.

The integration layer: APIs, files and government platforms

An ERP exchanges data in two ways. An API lets another system read or write records directly, one transaction at a time. A file exchange moves a batch, such as a bank payment file, an Excel import of opening balances or a price list. Most mid-sized companies use both, and the useful question for each link is who owns it when it stops working.

For a business already in ZATCA’s integration phase, e-invoicing is the link it depends on most. In that phase, standard tax invoices (B2B) are cleared by ZATCA before they reach the buyer, and simplified invoices (B2C) are reported after they are issued. The architecture should keep a log of every submission and its response, hold failed submissions in a queue rather than losing them, and show the finance team which invoices are still pending at month-end.

Backup, recovery and a worked example

Two numbers describe recovery. The recovery point objective (RPO) is how much recent data you can lose, measured in time. The recovery time objective (RTO) is how long the system can be down before it is back. Both should be written in the contract, and the vendor should be able to say when a restore was last tested.

The figures below are hypothetical. A distributor posts about 240 documents per working day (invoices, receipts, goods receipts, transfers) over ten working hours, so about 24 an hour. The worst-case loss is everything posted since the last recovery point.

Recovery point Worst-case data loss Documents to re-enter
One backup each night Up to one working day 240
Every 4 hours Up to 4 hours 4 × 24 = 96
Every hour Up to 1 hour 24

Re-keying is only half the cost. Invoices that ZATCA cleared or received before the failure already exist on its side with their numbers, so posting them again as new invoices would create duplicates. A recovery plan for a Saudi company needs a step that compares the restored invoice register with the e-invoice log before anyone starts invoicing again.

Shared responsibility: who secures what

In a cloud ERP the vendor secures the platform and the customer secures its use of it. The split below is typical for a multi-tenant system. The exact line belongs in the contract.

Layer Vendor Customer
Data center, network, servers Yes Check the vendor’s evidence
Operating system and database patches Yes No
Application security fixes Yes Test after release
Backups and restore tests Yes Agree RPO and RTO
User accounts and roles Provides the tools Yes
Two-factor sign-in and leavers Provides the tools Yes
Exported reports and files No Yes

The customer side is where we see most problems in practice. Shared logins at the warehouse counter, accounts left active after an employee resigns, and an administrator role given to everyone during go-live and never taken back. None of these is solved by a better data center.

Saudi rules that shape cloud ERP architecture

The National Cybersecurity Authority (NCA) publishes the Essential Cybersecurity Controls (ECC, current version ECC 2-2024) and, as an extension of them, the Cloud Cybersecurity Controls (CCC-2:2024). The CCC applies to cloud service providers that serve customers in scope, and to customers that are government agencies or private entities that own, operate or host critical national infrastructure. The NCA strongly encourages other organizations to use the controls as best practice.

The 2024 CCC removed the subcontrols that required cloud services, including storage, processing and disaster recovery, to be provided from inside the Kingdom. The NCA’s stated reason is that data localization now sits with the National Data Management Office at SDAIA, so in-scope entities check hosting location against NDMO requirements.

The Personal Data Protection Law, applied by SDAIA, covers the personal data an ERP holds, such as employee files, salaries and customer contacts. The controller must choose a processor that gives guarantees of compliance (Article 8), take organizational, administrative and technical measures to protect the data (Article 19), notify the competent authority of a breach (Article 20), and transfer personal data outside the Kingdom only as Article 29 and SDAIA’s transfer regulation allow.

For an ERP contract this means asking where the data, its backups and the vendor’s support staff are located.

How Tranquil ERP fits this architecture

Tranquil ERP is a web application used in the browser. The ERP area and HR and payroll share one login, one organization setup and one chart of accounts, and every screen switches between English and Arabic. Behavior is changed by configuration rather than code. Version 2.11 has 166 on/off company switches, approval settings per document, and a Report Designer for custom PDF layouts.

On the customer side of security, Tranquil has roles with screen-level access, per-user limits on departments, warehouses, price lists and cost centers, and two-factor authentication per user.

For integration, it has Excel templates for masters and opening balances, ZATCA Phase 2 onboarding per branch in Sandbox, Simulation or Production mode with a log of every call, and mobile apps for employee self-service and production workers.

Hosting location, backup frequency and recovery targets are contract terms, and you should ask for them in writing, from us as from any vendor. The product is described on the Tranquil ERP features page, and the wider case for moving is in cloud ERP software in Saudi Arabia.

Frequently asked questions

Is multi-tenant cloud ERP less secure than single-tenant?

Not by design. Both depend on how well the vendor separates and protects data, which you check through its controls and audit evidence. The real difference is control over timing, because a multi-tenant system upgrades every customer on the vendor’s schedule.

Do the NCA cloud controls apply to a private company?

Only if it owns, operates or hosts critical national infrastructure, or provides cloud services to customers in scope. Other private companies are not bound by the CCC, but the NCA strongly encourages them to use the controls as best practice, and customers sometimes write them into contracts.

Does the PDPL require ERP data to be hosted in Saudi Arabia?

The law does not ban hosting abroad outright. It limits transfers of personal data outside the Kingdom to the purposes and conditions in Article 29 and SDAIA’s transfer regulation. Government entities and some sectors have their own hosting rules, so check those before choosing a vendor.

What should a cloud ERP contract say about backups?

It should state the recovery point and recovery time objectives, how often restores are tested, where backups are kept, and how you get a full export of your data in a readable format if the contract ends.

See what this article covers in Tranquil

In the demo we show what this article covers on Tranquil’s own screens and answer your team’s questions.

Dammam +966 13 848 8080, +966 13 817 7724, Riyadh +966 11 213 1330
[email protected]
Sunday to Thursday, 8 am to 5 pm.