Construction ERP

Odoo ERP for Saudi Construction: Multi-Project Cost Control, IKTVA, and Subcontractor Management

Saudi construction companies running multiple Vision 2030 projects face a financial visibility problem: costs committed months before invoices arrive, subcontractors on milestone billing, materials tracked across sites, and IKTVA reporting due on every government contract. Odoo connects all of it in one system.

iWesabe Editorial TeamMarch 3, 202513 min read

Saudi Arabia's construction sector is executing a project pipeline that has no precedent in the region — NEOM, Red Sea Project, Diriyah, Qiddiya, King Salman Park, and hundreds of supporting infrastructure and housing programmes running simultaneously under Vision 2030. For Saudi contractors of every size, this creates a financial management challenge that generic accounting software cannot handle: multiple projects, each with its own cost structure, subcontractor network, materials procurement, and IKTVA local content obligation, must be tracked in parallel without confusion between project P&Ls, committed costs, and cash positions.

This article covers how Odoo ERP addresses the five core operational demands of a Saudi construction company: multi-project cost control, WIP (Work in Progress) accounting, subcontractor milestone billing and retention management, IKTVA local content tracking at the purchase order level, and NIDLP-aligned Saudisation reporting for construction site labour. The result is a single system that connects the project site to the finance team — and produces the reports that government clients, Zakat auditors, and IKTVA reviewers actually ask for.

What Are the Biggest Financial and Operational Challenges for Saudi Construction Companies?

Construction finance is structurally different from trading or service company finance. The challenges below are specific to the sector and consistently appear across Saudi contractors regardless of company size:

  1. Cost committed months before invoices arrive. In construction, materials are ordered and labour is deployed weeks or months before the owner invoices the client. Without a system that captures committed costs at the purchase order and timesheet level — not at the invoice — the project P&L is always understated during the project and overstated at close. A Saudi contractor running SAR 50–200M of simultaneous projects on this basis is flying blind on real margin.
  2. Multiple project P&Ls that must not bleed into each other. When a contractor runs five projects from a single accounting system without proper cost centre separation, materials purchased for Project A routinely end up posted against Project B. The correction exercise at year-end — or during a Zakat audit — can take weeks and typically reveals that the CFO's per-project profitability numbers were unreliable throughout the year.
  3. Subcontractor billing tied to physical progress milestones, not calendar dates. Saudi construction contracts typically pay subcontractors when a defined scope of work is completed and certified — a structural concrete pour, a mechanical systems test, a finishing handover. Managing these milestone-linked invoices, tracking partial completions, and enforcing retention deductions requires a system that connects purchase orders to milestone progress, not just a standalone accounts-payable ledger.
  4. IKTVA local content obligations on every government and Aramco-linked contract. The In-Kingdom Total Value Add (IKTVA) programme requires contractors to demonstrate a minimum percentage of local spend — Saudi-manufactured materials, Saudi subcontractors, Saudi direct-hire labour — in their project cost base. This data must be captured at the purchase order level, attributed to each contract, and reported in a format that satisfies the client's IKTVA reviewer. A spreadsheet built after the project is complete cannot produce an auditable trail.
  5. Cash flow forecasting when billing cycles lag committed costs by 60–90 days. Construction companies consistently face a cash conversion gap: costs go out in week one, progress invoices go to the client in week eight, and payment arrives in week twelve. Without a system that forecasts the committed-cost outflow against expected billing receipts across all active projects, the finance team manages cash by gut feel — and typically discovers a shortfall when it is already a problem.

Running multiple construction projects in Saudi Arabia?

iWesabe has implemented Odoo for Saudi contractors managing Vision 2030 projects — multi-project cost control, IKTVA reporting, subcontractor billing, and Saudi payroll in one system. Talk to us about your project portfolio.

How Does Odoo Manage Project Costs Across Multiple Saudi Construction Sites?

Odoo's project and accounting modules share a single data model, which means every cost transaction — purchase order, supplier invoice, labour timesheet, equipment rental — posts against a specific project and cost category in real time. There is no end-of-month allocation exercise and no risk of cross-project contamination when cost centres are defined correctly at project setup.

How Odoo manages the five core construction cost categories for Saudi contractors
Cost CategoryHow Odoo Captures ItWhat the Finance Team Sees
MaterialsPurchase orders raised against a project and cost centre; goods receipt confirms delivery; supplier invoice matched to POReal-time committed cost from PO confirmation; actual cost at goods receipt; three-way match before payment
Direct labour (own workforce)Timesheets by employee linked to project; Odoo HR/Payroll calculates gross cost including GOSI, EOSB accrual, and allowancesLabour cost per project per week; payroll liability broken down by project contribution; GOSI deduction allocated to project
SubcontractorsSubcontractor purchase orders tied to project, scope, and milestone list; payment released only after milestone completion is confirmed in the systemCommitted subcontractor cost by milestone; amount retained (held back) vs. amount paid; progress billing status per subcontractor
Equipment and plantEquipment rental POs or internal allocation from owned fleet; usage hours logged against project via timesheet or work orderEquipment cost per project including depreciation allocation for owned plant; rental cost vs. utilisation rate analysis
Overheads (site office, utilities, insurance)Overhead cost centre defined per project; indirect costs allocated by formula (fixed % of direct cost, or by headcount ratio) or manually distributed each periodOverhead absorption rate per project; total project cost including overhead allocation for client billing and Zakat deductibility purposes

How Does Odoo Handle Subcontractor Billing, Milestones, and Retention in Saudi Construction Contracts?

Saudi construction contracts almost universally use milestone-based progress billing for subcontractors, with a retention percentage (typically 5–10 %) withheld until the defects liability period expires. Managing this across a portfolio of subcontractors — some with five milestones, others with twenty — requires a system that tracks physical progress, not just invoice dates.

  • Milestone-linked purchase orders. Each subcontractor PO in Odoo lists the scope milestones and the payment amount tied to each. When the site engineer marks a milestone complete in the system, Odoo triggers the corresponding payable and allows the subcontractor invoice to be matched and approved — no milestone confirmation, no payment release.
  • Retention tracking. Odoo's purchase module supports retention deduction on subcontractor invoices — a configurable percentage held from each payment and tracked as a retention payable separate from the main balance. At the end of the defects liability period, the retention payable is released and settled. The finance team always sees the total retention held across all active projects as a distinct balance sheet item.
  • Partial billing against scopes-of-work. Not all subcontract milestones are binary (done / not done). Where a milestone is measured by completion percentage — earthworks 60 % complete, structural steel 45 % erected — Odoo allows partial billing against the milestone value, with the balance carried forward to the next assessment. This is essential for FIDIC-based contracts commonly used in Saudi government and Aramco projects.
  • GOSI compliance for direct-hire site labour. When a Saudi contractor employs workers directly on site (rather than through a subcontractor), Odoo's HR and payroll module manages GOSI deductions, WPS/Mudad submission, and EOSB (End of Service Benefits) accruals per the Saudi Labour Law — all attributed to the project. Nitaqat Saudisation headcount is tracked at the employee record level, allowing the contractor to report the Saudi workforce percentage on any project at any point.

How Does Odoo Support IKTVA Local Content and NIDLP Compliance for Saudi Contractors?

IKTVA (In-Kingdom Total Value Add) is now a scoring requirement on most Aramco-related and a growing number of government-sector construction contracts in Saudi Arabia. Contractors that cannot demonstrate their IKTVA score digitally are at a disadvantage in tender evaluation — and risk contract non-compliance if they cannot produce auditable evidence during project execution.

How Odoo captures IKTVA and NIDLP data at the point of transaction for Saudi construction companies
Compliance AreaWhat the Programme RequiresHow Odoo Captures It
IKTVA — local material spendPercentage of materials sourced from Saudi-manufactured products or in-Kingdom suppliersVendor master record flags supplier nationality and origin country; purchase orders tagged to contract; IKTVA spend % calculated automatically from PO data per contract
IKTVA — Saudi subcontractor spendPercentage of subcontracted work awarded to Saudi-registered companiesSubcontractor vendor records flagged by registration type (Saudi-registered vs. foreign); subcontractor POs tagged to contract; Saudi subcontract value % calculated per project
IKTVA — Saudi direct-hire labour spendPercentage of direct labour cost attributable to Saudi nationals employed on the projectEmployee nationality recorded in HR module; timesheets linked to project; Saudi vs. non-Saudi labour cost split calculated from payroll per project
NIDLP — Saudisation percentage for construction tradesMinimum Saudi national percentage in the contractor's workforce, broken down by occupational category per HRSD activity classificationEmployee nationality and occupational category stored in HR module; Nitaqat classification applied at employee record level; NIDLP-compliant headcount report generated by project or at company level

What Does the Odoo Construction Module Stack Look Like for a Saudi Contractor?

A typical Odoo implementation for a Saudi construction company covers these modules, deployed in a phased sequence starting with the highest compliance risk (finance and ZATCA) and expanding to operations and project management:

Odoo module stack for Saudi construction companies: function, module, and KSA-specific capability
Construction FunctionOdoo Module(s)KSA-Specific Capability
Project cost tracking and budget controlProject + AccountingMulti-project cost centres; budget validation before PO is confirmed; real-time cost-to-complete calculation; Zakat-ready project P&L
Procurement and IKTVA trackingPurchaseVendor nationality flag; IKTVA spend % per contract; three-way PO/receipt/invoice match; multi-currency for imported materials with SAR accounting
Subcontractor managementPurchase + AccountingMilestone-linked POs; retention deduction and tracking; partial milestone billing; certified payment application workflow
Client billing and progress invoicingAccounting + ProjectZATCA Phase 2 compliant sales invoices; progress billing schedule linked to project milestones; client retention (receivable) tracking; Arabic RTL invoice format
Materials and site inventoryInventoryMulti-site warehouse tracking; lot/serial numbers for SFDA-regulated materials; perpetual inventory valuation in SAR; goods receipt against project PO
Direct-hire labour and Saudi complianceHR + PayrollGOSI deduction and EOSB accrual per project; WPS/Mudad SIF file generation; Nitaqat Saudisation tracking; timesheets linked to project for labour cost allocation
Tender and client relationship managementCRMOpportunity pipeline for government tenders; bid cost tracking; win-rate analysis by project type; client history and document management for repeat contractor relationships

Why Do Saudi Construction Companies Choose iWesabe for Odoo Implementation?

200+
Odoo implementations across Saudi Arabia and the Gulf — including construction, contracting, and real estate sectors
14+
years as a certified Odoo Gold Partner in KSA
3
Odoo awards — Best Partner MENA 2023, Highest Revenue KSA 2022/2023, Top Revenue Achiever KSA 2023/2024

Saudi construction companies implementing Odoo need a partner with two capabilities that most generalist implementation firms lack: deep Odoo module knowledge across project, procurement, HR, and accounting; and direct familiarity with the Saudi-specific requirements — ZATCA Phase 2 for progress billing invoices, IKTVA reporting format for Aramco and government clients, GOSI and WPS/Mudad for direct-hire site labour, and Nitaqat classification for construction trades. iWesabe brings 14+ years of certified Odoo delivery in the Saudi market, is the first Gulf partner to hold Odoo certification across all versions from v10 to v19, and has delivered 200+ implementations across the Kingdom and the Gulf — including contractors managing Vision 2030 project portfolios. The three Odoo awards (Best Partner MENA 2023, Highest Revenue KSA 2022/2023, Top Revenue Achiever KSA 2023/2024) reflect consistent delivery, not a single landmark project.

Saudi Arabia's most awarded Odoo Gold Partner

200+ implementations across KSA and the Gulf. 14+ years as a certified Odoo Gold Partner. Full KSA localisation: ZATCA Phase 2, GOSI, WPS/Mudad, Nitaqat, IKTVA tracking.

If you are a Saudi contractor running multiple projects and want to understand how Odoo can be configured for your specific contract types — government, Aramco-linked, private sector — and your IKTVA reporting obligations, we offer a free 90-minute construction ERP workshop that maps the implementation to your project portfolio.

Ready to connect your project sites to your finance team?

Tell us about your project portfolio, your contract types (government, Aramco, private), and your current cost-tracking method. We will map the Odoo construction setup that fits your operations.

WhatsApp

Frequently Asked Questions

Can Odoo manage multiple construction projects simultaneously in Saudi Arabia?
Yes — Odoo's project and accounting modules are designed for multi-entity, multi-project environments. Each project is assigned its own cost centre, budget, and P&L in the accounting module. Every purchase order, supplier invoice, timesheet, and materials movement is attributed to a specific project in real time, so there is no cross-project contamination and no end-of-month allocation exercise. A Saudi contractor running five simultaneous projects sees a separate budget vs. actual report for each, plus a consolidated view across all active projects — updated continuously, not compiled monthly.
How does Odoo handle WIP (Work in Progress) accounting for Saudi construction contractors?
Odoo handles WIP accounting through the project and accounting modules working together. Costs incurred on a project — materials, labour, subcontractors, equipment — are accumulated against a WIP asset account until the corresponding revenue milestone is billed to the client. When a progress invoice is raised, the recognised revenue is transferred from the WIP balance to the income statement. This produces a SOCPA-compliant balance sheet where the WIP balance accurately reflects incurred-but-unbilled project costs — critical for Zakat base calculations and auditor review.
Does Odoo support IKTVA local content tracking for Saudi construction and Aramco-linked projects?
Yes — Odoo captures IKTVA-relevant data at the vendor master level and at purchase order creation, which is the only way to build an auditable IKTVA trail. Vendor records store supplier nationality and material origin country. Purchase orders are tagged to the specific government or Aramco contract. Odoo then calculates the Saudi-origin spend percentage across materials, subcontractors, and direct labour for each contract — producing a report that matches the IKTVA scoring categories. Because the data is captured at the point of transaction, the IKTVA score is always current and auditable without requiring manual retrospective compilation.
How does Odoo manage subcontractor milestone billing and retention in Saudi construction contracts?
Odoo manages subcontractor billing through milestone-linked purchase orders. Each subcontractor PO lists the defined scope milestones and the payment value tied to each. Payment is only released when the site team confirms milestone completion in the system. Retention deductions are configured per subcontractor contract — typically 5–10 % of each certified payment — and tracked as a separate retention payable on the balance sheet until the defects liability period expires and the retention is released. For contracts with partial milestone billing (completion percentages rather than binary done/not done), Odoo supports partial invoice matching against the milestone value.
Can Odoo track Saudi labour compliance — GOSI, WPS, and Nitaqat — for workers employed on construction sites?
Yes — for workers employed directly by the contractor (not through subcontractors), Odoo's HR and payroll module handles all three Saudi labour compliance obligations. GOSI contributions are calculated automatically per the current contribution rates and salary ceiling, deducted from employee pay, and recorded as employer liability by project. WPS compliance is managed through automatic SIF file generation each payroll cycle for submission to Mudad. Nitaqat Saudisation tracking is maintained at the employee record level — nationality, job classification, and project assignment — allowing the contractor to generate a Saudi workforce percentage report for any project at any point in time.
What is the typical Odoo implementation timeline for a Saudi construction company?
A Saudi construction company implementing Odoo across finance, procurement, project management, and HR/payroll follows a phased timeline of 14–20 weeks for a mid-market contractor (SAR 50M–200M annual revenue, 3–8 active projects). The typical sequence: finance and ZATCA go-live in weeks 8–12, followed by procurement and subcontractor management in weeks 10–14, then inventory and HR/payroll in weeks 14–20. Companies with more complex multi-entity structures or extensive IKTVA reporting requirements typically run 18–26 weeks. The phased approach avoids the training overload that causes full simultaneous go-lives to destabilise in the first 90 days.
iWesabe Editorial Team

iWesabe Editorial Team

Practitioner insights on Odoo ERP, ZATCA compliance, and Saudi enterprise digital operations — written by iWesabe's consulting, finance, and engineering teams.

About iWesabe

Related Articles