Multi-entity construction accounting: where it breaks down

Lallier Construction, a family-owned contractor running four entities, was recording every intercompany transaction twice and spending 10 to 20 hours a week reconciling the results by hand. After moving to Intuit Enterprise Suite, the company cut its month-end intercompany reconciliation time by up to 90%.

That time wasn't lost inside any single job. A construction firm's estimating, job costing, and billing can work well within each function and still create problems the moment the financial data must be consolidated.

The breakdown shows up in the seam between entities, where WIP that rolls up cleanly within one company file has to be stitched together by hand, and job-cost data, intercompany balances, and billing all need to be reconciled.

Today, we'll cover where that seam tends to start and what’s worth requiring from a system before you scale past it.

What changes when a construction firm operates more than one entity

Multi-entity accounting has to do everything single-entity accounting does, then consolidate it across entities without losing the job-level detail a controller needs to manage margin. A few specific breakdowns tend to drive that friction, and each one feeds the next.

Cost codes and GL structure

The chart of accounts, or GL structure, is how a company organizes its ledger accounts. Cost codes, the categories used to track costs within a specific job, are a separate layer underneath the chart of accounts, typically organized by phase or trade. A single entity can keep both loose because one controller knows where everything lives.

Add a second entity with its own cost code conventions, and the same cost no longer means the same thing across entities unless someone manually maps it. A system that lets every entity share a single chart of accounts and cost code structure removes the mapping step, though few systems offer this by default.

Billing and retainage

The inconsistent way entities track job and financial data carries into billing. AIA-style billing and retainage workflows can be managed within a single company file. Across entities, controllers may have to reconcile draw schedules and retainage across several sets of books that use different formats.

A single billing workflow and a centralized view eliminate that reconciliation work at every close, regardless of whether every entity's format currently differs.

Job costing and labor allocation

Crews and equipment often move between entities on multi-entity jobs, and without a shared system, it's easy to lose track of which entity a cost belongs to. That's what breaks job-profitability comparisons across a portfolio. Similar costs don't always land on the same entity's books in the same way.

Labor burden compounds the problem: the same crew can carry different burden rates and allocation rules depending on which entity runs payroll, so two jobs with identical field costs can report different margins for reasons unrelated to performance.

When a controller can't trust that a cost means the same thing on every entity's books, portfolio-level margin analysis stops being reliable, and margin comparability is exactly what a CFO needs to decide where to bid next.

Consolidated reporting

This is where the first three breakdowns converge. If you don't standardize cost codes, billing and job costing upstream, you end up manually reassembling data at every close. That makes it harder to get the consolidated, on-demand visibility a CFO needs.

In a Forrester study, organizations adopting the Intuit Enterprise Suite saw projected reductions of 75% to 95% in annual data-entry time and 60% to 95% in reconciliation task time by year three. These figures illustrate the potential time savings from integrating financial data and reducing manual work.

Bonding capacity and lender confidence

Lenders and sureties can rely on WIP and consolidated financial reporting when evaluating a contractor, often looking at the portfolio as a whole for multi-entity firms. Inconsistent or delayed reporting doesn't just slow down a close. It can also look like a red flag on the exact document a bank or bonding agent uses to decide how much capacity to extend.

Imagine that a three-entity contractor misses a bid deadline for a $5 million performance bond because cash balances take too long to consolidate by hand. A real-time, multi-entity cash view can help contractors avoid such delays by providing a current snapshot of cash across entities.

Signs it's time to upgrade, and what to look for instead

The breakdowns above point to a few practical requirements for any system. Get these pieces in place, and construction multi-entity management becomes a lot less of a monthly scramble.

The goal of construction project accounting

The goal of construction accounting is to maintain margin control across a complex portfolio of jobs at different stages. It provides the level of granularity needed to identify and prevent profit fade—or the expected margins on a job from shrinking because of uncaptured costs.

This form of project-based accounting gives you much greater control over matters like construction material costs and revenue recognition. Left unchecked, it will result in a write-down and impact your company’s overall quarterly performance.

The building blocks of construction project accounting are:

• Phases: These are individual parts of a job, usually major stages of work like groundwork, framing, roofing, or finishing. This can include site mobilization, MEP rough-ins, and commissioning.
• Cost codes: This is how you organize the classification of specific costs like materials, labor, equipment rental, or subcontractor fees. Larger construction firms often use CSI MasterFormat codes to distinguish between, for example, 03-3000 (cast-in-place concrete) and 05-1200 (structural steel framing).

Job costing ties these building blocks together by making sure every transaction is assigned to a specific project and cost code. The correct allocation of costs is the foundation of work-in-progress (WIP) reporting, which links the revenue you recognize with the actual work completed.

When companies record costs inconsistently and incorrectly, job-level P&Ls can become misleading. This lack of visibility is a prime driver in budget failure across the industry.

General accounting vs. construction project accounting: overview

How a connected multi-entity financial workflow works

A connected financial workflow should give every entity a shared chart of accounts and cost code structure, with billing, retainage and job costing following the same framework. Intuit Enterprise Suite is one option built around these requirements, offering a construction ERP that lets job-cost data roll up without a remapping exercise at close.

Billing, retainage, job costing, and labor allocation follow that shared structure across entities, while WIP consolidates into a single view. That kind of multi-entity consolidation reduces the manual reassembly needed to produce consistent financial reporting as you add entities.

That's the shift Lallier saw firsthand. Recording intercompany transactions twice had cost its finance team 10 to 20 hours a week; on the platform, that month-end reconciliation work dropped by up to 90%, freeing the team to focus on analysis rather than manual data entry.

Start reducing friction between your entities

Optimizing construction financial workflows starts with putting a consolidation layer in place before entity growth makes manual work harder to manage, rather than stitching one together after growth has already occurred. Intercompany eliminations are one piece of that; standardized cost codes and consolidated WIP reporting are the rest.

If your close still runs on spreadsheets stitched together across entities, Intuit Enterprise Suite for construction gives you a way to build the shared financial structure needed to streamline reporting as your business grows.

Recommended for you