Facility Management ERP, Saudi Arabia

Government clients, penalties and long approval chains

A large share of FM spending in the Kingdom comes from government entities, government-owned companies and major developers. Their contracts tend to specify staffing levels by role, performance indicators with penalty deductions, detailed monthly reporting and formal invoice approval steps that can involve several departments. Payment timing then depends on how complete the supporting evidence is: attendance records, completed PPM reports, KPI results and sometimes photographs or signed job sheets.

This changes what the ERP must do. The contract record should store required staffing per role and site, the penalty schedule and the evidence the client expects with each invoice. Billing should start from actual staffing and performance, not from the contract value, so deductions are calculated before the client calculates them. Receivables need tracking by approval stage, because a submitted invoice waiting for a committee is a different problem from an approved invoice waiting for payment. I document these steps with your contracts and finance teams and test them using one of your real monthly submissions. Interpretation of contract terms stays with your legal and commercial advisors.

Saudization, workforce housing and wage protection

FM providers in Saudi Arabia employ a mix of Saudi nationals and expatriate workers, and localization requirements under the Nitaqat program influence hiring decisions, entity structure and sometimes how easily a company can staff a new contract. HR usually tracks this in its own tools and official platforms, but the ERP should hold the data that lets management see workforce mix by entity and contract and understand its cost impact.

Expatriate staff bring residence permit, visa, recruitment and housing costs, while all employees accrue end-of-service benefits. Salaries flow through the wage protection arrangements that apply to private employers, so the payroll process has to produce accurate salary data each month. I map where each of these costs arises and agree allocation rules per contract, and then we weigh a payroll module within the ERP against a Saudi HR and payroll product connected to it. The regulatory rules come from your HR advisors and current official guidance; I make sure the system design can carry them and that contract margins include every element of workforce cost.

ZATCA e-invoicing, zakat, VAT and Arabic

Every monthly FM invoice, penalty credit note and advance invoice has to follow ZATCA's e-invoicing rules, which for many taxpayers include integration with the authority's platform. When you evaluate platforms, ask each vendor or implementer to demonstrate their compliance approach on your own invoice types rather than relying on a general statement, and have your tax advisor confirm the details. VAT applies to most services, and zakat or income tax depends on your ownership, so the chart of accounts and entity setup should reflect advisor guidance from the outset.

I also check how each platform handles a credit note raised long after the original invoice, because KPI penalties are often agreed late in the approval cycle. Arabic is the primary language for contracts and invoices, frequently with English alongside, and some clients reference Hijri dates in contract periods and payment terms. Print layouts, right-to-left handling and date formats belong in the demo script. More on the national context is on the Saudi Arabia hub and the Saudi ERP consultant page.

Multi-region mobilization and migration

Saudi FM providers often mobilize several contracts at once in different regions, with assets and PPM schedules handed over from previous contractors in inconsistent formats. Without a standard setup, every region ends up with its own site codes and cost centers, and consolidated reporting breaks. I define a mobilization checklist the system enforces: sites, assets, staffing plan, housing assignment, billing schedule and cost structure must be complete before the contract goes live.

Many companies start from an older local accounting system, a separate HR and payroll package, a CAFM or helpdesk for technical work and spreadsheets for billing and penalties. What moves across: current staff with cost data, contracts in force, unfinished jobs and outstanding ledger balances; closed history remains in the old system for lookup. I recommend a pilot contract in one region before rolling out further. I am not tied to any product, so I can work next to whichever implementation partner you appoint. See ERP for facility management for the overall approach, the service management problem page, and ERP implementation for how I oversee delivery.