A custom construction ERP in Khobar,running the work rather than reporting on it

In this one: projects and tasks, planning and resources, project costs, customers, assets, an approval workflow, HR and recruitment, and an accounting side carrying ZATCA e-invoice clearance. That list is the delivered system rather than a menu — it is what the screens show, which is the only list we are willing to publish about someone else's software.

At minimum, a project register that the costs hang off, an approval chain that produces a record, and a compliant invoice at the end of it. Everything else is a question of how the company runs. This system adds planning and resources, customers, assets, and HR with recruitment, because those were the parts of the operation that were being held together manually.

The invoice is raised where the work is recorded, then submitted for clearance from the accounting module itself. This system reports every invoice by state — submitted, failed, pending or draft — with a compliance score, a trend over the period and diagnostics on a failure. The alternative, a separate compliance tool fed by hand, is a second data-entry job with a compliance badge on it.

Against the project, not against the month. Project costs are their own module here, selected per project, so cost sits with the job it belongs to and the portfolio view adds up from real records. Strengthening cost control was the stated purpose of the delivery, and this is the mechanism that does it.

This one treats approval as a module rather than as an email convention: requests are raised and queued, there is a pending view, and there are approval analytics and approval reports over the history. The decision also drives what happens next — an approved request generates the invoice request instead of relying on someone to remember.

It can, and there is a good reason to want it in the same system: the people are the cost on the projects the same system is tracking. Human resources and recruitment are both modules here, with document expiry alerts running across the records — which for a Saudi contractor is the difference between a renewal and a stoppage.

As a register in the same system, with a live count on the operational dashboard alongside projects, tasks and people. Keeping assets in the system that holds the projects is what makes it possible to ask what is deployed where without someone reconciling two lists first.

An off-the-shelf system asks the business to adopt its assumptions about approvals, project structure and cost breakdown. A custom one starts from how the company already works. Neither is automatically right — but for a contractor whose approval chain effectively is the business, rewriting that chain to suit a product is an expensive way to save on licensing.

It depends on how much of the operation goes in at once, and we are not going to put a number on this one that we cannot source. What is fair to say is that a system of this scope is not a one-quarter project, and that it does not finish: this one is in production in Khobar and continues to be extended as the work changes.

Because accounting software answers what was spent, and a contractor needs to know what was spent on which job, approved by whom, against which budget, and whether the resulting invoice cleared. Once those questions are being answered by joining exports together by hand, the accounting package has stopped being the system of record whatever the finance team calls it.