Implementing an ERP System for the Construction Industry: Rollout Guide & Pitfalls
Most construction ERP rollouts stall on data, adoption and scope, not software. This guide walks through a phased rollout, migrating off spreadsheets, getting site teams and subcontractors on board, and a realistic timeline. It also shows how a right-sized owned system de-risks the whole thing versus a heavy off-the-shelf ERP.
Implementing an ERP system for construction industry firms succeeds or fails on the work done before go-live: agreeing scope, designing cost codes, migrating live jobs accurately and configuring CIS and VAT correctly. The software matters, but a well-chosen platform still fails if open commitments are loaded twice, retentions disappear in migration or subcontractor payments use the wrong deduction.
The practical problem is that a contractor cannot pause trading while the system changes. Jobs are part-valued, subcontractors are mid-package, retentions sit on both sides of the ledger and HMRC deadlines keep running. This guide sets out a rollout sequence that protects those live positions, with a pilot job, a planned cutover and training that suits site teams.

A rollout has to keep live sites, subcontractors and valuations moving while records change systems. Illustrative photograph, not an OpsMavix project.
Image credit: shraga kopstein, Unsplash License. No edits.
Key Takeaways
- Phase the rollout so job costing and finance are stable before site tools go live.
- Design cost codes once, with site and finance agreeing the structure before any data loads.
- Migrate open jobs as reconciled positions: valuations, cash, retentions and remaining commitments.
- Configure CIS verification, deduction basis and monthly returns from HMRC guidance, then test them.
- Set up the VAT domestic reverse charge with end user and intermediary status recorded per customer.
- Prove everything on a pilot job, then cut over on a planned date with the old records frozen.
In this guide:
- 1. Plan the Rollout in Phases
- 2. Design Cost Codes Before Loading Data
- 3. Migrate Open Jobs, Commitments and Retentions
- 4. Configure CIS From HMRC Guidance
- 5. Set Up the VAT Domestic Reverse Charge
- 6. Test Real Construction Scenarios
- 7. Run a Pilot Job and Plan Cutover
- 8. Train Site Users and Avoid Common Pitfalls
- Frequently Asked Questions
- How OpsMavix Can Help
1. Plan the Rollout in Phases
Decide the scope before the build
This guide assumes the decision to implement has already been made. If you are still weighing that up, read do you need construction ERP and the buyer’s map of ERP systems for construction first. For budgeting, see construction ERP cost.
Once the platform or build approach is chosen, write down which records the new system will own on day one. A typical contractor list covers jobs and cost codes, budgets, purchase orders and subcontract orders, subcontractor valuations, client applications, CIS, retentions and the ledger. Anything outside that list either stays where it is or waits for a later phase.
Sequence the phases
| Phase | What goes live | Exit test before the next phase |
|---|---|---|
| 1. Foundations | Cost codes, job set-up, chart of accounts, VAT and CIS settings | Finance signs off codes, tax settings and permissions |
| 2. Commercial and finance | Budgets, orders, subcontract valuations, client applications, retentions | Pilot job reconciles to the old records |
| 3. Cutover | All open jobs migrated, old records frozen | Opening positions agree job by job |
| 4. Site capture | Timesheets, deliveries, daily records on mobile | Site entries reach the right job and code without rework |
| 5. Review | Reporting, exceptions, change requests | Agreed reports run from the new system only |
Each phase has a named owner and written acceptance criteria. A big-bang launch of every module on one date puts payroll, subcontractor payments and client billing at risk together, so most contractors are better served by a sequence like this. The general method is covered in our ERP implementation guide; this guide focuses on the construction-specific parts.
Name the people, not just the roles
- Project owner: one person with authority to decide scope questions and hold the date.
- Finance lead: owns VAT, CIS, ledger mapping and opening balances.
- Commercial lead: owns cost codes, budgets, valuations and retentions.
- Site champion: one respected site manager or foreman who tests mobile capture.
- Supplier or developer contact: responsible for configuration, data loads and fixes.
2. Design Cost Codes Before Loading Data
Agree one structure that both site and finance use
Cost codes are the backbone of construction reporting. If the structure changes after go-live, historical comparisons break and migrated budgets need remapping. Settle it first.
A workable structure usually has two or three levels: a work package or trade, an element within it, and a cost type such as labour, materials, plant, subcontract or preliminaries. The structure should be detailed enough to show where a job is losing margin, and simple enough that a site manager can choose the right code in seconds.
| Design choice | Too coarse | Too fine | Workable middle |
|---|---|---|---|
| Levels | One flat list | Five or more nested levels | Package, element, cost type |
| Number of codes per job | Under 10 | Several hundred | Enough to match how you price and value |
| Who can create codes | Anyone | Nobody without a change request | Commercial lead, with finance review |
| Link to estimate | None | Every estimate line | Estimate summary maps to code level |
Cost code design checklist
- Map your current estimate template to the proposed codes before approving them.
- Separate cost types so labour, materials, plant and subcontract can be reported apart.
- Keep preliminaries and overheads distinct from package costs.
- Add a code for variations, or a variation reference, so change costs are traceable.
- Decide how codes map to the ledger so job reports reconcile to the accounts.
- Lock the structure and restrict who can add codes after go-live.
Separating cost, value and cash in reporting is explained in construction enterprise resource planning. Here the point is practical: every migrated budget, commitment and cost line needs a valid code before it loads.
3. Migrate Open Jobs, Commitments and Retentions
Migrate positions, not every transaction
Completed jobs rarely need full transaction history in the new system; an archive the team can search is usually enough. Open jobs are different. Each one needs an opening position that agrees with the old records on the cutover date, covering what has been valued, invoiced, received, committed and retained.
| Record | What to migrate | Reconcile against |
|---|---|---|
| Job and budget | Contract sum, approved variations, budget by cost code | Latest commercial report |
| Client valuations | Gross valuation to date, retention held by client, amounts invoiced and received | Sales ledger and valuation file |
| Cost to date | Actual cost by cost code at cutover | Job cost report and purchase ledger |
| Subcontract orders | Order value, gross certified to date, retention held, remaining commitment | Subcontract ledger and valuation records |
| Purchase orders | Unreceived and uninvoiced order lines | Open order report |
| Subcontractor records | UTR, verification result and deduction rate, VAT status | CIS records and HMRC verification results |
| Retention release dates | Expected release dates and conditions from each contract | Contract documents |
Hypothetical worked example: one open job at cutover
All figures are hypothetical and exclude VAT.
| Sales side | Amount |
|---|---|
| Contract sum including approved variations | £480,000 |
| Gross valuation certified to date | £300,000 |
| Retention held by client at 5% | £15,000 |
| Net certified to date | £285,000 |
| Cash received to date | £240,000 |
| Certified but unpaid at cutover | £45,000 |
On the cost side, actual cost to date is £255,000. That includes £70,000 certified on a £120,000 subcontract order, so the remaining subcontract commitment is £50,000. The contractor holds 3% retention on that subcontract, which is £2,100 owed to the subcontractor when release conditions are met. Materials orders not yet received total £8,000, and the commercial team expects a further £110,000 of uncommitted cost to finish.
| Cost forecast | Amount |
|---|---|
| Actual cost to date | £255,000 |
| Remaining subcontract commitment | £50,000 |
| Open materials orders | £8,000 |
| Uncommitted cost to complete | £110,000 |
| Forecast final cost | £423,000 |
| Forecast margin against £480,000 | £57,000 |
The forecast margin is about 11.9%. The most common migration error is loading the full £120,000 subcontract order as a commitment while also loading the £70,000 already certified as cost. That would overstate the forecast by £70,000 and turn a £57,000 margin into a £13,000 loss.
Migration checklist
- Clean supplier and subcontractor records before extraction, removing duplicates.
- Load one closed job first as a rehearsal and reconcile it in full.
- Agree a cutover date and extract every open job at that date.
- Reconcile each job’s opening position against the old records before sign-off.
- Load retention receivable and payable balances with release dates, not as one lump.
- Freeze the old spreadsheets and ledgers for editing once the load is accepted.
Our guide on how to build one source of truth covers the wider discipline of retiring duplicate records.
4. Configure CIS From HMRC Guidance
Verification and rates
HMRC says that before you can pay a new subcontractor, you need to verify them. The same page says you must also verify a subcontractor you have used before if you have not included them on a CIS return in the current or last 2 tax years. The details must match what the subcontractor used to register.
HMRC’s deduction guidance lists three rates: 20% for registered subcontractors, 30% for unregistered subcontractors and 0% where the subcontractor has gross payment status. The rate comes from verification, so the system should store the verification result against each subcontractor rather than assuming a default.
Deduction basis and statements
The deduction is not calculated on the whole invoice. HMRC says to start with the gross amount of the invoice and remove what the subcontractor paid for VAT, materials, consumable stores, fuel other than for travelling, plant hire for the job and manufacturing or prefabricating materials. The rate applies to what remains. Your configuration therefore needs invoice lines that separate labour from those other amounts.
HMRC also says payment and deduction statements are due within 14 days of the end of each tax month. Monthly returns must reach HMRC by the 19th of the month after the tax month ends, so a tax month of 6 May to 5 June has a return due by 19 June. HMRC says late filing penalties start at £100.
CIS configuration checklist
- Store UTR, legal form, verification result and deduction rate per subcontractor.
- Flag subcontractors who need re-verification under the 2 tax year rule.
- Split subcontractor invoices into labour and the deductible categories HMRC lists.
- Generate payment and deduction statements from the same records as the payment.
- Produce the monthly return figures from the system and reconcile them before filing.
- Have your finance team or accountant confirm the set-up against your own position.
The general scheme is described on HMRC’s Construction Industry Scheme overview.
5. Set Up the VAT Domestic Reverse Charge

Tax settings only work if the records captured on site and in the office reach the right job and supplier. Illustrative photograph, not an OpsMavix project.
Image credit: Marc Zeman, Unsplash License. No edits.
When it applies
HMRC’s guidance on the domestic reverse charge for building and construction services says it applies to standard and reduced rate services, between VAT-registered businesses, that are reported within the Construction Industry Scheme. The guidance update history shows it was introduced on 1 March 2021. The same page lists services excluded when supplied on their own, such as professional work by architects and surveyors, and advises businesses to make sure their accounting systems and software can deal with the reverse charge.
Customer status and invoices
HMRC’s reverse charge technical guide explains that the reverse charge does not apply where the customer is an end user or an intermediary supplier and tells the supplier this in writing. It also describes a 5% disregard, where reverse charge elements of 5% or less of the whole supply value can be disregarded, agreed from the start of the contract rather than invoice by invoice.
Invoices must make clear that the reverse charge applies and that the customer accounts for the VAT. HMRC gives example wording including “S55A VATA 94 applies” and “Customer to pay the VAT to HMRC”. The buyer adds the VAT to the output tax on its VAT return and can usually reclaim it as input tax under the normal rules.
Hypothetical worked example: one subcontractor invoice
A hypothetical VAT-registered subcontractor, verified at the 20% CIS rate, invoices £10,000: £8,000 of labour and £2,000 of materials it bought directly. The reverse charge applies, so no VAT is charged on the invoice. Retention is ignored to keep the example simple.
| Calculation | Amount |
|---|---|
| Invoice total, no VAT charged | £10,000 |
| Less materials paid for by the subcontractor | £2,000 |
| Amount subject to CIS deduction | £8,000 |
| CIS deduction at 20% | £1,600 |
| Paid to subcontractor | £8,400 |
| VAT the contractor accounts for as output tax at 20% | £2,000 |
| Input tax normally reclaimable on the same purchase | £2,000 |
The system has to handle both rules on one document: the CIS deduction on the labour element and the reverse charge VAT on the full value. Test that both appear correctly in the CIS return figures and the VAT return.
Reverse charge configuration checklist
- Record end user or intermediary status per customer, with the written notice attached.
- Record each supplier’s VAT and CIS status so purchase invoices default correctly.
- Add reverse charge tax codes for standard and reduced rate supplies.
- Include the required invoice wording on sales templates where the charge applies.
- Check that reverse charge VAT reaches the right VAT return figures.
- For cutover timing around VAT periods, see ERP implementation UK.
6. Test Real Construction Scenarios
Test the awkward cases, not just the happy path
A standard invoice posting proves only that one route works. Construction rollouts fail on part-deliveries, disputed valuations, retentions and tax exceptions. Write test scripts from real recent jobs, with expected results agreed before testing starts.
| Scenario | Expected result to check |
|---|---|
| Partial delivery against a purchase order | Received quantity costed, balance remains committed |
| Subcontract valuation with retention and CIS | Retention held, CIS on correct basis, statement produced |
| Reverse charge sale to a main contractor | No VAT charged, correct invoice wording |
| End user customer with written notice | Normal VAT invoice issued |
| Client pays less than the application | Difference visible, not silently written off |
| Variation proposed then approved | Budget and value change only on approval |
| Retention release on practical completion | Correct portion released, remaining balance and date held |
| Cost posted to a closed job or invalid code | Blocked or sent to an exceptions queue |
Testing checklist
- Use migrated data, not just new sample jobs.
- Have finance run a trial CIS return and VAT return from test data.
- Test user permissions: who can approve orders, valuations and code changes.
- Test reports against figures calculated by hand.
- Record every failure, its owner and its retest result.
7. Run a Pilot Job and Plan Cutover
Choose a representative pilot
The pilot should be a live job with purchasing, at least one subcontractor under CIS, a client valuation, retention and preferably a variation. A small, simple job proves little. Run it through the new system for at least one full valuation cycle while the old records continue in parallel, then compare the results line by line.
Plan cutover as a dated sequence
| Step | Owner | Done when |
|---|---|---|
| Confirm cutover date, avoiding a CIS return or VAT deadline week | Project owner | Date agreed with finance |
| Final extract of open jobs, commitments and retentions | Finance and commercial leads | Extract signed off |
| Load and reconcile opening positions | Supplier or developer, finance | Every job agrees to the old records |
| Freeze old spreadsheets and ledgers | Project owner | Edit access removed |
| First live valuations and subcontractor payments | Commercial lead | Outputs checked against expectations |
| Short parallel check, then retire old records | Finance lead | Retirement date met |
Keep the parallel period short and dated. If it drifts, staff keep using the old records they trust and the new system never becomes the reference.
8. Train Site Users and Avoid Common Pitfalls
Train by role, on real tasks
Site users need a few tasks done quickly on a phone: book time to the right job and code, record a delivery or shortage, raise a requisition and attach a photo. Train those tasks on the devices they will use, with the site champion running short refresher sessions in the first weeks. Office users need deeper training on approvals, valuations, CIS and reports.
- Give each role a one-page task guide, not a full manual.
- Test mobile capture where signal is poor, and confirm whether offline entry is supported.
- Explain the benefit to each group, such as faster subcontractor payment from cleaner valuations.
- Set a date to retire the paper forms and messaging groups that the system replaces.
Common pitfalls and how to avoid them
| Pitfall | Why it hurts | Prevention |
|---|---|---|
| Changing cost codes after go-live | Breaks comparisons and migrated budgets | Agree and lock codes in phase 1 |
| Loading full order values as commitments | Double counts cost already certified | Migrate remaining commitment only |
| Losing retention detail | Releases missed or paid twice | Load retentions per job with dates |
| One default CIS rate for everyone | Wrong deductions and returns | Store verification result per subcontractor |
| Reverse charge applied to end users | Incorrect invoices | Record customer status with written notice |
| Long, open-ended parallel running | Two versions of the truth | Fixed retirement date |
| Skipping the pilot | Problems surface on every job at once | Pilot on a representative live job |
For the wider question of what construction ERP should include, see construction ERP software and the construction company ERP features checklist.
Frequently Asked Questions
How long does it take to implement an ERP system in a construction firm?
It depends on scope, data quality, the number of open jobs and integrations. Ask for a phased plan with dated milestones, named owners and acceptance criteria rather than a single headline duration.
Should we migrate all historical jobs?
Usually not. Migrate open jobs as reconciled opening positions and keep completed jobs in a searchable archive, retained for the periods your accountant advises.
How do we migrate retentions?
Load retention held by clients and retention you hold from subcontractors per job, with amounts, release conditions and expected dates taken from each contract. Reconcile totals to the old records before sign-off.
What CIS settings must a construction ERP support?
Per-subcontractor verification results and deduction rates, a deduction basis that excludes the items HMRC lists such as materials and VAT, payment and deduction statements, and monthly return figures. Finance should confirm the set-up.
Does the domestic reverse charge apply to every construction invoice?
No. HMRC says it applies to standard and reduced rate services between VAT-registered businesses that are reported within CIS, and not where the customer is an end user or intermediary supplier who has told the supplier in writing.
What makes a good pilot job?
A live job with purchasing, at least one CIS subcontractor, a client valuation, retention and ideally a variation, run through a full valuation cycle and compared with the old records.
How do we get site teams to use the system?
Keep site tasks short and mobile, train on real tasks, appoint a site champion and set a date to retire the old forms and messaging groups.
Can OpsMavix build a construction ERP?
Yes. OpsMavix can build focused applications or a full custom construction ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how jobs, orders, subcontractor valuations, CIS and retentions move through your business today, then plan a phased rollout that protects live positions during migration.
That may mean configuring and connecting the tools you already use, building a project operations dashboard for live cost and forecast reporting, adding an invoice approval workflow for purchase and subcontractor invoices, or developing a full custom ERP where that fits better.
Contact OpsMavix with one recent subcontractor valuation, the records behind it and the step that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.