Construction ERP in Saudi Arabia: Job Costing, Progress Claims, Retention, Subcontractors and ZATCA E-Invoicing (2026 Guide)

It is 7 a.m. in the office of a mid-sized contractor in north Riyadh. The projects manager opens the WhatsApp group for the villa compound in Jeddah and finds a photo of a handwritten request for rebar, plus a second request for the same item from the same site engineer two days earlier. Nobody can tell which one was approved. In the next room, the accountant is preparing the monthly progress claim for a warehouse project in Dammam's industrial city and discovers that the quantities in his spreadsheet do not match the quantities the site engineer submitted to the consultant. Meanwhile, the electrical subcontractor on the Khobar project calls to ask about a claim he "sent three weeks ago". Nobody knows which drawer it is in.

At month end, the finance manager tries to answer a simple question from the owner: is the Jeddah project making money so far? He cannot. The rented excavator working in Dammam is charged to the Riyadh project because the rental contract was signed under its name. Labor hours live on paper attendance sheets that are not linked to any cost item. Materials moved from one site store to another left the first project's books and never entered the second. The progress invoice was issued electronically from a generic accounting package, but retention and advance-payment recovery were calculated by hand in a side spreadsheet. The scene is a scenario, but versions of it play out in contracting companies across Riyadh, Jeddah, Dammam and Khobar.

The problem is not the accountant or the site engineer. A contracting company runs on projects, while generic accounting software runs on invoices. That is why contractors need a construction ERP in Saudi Arabia that puts the project and its cost codes at the center, then produces progress claims, tax invoices, payroll and reports from that single source. If you want the broader picture of ERP across sectors in the Kingdom, start with our ERP system in Saudi Arabia guide; this article goes deep on contracting only.

At Jad Digital (جاد للتطوير الرقمي), a Cairo software house building custom business systems since 2019 for clients in Egypt and Saudi Arabia, we serve Saudi clients remotely with on-site visits when needed — and we will tell you honestly when ready-made software is the smarter choice.

A construction ERP in Saudi Arabia is a single system that ties every project's costs to its budget, issues progress claims and ZATCA-compliant electronic tax invoices, manages subcontractors, procurement, site stores, equipment and labor, and shows management each project's profitability and cash flow on any given day.

• The best construction ERP for Saudi contractors builds accounting around job costing and cost codes, rather than adding a "project" field to a generic accounting package.
• A good construction ERP calculates each progress claim from executed quantities, deducts retention and advance-payment recovery automatically, and issues the electronic tax invoice from the same certified claim.
• VAT and e-invoicing in Saudi Arabia require a construction ERP to generate invoices in the format and with the data specified by the Zakat, Tax and Customs Authority (ZATCA) and to connect to its platform; current requirements should always be confirmed with ZATCA directly.
• Payroll in a construction ERP starts from labor hours recorded per project and cost code, flows into the monthly payroll run, and connects to the official wage-protection and social-insurance channels according to the requirements in force.
• Subcontractors are managed in a construction ERP with their own contracts, item rates, claims, retention and back-charges — the mirror image of how the main client is billed.
• Ready-made construction software suits a small contractor with a few similar projects, while a custom construction ERP pays off when projects, cities, subcontractors, equipment and accounting rules multiply.

A contractor needs a system when it can no longer tell whether a project is profitable before it ends. That usually comes with these symptoms:

• Each progress claim takes a week to assemble. Quantities sit with the site engineer, rates in the contract, retention in the accountant's file, and changes in the consultant's emails.
• Nobody tracks budget versus actual. The budget was set at tender stage, and nobody compared it with real spending until the loss appeared at handover.
• Material requests arrive on WhatsApp. A photo of a sheet of paper or a voice note, followed by duplicate purchases or items nobody approved.
• Site stores have no known balance. Rebar, cement and cable move between sites without a document, so some projects look profitable and others look loss-making for the wrong reasons.
• Equipment is not charged to projects. The rented excavator or the company-owned crane works on several sites, but its cost lands in one account.
• Subcontractor claims get lost or delayed. Relationships sour, or subcontractors are paid more than they executed because nobody compared.
• Bank guarantees expire unnoticed. A performance bond or an advance-payment guarantee needs renewal, and the date sits in a file nobody opens.

The core difference is that the unit of work in contracting is the project, and revenue arrives in installments tied to progress, not on delivery of a product. That is why generic accounting and retail systems break quickly for contractors, for specific reasons:

• Cost is measured against a budget per item. Each project has a bill of quantities and a budget per item. The daily question is: how much have we spent on concrete against its estimate, and how much is left?
• Revenue comes through progress claims. The monthly claim calculates cumulative executed quantities, subtracts what was certified before, deducts retention and advance-payment recovery, then adds VAT.
• A chain of parties. The owner or client, the consultant who certifies quantities, the main contractor, subcontractors, suppliers and equipment lessors — each with its own documents and approval cycle.
• Scattered sites. One project in Riyadh, another in Jeddah, a third in Dammam, each with a store, labor and equipment, while management sits somewhere else.
• Constant variations. Added or omitted works change the contract value and the budget, and they must be documented before they are executed, not after.
• Long duration. A project may run for years, and retention may remain outstanding after handover until the defects liability period ends.

These are the modules a serious construction ERP is built on. You do not have to switch all of them on from day one, but the design must allow for them from the start.

The heart of a construction system is the cost structure. Each project is broken into sections and items — earthworks, concrete, masonry, electrical, HVAC, finishes — and each item has a cost code and a budget split into materials, labor, equipment and subcontract. Every cost in the company, whether a supplier invoice, an hour of labor or a liter of fuel, must carry a project code and a cost code.

The output is a report that compares four figures for each item: budget, committed (purchase orders and subcontracts not yet invoiced), actual cost, and estimate to complete. That report answers the owner's question "is this project profitable?" in the middle of the job, not after handover.

Before the project exists, the tender exists. The tendering module imports the client's bill of quantities and prices each item through a rate analysis covering materials, labor, equipment, overheads and margin. It keeps rates from previous tenders as a reference and tracks each bid through its stages: being priced, submitted, won or lost.

The real value shows up when you win. The priced BOQ turns into the project budget and its cost codes in one step, instead of being retyped into another file. Variation orders are later recorded against the same items, so the revised contract value and budget stay aligned.

Progress claims are how a contractor gets paid. The system pulls executed quantities for each item up to the claim date, multiplies them by contract rates, subtracts previously certified amounts, deducts the retention rate agreed in the contract, advance-payment recovery and any other deductions, and adds approved variations.

The system must support the approval cycle: submitted, revised by the consultant, certified, then partly or fully paid. It also keeps a retention ledger per project until release after handover or the end of the defects liability period, so money that belongs to the company is not forgotten. The certified claim is what generates the tax invoice, as the integrations section explains.

The mirror image of the progress claim is the subcontractor. Each subcontractor has a contract in the system with its items, rates and scope, and submits claims against it. The site engineer compares each claim with the quantities actually executed before approval. Retention, advances and back-charges — for materials the company supplied or rework done at the subcontractor's expense — are deducted automatically.

The result is that at any moment the company sees what it has committed to each subcontractor, what was executed, what was paid and what remains. Subcontract commitments also feed the "committed" column in the job-cost report.

Procurement starts on site. The site engineer raises a material request in the app, linked to the project and cost code, with the quantity and the date it is needed. The request is approved according to authority limits, then becomes a request for quotation to suppliers, a purchase order, a goods-received note signed by the site storekeeper, and finally a match against the supplier invoice.

This cycle stops duplicate purchases, ties every supplier invoice to a purchase order and a physical receipt, and makes purchase commitments appear in project cost before the invoice even arrives.

Each site has its own store in the system, alongside the main yard if you have one. Receipts bring materials in, issues to works take them out against a specific cost code, and transfers from one site to another move the cost together with the material. Periodic stock counts expose variances early.

This way, each project's cost reflects what it actually consumed. For a deeper look at inventory balances, transfers and stock counts in general, see our guide to warehouse management systems.

Equipment is an expensive asset in contracting: cranes, excavators, loaders, trucks, generators and mixers. The system records each unit, owned or rented, with its current location, the hours or days it worked on each project, the fuel it consumed, scheduled maintenance and breakdowns. It then charges the equipment to the project where it worked, at an internal rate for owned units or at the actual rental cost for hired ones.

It also tracks rental contracts and their end dates, plus inspection, insurance and registration dates, so that a rented machine does not sit idle on a site while rent keeps running. Because trucks and vehicles are a world of their own, our guide to fleet management systems covers tracking, fuel and maintenance in more depth.

Construction labor moves between sites. The site supervisor records daily attendance in the app, and each worker's hours are allocated to the project and cost code worked on, including overtime and absence. These hours do two jobs: they charge labor cost to projects accurately, and they feed the monthly payroll run.

For payroll itself, the mechanism is that the system combines basic salary, allowances, overtime, deductions and advances, then produces the payroll file in the format required by the official wage-protection and social-insurance channels, or integrates with them where an API is available. These requirements change, so confirm current requirements with the official authority and your HR advisor before signing off on any design.

A project produces thousands of documents: drawings in successive revisions, requests for information to the consultant, material submittals, meeting minutes and daily reports. Document control stores each document against its project, with revision number, status and approver, so nobody on site works from a superseded drawing.

The daily site report gathers the labor on site, equipment working, work completed, obstacles and photos. A photo taken in the app carries the date and location, which turns it into evidence when quantities are disputed.

All of the above fails if the site engineer has to drive back to the office to enter data. The mobile app lets him raise material requests, record attendance, write the daily report, take photos, enter executed quantities and confirm material receipts. It should work offline on sites with weak coverage and sync when the connection returns. We build this through our mobile app development service when the app is part of the system.

The financial layer ties everything together: journal entries posted automatically from claims, procurement documents, payroll and equipment charges; ledgers for clients, subcontractors and suppliers; and profitability reports per project and per city.

Contractors also need a cash-flow forecast: what will come in from upcoming claims and retention releases, and what will go out to subcontractors, suppliers, payroll and rentals, week by week. Alongside it sits a register of bank guarantees by type, with expiry dates and alerts well in advance.

The tax invoice should be generated from the certified progress claim itself, not retyped into another program. The mechanism works like this: the certified claim carries the net amount after deductions; the system creates a tax invoice with the required fields and both parties' details, applies VAT according to the company's configuration, sends it to ZATCA's e-invoicing platform through the approved integration, and stores the response and the identifiers linked to the invoice. If a claim is corrected after issue, the system raises a credit or debit note linked to the original invoice rather than editing it.

Some tax questions are specific to construction, such as how VAT applies to retention and advance payments, and when it becomes due. These are not decisions for a programmer. Your tax advisor should determine them based on ZATCA guidance, and the system must be configurable to apply whatever they decide. We explain the integration mechanism itself in detail in our guide to ZATCA e-invoicing and ERP integration. In every case, confirm current requirements with the official authority before go-live.

For general accounting you have two options: accounting inside the construction ERP itself, or keeping the accounting software your team already knows and linking the construction system to it through summarized journal postings. Each has its logic, and we discuss the decision in ready-made accounting software vs a custom system. Other useful integrations include bank statement imports, biometric attendance devices on site, and equipment tracking devices where they exist.

A construction ERP holds tender rates, project costs and staff salaries — commercially sensitive information. Protection has to be designed in from the start:

These are technical mechanisms. For personal-data protection requirements in the Kingdom, including where data may be stored, confirm current requirements with the official authority and a legal advisor before launch.

• Role- and project-based permissions: a site engineer sees only his own project and never tender rates or salaries; a project manager sees his budget; finance sees every project.
• Approval limits: purchase orders and subcontractor claims are approved at the right level according to their value and type.
• Audit log: who changed a quantity in a claim, approved a purchase order or edited an item budget, and when.
• Automatic backups with real restore tests.
• Known hosting location: where the data lives, who can access the servers, and how you get a full copy if you change vendor.

The honest answer: not every contractor needs a custom system. We cover the general logic in custom ERP vs off-the-shelf, and the Saudi market specifics in our guide to choosing an ERP system in Saudi Arabia.

Here the smart move is to start ready-made.

• A small contractor running one or two similar projects in a single city.
• Few subcontractors and no equipment fleet to speak of.
• A ready-made package that supports Saudi e-invoicing and allows cost tracking per project.

• Several projects across more than one city, with site stores and transfers between them.
• Progress-claim formats imposed by your clients or their consultants that the ready-made package cannot produce.
• Many subcontractors with contracts, retention and back-charges.
• An owned and rented equipment fleet that must be charged accurately to projects.
• A need for an offline site app, or management reports the ready-made package does not offer.

Many contractors keep a ready-made accounting package that already handles e-invoicing and build a custom layer around it for projects, claims and sites, posting journal entries into it. This works well provided the ready-made package offers an API; otherwise manual re-entry creeps back in.

The cost of a construction ERP is driven by a set of factors, not a fixed figure. The main ones are:

We will not put a number here, because any figure given without understanding your projects would mislead you. Tell us about your company in a free consultation and we will define the right scope with you.

• Scope of phase one: job costing and progress claims alone are one thing; the full suite with equipment, labor and document control is another.
• Complexity of progress claims: one format, or different formats per client and consultant, with variations and multi-level retention.
• Number of projects, sites and users.
• Integrations with e-invoicing, accounting, banks and payroll channels.
• The site mobile app, and whether it must work offline.
• Data migration from spreadsheets or a legacy system.
• Language (Arabic and English) and the number of custom reports.
• Hosting and support after launch.

Map the current workflow: from tender to final claim, and from material request to supplier invoice. Agree on one unified cost-code structure for all projects, choose a single pilot project, and gather the active BOQs, contracts and subcontractor claims.

Run job costing, progress claims and material requests on the pilot project, with the site app for one engineer. Issue the first claim from the system in parallel with the old method and compare the results, and test the tax invoice in a test environment before going live.

Roll the system out to the remaining projects, and add subcontractors, equipment, labor and the payroll interface. Start reviewing budget-versus-actual and cash flow weekly with management, and collect feedback from site teams for an improvement round.

The more of this you prepare, the sharper the meeting and the more realistic the proposal. For more on writing requirements, see how to write a software project brief.

• A list of active projects, their cities, approximate size and number of sites.
• A sample progress claim to a client and one from a subcontractor, with sensitive data hidden.
• The cost-code structure you use today, or a sample BOQ.
• How retention and advance payments are calculated in your contracts.
• The number of subcontractors and how their claims are approved.
• Your list of owned and rented equipment and how it is charged today.
• Labor headcount, how attendance is recorded and how payroll is prepared.
• Your current accounting software and how you issue e-invoices.
• The reports the owner wants to see every week.
• The person who will own the project on your side.

We start with a discovery session by video with the owner, the finance manager and at least one project manager, and map the project lifecycle from tender to retention release. Then we split the work into short phases: the job-costing and progress-claim core first, then procurement and sites, then equipment and labor. If ready-made software covers part of your needs, we say so and build only around it.

Our team is in Cairo, and we work with Saudi clients remotely through regular meetings, with on-site visits when needed for discovery or training. We build Arabic and English interfaces and hand over the code and documentation. Learn more about our work in Saudi Arabia and our ERP and business systems service, and if you are still comparing vendors, read our guide to choosing a software company in Saudi Arabia.

If your projects still run on spreadsheets and WhatsApp groups, book a free consultation. We will listen, and tell you honestly whether ready-made software is enough or a custom system will pay you back more.