Consolidated WIP for multi-entity contractors: how to close the books across entities without losing job-level detail
A consolidated WIP schedule is a single work-in-progress report that combines contract value, costs incurred, estimated cost to complete, and over/under-billing across every legal entity in a contractor's organization, so the CFO sees total job exposure in one view rather than separate entity snapshots. Entity-level WIP reports hide intercompany cost transfers, shared equipment charges, and cross-entity billing mismatches. That means the roll-up the CFO signs off on is structurally incomplete before a single formula error is made.
Key takeaways
Here is what matters most before you compare options.
What consolidated WIP is: A consolidated WIP schedule combines work-in-progress data across every legal entity so the CFO sees total job exposure, overbilling, and cost-to-complete in one view rather than separate entity snapshots.
The distortion problem: Entity-level WIP hides intercompany cost transfers, shared equipment charges, and cross-entity billing mismatches, making any manual roll-up unreliable without eliminations applied at the consolidated layer.
Surety standard: Sureties expect a single consolidated WIP schedule showing percentage-of-completion and over/under-billing across all entities, not separate reports stapled together — and the inability to produce one quickly signals weak operational controls.
Two paths to consolidation: Multi-entity contractors can keep QuickBooks Online per entity and consolidate reporting in LiveFlow FP&A, or migrate to Flow ERP, where multi-entity WIP is built into the accounting ledger natively with automatic intercompany eliminations.
Implementation speed: Flow ERP migrates books from QuickBooks Online in under 2 minutes, with books live in 11 days or less — no six-figure implementation required.
Why does entity-level WIP give the CFO a false picture of job performance?
Entity-level WIP reports show job performance within one legal entity but cannot surface costs or billings that have moved across entities, making the roll-up structurally incomplete. The problem isn't bad data entry — it's that each entity's WIP schedule is correct on its own terms, while the consolidated picture remains distorted by design.
Three specific failures compound the problem. First, when cost transfers from one entity to another, the originating entity's WIP drops the cost from its schedule. The receiving entity picks it up, but without a consolidated view, the cost appears to have changed jobs rather than moved within the enterprise. Second, overbilling in one entity is offset by underbilling in another, so the aggregate exposure looks balanced when the actual cash drain is concentrated in specific jobs. Third, the CFO approves a WIP number that has no elimination layer applied — meaning internal revenue between entities inflates the consolidated gross contract value.
What a WIP schedule is and what it's supposed to show
A WIP schedule is the accounting document that records contract value, costs incurred to date, estimated cost to complete, and the resulting over- or under-billing position for each active job. Percentage-of-completion is the method of measuring how much of a contract's revenue has been earned based on costs incurred relative to total estimated costs — for example, if a job has consumed 60% of its estimated total cost, the schedule recognizes 60% of the contract value as earned revenue. See how to create a WIP schedule for a step-by-step breakdown of the mechanics. The schedule is both a management tool and an audit document — it is what your surety, lender, and CPA will request first.
The three numbers that break when you roll up entity-level schedules
Three specific failure points appear in every manual multi-entity roll-up. First, revenue is recognized twice when one entity bills another for subcontracted scope — the billing entity records contract revenue, and the receiving entity also records its full contract value, so the group's total backlog and earned revenue are both overstated. Second, equipment cost is double-counted when a plant entity charges a job entity for crane or fleet use without elimination; the plant entity shows rental revenue and the job entity shows a rental cost, and both survive into the consolidated schedule. Third, over/under-billing netting hides which jobs are actually a cash drain — a $200,000 overbilled job in Entity A offsets a $200,000 underbilled job in Entity B, and the consolidated total shows zero net exposure even though Entity B has a genuine liquidity problem. Understanding over- and under-billing in construction is the foundation for seeing why these netting effects are dangerous at scale.
How do intercompany jobs, shared equipment, and cost transfers distort your consolidated WIP?
Intercompany transactions — equipment rentals, shared labor, material transfers, and management fees between related entities — must be eliminated from a consolidated WIP schedule, or the combined revenue and cost figures are overstated. These transactions are legitimate for entity-level reporting: each entity correctly records its side of the exchange. The problem is exclusively at the consolidated layer, where internal activity inflates both the revenue and cost lines of the group P&L and distorts the percentage-of-completion calculation for any job that spans entities.
General contractors operating with a plant or equipment-holding entity, a management entity, and one or more operating subsidiaries run into this constantly. Surety underwriters review the consolidated schedule precisely because they are underwriting the enterprise — not a single legal entity. A consolidated WIP that hasn't had eliminations applied will be sent back, or worse, accepted and later found to misrepresent the group's actual bonding capacity.
Equipment and plant entities: the elimination most teams miss
The most commonly missed elimination in multi-entity construction WIP occurs when a contractor operates a separate plant or equipment-holding entity that rents assets to job-site entities. The plant entity records rental revenue; the job entity records a rental cost. Both entries are correct at the entity level and both are wrong at the consolidated level, because the group cannot earn revenue from itself. The elimination follows a two-step sequence:
Identify all intercompany equipment charges flowing from the plant entity to each job entity during the period.
Eliminate the plant entity's rental revenue and the job entity's rental cost in the consolidated schedule before calculating percentage-of-completion — otherwise both the cost base and the denominator used to measure job progress are inflated.
Skipping this step overstates both consolidated revenue and consolidated cost. The percentage-of-completion ratio can still look plausible because the numerator and denominator move together, which makes this error particularly hard to catch in a spreadsheet-based roll-up.
Cross-entity job cost: when a job lives in more than one legal entity
A single construction project frequently spans multiple legal entities when bonding capacity, licensing requirements, or risk allocation demands separate structures for different scopes of work on the same project. For example, a GC may hold the prime contract in Entity A while a specialty trade license required for mechanical scope sits in Entity B. The consolidated WIP schedule must aggregate all costs and billings for that project across both entities and treat it as a single job for reporting purposes, with any intercompany billings between Entity A and Entity B eliminated. For specialty trade contractors managing job costing reporting across multiple license structures, this cross-entity aggregation is where spreadsheet-based consolidations break down permanently. Once a job lives in three or more entities, the manual reconciliation required to produce a clean single-job WIP line exceeds what a lean finance team can absorb at month-end.
What does a consolidated WIP pack need to include for surety approval?
A consolidated WIP pack for surety review must include a single schedule showing contract value, costs incurred, estimated cost to complete, percentage-of-completion, earned revenue, and over/under-billing for every active job across all entities, with intercompany transactions eliminated. Sureties underwrite the enterprise — they want to see the group's total bonding exposure, backlog quality, and cash position, not entity-level snapshots that require them to do the consolidation themselves.
A complete surety-ready pack contains four components:
Consolidated WIP schedule: Elimination-adjusted, showing every active job across all entities with percentage-of-completion calculated on the consolidated cost basis.
Backlog summary: Remaining contract value by entity and in aggregate, reconciled to the WIP schedule's contract values.
Aging of receivables: AR by entity and consolidated, with retainage separated from current billings.
Intercompany balance note: A disclosure of the intercompany transactions eliminated and confirmation that the elimination entries balance across all entities.
The ability to produce this pack quickly at month-end is itself a signal of operational control. A surety underwriter who receives a clean, elimination-adjusted consolidated WIP within five business days of month-end reads it as evidence that the finance function is organized and the job cost data is reliable. A pack that arrives two weeks late with a disclaimer about "pending intercompany reconciliation" signals the opposite. See the construction P&L template for a complementary view of how the P&L and WIP schedule connect in a surety review package.
The month-end close sequence that produces a clean WIP pack
Producing a surety-ready consolidated WIP requires a defined close sequence. Running it out of order — or running it all at once — produces reconciliation errors that force rework and extend the close. According to LiveFlow's Finance in the AI Era report (May 2026), 78% of finance leaders say waiting on data from other systems is the number one cause of close delays; for multi-entity contractors, intercompany reconciliation is among the biggest contributors. The correct order of operations is:
Close job costs at the entity level — lock each entity's cost coding so no late entries change the basis for percentage-of-completion.
Post intercompany charges and confirm intercompany balances agree across entities before any elimination entries are made.
Run eliminations at the consolidated layer, removing intercompany revenue, cost, and AR/AP from the group schedule.
Calculate percentage-of-completion on the consolidated job list using elimination-adjusted costs and total estimated costs.
Tie billing to the consolidated schedule and identify over/under positions by job, flagging any jobs where the billing exposure has changed materially since the prior period.
This five-step sequence requires either a system that enforces it natively or a heavily disciplined manual process with a documented close calendar. Most multi-entity contractors doing this work in spreadsheets report that steps 2 and 3 alone consume two to three days of controller time each month.
Should you use QuickBooks per entity with LiveFlow FP&A or switch to Flow ERP for native multi-entity WIP?
Multi-entity contractors have two practical paths to consolidated WIP reporting: keeping a QuickBooks Online file per entity and consolidating reporting in LiveFlow FP&A, or migrating to Flow ERP, which handles multi-entity accounting, job costing, intercompany eliminations, and WIP consolidation in a single ledger. Neither path is wrong — the right choice depends on where the team is in its growth, how frequently intercompany activity occurs, and whether the current close timeline is sustainable.
Comparing QBO per entity + LiveFlow FP&A vs. Flow ERP for consolidated WIP | ||
Dimension | QBO per entity + LiveFlow FP&A | Flow ERP (native multi-entity) |
|---|---|---|
Entity setup | Separate QBO file per entity; managed individually | All entities in a single workspace; no file switching |
WIP consolidation method | LiveFlow FP&A pulls live data from each QBO file and consolidates in a reporting layer | WIP rolls up natively from the shared ledger in real time |
Intercompany eliminations | Manual intervention required; LiveFlow FP&A surfaces the data, but elimination entries are posted manually | Eliminations calculated automatically at the transaction level; no manual posting |
Job cost reporting | Job costing remains within each QBO file; cross-entity job aggregation requires manual assembly | Job costs tagged across entities roll up to a consolidated job view natively |
Close timeline | Depends on how quickly each QBO file is closed; consolidation adds time on top | Continuous close design; consolidated view updates as transactions are posted |
Implementation time | LiveFlow FP&A connects to existing QBO files; minimal setup | Migrate from QBO in under 2 minutes; books live in 11 days or less |
When QuickBooks per entity + LiveFlow FP&A is the right call
A multi-entity contractor already running QuickBooks Online per entity, not ready to migrate systems, but needing consolidated WIP reporting and month-end visibility across files without manual exports is the right buyer for the LiveFlow FP&A path. LiveFlow FP&A pulls live data from each QBO file and surfaces the consolidated roll-up in a reporting layer, which means the controller stops spending days exporting and reformatting trial balances. One finance leader described the experience of managing multiple QBO files plainly: "We are kind of too big for QuickBooks Online... we are thinking that in the future we'll have to move into an ERP, but that roadmap is probably one to two years out." LiveFlow FP&A is built for exactly that window — a bridge that produces better reporting without requiring a system change. The honest limitation: intercompany eliminations and cross-entity job cost aggregation still require manual work in this setup. If the Buildertrend-QuickBooks WIP integration is already part of the stack, LiveFlow FP&A layers on top without disrupting that connection.
When Flow ERP is the right call
A contractor managing three or more entities, running intercompany equipment or cost transfers regularly, and preparing monthly consolidated WIP packs for a surety has outgrown the QuickBooks-plus-reporting-layer approach. Flow ERP has multi-entity architecture built into the core ledger — entity-level drill-down and consolidated views are available without exports, eliminations are calculated automatically at the transaction level, and job costs tagged across entities roll up to a consolidated WIP schedule in the same system where the books live. The AI Month-End Close Agent in Flow ERP runs a dynamic checklist tied to actual data, so the controller sees exactly what is still open across entities without chasing email threads. Account Harmonization is the Flow ERP feature that standardizes chart of accounts naming conventions across entities using AI on ingestion, which means cost code mismatches between entity files are resolved at migration rather than manually reconciled every month. Teams migrating from QuickBooks Online move their books in under 2 minutes, with books live in 11 days or less. See Flow ERP for construction for details on how the platform handles construction-specific job costing and multi-entity consolidation.
What controls do you need to close a consolidated WIP accurately every month?
Accurate consolidated WIP depends on three operational controls: a single chart of accounts and cost code structure shared across all entities, defined job ownership rules that prevent the same project from appearing in two entity WIP schedules, and a closing calendar that sequences entity-level close before consolidated close. These controls are necessary regardless of which system the team uses — they are the governance layer that makes the technology work correctly.
Standardized cost codes and chart of accounts across entities: Every entity must use the same cost code structure so that concrete, labor, equipment, and subcontractor costs aggregate cleanly at the consolidated level.
Job ownership policy: Define which entity owns each job, and document the treatment for jobs where scope crosses entities — including how intercompany billings between those entities are eliminated in the consolidated WIP.
The closing calendar: Entity-level books must be locked before the consolidated WIP is run. Running consolidation against open entity files produces a snapshot that changes as late entries post, forcing rework.
Cost code standardization across entities
Mismatched cost codes across entity files make consolidated WIP comparison impossible at the job level. If one entity codes concrete under "03-000" and another codes it under "Subcontractor-Concrete," the roll-up produces a meaningless sum that can't be analyzed by cost type or benchmarked against prior jobs. The standardization requirement is non-negotiable for any team producing a surety-ready consolidated WIP schedule. Flow ERP's Account Harmonization feature uses AI to align chart of accounts naming conventions across entities on ingestion, resolving cost code mismatches at migration rather than making them a permanent manual burden for the controller.
The closing calendar: sequencing entity close before consolidated close
A consolidated WIP schedule cannot be run until every entity's books are closed and intercompany balances are confirmed to agree. The practical sequencing is: entity controllers close their files by day X of the following month; intercompany reconciliation runs on day X+1 or X+2; the consolidated WIP is produced on day X+3. Any entity that misses its close deadline holds up the entire consolidated schedule — which is why a documented, enforced calendar is not optional for multi-entity contractors. Flow ERP's AI Month-End Close Agent runs a dynamic close checklist tied to actual data across all entities, so the controller sees which entities are still open and what is blocking them without sending a single status email. Continuous close is the practice of reconciling and reviewing financials throughout the month rather than in a single end-of-month push — and it is the architecture Flow ERP is built on, which means the consolidated WIP is always close to current rather than a product of a compressed five-day sprint.
Ready to close consolidated WIP faster?
Consolidated WIP for multi-entity contractors is a structural accounting challenge that requires intercompany eliminations, standardized cost codes, a sequenced close calendar, and either a purpose-built ledger or a disciplined reporting layer on top of existing QuickBooks files. Entity-level WIP schedules will always lie to the CFO when intercompany activity is in play — the only fix is eliminating that activity at the consolidated layer before the schedule is produced. Whether the right path is LiveFlow FP&A as a bridge on your current QBO stack or a migration to Flow ERP's native multi-entity ledger depends on your entity count, your intercompany complexity, and how much longer your current close timeline is sustainable. For a broader view of where consolidated WIP fits in the full construction finance picture, see our guide to the best construction accounting software by growth stage.
Book a demo to see how Flow ERP handles multi-entity WIP consolidation, intercompany eliminations, and the full close sequence in a single platform.
Frequently asked questions
Here is what matters most before you compare options.
What is a consolidated WIP schedule in construction accounting?
A consolidated WIP schedule is a single work-in-progress report that aggregates contract value, costs incurred, estimated cost to complete, percentage-of-completion, and over/under-billing across all legal entities in a construction enterprise, with intercompany transactions eliminated. It gives the CFO and surety underwriter a complete picture of total job exposure rather than separate entity-level snapshots that hide cross-entity billing and cost activity. In a multi-entity contractor, producing a consolidated WIP schedule requires intercompany eliminations — without them, internal revenue and cost inflate the group's reported position. Flow ERP produces this consolidated view natively; teams still on QuickBooks Online per entity can consolidate reporting using LiveFlow FP&A.
What does it mean when a company is consolidated for financial reporting purposes?
When a company is consolidated for financial reporting, it means the financial results of all related legal entities under common ownership are combined into a single set of statements, with intercompany transactions eliminated so the group reports only its activity with external third parties. For construction contractors, consolidation applies to the WIP schedule, the balance sheet, and the P&L — and it is required by GAAP under ASC 810 when a parent company controls one or more subsidiaries. Sureties, lenders, and auditors evaluate the consolidated entity, not individual legal entities in isolation.
How do you consolidate WIP schedules across multiple legal entities?
Consolidating WIP schedules across multiple legal entities requires five steps: close job costs at the entity level, confirm intercompany balances agree across entities, post and eliminate intercompany transactions at the consolidated layer, calculate percentage-of-completion on the elimination-adjusted cost basis, and tie billing to the consolidated schedule to identify over/under positions. The most error-prone step is the intercompany elimination — equipment charges, management fees, and cross-entity billings must all net to zero in the consolidated view or the revenue and cost figures are overstated. Forvis Mazars and other construction-focused audit firms consistently flag intercompany reconciliation as a leading cause of WIP restatements. Flow ERP automates the elimination step at the transaction level, so the consolidated WIP is accurate as soon as entity-level costs are posted.
What does consolidated mean in accounting?
In accounting, consolidated means that the financial statements of a parent company and all entities it controls are combined into a single set of reports, after eliminating transactions between those entities. The purpose is to show the economic reality of the enterprise as a whole — what it earns from and owes to external parties — rather than inflating results with internal activity. For multi-entity contractors, the consolidation concept applies directly to financial consolidation across job sites, subsidiaries, and legal entities that share revenue, cost, or equipment.
What is a consolidated document in the context of a surety WIP pack?
In a surety WIP pack, a consolidated document is a single WIP schedule that combines the work-in-progress data of all legal entities in the contractor's organization into one elimination-adjusted report, rather than separate entity-level schedules submitted individually. Sureties require the consolidated view because they underwrite the enterprise's total bonding capacity, which depends on the group's aggregate backlog, over/under-billing exposure, and cash position. A surety-ready consolidated WIP pack also includes a backlog summary, aging AR by entity, and an intercompany balance note confirming that eliminations have been applied. Deloitte's construction practice notes that surety underwriters treat the timeliness and accuracy of consolidated WIP production as a direct proxy for the strength of a contractor's financial controls.
