Most articles on this subject set up a two-way fight: accounting software on one side, ERP on the other. That is not how contractors buy. There are three categories on the table, and the third one, construction project management software, is the one most often confused with the other two.
Contractors rarely have a hole in one category. Far more often you own two of the three and nothing connects them. Project managers work in one system, the controller works in another, and the number that reconciles them is built by hand in Excel, once a month, by one person. That seam is the real problem, and it is the one no comparison article addresses.
The three categories, defined plainly
Three software categories are available to a contractor, and each was built to answer a different question. General accounting software answers what you owe and what you are owed. Construction project management software answers what happened in the field. Construction ERP answers both from one database, which is the only way to answer the question that actually matters: whether a job is making money right now.
Construction accounting software is a financial system organized around the job rather than the accounting period, tracking cost and revenue by project and cost code so profitability can be measured per job as well as per month.
Construction project management software is the operational system of record for the field, holding drawings, submittals, RFIs, daily logs, schedules and change order documentation.
Construction ERP is a single-database system carrying the general ledger, job costing, payroll, procurement, billing and project operations together, so a field transaction and its accounting consequence are one record rather than two that have to be matched later.
| General accounting software | Construction PM software | Construction ERP | |
|---|---|---|---|
| Examples | QuickBooks, Xero | Procore, Autodesk Build, Buildertrend | Acumatica Construction Edition, Sage Intacct Construction, Sage 100 Contractor, Viewpoint, Foundation, CMiC, Deltek |
| Organized around | The chart of accounts and the period | The project and its documents | The job, with the ledger attached to it |
| Native reports | P&L, balance sheet, A/R and A/P aging, sales tax | Daily logs, submittal and RFI logs, change order logs, schedule status | Job cost by cost code, WIP schedule, cost-to-complete, AIA G702/G703 billing, retainage aging, certified payroll, consolidated financials |
| Committed cost | No | Tracked operationally, not against the ledger | PO and subcontract balances post against the job budget |
| Retainage | A manual invoice line | Shown on billings; does not carry the receivable | A sub-ledger on both A/R and A/P, aged separately |
| WIP | No | No | Over- and under-billing from cost and billing in one database |
| Multi-entity | One file per entity | Not applicable | Consolidation with intercompany transactions |
The edges are blurring, and it matters when you shortlist
These three categories are converging from both directions. Project management platforms have been adding financial modules, and several construction ERPs have built out field tools that look a lot like PM software. Sage 100 Contractor and Foundation sit closer to the accounting end of the ERP range; Deltek and CMiC sit at the enterprise end; QuickBooks extended with a construction add-on such as Knowify occupies a genuine middle ground that is neither plain accounting software nor an ERP.
Take the convergence seriously when you shortlist, and do not take a vendor’s category label at face value. The question that cuts through it is always the same: does the general ledger live in this system, and does a field transaction post to the job and to the ledger in one step? A PM platform with an invoicing module has not become an accounting system, and an ERP with a photo log has not become a PM platform. Ask which database the transaction lands in.
What general accounting software genuinely does well
General accounting software is very good at what it was built for: a clean general ledger, fast bank reconciliation, payables and receivables, sales tax and tax-ready financials. For a contractor running a handful of jobs in one entity with an outside payroll service, it is often the right answer, and paying for more than that is waste.
It is inexpensive, well supported and understood by every CPA in the country. None of that is a reason to move. The difference between construction accounting and regular accounting is not software quality, it is unit of measure: regular accounting reports results by period, construction reports them by contract, over durations that cross periods.
The four things general accounting software structurally cannot do
Four construction reporting requirements cannot be produced by general accounting software without rebuilding them in spreadsheets: job costing to the cost-code level, a WIP schedule across open projects, retainage as a real sub-ledger, and multi-entity consolidation. These are structural limits, not settings you have missed.
Job costing to the cost-code level
Job costing is the assignment of every dollar of cost to a specific project and a specific cost code within that project, so labor, burden, material, equipment and subcontract cost can be compared to the estimate line by line.
General ledger accounts are not cost codes. Most general packages attach a class or a customer to a transaction, which gives cost by job and nothing underneath it: no CSI MasterFormat division, no phase, no cost type. If your estimator bid 03 30 00 as its own line, you need actual cost at that line, split by cost type, with labor burden loaded at its true rate rather than swept into period overhead.
A WIP schedule across projects
A WIP schedule is a report comparing cost to date, total estimated cost, and amount billed for every open contract, producing percentage-of-completion, earned revenue, and the over-billing or under-billing on each job.
It is the report your surety and your bank care about most, and the one that tells you whether this month’s profit is real or borrowed from a job you have over-billed. General accounting software cannot produce it because it doesn’t track cost-to-complete. Someone rebuilds it monthly from exported costs, exported billings, and remaining-cost estimates collected from PMs by email.
Retainage as a sub-ledger
Retainage is the portion of each progress payment withheld until the work is accepted, released at substantial completion or in stages. It is not a discount and not an ordinary receivable. It is money you have earned, cannot collect yet, and usually owe forward to your subcontractors at the same time.
A construction system carries retainage receivable and retainage payable as separately aged balances tied to the schedule of values, and ties release to lien waiver collection. In general accounting software, it is a line on an invoice and a number someone tracks on the side.
Multi-entity consolidation
Contractors accumulate entities: an operating company, an equipment company, a real estate holding entity, a joint venture, sometimes an entity per state for licensing. General accounting packages treat these as separate files, so consolidation, intercompany equipment charges and shared overhead allocation happen outside the system. The consolidated statement your bank reads is a spreadsheet, and the intercompany accounts never quite agree.
What construction project management software does well, and why it is not an accounting system
Construction project management software is the best available record of what happened on a job. Drawings, submittals, RFIs, daily logs, photos and change order correspondence belong there, and holding them in one place with a defensible timeline is worth paying for. It is excellent at that work.
What it is not is a system of accounting record. It does not hold your general ledger, run payroll, produce certified payroll for Davis-Bacon work, or calculate labor burden. Its cost figures are only as current as the last export from accounting, usually a period behind. A change order approved in PM software does not move revenue recognition until someone re-enters it on the accounting side, so contract value in the field and contract value on the WIP schedule drift apart between closes.
That is not a defect in the product. It is what happens when two systems each hold half of the same transaction.
The expensive middle: owning two systems and reconciling them by hand
The most common configuration in the industry is general accounting software plus construction project management software, joined by a spreadsheet and a person. On a license comparison, it looks like the cheapest option. In practice, it is usually the most expensive, because the cost sits in labor, in delay, and in decisions made on numbers that are weeks old.
Committed cost shows why. A committed cost is an obligation you have signed for but have not yet been invoiced for, mostly open purchase orders and unbilled subcontract balances. Your true position on a job is cost to date plus commitments against budget. When commitments live in the PM system and actual cost lives in accounting, nobody owns that number.
The PM sees margin, because he is counting approved change orders the ledger has not seen. The controller sees none, because she is counting billed cost without the commitments behind it. Both read their own system correctly. Neither is reading the job.
Everything downstream inherits it: billings assembled by hand because the schedule of values sits in one system and cost in the other, certified payroll rebuilt weekly from a timesheet export, and a WIP schedule that is three weeks stale when it lands.
Is QuickBooks an ERP?
No. QuickBooks is general accounting software, not an ERP. It maintains a general ledger, payables, receivables, and reporting for a single entity, and it does that well. It does not carry cost-code-level job costing, a WIP schedule, retainage sub-ledgers, certified payroll or multi-entity consolidation, which are the functions that make a system an ERP rather than a ledger.
The distinction is categorical, not a matter of size. QuickBooks does not become an ERP at a certain revenue, and an ERP is not simply a larger QuickBooks. They are organized around different units: the period versus the job.
One current qualifier is worth stating plainly, because a contractor researching this will meet it immediately. Intuit now markets Intuit Enterprise Suite as a higher tier for multi-entity businesses, and it is advertising against construction queries. It moves QuickBooks closer to ERP territory. Whether it closes the gap for a particular contractor comes down to the same five questions worth asking of any candidate: does it job cost to cost-code level, produce AIA G702/G703 pay applications, carry retainage as a native field on both sides, generate certified payroll for prevailing-wage work, and post committed cost from purchase orders and subcontracts against the job budget.
Where QuickBooks runs out is a question of complexity rather than revenue — jobs, entities and compliance obligations growing past what one person can hold in a spreadsheet beside it. For the symptom-level version of that question, written around what happens in your month-end close rather than around software categories, read signs you’ve outgrown QuickBooks for construction.
How to tell which of the three you actually need
You do not choose between these categories in the abstract. Name the report you cannot produce today, then ask which system owns the data that report requires. Three cases separate cleanly.
You need general accounting software if you can state your cost position on every open job from memory, you run one entity, and your compliance obligations stop at payroll and sales tax. You do not have a software problem.
You need construction project management software if your financial reporting is sound but your field record is not: change orders agreed verbally, submittals tracked in email, nothing defensible when a dispute arrives. That is a documentation gap, and an ERP will not close it.
You need construction ERP if the reports you cannot produce require cost and billing to sit in the same database: WIP on any day of the month rather than three weeks after close, cost-to-complete that reflects committed cost, consolidated statements across entities, certified payroll generated from the same time entry that hit job cost. No connector produces these, because the underlying transaction was never recorded once.
Decide on the next three years, not on this month
The most common selection error is choosing for today’s loudest pain. A contractor who picks a system to fix one broken payroll process often outgrows it inside two or three years, because the pain that was loudest was not the pain that was structural.
Run the decision against where the business is heading rather than where it sits. Work you are bidding but have not won yet changes the answer: public and institutional work brings certified payroll and bonding reporting, design-build brings revenue recognition complexity, a second state brings multi-jurisdiction payroll, and an acquisition brings consolidation. If any of those is on the three-year plan, weigh them now. They are expensive to retrofit and cheap to specify up front.
If you have reached the third case and are choosing between platforms, compare Acumatica against NetSuite, Sage and QuickBooks on the criteria that matter to a contractor.
What changes when you consolidate, and what it costs
Consolidating onto a construction ERP changes one thing structurally: a transaction is entered once and every report derives from it. A timecard coded to a job and cost code becomes burdened labor cost, a certified payroll line, a general ledger entry and an input to percentage-of-completion in a single step. Month-end close stops being a reconstruction project.
The practical effects are consistent. WIP is available on demand instead of on a lag. Billings come off the schedule of values already in the system. Retainage is aged rather than remembered. Entities consolidate without a spreadsheet in the middle.
The cost is real. There is license cost, implementation cost, and the internal time of the people who know how your jobs actually work, which is the part contractors underestimate. The chart of accounts and cost code structure get rebuilt, and prevailing-wage payroll setup takes longer than anyone expects.
A construction ERP implementation typically takes between 12 weeks and a year, and implementation costs typically range from $40,000 to $250,000.
Four things move a project within those ranges: the complexity of the business, how much historical data you want to bring across, the size of the company, and how much of your own staff’s time you can dedicate to the work. The last one is the least discussed and it is worth taking seriously — it is the variable you control, and it is largely what decides whether you land at twelve weeks or twelve months.
The ranges are wide because scope genuinely varies, not because the numbers are soft. A single-entity contractor moving job cost, billing and payroll is a different project from a multi-entity group migrating several years of job history and running certified payroll across several states. Any partner quoting you a figure before understanding which of those you are should be treated with suspicion.
Two things reliably go wrong: keeping the old spreadsheets running beside the new system, and treating the work as an accounting project rather than an operations one. The contractors who get value are the ones whose PMs adopt the cost coding discipline, because the data that makes WIP trustworthy is created in the field.
