In France, since 1 September 2026, every business established there and registered for VAT must be able to receive electronic invoices, and SMEs and micro-businesses will have to issue them from 1 September 2027, according to Service Public Entreprendre. That timetable is pushing many French construction firms towards an ERP. Yet the choice is decided elsewhere: on job management site by site, purchasing, time tracking and job costing, and on a phased rollout that does not bring operations to a halt.
Construction ERP software: what it really covers beyond quotes and invoices
Job management and budget per job: margins, progress and variances in real time
An ERP for construction is there to run your jobs like small businesses. For each job, you track a budget (labour, materials, subcontracting), progress and interim invoicing, and also the actual margin as the work goes on. The aim is simple: see the gap between budget and actual early enough to correct it, not just to record it.
Purchasing, supplier orders, stock and depot: avoiding stockouts and oversights
Purchasing is the heart of the day-to-day. The ERP links requisitions, purchase orders, goods received and supplier invoices. At the depot, you keep a clear view of stock levels, locations and reservations per job, with alerts on what is still to order. Fewer oversights, fewer stockouts, less material sitting idle.
Time tracking, payroll interface and job costing: linking hours, costs and results
Time tracking ties hours to tasks and jobs, agency staff and subcontractors included. Once it is linked to payroll, every hour becomes a cost, then an analytical hourly cost per job. By cross-checking time and purchases, you quickly see what makes money, and what is slipping.
When construction ERP software becomes worthwhile
Organisation: the point where coordination no longer works by word of mouth
An ERP pays its way when coordination no longer works by word of mouth and a site manager spends too much time piecing information back together between quotes, orders and timesheets.
Simultaneous jobs: when Excel spreadsheets are no longer enough
When several jobs run in parallel, Excel versions multiply, orders arrive too early or too late, and tracking job by job becomes hazy.
| Company situation | Main risk | What the ERP stabilises |
|---|---|---|
| A few jobs followed by the owner | Manageable by hand | Light centralisation of quotes and invoices |
| Several jobs in parallel, one site manager | Coordination | Purchasing, scheduling, deliveries |
| Several teams, a depot, subcontracting | Margin loss | Job costing, alerts, chasing |
Warning signs on the ground: double entry, stock errors, late invoicing, disputes
- Quotes, orders and hours keyed in twice, followed by VAT errors or costs booked to the wrong job.
- Recurring gaps between depot, van and site, with emergency purchases.
- Invoices going out at month end for want of delivery notes or approved timesheets.
- Disputes with subcontractors, variations nobody can find, photos and handover reports scattered.
If these signs come back every week, the issue is not only the tool. It is the ability to keep up the configuration and the routines.
Choosing your construction ERP software: criteria that avoid nasty surprises
Essential functions for your trade: renovation, maintenance, multiple depots, subcontracting
An ERP is worth above all what its scope covers. In renovation, aim for job tracking, purchasing, interim valuations and a simple reading of the job margin. In maintenance, look for contracts, scheduling, service history and reminders. With several depots, insist on stock movements, transfers and stocktakes. With subcontracting, secure orders, progress, attachments and sign-off before payment.
Mobility on site and at the depot: time tracking, delivery notes, photos and sign-off
On mobile, check time tracking by team, delivery notes, timestamped photos, approvals, signatures and snagging. The depot must be able to scan, pick and issue materials without keying anything in again. An offline mode makes all the difference when there is no signal on site.
Required integrations: accounting, payroll, banking, e-invoicing and document management
Without connectors, double entry piles up. Ask for an API, imports, exports, and document management linked to jobs. On the accounting side, the FEC export (France's standard accounting audit file) and entries broken down by job avoid workarounds. For French e-invoicing, ask whether the ERP is itself an approved platform or a compatible solution connected to one, and which. For payroll, the goal is time tracking you can use as it stands, with no spreadsheet, right through to the pay variables.
What construction ERP software really costs: full budget and hidden items
The price does not stop at the licence. The budget is mostly decided by the implementation, and by everything you pay on top as the team grows or as you add uses.
| Item | Type of spend | What pushes it up |
|---|---|---|
| Licence and modules | Recurring, per user or per profile | Extra profiles, modules added along the way |
| Configuration and data migration | One-off, often the heaviest | Inconsistent data, custom development |
| Interfaces (payroll, accounting, banking, document management) | One-off, then maintenance | Number of connectors and tools already in place |
| Training and support | One-off at launch, then recurring | Staff turnover, new uses |
Per-user licence: rights, profiles, modules and recurring costs
The recurring cost depends on the number of users, but also on profiles. A site manager, a buyer and someone in the office do not always have the same rights or the same modules. Watch out for options that get added along the way: read the vendor's pricing page on the day you compare, and have what is included written into the contract.
Initial configuration, data migration and training: the real entry ticket
The entry ticket is translating your jobs into rules: cost structure, job stages, purchase approval workflows, interim valuation templates. Data migration and training take time, especially when the files are inconsistent.
Deployment time: typical schedule and what drags a project out
A realistic schedule is counted in weeks, even months, not days. What drags it out: too much bespoke work, payroll or accounting interfaces to connect, dirty data, and no internal lead on the company side.
Avoiding failure: classic pitfalls and a rollout method that holds up
The fake ERP trap: quoting software plus an invoicing module, and its day-to-day limits
A fake ERP is often quoting software with an invoicing module and a few lists. At first, it gets by. Then, as soon as you have several jobs at once, purchasing, stock, time tracking and job costing turn into a saga: double entry and a margin estimated by guesswork. An ERP must cover the whole job, not only the quote.
Configuration: why it is the first cause of failure and how to scope it
The software works. What breaks the project is configuration pushed back to the end: job coding, items, units, approval workflows, entry rules, cost structure. Scoping it stays simple: short workshops, written decisions, test data, then acceptance testing on real cases. Keep a first version that is manageable.
Deploying without breakage: pilot, management rules, internal lead and ramp-up
- A time-boxed pilot on one team and one depot, with written objectives.
- An internal lead given the time it takes, and one rule: one piece of data, one owner.
- A ramp-up in phases, with training on the ground, support and a weekly check-in.



