Construction ERP differs from general ERP in four places: job costing against a cost code structure, retention held on both what you bill and what you pay, subcontract valuations that certify work done, and progress billing against a schedule of values. A system that handles these correctly gives a live margin per job; one that does not leaves the numbers in spreadsheets until the job is over.
Contractors lose money quietly. A cost is coded to the wrong job, a variation is agreed on site but never priced, a subcontractor is paid for more than was certified, or retention is released without checking defects. This guide explains how each area should work inside an ERP, with small worked examples, and ends with a guide to choosing between a packaged construction system and a custom build. For the overview of construction ERP modules and a selection checklist, see our guide to ERP for construction companies. To read about the platform we build, see our custom ERP development page. Terms such as retention, retainage, valuation and application for payment vary by country and contract form, so the examples use plain wording.
Job costing: the structure comes first
Job costing records every cost against a job and a cost code, so you can compare budget, committed cost and actual cost at any time. Build the structure before you build the screens.
| Level | Purpose | Example |
|---|
| Job or project | The contract you are building | Office block, phase 2 |
| Phase or section | A stage or area | Substructure, frame, fit-out |
| Cost code | The type of work or cost | Concrete, rebar, formwork, labour, plant |
| Cost type | The nature of the cost | Labour, material, subcontract, equipment, other |
Keep the cost code list stable across jobs so reports can compare jobs, and keep it as short as you can manage. Forty well-used codes beat four hundred mostly empty ones.
The three numbers that matter on each line are:
- Budget: the estimate converted to cost codes at award, with a version history when it is revised.
- Committed cost: purchase orders and subcontracts signed but not yet fully invoiced. Without commitments, the cost report ignores the money you already owe.
- Actual cost: invoices, timesheets, plant charges and stock issues posted.
The forecast final cost is actual plus the estimate to complete, entered or confirmed by the project manager each month. The system should show forecast margin and flag a line that is forecast to overrun.
A worked example (illustrative numbers)
All figures below are illustrative. A contractor holds a contract worth 1,000,000 for a building package. The cost budget at award is 880,000, so the planned margin is 120,000, or 12%.
| Cost code | Budget | Committed | Actual to date | Estimate to complete | Forecast final | Variance |
|---|
| Concrete and rebar | 250,000 | 240,000 | 150,000 | 100,000 | 250,000 | 0 |
| Formwork | 80,000 | 70,000 | 60,000 | 28,000 | 88,000 | -8,000 |
| Subcontract: mechanical | 300,000 | 300,000 | 90,000 | 210,000 | 300,000 | 0 |
| Labour (own crew) | 150,000 | n/a | 100,000 | 65,000 | 165,000 | -15,000 |
| Plant | 50,000 | 40,000 | 30,000 | 20,000 | 50,000 | 0 |
| Other | 50,000 | 30,000 | 20,000 | 30,000 | 50,000 | 0 |
| Total | 880,000 | | 450,000 | | 903,000 | -23,000 |
Forecast final cost is 903,000, so the forecast margin is 97,000, or 9.7%, down from 12%. A spreadsheet can show this too. The ERP advantage is that it shows it at the end of each week, with drill-down from the 15,000 labour overrun to the timesheets and the site that caused it.
Progress billing and the schedule of values
Contractors rarely invoice a lump sum. They bill periodically for the percentage of work completed, against a breakdown of the contract price. In the US this is often a schedule of values; in other markets it may be a bill of quantities or a payment schedule. The mechanics are similar.
- The contract price is split into billing lines, each with a value.
- Each period, the project team records the percentage or quantity complete per line.
- The system calculates the amount due: work completed to date, less amounts billed before, less retention held.
- A payment application or invoice is produced in the format the client requires, often with supporting sheets.
- Variations (change orders) are added as new lines or revised values once agreed, and clearly marked if they are only proposed.
Common failure points are billing for stored materials with no rule for how they are valued, front-loading the schedule of values, and variations that were instructed on site but not recorded as approved. A good system keeps three variation statuses visible: proposed, instructed and approved, and bills only what the contract allows.
Retention: held from you and held by you
Retention (called retainage in the US) is a percentage of each payment held back until a later milestone, such as practical completion or the end of the defects period. Typical percentages are commonly between 5% and 10%, but it is set by each contract, and rules about retention differ by country and sector, so follow your contracts and local law.
The ERP must handle retention twice.
- Retention held on your sales: the client withholds part of your billing. You show it as a receivable due later.
- Retention held on your subcontractors: you withhold part of what you owe subcontractors. You show it as a payable due later.
A simple example with illustrative numbers: your work completed to date is 400,000, previously billed 250,000, retention 5%. The gross for this period is 150,000. Retention on this period is 7,500, so the net due is 142,500. The retention receivable accumulates in a separate balance, with a release date or condition recorded per contract. When half of the retention is released at practical completion, the system should raise the release as a billable event and track the balance remaining.
The mistake to avoid is treating retention as a manual journal at month end. Retention should be calculated on every application and every subcontractor payment, carry a release rule, and appear on the aged receivables and payables reports as its own category.
Subcontract management and valuations
Subcontractors often make up a majority of a contractor's cost. The ERP should handle the subcontract as a controlled document, not a purchase order with a long description.
- Subcontract record: scope, value, retention rate, payment terms, insurance and licence expiry dates, and any back-to-back terms from the main contract.
- Valuation: each period the site team records work done by line, the system calculates gross value, less previous payments, less retention, less any deductions or back-charges, and produces a payment certificate for approval.
- Variations: subcontract variations are linked to client variations where they are passed through, so you can see whether a pass-through is covered.
- Pay-when-certified controls: the system blocks payments above the certified amount without an approval.
- Compliance dates: warnings when insurance or certificates expire, as your own rules require.
Keep valuation and payment as separate steps so that you can see what was certified, approved and paid. For the procurement side of this flow in general ERP terms, see our guide to the ERP procurement module.
Equipment, plant and site data
Plant hire and own equipment are a major cost on some jobs. The system should charge plant to jobs by an internal rate or external hire cost, and record usage from timesheets, meters or daily logs. Site data capture should be simple enough to be done on a phone: daily labour hours by task, materials received, plant used, and issues. If it is not captured on site, it is reconstructed at the end of the month, and reconstructed data is where coding errors come from. Our article on offline-first field apps explains how a site app can work in places with poor signal.
Custom or packaged construction software?
Packaged construction ERP and job-costing products exist at every size, and many contractors should buy one. The comparison below is for the decision, not a verdict.
| Question | Leans packaged | Leans custom |
|---|
| Is your contract and billing format standard? | Yes: standard forms, one country | No: several forms, clients with own formats, multi-country |
| Are subcontract valuation rules standard? | Yes | No: pass-through terms, complex deductions, specialised trades |
| Is site capture central to your edge? | Standard timesheets and daily logs | Specialised capture: drawings, inspections, geolocated progress, offline |
| Do you integrate with estimating, scheduling, BIM or client portals? | A few standard connectors | Many one-off integrations |
| What do licences cost at your headcount? | Manageable | Per-user fees grow with a large field workforce |
| How fast do your processes change? | Slowly | Quickly, with new contract types or services |
| Who owns the roadmap? | The vendor | You |
If your answers are mostly in the first column, buy. If they split, a hybrid is common: a packaged core for finance, and custom site and valuation tools around it. Our page on ERP versus custom development gives the full comparison, and our guide to ERP total cost of ownership shows how to compare costs over several years fairly.
What to include in a construction ERP pilot
Ask any vendor to run the same slice on your own data. A strong test is one live job through four steps: budget loaded by cost code, a supplier invoice and a timesheet posted, a subcontract valuation with retention certified and paid, and a progress application to the client with retention held. Check that the forecast margin report agrees with a manual calculation. Before you commit to the full project, we build 2 to 3 of your key modules as working software, free of charge, ready in about 2 days. Your team tests the pilot, and the full build starts only after you approve it.
How Timeline Digital approaches construction systems
Timeline Digital is a custom software development company founded in 2013 and headquartered in Islamabad, Pakistan. We build custom ERP modules for job costing, subcontract valuation, retention and progress billing, and will say so plainly when a packaged system fits you better. The full project starts after you approve the pilot, and the scope, milestones and terms are agreed after it. Timeline Digital does not publish prices for custom software, because every project is custom. We design records and approvals to support your contracts, and we confirm local payment rules per project with your own advisers. Support hours are Monday to Friday, 9:00 to 18:00 Pakistan time (PKT, UTC+5).
Summary checklist
- Define a short, stable cost code structure before configuration.
- Track budget, committed and actual cost, and forecast to complete every month.
- Make progress billing rule-based, with variation statuses visible.
- Calculate retention on every application and every subcontract payment, with release rules.
- Separate subcontract valuation, certification and payment.
- Capture site data on phones, with offline support if sites have poor signal.
- Test any option with one live job through budget, cost, valuation, retention and billing.