ERP Integration With Saudi Government Platforms

Why ERP Integration With Saudi Government Platforms Matters

A typical Saudi company with a hundred employees deals with a long list of government platforms every month. Sales invoices are cleared or reported through ZATCA's Fatoora system. Wages go through the Wage Protection System on Mudad. Contributions are settled with GOSI. Expatriate staff need iqama renewals and exit and re-entry visas through Muqeem. Employment contracts and Saudization status sit on Qiwa. Government contracts run on Etimad. Annual financial statements are filed on Qawaem.

Each platform asks for data the company already has somewhere: an employee's basic wage and housing allowance, an invoice total and VAT amount, a passport number and iqama expiry. When that data is typed again into each platform, three things happen. Staff time goes into re-entry, small differences creep in between systems, and deadlines are missed because nobody saw them coming.

ERP integration with Saudi government platforms means the ERP becomes the source of that data and the place where deadlines are tracked, with information passed to each platform through an official interface, a structured file or a controlled manual step. This guide explains what each major platform needs, how integration works in practice, what to automate first and how to avoid the mistakes that cause penalties.

The Main Platforms and What They Need From Your ERP

Platform by Platform

ZATCA e-invoicing (Fatoora)

This is the one integration that is mandatory by design. Phase 1, generation of electronic invoices, started on 4 December 2021. Phase 2, integration with ZATCA, is rolled out in waves from 1 January 2023. Wave 24 covered taxpayers with turnover above SAR 375,000 in 2022 to 2024 and had to integrate between 1 April and 30 June 2026. Wave 25 covers turnover above SAR 187,500 in any year from 2022 to 2025, with compliance due from 1 February 2027. ZATCA notifies each taxpayer of its wave at least six months in advance.

In Phase 2, standard tax invoices (B2B and B2G) are cleared by ZATCA in real time before being shared with the buyer, while simplified invoices (B2C) are reported within 24 hours. Each invoice-generating unit needs its own cryptographic stamp identifier, obtained through an onboarding process in the Fatoora portal. Note that there is no official "Phase 3"; vendors who sell a "Phase 3 upgrade" are using a marketing label.

Because the invoice has to come from the system that holds the sale, this integration belongs inside the ERP. A separate invoicing tool that someone feeds manually defeats the point and creates reconciliation gaps. Our e-invoicing guide covers the requirements in more detail.

VAT and zakat returns

VAT returns are filed monthly if annual taxable turnover exceeds SAR 40 million and quarterly otherwise, due by the last day of the month after the period. Zakat and income tax returns are due within 120 days of the year end. Returns are submitted on ZATCA's portal, but the figures come from the ERP: output VAT by rate, input VAT from valid tax invoices, and adjustments such as credit notes and reversals of input tax where suppliers have not been paid within 12 months. An ERP that produces a VAT return working paper, reconciled to the general ledger, turns filing from a week of work into a review.

Mudad and the Wage Protection System

Employers upload a monthly wage file through Mudad showing what each employee was paid. Since 1 March 2025, the file must be uploaded within 30 days, down from 60. Mudad also raises alerts when a recorded basic wage looks inconsistent with other data or when deductions exceed 50% of wage. The ERP's role is to produce payroll that matches the contract and the bank transfer exactly, and to export the file in the required layout. Our article on WPS and Mudad compliance goes deeper.

GOSI

Contributions are calculated on basic wage plus housing allowance, capped at SAR 45,000 a month. Under the existing system, Saudi employees contribute 9.75% and employers 11.75%; for expatriates the employer pays 2% for occupational hazards. Employees who joined from 3 July 2024 with no prior contributions fall under the new Social Insurance Law, where the annuity rate started at 9% each side and rises by half a point every 1 July: 9.5% from July 2025, 10% from July 2026, up to 11% in July 2028. Older articles that quote a flat "12% plus 10%" are simply wrong. An ERP should hold each employee's scheme and calculate the right rate automatically, so that payroll and GOSI agree each month.

Qiwa and Nitaqat

Employment contracts are registered on Qiwa, which also shows the establishment's Nitaqat band. Nitaqat sets a minimum Saudization rate by activity, rising with headcount, and places establishments in bands from Platinum to Red. A Red band blocks new visas, work permit renewals and transfers in. The ERP cannot change your band, but it can show the effect of each hiring or leaving decision on your Saudi ratio before it happens, which is far better than finding out on Qiwa afterwards.

Muqeem

Muqeem is used by employers to manage services for expatriate employees, such as iqama renewals, exit and re-entry visas and related enquiries. The integration value here is in data and timing: holding passport and iqama numbers and expiry dates in the HR record, alerting before expiry, and reducing manual look-ups.

Etimad

For contractors and suppliers to government entities, Etimad handles tendering and contract management. A new Government Tenders and Procurement Law was published on 4 September 2026 and takes effect on 2 January 2027, replacing the 2019 law. The ERP should link each government contract to its bid and performance guarantees, claims and payments, so cash flow from government work is visible.

Qawaem, Salamah and other periodic platforms

Companies must file financial statements on the Ministry of Commerce's Qawaem platform within six months of the financial year end. Commercial and industrial establishments, including warehouses, also need a Civil Defense fire-safety licence through the Salamah platform, renewed periodically. Commercial leases are registered on Ejar. These are not daily transactions, but each has a deadline that an ERP's document and expiry tracking can hold in one calendar.

How Integration Actually Works

It helps to be realistic about what "integration" means, because platforms differ and vendors sometimes overpromise.

• Direct system-to-system interface: ZATCA e-invoicing is the clearest example, with a documented onboarding process and real-time clearance. The ERP talks to the platform without anyone re-entering data.
• Structured file exchange: the ERP generates a file in the layout the platform expects, and an authorised user uploads it. Wage files are a typical case. This removes re-keying while keeping a human approval step.
• Bank channel: salaries and some government payments flow through the company's bank. ERP-to-bank integration sends payment instructions directly and brings back confirmation.
• Data and deadline management: where no interface is available or appropriate, the ERP holds the master data, calculates what is due and tracks the deadline, and the submission is done on the platform by an authorised person.

Before you sign with a vendor, ask which of these methods applies to each platform on your list, and ask to see it working. A clear answer for each platform is worth more than a long list of logos.

A Worked Example of the Monthly Cycle

Consider a hypothetical contracting company with 140 employees, 40 Saudi and 100 expatriate, and two branches under one legal entity. Here is how one month looks when the ERP is the source of truth:

1. Day 1 to 25: attendance and overtime are recorded. Overtime is paid at the hourly wage plus 50% of basic wage, as the Labor Law requires. Iqama expiry alerts for the next 60 days go to HR.
2. Day 26: payroll is calculated. GOSI rates are applied per employee scheme: existing-system Saudis, new-law Saudis and expatriates each get the correct rate.
3. Day 28: after approval, salary instructions go to the bank and the wage file is exported for Mudad, both generated from the same approved payroll.
4. Throughout the month: every sales invoice is cleared or reported through Fatoora at the moment it is issued.
5. Quarter end: the VAT working paper is produced from the ledger, reviewed and filed by the end of the following month.

The difference is not that people stop working on compliance. It is that they review exceptions instead of re-entering data, and the same figure appears in payroll, the bank file, Mudad and GOSI.

What to Integrate First

Common Mistakes

• Integrating dirty data: if an employee's iqama number or wage is wrong in HR, automation simply sends the wrong figure faster. Clean master data first.
• Two payroll truths: paying salaries from one spreadsheet and producing the wage file from another guarantees mismatches.
• Ignoring entity structure: branches of one legal entity invoice under one VAT number, while separate legal entities need their own registrations, wage files and Nitaqat status. Set up the ERP to match the legal structure.
• No fallback: platforms have maintenance windows. Know who does what if a submission cannot go through on the day.
• Treating integration as finished: rules change, as the GOSI rate steps and the WPS deadline show. Assign someone to watch for updates.
• Sharing logins: platform access should be personal and role-based, not one shared password for the HR team.

Controls, Security and Audit Trail

Government data flows carry personal and financial information, so integration is also a governance question. The Personal Data Protection Law has been enforced since September 2024, and payroll, iqama and passport data are exactly the kind of personal data it protects. A few controls make a large difference:

• Segregation of duties: the person who edits wages should not be the person who approves the payroll and releases the bank file.
• Approval before submission: wage files, VAT working papers and contract claims should pass a documented review step in the ERP before they leave it.
• Audit log: every change to an employee's wage, bank account or document dates should be recorded with user and timestamp, so a Mudad alert or a GOSI query can be answered from the record.
• Retention: keep submitted files and acknowledgements with the transaction. VAT records generally need to be kept for at least six years.

Measuring the Benefit

Rather than relying on vendor savings claims, measure your own baseline for three months before integration: hours spent each month on re-entering data into platforms, number of corrections or resubmissions, number of renewals that were late, and days taken to close payroll and file VAT. Measure the same items after go-live. These are the numbers that justify the project to management, and they are specific to your company.

How Tranquil Helps

Tranquil is a cloud ERP whose ZATCA e-invoicing supports Phase 1 and Phase 2 compliance with real-time integration, automatic validation and deadline alerts. On the HR side, it offers Muqeem integration for iqama and visa services, bank integration for direct salary transfer, payroll, and document expiry alerts. Customisation services cover API integrations where a business needs a specific connection.

Frequently Asked Questions

Which government platform should we integrate first?

ZATCA e-invoicing, because it is mandatory for your wave and touches every sales invoice. Payroll, the bank and Mudad come next because of the monthly deadline.

Do all government platforms offer APIs?

No. Some, like ZATCA e-invoicing, have a documented integration process. Others work through file uploads, bank channels or manual submission. Ask your vendor exactly which method applies to each platform.

Is there a ZATCA Phase 3?

No official Phase 3 exists. Phase 2 integration is being extended to more taxpayers through waves, with Wave 25 due from 1 February 2027.

What GOSI rates should payroll use?

It depends on the employee. Saudis under the existing system: 9.75% employee and 11.75% employer. New entrants from 3 July 2024 follow a rising annuity schedule, 10% each side from July 2026. Expatriates: 2% employer for occupational hazards.

How does Tranquil handle government integration?

It covers ZATCA e-invoicing, Muqeem integration, bank integration for salaries and document expiry alerts, with customisation available for other API connections. Contact the Tranquil team to map your platform list.