— Industries / Construction
ERPNext for UAE construction — projects, BOQ, retention, WPS, profitability.
UAE construction runs on long projects, complex sub-contractor chains, retention regimes, and WPS payroll. Here's how we configure ERPNext to handle all of it without spreadsheets.
TL;DR
Five things to know.
- Vanilla ERPNext stops at project costing. POC revenue recognition, formal BOQ, retention regimes, and WPS payroll are custom layers we add as standard for construction.
- Project profitability is the single most-used report. Budget vs commitment vs actual vs forecast — at cost-head level — drives every weekly project review.
- Sub-contractor retention is unforgiving. 5–10% held per sub, released across substantial completion and defect-liability expiry. Without proper tracking, retention liability balances drift.
- WPS file generation works — once. We build the SIF export validated against your specific WPS bank. Tested monthly thereafter.
- Plant and equipment costing matters. Charging plant hire to projects at internal rates is the difference between knowing a project lost money and finding out at year-end.
Context
The construction business in the UAE & GCC.
Construction is one of the UAE's largest non-oil sectors and a core driver of GDP, and it has been since the 1970s. Mega-projects — Expo legacy works, Dubai Urban Master Plan 2040, Abu Dhabi's Saadiyat and Yas developments, the Etihad Rail rollout, and an active pipeline of residential, commercial, hospitality and infrastructure projects across all seven emirates — keep contractors busy in every tier.
The contracting hierarchy is layered. Tier-1 main contractors hold direct contracts with developers (Emaar, Aldar, DP, Wasl, government clients). Tier-2 trade specialists deliver MEP, façade, joinery, civil works, fit-out under main-contractor sub-contracts. Tier-3 specialists handle steel, glazing, waterproofing, painting, and a long tail of trade packages. Most ERPNext construction clients sit in tiers 2–3, with annual revenue from AED 20m to AED 500m and 50–500 staff.
Common business shapes: single-entity contractors with a mainland licence (most tier-2 and tier-3 firms); multi-entity groups with separate trading, contracting and equipment-rental arms; JV vehicles set up project-by-project for large jobs; family-office construction groups spanning 3–6 entities across UAE and Saudi; infrastructure specialists with fewer, larger, longer-running projects (often 18–36 months); fit-out and joinery firms with high project velocity (50–200 projects per year, each 3–8 weeks).
Regulatory load is moderate. WPS (Wage Protection System), run by MoHRE, is mandatory for mainland-licensed entities and most free-zone employers — monthly SIF file generation is a hard compliance requirement. FTA VAT applies normally to construction (standard 5% on most works, with specific zero-rating for first sale of new residential within three years of completion). Health and safety / DM and DCD requirements live outside the ERP but interact with timesheet data and incident logging, which we often build into ERPNext as custom DocTypes.
Capabilities
What ERPNext gives construction companies.
Projects with budgets, commitments, actuals and forecast
Each Project carries a budget by cost head (labour, material, subcontract, plant, overhead). POs against the project create commitments. Invoices and timesheets create actuals. A custom forecast-to-complete field plus the budget gives you forecast final cost. Variance reporting at project, cost-head and line level drives weekly project reviews.
Bill of Quantities (BOQ) and contract variations
BOQ DocType layered on Project: line description, unit, quantity, rate, target margin, certified-to-date, billed-to-date. Variation Orders update contract value with client approval. Progress invoicing pulls from BOQ with percentage-complete per line. Certified vs uncertified variations tracked separately.
Work-in-progress and POC revenue recognition
Costs accrue against project as WIP. Periodic POC calc (cost-incurred/total-budget) recognises revenue and moves WIP into Cost of Sales via scheduled Journal Entry. Final account closes at handover with retention transferred to retention-receivable. We build the POC engine as a standard custom — vanilla ERPNext stops at cost tracking.
Sub-contractor management with retention
Sub-contractors as Suppliers with default-retention-percentage field. Each subcontract invoice auto-splits payable-now and retention-held. Retention release Journal Entries fire on substantial completion (e.g. 50%) and defect-liability expiry (e.g. 50%). Retention ageing report flags held balances by sub and projected release date.
WPS payroll with SIF file export
Payroll Entry generates the WPS Salary Information File in MoHRE-compliant format — header, employee body records, trailer with checksums. Validated against major UAE payroll banks. Finance uploads to the WPS-enrolled bank monthly. Per-employee earning, deduction and net-pay records reconcile back to ERPNext payslips.
Timesheets, labour costing and plant utilisation
Site-based timesheets capture employee hours by project and activity, post to project cost at standard or actual labour rate. Plant assets allocated to projects with daily/hourly internal hire rate; daily plant-hire Journal Entries charge projects automatically. Utilisation reports per asset and per project surface idle plant.
Procurement aligned to project budgets
Material Requests against a project visible to procurement. POs reference project, quantity, rate; commitment posts on PO submission. Budget warnings or hard-blocks on POs that breach project budget. Goods receipts post project actuals; supplier invoices reconcile against GRs. Three-way match reduces invoice fraud risk.
Multi-company for groups with separate trading and contracting arms
Many UAE contractors run a contracting LLC plus a sister trading LLC plus an equipment-rental arm. Multi-company in one ERPNext database keeps each entity separate for legal and VAT but allows inter-company transactions (trading sells materials to contracting, equipment rents to contracting) and consolidated group reporting.
Real scenarios
Common construction scenarios we've delivered.
A Dubai-based MEP sub-contractor on tier-2 jobs across 30+ active projects. Tier-1 main contractors as customers; specialised material suppliers and labour-supply sub-contractors as suppliers. ERPNext configured with project-level WIP, monthly POC revenue recognition, sub-contractor retention at 10%, and progress-claim invoicing per certified BOQ line. Project profitability dashboard refreshed weekly; loss-making projects flagged early enough to negotiate variations or recoveries before final account.
A multi-entity contracting group with a contracting LLC, an aluminium fabrication arm and an equipment-rental subsidiary. Three Companies in one ERPNext instance, all under common ownership. Aluminium arm fabricates curtain-walling and ships to contracting projects (inter-company sales with VAT correctly handled). Equipment-rental subsidiary hires cranes and scaffolding to the contracting arm at intercompany rates; daily hire postings charge projects automatically. Consolidated group P&L plus per-entity statutory P&Ls.
A fit-out specialist running 100+ short projects per year across hospitality and retail. Project velocity high enough that lightweight templates matter. We built a Project Template per project type (restaurant fit-out, retail fit-out, office fit-out) that pre-populates BOQ structure, default cost-head budget split, and standard sub-contractor list. Project setup time dropped from a half-day per project to 30 minutes. Profitability tracked per project and per project manager.
An infrastructure contractor with two long-running multi-year projects (rail and roadworks). Long-duration POC revenue recognition critical here — without it, year-1 looks loss-making and year-3 looks artificially profitable. Custom POC engine recognises revenue smoothly across the project life. Retention regimes layered: 5% retention on each interim payment, with release at substantial completion plus defect-liability expiry per the contract. Plant fleet allocated to projects with full utilisation visibility.
Day one
What we configure on day one.
Every Craft construction engagement starts with a fixed checklist.
- UAE-localised Chart of Accounts with construction-specific cost-head structure
- Project DocType extended with budget, BOQ, certified-to-date, retention fields
- BOQ DocType with line description, unit, qty, rate, target margin
- Variation Order workflow with client-approval gating
- POC revenue recognition engine — scheduled Journal Entry per project
- Sub-contractor master with default retention percentage
- Subcontract invoice split: payable-now vs retention-held automatic
- Retention release workflow tied to project milestones
- WPS SIF export validated against your specific payroll bank
- Plant-and-equipment Asset masters with internal hire rates
- Daily plant-hire Journal Entry automation per active allocation
- Standard sales and purchase Tax Templates with construction-specific zero-rating cases
- Project Templates per common project type for fast setup
- Reports pinned: Project Profitability, Retention Ageing, WIP, Cost-Head Variance, Plant Utilisation
- User roles for QS, project manager, procurement, finance, HR, payroll, management
Pricing
Pricing approach.
Construction implementations run on a fixed-fee, fixed-scope model. Once discovery is complete — including project-portfolio review, sub-contractor regime, retention policy, and WPS bank validation — we issue a single SOW with a not-to-exceed price.
Pricing depends on entity count, project volume, BOQ complexity, integration count (banks, plant management), POC engine scope, and migration effort.
See our ERPNext pricing approach for engagement structure.
Add-ons
Add-ons we often implement.
Most construction clients add one or more of these in phase 2:
- HSE incident-logging DocType — near-misses, incidents, root-cause and corrective-action workflow.
- Cost-to-complete forecasting — formal CTC engine with project-manager input, surfacing cost overruns earlier.
- Bank file integrations — WPS, payment file export and statement import for major UAE payroll banks.
- Document-control DocType — drawings, RFIs, submittals, transmittals — useful for tier-2 contractors not running a separate document-control system.
- VAT optimisation — for groups spanning trading, contracting and rental with mixed VAT treatments.
- Managed AMC — version upgrades, monitoring, ticket SLAs, quarterly reviews.
Questions
FAQ.
Does ERPNext do work-in-progress (WIP) accounting for long-running construction projects?
Yes — through the Project DocType and percentage-of-completion (POC) revenue recognition. As costs accrue against a project, you book WIP. Periodic POC calculations (cost-incurred / total-budgeted-cost) trigger revenue recognition Journal Entries that move WIP into Cost of Sales and recognise the matching revenue. Final account closes at handover. We configure this as a standard recipe for every construction client; vanilla ERPNext stops at project costing — POC revenue recognition is a custom DocType layer we add.
How do we track sub-contractor liabilities and retention?
Sub-contractors are Suppliers in ERPNext, with a custom field for default retention percentage (typically 5–10%). Each sub-contractor invoice splits into payable now and retention held; retention posts to a separate balance-sheet account. On retention release (commonly 50% at substantial completion, 50% after defect-liability period), a Journal Entry releases the held amount to AP for payment. Retention ageing reports flag held balances and projected release dates.
Can ERPNext generate WPS (Wage Protection System) files for UAE payroll?
Yes. We build a WPS export from ERPNext's Payroll Entry that produces the SIF (Salary Information File) format required by the MoHRE WPS programme — bank-readable, employee-by-employee, with the right header, body and trailer records. Finance uploads the SIF to the company's WPS-enrolled bank for processing. We have validated the format with the major UAE payroll banks. Note: WPS applies primarily to mainland and certain free-zone entities; some free-zone authorities run their own equivalents.
How does project profitability reporting work?
Each Project carries a budget (broken down by cost head — labour, materials, subcontract, plant hire, overhead), commitments (POs raised against the project), actuals (invoices and timesheets posted), and forecast cost-to-complete. The Project Profitability report compares contract revenue (signed contract value plus approved variations) against committed and actual costs, showing margin earned, margin remaining, and forecast final-account margin. This is the single most-used report on every construction implementation we deliver.
Can it handle Bill of Quantities (BOQ) and contract variations?
BOQ is modelled via the Project Template feature plus a custom BOQ DocType we layer in. Each line carries description, unit, quantity, rate, and target margin. Variations (additions or omissions) are formal Variation Order documents that update the contract value with client approval. Progress invoicing pulls from BOQ lines with a percentage-complete per item; certified vs uncertified variations are tracked separately. This is core to our construction template.
Does it integrate with plant-and-equipment hire?
Yes. Plant items (cranes, excavators, scaffolding, formwork) modelled as Assets in ERPNext, allocated to projects with hire-rate per day or hour, and posting daily hire charges to the project's cost. For external plant hire from third parties, the supplier invoice posts directly to the project. Plant utilisation reports show usage rate per asset across active projects — useful for fleet right-sizing.
How do progress claims and retention releases work in ERPNext?
Progress claims are interim Sales Invoices against a Project, typically generated monthly, citing percentage-complete per BOQ line. Retention is automatically deducted at the certified retention rate (usually 5%) and posted to a retention-receivable account. On retention release events (substantial completion, defect-liability expiry), Journal Entries move retention to standard AR for payment. Aged retention reports flag releases due, helping the QS team chase certificates.
How long does an ERPNext implementation take for a construction company?
A small contractor with 5–15 active projects typically runs 12–16 weeks from signed SOW to go-live. Mid-size contractors with 30+ projects, multi-entity groups, or formal POC revenue recognition needs run 18–24 weeks. The longest pole is usually the BOQ template setup and migrating active projects — finishing them in the legacy system is often easier than migrating mid-flight.
— Ready when you are
Talk to a real ERP consultant.
A 30-minute call is the fastest way to know if we're a fit. No slides.