What is construction ERP? A business system that keeps the job, not the accounting month, as the unit of record for cost, revenue and change orders. The test is the period boundary. When a change order for September work arrives after September closes, construction ERP attaches it to the job and keeps job-to-date margin right while September stays closed.
That definition is narrower than the feature lists that rank for this question. Accounting software with job costing added can tag a cost to a job. Where it breaks is the moment the job and the calendar disagree, and on a construction job that happens every month. Crestwood has analyzed 28 of its own buyer meetings for the problems finance and operations leaders describe. In 6 of them, the buyer described the field and the books as disconnected. One finance lead put the mechanism in a sentence: revenue “isn’t even captured in the same period,” with “no way of period matching revenue and expenses.” This article defines construction ERP by that boundary, shows what a general system does when a job crosses it, and gives you five tests to run against your own system this week.
What construction ERP is
Construction ERP is enterprise resource planning built around the job. Every cost, commitment, change order, bill and payroll hour carries a job and a cost code, and the system reports each job from start to finish however many accounting periods it spans. General accounting tracks the business by month. Construction ERP tracks it by month and by job, and keeps the two reconciled.
Six things hang off the job in a construction system:
- Job cost against budget, by cost code
- Commitments: subcontracts and purchase orders counted against the budget before the invoice arrives
- Change orders, pending and approved, as documents attached to the contract
- Progress billing, including AIA-style pay applications, with retainage held and released
- A WIP schedule comparing cost to date with billings to date, job by job
- Payroll that splits hours across jobs, including certified payroll on prevailing wage work
Each one is a reason the job has to outlive the month. Retainage is the plainest case: it is billed in one period and often collected many periods later.
The period boundary, and why every job crosses one
A job crosses a period boundary when the work happens in one accounting period and the document that prices it arrives in another. The subcontractor invoice for August work lands on 12 September. The foreman’s time cards come in after the cutoff. The owner approves a change order three weeks after the crew did the work.
On a job that runs six months, this is the normal shape of the paperwork, every month. Close is where it bites. Finance closes the month on the documents it has, and anything that arrives later belongs to a period already reported.
If you are the controller, you know the day. The field sends in the paperwork that reprices a job the books already closed, and a job that looked profitable in the system looks thin in the field report.
What a general system does at the boundary
A general accounting system closes the period on the numbers it has and locks it. A late change order then has two places to go. It can go back into the closed month, which means reopening it and restating a number already reported. Or it can go into the current month, which leaves the job’s margin split across two periods that no longer describe the work.
QuickBooks makes a useful example. Intuit’s own help documentation describes closing the books as a lock: “You can’t change any transactions on or before that date without approval,” and an attempt to change one triggers a warning or a password prompt (Intuit, Close your books in QuickBooks Online). For a business whose unit of record is the month, that is a sound control.
For a contractor, the lock forces the choice above, and both branches end in the same place: a manual journal entry, and a spreadsheet that holds the real job margin because the system no longer does. That is where QuickBooks and spreadsheets stop working for construction: at the boundary, well before anyone runs out of job costing features. Across the 28 buyer meetings, a spreadsheet doing a system’s job came up in 15.
What construction ERP does instead
Construction ERP keeps the closed month closed and keeps the job whole. The late change order posts to the current period in the general ledger and stays attached to its job, contract and cost codes. Job-to-date cost, billing and margin read correctly on the day it is entered. The month and the job each tell the truth, and nobody rebuilds one from the other at close.
| SEPTEMBERCrew does the extra work18 SeptemberSeptember closed | OCTOBERChange order approved and priced6 October |
The same logic runs through the rest of the job. A commitment shows against the budget when the subcontract is signed, so the WIP schedule reflects cost that is coming as well as cost that has arrived.
| What you look at | General accounting with job costing added | Construction ERP |
|---|---|---|
| Unit of record | The month. Jobs are a tag on transactions | The job, from contract to closeout, reconciled to the month |
| A change order | A note, or an adjusted invoice line, after the fact | A document with a status, an amount and a budget impact, attached to the contract and cost codes |
| Cost that arrives after close | Reopen the closed month, or post to the current one and fix job margin in a spreadsheet | Posts to the current month; job-to-date cost and margin stay correct |
| Commitments | Usually invisible until the invoice arrives | Subcontracts and purchase orders visible against budget when issued |
| WIP schedule | Rebuilt in a spreadsheet at each close | Produced from job data: cost to date against billings to date, job by job |
| Retainage | Tracked in a separate account or list | Held and released on the job’s own billing |
Five ways to test your own system this week
You can run all five without talking to a vendor. Use a test company or sandbox where you have one, and write down what you see.
1. Date a change order into a closed month
Pick a job with a change order approved after the month it covers was closed. Find where it was entered, then pull job-to-date margin for that job. If the right number comes out of the system, you pass. If the right number lives in a spreadsheet, you have found the boundary.
2. Count the days from field cost to job report
Pick one cost incurred in the field last week: a delivery, a rental, a day of labor. Note the day it was incurred and the day it appeared in the job cost report. The gap is the window in which every job decision runs on old numbers.
3. Match revenue to the period that earned it
Take one job and pull revenue and cost by period for the last three months. Check whether revenue sits in the same period as the cost that earned it. That is the period matching the finance lead quoted above said they had no way to do.
4. Split one person’s hours across two jobs
Run payroll for one employee who worked two jobs in one week, at two rates if you do prevailing wage work. If the job split, and any certified payroll report, comes out of the system without rekeying, you pass.
5. List the spreadsheets open at close
At your next close, list every spreadsheet someone opens. Ask one question of each: is it carrying a month or a job? A spreadsheet carrying a job is doing a construction system’s work.
Score it. Five passes means your system already carries the job across the boundary. Two or more failures means the pain at close has a location, and it is a property of the system rather than of the team. When you take the results to vendors, the eight questions to ask when buying ERP software for construction turn each failed test into a question a vendor has to answer on screen, starting with the closed-period change order.
When a general system is still the right answer
A general system is the right answer when the job and the month rarely disagree. That usually means all of these hold:
- Jobs start and finish inside one accounting period
- No retainage and no progress billing
- No prevailing wage work and no certified payroll
- One legal entity
- Change orders are rare and priced before the work starts
If that describes your business, construction ERP adds setup and discipline you would pay for and not use. Keep the system, tighten the close, and rerun the five tests once a year or when your jobs get longer.
Why Crestwood for construction ERP
Crestwood is an Acumatica Partner and a Microsoft Business Central partner, and the contractors on this page run Acumatica. Selling and supporting two platforms means a recommendation costs us something, which is why the five tests above come before any platform name in this article.
Alpha Insulation & Waterproofing, a specialty construction subcontractor in Columbus, Ohio, moved off a legacy project and financial system that limited its visibility into job performance. It cut WIP reporting from more than a day to minutes. Liberty Elevator, an elevator construction, modernization and service company, had much of its accounting running on spreadsheets and no project costing or WIP. It reduced accounting expense by at least 10% and had cost against budget reports available from day one of go-live.
When you reach the vendor stage, evaluate the partner as well as the platform. The Three-Legged Stool framework Crestwood uses to evaluate ERP partners, across Partner, Platform, and People, exists because software is one leg of three. Our construction ERP services page covers how that work runs for contractors.
Start with what is slowing the close down
If the tests turned up failures and you want an outside read before deciding anything, start with the Business Optimization Assessment. A Crestwood advisor works through five areas with your finance and operations leads: workflow, reporting, system utilization, connected systems, and finance and controls, including where your close time goes. Within 24 hours you receive a written, prioritized summary that is yours to act on with us or without us.
The business may not have a people problem. It may have an operating model problem.
We sell, implement, support, and optimize it. An in-house team of industry experts. One hand to shake.
Frequently asked questions
What is construction ERP?
Construction ERP is enterprise resource planning built around the job. Cost, commitments, change orders, progress billing, retainage and payroll all carry a job and a cost code, and the system reports each job across however many accounting periods it spans. The practical test: a change order arriving after its month has closed lands on the job without reopening the month.
What does ERP stand for in construction?
ERP stands for enterprise resource planning. In construction it means one system for job cost, commitments, change orders, progress billing, retainage, payroll and the general ledger, with the job as the unit of record. The test of whether a system qualifies is whether it carries a job across a closed accounting period without a manual journal entry and a spreadsheet.
How does job costing work in construction ERP?
Every cost carries a job and a cost code at the moment it is captured: a time card, a purchase order, a subcontract invoice. The system compares those costs with the job’s budget, including approved change orders, and reports job-to-date cost and margin whether the costs fall in one accounting period or twelve.
Why do construction companies need ERP systems?
Construction jobs run across accounting periods, and general accounting closes by period. When a change order or a late invoice lands after close, a general system forces a choice between reopening the month and splitting the job’s margin across periods. Construction ERP removes that choice. Companies whose jobs start and finish inside one month often do not need it.
How do you connect construction field data to ERP?
Capture each cost where it happens, against a job and a cost code: time on a phone or tablet, deliveries against a purchase order, daily reports from the site. Then measure the result with the second test in this article: count the days between a field cost being incurred and appearing in the job cost report.
What is the best ERP for a construction company?
The one that passes the five tests in this article for your jobs, your billing and your payroll. Run them on your current system first. If it fails two or more, take the failures to vendors as questions, and ask each to demonstrate the closed-period change order on screen using one of your own jobs.
