Ask a construction CFO what keeps them up at night, and job costing comes up almost every time. Not because they don't understand their business, but because their software doesn't understand it the way they need it to.
QuickBooks was never built for construction. That's not a criticism; it's just the truth. It's a general ledger, and construction accounting isn't general. It's project-based, retainage-heavy, subcontractor-dependent, and margin-sensitive in ways that a standard chart of accounts and basic job costing tools can't fully capture. For small contractors, that gap is manageable. Past a certain size, it becomes the thing quietly eating your margins on every job.
Most software categories can treat "the business" as one thing. Construction accounting can't, because every project is effectively its own mini-business with its own budget, its own cost structure, its own subcontractors, and its own profitability that needs to be tracked in real time, not reconstructed after the job closes.
That means construction ERP needs to handle several things natively. Job costing at a level of granularity that ties labor, materials, equipment, and subcontractor costs to specific cost codes on specific projects. Retainage tracking on both the receivable side (what your GC owes you) and the payable side (what you owe subs), which QuickBooks doesn't handle with any real sophistication. Commitment management that tracks purchase orders and subcontracts against budget in real time, not after invoices land. Percentage-of-completion accounting, which is standard for construction but foreign to QuickBooks's transaction-based model. And field-level visibility so project managers see cost and budget data without waiting for accounting to compile it.
QuickBooks approximates some of these with add-ons and workarounds. But approximation is exactly the problem. It's why job costs are "always a little off" at so many contractors, discovered late, and never quite trusted by the people making decisions on them.
Here's the mechanism worth understanding: in a business with tight margins on individual jobs, small inaccuracies in job costing don't average out. They compound, because pricing on future jobs gets built on the assumption that past job costs were accurate. If your job costing has been quietly wrong by a few percentage points, that error is baked into how you're bidding new work, which means you're not just misreading history. You're mispricing the future.
That's the real danger of "close enough" job costing. It doesn't just distort last quarter's numbers. It distorts next quarter's bids.
Carma Group is a Las Vegas general contractor doing over $100M in revenue, running high-profile projects including the Bellagio grandstand build for Formula One. They'd outgrown QuickBooks Online and knew it. The specific gaps were exactly the ones described above: no real job costing depth, no retainage tracking, no commitment management. For a company running projects at that scale and visibility, those weren't nice-to-haves. They were basics the software simply didn't have.
During their evaluation, the deciding factor wasn't a features checklist. It was fit. Acumatica's Construction Edition had project accounting, subcontractor management, and field-level visibility built in natively. Just as important, it integrated seamlessly with Procore, which Carma already relied on for field operations. That single integration eliminated an entire layer of manual data transfer between systems that previously didn't talk to each other, and gave project managers real-time margin visibility on their projects for the first time.
The lesson generalizes well beyond Carma's specific size: the deciding factor for construction companies usually isn't a long list of features. It's whether the platform has your industry's core requirements built in natively, or whether you're going to spend the next three years stitching together add-ons to approximate them.
Native project accounting, not a bolted-on module. There's a real difference between an ERP that was built with construction workflows in mind and one that added "job costing" as a feature to compete on a checklist. Ask specifically how percentage-of-completion, retainage, and commitment tracking work in the platform, and ask to see it, not just hear about it.
Field-to-office connection in real time. If your PMs are emailing spreadsheets to accounting, or if cost data takes days to move from the field into the books, you haven't actually solved the problem. You've just changed which system the workaround happens in.
Integration with the field tools you already use. Most construction companies already run something like Procore for field operations. Whatever ERP you choose needs to integrate with that natively, not through a custom-built connector that becomes a maintenance headache down the line.
Subcontractor management depth. Compliance tracking, lien waivers, insurance certificates, payment applications: these are daily operational realities in construction, and a platform that treats them as an afterthought will cost you time every single week.
An implementation partner who's actually built this before. This is where a lot of construction ERP projects go sideways. A partner without specific construction experience will configure the system around generic assumptions that don't match how contractors actually operate, from job costing structures to retainage rules to reporting needs that are specific to the industry. Ask for construction-specific references and results, not a general client list.
It's not "does QuickBooks technically still work?" Of course it does. You're running the business on it right now. The real question is: can you see project margin in real time, while there's still time to act on it, or are you finding out a job went over budget only after it's already closed?
If it's the latter, you're not managing project profitability. You're documenting it after the fact, which is a fundamentally different, and much more expensive, thing.
Construction is one of the industries where the gap between QuickBooks and a purpose-built ERP shows up fastest and costs the most. If you're running projects at meaningful scale and still reconciling job costs manually, that gap is very likely already costing you more than the ERP would.
A Catalyst360 Discovery Session with PTP is built to look specifically at how your projects run today, where cost visibility is breaking down, and whether a construction-depth platform like Acumatica's Construction Edition is the right fit. No generic pitch. No pressure to commit to a platform on day one.
Talk to PTP About ERP for Your Construction Business →
See how Acumatica Construction Edition works →