Contractors: The Job Is Done. Do You Know If You Made Money?

The job finished on time. The crew performed. The customer signed off.

And you still can’t tell whether it made money.

Not because the numbers don’t exist — they do. They’re in a spreadsheet your controller built from three different exports, a stack of Friday timesheets, and a change order that was approved over the phone and never made it into the system. By the time construction job costing data is assembled, the job is closed and whatever lesson it held is academic.

This is not a staffing problem. It is what happens when the financial system isn’t built for how construction actually operates.

Key Takeaways

• Construction businesses lose margin most often in the gap between field operations and financial records — not on bad jobs
• Job costing, progress billing, change order tracking, and field-to-office data sync are where most mid-market accounting systems break first
• Intuit launched a construction edition of Intuit Enterprise Suite in February 2026, purpose-built for mid-market builders and contractors
• The construction edition includes cost code-level job costing, AIA-style invoicing, project phases, and construction-specific reporting — contact Intuit directly to understand current availability and eligibility
• For multi-entity construction businesses, IES handles consolidated reporting and intercompany transactions natively, without the spreadsheet assembly that slows close and erodes confidence in the numbers
• The right question isn’t which software to buy — it’s whether your current system can support the next phase of the business

Where the Money Actually Goes

Construction margin erosion rarely announces itself. It accumulates across dozens of small disconnects that each seem manageable on their own.

The estimator bids the next job using gut feel because last year’s actuals aren’t accessible in any useful format. The foreman tracks labor hours in a notebook and hands them in Friday afternoon. Subcontractor invoices arrive at month-end and get coded fast, without matching to cost codes. The change order was approved over the phone and entered into the system three weeks later — after the job already closed.

None of that looks like a system failure. It looks like a busy season.

The structural problem is that field and office operate on different timelines. Work happens in real time. Financial records catch up — if at all — at the end of the week, or the month, or whenever the controller surfaces from the last close. That gap is where labor costs get miscoded, where change orders disappear, and where billing falls behind the work already performed.

That billing lag carries a direct cash flow cost. A specialty contractor doing $10 million in annual revenue running 30 to 60 days behind on progress billing is financing its clients’ projects out of its own operating cash. That isn’t a billing process problem. It’s a structural one.

For a business running 20 or 30 active jobs, knowing which ones are profitable right now — not last month, not when they close — requires a system that tracks actuals against budgets by cost code and phase in real time. For businesses whose financial structure has moved beyond what their current system was designed to handle, the answer is often a controller who exports data, builds the comparison in Excel, spots the errors, fixes them, and delivers a report that’s already a week old when leadership reads it.

What Intuit Enterprise Suite Is Built to Address

Intuit launched a construction edition of Intuit Enterprise Suite in February 2026 — its first industry-specific edition of IES, built specifically for mid-market contractors and the operational complexity they run.

The construction edition is currently available in open beta for IES customers in the construction industry at no additional cost, and as a paid add-on for QuickBooks Online Advanced customers. Contact Intuit directly to understand current availability, eligibility, and scope before incorporating specific features into your planning.

Cost code-level job costing connected to payroll. IES tracks projects at the cost code level. Labor costs flow into projects automatically through payroll and time tracking — no manual export, no re-entry. The cost rate calculator defines precise hourly costs including burden, so job cost data reflects what labor actually costs rather than just the payroll rate. Estimates and actuals can be compared at the cost code level as the job progresses. Not after it closes.

Project phases, change order tracking, and AIA invoicing. Budgets and estimates are structured by project phase, giving controllers and project managers layered visibility into where a job stands against its plan at each stage. Change orders — including negative change orders — are tracked within the system rather than in email threads that live outside the books. AIA-style invoicing is supported natively, meaning progress billing is generated from actual project data instead of manually prepared from a schedule of values maintained in a separate document. That is the mechanism that closes the billing lag.

Construction-specific reporting. IES includes 200+ report templates, with 15 or more built specifically for construction: Cost to Complete, Work in Progress, Committed Costs, Change Orders, Project Status, Project Costs by Vendor and Product, Time by Employee and Project. These reports pull from native project and cost code data — not from exports assembled by hand.

AI-driven project profitability monitoring. IES flags when a project is trending over budget, identifies what’s driving the variance, and surfaces that analysis without requiring a controller to build it manually. Intuit AI operates across invoices, bills, payroll, and hourly costs. For construction businesses where a job can go over budget in the field before the books reflect it, knowing at week three versus knowing at close is the difference between a recoverable problem and a margin hit you can’t undo.

Field-to-office data flow. IES is accessible via cloud across web, iOS, Android, and iPad. Project data, purchase orders, and time entry can be recorded from the jobsite in real time and flow into financials automatically — rather than waiting for a Friday afternoon data entry session that may or may not happen.

What This Means When You’re Running More Than One Entity

Many mid-market construction businesses operate more than one legal entity — a primary operating company, an equipment holding entity, a new division structured separately for liability or tax reasons. QuickBooks Online is designed around a single-entity file structure, which works well for most businesses. When a construction business grows to multiple legal entities, that architecture requires separate files for each — which means month-end close involves logging in and out of multiple accounts, reconciling intercompany transactions by hand, and assembling a consolidated picture in a spreadsheet.

IES handles multi-entity management natively. Multiple entities, subsidiaries, and locations within a single system, with automated intercompany transactions and consolidated reporting that updates in real time. A construction business with three entities gets a unified organizational view and can drill into any single entity from one dashboard — without changing files or rebuilding data outside the system.

If multi-entity management is the primary driver for this conversation, the post on what causes businesses to outgrow QuickBooks Online covers that in more depth.
Related Content: When Your Business Outgrows QuickBooks Online

Example: The Specialty Contractor Running Two Sets of Books

The following is an example to show how this works in practice — not a specific client case study.

A specialty mechanical contractor does $18 million in annual revenue across 35 to 40 active projects. The business operates two legal entities. The controller manages two separate QBO files. At month-end, she exports job cost data into Excel, compares it to the project management software — which doesn’t sync to accounting — and reconciles the two manually. The process takes three to four days. Change orders live in a separate spreadsheet. AIA invoices are prepared in Word from a template. Billing goes out late because the data needed to prepare it accurately is never all in one place at the same time.

The owner knows which jobs are in trouble. But only because he’s talking to project managers — not because the system is telling him.

In IES, project management, job costing, billing, and financial reporting live in the same system. Labor costs flow into project actuals through payroll. Change orders are tracked natively. AIA invoices are generated from actual project data. The controller’s three-day close process isn’t eliminated — but the manual assembly component is significantly reduced, and the owner has visibility into project profitability without waiting for end-of-month reconciliation.

When This Is the Wrong Move

IES is not the right answer for every construction business that is frustrated with QBO.

If the business operates as a single entity, runs fewer than 20 active projects, and the job costing problems trace back to setup rather than platform capability, the right first step is almost always a QBO implementation review — not a migration. Many construction job costing problems in QBO come from chart of accounts design, class structure, or bank feed configuration that was never built for the business. Fixing those problems is faster and less expensive than moving to IES.

If the business is considering IES primarily because the controller is overwhelmed, that warrants a careful look. Overwhelmed controllers typically reflect a combination of system problems and workflow problems. A move to IES addresses the system problems. It does not fix the workflow problems a system upgrade doesn’t touch. If workflow is the primary issue, the IES transition won’t deliver the relief the business expects.

The construction edition of IES is built for businesses roughly in the $3 million to $50+ million range running meaningful project complexity — multiple active jobs, progress billing, cost code tracking, and either a multi-entity structure or serious growth toward one. Below that threshold, the implementation investment is difficult to justify.

Peak Advisers works with businesses at both decision points — those who need a QBO restructure and those who need a migration. The first step is understanding which problem you actually have. Our post on the ERP evaluation most growing businesses get wrong is a useful place to start if you’re not sure.

How Peak Advisers Approaches This Conversation

Peak Advisers is a certified QuickBooks Solution Provider with more than 30,000 hours of hands-on experience and a QuickBooks Solution Provider since 2011. We work with the full range of Intuit products — including Intuit Enterprise Suite — because our job is to match the right tool to the right business, not to sell the same solution to every client.

When a construction business owner comes to us with a job costing problem, a slow close, or a financial picture that requires manual assembly before leadership can read it, the first conversation is never about which software to buy. It is about understanding where the system is actually failing and what that failure is costing — in controller time, billing lag, margin erosion on jobs that were profitable on paper and weren’t in practice.

From that picture, the right next step becomes clear. Sometimes that’s a QBO restructuring. Sometimes it’s a migration to IES. Often it’s both, in sequence.

If you want an honest assessment of whether your current financial structure can support where your construction business is heading, that is the conversation we are built for.