Construction Expense Management: How GCC Contractors Control Site Allowances, Per Diems, and Petty Cash

The expenses nobody tracks until the audit

A site manager submits a receipt for SAR 840 in diesel fuel. He fills in a handwritten petty cash voucher. Someone files it in a folder. At month-end, the finance team reconciles an SAR 18,000 petty cash float and finds SAR 2,400 they can't account for — no receipts, no work orders, no project codes.

This happens on construction sites across the GCC every month. The individual amounts look small. Across a SAR 300M project with 200 site staff, small adds up fast.

Expenses in construction aren't just travel claims and team lunches. They're a significant operational cost category: housing supplements, site transportation, per diems for expat supervisors, petty cash for daily consumables, subsistence allowances for remote sites, and mileage for engineers moving between office and project locations. When none of this is tracked against a project or WBS code, the cost lands in G&A overhead — invisible to job costing and useless for future project estimation.

Why expense management breaks in construction

Most GCC construction companies manage expenses through a combination of WhatsApp approvals, handwritten vouchers, and month-end reconciliation. It works — until it doesn't.

The WBS blindspot

Travel, site allowances, and petty cash typically hit a single "general expenses" GL code. The cost never reaches the project cost report. Project managers see labour and materials. They don't see the SAR 120K in site allowances the team claimed over 6 weeks on that MEP package. Multiply that across 8 active packages and the number is significant — and invisible.

The petty cash float cycle

A site engineer holds SAR 5,000–15,000 in a cash box for daily site expenses. Receipts accumulate in pockets and drawers. Every 2–3 weeks, the engineer submits a reconciliation to get a top-up. Discrepancies are common. The gap between actual disbursements and documented spend on a medium-sized site runs 2–5% — SAR 100–250K annually on a SAR 5M petty cash base.

Approval via WhatsApp

An engineer sends a photo of a receipt. The PM replies "approved." There's no audit trail, no GL code assigned, no policy check on whether the expense type is allowed or the amount is within limits. When the auditor asks for expense approvals from two years ago, nobody has them.

ZATCA Phase 2 exposure

Saudi Arabia's e-invoicing mandate requires ZATCA-compliant tax invoices from VAT-registered vendors. Many petty cash purchases — particularly from small suppliers at building material souks — come with informal receipts that don't meet the requirement. This creates input VAT risk and audit exposure that compounds across a large project portfolio. A single ZATCA audit finding across 15 projects can trigger penalties and disallowed VAT reclaims in material amounts.

What site expense management should look like

The principle is straightforward: every riyal spent on a project should hit a cost code, carry an approval timestamp, and be traceable to a receipt or documentation record. That's it. The execution is where most contractors fall short.

Digital expense submission

Site staff submit expenses via mobile, photographing receipts at the point of purchase. The submission form requires a mandatory expense category, a project and WBS code, vendor name and invoice reference for ZATCA tracking, and a receipt image attached at submission — not chased later. Offline capture is essential for remote NEOM and eastern province sites where connectivity is intermittent. Data syncs automatically when the device reconnects.

Policy-embedded approval routing

Approval limits are set by expense amount, not by the informal judgment of whoever is available on WhatsApp. A typical GCC construction contractor runs four tiers:

• Up to SAR 500: Direct supervisor
• SAR 500 – 2,500: Project manager
• SAR 2,500 – 10,000: Commercial manager
• Above SAR 10,000: COO or CFO

Policy rules flag out-of-category expenses — entertainment on a restricted project, accommodation claims above the approved per diem rate — before they reach the approver. The approver sees a clean request, not a policy question dressed as an approval.

Petty cash float management

Each site float is registered with a defined limit, a named custodian, and a minimum replenishment threshold. Disbursements are logged digitally at the site hut or project office. Weekly reconciliation compares the digital ledger against physical cash. Discrepancies above SAR 200 trigger an automatic review flag before they compound into a month-end gap that nobody can explain.

The reimbursement cycle shifts from "when the engineer asks" to "when the balance hits 30% of the float limit" — automatic, rule-driven, documented.

GL posting with WBS attribution

Approved expenses auto-post to the general ledger with the correct GL account (site expense, travel, per diem), cost centre and project, and WBS code for job costing. The project cost report sees the expense. The CFO sees it broken down by project. The estimating team can extract actual site expense rates per project type at closeout and build them into future tenders — replacing the rough percentage contingency that most contractors pad in instead.

The GCC context that makes this harder

Construction projects in Saudi Arabia and the wider GCC carry a higher expense intensity than many other markets. Remote sites like NEOM, eastern province oil and gas expansions, and Riyadh giga-project clusters involve significant logistical costs that go well beyond a standard per diem policy.

Contractors running Musaned-registered workforces must manage nationality-specific allowance structures — Filipino POEA provisions, Indian and Pakistani annual airfare, Saudi GOSI-registered overtime — each with its own rate, eligibility, and documentation requirement. When those allowances are processed through a manual claims system without WBS attribution, the project cost report has a structural gap from day one.

Summer heat restrictions (June 15 – September 15) add a seasonal expense dimension: extended rest periods, cooling provisions, additional transportation for workers under prohibition hours. These aren't discretionary — they're compliance costs. Tracking them by project and WBS enables proper recovery through the project budget and identifies sites where the compliance cost is higher than the norm.

The numbers that make the case

For a SAR 300M construction contract running over 30 months, site expenses for the project team typically run SAR 800K–1.2M per month at peak: housing supplements, transportation allowances, site per diems, consumables petty cash, and engineer travel. That's SAR 24–36M in total expenditure that should appear in the project cost report but often doesn't.

A 2% petty cash discrepancy on SAR 8M in petty cash disbursements over the project life equals SAR 160K in undocumented spend — which will appear in the project closeout audit as unreconciled cash. A ZATCA audit finding on VAT-ineligible input credits across 15 projects represents material financial and penalty risk.

These aren't hypothetical exposures. They appear in routine finance audits on GCC construction projects. The fix — a structured expense management workflow with mandatory WBS codes, digital receipt capture, and rules-based approvals — isn't complex. It's just disciplined.

Five starting steps

Most GCC construction companies can close this gap in 60–90 days without a full system overhaul.

• Run an expense category audit. Pull the last 3 months of expense claims. How many have a WBS code? How many have valid receipts? What percentage went through documented approvals? The gap between what you have and what an auditor would expect is your current exposure.
• Define your per diem policy in writing. If site managers don't have a policy document covering allowance rates, eligible categories, and receipt requirements — they're improvising. Document it, distribute it, enforce it.
• Register every petty cash float. List every active float: custodian, limit, current balance, last reconciliation date. If you can't answer those questions for every site in under 10 minutes, the float management process needs a reset.
• Require WBS codes at submission, not at month-end. The WBS code must be captured when the expense is submitted — not added by accounts payable staff during month-end processing. Retro-coding is inaccurate and useless for real-time job costing.
• Check your ZATCA exposure. For Saudi projects, identify what percentage of petty cash purchases carry ZATCA-compliant tax invoices. If you're reclaiming input VAT on purchases that don't qualify, the exposure grows every reporting period.

Site expenses are not a minor back-office issue. They're a job costing blind spot, an audit risk, and an estimation gap — all at once. Closing those gaps starts with treating every site riyal the same way you treat every purchase order.