ERP for the Construction Industry: The Problems It Actually Solves
Generic business software wasn't built for CIS, retentions, or applications for payment. This is a plain-English tour of the specific problems an ERP for the construction industry has to solve, and what a right-sized system needs to do about each one.
An ERP for the construction industry earns its keep by solving the money-and-paperwork problems that off-the-shelf accounting and generic project tools simply ignore: CIS deductions, retentions held for years, applications for payment, work-in-progress, plant tracking, and the risk of a client going under and dragging your cash down with them. This article walks each pain in turn, then says plainly what a system has to do about it.
Quick summary: Construction runs on rules generic software never accounts for — CIS deductions passed to HMRC, staged payments and retentions defined by the Housing Grants, Construction and Regeneration Act 1996, and long payment chains where one insolvency cascades downward. Construction is consistently the single highest sector for company insolvencies in the UK, around 17% of all cases where industry is recorded, which is exactly why cash visibility matters more here than almost anywhere else.
Contents
- Why generic business software breaks in construction
- CIS deductions and subcontractor verification
- Retentions held across long projects
- Applications for payment and valuations
- WIP and over/under-billing
- Plant and equipment tracking
- Multi-project cash flow
- Document and drawing control
- Payment-chain risk when insolvency cascades
- A worked example
- FAQ
- How OpsMavix can help
Why generic business software breaks in construction
Most accounting packages and off-the-shelf project tools are built for a simple world: you sell a thing, you invoice for it, you get paid. Construction is not that world. A single job can run 18 months, be billed in stages against a valuation, have 5% held back as retention for a year after practical completion, involve a dozen subcontractors each needing a tax deduction and a verification check, and be exposed to a main contractor who could fold before your final account clears.
None of that fits a standard sales-invoice-and-receipt model. So the gaps get filled by spreadsheets, memory, and a quantity surveyor who is the only person who knows where the money is — too complex for spreadsheets, not ready for a heavyweight ERP.
Here is the short version of what breaks:
| Construction pain | What generic software does | What a construction-fit system needs to do |
|---|---|---|
| CIS deductions | Treats a subcontractor bill as a normal purchase invoice | Verify status, split labour vs materials, deduct 20/30/0%, file the monthly return |
| Retentions | No concept of holding back a percentage | Track retention held per project, flag release dates |
| Applications for payment | Only knows fixed invoices | Value work-to-date, net off previous payments and retention |
| WIP / over-billing | Revenue = invoices raised | Compare cost-to-date and billed-to-date against the contract |
| Plant & equipment | Assets sit in a fixed-asset register | Track location, hire vs owned, cost recharged to jobs |
| Multi-project cash | One company cash figure | Cash position per project and forecast across the portfolio |
| Documents & drawings | Files in folders, no version control | Current-revision control tied to the job and the trade |
| Payment-chain risk | Invisible until a bad debt lands | Exposure per client, retention at risk, early warning |
Every row below gets its own section. The theme throughout: the fix is not “buy a bigger ERP”, it is a right-sized system that models how construction money and paperwork actually move.
CIS deductions and subcontractor verification
The Construction Industry Scheme is the first thing generic software gets wrong. Under CIS, when you pay a subcontractor you are usually a “contractor” in HMRC’s eyes, which means you must deduct money from their payment and pass it to HMRC as an advance against their tax and National Insurance (gov.uk). The deduction is 20% for a registered subcontractor, 30% for one who is not registered or cannot be verified, and 0% for those with gross payment status.
That single rule breaks a normal purchase-invoice workflow in three ways. First, you cannot deduct from the whole bill — materials, plant hire and certain other costs are excluded, so labour and materials have to be split on every invoice. Second, you have to verify each subcontractor with HMRC to know which rate applies, and re-verify when things change. Third, you owe HMRC a monthly CIS return summarising every deduction, with penalties for late or wrong filing.
What a system needs to do: hold each subcontractor’s CIS status and verification, split labour from materials automatically on entry, apply the right deduction rate, produce the payment-and-deduction statement the subcontractor is owed, and generate the monthly return data without anyone rebuilding it in a spreadsheet. Get this right once and it stops being a monthly fire drill.
Retentions held across long projects
Retention is money you have earned but are not allowed to collect yet. On most construction contracts the payer holds back a percentage of each payment — commonly around 5%, half released at practical completion and half at the end of the defects period, which can be a year or more later. It exists so the client has leverage to get snags fixed. The right to stage payments, and the mechanics around them, sit in the Construction Act 1996.
The problem is scale and memory. Across a portfolio of live and recently completed jobs, a firm can have a very large sum sitting in retentions it has genuinely earned but is not chasing, because no single view shows it. Government-commissioned research behind the retentions consultation estimated billions are tied up in retentions across UK construction at any one time, with a meaningful share never recovered when the party holding it goes under (gov.uk retention payments consultation).
What a system needs to do: record retention held on every certificate and application, per project, with the two release dates calculated automatically. It should show total retention outstanding across the business, flag releases coming due, and turn “money we forgot to ask for” into a chased, forecastable line. This is one of the fastest paybacks in the whole build — you are collecting cash you already earned.
Applications for payment and valuations
Construction rarely bills a flat invoice. You submit an application for payment (a valuation) for the work done to date, the client or their QS assesses it and issues a payment notice, and the amount actually due is the cumulative value of work minus everything previously paid minus retention. Under the Construction Act the payer has to respond within set timeframes, and if they do not pay you can, in defined circumstances, suspend performance (Construction Act 1996).
Generic invoicing tools only understand a fixed invoice for a fixed amount. They have no concept of “cumulative value to date less previous certificates less retention”, so the QS rebuilds every application by hand and reconciliation with the ledger is a monthly headache.
What a system needs to do: build each application from the contract and the work-to-date figures, net off prior certificates and retention automatically, and track the notice dates so a late or short payment is visible immediately rather than discovered weeks later. Payment discipline is a legal right in this sector; the system should make exercising it effortless.
WIP and over/under-billing
Work-in-progress is where construction profit hides or leaks. Because you bill in stages, at any moment the value you have billed rarely equals the value of work you have done. Bill ahead of the work and you are over-billed — cash looks healthy but you owe that work. Bill behind the work and you are under-billed — you have spent money you have not yet claimed, quietly funding the client. Both distort profit if you judge a job by invoices raised.
Standard accounting treats revenue as invoices issued, so it cannot tell you whether a job is genuinely making money mid-flight. You only learn the truth at the final account, which is far too late to do anything about it. Tracking cost-to-date against billed-to-date against the contract value is the core discipline here, and it is exactly what tracking project profitability without spreadsheets is about.
What a system needs to do: hold committed and actual costs per job, compare them to billed-to-date and the contract value, and surface over/under-billing and margin per project in real time. That turns the final account from a nasty surprise into a running number you manage.
Plant and equipment tracking
Plant is capital that moves. Excavators, generators, scaffolding, cabins and tools live on sites, get transferred between jobs, break down, need servicing, and cost real money whether hired in or owned. Generic software parks owned kit in a fixed-asset register for depreciation and treats hired kit as a supplier invoice — neither tells you where anything is or which job is carrying its cost right now.
The leaks are ordinary and expensive: hire kept on hire long after a job finished, owned plant sitting idle on one site while another hires the same thing in, and costs never recharged to the job that used them.
What a system needs to do: track each significant item — owned or hired — by location and current job, record hire on/off dates, and recharge running cost to the job that has it. Nothing exotic, just knowing where your capital is and which project is paying for it.
Multi-project cash flow
A construction firm does not have one cash position; it has one per project, and the company figure is the sum of a dozen very different stories. One job is over-billed and flush, another is under-billed and haemorrhaging, a third has £40k of retention due next month. A single bank balance hides all of that.
Generic tools show you company cash today. They cannot forecast, because forecasting in construction means projecting each job’s applications, certifications, retention releases and subcontractor payments forward and adding them up. Without that, you find out about a cash squeeze when a payment bounces.
What a system needs to do: model cash per project — expected receipts from applications and retention releases, expected outgoings on subcontractors, plant and materials — and roll it up into a portfolio forecast. That is the difference between managing cash and being surprised by it, and it is one reason firms move toward an operations dashboard that shows the whole book at a glance.
Document and drawing control
Construction runs on documents that change: drawings, revisions, RFIs, variations, RAMS, certificates, sign-offs. The expensive failure is not a lost file — it is someone building to an old drawing revision because the current one lived in an email nobody forwarded. That is rework, and rework is margin.
General file storage has folders, not version control tied to work. It cannot guarantee that the person on site is looking at revision C and not revision A, and it keeps no clean audit trail of who approved what and when — which matters enormously the moment a dispute or a final account is in play.
What a system needs to do: hold the current revision of each document against the job and the trade, make superseded versions clearly superseded, and keep an audit trail of approvals and variations. It does not need to be a full construction-management suite; it needs one source of truth for “what is current”.
Payment-chain risk when insolvency cascades
This is the pain that ends firms. Construction supply chains are long — client to main contractor to subcontractor to sub-subcontractor — and cash flows down slowly, with retention held at every link. When someone upstream fails, everyone below loses money owed plus retention held by the failed party. It cascades.
The numbers make it concrete: construction is consistently the highest single sector for company insolvencies in the UK — roughly 17% of all cases where the industry is captured (gov.uk insolvency statistics). If one in six failures across the economy is a construction firm, the odds that someone in your chain is fragile are not small.
What a system needs to do: show exposure per client — outstanding applications, certified-but-unpaid amounts, and retention held by them — so a slow-paying or over-concentrated client is visible before it becomes a bad debt. You cannot eliminate the risk, but you can stop being blind to it and refuse to let one client quietly become half your book.
A worked example
Take a groundworks subcontractor, £4m turnover, roughly 20 live and recently completed jobs, three staff plus a QS, running everything on Sage plus spreadsheets.
- CIS: every subcontractor bill is split labour/materials by hand and the monthly return is rebuilt in Excel. One mis-split last year triggered an HMRC correction and a penalty.
- Retention: across those 20 jobs, roughly £95k sits in retention. Nobody has a single list of release dates, so about £30k is overdue and unchased.
- WIP: two jobs look profitable on invoices raised but are actually under-billed and losing margin; the QS only spots it at final account.
- Cash: the company bank balance looks fine, so a £60k subcontractor run and a slow-paying main contractor collide unexpectedly, forcing an emergency overdraft conversation.
A right-sized system does not bolt “construction features” onto Sage. It models the job: costs and commitments per project, CIS handled on entry, retention tracked with release dates, applications built from work-to-date, and a per-project cash forecast across the book. The first win is usually the simplest — chasing the £30k of overdue retention nobody had a list of. It pays for itself before the clever parts even switch on.
FAQ
Do I need a full construction ERP or something smaller?
Most firms under roughly £20m do not need a heavyweight ERP rollout, and often cannot absorb one. What they need is a right-sized system that models the handful of things generic software gets wrong — CIS, retentions, applications, WIP, cash — and connects to the accounting they already run. The distinction between a heavy finance suite and a focused operational layer is covered in operational systems vs ERP.
Can’t my accountant just handle CIS?
Your accountant can file the returns, but they file from your data. If the labour/materials split and subcontractor verification are wrong or late at source, the return is wrong or late. A construction-fit system captures CIS correctly at the point of entry so filing becomes a by-product, not a monthly scramble.
What is the single biggest quick win?
Usually retention. Almost every firm has earned money sitting in retentions with no single list of what is held and when it is due for release. Making that visible often recovers cash within weeks — the fastest payback in the whole build.
Will this replace my accounting software?
No. Accounting stays where it is for the ledger, VAT and statutory accounts. The operational system sits alongside it, handling job costing, CIS, retentions, applications and cash forecasting, and feeds clean figures back. For a broader picture of why construction needs its own layer, see the pillar on construction ERP software.
How long does a right-sized build take?
A focused first phase — say CIS, retention tracking and a cash view — is a matter of weeks, not the year-long programmes big ERPs are known for. It is built in stages, each one delivering something usable, with a delivery guarantee rather than an open-ended project.
How OpsMavix Can Help
OpsMavix builds right-sized, owned operations systems for construction firms that are too messy for spreadsheets but not ready for — or well served by — a full ERP. We do not sell you a generic ERP licence or a pile of custom code and walk away. We start by finding where your money and time actually leak — retentions you have not chased, jobs quietly losing margin, CIS eating your month, clients you are dangerously exposed to — and we build the smallest system that closes those leaks.
You own it. It fits how your firm already works, connects to the accounting you already run, and is delivered in stages against a delivery guarantee — so you see value early instead of waiting a year for a big-bang go-live that never quite lands.
If you run a construction or specialist subcontracting firm and any of the pains above sound familiar, the first step costs nothing. Book a Free Operations Leak Audit.